After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 105660 - notification applet crashes on logout
notification applet crashes on logout
Status: RESOLVED DUPLICATE of bug 105421
Product: gnome-panel
Classification: Other
Component: notification area
unspecified
Other other
: Normal normal
: ---
Assigned To: Havoc Pennington
Panel Maintainers
: 105560 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-02-09 17:34 UTC by Frank
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Frank 2003-02-09 17:30:16 UTC 
Package: gnome-panel
Severity: normal
Version: GNOME2.2.0 2.2.0.1
os_details: Gnome.Org
Synopsis: notification applet crashes on logout
Bugzilla-Product: gnome-panel
Bugzilla-Component: Notification Area Applet
Description:
Description of Problem:


Steps to reproduce the problem:
1. add notification applet to topmost panel
2. logout	
3. 

Actual Results:
notf. app. segfaults on logout

Expected Results:
clean logout

How often does this happen?
everytime

Additional Information:
garnome 0.20.2




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-09 12:30 -------

The original reporter (naru_usenet@hotmail.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, hp@redhat.com.
Comment 1 Ross Burton 2003-02-10 11:13:44 UTC 
*** Bug 105560 has been marked as a duplicate of this bug. ***
Comment 2 fatwreckfan 2003-02-11 00:59:51 UTC 
Panel Notification Area 2.2.0.1 does the same for me, segfaulting on
removal from the panel or logout.  Running Gentoo Linux 1.4_rc2.
Comment 3 Vincent Untz 2003-02-11 21:22:34 UTC 
A stack trace would be useful, but I guess it's a dup of bug #105421.
If not, please reopen.

*** This bug has been marked as a duplicate of 105421 ***