damn QTDIR and KDEDIR
![](https://seccdn.libravatar.org/avatar/4e8838f16e52ca85d1a8a2605013fe62.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi startkde in /opt/kde3 sets the above to kde3 and qt3 directories, but by the time i'm in kde they are back at the kde2 settings... What can change them between the two? Tom - -- Even though they raised the rate for first class mail in the United States we really shouldn't complain -- it's still only two cents a day. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8oMdMAEYnIVU7X9IRAo2eAJ9Xrz4fgp81KvQK/rlvIzYaPTWjKQCeLb3I W0SfTIUwrkl0sttVJT0vP7A= =C5Md -----END PGP SIGNATURE-----
![](https://seccdn.libravatar.org/avatar/d637c21d919d6695a47c052cbc32aac2.jpg?s=120&d=mm&r=g)
Hi, On Tuesday, March 26, 2002 at 19:08:58, Tom Wesley wrote:
startkde in /opt/kde3 sets the above to kde3 and qt3 directories, but by the time i'm in kde they are back at the kde2 settings... What can change them between the two?
There are several ways. One is to use your shell environment to set them. ~/.bashrc if you use bash. Henne -- Hendrik Vogelsang aka Henne mailto: hvogel@hennevogel.de I haven't been fucked like that since grade school! # figth club sigs made with fortune
![](https://seccdn.libravatar.org/avatar/4e8838f16e52ca85d1a8a2605013fe62.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 26 March 2002 7:23 pm, Henne Vogelsang wrote:
Hi,
On Tuesday, March 26, 2002 at 19:08:58, Tom Wesley wrote:
startkde in /opt/kde3 sets the above to kde3 and qt3 directories, but by the time i'm in kde they are back at the kde2 settings... What can change them between the two?
There are several ways. One is to use your shell environment to set them. ~/.bashrc if you use bash.
Henne
nice idea. was more interested in where it is that they are set back to qt2 etc. Is there anything else that gets executed? Could try forcing them in .bashrc Tom - -- Twenty Percent of Zero is Better than Nothing. -- Walt Kelly -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8oMzDAEYnIVU7X9IRAqykAJ9sWEkkqK8otMTibABHGtagNsqyEQCfYmjf CwxxZntMVQ5+LPYPYQfsafw= =GpVm -----END PGP SIGNATURE-----
![](https://seccdn.libravatar.org/avatar/98b4308dea1244ecdc466d868352a98f.jpg?s=120&d=mm&r=g)
Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 26 March 2002 7:23 pm, Henne Vogelsang wrote:
Hi,
On Tuesday, March 26, 2002 at 19:08:58, Tom Wesley wrote:
startkde in /opt/kde3 sets the above to kde3 and qt3 directories, but by the time i'm in kde they are back at the kde2 settings... What can change them between the two?
There are several ways. One is to use your shell environment to set them. ~/.bashrc if you use bash.
Henne
nice idea. was more interested in where it is that they are set back to qt2 etc. Is there anything else that gets executed? Could try forcing them in .bashrc
When I tried the kde3 stuff I stuck them in ~/.xinitrc or ~/.xsession if you use kdm or xdm. This way they will only be set in X's environment. It makes going between kde2 and kde3 very easy.
![](https://seccdn.libravatar.org/avatar/4e8838f16e52ca85d1a8a2605013fe62.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 26 March 2002 7:56 pm, Jesse Marlin wrote:
Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 26 March 2002 7:23 pm, Henne Vogelsang wrote:
Hi,
On Tuesday, March 26, 2002 at 19:08:58, Tom Wesley wrote:
startkde in /opt/kde3 sets the above to kde3 and qt3 directories, but by the time i'm in kde they are back at the kde2 settings... What can change them between the two?
There are several ways. One is to use your shell environment to set them. ~/.bashrc if you use bash.
Henne
nice idea. was more interested in where it is that they are set back to qt2 etc. Is there anything else that gets executed? Could try forcing them in .bashrc
When I tried the kde3 stuff I stuck them in ~/.xinitrc or ~/.xsession if you use kdm or xdm. This way they will only be set in X's environment. It makes going between kde2 and kde3 very easy.
I'm sorta pleased that this isn't just me then... a section of my .xinitrc: test -r $HOME/.xim && source $HOME/.xim # # Add your own lines here... # # day planer deamon # pland & export QTDIR=/usr/lib/qt3 export KDEDIR=/opt/kde3 echo $WINDOWMANAGER # # finally start the window manager # exec $WINDOWMANAGER # call failsafe exit 0 So why does it not work....? Tom - -- Hofstadter's Law: It always takes longer than you expect, even when you take Hofstadter's Law into account. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8oNThAEYnIVU7X9IRAjiAAJkB2+QlQlCcLm6UcYImClxFgPiO2ACdF+RD puFHJ1nFN71mMqBv6+DZBfQ= =BFX2 -----END PGP SIGNATURE-----
![](https://seccdn.libravatar.org/avatar/98b4308dea1244ecdc466d868352a98f.jpg?s=120&d=mm&r=g)
Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 26 March 2002 7:56 pm, Jesse Marlin wrote:
Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 26 March 2002 7:23 pm, Henne Vogelsang wrote:
Hi,
On Tuesday, March 26, 2002 at 19:08:58, Tom Wesley wrote:
startkde in /opt/kde3 sets the above to kde3 and qt3 directories, but by the time i'm in kde they are back at the kde2 settings... What can change them between the two?
There are several ways. One is to use your shell environment to set them. ~/.bashrc if you use bash.
Henne
nice idea. was more interested in where it is that they are set back to qt2 etc. Is there anything else that gets executed? Could try forcing them in .bashrc
When I tried the kde3 stuff I stuck them in ~/.xinitrc or ~/.xsession if you use kdm or xdm. This way they will only be set in X's environment. It makes going between kde2 and kde3 very easy.
I'm sorta pleased that this isn't just me then...
a section of my .xinitrc: test -r $HOME/.xim && source $HOME/.xim
# # Add your own lines here... #
# day planer deamon # pland &
export QTDIR=/usr/lib/qt3 export KDEDIR=/opt/kde3
Whoops heres the prob: export LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib export PATH=$KDEDIR/bin:$PATH export WINDOWMANAGER=/opt/kde3/bin/startkde
echo $WINDOWMANAGER # # finally start the window manager # exec $WINDOWMANAGER
# call failsafe exit 0
So why does it not work....?
![](https://seccdn.libravatar.org/avatar/4e8838f16e52ca85d1a8a2605013fe62.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've a feeling I'm going in circles here. Maybe time for sleep... But anyway, that doesn't work at all. I am using KDM though from kde2, but surely that won't affect anything. The settings from SOMEWHERE, and god knows I've tried everywhere should work. Is there something that can explain the order things get executed in SuSE from starting the xdm service to actually getting to the desktop. Or somewhere where I can read about it at least. Tom On Tuesday 26 March 2002 9:39 pm, Jesse Marlin wrote:
Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 26 March 2002 7:56 pm, Jesse Marlin wrote:
Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 26 March 2002 7:23 pm, Henne Vogelsang wrote:
Hi,
On Tuesday, March 26, 2002 at 19:08:58, Tom Wesley wrote:
startkde in /opt/kde3 sets the above to kde3 and qt3 directories, but by the time i'm in kde they are back at the kde2 settings... What can change them between the two?
There are several ways. One is to use your shell environment to set them. ~/.bashrc if you use bash.
Henne
nice idea. was more interested in where it is that they are set back to qt2 etc. Is there anything else that gets executed? Could try forcing them in .bashrc
When I tried the kde3 stuff I stuck them in ~/.xinitrc or ~/.xsession if you use kdm or xdm. This way they will only be set in X's environment. It makes going between kde2 and kde3 very easy.
I'm sorta pleased that this isn't just me then...
a section of my .xinitrc: test -r $HOME/.xim && source $HOME/.xim
# # Add your own lines here... #
# day planer deamon # pland &
export QTDIR=/usr/lib/qt3 export KDEDIR=/opt/kde3
Whoops heres the prob:
export LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib export PATH=$KDEDIR/bin:$PATH export WINDOWMANAGER=/opt/kde3/bin/startkde
echo $WINDOWMANAGER # # finally start the window manager # exec $WINDOWMANAGER
# call failsafe exit 0
So why does it not work....?
- -- You can get more of what you want with a kind word and a gun than you can with just a kind word. -- Bumper Sticker -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8oO0tAEYnIVU7X9IRAojfAJ0Q9+zGPwInKIHZetq76f5By8R3lACggj4w Hm7VGvO4cohKBQStuEDbUUc= =WPt2 -----END PGP SIGNATURE-----
![](https://seccdn.libravatar.org/avatar/98b4308dea1244ecdc466d868352a98f.jpg?s=120&d=mm&r=g)
Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I've a feeling I'm going in circles here. Maybe time for sleep... But anyway, that doesn't work at all. I am using KDM though from kde2, but surely that won't affect anything. The settings from SOMEWHERE, and god knows I've tried everywhere should work. Is there something that can explain the order things get executed in SuSE from starting the xdm service to actually getting to the desktop. Or somewhere where I can read about it at least.
If you are using kdm or xdm then the startup file is ~/.xsession not ~/.xinitrc. Make those changes in ~/.xsession to see if that works.
Tom
On Tuesday 26 March 2002 9:39 pm, Jesse Marlin wrote:
Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 26 March 2002 7:56 pm, Jesse Marlin wrote:
Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 26 March 2002 7:23 pm, Henne Vogelsang wrote:
Hi,
On Tuesday, March 26, 2002 at 19:08:58, Tom Wesley wrote: > startkde in /opt/kde3 sets the above to kde3 and qt3 > directories, but by the time i'm in kde they are back at the > kde2 settings... What can change them between the two?
There are several ways. One is to use your shell environment to set them. ~/.bashrc if you use bash.
Henne
nice idea. was more interested in where it is that they are set back to qt2 etc. Is there anything else that gets executed? Could try forcing them in .bashrc
When I tried the kde3 stuff I stuck them in ~/.xinitrc or ~/.xsession if you use kdm or xdm. This way they will only be set in X's environment. It makes going between kde2 and kde3 very easy.
I'm sorta pleased that this isn't just me then...
a section of my .xinitrc: test -r $HOME/.xim && source $HOME/.xim
# # Add your own lines here... #
# day planer deamon # pland &
export QTDIR=/usr/lib/qt3 export KDEDIR=/opt/kde3
Whoops heres the prob:
export LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib export PATH=$KDEDIR/bin:$PATH export WINDOWMANAGER=/opt/kde3/bin/startkde
echo $WINDOWMANAGER # # finally start the window manager # exec $WINDOWMANAGER
# call failsafe exit 0
So why does it not work....?
- -- You can get more of what you want with a kind word and a gun than you can with just a kind word. -- Bumper Sticker -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iD8DBQE8oO0tAEYnIVU7X9IRAojfAJ0Q9+zGPwInKIHZetq76f5By8R3lACggj4w Hm7VGvO4cohKBQStuEDbUUc= =WPt2
![](https://seccdn.libravatar.org/avatar/00045724aabc71a7ac8e3f237cfead7b.jpg?s=120&d=mm&r=g)
This may not be helpful because our needs are different, but I have export QTDIR='/usr/lib/qt-2.3.0' export KDEDIR='/opt/kde2' and these I set in /etc/profile.local Works for me, but I'm just learning just Qt2 programming exercises.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I've a feeling I'm going in circles here. Maybe time for sleep... > But anyway, that doesn't work at all. I am using KDM though from kde2, but > surely that won't affect anything. The settings from SOMEWHERE, and god knows > I've tried everywhere should work. > Is
Tom Wesley writes: there something that can explain the order things get executed in SuSE from > starting the xdm service to actually getting to the desktop. Or somewhere > where I can read about it at least.
If you are using kdm or xdm then the startup file is ~/.xsession not ~/.xinitrc. Make those changes in ~/.xsession to see if that works.
Tom
On Tuesday 26 March 2002 9:39 pm, Jesse Marlin wrote:
Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 26 March 2002 7:56 pm, Jesse Marlin wrote:
Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday 26 March 2002 7:23 pm, Henne Vogelsang wrote: > Hi, > > > > > > > > > > > > On Tuesday, March 26,
There are several ways. One is to use your shell environment to > > > > > > set them. ~/.bashrc if you use bash. > > > > > > >
Henne > > > > > > > > > > nice idea. was more interested in where it is that they are set > > > > > back to qt2 etc. Is there anything else that gets executed? > > > > > Could try forcing them in .bashrc > > > > > > > > When I tried the kde3 stuff I stuck them in ~/.xinitrc or ~/.xsession > > > > if you use kdm or xdm. This way they will only be set in X's > > > > environment. It makes going between kde2 and kde3 very easy. > > > > > > I'm sorta
2002 at 19:08:58, Tom Wesley wrote: > > > > > > > startkde in /opt/kde3 sets the above to kde3 and qt3 > > > > > > > directories, but by the time i'm in kde they are back at the > > > > > > > kde2 settings... What can change them between the two? > > > > > > > > pleased that this isn't just me then... > > > > > > a section of my .xinitrc: > > > test -r $HOME/.xim && source $HOME/.xim > > > > >
# > > > # Add your own lines here... > > > # > > > > > > > > > # day planer deamon > > > # pland & > > > > > > export QTDIR=/usr/lib/qt3 > > > export KDEDIR=/opt/kde3 > > > > Whoops heres the prob: > > > > export LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib
export PATH=$KDEDIR/bin:$PATH > > export WINDOWMANAGER=/opt/kde3/bin/startkde > > > > > echo $WINDOWMANAGER > # > > > # finally start the window manager > > > # > > > exec $WINDOWMANAGER > > > > > > > > > # call failsafe > > > exit 0 > >
> > > > > So why does it not work....? > > - -- > You can get more of what you want with a kind word and a gun than you > can with just a kind word. > -- Bumper Sticker > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE8oO0tAEYnIVU7X9IRAojfAJ0Q9+zGPwInKIHZetq76f5By8R3lACggj4w > Hm7VGvO4cohKBQStuEDbUUc= > =WPt2
-- 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 archives at http://lists.suse.com
![](https://seccdn.libravatar.org/avatar/98b4308dea1244ecdc466d868352a98f.jpg?s=120&d=mm&r=g)
Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I've a feeling I'm going in circles here. Maybe time for sleep... But anyway, that doesn't work at all. I am using KDM though from kde2, but surely that won't affect anything. The settings from SOMEWHERE, and god knows I've tried everywhere should work. Is there something that can explain the order things get executed in SuSE from starting the xdm service to actually getting to the desktop. Or somewhere where I can read about it at least.
man X search for xsession. Here is a blurp: xdm (the X Display Manager) If you want to always have X running on your dis play, your site administrator can set your machine up to use the X Display Manager xdm. This program is typically started by the system at boot time and takes care of keeping the server running and getting users logged in. If you are running xdm, you will see a window on the screen welcoming you to the system and asking for your username and password. Simply type them in as you would at a normal terminal, pressing the Return key after each. If you make a mistake, xdm will display an error message and ask you to try again. After you have successfully logged in, xdm will start up your X environment. By default, if you have an executable file named .xsession in your home directory, xdm will treat it as a program (or shell script) to run to start up your initial clients (such as terminal emulators, clocks, a window manager, user settings for things like the background, the speed of the pointer, etc.). Your site administrator can provide details. <snip> Here is exactly what I have in mine: ~/.xsession # Suse stuff here ... # Towards the bottom ##################### # Start up kde3 beta export LD_LIBRARY_PATH=/usr/lib/qt3/lib:/opt/kde3/lib:$LD_LIBRARY_PATH export PATH=/opt/kde3/bin:$PATH WINDOWMANAGER=/opt/kde3/bin/startkde exec $WINDOWMANAGER
![](https://seccdn.libravatar.org/avatar/a7eb1ec9ad33cd3ffb68cd5dabcf4449.jpg?s=120&d=mm&r=g)
Know what you mean. I encountered the same and have not found the cause. A good startpoint can be the driectory /usr/X11R6/lib/X11/xdm, the file Xsession. Or read the source of the startx startup script. Op dinsdag 26 maart 2002 20:08, schreef je:
startkde in /opt/kde3 sets the above to kde3 and qt3 directories, but by the time i'm in kde they are back at the kde2 settings... What can change them between the two?
-- Richard Bos For those without home the journey is endless
participants (5)
-
Henne Vogelsang
-
Jesse Marlin
-
Richard Bos
-
Tom Nicholson
-
Tom Wesley