Bug 608522 – crash in Panel: Solo había arrancado una...

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 608522 - crash in Panel: Solo había arrancado una...


Summary:	crash in Panel: Solo había arrancado una...


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:	2010-01-30 13:59 UTC by qdii
Modified:	2010-01-30 19:17 UTC

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

Description qdii 2010-01-30 13:59:08 UTC

Version: 2.28.0

What were you doing when the application crashed?
Solo había arrancado una sessión de Gnome. La barra de menus parecía aparecer, desaparecer, aparecer, etc.

I had just opened a Gnome session. Its menu bar kept appearing, disappearing, appearing ... as if it was trying to start (or to draw) but kept crashing and being restarted.


Distribution: Gentoo Base System release 2.0.1
Gnome Release: 2.28.2 2009-12-26 (Gentoo)
BugBuddy Version: 2.28.0

System: Linux 2.6.32-gentoo-r3 #1 SMP Sat Jan 30 10:32:43 CET 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10704000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 326651904 vsize: 326651904 resident: 45727744 share: 24387584 rss: 45727744 rss_rlim: 18446744073709551615
CPU usage: start_time: 1264859737 rtime: 29 utime: 24 stime: 5 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]
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.4-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
0x00007f714ae21f75 in waitpid () from /lib/libpthread.so.0
Current language:  auto
The current source language is "auto; currently asm".

+ Trace 220315

Thread 1 (Thread 0x7f7154118760 (LWP 8699))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib64/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 /usr/lib/libglib-2.0.so.0
#8 g_assertion_message_expr
from /usr/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 bonobo_control_frame_new
from /usr/lib/libbonoboui-2.so.0
#16 bonobo_widget_construct_control_from_objref
from /usr/lib/libbonoboui-2.so.0
#17 bonobo_widget_new_control_from_objref
from /usr/lib/libbonoboui-2.so.0
#18 panel_applet_frame_activated
#19 ??
from /usr/lib/libbonobo-activation.so.4
#20 ??
from /usr/lib/libORBit-2.so.0
#21 giop_invoke_async
from /usr/lib/libORBit-2.so.0
#22 giop_connection_handle_input
from /usr/lib/libORBit-2.so.0
#23 ??
from /usr/lib/libORBit-2.so.0
#24 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_iteration
from /usr/lib/libglib-2.0.so.0
#27 giop_recv_buffer_get
from /usr/lib/libORBit-2.so.0
#28 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#29 Bonobo_Unknown_unref
from /usr/lib/libbonobo-activation.so.4
#30 bonobo_object_release_unref
from /usr/lib/libbonobo-2.so.0
#31 bonobo_control_frame_bind_to_control
from /usr/lib/libbonoboui-2.so.0
#32 ??
from /usr/lib/libbonoboui-2.so.0
#33 ??
from /usr/lib/libORBit-2.so.0
#34 ??
from /usr/lib/libORBit-2.so.0
#35 ??
from /usr/lib/libORBit-2.so.0
#36 link_connection_state_changed
from /usr/lib/libORBit-2.so.0
#37 link_connection_exec_disconnect
from /usr/lib/libORBit-2.so.0
#38 ??
from /usr/lib/libORBit-2.so.0
#39 link_exec_command
from /usr/lib/libORBit-2.so.0
#40 ??
from /usr/lib/libORBit-2.so.0
#41 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#42 link_connections_close
from /usr/lib/libORBit-2.so.0
#43 giop_shutdown
from /usr/lib/libORBit-2.so.0
#44 CORBA_ORB_shutdown
from /usr/lib/libORBit-2.so.0
#45 CORBA_ORB_destroy
from /usr/lib/libORBit-2.so.0
#46 ??
from /usr/lib/libORBit-2.so.0
#47 __run_exit_handlers
from /lib/libc.so.6
#48 exit
from /lib/libc.so.6
#49 gdk_x_error
from /usr/lib/libgdk-x11-2.0.so.0
#50 _XError
from /usr/lib/libX11.so.6
#51 process_responses
from /usr/lib/libX11.so.6
#52 _XReply
from /usr/lib/libX11.so.6
#53 XInternAtom
from /usr/lib/libX11.so.6
#54 XGetWMColormapWindows
from /usr/lib/libX11.so.6
#55 gdk_window_add_colormap_windows
from /usr/lib/libgdk-x11-2.0.so.0
#56 _gdk_window_impl_new
from /usr/lib/libgdk-x11-2.0.so.0
#57 gdk_window_new
from /usr/lib/libgdk-x11-2.0.so.0
#58 gtk_socket_realize
from /usr/lib/libgtk-x11-2.0.so.0
#59 na_tray_child_realize
from /usr/lib64/gnome-panel/libnotification-area-applet.so
#60 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#61 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#62 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#63 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#64 gtk_widget_realize
from /usr/lib/libgtk-x11-2.0.so.0
#65 gtk_widget_set_parent
from /usr/lib/libgtk-x11-2.0.so.0
#66 gtk_box_pack
from /usr/lib/libgtk-x11-2.0.so.0
#67 tray_added
from /usr/lib64/gnome-panel/libnotification-area-applet.so
#68 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#69 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#70 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#71 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#72 na_tray_manager_window_filter
from /usr/lib64/gnome-panel/libnotification-area-applet.so
#73 gdk_event_translate
from /usr/lib/libgdk-x11-2.0.so.0
#74 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#75 gdk_event_dispatch
from /usr/lib/libgdk-x11-2.0.so.0
#76 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#77 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#78 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#79 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#80 main

A debugging session is active.

	Inferior 1 [process 8699] will be detached.

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


----------- .xsession-errors (558 sec old) ---------------------
   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.)
The program 'gnome-panel' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 2180 error_code 8 request_code 1 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.)
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2010-01-30 19:17:43 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 ***