Message-Id: <200012270410.WAA71674048@smtppop2pub.verizon.net>
Date: Tue, 26 Dec 2000 23:12:46 -0500
From: Ed Harrison
Date: Tue, 26 Dec 2000 22:00:47 -0800
From: Ben Rosenberg
From: Eduardo Diaz Uriarte
I have both kde1 and kde2. I read the /www.kde.org/kde1-and-kde2.html and set everything up as they said.
As root or user, if I am in init 2, WINDOWMANAGER=kde2 startx, KDE2 starts perfectly, remembers changes I make and exits cleanly. Does it really remember changes? I do the same (with the files for my suse 6.4 from the suse site installed) and it doesn't remember changes.
Any hints about this silly thing?
Message-ID: <3A4A5709.47576BDF@compro.net>
Date: Wed, 27 Dec 2000 15:54:33 -0500
From: Mark Hounschell
On Wed, 27 Dec 2000, you wrote:
I have both kde1 and kde2. I read the /www.kde.org/kde1-and-kde2.html and set everything up as they said.
As root or user, if I am in init 2, WINDOWMANAGER=kde2 startx, KDE2 starts perfectly, remembers changes I make and exits cleanly. Does it really remember changes? I do the same (with the files for my suse 6.4 from the suse site installed) and it doesn't remember changes.
What kind of CHANGES are you talking about? Every thing I've done in KDE2 environment has still been there when I returned. What CHANGES are you refering to? -- Mark Hounschell markh@compro.net
From: Eduardo Diaz Uriarte
Eduardo Diaz Uriarte wrote:
On Wed, 27 Dec 2000, you wrote:
I have both kde1 and kde2. I read the /www.kde.org/kde1-and-kde2.html and set everything up as they said.
As root or user, if I am in init 2, WINDOWMANAGER=kde2 startx, KDE2 starts perfectly, remembers changes I make and exits cleanly. Does it really remember changes? I do the same (with the files for my suse 6.4 from the suse site installed) and it doesn't remember changes.
What kind of CHANGES are you talking about? Every thing I've done in KDE2 environment has still been there when I returned. What CHANGES are you refering to?
If I change the theme for kde2 or the monitor power management, kde2 is able to remember that. But, particullarly, if I change the size, position and auto-hide option of the panel, or the screensaver, I get again the defaults in the next sesion. Thanks <p>> --
Mark Hounschell markh@compro.net
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Message-ID: <3A4B6199.5543017E@compro.net>
Date: Thu, 28 Dec 2000 10:51:53 -0500
From: Mark Hounschell
On Wed, 27 Dec 2000, you wrote:
Eduardo Diaz Uriarte wrote:
On Wed, 27 Dec 2000, you wrote:
I have both kde1 and kde2. I read the /www.kde.org/kde1-and-kde2.html and set everything up as they said.
As root or user, if I am in init 2, WINDOWMANAGER=kde2 startx, KDE2 starts perfectly, remembers changes I make and exits cleanly. Does it really remember changes? I do the same (with the files for my suse 6.4 from the suse site installed) and it doesn't remember changes.
What kind of CHANGES are you talking about? Every thing I've done in KDE2 environment has still been there when I returned. What CHANGES are you refering to?
If I change the theme for kde2 or the monitor power management, kde2 is able to remember that. But, particullarly, if I change the size, position and auto-hide option of the panel, or the screensaver, I get again the defaults in the next sesion.
Thanks
The setup info for the size, position, and auto-hide option of the panel is written to a file called /home/user/KDesktop/share/config/kickerrc which is read by the kicker program which is lit off by kdeinit along with a whole lot of other programs when kde2 starts. Do you have all these programs running after logging in to kde2? This is the output from a "ps -ax | grep kde" 336 ? S 0:00 /opt/kde/bin/kdm 393 ? S 0:00 sh --login /opt/kde2/bin/startkde 441 ? S 0:00 kdeinit: dcopserver 443 ? S 0:00 kdeinit: klauncher 445 ? S 0:01 kdeinit: kdesktop 457 ? S 0:00 kdeinit: kded 468 ? S 0:00 kdeinit: kxmlrpcd 488 ? S 0:02 kdeinit: kicker 490 ? S 0:00 kdeinit: klipper 494 ? S 0:00 kdeinit: khotkeys 496 ? S 0:00 kdeinit: Running... 497 ? S 0:00 kdeinit: kwrited 504 ? S 0:00 kdeinit: kwin 517 ? S 0:01 kdeinit: konsole All of these should be running. -- Mark Hounschell markh@compro.net
Message-ID: <3A4B82A1.36BD0CC0@compro.net>
Date: Thu, 28 Dec 2000 13:12:49 -0500
From: Mark Hounschell
As root or user, if I am in init 2, WINDOWMANAGER=kde2 startx, KDE2 starts perfectly, remembers changes I make and exits cleanly. Does it really remember changes? I do the same (with the files for my suse 6.4 from the suse site installed) and it doesn't remember changes.
What kind of CHANGES are you talking about? Every thing I've done in KDE2 environment has still been there when I returned. What CHANGES are you refering to?
If I change the theme for kde2 or the monitor power management, kde2 is able to remember that. But, particullarly, if I change the size, position and auto-hide option of the panel, or the screensaver, I get again the defaults in the next sesion.
Thanks
The setup info for the size, position, and auto-hide option of the panel is written to a file called /home/user/KDesktop/share/config/kickerrc which is read by the kicker program which is lit off by kdeinit along with a whole lot of other programs when kde2 starts. Do you have all these programs running after logging in to kde2?
This is the output from a "ps -ax | grep kde" 336 ? S 0:00 /opt/kde/bin/kdm 393 ? S 0:00 sh --login /opt/kde2/bin/startkde 441 ? S 0:00 kdeinit: dcopserver 443 ? S 0:00 kdeinit: klauncher 445 ? S 0:01 kdeinit: kdesktop 457 ? S 0:00 kdeinit: kded 468 ? S 0:00 kdeinit: kxmlrpcd 488 ? S 0:02 kdeinit: kicker 490 ? S 0:00 kdeinit: klipper 494 ? S 0:00 kdeinit: khotkeys 496 ? S 0:00 kdeinit: Running... 497 ? S 0:00 kdeinit: kwrited 504 ? S 0:00 kdeinit: kwin 517 ? S 0:01 kdeinit: konsole
All of these should be running.
ERRORERROR kickerrc is in $HOME/.kde2/share/config/
-- Mark Hounschell markh@compro.net
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- Mark Hounschell markh@compro.net
From: Eduardo Diaz Uriarte
The setup info for the size, position, and auto-hide option of the panel is written to a file called /home/user/KDesktop/share/config/kickerrc which is read by the kicker program which is lit off by kdeinit along with a whole lot of other programs when kde2 starts. Do you have all these programs running after logging in to kde2?
This is the output from a "ps -ax | grep kde" 336 ? S 0:00 /opt/kde/bin/kdm 393 ? S 0:00 sh --login /opt/kde2/bin/startkde 441 ? S 0:00 kdeinit: dcopserver 443 ? S 0:00 kdeinit: klauncher 445 ? S 0:01 kdeinit: kdesktop 457 ? S 0:00 kdeinit: kded 468 ? S 0:00 kdeinit: kxmlrpcd 488 ? S 0:02 kdeinit: kicker 490 ? S 0:00 kdeinit: klipper 494 ? S 0:00 kdeinit: khotkeys 496 ? S 0:00 kdeinit: Running... 497 ? S 0:00 kdeinit: kwrited 504 ? S 0:00 kdeinit: kwin 517 ? S 0:01 kdeinit: konsole
All of these should be running.
All of them are running, even kicker. And when I change the size of the panel or something like that I can see (with kpm) an increase of activity for kicker. And I have $HOME/.kde2/share/config/kickerrc. Could this be related to my Xserver (I still have xfree86 3.3.6, not the version 4)?
Message-ID: <3A4C5AAE.608991F0@cfl.rr.com>
Date: Fri, 29 Dec 2000 04:34:38 -0500
From: Mark Hounschell
On Thu, 28 Dec 2000, you wrote:
The setup info for the size, position, and auto-hide option of the panel is written to a file called /home/user/KDesktop/share/config/kickerrc which is read by the kicker program which is lit off by kdeinit along with a whole lot of other programs when kde2 starts. Do you have all these programs running after logging in to kde2?
This is the output from a "ps -ax | grep kde" 336 ? S 0:00 /opt/kde/bin/kdm 393 ? S 0:00 sh --login /opt/kde2/bin/startkde 441 ? S 0:00 kdeinit: dcopserver 443 ? S 0:00 kdeinit: klauncher 445 ? S 0:01 kdeinit: kdesktop 457 ? S 0:00 kdeinit: kded 468 ? S 0:00 kdeinit: kxmlrpcd 488 ? S 0:02 kdeinit: kicker 490 ? S 0:00 kdeinit: klipper 494 ? S 0:00 kdeinit: khotkeys 496 ? S 0:00 kdeinit: Running... 497 ? S 0:00 kdeinit: kwrited 504 ? S 0:00 kdeinit: kwin 517 ? S 0:01 kdeinit: konsole
All of these should be running.
All of them are running, even kicker. And when I change the size of the panel or something like that I can see (with kpm) an increase of activity for kicker. And I have $HOME/.kde2/share/config/kickerrc.
Could this be related to my Xserver (I still have xfree86 3.3.6, not the version 4)?
I don't think so. What are the output of these commands: env | grep kde and env | grep qt Do the contents of kickerrc (such as the AutoHide and size values) change when you set them? What are the permissions on $HOME/.kde2........and on down to kickerrc itself? -- Mark Hounschell dmarkh@cfl.rr.com
From: Eduardo Diaz Uriarte
All of them are running, even kicker. And when I change the size of the panel or something like that I can see (with kpm) an increase of activity for kicker. And I have $HOME/.kde2/share/config/kickerrc.
Could this be related to my Xserver (I still have xfree86 3.3.6, not the version 4)?
I don't think so. What are the output of these commands:
There you go:
env | grep kde LTDL_LIBRARY_PATH=/home/eduardo/.kde2/lib:/opt/kde2/lib LD_LIBRARY_PATH=/opt/kde/lib:/home/eduardo/.kde2/lib:/opt/kde2/lib KDEDIRS=/etc/opt/kde2:/opt/kde2 KDEHOME=/home/eduardo/.kde2 KDEDIR=/opt/kde WINDOWMANAGER=/usr/X11R6/bin/kde2 PATH=/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games/bin:/usr/games:/opt/gnome/bin:/opt/kde/bin:.
env | grep qt QTDIR=/usr/lib/qt
Do the contents of kickerrc (such as the AutoHide and size values) change when you set them? What are the permissions on $HOME/.kde2........and on down to kickerrc itself?
Almost evrything inthat directory has 600 except somethings with 644. Kickerrc change when I'm running kde2, but if I restart kde2, it is reset to the original again (diff tells me that). Another thing that makes mistakes like this is kandalf, that is launched every time I start even when I don't set 'lanch on startup'. I don't know if this is related, but kde2 launches this error (among others) when running (in fact, when shuting down): ICE default IO error handler doing an exit(), pid = 2109, errno = 0 waiting for X server to shut down kdeinit: Fatal IO error: client killed KLauncher: Exiting on signal 1 Thanks again
Message-ID: <3A4C86C1.BCDEADCF@cfl.rr.com>
Date: Fri, 29 Dec 2000 07:42:41 -0500
From: Mark Hounschell
On Fri, 29 Dec 2000, you wrote:
All of them are running, even kicker. And when I change the size of the panel or something like that I can see (with kpm) an increase of activity for kicker. And I have $HOME/.kde2/share/config/kickerrc.
Could this be related to my Xserver (I still have xfree86 3.3.6, not the version 4)?
I don't think so. What are the output of these commands:
There you go:
env | grep kde LTDL_LIBRARY_PATH=/home/eduardo/.kde2/lib:/opt/kde2/lib
LD_LIBRARY_PATH=/opt/kde/lib:/home/eduardo/.kde2/lib:/opt/kde2/lib This one doesn't look right it should look like: LD_LIBRARY_PATH=/opt/kde2/lib:/usr/lib/qt2/lib
KDEDIRS=/etc/opt/kde2:/opt/kde2 KDEHOME=/home/eduardo/.kde2
KDEDIR=/opt/kde This one doesn't look right it should look like: KDEDIR=/opt/kde2
<p>> WINDOWMANAGER=/usr/X11R6/bin/kde2
PATH=/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games/bin:/usr/games:/opt/gnome/bin:/opt/kde/bin:. This one doesn't look right as there is no path to /opt/kde2/bin like: PATH=/opt/kde2/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/lib/java/bin:/var/lib/dosemu:/usr/games/bin:/usr/games:/opt/gnome/bin:/opt/kde/bin:/usr/openwin/bin:.:/usr/lib/pgsql/bin:/opt/pilotsdk/bin
env | grep qt QTDIR=/usr/lib/qt
This one doesn't look right. Should be: LD_LIBRARY_PATH=/opt/kde2/lib:/usr/lib/qt2/lib QTDIR=/usr/lib/qt2
First make sure that: markh@harley:> locate bin/kde2 /opt/kde2/bin/kde2 /usr/X11R6/bin/kde2 - This one should be a link to /opt/kde2/bin/startkde markh@harley:>ls -al /opt/kde2/bin/kde2 /usr/X11R6/bin/kde2 -rw-r--r-- 1 root root 136 Dec 14 06:34 /opt/kde2/bin/kde2 lrwxrwxrwx 1 root root 22 Oct 26 19:48 /usr/X11R6/bin/kde2 ->/opt/kde2/bin/startkde ------------------------------------------------------------------------- Then your /opt/kde2/bin/kde2 should look like: export KDEDIR=/opt/kde2 export QTDIR=/usr/lib/qt2 - note that this path is a link to qt-2.2.2 export PATH=$KDEDIR/bin:$PATH export LD_LIBRARY_PATH=$KDEDIR/lib:$QTDIR/lib Then check that /usr/lib/qt* are like this: drwxr-xr-x 8 root root 4096 Apr 17 2000 qt drwxr-xr-x 8 root root 4096 Apr 17 2000 qt-2.2.1 drwxr-xr-x 10 root root 4096 Nov 30 20:47 qt-2.2.2 lrwxrwxrwx 1 root root 8 Dec 28 19:59 qt2 -> qt-2.2.2 ---------------------------------------------------------------------- Then check that /etc/X11/xdm/Xsession looks like: # If the user doesn't have their own xsession, then run # xinitrc if they exist XSESSION_IS_UP=yes export XSESSION_IS_UP if test "$WINDOWMANAGER" = "kde2"; then source /opt/kde2/bin/kde2 export KDEHOME=$HOME/.kde2 exec startkde exit 1 fi ----------------------------------------------------------- Then for good measure I added this to my /etc/profile.local: if test "$WINDOWMANAGER" = "kde2" ; then source /opt/kde2/bin/kde2 fi I'm sure that one or more of the above is your problem. Let me know. Fun stuff eh? -- Mark Hounschell dmarkh@cfl.rr.com
From: ally
On Wed, 27 Dec 2000, you wrote:
I have both kde1 and kde2. I read the /www.kde.org/kde1-and-kde2.html and set everything up as they said.
As root or user, if I am in init 2, WINDOWMANAGER=kde2 startx, KDE2 starts perfectly, remembers changes I make and exits cleanly.
Does it really remember changes? I do the same (with the files for my suse 6.4 from the suse site installed) and it doesn't remember changes.
Any hints about this silly thing?
Hi! I had the same problem! It is the kdebase2.0.1-0 version from SuSE ftp server. Get a version from KDE.org instead for SuSE 6.4, it works it took me less than a minute to install no problems since. Cheers Alan
participants (6)
-
ally＠chariot.net.au -
brosenb＠suse.com -
dmarkh＠cfl.rr.com -
ED.TMAN＠verizon.net -
ediazuri＠wanadoo.es -
markh＠compro.net