Bug 493985 – crash in Panel:

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 493985 - crash in Panel:


Summary:	crash in Panel:


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-06 02:01 UTC by sdfg
Modified:	2007-11-13 09:06 UTC

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

Description sdfg 2007-11-06 02:01:04 UTC

Version: 2.18.3

What were you doing when the application crashed?



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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 37052416 vsize: 37052416 resident: 19587072 share: 16150528 rss: 19587072 rss_rlim: 4294967295
CPU usage: start_time: 1194314425 rtime: 27 utime: 22 stime: 5 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 -1208195360 (LWP 9427)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 175600

Thread 1 (Thread -1208195360 (LWP 9427))

#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_loop_run
from /lib/libglib-2.0.so.0
#32 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#33 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0)
aborting...
** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0)
aborting...
** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0)
aborting...
** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0)
aborting...
** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0)
aborting...
--------------------------------------------------

Comment 1 Vincent Untz 2007-11-13 09:06:03 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 ***