Bug 466980 – 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 466980 - crash in Panel:


Summary:	crash in Panel:


Status:	RESOLVED DUPLICATE of bug 446183

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-15 15:08 UTC by john.satterfield
Modified:	2007-09-02 12:23 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description john.satterfield 2007-08-15 15:08:38 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: ale-panther_gtk2
Icon Theme: MacOS-X

Memory status: size: 39489536 vsize: 39489536 resident: 18808832 share: 16265216 rss: 18808832 rss_rlim: 4294967295
CPU usage: start_time: 1187190429 rtime: 21 utime: 16 stime: 5 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 -1208330528 (LWP 2951)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 155418

Thread 1 (Thread -1208330528 (LWP 2951))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_slice_alloc
from /lib/libglib-2.0.so.0
#5 g_slist_copy
from /lib/libglib-2.0.so.0
#6 ??
from /usr/lib/libgtk-x11-2.0.so.0
#7 ??
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_rc_get_style
from /usr/lib/libgtk-x11-2.0.so.0
#9 ??
from /usr/lib/libgtk-x11-2.0.so.0
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_widget_reset_rc_styles
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
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 ---------------------
localuser:dad being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2828
Starting gdesklets-daemon...

Connecting to daemon [###          ]
Connecting to daemon [ ###         ]
Connecting to daemon [  ###        ]
Connecting to daemon [   ###       ]
Connecting to daemon [    ###      ]
Connecting to 
(gnome-panel:2951): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

Connecting to daemon [        ###  ]
Connecting to daemon [         ### ]
Connecting to daemon [          ###]
Connecting to daemon [         ### ]
Connecting to daemon [        ###  ]
Connecting to 
--------------------------------------------------

Comment 1 Vincent Untz 2007-09-02 12:23:18 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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