From: <ra...@ma...> - 2003-03-31 15:30:32
|
El lunes, 31 marz, 2003, a las 14:59 Europe/Madrid, Benjamin Reed=20 escribi=F3: > Ramiro T=E9llez Sanz wrote: > >> #exec quartz-wm > source /sw/bin/init.sh >> export KDEWM=3Dkwin >> exec startkde >/users/ramiro/desktop/kde.log 2>&1 Thanks for your answer, Ben. However, that's not the problem. I source=20= init.sh from X11.app itself, i.e., I applied the hack Martin explained=20= to us long ago in order to have the correct path in X11: --- [localhost:X11.app/contents/macos] ramiro% ls -la total 32 drwxrwxr-x 5 root admin 170 Mar 19 11:01 . drwxrwxr-x 7 root admin 238 Mar 19 10:46 .. -rwxrwxr-x 1 ramiro admin 6148 Mar 19 11:01 .DS_Store -rwxr-xr-x 1 root admin 157 Mar 19 10:59 X11 -rwxrwxr-x 1 root admin 19536 Mar 11 04:17 X11.bin [localhost:X11.app/contents/macos] ramiro% cat X11 #!/bin/sh source /etc/csh.cshrc source /etc/csh.login source /sw/bin/init.sh exec /Applications/X11.app/Contents/MacOS/X11.bin -dpi 97 [localhost:X11.app/contents/macos] ramiro% --- What's more, I have the exact same configuration (.xinitrc and X11's=20 contents) at home, and everything works fine: KDE can start up from=20 .xinitrc loading its own wm. I really have no clue about why. The only thing I know is that KDE=20 shuts down at the end of the peripheral set up, and that's why I told=20 you about my network and the printer I use. Ramiro T=E9llez Sanz ra...@ma...= |