Bug 454475 – crash in Panel: Another panel crash with...

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 454475 - crash in Panel: Another panel crash with...


Summary:	crash in Panel: Another panel crash with...


Status:	RESOLVED DUPLICATE of bug 446183

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:	2007-07-07 06:13 UTC by fpiraneo
Modified:	2007-07-07 08:45 UTC

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

Description fpiraneo 2007-07-07 06:13:05 UTC

Version: 2.18.2

What were you doing when the application crashed?
Another panel crash with all debugging symbols installed. Hope will be useful.
Panels just starting at user's login.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 70275072 vsize: 70275072 resident: 29843456 share: 26927104 rss: 29843456 rss_rlim: 4294967295
CPU usage: start_time: 1183788340 rtime: 27 utime: 22 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208326432 (LWP 2785)]
0x00c5f402 in __kernel_vsyscall ()

+ Trace 146269

Thread 1 (Thread -1208326432 (LWP 2785))

#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 ??
from /usr/lib/libgtk-x11-2.0.so.0
#6 IA__g_hash_table_foreach
at ghash.c line 662
#7 gtk_rc_reset_styles
from /usr/lib/libgtk-x11-2.0.so.0
#8 ??
from /usr/lib/libgtk-x11-2.0.so.0
#9 IA__g_cclosure_marshal_VOID__PARAM
at gmarshal.c line 531
#10 IA__g_closure_invoke
at gclosure.c line 490
#11 signal_emit_unlocked_R
at gsignal.c line 2440
#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 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/libgtk-x11-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_rc_reparse_all_for_settings
from /usr/lib/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib/libgtk-x11-2.0.so.0
#24 IA__g_cclosure_marshal_VOID__PARAM
at gmarshal.c line 531
#25 IA__g_closure_invoke
at gclosure.c line 490
#26 signal_emit_unlocked_R
at gsignal.c line 2440
#27 IA__g_signal_emit_valist
at gsignal.c line 2199
#28 IA__g_signal_emit
at gsignal.c line 2243
#29 g_object_dispatch_properties_changed
at gobject.c line 563
#30 g_object_notify_dispatcher
at gobject.c line 245
#31 IA__g_object_notify
at gobjectnotifyqueue.c line 123
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgdk-x11-2.0.so.0
#35 IA__g_main_context_dispatch
at gmain.c line 2045
#36 g_main_context_iterate
at gmain.c line 2677
#37 IA__g_main_loop_run
at gmain.c line 2881
#38 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#39 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 236, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 165, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 261, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 598, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files
(gnome-panel:2785): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
warning: the debug information found in "/usr/lib/debug//usr/bin/gnome-panel.debug" does not match "/usr/bin/gnome-panel" (CRC mismatch).
--------------------------------------------------

Comment 1 Vincent Untz 2007-07-07 08:45:54 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?

It seems it's memory corruption happening here, and we need a valgrind log to know why it happens. See the last comments in bug 446183.

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