Bug 448574 – crash in Panel: starting up

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 448574 - crash in Panel: starting up


Summary:	crash in Panel: starting up


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-17 19:46 UTC by jason.russler
Modified:	2007-06-17 20:35 UTC

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

Description jason.russler 2007-06-17 19:46:14 UTC

Version: 2.18.2

What were you doing when the application crashed?
starting up


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 296603648 vsize: 296603648 resident: 20983808 share: 17195008 rss: 20983808 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182109528 rtime: 13 utime: 11 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496417808 (LWP 2767)]
(no debugging symbols found)
0x0000003988c0d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 141720

Thread 1 (Thread 46912496417808 (LWP 2767))

#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_slist_remove_all
from /lib64/libglib-2.0.so.0
#4 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#5 g_hash_table_foreach
from /lib64/libglib-2.0.so.0
#6 gtk_rc_reset_styles
from /usr/lib64/libgtk-x11-2.0.so.0
#7 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#8 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#9 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit
from /lib64/libgobject-2.0.so.0
#12 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#13 g_object_notify
from /lib64/libgobject-2.0.so.0
#14 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#15 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#16 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgdk-x11-2.0.so.0
#17 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#18 g_cclosure_marshal_VOID__ENUM
from /lib64/libglib-2.0.so.0
#19 g_main_loop_run
from /lib64/libglib-2.0.so.0
#20 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#21 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (7 sec old) ---------------------
localuser:jason being added to access control list
SESSION_MANAGER=local/rowlf.electricmayhem:/tmp/.ICE-unix/2641
Initializing nautilus-flac-converter extension
Initializing nautilus-image-converter extension
Initializing nautilus-open-terminal extension
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
(gnome-panel:2767): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------

Comment 1 Vincent Untz 2007-06-17 20:35:40 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 ***