Re: Fail to start KDE and Gnome
Hi Armin,
Tks for your advice.
--- Armin Pirkovitsch [EMAIL PROTECTED] wrote:
Stephen Liu wrote:
Hi Jonathan Chen,
Tks for your advice.
If you're going to use startx you will need a ${HOME}/.xinitrc
with
the following contents:
#/bin/sh
startkde
Make sure the file is 755 permissions. This will start up X with
KDE.
I would suggest you configure /etc/ttys to start up KDM instead of
using startx
Your advice worked here starting KDE.
What I'm trying to do is running;
$ startkde
will start K desktop
$ gnome-session
will start Gnome desktop
This won't work since those are just the windowmanagers - you need an
X
server to start them.
However you could solve it with some small scripts:
start-gnome.sh:
#!/bin/sh
rm -f ~/.xinitrc
ln -s ~/.xinitrc_gnome ~/.xinitrc
startx
.xinitrc_gnome:
#!/bin/sh
exec /usr/local/bin/gnome-session
start-kde.sh:
#!/bin/sh
rm -f ~/.xinitrc
ln -s ~/.xinitrc_kde ~/.xinitrc
startx
.xinitrc_gnome:
#!/bin/sh
exec /usr/local/bin/startkde
make sure all of these files are executable (chmod 755 file)
the .xinitrc* files have to be in your home directory -
start-gnome.sh
and start-kde.sh in any directory in your PATH (eg. ~/bin if it's
only
for one user)
Something strange happened here. If copying xorg.conf.new on
/etc/X11/ and renaming it as xorg.conf. I can't start X, the HD only
turning. Now I don't have /etc/X11/xorg.conf. I can start KDE (not
Gnome). I don't know which xorg.conf I am now running.
I can toggle resolution to increase font size on browser witn
[Ctrl]+[Alt]+[+]
B.R.
satimis
Send instant messages to your online friends http://uk.messenger.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE and Gnome
Stephen Liu wrote: [...] Something strange happened here. If copying xorg.conf.new on /etc/X11/ and renaming it as xorg.conf. I can't start X, the HD only turning. Now I don't have /etc/X11/xorg.conf. I can start KDE (not Gnome). I don't know which xorg.conf I am now running. just have a look at /var/log/Xorg.0.log - it will tell you which config file is used I can toggle resolution to increase font size on browser witn [Ctrl]+[Alt]+[+] -- Armin Pirkovitsch [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE and Gnome
--- Armin Pirkovitsch [EMAIL PROTECTED] wrote: Stephen Liu wrote: [...] Something strange happened here. If copying xorg.conf.new on /etc/X11/ and renaming it as xorg.conf. I can't start X, the HD only turning. Now I don't have /etc/X11/xorg.conf. I can start KDE (not Gnome). I don't know which xorg.conf I am now running. just have a look at /var/log/Xorg.0.log - it will tell you which config file is used Hi Armin, # cat /var/log/Xorg.0.log | grep xorg (**) Option XkbRules xorg (**) default keyboard: XkbRules: xorg # cat /var/log/Xorg.0.log | grep conf Markers: (--) probed, (**) from config file, (==) default setting, (EE) Unable to locate/open config file Running /usr/X11R6/bin/getconfig -X 6090 -I /etc/X11,/usr/X11R6/etc/X11,/usr/X11R6/lib/modules,/usr/X 11R6/lib/X11/getconfig -v 0x10de -d 0x01df -r 0xa1 -s 0x1043 -b 0x81f3 -c 0x0300 (==) Using default built-in configuration (53 lines) (==) --- Start of built-in configuration --- (==) --- End of built-in configuration --- Using the default mouse configuration. Using the default keyboard configuration. Would it be getconfig? Why I'm not allowed to copy /root/xorg.conf.ne /etc/X11/xorg and run xorg.conf there? Unfortunataely xorg.0.log is a big file. I have no idea where to look at the error message on running xorg.conf. Any suggestion? TIA B.R. satimis Send instant messages to your online friends http://uk.messenger.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE and Gnome - further test
--- Stephen Liu [EMAIL PROTECTED] wrote: --- Armin Pirkovitsch [EMAIL PROTECTED] wrote: Stephen Liu wrote: [...] Something strange happened here. If copying xorg.conf.new on /etc/X11/ and renaming it as xorg.conf. I can't start X, the HD only turning. Now I don't have /etc/X11/xorg.conf. I can start KDE (not Gnome). I don't know which xorg.conf I am now running. just have a look at /var/log/Xorg.0.log - it will tell you which config file is used Hi Armin, # cat /var/log/Xorg.0.log | grep xorg (**) Option XkbRules xorg (**) default keyboard: XkbRules: xorg # cat /var/log/Xorg.0.log | grep conf Markers: (--) probed, (**) from config file, (==) default setting, (EE) Unable to locate/open config file Running /usr/X11R6/bin/getconfig -X 6090 -I /etc/X11,/usr/X11R6/etc/X11,/usr/X11R6/lib/modules,/usr/X 11R6/lib/X11/getconfig -v 0x10de -d 0x01df -r 0xa1 -s 0x1043 -b 0x81f3 -c 0x0300 (==) Using default built-in configuration (53 lines) (==) --- Start of built-in configuration --- (==) --- End of built-in configuration --- Using the default mouse configuration. Using the default keyboard configuration. Would it be getconfig? Why I'm not allowed to copy /root/xorg.conf.ne /etc/X11/xorg and run xorg.conf there? Unfortunataely xorg.0.log is a big file. I have no idea where to look at the error message on running xorg.conf. Any suggestion? TIA B.R. satimis Hi Armin and folks, I made further test as follow; # cp /root/xorg.conf.new /etc/X11/xorg.conf Hard reboot X = [Ctrl]+[Alt]+[Back Space] exited to runlevel 3 Login : satimis Password: xxx $ startx KDE started with color looking strangely and finally PC hung. Hard reboot and removed xorg.conf # cat /var/log/Xorg.0.log . FreeFontPath:FPE /usr/XR11R6/lib/X11/Fonts/misc/ refcount is 2. should be 1: fixing * end * Any advice how to fix this problem. TIA B.R. Stephen Liu Send instant messages to your online friends http://uk.messenger.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE and Gnome
Hi Armin, Tks for your advice. There are two files that control which windowsmanager shall be used (depending on whether you use a login manager or just startx) One is called .xinitrc the other one .xsession - they are both in your home directory - create them (you can create one of them and symlink the other one) and add the start command to the file (full path) - and make sure they are set executable (chmod 755 filename) eg. for kde: exec /usr/local/bin/startkde eg for gnome: exec /usr/local/bin/gnome-session Done as per your advice. $ cat ~/.xsession exec /usr/local/bin/startkde exec /usr/local/bin/gnome-session $ ls -al ~/.xsession -rwxr-xr-x 1 satimis wheel 62 Feb 27 07:59 /home/satimis/.xsession $ startkde ksplash: cannot connect to X server kdeinit: Aborting, $DISPLAY is not set Warning: Connect() failed: No such file or directory ksmserver: Cannot connect to Xserver ! startkde: shutting down ... Warning: Connect() failed: No such file or directory Error: Can't contact kdeinit ! startkde running shutdown script startkde : Done Still failed. B.R. satimis Send instant messages to your online friends http://uk.messenger.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE and Gnome
On Tue, Feb 27, 2007 at 01:26:41PM +0800, Stephen Liu wrote:
Hi folks,
FreeBSD-6.2-amd64
This is a test, I insalled aprox 80% of the packages on Disc 2
After installation completed PC rebooted to runlevel 3. Login as user
and run;
$ startkde
warning:
Kpersonalizer : Cannot connect to Xserer
- repeated-
$ gnome-session
(gnome-session 1968) gtk-Warning ** cannot open displayed
$ startx
3 xterm windows started. On xterm I can start KDE with a lot of
warning displayed on xterm windonw. But I can't start Gnome on xterm.
If you're going to use startx you will need a ${HOME}/.xinitrc with
the following contents:
#/bin/sh
startkde
Make sure the file is 755 permissions. This will start up X with KDE.
I would suggest you configure /etc/ttys to start up KDM instead of
using startx
Cheers.
--
Jonathan Chen [EMAIL PROTECTED]
--
Nyuck, nyuck, nyuck - Curly
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE and Gnome
On Tue, Feb 27, 2007 at 04:23:37PM +0800, Stephen Liu wrote: Hi Armin, Tks for your advice. There are two files that control which windowsmanager shall be used (depending on whether you use a login manager or just startx) One is called .xinitrc the other one .xsession - they are both in your home directory - create them (you can create one of them and symlink the other one) and add the start command to the file (full path) - and make sure they are set executable (chmod 755 filename) eg. for kde: exec /usr/local/bin/startkde eg for gnome: exec /usr/local/bin/gnome-session Done as per your advice. $ cat ~/.xsession exec /usr/local/bin/startkde exec /usr/local/bin/gnome-session You didn't follow his instructions. You only need *ONE* of the lines in there - either startkde or gnome-session. $ ls -al ~/.xsession -rwxr-xr-x 1 satimis wheel 62 Feb 27 07:59 /home/satimis/.xsession $ startkde You will need to use startx instead. -- Jonathan Chen [EMAIL PROTECTED] -- Do not take life too seriously. You will never get out of it alive. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE and Gnome
Hi Jonathan Chen,
Tks for your advice.
If you're going to use startx you will need a ${HOME}/.xinitrc with
the following contents:
#/bin/sh
startkde
Make sure the file is 755 permissions. This will start up X with KDE.
I would suggest you configure /etc/ttys to start up KDM instead of
using startx
Your advice worked here starting KDE.
What I'm trying to do is running;
$ startkde
will start K desktop
$ gnome-session
will start Gnome desktop
Tks.
B.R.
Stephen Liu
Send instant messages to your online friends http://uk.messenger.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE and Gnome
Hi Jonathan, I would suggest you configure /etc/ttys to start up KDM instead of using startx I'm prepared running this box building servers for test. I don't expect the box booting straight to login page. X is only for communicating outside World. I'm not used to running elinks, the text broswer. Tks. B.R. satimis Send instant messages to your online friends http://uk.messenger.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE and Gnome
Stephen Liu wrote:
Hi Jonathan Chen,
Tks for your advice.
If you're going to use startx you will need a ${HOME}/.xinitrc with
the following contents:
#/bin/sh
startkde
Make sure the file is 755 permissions. This will start up X with KDE.
I would suggest you configure /etc/ttys to start up KDM instead of
using startx
Your advice worked here starting KDE.
What I'm trying to do is running;
$ startkde
will start K desktop
$ gnome-session
will start Gnome desktop
This won't work since those are just the windowmanagers - you need an X
server to start them.
However you could solve it with some small scripts:
start-gnome.sh:
#!/bin/sh
rm -f ~/.xinitrc
ln -s ~/.xinitrc_gnome ~/.xinitrc
startx
.xinitrc_gnome:
#!/bin/sh
exec /usr/local/bin/gnome-session
start-kde.sh:
#!/bin/sh
rm -f ~/.xinitrc
ln -s ~/.xinitrc_kde ~/.xinitrc
startx
.xinitrc_gnome:
#!/bin/sh
exec /usr/local/bin/startkde
make sure all of these files are executable (chmod 755 file)
the .xinitrc* files have to be in your home directory - start-gnome.sh
and start-kde.sh in any directory in your PATH (eg. ~/bin if it's only
for one user)
--
Armin Pirkovitsch
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE and Gnome
Stephen Liu wrote: Hi folks, FreeBSD-6.2-amd64 This is a test, I insalled aprox 80% of the packages on Disc 2 After installation completed PC rebooted to runlevel 3. Login as user and run; $ startkde warning: Kpersonalizer : Cannot connect to Xserer - repeated- $ gnome-session (gnome-session 1968) gtk-Warning ** cannot open displayed $ startx 3 xterm windows started. On xterm I can start KDE with a lot of warning displayed on xterm windonw. But I can't start Gnome on xterm. I can start firefox on xterm. Now I'm posting on firefox browser. Please advise where I have to check fixing the problems. TIA There are two files that control which windowsmanager shall be used (depending on whether you use a login manager or just startx) One is called .xinitrc the other one .xsession - they are both in your home directory - create them (you can create one of them and symlink the other one) and add the start command to the file (full path) - and make sure they are set executable (chmod 755 filename) eg. for kde: exec /usr/local/bin/startkde eg for gnome: exec /usr/local/bin/gnome-session -- Armin Pirkovitsch [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fail to start KDE and Gnome
Hi folks, FreeBSD-6.2-amd64 This is a test, I insalled aprox 80% of the packages on Disc 2 After installation completed PC rebooted to runlevel 3. Login as user and run; $ startkde warning: Kpersonalizer : Cannot connect to Xserer - repeated- $ gnome-session (gnome-session 1968) gtk-Warning ** cannot open displayed $ startx 3 xterm windows started. On xterm I can start KDE with a lot of warning displayed on xterm windonw. But I can't start Gnome on xterm. I can start firefox on xterm. Now I'm posting on firefox browser. Please advise where I have to check fixing the problems. TIA B.R. Stephen Liu Send instant messages to your online friends http://uk.messenger.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE
- snip - 2) After starting 3 'Xterm windows' I can start KDE 3.1 from any one of the 'Xterm window' with; # startkde It worked with KDE started. 3) On INIT 3/text mode I can login either as 'root' or as 'user' with correct password without problem I haven't used xdm in ttys for a long time, and suspect this is an obsolete method. If you enter kdm at a root prompt, kdm should start. Hi Mike, Tks for your advice which works. What is '' for I don't see why you shouldn't put it into /usr/local/etc/rc.d to make it work on startup, and I am pretty sure I used to run it that way. /usr/local/etc/rc.d is a directory. Whether you recommend to create a file with only a single line :- 'Kdm ' (without quote) on it and save it to /usr/local/etc/rc.d/ Shall I 'chmod 775' the file created? Files in /usr/local/etc/rc.d/ directory have an extension '.h'. Shall I name the file as xxx.h? TIA B.R. Stephen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE
On Tue, 24 Feb 2004 21:51:14 +0800 Stephen Liu [EMAIL PROTECTED] wrote: - snip - 2) After starting 3 'Xterm windows' I can start KDE 3.1 from any one of the 'Xterm window' with; # startkde It worked with KDE started. 3) On INIT 3/text mode I can login either as 'root' or as 'user' with correct password without problem I haven't used xdm in ttys for a long time, and suspect this is an obsolete method. If you enter kdm at a root prompt, kdm should start. Hi Mike, Tks for your advice which works. What is '' for I don't see why you shouldn't put it into /usr/local/etc/rc.d to make it work on startup, and I am pretty sure I used to run it that way. /usr/local/etc/rc.d is a directory. Whether you recommend to create a file with only a single line :- 'Kdm ' (without quote) on it and save it to /usr/local/etc/rc.d/ Shall I 'chmod 775' the file created? Files in /usr/local/etc/rc.d/ directory have an extension '.h'. Shall I name the file as xxx.h? TIA B.R. Stephen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] The makes it run the command as a background job, so that the prompt re-appears immedidately, and you can go on working in that shell. In this case, it just means that if you go back to that virtual terminal (with CTRL-Alt-F1 or whatever) you can run more commands outside KDE. I think the rule for scripts in /usr/local/etc/rc.d is that they will all be run on startup, provided they are executable. The convention is to name them xxx.sh, but I don't know if that is actually required. So a chmod 500 should be the minimum required permissions (-r-x--), and 755 will work OK. -- Personal : Mike.Jeays -at- rogers.com Phone : 613-724-4510 Work : Mike.Jeays -at- statcan.ca Phone : 613-951-9929 FAX 613-951-0395 Web page : http://members.rogers.com/mike.jeays ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE
- snip - /usr/local/etc/rc.d is a directory. Whether you recommend to create a file with only a single line :- 'Kdm ' (without quote) on it and save it to /usr/local/etc/rc.d/ Shall I 'chmod 775' the file created? Files in /usr/local/etc/rc.d/ directory have an extension '.h'. Shall I name the file as xxx.h? The makes it run the command as a background job, so that the prompt re-appears immedidately, and you can go on working in that shell. In this case, it just means that if you go back to that virtual terminal (with CTRL-Alt-F1 or whatever) you can run more commands outside KDE. I think the rule for scripts in /usr/local/etc/rc.d is that they will all be run on startup, provided they are executable. The convention is to name them xxx.sh, but I don't know if that is actually required. So a chmod 500 should be the minimum required permissions (-r-x--), and 755 will work OK. Hi Mike, Tks for your advice. Have tried following version without success /usr/local/etc/rc.d/kguilogin.sh #! /bin/sh 1) kdm 2) exec kdm 3) kdm 4) xinit kdm 5) xinit /usr/local/bin/kdm -- 6) xinit /usr/local/bin/kdm B.R. Stephen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE
On Mon, 23 Feb 2004 11:48:56 +0800 Stephen Liu [EMAIL PROTECTED] wrote: Mike Jeays wrote: Version 5.2 new installation - snip - Create a file .xinitrc in the home directory, containing the single line 'startkde ' (without the quotes). Then try startx again. Hi Mike, Tks for your advice. Sorry I forgot to mention in my previous posting; 1) KDE could not start if editing /etc/ttys as; . ttyv8 user/local/bin/xdm -nodaemon xterm on secure . ... # startkde (on INIT 3/text mode) ... Kpersonalizer: cannot connect to X server. (continue to run on screen) I suspect whether it was caused by failure on login. Because after booting, the 'Welcom to the XFree86 Project Inc' GUI login popup. I can keyin either as 'root' or as 'username' but can't keyin password. I just typed in password and hit Enter the GUI login screen popup again without mentioning anything. The X window started with a small Xterm window appearing on the screen, mouse working but I could not type on it. I tried many times without a solution. If changing 'xdm' to 'kdm' on the abovementioned line 'ttyv8.', GUI login failed to start. # startx (on INIT 3) started 3 'Xterm windows' 2) After starting 3 'Xterm windows' I can start KDE 3.1 from any one of the 'Xterm window' with; # startkde It worked with KDE started. 3) On INIT 3/text mode I can login either as 'root' or as 'user' with correct password without problem Kindly advise how to fix the problem. TIA B.R. Stephen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I haven't used xdm in ttys for a long time, and suspect this is an obsolete method. If you enter kdm at a root prompt, kdm should start. I don't see why you shouldn't put it into /usr/local/etc/rc.d to make it work on startup, and I am pretty sure I used to run it that way. -- Personal : Mike.Jeays -at- rogers.com Phone : 613-724-4510 Work : Mike.Jeays -at- statcan.ca Phone : 613-951-9929 FAX 613-951-0395 Web page : http://members.rogers.com/mike.jeays ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE
On Sun, 22 Feb 2004 23:46:54 +0800 Stephen Liu [EMAIL PROTECTED] wrote: Hi all folks, Version 5.2 new installation I encountered problem in starting KDE after installation. 1) KDE installed pkg_info | grep kde kde-3.1.4 The meta-port for KDE kdeaddons-3.1.4 Additional plugins and scripts for some KDE applications kdeadmin-3.1.4 KDE applications related to system administration kdeartwork-3.1.4_1 Additional themes, sounds, wallpapers and window styles for kdebase-3.1.4 This package provides the basic applications for the KDE sy kdeedu-3.1.4 Collection of entertaining, educational programs for KDE kdegames-3.1.4 Games for the KDE integrated X11 desktop kdegraphics-3.1.4 Graphics utilities for the KDE3 integrated X11 desktop kdelibs-3.1.4_1 This is the base set of libraries needed by KDE programs kdemultimedia-3.1.4 Multimedia utilities for the KDE integrated X11 desktop kdenetwork-3.1.4 Network-related programs and modules for KDE kdepim-3.1.4 Personal Information Management tools for KDE kdesdk-3.1.4 KDE Software Development Kit kdetoys-3.1.4 Small applications for KDE kdeutils-3.1.4 Utilities for the KDE integrated X11 desktop kdevelop-2.1.5 Powerful IDE for developing KDE/Qt-based apps 2) /home/user/.xinitrc file not found ls -al /home/user/ total 22 drwxr-xr-x 2 satimis wheel 512 Feb 23 05:58 . drwxr-xr-x 3 root wheel 512 Feb 23 07:16 .. -rw--- 1 satimis wheel 0 Feb 23 05:58 .Xauthority -rw-r--r-- 1 satimis wheel 767 Feb 23 07:16 .cshrc -rw-r--r-- 1 satimis wheel 248 Feb 23 07:16 .login -rw-r--r-- 1 satimis wheel 158 Feb 23 07:16 .login_conf -rw--- 1 satimis wheel 373 Feb 23 07:16 .mail_aliases -rw-r--r-- 1 satimis wheel 331 Feb 23 07:16 .mailrc -rw-r--r-- 1 satimis wheel 797 Feb 23 07:16 .profile -rw--- 1 satimis wheel 276 Feb 23 07:16 .rhosts -rw-r--r-- 1 satimis wheel 975 Feb 23 07:16 .shrc -rw--- 1 satimis wheel 106 Feb 23 05:58 .xsession-errors 3) cat /home/user/.xsession-errors Xlib: connection to :0.0 refused by server Xlib: No protocol specified Error: Can't open display: :0 Kindly advise how to fix the problems. TIA B.R. satimis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Create a file .xinitrc in the home directory, containing the single line 'startkde ' (without the quotes). Then try startx again. -- Personal : Mike.Jeays -at- rogers.com Phone : 613-724-4510 Work : Mike.Jeays -at- statcan.ca Phone : 613-951-9929 FAX 613-951-0395 Web page : http://members.rogers.com/mike.jeays ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE
On Sunday 22 February 2004 10:33 am, Mike Jeays wrote: On Sun, 22 Feb 2004 23:46:54 +0800 Create a file .xinitrc in the home directory, containing the single line 'startkde ' (without the quotes). Then try startx again. Kindly explain the difference between between the following in your .xinitrc file. exec startkde startkde -- Best regards, Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE
On Sun, 22 Feb 2004 11:07:52 -0600 Chris [EMAIL PROTECTED] wrote: On Sunday 22 February 2004 10:33 am, Mike Jeays wrote: On Sun, 22 Feb 2004 23:46:54 +0800 Create a file .xinitrc in the home directory, containing the single line 'startkde ' (without the quotes). Then try startx again. Kindly explain the difference between between the following in your .xinitrc file. exec startkde startkde -- Best regards, Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Not much in practice - I think they will both work. Exec just says call this other script/command, and don't return to the calling script. -- Personal : Mike.Jeays -at- rogers.com Phone : 613-724-4510 Work : Mike.Jeays -at- statcan.ca Phone : 613-951-9929 FAX 613-951-0395 Web page : http://members.rogers.com/mike.jeays ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fail to start KDE
On Sun, Feb 22, 2004 at 11:07:52AM -0600, Chris wrote: On Sunday 22 February 2004 10:33 am, Mike Jeays wrote: On Sun, 22 Feb 2004 23:46:54 +0800 Create a file .xinitrc in the home directory, containing the single line 'startkde ' (without the quotes). Then try startx again. Kindly explain the difference between between the following in your .xinitrc file. exec startkde startkde 'exec startkde' replaces the .xinitrc process with the startkde process. 'startkde ' starts up a separate startkde process in the background and then continues executing the .xinitrc process. That may or may not be a good thing -- if the .xinitrc process exits (or the stardkde process that it morphs into in the first instance) then your session will be deemed to have ended and you'll be dumped back at the shell prompt. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: Fail to start KDE
Mike Jeays wrote: Version 5.2 new installation - snip - Create a file .xinitrc in the home directory, containing the single line 'startkde ' (without the quotes). Then try startx again. Hi Mike, Tks for your advice. Sorry I forgot to mention in my previous posting; 1) KDE could not start if editing /etc/ttys as; . ttyv8 user/local/bin/xdm -nodaemon xterm on secure . ... # startkde (on INIT 3/text mode) ... Kpersonalizer: cannot connect to X server. (continue to run on screen) I suspect whether it was caused by failure on login. Because after booting, the 'Welcom to the XFree86 Project Inc' GUI login popup. I can keyin either as 'root' or as 'username' but can't keyin password. I just typed in password and hit Enter the GUI login screen popup again without mentioning anything. The X window started with a small Xterm window appearing on the screen, mouse working but I could not type on it. I tried many times without a solution. If changing 'xdm' to 'kdm' on the abovementioned line 'ttyv8.', GUI login failed to start. # startx (on INIT 3) started 3 'Xterm windows' 2) After starting 3 'Xterm windows' I can start KDE 3.1 from any one of the 'Xterm window' with; # startkde It worked with KDE started. 3) On INIT 3/text mode I can login either as 'root' or as 'user' with correct password without problem Kindly advise how to fix the problem. TIA B.R. Stephen ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
