Bug 462679 – crash in Panel: i cant remember

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 462679 - crash in Panel: i cant remember


Summary:	crash in Panel: i cant remember


Status:	RESOLVED DUPLICATE of bug 441520

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-08-02 04:03 UTC by hell.no.doubt
Modified:	2011-04-06 15:07 UTC

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

Description hell.no.doubt 2007-08-02 04:03:15 UTC

Version: 2.18.3

What were you doing when the application crashed?
i cant remember


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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 44519424 vsize: 44519424 resident: 9084928 share: 5922816 rss: 9084928 rss_rlim: 4294967295
CPU usage: start_time: 1186015691 rtime: 1956 utime: 836 stime: 1120 cutime:1 cstime: 9 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 -1208965408 (LWP 2461)]
(no debugging symbols found)
0x009c2402 in __kernel_vsyscall ()

+ Trace 152236

Thread 1 (Thread -1208965408 (LWP 2461))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 panel_profile_delete_object
#5 ??
from /usr/lib/libbonoboui-2.so.0
#6 g_closure_invoke
from /lib/libgobject-2.0.so.0
#7 bonobo_closure_invoke_va_list
from /usr/lib/libbonobo-2.so.0
#8 bonobo_closure_invoke
from /usr/lib/libbonobo-2.so.0
#9 ??
from /usr/lib/libbonoboui-2.so.0
#10 _ORBIT_skel_small_Bonobo_UIComponent_execVerb
from /usr/lib/libbonobo-2.so.0
#11 ??
from /usr/lib/libORBit-2.so.0
#12 ORBit_OAObject_invoke
from /usr/lib/libORBit-2.so.0
#13 ORBit_small_invoke_adaptor
from /usr/lib/libORBit-2.so.0
#14 ??
from /usr/lib/libORBit-2.so.0
#15 ??
from /usr/lib/libORBit-2.so.0
#16 ??
from /usr/lib/libORBit-2.so.0
#17 ORBit_handle_request
from /usr/lib/libORBit-2.so.0
#18 giop_connection_handle_input
from /usr/lib/libORBit-2.so.0
#19 ??
from /usr/lib/libORBit-2.so.0
#20 ??
from /usr/lib/libORBit-2.so.0
#21 ??
#22 ??
#23 ??
from /usr/lib/libORBit-2.so.0
#24 ??
#25 ??
#26 ??
#27 pthread_mutex_unlock
from /lib/libpthread.so.0
#28 ??
#29 ??
#30 ??
#0 __kernel_vsyscall



----------- .xsession-errors (22 sec old) ---------------------
warning: .dynamic section for "/usr/lib/libavahi-glib.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/librsvg-2.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgsf-1.so.114" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Iestyn Pryce 2007-08-02 19:48:31 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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

Comment 2 Fabio Durán Verdugo 2011-04-06 01:41:47 UTC

*** Bug 646844 has been marked as a duplicate of this bug. ***