SUSE 10.0
-
The Beatles
- Fear me for I am root
- Posts: 6285
- Joined: Tue May 24, 2005 8:12 pm
-
The Beatles
- Fear me for I am root
- Posts: 6285
- Joined: Tue May 24, 2005 8:12 pm
-
Floppy_Drive
- Advanced Member
- Posts: 99
- Joined: Mon Aug 01, 2005 3:21 pm
Hmm. I have no idea what to say. I am glad you find this funny. Thanks for the information:So that's what you do! :*laughs*: I messed with config files all night. I did get the x server running.
Undefined said Undefined messed with config files all night.
When? Where can I get the x server running?
-
Guest
-
Floppy_Drive
- Advanced Member
- Posts: 99
- Joined: Mon Aug 01, 2005 3:21 pm
The whole thing is somewhat ironic, considering that SUSE has been the distro I have had the LEAST trouble with. Ubuntu was probably the worse.
If you go down to the woods today, you better not go alone
It's a lovely day in the woods today, but safer to stay at home
BECAUSE EVIL FREEN IS KILLING ALL THE TEDDY BEARS AT THEIR PICNIC
It's a lovely day in the woods today, but safer to stay at home
BECAUSE EVIL FREEN IS KILLING ALL THE TEDDY BEARS AT THEIR PICNIC
-
The Beatles
- Fear me for I am root
- Posts: 6285
- Joined: Tue May 24, 2005 8:12 pm
Devari -- thanks for the tip, I shall try it soon. I hope it doesn't mind me spawning 16 instances of it and leaving them lying about for weeks. XD
So now, the first problem I had with SUSE, and why it shows SUSE is very good. To wit: I accidentally unplugged the power cable when pushing the laptop around, and in the middle of some work it died. Pretty straightforward. Then I start it again, and decide to resume work on a document. I try to double-click 'Home' icon on my Desktop -- but a problem! Amarok seems to start, and what's more, when the icon appears in the tray, I can't click it!
Here comes the techie reaction. Some more failed experiments and killall amarokapps later, I begin googling. The sacred name kfmclient comes up. I do a --help and start messing around. More killall amarokapps later, I begin to get slightly frustrated. I move my .kde directory to a backup, create a new user with YAST, and copy their .kde into mine. Logout, login, (virtual terminal to make sure kdm didn't touch my .kde), and whee. Except now no preferences. I start copying over bits and pieces of my kde backup, directories at a time; eventually the double-click breaks again. I am frustrated and continue googling for the application/x-desktop stuff. Eventually I find a forum post that says nobody has any idea what is going on. I find a mailing list post in the same vein. Then I find a third forum post in which a newbie asks the same question as I had. Nobody has any idea, but the newbie does:
What the non-techie reaction is. He reinstalls amarok with YAST. Voila, problem fixed.
The point? Well, there are several, but I drew two conclusions:
1. Approach SUSE with the mentality of "Everything works, but if it doesn't, don't think about it too hard, think what your Aunt Margie might do, because SUSE is very good."
2. SUSE's rpm system is so well-engineered, that it resolved the problem with KDE's (I assume corrupted) file associations. That must mean at the very least that they put a lot of design thought, redundancy, and error-handling into their rpm system. I am very impressed.
So now, the first problem I had with SUSE, and why it shows SUSE is very good. To wit: I accidentally unplugged the power cable when pushing the laptop around, and in the middle of some work it died. Pretty straightforward. Then I start it again, and decide to resume work on a document. I try to double-click 'Home' icon on my Desktop -- but a problem! Amarok seems to start, and what's more, when the icon appears in the tray, I can't click it!
Here comes the techie reaction. Some more failed experiments and killall amarokapps later, I begin googling. The sacred name kfmclient comes up. I do a --help and start messing around. More killall amarokapps later, I begin to get slightly frustrated. I move my .kde directory to a backup, create a new user with YAST, and copy their .kde into mine. Logout, login, (virtual terminal to make sure kdm didn't touch my .kde), and whee. Except now no preferences. I start copying over bits and pieces of my kde backup, directories at a time; eventually the double-click breaks again. I am frustrated and continue googling for the application/x-desktop stuff. Eventually I find a forum post that says nobody has any idea what is going on. I find a mailing list post in the same vein. Then I find a third forum post in which a newbie asks the same question as I had. Nobody has any idea, but the newbie does:
What the non-techie reaction is. He reinstalls amarok with YAST. Voila, problem fixed.
The point? Well, there are several, but I drew two conclusions:
1. Approach SUSE with the mentality of "Everything works, but if it doesn't, don't think about it too hard, think what your Aunt Margie might do, because SUSE is very good."
2. SUSE's rpm system is so well-engineered, that it resolved the problem with KDE's (I assume corrupted) file associations. That must mean at the very least that they put a lot of design thought, redundancy, and error-handling into their rpm system. I am very impressed.
:wq
-
Members connected in real time
