vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I had hoped that migrating to udev would have helped(In the forums appearantly this issue is udev related(?) - look at http://forums.gentoo.org/viewtopic-t-348114.html http://forums.gentoo.org/viewtopic-t-347323.html), I now need to work a bit more solving this. I did my daily "emerge sync && emerge -Duva world" on 9th June, and after that kdm is beaving oddly. I get the kdm logon allright, but if I try to log in as user, I just get the logon prompt again. If I log in as root, everything comes up nicely. If I login as user, in the commandpromt, and fire up "startx", KDE starts fine. This problem came up while running devfs, and Gentoo-kernel-2.6.11-r4. Now I use udev and Gentoo-kernel-2.6.11-r9. KDE-3.3.2 on both cases. My /etc/rc.conf is as I left it, and copy pasted in below. /Stig ***********copy paste begin********* # /etc/rc.conf: Global startup script configuration settings # $Header: /var/cvsroot/gentoo-src/rc-scripts/etc/rc.conf,v 1.30.4.1 2005/02/10 01:11:52 vapier Exp $ # UNICODE specifies whether you want to have UNICODE support in the console. # If you set to yes, please make sure to set a UNICODE aware CONSOLEFONT and # KEYMAP in the /etc/conf.d/consolefont and /etc/conf.d/keymaps config files. UNICODE="no" # Set EDITOR to your preferred editor. # You may use something other than what is listed here. EDITOR="/bin/nano" #EDITOR="/usr/bin/vim" #EDITOR="/usr/bin/emacs" # What display manager do you use ? [ xdm | gdm | kdm | entrance ] DISPLAYMANAGER="kdm" # XSESSION is a new variable to control what window manager to start # default with X if run with xdm, startx or xinit. The default behavior # is to look in /etc/X11/Sessions/ and run the script in matching the # value that XSESSION is set to. The support scripts are smart enough to # look in all bin directories if it cant find a match in /etc/X11/Sessions/, # so setting it to "enlightenment" can also work. This is basically used # as a way for the system admin to configure a default system wide WM, # allthough it will work if the user export XSESSION in his .bash_profile, etc. # # NOTE: 1) this behaviour is overridden when a ~/.xinitrc exists, and startx # is called. # 2) even if ~/.xsession exists, if XSESSION can be resolved, it will # be executed rather than ~/.xsession, else KDM breaks ... # # Defaults depending on what you install currently include: # # Gnome - will start gnome-session # kde-<version> - will start startkde (ex: kde-3.0.2) # Xsession - will start a terminal and a few other nice apps XSESSION="kde-3.3.2" |
| |||
| Stig Mogensen wrote: > I did my daily "emerge sync && emerge -Duva world" on 9th June, and after > that kdm is beaving oddly. > > I get the kdm logon allright, but if I try to log in as user, I just get the > logon prompt again. If I log in as root, everything comes up nicely. > If I login as user, in the commandpromt, and fire up "startx", KDE starts > fine. Which packages did you update between when it was working OK and when it was broken? Use "genlop -l" to see the history. |
| |||
| Stig Mogensen wrote: > I did my daily "emerge sync && emerge -Duva world" on 9th June, and > after that kdm is beaving oddly. Right around that time a couple of really important packages were upgraded. Messing up on or more configuration file updates could have caused you some odd trouble. It would, however, be strange if it affected kdm. > I get the kdm logon allright, but if I try to log in as user, I just > get the logon prompt again. If I log in as root, everything comes up > nicely. If I login as user, in the commandpromt, and fire up > "startx", KDE starts fine. Sort of reminds me of what happened a time when my ~/.dmrc file got corrupted. Just deleting it did the trick for me. Not sure this is the same issue, though. -- PeKaJe And yes, IMO it does look like a cross between chicken scratchings, C++ barf, and a very bad day at the data dump. -- High opinions of X.CPP |
| |||
| Paul Bredbury wrote: > Stig Mogensen wrote: >> I did my daily "emerge sync && emerge -Duva world" on 9th June, and after >> that kdm is beaving oddly. >> >> I get the kdm logon allright, but if I try to log in as user, I just get >> the logon prompt again. If I log in as root, everything comes up nicely. >> If I login as user, in the commandpromt, and fire up "startx", KDE starts >> fine. > > Which packages did you update between when it was working OK and when it > was broken? Use "genlop -l" to see the history. I was not aware of genlop untill now.....nice...thanks Following got updated; Thu Jun 9 19:32:57 2005 >>> app-shells/bash-3.0-r11 Thu Jun 9 19:34:50 2005 >>> sys-libs/readline-5.0-r2 Thu Jun 9 19:37:15 2005 >>> media-libs/libmng-1.0.8-r1 Thu Jun 9 19:37:42 2005 >>> sys-apps/sysvinit-2.86 Thu Jun 9 19:38:30 2005 >>> sys-apps/baselayout-1.11.12 and baselayout sticks out(?). Also etc-update was necessary at the time of update, and some 15 configfiles were altered. I keep an eye on the configfiles that I have changed manually over the time(fstab, rc.conf etc etc), so I don't overwrite anything essential for my system to run properly, so the only ones that have changed are the system written/default ones. /Stig |
| |||
| Stig Mogensen wrote: > Following got updated; > Thu Jun 9 19:32:57 2005 >>> app-shells/bash-3.0-r11 > Thu Jun 9 19:34:50 2005 >>> sys-libs/readline-5.0-r2 > Thu Jun 9 19:37:15 2005 >>> media-libs/libmng-1.0.8-r1 > Thu Jun 9 19:37:42 2005 >>> sys-apps/sysvinit-2.86 > Thu Jun 9 19:38:30 2005 >>> sys-apps/baselayout-1.11.12 Looking at http://packages.gentoo.org/search/?sstring=baselayout , the latest stable baselayout is 1.11.12-r4 on all architectures. Upgrade to that version. You could try creating a temporary test user, and seeing if you can log into KDE as that test user. That would tell you whether it's a problem with your system, or with your normal user's config. useradd -m -G users,audio,video testkde passwd testkde When finished testing with the user: userdel -r testkde |
| |||
| Paul Bredbury wrote: > Stig Mogensen wrote: >> Following got updated; >> Thu Jun 9 19:32:57 2005 >>> app-shells/bash-3.0-r11 >> Thu Jun 9 19:34:50 2005 >>> sys-libs/readline-5.0-r2 >> Thu Jun 9 19:37:15 2005 >>> media-libs/libmng-1.0.8-r1 >> Thu Jun 9 19:37:42 2005 >>> sys-apps/sysvinit-2.86 >> Thu Jun 9 19:38:30 2005 >>> sys-apps/baselayout-1.11.12 > > Looking at http://packages.gentoo.org/search/?sstring=baselayout , the > latest stable baselayout is 1.11.12-r4 on all architectures. Upgrade to > that version. Have done already. > You could try creating a temporary test user, and seeing if you can log > into KDE as that test user. That would tell you whether it's a problem > with your system, or with your normal user's config. Good idea. User "testkde" logs on just fine.....so I can get around this nonstarting KDE issue, by deleting/resetting something in my ~./ ??. /Stig |
| |||
| Stig Mogensen wrote: > Good idea. User "testkde" logs on just fine.....so I can get around this > nonstarting KDE issue, by deleting/resetting something in my ~./ ??. Probably - I don't use KDE, so can't help you much. Is there any useful info in e.g.: /var/log/kdm/ ~/.xsession-errors ~/.xinitrc |
| |||
| > /var/log/kdm/ Gives me; *************************** /bin/sh: kworldclock: command not found QImage::convertDepth: Image is a null image QImage::smoothScale: Image is a null image krootimage: Fatal IO error: client killed Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. Please consult the The X.Org Foundation support at http://wiki.X.Org for help. *********************** But I have no clue as to what it means......the search continues > ~/.xsession-errors It says; Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server xterm Xt error: Can't open display: :0 > ~/.xinitrc I have no such file?. /Stig |
| |||
| Stig Mogensen wrote: >>~/.xsession-errors > > It says; > Xlib: connection to ":0.0" refused by server > Xlib: Protocol not supported by server > > xterm Xt error: Can't open display: :0 See http://groups-beta.google.com/group/...d1e7f354445e69 Try renaming your ~/.Xauthority file. |
| ||||
| Paul Bredbury wrote: > Stig Mogensen wrote: >>>~/.xsession-errors >> >> It says; >> Xlib: connection to ":0.0" refused by server >> Xlib: Protocol not supported by server >> >> xterm Xt error: Can't open display: :0 > > See > http://groups-beta.google.com/group/...d1e7f354445e69 > > Try renaming your ~/.Xauthority file. I did, and a new one got created when KDE shuts down. The on boot, I enter some strange looking console(all green screen, with a white window bottom left), where I'm already logged in(!). I then start X by using "startx -- :1" as "startx" gives the same xterm Xt error. /Stig |