Bug 604010 – crash in Panel: Just starting up Gnome.

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 604010 - crash in Panel: Just starting up Gnome.


Summary:	crash in Panel: Just starting up Gnome.


Status:	RESOLVED DUPLICATE of bug 597914

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-12-07 18:27 UTC by pmbarros
Modified:	2009-12-07 19:27 UTC

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

Description pmbarros 2009-12-07 18:27:47 UTC

Version: 2.28.0

What were you doing when the application crashed?
Just starting up Gnome.


Distribution: Debian squeeze/sid
Gnome Release: 2.28.0 2009-11-21 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.30-1-powerpc #1 Mon Aug 3 18:50:42 UTC 2009 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10605000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Shiki-Dust
Icon Theme: oxygen
GTK+ Modules: gail:atk-bridge, gnomebreakpad, canberra-gtk-module

Memory status: size: 89088000 vsize: 89088000 resident: 26349568 share: 19226624 rss: 26349568 rss_rlim: 18446744073709551615
CPU usage: start_time: 1260210161 rtime: 483 utime: 443 stime: 40 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]
0x0f2cc500 in waitpid () from /lib/libpthread.so.0

+ Trace 219483

Thread 1 (Thread 0x48057250 (LWP 29096))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_assertion_message
from /lib/libglib-2.0.so.0
#8 g_assertion_message_expr
from /lib/libglib-2.0.so.0
#9 ??
from /usr/lib/libORBit-2.so.0
#10 PortableServer_POA_servant_to_reference
from /usr/lib/libORBit-2.so.0
#11 ??
from /usr/lib/libbonobo-2.so.0
#12 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#13 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_object_new
from /usr/lib/libgobject-2.0.so.0
#15 spi_accessible_construct
from /usr/lib/libspi.so.0
#16 spi_accessible_new
from /usr/lib/libspi.so.0
#17 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#18 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#19 ??
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 ??
from /usr/lib/libatk-1.0.so.0
#23 g_cclosure_marshal_VOID__PARAM
from /usr/lib/libgobject-2.0.so.0
#24 ??
from /usr/lib/libgobject-2.0.so.0
#25 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#26 ??
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#29 ??
from /usr/lib/libgobject-2.0.so.0
#30 ??
from /usr/lib/libgobject-2.0.so.0
#31 g_object_notify
from /usr/lib/libgobject-2.0.so.0
#32 atk_object_set_name
from /usr/lib/libatk-1.0.so.0
#33 ??
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgobject-2.0.so.0
#35 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#36 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#37 g_object_new
from /usr/lib/libgobject-2.0.so.0
#38 gtk_message_dialog_new
from /usr/lib/libgtk-x11-2.0.so.0
#39 ??
#40 ??
from /usr/lib/libORBit-2.so.0
#41 ??
from /usr/lib/libORBit-2.so.0
#42 ??
from /usr/lib/libORBit-2.so.0
#43 link_connection_state_changed
from /usr/lib/libORBit-2.so.0
#44 link_connection_exec_disconnect
from /usr/lib/libORBit-2.so.0
#45 ??
from /usr/lib/libORBit-2.so.0
#46 link_exec_command
from /usr/lib/libORBit-2.so.0
#47 link_connection_disconnect
from /usr/lib/libORBit-2.so.0
#48 giop_connection_close
from /usr/lib/libORBit-2.so.0
#49 ??
from /usr/lib/libORBit-2.so.0
#50 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#51 link_connections_close
from /usr/lib/libORBit-2.so.0
#52 giop_shutdown
from /usr/lib/libORBit-2.so.0
#53 CORBA_ORB_shutdown
from /usr/lib/libORBit-2.so.0
#54 CORBA_ORB_destroy
from /usr/lib/libORBit-2.so.0
#55 ??
from /usr/lib/libORBit-2.so.0
#56 ??
from /lib/libc.so.6
#57 exit
from /lib/libc.so.6
#58 ??
from /usr/lib/libgdk-x11-2.0.so.0
#59 ??
from /usr/lib/libbonoboui-2.so.0
#60 _XError
from /usr/lib/libX11.so.6
#61 ??
from /usr/lib/libX11.so.6
#62 _XEventsQueued
from /usr/lib/libX11.so.6
#63 _XFlush
from /usr/lib/libX11.so.6
#64 XFlush
from /usr/lib/libX11.so.6
#65 gdk_display_flush
from /usr/lib/libgdk-x11-2.0.so.0
#66 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#67 ??
from /usr/lib/libgtk-x11-2.0.so.0
#68 ??
from /usr/lib/libgdk-x11-2.0.so.0
#69 ??
from /lib/libglib-2.0.so.0
#70 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#71 ??
from /lib/libglib-2.0.so.0
#72 g_main_loop_run
from /lib/libglib-2.0.so.0
#73 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#74 main

A debugging session is active.

	Inferior 1 [process 29096] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** Gdk **: gdk_x11_colormap_foreign_new: assertion `GDK_IS_VISUAL (visual)' failed 


----------- .xsession-errors ---------------------
(gnome-panel:29096): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24
(gnome-panel:29096): Gdk-CRITICAL **: gdk_x11_colormap_foreign_new: assertion `GDK_IS_VISUAL (visual)' failed
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadPixmap (invalid Pixmap parameter)'.
  (Details: serial 5567 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)
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2009-12-07 19:27:14 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 597914 ***