Bug 493081 – crash in Panel: logging after adding wp_...

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 493081 - crash in Panel: logging after adding wp_...


Summary:	crash in Panel: logging after adding wp_...


Status:	RESOLVED DUPLICATE of bug 452428

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-11-03 15:44 UTC by alexandre
Modified:	2007-11-05 08:32 UTC

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

Description alexandre 2007-11-03 15:44:45 UTC

Version: 2.18.3

What were you doing when the application crashed?
logging after adding wp_tray, crash from bar, but work well on another computer


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 42401792 vsize: 42401792 resident: 24285184 share: 20525056 rss: 24285184 rss_rlim: 4294967295
CPU usage: start_time: 1194104465 rtime: 29 utime: 25 stime: 4 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 -1208895776 (LWP 17744)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 174884

Thread 1 (Thread -1208895776 (LWP 17744))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libORBit-2.so.0
#11 CORBA_any__freekids
from /usr/lib/libORBit-2.so.0
#12 ??
from /usr/lib/libORBit-2.so.0
#13 CORBA_exception_free
from /usr/lib/libORBit-2.so.0
#14 CORBA_exception_set
from /usr/lib/libORBit-2.so.0
#15 CORBA_exception_set_system
from /usr/lib/libORBit-2.so.0
#16 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#17 ORBit_small_invoke_stub_n
from /usr/lib/libORBit-2.so.0
#18 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#19 Bonobo_Control_getProperties
from /usr/lib/libbonobo-2.so.0
#20 bonobo_control_frame_get_control_property_bag
from /usr/lib/libbonoboui-2.so.0
#21 ??
#22 ??
from /usr/lib/libbonobo-2.so.0
#23 ??
from /usr/lib/libbonobo-2.so.0
#24 ??
from /usr/lib/libORBit-2.so.0
#25 giop_invoke_async
from /usr/lib/libORBit-2.so.0
#26 giop_connection_handle_input
from /usr/lib/libORBit-2.so.0
#27 ??
from /usr/lib/libORBit-2.so.0
#28 ??
from /usr/lib/libORBit-2.so.0
#29 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#30 ??
from /lib/libglib-2.0.so.0
#31 g_main_context_iteration
from /lib/libglib-2.0.so.0
#32 link_main_iteration
from /usr/lib/libORBit-2.so.0
#33 giop_recv_buffer_get
from /usr/lib/libORBit-2.so.0
#34 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#35 ORBit_small_invoke_stub_n
from /usr/lib/libORBit-2.so.0
#36 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#37 Bonobo_ActivationContext_activateMatchingFull
from /usr/lib/libbonobo-activation.so.4
#38 bonobo_activation_activate
from /usr/lib/libbonobo-activation.so.4
#39 bonobo_activation_activate_from_id
from /usr/lib/libbonobo-activation.so.4
#40 bonobo_moniker_oaf_resolve
from /usr/lib/bonobo/monikers/libmoniker_std_2.so
#41 ??
from /usr/lib/libbonobo-2.so.0
#42 g_closure_invoke
from /lib/libgobject-2.0.so.0
#43 bonobo_closure_invoke_va_list
from /usr/lib/libbonobo-2.so.0
#44 bonobo_closure_invoke
from /usr/lib/libbonobo-2.so.0
#45 ??
from /usr/lib/libbonobo-2.so.0
#46 ??
from /usr/lib/libbonobo-2.so.0
#47 _ORBIT_skel_small_Bonobo_Moniker_resolve
from /usr/lib/libbonobo-2.so.0
#48 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#49 Bonobo_Moniker_resolve
from /usr/lib/libbonobo-2.so.0
#50 bonobo_moniker_item_resolve
from /usr/lib/bonobo/monikers/libmoniker_std_2.so
#51 ??
from /usr/lib/libbonobo-2.so.0
#52 g_closure_invoke
from /lib/libgobject-2.0.so.0
#53 bonobo_closure_invoke_va_list
from /usr/lib/libbonobo-2.so.0
#54 bonobo_closure_invoke
from /usr/lib/libbonobo-2.so.0
#55 ??
from /usr/lib/libbonobo-2.so.0
#56 ??
from /usr/lib/libbonobo-2.so.0
#57 _ORBIT_skel_small_Bonobo_Moniker_resolve
from /usr/lib/libbonobo-2.so.0
#58 ??
from /usr/lib/libORBit-2.so.0
#59 ORBit_OAObject_invoke
from /usr/lib/libORBit-2.so.0
#60 ORBit_small_invoke_adaptor
from /usr/lib/libORBit-2.so.0
#61 ??
from /usr/lib/libORBit-2.so.0
#62 ??
from /usr/lib/libORBit-2.so.0
#63 ??
from /usr/lib/libORBit-2.so.0
#64 ORBit_handle_request
from /usr/lib/libORBit-2.so.0
#65 giop_connection_handle_input
from /usr/lib/libORBit-2.so.0
#66 ??
from /usr/lib/libORBit-2.so.0
#67 ??
from /usr/lib/libORBit-2.so.0
#68 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#69 ??
from /lib/libglib-2.0.so.0
#70 g_main_loop_run
from /lib/libglib-2.0.so.0
#71 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#72 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
localuser:groschat being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/17624
** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0)
aborting...
--------------------------------------------------

Comment 1 alexandre 2007-11-04 10:58:32 UTC

Ok, this happened while addind wp_tray two times. As the wp_tray takes time to setup in the gnome bar, i've added it a second time wich caused the crash. Then, add to restart the session so has gnome ask for removing this crashed gadget. Clicked yes, then, i put it back only once and it worked.

Comment 2 Christoph Wolk 2007-11-05 08:32:30 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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