KDE login hang at "Initializing peripherals"
Hi all, SuSE 9.1 Pro here. I just did a YOU today and all went well. However after logging out as myself (non-root user) I can no longer log in again under KDE. The login splash screen hangs while at the "Initializing peripherals" stage with the blinking icon, and then after a few moments the splash goes away and all that is left is a blank "welcome" background screen. Interestingly, logging in under KDE as another user, or as root, works fine. So I thought maybe something got munged in my configuration. I deleted all the ~/.kde ~/.mcop* files and directories, as well as all the KDE related stuff under /tmp and /var/tmp. And none of that made any difference. I still get the same login hang. Rebooting the system also doesn't clear things up. I googled the web in search of a solution and tried just about everything, and still no dice. I don't know if the YOU today has anything to do with this, but it did update the kde3-base libraries and some related stuff. Can someone shed some light on this? P.S. The ~/.xsession-errors file contains some stuff, but I am not sure if any of it is telltale. I'll include that below. -Ti ---------- .xsession-errors ---------- <stdin>:1: invalid preprocessing directive #Dtsession xset: bad font path element (#60), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax xset: bad font path element (#60), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax xset: bad font path element (#60), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax xset: bad font path element (#60), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax Creating link /home/ti/.kde/socket-obelisk. Created link from "/home/ti/.kde/socket-obelisk" to "/tmp/ksocket-ti" /usr/bin/X11/iceauth: creating new authority file /home/ti/.ICEauthority Creating link /home/ti/.kde/tmp-obelisk. Created link from "/home/ti/.kde/tmp-obelisk" to "/tmp/kde-ti" ksplash: WARNING: KGenericFactory: instance requested but no instance name passed to the constructor! kbuildsycoca running... Creating link /home/ti/.kde/cache-obelisk. Created link from "/home/ti/.kde/cache-obelisk" to "/var/tmp/kdecache-ti" Reusing existing ksycoca kbuildsycoca: WARNING: Property 'X-KDE-Weight' is defined multiple times (KOfficeFilter) kio (KService*): WARNING: Invalid Service : Applications/KBarcode/kbarcode-label.desktop kio (KService*): WARNING: Invalid Service : /usr/share/applications/cphone.desktop Invalid entry (missing '=') at /tmp/kde-ti/kconf_updatejMKzBa.tmp:1 Invalid entry (missing '=') at /tmp/kde-ti/kconf_updateR0rFra.tmp:1 <stdin>:491: invalid preprocessing directive #Dtsession kbuildsycoca running... Reusing existing ksycoca kbuildsycoca: WARNING: Property 'X-KDE-Weight' is defined multiple times (KOfficeFilter) kio (KService*): WARNING: Invalid Service : Applications/KBarcode/kbarcode-label.desktop kio (KService*): WARNING: Invalid Service : /usr/share/applications/cphone.desktop
Ti Kan wrote:
SuSE 9.1 Pro here.
I just did a YOU today and all went well. However after logging out as myself (non-root user) I can no longer log in again under KDE. The login splash screen hangs while at the "Initializing peripherals" stage with the blinking icon, and then after a few moments the splash goes away and all that is left is a blank "welcome" background screen.
Try deleting the .Xauthority file in your user directory. I was bit by that one as well. Seems something changed and the old file was no longer compatible. It will be recreated when you log in again. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
"Joe Morris (NTM)" writes:
Ti Kan wrote:
SuSE 9.1 Pro here.
I just did a YOU today and all went well. However after logging out as myself (non-root user) I can no longer log in again under KDE. The login splash screen hangs while at the "Initializing peripherals" stage with the blinking icon, and then after a few moments the splash goes away and all that is left is a blank "welcome" background screen.
Try deleting the .Xauthority file in your user directory. I was bit by that one as well. Seems something changed and the old file was no longer compatible. It will be recreated when you log in again.
Thanks for the tip, I did that but it didn't make any difference. I am just about ready to pull my hair out now... it's aggravating not being able to log in. -Ti
* Ti Kan
I am just about ready to pull my hair out now... it's aggravating not being able to log in.
As a temporary measure, open a console as <your-logon-name> and type: startx note: no logon will be required as you are already logged on when starting x. The more regular logon, init 5, is started by system, not a logged on user or root. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Sunday 15 August 2004 14:35, Patrick Shanahan wrote:
* Ti Kan
[08-14-04 23:55]: I am just about ready to pull my hair out now... it's aggravating not being able to log in.
If you're on a lan then try giving each user their own space on the server. e.g. we found that many users sharing the ~.kde directory hung at the same place. Steve.
Patrick Shanahan writes:
* Ti Kan
[08-14-04 23:55]: I am just about ready to pull my hair out now... it's aggravating not being able to log in.
As a temporary measure, open a console as <your-logon-name> and type: startx
note: no logon will be required as you are already logged on when starting x. The more regular logon, init 5, is started by system, not a logged on user or root.
I finally solved the problem... the brute force way. I created a new user account, established that KDE login works, then I moved all files and directories from my original home directory to the new home directory, except those that are already created in the new account, and making sure the ownership of all files are switched to that of the new account. I then deleted my old account and renamed the new account to the old name. Whatever it was, some file was causing KDE to become wedged. By doing the above I was able to get a fresh start as far as KDE is concerned, and it seems to fix the problem. -Ti
participants (4)
-
Joe Morris (NTM)
-
Patrick Shanahan
-
steve-ss
-
ti@amb.org