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 520158 - crash in Panel: Panel crashed immediatel...
crash in Panel: Panel crashed immediatel...
Status: RESOLVED DUPLICATE of bug 475065
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-03-03 19:20 UTC by Paul Jenner
Modified: 2008-03-03 21:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Paul Jenner 2008-03-03 19:20:39 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Panel crashed immediately on login.


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.17-82.fc7 #1 SMP Thu Feb 28 16:22:02 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 59719680 vsize: 59719680 resident: 11718656 share: 8912896 rss: 11718656 rss_rlim: 4294967295
CPU usage: start_time: 1204571953 rtime: 57 utime: 48 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1209022752 (LWP 6029)]
0x00110402 in __kernel_vsyscall ()

+ Trace 191183

Thread 1 (Thread -1209022752 (LWP 6029))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 IA__g_slist_remove_all
    at gslist.c line 233
  • #5 gtk_rc_clear_realized_style
    at gtkrc.c line 1622
  • #6 IA__g_hash_table_foreach
    at ghash.c line 662
  • #7 IA__gtk_rc_reset_styles
    at gtkrc.c line 1668
  • #8 gtk_settings_notify
    at gtksettings.c line 753
  • #9 IA__g_cclosure_marshal_VOID__PARAM
    at gmarshal.c line 531
  • #10 g_type_class_meta_marshal
    at gclosure.c line 567
  • #11 IA__g_closure_invoke
    at gclosure.c line 490
  • #12 signal_emit_unlocked_R
    at gsignal.c line 2370
  • #13 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #14 IA__g_signal_emit
    at gsignal.c line 2243
  • #15 g_object_dispatch_properties_changed
    at gobject.c line 563
  • #16 g_object_notify_dispatcher
    at gobject.c line 245
  • #17 IA__g_object_notify
    at gobjectnotifyqueue.c line 123
  • #18 _gtk_settings_handle_event
    at gtksettings.c line 1464
  • #19 IA__gtk_main_do_event
    at gtkmain.c line 1423
  • #20 gdk_event_dispatch
    at gdkevents-x11.c line 2318
  • #21 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #22 g_main_context_iterate
    at gmain.c line 2677
  • #23 IA__g_main_loop_run
    at gmain.c line 2881
  • #24 IA__gtk_main
    at gtkmain.c line 1154
  • #25 main
    at main.c line 100
  • #0 __kernel_vsyscall 


----------- .xsession-errors (20 sec old) ---------------------
localuser:psj being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/5922
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
(gnome-panel:6029): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** Message: failed to load session from /home/psj/.nautilus/saved-session-DTK10T
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
warning: the debug information found in "/usr/lib/debug//lib/libdbus-1.so.3.2.0.debug" does not match "/lib/libdbus-1.so.3" (CRC mismatch).
--------------------------------------------------
Comment 1 Philip Withnall 2008-03-03 21:28:29 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 475065 ***