KDE/KDM initialisation problem [SOLVED]

Valheru · 2007-01-20 23:41:23

On my laptop, all of a sudden, kdm refuses to start KDE anymore. It will just launch a single borderless white terminal and that's it. The strange thing is, if I add "startkde" to ~/.xinitrc and run "startx" then kde starts up fine. I've never encountered this before, and am at a loss as to why it is happening. Has anyone ever encountered this before?

Last edited by Valheru (2007-01-31 20:09:31)

stingray · 2007-01-21 02:25:25

One thing to try...

In KDM, after you have selected your user and entered your passowrd, click "Menu/session Type/KDE" to make sure it's starting KDE.

Just a thought.

superstoned · 2007-01-21 13:39:18

weird. if you run 'startkde' in the white terminal, does that work? and you get no error message at all?

Valheru · 2007-01-21 13:57:39

The session type is set to KDE.

One thing I noticed, /var/log/kdm has a few errors in it that are strange :

********************************************************************************
Note that your system uses syslog. All of kdm's internally generated messages
(i.e., not from libraries and external programs/scripts it uses) go to the
daemon.* syslog facility; check your syslog configuration to find out to which
file(s) it is logged. PAM logs messages related to authentication to authpriv.*.
********************************************************************************

X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux penguin 2.6.19-beyond2 #2 PREEMPT Sat Dec 30 23:05:58 CET 2006 i686
Build Date: 11 January 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Jan 21 14:36:10 2007
(==) Using config file: "/etc/X11/xorg.conf"
Fulfilled via DRI at 12587008
Freed 12587008 (pool 2)
(EE) PreInit returned NULL for "Mouse1"
Synaptics DeviceInit called
SynapticsCtrl called.
Synaptics DeviceOn called
Could not init font path element /usr/share/fonts/cyrillic, removing from list!
Could not init font path element /usr/share/fonts/speedo, removing from list!
Could not init font path element /usr/share/fonts/util, removing from list!
QSettings: error creating /tmp/0925345898/.qt
QSettings: failed to open file '/tmp/0925345898/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
QSettings: error creating /tmp/0925345898/.qt
QSettings: failed to open file '/tmp/0925345898/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
Link points to "/var/tmp/kdecache-root"
QSettings: error creating /tmp/0925345898/.qt
QSettings: failed to open file '/tmp/0925345898/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
Synaptics DeviceOff called
Freed 12587008 (pool 1)
(EE) VIA(0): [dri] DRIScreenInit failed. Disabling DRI.
(EE) AIGLX: Screen 0 is not DRI capable
Synaptics DeviceInit called
SynapticsCtrl called.
Synaptics DeviceOn called
Could not init font path element /usr/share/fonts/cyrillic, removing from list!
Could not init font path element /usr/share/fonts/speedo, removing from list!
Could not init font path element /usr/share/fonts/util, removing from list!
QSettings: error creating /tmp/0506252434/.qt
QSettings: failed to open file '/tmp/0506252434/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
QSettings: error creating /tmp/0506252434/.qt
QSettings: failed to open file '/tmp/0506252434/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
QSettings: error creating /tmp/0506252434/.qt
QSettings: failed to open file '/tmp/0506252434/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
Link points to "/var/tmp/kdecache-root"
Synaptics DeviceOff called

superstoned · 2007-01-22 08:35:38

would there be something wrong with /tmp?!?

Valheru · 2007-01-31 20:09:19

In the end it was a corrupt kdmrc file The Shell = line had gotten corrupted somehow, and read Shell = /usr/sh?), which fscked thing up royally, obviously

Arch Linux

#1 2007-01-20 23:41:23

KDE/KDM initialisation problem [SOLVED]

#2 2007-01-21 02:25:25

Re: KDE/KDM initialisation problem [SOLVED]

#3 2007-01-21 13:39:18

Re: KDE/KDM initialisation problem [SOLVED]

#4 2007-01-21 13:57:39

Re: KDE/KDM initialisation problem [SOLVED]

#5 2007-01-22 08:35:38

Re: KDE/KDM initialisation problem [SOLVED]

#6 2007-01-31 20:09:19

Re: KDE/KDM initialisation problem [SOLVED]

Board footer