| Summary: | KDE crashes when firefox crashes | ||
|---|---|---|---|
| Product: | [I don't know] kde | Reporter: | Sawan Gupta <sawangupta.it> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | adaptee, cfeck |
| Priority: | NOR | Keywords: | triaged |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | RedHat Enterprise Linux | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Sawan Gupta
2012-06-29 08:30:03 UTC
> my KDE session dies
It is very likely that the Xorg server crashes because of Firefox. Please check the xorg.log files, or otherwise attach a backtrace if the crash is in a KDE component.
I didn't see anything weird in Xorg.0.log file How /var/log/messages show the following: Jun 29 13:40:43 sawangupta gconfd (sawan-4665): Received signal 15, shutting down cleanly Jun 29 13:40:43 sawangupta gdm[3918]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Jun 29 13:40:43 sawangupta gconfd (sawan-4665): Failed to give up lock on XML directory "/home/sawan/.gconf": Failed to remove lock directory `/home/sawan/.gconf/%gconf-xml-backend.lock': Directory not empty Jun 29 13:40:44 sawangupta gconfd (sawan-4665): Error releasing lockfile: Failed to remove lock directory `/home/sawan/.gconfd/lock': Directory not empty Jun 29 13:40:44 sawangupta gconfd (sawan-4665): Exiting Jun 29 13:40:45 sawangupta kernel: [drm] Setting GART location based on new memory map Jun 29 13:40:45 sawangupta kernel: [drm] Setting GART location based on new memory map Jun 29 13:40:45 sawangupta kernel: [drm] Loading R300 Microcode Jun 29 13:40:45 sawangupta kernel: [drm] Loading R300 Microcode Jun 29 13:40:45 sawangupta kernel: [drm] writeback test succeeded in 1 usecs Jun 29 13:40:45 sawangupta kernel: [drm] writeback test succeeded in 1 usecs Jun 29 13:42:28 sawangupta avahi-daemon[6522]: server.c: Packet too short or invalid while reading response record. (Maybe an UTF8 problem?) Jun 29 13:58:50 sawangupta automount[5314]: update_negative_cache: key "ddts" not found in map. Jun 29 13:59:03 sawangupta gconfd (sawan-6531): starting (version 2.14.0), pid 6531 user 'sawan' Jun 29 13:59:04 sawangupta gconfd (sawan-6531): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Jun 29 13:59:04 sawangupta gconfd (sawan-6531): Resolved address "xml:readwrite:/home/sawan/.gconf" to a writable configuration source at position 1 Jun 29 13:59:04 sawangupta gconfd (sawan-6531): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Jun 29 13:59:04 sawangupta pcscd: winscard.c:304:SCardConnect() Reader E-Gate 0 0 Not Found Jun 29 13:59:07 sawangupta last message repeated 3 times Jun 29 14:02:57 sawangupta gconfd (sawan-6531): Received signal 15, shutting down cleanly Jun 29 14:02:57 sawangupta gdm[5077]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Jun 29 14:02:57 sawangupta gconfd (sawan-6531): Failed to give up lock on XML directory "/home/sawan/.gconf": Failed to remove lock directory `/home/sawan/.gconf/%gconf-xml-backend.lock': Directory not empty Jun 29 14:02:58 sawangupta gconfd (sawan-6531): Error releasing lockfile: Failed to remove lock directory `/home/sawan/.gconfd/lock': Directory not empty Jun 29 14:02:58 sawangupta gconfd (sawan-6531): Exiting You have to check the Xorg.log of the previous server start, not that of the current. The file is usually named "Xorg.0.log.old".
> gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Here it says the X server failed.
I think KDE3 has been unmaintained for a long time. Xorg.0.log.old and Xorg.0.log are almost similar without any crash/failure error info. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |