Bug 97783 - Panel crashes when logging out with ctrl-alt-del
Summary: Panel crashes when logging out with ctrl-alt-del
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-panel
Version: 9
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: CambridgeBlocker
TreeView+ depends on / blocked
 
Reported: 2003-06-20 22:05 UTC by Carlos Rodrigues
Modified: 2007-04-18 16:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-02-27 13:14:59 UTC
Embargoed:


Attachments (Terms of Use)

Description Carlos Rodrigues 2003-06-20 22:05:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
If I press ctrl-alt-del and then logout, the gnome panel segfaults.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Press ctrl-alt-del
2. Click logout
3. Click Ok
    

Actual Results:  I get a dialog stating that the gnome panel has crashed.

Expected Results:  It should not crash.

Additional info:

Comment 1 petrosyan 2003-08-16 15:06:30 UTC
I cannot reproduce this bug with the latest gnome-panel-2.3.6.2-2 from Rawhide.

Comment 2 Alexander Larsson 2003-08-27 11:00:23 UTC
I can't reproduce it either. It might be related to the second-logout dialog
crashes bug which was fixed. It was a gtk2 bluecurve theme.

Comment 3 petrosyan 2003-11-07 18:42:39 UTC
this bug should be closed now. it is not reproducible in Fedora Core 1
( gnome-panel-2.4.0-3 ).


Comment 4 Leonard den Ottolander 2004-02-26 16:37:05 UTC
Carlos, do you still experience this issue after doing all upgrades?


Comment 5 Carlos Rodrigues 2004-02-27 03:05:04 UTC
I am using Fedora Core 1 now. This problem seems to be gone.

Comment 6 petrosyan 2004-02-27 05:52:33 UTC
this bug should be resolved with CURRENTRELEASE resolution


Note You need to log in before you can comment on or make changes to this bug.