Bug 520940 – crash in Panel:

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 520940 - crash in Panel:


Summary:	crash in Panel:


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-03-07 09:52 UTC by justin
Modified:	2008-03-07 12:07 UTC

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

Description justin 2008-03-07 09:52:45 UTC

Version: 2.18.3

What were you doing when the application crashed?



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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 46612480 vsize: 46612480 resident: 20647936 share: 17235968 rss: 20647936 rss_rlim: 4294967295
CPU usage: start_time: 1204883382 rtime: 31 utime: 27 stime: 4 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 -1208379680 (LWP 2852)]
0x00110402 in __kernel_vsyscall ()

+ Trace 191605

Thread 1 (Thread -1208379680 (LWP 2852))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#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 (129568 sec old) ---------------------
(gnome-terminal:18637): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:18637): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:18637): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
CalDAV Eplugin starting up ...
** (evolution:20393): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:20393): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:20393): e-data-server-DEBUG: Loading categories from "/home/justin/.evolution/categories.xml"
(evolution:20393): e-data-server-DEBUG: Loaded 29 categories
(evolution:20393): libebook-WARNING **: invalid escape, passing it through
--------------------------------------------------

Comment 1 Gianluca Borello 2008-03-07 12:07:32 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 ***