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 104470 - Crash while removing gaim notification
Crash while removing gaim notification
Status: RESOLVED DUPLICATE of bug 94514
Product: gnome-panel
Classification: Other
Component: panel
2.1.x
Other other
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-01-26 15:57 UTC by alex
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description alex 2003-01-26 15:54:59 UTC 
Package: gnome-panel
Severity: normal
Version: GNOME2.1.5 2.1.5
Synopsis: Crash while removing gaim notification
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.1.5)
Description:
Description of Problem:

Not reproduced, panel crash when removing gaim




Debugging Information:

Backtrace was generated from '/usr/bin/gnome-panel'

[New Thread 16384 (LWP 6342)]
0x41dfec49 in wait4 () from /lib/libc.so.6

+ Trace 33150

  • #0 wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 646
  • #4 __pthread_sighandler
    from /lib/libpthread.so.0
  • #5 <signal handler called>
  • #6 g_type_check_instance
    from /usr/lib/libgobject-2.0.so.0
  • #7 g__g_dataset_global_lock
    from /usr/lib/libglib-2.0.so.0
  • #8 gdk_event_apply_filters
    from /usr/lib/libgdk-x11-2.0.so.0
  • #9 ?? 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-26 10:54 -------

The original reporter (alex@corcoles.net) 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, gnome-panel-maint@bugzilla.gnome.org.
Comment 1 Elijah Newren 2003-02-01 00:50:45 UTC 
Any chance you could get us a more complete stack trace?  (See
http://bugzilla.gnome.org/getting-traces.cgi for information on how to
do this).

Setting version->2.1.x, adding GNOMEVER2.1 keyword, setting
priority->high & severity->critical (it's a crasher).  The
simple-dup-finder seems to list this as unique, even with the short
stack trace that is there.  I probably would have marked this bug as
NEEDINFO, but thought the unique stack trace might be useful and the
reporter already said he hadn't reproduced it.  So I'll just mark it
as NEW for now.
Comment 2 alex 2003-02-01 01:23:02 UTC 
OK, I've tried to reproduced but I couldn't. I'm now running a Gnome
2.2rc, so perhaps the problem was solved in one of the releases?
Comment 3 Elijah Newren 2003-02-01 14:03:52 UTC 
Could be, or maybe it's a hard to reproduce bug.  Were you able to get
this crash multiple times while you were still using GNOME2.1.5?  If
so, then I'll probably just close this as fixed, but if not it may be
better to leave open for a while.

Thanks for the quick follow up, by the way.
Comment 4 Mark McLoughlin 2003-03-10 00:11:46 UTC 
This looks like a variant of bug #94514.

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