Bug 598963 – crash in Panel: gnome panel crashes when...

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 598963 - crash in Panel: gnome panel crashes when...


Summary:	crash in Panel: gnome panel crashes when...


Status:	RESOLVED DUPLICATE of bug 599851

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	2.26.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-10-19 17:29 UTC by le.gauche
Modified:	2009-10-29 04:15 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description le.gauche 2009-10-19 17:29:15 UTC

Version: 2.26.3

What were you doing when the application crashed?
gnome panel crashes when the session start


Distribution: Debian squeeze/sid
Gnome Release: 2.28.0 2009-09-27 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.30-1-486 #1 Sat Aug 15 18:14:04 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10604000
Selinux: No
Accessibility: Enabled
GTK+ Theme: ClearlooksClassic
Icon Theme: Gion
GTK+ Modules: gail:atk-bridge, gnomebreakpad, canberra-gtk-module

Memory status: size: 75460608 vsize: 75460608 resident: 25305088 share: 17031168 rss: 25305088 rss_rlim: 18446744073709551615
CPU usage: start_time: 1255972572 rtime: 1347 utime: 1234 stime: 113 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
0xb7f88430 in __kernel_vsyscall ()

+ Trace 218428

Thread 1 (Thread 0xb6c85750 (LWP 2608))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gspawn.c line 386
#3 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gspawn.c line 700
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 IA__g_assertion_message
#10 IA__g_assertion_message_expr
#11 ??
from /usr/lib/libORBit-2.so.0
#12 PortableServer_POA_servant_to_reference
from /usr/lib/libORBit-2.so.0
#13 ??
from /usr/lib/libbonobo-2.so.0
#14 IA__g_object_set_property
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gobject.c line 1653
#15 IA__g_object_newv
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gobject.c line 1278
#16 object_set_property
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gobject.c line 951
#17 IA__g_object_newv
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gobject.c line 1279
#18 spi_accessible_construct
at accessible.c line 566
#19 spi_accessible_new
at accessible.c line 545
#20 spi_atk_emit_eventv
at bridge.c line 777
#21 spi_atk_bridge_property_event_listener
at bridge.c line 978
#22 signal_emit_unlocked_R
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gsignal.c line 3220
#23 signal_check_skip_emission
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gsignal.c line 2776
#24 IA__g_signal_emit_valist
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gsignal.c line 2933
#25 signal_parse_name
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gsignal.c line 995
#26 IA__g_signal_emit_by_name
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gsignal.c line 3066
#27 atk_object_notify
at atkobject.c line 1476
#28 IA__g_cclosure_marshal_VOID__BOXED
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gmarshal.c line 566
#29 g_type_iface_meta_marshal
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gclosure.c line 901
#30 IA__g_closure_invoke
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gclosure.c line 752
#31 signal_emit_unlocked_R
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gsignal.c line 3171
#32 signal_check_skip_emission
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gsignal.c line 2776
#33 IA__g_signal_emit_valist
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gsignal.c line 2933
#34 signal_parse_name
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gsignal.c line 995
#35 IA__g_signal_emit_by_name
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gsignal.c line 3066
#36 g_object_finalize
at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gobject.c line 772
#37 ??

Backtrace stopped: previous frame inner to this frame (corrupt stack?)
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
The error was 'BadPixmap (invalid Pixmap parameter)'.
  (Details: serial 157625 error_code 4 request_code 54 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
**
ERROR:poa.c:1028:ORBit_POA_activate_object_T: assertion failed: ((poa->life_flags & ORBit_LifeF_DeactivateDo) == 0)
warning: .dynamic section for "/usr/lib/libgio-2.0.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libgconf-2.so.4" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libgnomevfs-2.so.0" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------

Comment 1 Akhil Laddha 2009-10-29 04:15:25 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 bug 599851 ***