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 608490 - crash in Panel: clic on the bubble sayin...
crash in Panel: clic on the bubble sayin...
Status: RESOLVED DUPLICATE of bug 597914
Product: gnome-panel
Classification: Other
Component: general
2.28.x
Other All
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 610390 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-01-29 22:04 UTC by marcbelfortain
Modified: 2010-02-18 19:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description marcbelfortain 2010-01-29 22:04:38 UTC
Version: 2.28.0

What were you doing when the application crashed?
clic on the bubble saying I have a new mail


Distribution: Debian squeeze/sid
Gnome Release: 2.28.2 2009-12-18 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10704000
Selinux: No
Accessibility: Enabled
GTK+ Theme: SphereCrystal
Icon Theme: gnome-alternative
GTK+ Modules: gnomebreakpad, gail:atk-bridge, canberra-gtk-module

Memory status: size: 405094400 vsize: 405094400 resident: 59224064 share: 18980864 rss: 59224064 rss_rlim: 18446744073709551615
CPU usage: start_time: 1264784899 rtime: 13511 utime: 10535 stime: 2976 cutime:0 cstime: 14 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
0x00007f56f17694de in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x7f56f48fe7d0 (LWP 22699))

  • #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 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #17 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #18 ??
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib/libatk-1.0.so.0
  • #22 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #26 ??
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_object_notify
    from /usr/lib/libgobject-2.0.so.0
  • #28 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #33 gtk_message_dialog_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 ??
  • #35 ??
    from /usr/lib/libORBit-2.so.0
  • #36 ??
    from /usr/lib/libORBit-2.so.0
  • #37 ??
    from /usr/lib/libORBit-2.so.0
  • #38 link_connection_state_changed
    from /usr/lib/libORBit-2.so.0
  • #39 link_connection_exec_disconnect
    from /usr/lib/libORBit-2.so.0
  • #40 ??
    from /usr/lib/libORBit-2.so.0
  • #41 link_exec_command
    from /usr/lib/libORBit-2.so.0
  • #42 ??
    from /usr/lib/libORBit-2.so.0
  • #43 g_object_run_dispose
    from /usr/lib/libgobject-2.0.so.0
  • #44 link_connections_close
    from /usr/lib/libORBit-2.so.0
  • #45 giop_shutdown
    from /usr/lib/libORBit-2.so.0
  • #46 CORBA_ORB_shutdown
    from /usr/lib/libORBit-2.so.0
  • #47 CORBA_ORB_destroy
    from /usr/lib/libORBit-2.so.0
  • #48 ??
    from /usr/lib/libORBit-2.so.0
  • #49 ??
    from /lib/libc.so.6
  • #50 exit
    from /lib/libc.so.6
  • #51 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #52 _XError
    from /usr/lib/libX11.so.6
  • #53 ??
    from /usr/lib/libX11.so.6
  • #54 _XEventsQueued
    from /usr/lib/libX11.so.6
  • #55 XFlush
    from /usr/lib/libX11.so.6
  • #56 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #57 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #58 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #59 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #60 ??
    from /lib/libglib-2.0.so.0
  • #61 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #62 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #63 main
A debugging session is active.

	Inferior 1 [process 22699] 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 ---------------------
** (evolution:23525): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (evolution:23525): CRITICAL **: atk_object_set_name: assertion `name != NULL' 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 1062396 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 2010-01-30 01:02:04 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 ***
Comment 2 Fabio Durán Verdugo 2010-02-18 19:44:11 UTC
*** Bug 610390 has been marked as a duplicate of this bug. ***