Bug 483774 – 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 483774 - 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-10-05 15:03 UTC by gerard.bourzat
Modified:	2007-10-06 11:47 UTC

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

Description gerard.bourzat 2007-10-05 15:03:14 UTC

Version: 2.18.1

What were you doing when the application crashed?



Distribution: Mandriva Linux release 2007.1 (Official) for x86_64
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-15mdv #1 SMP Tue Aug 14 18:32:17 MDT 2007 x86_64
X Vendor: The X.Org Group
X Vendor Release: 6600
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gorilla
Icon Theme: Gorilla

Memory status: size: 278335488 vsize: 278335488 resident: 21311488 share: 12283904 rss: 21311488 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191596502 rtime: 19 utime: 16 stime: 3 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47297606396112 (LWP 4809)]
(no debugging symbols found)
0x00002b0452242bf4 in waitpid () from /lib64/libpthread.so.0

+ Trace 168027

Thread 1 (Thread 47297606396112 (LWP 4809))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /usr/lib64/libglib-2.0.so.0
#6 g_log
from /usr/lib64/libglib-2.0.so.0
#7 g_assert_warning
from /usr/lib64/libglib-2.0.so.0
#8 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libORBit-2.so.0
#9 CORBA_any__freekids
from /usr/lib64/libORBit-2.so.0
#10 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libORBit-2.so.0
#11 CORBA_exception_free
from /usr/lib64/libORBit-2.so.0
#12 CORBA_exception_set
from /usr/lib64/libORBit-2.so.0
#13 ORBit_small_invoke_stub
from /usr/lib64/libORBit-2.so.0
#14 Bonobo_Control_getProperties
from /usr/lib64/libbonobo-2.so.0
#15 bonobo_control_frame_get_control_property_bag
from /usr/lib64/libbonoboui-2.so.0
#16 ??
#17 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libbonobo-2.so.0
#18 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libbonobo-2.so.0
#19 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libORBit-2.so.0
#20 giop_invoke_async
from /usr/lib64/libORBit-2.so.0
#21 giop_connection_handle_input
from /usr/lib64/libORBit-2.so.0
#22 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libORBit-2.so.0
#23 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#24 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libglib-2.0.so.0
#25 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#26 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#27 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
(gnome-panel:4809): Wnck-WARNING **: Property _NET_WM_VISIBLE_NAME contained invalid UTF-8
(gnome-panel:4809): Wnck-WARNING **: Property _NET_WM_VISIBLE_NAME contained invalid UTF-8
(gnome-panel:4809): Wnck-WARNING **: Property _NET_WM_VISIBLE_NAME contained invalid UTF-8
(gnome-panel:4809): Wnck-WARNING **: Property _NET_WM_VISIBLE_NAME contained invalid UTF-8
** ERROR **: file orbit-object.c: line 149 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0)
aborting...
--------------------------------------------------

Comment 1 Susana 2007-10-06 11:47:43 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 ***