Bug 448192 – 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 448192 - 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-06-16 12:56 UTC by halcyon_consultant
Modified:	2007-06-16 13:04 UTC

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

Description halcyon_consultant 2007-06-16 12:56:32 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.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 311349248 vsize: 311349248 resident: 24788992 share: 18235392 rss: 24788992 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184589661 rtime: 234 utime: 108 stime: 126 cutime:3 cstime: 9 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496352272 (LWP 2619)]
(no debugging symbols found)
0x000000397d20d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 141431

Thread 1 (Thread 46912496352272 (LWP 2619))

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



----------- .xsession-errors (6 sec old) ---------------------
Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
SESSION_MANAGER=local/p930-c.falcon.com:/tmp/.ICE-unix/2494
GTK Panel of SCIM 1.4.5
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
(gnome-panel:2619): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:2726): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: 第 1 行第 40 個字發生錯誤：元素‘b’已關閉，但開啟中的元素是‘span’
--------------------------------------------------

Comment 1 Vincent Untz 2007-06-16 13:04:08 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 ***