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 462173 - crash in Panel: Only start up as root.
crash in Panel: Only start up as root.
Status: RESOLVED DUPLICATE of bug 461667
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-31 15:33 UTC by qyl05111
Modified: 2007-08-01 12:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description qyl05111 2007-07-31 15:33:49 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Only start up as root.


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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve-Lime
Icon Theme: Bluecurve

Memory status: size: 61550592 vsize: 61550592 resident: 28192768 share: 23588864 rss: 28192768 rss_rlim: 4294967295
CPU usage: start_time: 1185895885 rtime: 20 utime: 18 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208822048 (LWP 2692)]
(no debugging symbols found)
0x00dad402 in __kernel_vsyscall ()

+ Trace 151840

Thread 1 (Thread -1208822048 (LWP 2692))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #6 gtk_rc_reset_styles
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_cclosure_marshal_VOID__PARAM
    from /lib/libgobject-2.0.so.0
  • #9 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #11 g_cclosure_marshal_VOID__ENUM
    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 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #15 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #16 g_object_notify
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #20 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #21 g_cclosure_marshal_VOID__ENUM
    from /lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (7 sec old) ---------------------
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
Launching a SCIM process with x11...
Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
GTK Panel of SCIM 1.4.5
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2589
(gnome-panel:2692): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 palfrey 2007-08-01 12:38:34 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 461667 ***