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 441728 - crash in Panel:
crash in Panel:
Status: RESOLVED DUPLICATE of bug 403377
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-28 02:37 UTC by mathammer
Modified: 2007-05-28 08:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description mathammer 2007-05-28 02:37:06 UTC 
Version: 2.18.1

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.1 2007-05-04 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-sabayon-r2 #1 SMP Wed May 16 14:18:15 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Human-Graphite
Icon Theme: Tango

Memory status: size: 150736896 vsize: 150736896 resident: 23920640 share: 13750272 rss: 23920640 rss_rlim: 18446744073709551615
CPU usage: start_time: 1180287416 rtime: 344 utime: 344 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
0x00002b91541d9ad5 in waitpid () from /lib/libpthread.so.0

+ Trace 136380

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 wnck_workspace_get_width
    from /usr/lib64/libwnck-1.so.18
  • #4 ??
    from /usr/lib64/libwnck-1.so.18
  • #5 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 ??
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #13 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 ??
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #18 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 main 


----------- .xsession-errors ---------------------
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object
at Search.Tray.NotificationArea.UpdateManagerWindow (bool) [0x00000] in /var/tmp/portage/app-misc/beagle-0.2.16.2/work/beagle-0.2.16.2/search/Tray/NotificationArea.cs:168
at Search.Tray.NotificationArea.ManagerFilter (intptr,Gdk.Event) [0x0006d] in /var/tmp/portage/app-misc/beagle-0.2.16.2/work/beagle-0.2.16.2/search/Tray/NotificationArea.cs:233
at (wrapper delegate-invoke) System.MulticastDelegate.invoke_FilterReturn_intptr_Event (intptr,Gdk.Event) <0x0005e>
at GdkSharp.FilterFuncWrapper.NativeCallback (intptr,intptr,intptr) <0x00057>
at (wrapper native-to-managed) GdkSharp.FilterFuncWrapper.NativeCallback (intptr,intptr,intptr) <0x00078>
in (unmanaged) 0x2aaaad12a5fb
at (wrapper managed-to-native) Gtk.Application.gtk_main () <0x0000b>
at Gtk.Application.Run () <0x00008>
at Gnome.Program.Run () <0x0000c>
at Search.MainWindow.Main (string[]) [0x00075] in /var/tmp/portage/app-misc/beagle-0.2.16.2/work/beagle-0.2.16.2/search/Search.cs:72
(gnome-panel:954): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24
--------------------------------------------------
Comment 1 Vincent Untz 2007-05-28 08:29:34 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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