Bug 459754 – 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 459754 - 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-07-23 23:43 UTC by mpajoh
Modified:	2007-07-24 00:42 UTC

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

Description mpajoh 2007-07-23 23:43:10 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.22.1-27.fc7 #1 SMP Tue Jul 17 17:19:58 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Nuvola

Memory status: size: 331202560 vsize: 331202560 resident: 35291136 share: 25985024 rss: 35291136 rss_rlim: 18446744073709551615
CPU usage: start_time: 1185234161 rtime: 15 utime: 12 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 46912496417200 (LWP 4048)]
(no debugging symbols found)
0x000000338a20d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 150109

Thread 1 (Thread 46912496417200 (LWP 4048))

#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 /lib64/libglib-2.0.so.0
#6 g_log
from /lib64/libglib-2.0.so.0
#7 g_assert_warning
from /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 /lib64/libglib-2.0.so.0
#24 g_cclosure_marshal_VOID__ENUM
from /lib64/libglib-2.0.so.0
#25 g_main_loop_run
from /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

Comment 1 Susana 2007-07-24 00:42:57 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 ***