LinuxQuestions.org
Help answer threads with 0 replies.
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 09-25-2005, 11:33 AM   #1
Basel
Member
 
Registered: Feb 2004
Location: United States
Distribution: Ubuntu 10.10
Posts: 319

Rep: Reputation: 30
Slackware crashes when log-off or restart under X


Hi,

Does anyone know why X crashes whenever I try to log-off or restart Slackware 10.2? This happens all the time even after a fresh install. I tried to reinstall Slackware more than once but the problem persists.

Code:
(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
.
.
.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1239627520 (LWP 2806)]
(no debugging symbols found)
.
.
.
(no debugging symbols found)
[KCrash handler]
#3  0xb73f1ad8 in QGList::find () from /usr/lib/qt/lib/libqt-mt.so.3
#4  0xb77bd55e in KGlobal::registerStaticDeleter ()
   from /opt/kde/lib/libkdecore.so.4
#5  0xb7d443dc in KDirWatch::self () from /opt/kde/lib/libkio.so.4
#6  0xb7d953d3 in KDirListerCache::KDirListerCache ()
   from /opt/kde/lib/libkio.so.4
#7  0xb7d99317 in KDirListerCache::self () from /opt/kde/lib/libkio.so.4
#8  0xb7d9df39 in KDirLister::stop () from /opt/kde/lib/libkio.so.4
#9  0xb7d9da60 in KDirLister::~KDirLister () from /opt/kde/lib/libkio.so.4
#10 0xb59f7e33 in SystemMenu::~SystemMenu ()
   from /opt/kde/lib/kde3/kickermenu_systemmenu.so
#11 0xb7aff9ae in QPtrList<QObject>::deleteItem ()
   from /opt/kde/lib/libkdeui.so.4
#12 0xb73f1a3e in QGList::clear () from /usr/lib/qt/lib/libqt-mt.so.3
#13 0xb77c83d3 in KLibrary::~KLibrary () from /opt/kde/lib/libkdecore.so.4
#14 0xb77ca0b6 in KLibLoader::close_pending ()
   from /opt/kde/lib/libkdecore.so.4
#15 0xb77c94ea in KLibLoader::~KLibLoader () from /opt/kde/lib/libkdecore.so.4
#16 0xb77c8f38 in KLibLoader::cleanUp () from /opt/kde/lib/libkdecore.so.4
#17 0xb7715b73 in KApplication::~KApplication ()
   from /opt/kde/lib/libkdecore.so.4
#18 0xb77cdc47 in KUniqueApplication::~KUniqueApplication ()
   from /opt/kde/lib/libkdecore.so.4
#19 0xb601cb59 in Kicker::~Kicker () from /opt/kde/lib/libkdeinit_kicker.so
#20 0xb601a9b3 in kdemain () from /opt/kde/lib/libkdeinit_kicker.so
#21 0xb60957d6 in kdeinitmain () from /opt/kde/lib/kde3/kicker.so
#22 0x0804ce12 in ?? ()
.
.
.
#54 0x00000000 in ?? ()
#55 0xb7578cc0 in vtable for QGArray () from /usr/lib/qt/lib/libqt-mt.so.3
#56 0x00000000 in ?? ()
.
.
.
#67 0x0805b778 in ?? ()
#68 0xb69ed5f4 in _int_malloc () from /lib/tls/libc.so.6
#69 0x0804e33b in ?? ()
.
.
.
#78 0x00000000 in ?? ()
#79 0x080506b7 in _IO_stdin_used ()
#80 0x00000000 in ?? ()
#81 0x00000000 in ?? ()
#82 0x00000000 in ?? ()
#83 0x080506b7 in _IO_stdin_used ()
#84 0x00000000 in ?? ()
.
.
.
#97 0x00000013 in ?? ()
#98 0x08052658 in vtable for QCString ()
#99 0x0805b780 in ?? ()
#100 0x00000000 in ?? ()
#101 0x00000000 in ?? ()
#102 0x08052658 in vtable for QCString ()
#103 0x0805b770 in ?? ()
.
.
.
#120 0xffffffff in ?? ()
#121 0xb6b6148d in operator delete () from /usr/lib/./libstdc++.so.5
 
Old 09-25-2005, 12:06 PM   #2
MS3FGX
LQ Guru
 
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,852

Rep: Reputation: 360Reputation: 360Reputation: 360Reputation: 360
Interesting problem.

If it persists through installs, it must be some problem with your hardware, or perhaps more likely, some problem Linux has with your hardware. The hardware is probably working fine, the system just doesn't like it.

Have you had any other distros installed on this machine? And are you using the stock 2.4 kernel with Slackware? If so, which one, the bare kernel, or one of the special ones.

If you could post your hardware, that may also help.

Also, can you reboot/shutdown the machine from the command line without it crashing, or does it crash no matter how it is shutdown?

My first guess would be it is an APM/ACPI problem. Perhaps there is a bug in your BIOS that needs to be addressed in the kernel.
 
Old 09-25-2005, 12:26 PM   #3
Basel
Member
 
Registered: Feb 2004
Location: United States
Distribution: Ubuntu 10.10
Posts: 319

Original Poster
Rep: Reputation: 30
Quote:
Have you had any other distros installed on this machine? And are you using the stock 2.4 kernel with Slackware? If so, which one, the bare kernel, or one of the special ones.
No I don't have any other Linux distributions installed currently other than Slackware 10.2. I tried sata.i, test26.i and I am currently running kernel-2.6.13 compiled from source.

Quote:
If you could post your hardware, that may also help.
Processor: AMD64 Athlon 3000+ 939 Socket
Mainboard: MSI K8N Neo2
HD: Serial ATA 200GB
RAM: 1GB DDR
AGP: FX5200-TD128 MB DDR 8X

Quote:
Also, can you reboot/shutdown the machine from the command line without it crashing, or does it crash no matter how it is shutdown?
I have no problems at all with shutdown/reboot from the console. Slackware starts at run level 3 and from there I run startx as a normal user.

Quote:
My first guess would be it is an APM/ACPI problem.
I have compile ACPI support into the kernel but not APM.
Code:
basel@slackware-10:~/opt/linux-2.6.13$ grep ACPI .config
# Power management options (ACPI, APM)
# ACPI (Advanced Configuration and Power Interface) Support
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
# CONFIG_ACPI_SLEEP_PROC_SLEEP is not set
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=y
# CONFIG_ACPI_HOTKEY is not set
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_X86_ACPI_CPUFREQ is not set
CONFIG_X86_POWERNOW_K8_ACPI=y
# CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
# CONFIG_SERIAL_8250_ACPI is not set
basel@slackware-10:~/opt/linux-2.6.13$ grep APM .config
# Power management options (ACPI, APM)
# APM (Advanced Power Management) BIOS Support
# CONFIG_APM is not set
Quote:
Perhaps there is a bug in your BIOS that needs to be addressed in the kernel.
I will check my BIOS setting later today.
 
Old 09-25-2005, 02:26 PM   #4
MS3FGX
LQ Guru
 
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,852

Rep: Reputation: 360Reputation: 360Reputation: 360Reputation: 360
In that case (system shuts down in runlevel 3) I would say the problem is more with X and the video hardware.

Are you using the NVIDIA drivers for your card? I have the FX5600 myself, and it doesn't work terribly well unless you use the NVIDIA Linux drivers.

The driver in the kernel "nv" works in a basic sense, but as I understand it, does not fully support all functions of the cards, and as such, can be a bit wonky.
 
Old 09-25-2005, 06:30 PM   #5
dsojat10
LQ Newbie
 
Registered: Nov 2003
Distribution: Fedora 5
Posts: 16

Rep: Reputation: 0
I am upgrading the os on my server right now that has an nVidia FX 5200 agp video card. Everything was going like gang busters until while configuring the box, X would freeze. I was not able to use the keyboard although the usb mouse still worked. I found that I was able to ssh to the box and found that X was using 99% cpu.

I did the following command as root; "kill -HUP `cat /var/run/gdm.pid ` and that restarted X and I could continue working.

This happened a couple more times and I thought my install was bad and went back to v10.1 and found that I was still experiencing the same issue. The only difference was that I was now using the latest Linux driver from nVidia.

I reinstalled v10.2 and I have installed the older, smaller (by 4 megs), and apparently very stable version of 1.0-6111. I haven't had any issue since.

So, moral of the story is to check your video driver. The latest is not always the greatest as I have found here!
 
Old 09-26-2005, 04:09 AM   #6
Basel
Member
 
Registered: Feb 2004
Location: United States
Distribution: Ubuntu 10.10
Posts: 319

Original Poster
Rep: Reputation: 30
Quote:
Are you using the NVIDIA drivers for your card?
Yes, I am using the nvidia driver and not the default nv driver. To be precise, I used NVIDIA-Linux-x86-1.0-7676-pkg1.run to install nVidia support into the kernel.

Quote:
I reinstalled v10.2 and I have installed the older, smaller (by 4 megs), and apparently very stable version of 1.0-6111. I haven't had any issue since.
I have just downloaded an older version of the driver. I will try it and see if the problem would appear again.
 
Old 09-26-2005, 04:51 AM   #7
Ilgar
Senior Member
 
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware64 14.2, Slackwarearm-current
Posts: 1,060

Rep: Reputation: 166Reputation: 166
The crash log you posted indicates that you were using KDE (they're all Qt/KDE functions). Are you sure that it's X that is causing the crash? Perhaps something wrong with KDE? Did you try another window manager?
 
Old 09-26-2005, 04:59 AM   #8
Basel
Member
 
Registered: Feb 2004
Location: United States
Distribution: Ubuntu 10.10
Posts: 319

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by Ilgar
The crash log you posted indicates that you were using KDE (they're all Qt/KDE functions). Are you sure that it's X that is causing the crash? Perhaps something wrong with KDE? Did you try another window manager?
Okay, I will be using Xfce today and see how it goes.
 
Old 09-27-2005, 02:01 PM   #9
Basel
Member
 
Registered: Feb 2004
Location: United States
Distribution: Ubuntu 10.10
Posts: 319

Original Poster
Rep: Reputation: 30
Hi,

KDE still crashes even after using a different release of the nVidia driver. I noticed that the console prints a long list of 'invalid Window parameter' error messages after I log-off . Here is a list of messages from the console after X shuts down. bThis time the KDE didn't crash
Code:
X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.13 i686 [ELF]
Current Operating System: Linux darkstar 2.6.13 #1 Mon Sep 26 17:25:04 AST 2005 i686
Build Date: 11 September 2005
        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: Tue Sep 27 18:11:06 2005
(==) Using config file: "/etc/X11/xorg.conf"
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
xset:  bad font path element (#277), 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...
KWrited - Listening on Device /dev/pts/0
kdecore (KLibLoader): WARNING: KLibrary: /opt/kde/lib/kde3/kcm_kdnssd.so: undefined symbol: init_kdnssd
SetClientVersion: 0 8
kxkb: WARNING: Unable to open /tmp/kde-basel/us.xkm: No such file or directory
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x40004b
Launched ok, pid = 2001
SetClientVersion: 0 8
SetGrabKeysState - disabled
X Error: BadAccess (attempt to access private resource denied) 10
  Major opcode:  2
  Minor opcode:  0
  Resource id:  0x2400005
SetGrabKeysState - enabled
DCOP Cleaning up dead connections.
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  7
  Minor opcode:  0
  Resource id:  0x1c00005
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  6
  Minor opcode:  0
  Resource id:  0x1c00005
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  7
  Minor opcode:  0
  Resource id:  0x200000b
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  6
  Minor opcode:  0
  Resource id:  0x200000b
kio (KDirWatch): WARNING: KDirWatch::removeDir can't handle 'Office/kword.desktop'
startkde: Shutting down...
klauncher: Exiting on signal 1
startkde: Running shutdown scripts...
startkde: Done.

waiting for X server to shut down
BTW, I could not get a chance to try Xfce.
 
Old 09-27-2005, 06:22 PM   #10
Ilgar
Senior Member
 
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware64 14.2, Slackwarearm-current
Posts: 1,060

Rep: Reputation: 166Reputation: 166
The last log seems to be clean. It would be more useful if we had a crash log. Why didn't it crash this time? Perhaps a program which you didn't run this time was causing the crash.

Also, why couldn't you try XFCE or something else? There wasn't a problem with starting X I hope?
 
Old 09-27-2005, 11:36 PM   #11
MS3FGX
LQ Guru
 
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,852

Rep: Reputation: 360Reputation: 360Reputation: 360Reputation: 360
I imagine it was an issue of time more than anything.
 
Old 09-28-2005, 03:03 AM   #12
Basel
Member
 
Registered: Feb 2004
Location: United States
Distribution: Ubuntu 10.10
Posts: 319

Original Poster
Rep: Reputation: 30
Quote:
The last log seems to be clean. It would be more useful if we had a crash log. Why didn't it crash this time? Perhaps a program which you didn't run this time was causing the crash.
Here is a log after KDE crashed:
Code:
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x24045dc
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x240d25d
Launched ok, pid = 2416
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x2a007ae
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x2a007ae
Opener: received KillPPPDaemon
In killpppd(): Sending SIGTERM to 2344
Opener: received RemoveSecret
Opener: received RemoveSecret
Opener: received OpenResolv
Opener: received OpenResolv
Opener: received RemoveLock
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  7
  Minor opcode:  0
  Resource id:  0x1c00005
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  6
  Minor opcode:  0
  Resource id:  0x1c00005
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  7
  Minor opcode:  0
  Resource id:  0x200000b
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  6
  Minor opcode:  0
  Resource id:  0x200000b
kio (KDirWatch): WARNING: KDirWatch::removeDir can't handle 'Office/kword.desktop'
kicker: crashHandler called
KCrash: Application 'kicker' crashing...
Session management error: Could not open network socket
startkde: Shutting down...
kicker: sighandler called
klauncher: Exiting on signal 1
DCOP Cleaning up dead connections.
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  7
  Minor opcode:  0
  Resource id:  0xc00006
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  6
  Minor opcode:  0
  Resource id:  0xc00006
kio (KDirWatch): WARNING: KDirWatch::removeDir can't handle 'Office/kword.desktop'
startkde: Running shutdown scripts...
startkde: Done.

waiting for X server to shut down
Quote:
I imagine it was an issue of time more than anything.
KDE crashes even if I log-off just after it finishes starting.

Here is a log after exiting from Xfce with no crashes:


Code:
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
*** attempt to put segment in horiz list twice
** Message: xfce4-panel: Exit
Agent pid 1946 killed
xscreensaver: 10:50:02: SIGHUP received: restarting...
xscreensaver: 10:50:02: initial effective uid/gid was basel/shadow (1000/43)
xscreensaver: 10:50:02: running as basel/users (1000/100)


waiting for X server to shut down The application 'xfce-mcs-manager' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 3 requests (0 known processed) with 0 events remaining.
I will be using Xfce for the rest of the day and I will try to exit and start it again now and then to observe it. I will let you know I anything happens.
 
Old 09-28-2005, 03:38 AM   #13
Ilgar
Senior Member
 
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware64 14.2, Slackwarearm-current
Posts: 1,060

Rep: Reputation: 166Reputation: 166
I'm confused. You gave 3 logs so far (concerning KDE):
1) KDE w/crash
2) KDE w/out crash
3) KDE w/crash

In (1) it is clear that there is a crash, KCrash handler displays the crash info. (2) and (3) are almost identical, and they both indicate a clean exit. So there is no crash in (3) as you say. Only in (1) was there really a crash. And your exit from XFCE was also clean.

I wonder what made you think that there was a crash in (3). Btw, which DM do you use? KDM/GDM?
 
Old 09-28-2005, 04:46 AM   #14
Basel
Member
 
Registered: Feb 2004
Location: United States
Distribution: Ubuntu 10.10
Posts: 319

Original Poster
Rep: Reputation: 30
Let me clarify things:
1. I got the first log from KDE itself before returning to the console under runlevel 3. When I try to log-off from KDE a new window pops up with a bomb and that window contains the complete log. It allows me to store the file as well. KDE won't let me log-off unless I click on the 'close' button on that window.
2. I got the second log from the console under runlevel 3 after I tried to log-off from KDE. This the popup window did not show up.
3. I got the third log from the console under runlevel 3 after I tried to log-off from KDE as well. This time window with a picture of a bomb showed up however I took the log from the console and not from the stack trace.

Quote:
Btw, which DM do you use? KDM/GDM?
Slackware 10.2 starts under runlevel 3 for me. I don't have GDM.
 
Old 09-28-2005, 05:08 AM   #15
cathectic
Member
 
Registered: Sep 2004
Location: UK, Europe
Distribution: Slackware64
Posts: 761

Rep: Reputation: 35
It looks more like Kicker is causing the crash here.

Try deleting the configuration files for Kicker in ~/.kde

~/.kde/share/config/kicker (file)
~/.kde/share/apps/kicker (directory)
 
  


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
Unlock dialog crashes computer (causing restart) Mehtaw Linux - Software 3 08-15-2005 08:40 PM
gdm crashes but ok after restart ArchNGEL Linux - Software 6 07-31-2005 02:48 PM
Mysql crashes after restart ... :( sys7em Slackware 1 11-24-2004 03:33 PM
How can i get this command to restart at boot and in the background even if i log off abefroman Linux - Security 1 09-07-2004 03:40 PM
Removing Shutdown/Restart From Log Out Menu Guru3 Red Hat 0 07-03-2004 05:59 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:06 AM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration