LinuxQuestions.org - Crashing out of kde login

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Crashing out of kde login (https://www.linuxquestions.org/questions/slackware-14/crashing-out-of-kde-login-609940/)

Crashing out of kde login

Using runlevel 4

When I log in from the kdm login screen the start process reaches 'peripherals' then crashes back to the login screen. When I log in again all is Ok. This thing cannot be reproduced consistently but usually happens on my first login after turning on the PC.

I do not think that this is a kde crash because the nvidia splash does not appear. I cannot find anything in xorg.log and I do not know where else to look to try and investigate this

Alan

I would also look for records in .xsession-errors file to be found in your home directory.

I've read about some issues with proprietary graphics drivers. Can be reproduced this behaviour with original Xorg driver, ie. not with Nvidia's ?

.xsessions-errors below.

I doubt that it is the video driver. This installation has been going for the best part of a year without a problem.

Quote:

xset: bad font path element (#309), 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 (#309), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
startkde: Starting up...
kbuildsycoca running...
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x81a0df8 ): KAccel object already contains an action name "play_pause"
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x81a0df8 ): KAccel object already contains an action name "play_pause"
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
STARTUP
QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )
kio (KIOConnection): ERROR: Could not write data
Launched ok, pid = 6411
kio (KIOConnection): ERROR: Could not write data
kio (KIOConnection): ERROR: Could not write data
kio (KIOConnection): ERROR: Could not write data
kio (KIOConnection): ERROR: Could not write data
kio (KIOConnection): ERROR: Could not write data
kio (KIOConnection): ERROR: Could not write data
kio (KIOConnection): ERROR: Could not write data
kio (KIOConnection): ERROR: Could not write data

I had this too, read this thread, it worked for me. :)

So I need to delete /tmp/.ICE-unix every time I close down the machine?

Or should I delete everything in /tmp ? It currently holds over 1GB

I did it once and that was enough. :)

If /tmp/ is more than one GB I'd certainly clean it up a bit...
You can automate that by creating /etc/rc.d/rc.local_shutdown (and make it executable) and put this line in it:

Code:

find /tmp -mtime +10 -exec rm -f {} \;

That should do the trick.

Thanks. That seems to have sorted it.

If there is a tendency for /tmp/ to fill with garbage why does slackware not empty it by default?

Quote:

Originally Posted by arubin (Post 3008407)

Thanks. That seems to have sorted it.

Good!

Quote:

Originally Posted by arubin (Post 3008407)

If there is a tendency for /tmp/ to fill with garbage why does slackware not empty it by default?

Dunno...