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 512018 - crash in Panel: Just logged in via gdm. ...
crash in Panel: Just logged in via gdm. ...
Status: RESOLVED DUPLICATE of bug 446183
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-25 11:04 UTC by Ben Caradoc-Davies
Modified: 2008-01-25 18:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Ben Caradoc-Davies 2008-01-25 11:04:02 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Just logged in via gdm. Theme has not yet been fully applied (e.g. gnome-terminal icon is wrong, font not set ...).


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 20:27:10 EST 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: 336584704 vsize: 336584704 resident: 34734080 share: 30433280 rss: 34734080 rss_rlim: 18446744073709551615
CPU usage: start_time: 1201258902 rtime: 21 utime: 16 stime: 5 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 46912496335728 (LWP 2207)]
(no debugging symbols found)
0x0000003b5960d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 186745

Thread 1 (Thread 46912496335728 (LWP 2207))

  • #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:ben being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2137
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
(gnome-panel:2207): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff90ffd000
--------------------------------------------------
Comment 1 Philip Withnall 2008-01-25 18:06:42 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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