Bug 551265 – crash in Panel:

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 551265 - crash in Panel:


Summary:	crash in Panel:


Status:	RESOLVED DUPLICATE of bug 446183

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-09-07 18:32 UTC by arv1918
Modified:	2008-09-07 18:48 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description arv1918 2008-09-07 18:32:51 UTC

Version: 2.20.1

What were you doing when the application crashed?



Distribution: CentOS release 5 (Final)
Gnome Release: 2.20.1 2007-11-09 (Joel Barrios D., para Alcance Libre. - Dedicado a Blanca Caullieres)
BugBuddy Version: 2.20.1

System: Linux 2.6.18-8.1.15.el5 #1 SMP Mon Oct 22 08:32:04 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaAquaIsh
Icon Theme: Tango

Memory status: size: 103944192 vsize: 103944192 resident: 12763136 share: 9625600 rss: 12763136 rss_rlim: 4294967295
CPU usage: start_time: 1220812328 rtime: 16 utime: 14 stime: 2 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)
[Thread debugging using libthread_db enabled]
[New Thread -1208420656 (LWP 5919)]
0x0017a402 in __kernel_vsyscall ()

+ Trace 206456

Thread 1 (Thread -1208420656 (LWP 5919))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 g_spawn_sync
from /lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#4 run_bug_buddy
at gnome-breakpad.cc line 213
#5 check_if_gdb
at gnome-breakpad.cc line 283
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
#7 google_breakpad::ExceptionHandler::HandleException
at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
#8 <signal handler called>
#9 g_slist_remove_all
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#12 gtk_rc_reset_styles
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_cclosure_marshal_VOID__PARAM
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /lib/libgobject-2.0.so.0
#17 ??
from /lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#19 g_signal_emit
from /lib/libgobject-2.0.so.0
#20 ??
from /lib/libgobject-2.0.so.0
#21 ??
from /lib/libgobject-2.0.so.0
#22 g_object_notify
from /lib/libgobject-2.0.so.0
#23 ??
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#25 ??
from /usr/lib/libgdk-x11-2.0.so.0
#26 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#27 ??
from /lib/libglib-2.0.so.0
#28 g_main_loop_run
from /lib/libglib-2.0.so.0
#29 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#30 main
#0 __kernel_vsyscall



----------- .xsession-errors (14 sec old) ---------------------
Initializing nautilus-main-menu extension
Initializing gnome-mount extension
Initializing nautilus-open-terminal extension
(gnome-panel:5919): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------

Comment 1 Pascal Terjan 2008-09-07 18:48:59 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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