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 107007 - random gtk crash [gtk_widget_get_toplevel]
random gtk crash [gtk_widget_get_toplevel]
Status: RESOLVED DUPLICATE of bug 105745
Product: gtk+
Classification: Platform
Component: Widget: Other
2.2.x
Other other
: High critical
: ---
Assigned To: gtk-bugs
Panel Maintainers
: 110379 111980 112562 112774 113745 115852 116893 117061 117300 117715 118571 118847 119402 119503 121735 123530 123810 124048 124405 124629 124862 126560 129917 130405 130616 133308 141885 155939 304745 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-02-25 04:25 UTC by James Ralston
Modified: 2005-05-20 01:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description James Ralston 2003-02-25 04:20:06 UTC 
Package: gnome-panel
Severity: normal
Version: 2.2.0.1
Synopsis: gnome-panel crashed for no reason (?)
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:

The gnome-panel crashed out-of-the-blue.  If something I did caused it
to crash, I have no idea what I did.

How often does this happen?

Rarely; this is the first time since upgrading to Phoebe 8.0.94.




Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...[New Thread 1086447968 (LWP 4748)]
0xffffe002 in ?? ()

+ Trace 34245

Thread 1 (Thread 1086447968 (LWP 4748))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_widget_get_toplevel
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 gtk_false
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ?? 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-24 23:20 -------

Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
Comment 1 Elijah Newren 2003-02-27 23:06:11 UTC 
Appears to be a unique stack trace, according to the
simple-dup-finder.  Setting version->2.2.x, marking priority->high &
severity->critical (it's a crasher), adding GNOMEVER2.2 and bugsquad
keywords, and marking as new.
Comment 2 Mark McLoughlin 2003-03-10 02:05:09 UTC 
Hmm, another totally random bug involving gtk_widget_get_toplevel().

Havoc: was the notification area in-proc in that version of Phoebe ?
Comment 3 Elijah Newren 2003-03-20 17:28:52 UTC 
Looks like the stack trace in bug 108854, which is a bug filed against
the most recent nautilus.  If this is a duplicate, then this would
have to be a gtk+ bug.

Why is this bug NEEDINFO?  What extra info is the reporter suppose to
provide?
Comment 4 Elijah Newren 2003-07-07 02:08:16 UTC 
*** Bug 113745 has been marked as a duplicate of this bug. ***
Comment 5 Elijah Newren 2003-07-07 02:09:28 UTC 
*** Bug 110379 has been marked as a duplicate of this bug. ***
Comment 6 Elijah Newren 2003-07-07 02:10:41 UTC 
*** Bug 111980 has been marked as a duplicate of this bug. ***
Comment 7 Elijah Newren 2003-07-07 02:12:18 UTC 
*** Bug 112562 has been marked as a duplicate of this bug. ***
Comment 8 Elijah Newren 2003-07-07 02:13:39 UTC 
*** Bug 112774 has been marked as a duplicate of this bug. ***
Comment 9 Elijah Newren 2003-07-07 02:17:07 UTC 
The duplicates were in nautilus, gnome-terminal, and gnome-panel.  I'm
moving to gtk+, and reopening so that I can reassign to the "owner of
select component"...
Comment 10 Elijah Newren 2003-07-07 02:18:11 UTC 
Now I'm reassigning...
Comment 11 Owen Taylor 2003-07-08 15:13:18 UTC 
*** Bug 116893 has been marked as a duplicate of this bug. ***
Comment 12 Kjartan Maraas 2003-07-09 17:16:59 UTC 
*** Bug 117061 has been marked as a duplicate of this bug. ***
Comment 13 John Fleck 2003-07-18 01:34:04 UTC 
*** Bug 117715 has been marked as a duplicate of this bug. ***
Comment 14 John Fleck 2003-07-18 01:34:27 UTC 
*** Bug 117300 has been marked as a duplicate of this bug. ***
Comment 15 Elijah Newren 2003-07-29 18:14:24 UTC 
*** Bug 118571 has been marked as a duplicate of this bug. ***
Comment 16 Elijah Newren 2003-08-01 15:30:20 UTC 
*** Bug 118847 has been marked as a duplicate of this bug. ***
Comment 17 Owen Taylor 2003-08-01 21:27:50 UTC 
*** Bug 115852 has been marked as a duplicate of this bug. ***
Comment 18 Elijah Newren 2003-08-08 17:34:22 UTC 
*** Bug 119402 has been marked as a duplicate of this bug. ***
Comment 19 Elijah Newren 2003-08-09 19:04:13 UTC 
*** Bug 119503 has been marked as a duplicate of this bug. ***
Comment 20 Owen Taylor 2003-08-13 21:55:33 UTC 
Looking at these backtraces, I think it's pretty likely this
is just another manifestation of bug 105745. If we get
any duplicates that are definitely GTK+-2.2.2 or newer,
please reopen.


*** This bug has been marked as a duplicate of 105745 ***
Comment 21 Owen Taylor 2003-08-14 19:26:06 UTC 
The fix wasn't actually in 2.2.2, so read "2.2.3 or newer"
Comment 22 Vincent Untz 2003-09-30 10:33:13 UTC 
*** Bug 123530 has been marked as a duplicate of this bug. ***
Comment 23 Vincent Untz 2003-09-30 10:33:27 UTC 
*** Bug 121735 has been marked as a duplicate of this bug. ***
Comment 24 Kjartan Maraas 2003-10-04 20:32:30 UTC 
*** Bug 123810 has been marked as a duplicate of this bug. ***
Comment 25 mwehner 2003-10-11 01:55:44 UTC 
*** Bug 124048 has been marked as a duplicate of this bug. ***
Comment 26 Vincent Untz 2003-10-12 14:18:09 UTC 
*** Bug 124405 has been marked as a duplicate of this bug. ***
Comment 27 Vincent Untz 2003-10-15 09:01:59 UTC 
*** Bug 124629 has been marked as a duplicate of this bug. ***
Comment 28 Vincent Untz 2003-10-20 08:57:59 UTC 
*** Bug 124862 has been marked as a duplicate of this bug. ***
Comment 29 Crispin Flowerday (not receiving bugmail) 2003-11-09 21:03:59 UTC 
*** Bug 126560 has been marked as a duplicate of this bug. ***
Comment 30 Heath Harrelson 2004-01-02 20:15:49 UTC 
*** Bug 130405 has been marked as a duplicate of this bug. ***
Comment 31 Heath Harrelson 2004-01-02 20:19:21 UTC 
*** Bug 129917 has been marked as a duplicate of this bug. ***
Comment 32 Vincent Untz 2004-02-04 15:59:16 UTC 
*** Bug 133308 has been marked as a duplicate of this bug. ***
Comment 33 Elijah Newren 2004-02-10 06:00:29 UTC 
*** Bug 130616 has been marked as a duplicate of this bug. ***
Comment 34 Martin Wehner 2004-05-08 19:53:19 UTC 
*** Bug 141885 has been marked as a duplicate of this bug. ***
Comment 35 Elijah Newren 2004-10-20 21:01:42 UTC 
*** Bug 155939 has been marked as a duplicate of this bug. ***
Comment 36 Elijah Newren 2005-05-20 01:27:27 UTC 
*** Bug 304745 has been marked as a duplicate of this bug. ***