Re: startx Fatal server error: Cannot open /dev/tty0
From: robbie chen (robbiecn_at_gmail.com)
Date: 11/24/05
- Next message: houghi: "Re: We've got visio!"
- Previous message: houghi: "Re: We've got visio!"
- In reply to: BearItAll: "Re: startx Fatal server error: Cannot open /dev/tty0"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 24 Nov 2005 07:48:20 -0800
Hi BearItAll:
> startx fails under your normal user login but starts normally under your
> root login. So its the local user settings that have gone faulty.
>
> So I bet your socks that if you created a new standard user then his
> startx - kde/gnome would work properly.
>
> It is very likely that deleting the session file will be all thats needed.
> Clear out the kde /tmp files, thats kde-{user or session name} ksocket-*
>
> You would also clear out some from $HOME/.kde but I'm am not sure which
> parts have to be removed to put it back to a default. So all I can do
> there is say to look for how to do this properly on the kde web site. It
> was tempting to tell you to just rename the .kde (so you can get back you
> knode settings and some others, then that users .kde would be setup from
> scratch on the first login.
Thank u for reply, but I don't think it's due to KDE or Gnome or other
Window Manager wrong config. Shell *startx* run in steps:
1. make X server process ready
2. start some X-application
3. finally start Window Manager (that's KDE|Gnome|etc.)
My problem exists in step1. Now, the question become why root user
can init the video device, why not for normal user? Which device file
represent video device. In my system, only one framebuffer device
/dev/fb0.
Oh, god, now ,I have to work as root :(
- Next message: houghi: "Re: We've got visio!"
- Previous message: houghi: "Re: We've got visio!"
- In reply to: BearItAll: "Re: startx Fatal server error: Cannot open /dev/tty0"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|