Bug 2908

Summary: Gnome/Enlightenment dumps core on reboots
Product: [Retired] Red Hat Linux Reporter: Suhaib Siddiqi <ssiddiqi>
Component: distributionAssignee: Michael Fulbright <msf>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: lp.brais, ssiddiqi
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-07-06 16:01:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Suhaib Siddiqi 1999-05-18 14:25:36 UTC 
RedHat 6.0 does core dump, if Gnome/Enlightment is used
as desktop.  If I use AfterStep or anyother desktop windows
manager, core file is not created.

On each reboot Gnome/Enlightment creates a *core* file
under /root, though system boots and works OK.  It is
annoying to see *core* in /root on each rebot of RedHat 6.0
Comment 1 Derek Tattersall 1999-05-18 19:08:59 UTC 
Try to use gdb to determine which program is causing the core dump.  I
can not get gnome/enlightenment to fail.

------- Email Received From  "Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com> 05/18/99 15:23 -------
Comment 2 Suhaib Siddiqi 1999-05-19 00:45:59 UTC 
OK here is the GDB report of the core file.  Drivemount_applet
in Gnome does a core dump.
--GDB/DDD output---
Core was generated by 'drivemount_applet --activate-goad-server
drivemount-applet-factory'
Program terminated with signal 6, Aborted
#0 0x40416111 in ?? ()
----
Removing drivemount option from Factory installed settings stops
producing core dump.
Comment 3 Jay Turner 1999-05-19 14:29:59 UTC 
I am able to recreate this in the lab.

------- Email Received From  "Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com> 05/20/99 06:13 -------
Comment 4 Michael Fulbright 1999-07-06 16:01:59 UTC 
This will be fixed soon in a gnome-core and gtk+ update.

It has to do with how GNOME/GTK+ programs handled the case
where they could no longer talk to the X server.  For debugging
purposes a core file was created. This behaviour will be changed.