Bug 462361 – crash in Panel: the system was starting ...

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 462361 - crash in Panel: the system was starting ...


Summary:	crash in Panel: the system was starting ...


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-01 04:12 UTC by Alejandro Ochoa
Modified:	2007-09-02 12:25 UTC

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

Description Alejandro Ochoa 2007-08-01 04:12:33 UTC

Version: 2.18.3

What were you doing when the application crashed?
the system was starting (logged in after reboot)


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:21:43 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 310841344 vsize: 310841344 resident: 31211520 share: 27377664 rss: 31211520 rss_rlim: 18446744073709551615
CPU usage: start_time: 1185941507 rtime: 13 utime: 9 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912516393280 (LWP 3054)]
(no debugging symbols found)
0x00000037ea60d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 151995

Thread 1 (Thread 46912516393280 (LWP 3054))

#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 ---------------------
localuser:viiia being added to access control list
SESSION_MANAGER=local/pu110769.student.Princeton.EDU:/tmp/.ICE-unix/2927
Initializing nautilus-open-terminal extension
(gnome-panel:3054): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------

Comment 1 Vincent Untz 2007-09-02 12:25: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 ***