LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 12-30-2007, 07:40 AM   #1
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Rep: Reputation: 55
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
 
Old 12-30-2007, 12:32 PM   #2
dunric
Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 479

Rep: Reputation: 89
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 ?
 
Old 12-30-2007, 12:56 PM   #3
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Original Poster
Rep: Reputation: 55
.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
 
Old 12-30-2007, 02:37 PM   #4
adriv
Member
 
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.1
Posts: 661

Rep: Reputation: 38
I had this too, read this thread, it worked for me.
 
Old 12-30-2007, 04:03 PM   #5
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Original Poster
Rep: Reputation: 55
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
 
Old 12-30-2007, 04:35 PM   #6
adriv
Member
 
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.1
Posts: 661

Rep: Reputation: 38
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.
 
Old 01-02-2008, 07:13 AM   #7
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Original Poster
Rep: Reputation: 55
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?
 
Old 01-02-2008, 05:29 PM   #8
adriv
Member
 
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.1
Posts: 661

Rep: Reputation: 38
Quote:
Originally Posted by arubin View Post
Thanks. That seems to have sorted it.
Good!
Quote:
Originally Posted by arubin View Post
If there is a tendency for /tmp/ to fill with garbage why does slackware not empty it by default?
Dunno...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Login app appears to be crashing on ttyS0 jrog Linux - Software 1 07-20-2006 09:01 AM
KDE crashing Klaus Paiva Linux - Software 3 10-27-2005 07:54 AM
KDE crashing vinceo03 Mandriva 8 10-26-2005 10:46 PM
KDE crashing jasonmcneil0 Linux - Software 3 12-15-2003 06:07 PM
KDE crashing localnihilist Slackware 0 09-28-2003 03:34 PM


All times are GMT -5. The time now is 06:45 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration