Bug 512697 – crash in Panel: Logging into desktop.

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 512697 - crash in Panel: Logging into desktop.


Summary:	crash in Panel: Logging into desktop.


Status:	RESOLVED DUPLICATE of bug 475065

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:	2008-01-29 01:14 UTC by elliot
Modified:	2008-01-29 06:59 UTC

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

Description elliot 2008-01-29 01:14:53 UTC

Version: 2.18.3

What were you doing when the application crashed?
Logging into desktop.


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 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: Echo

Memory status: size: 94457856 vsize: 94457856 resident: 36552704 share: 33792000 rss: 36552704 rss_rlim: 4294967295
CPU usage: start_time: 1201569241 rtime: 58 utime: 46 stime: 12 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 -1208178976 (LWP 2723)]
0x00110402 in __kernel_vsyscall ()

+ Trace 187138

Thread 1 (Thread -1208178976 (LWP 2723))

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



----------- .xsession-errors (17 sec old) ---------------------
localuser:elliot being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2599
winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running
Initializing nautilus-open-terminal extension
Initializing nautilus-image-converter extension
Window manager warning: Log level 8: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nautilus:2725): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(gnome-panel:2723): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(nm-applet:2742): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
/usr/bin/puplet:437: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  gtk.main()
--------------------------------------------------

Comment 1 Philip Withnall 2008-01-29 06:59:37 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 475065 ***