Bug 452961 – 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 452961 - 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-07-02 00:42 UTC by henryrayker
Modified:	2008-01-26 13:34 UTC

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

Description henryrayker 2007-07-02 00:42:38 UTC

Version: 2.18.2

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3163.fc7 #1 SMP Tue May 15 17:23:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Bluecurve

Memory status: size: 36560896 vsize: 36560896 resident: 19103744 share: 16207872 rss: 19103744 rss_rlim: 4294967295
CPU usage: start_time: 1183336931 rtime: 31 utime: 27 stime: 4 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 -1208752416 (LWP 2890)]
(no debugging symbols found)
0x0043d402 in __kernel_vsyscall ()

+ Trace 145144

Thread 1 (Thread -1208752416 (LWP 2890))

#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_slist_remove_all
from /lib/libglib-2.0.so.0
#5 ??
from /usr/lib/libgtk-x11-2.0.so.0
#6 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#7 gtk_rc_reset_styles
from /usr/lib/libgtk-x11-2.0.so.0
#8 ??
from /usr/lib/libgtk-x11-2.0.so.0
#9 g_cclosure_marshal_VOID__PARAM
from /lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /lib/libgobject-2.0.so.0
#11 ??
from /lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#13 g_signal_emit
from /lib/libgobject-2.0.so.0
#14 ??
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_object_thaw_notify
from /lib/libgobject-2.0.so.0
#17 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_rc_reparse_all_for_settings
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_cclosure_marshal_VOID__PARAM
from /lib/libgobject-2.0.so.0
#21 g_closure_invoke
from /lib/libgobject-2.0.so.0
#22 ??
from /lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#24 g_signal_emit
from /lib/libgobject-2.0.so.0
#25 ??
from /lib/libgobject-2.0.so.0
#26 ??
from /lib/libgobject-2.0.so.0
#27 g_object_thaw_notify
from /lib/libgobject-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib/libgdk-x11-2.0.so.0
#32 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#33 ??
from /lib/libglib-2.0.so.0
#34 g_main_loop_run
from /lib/libglib-2.0.so.0
#35 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#36 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
localuser:kerry being added to access control list
SESSION_MANAGER=local/Edgy32b:/tmp/.ICE-unix/2771
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
(gnome-panel:2890): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
error getting update info:  Cannot open/read repomd.xml file for repository: fedora
** Message: <info>  You are now connected to the wireless network 'Network'.
--------------------------------------------------

Comment 1 Karsten Bräckelmann 2007-07-02 01:31:38 UTC

Thanks for taking the time to report this bug.

Unfortunately, that stack trace is not very useful in determining the cause of
the crash. Can you get us a stack trace with debugging symbols? Please install
some debugging packages and reproduce the crash, if possible.

Please see http://live.gnome.org/GettingTraces for more information on how to
do so and reopen this bug or simply report a new one.  Thanks!

Comment 2 Philip Withnall 2008-01-26 13:34:27 UTC


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