Bug 465575 – crash in Panel: tried to remove an apple...

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 465575 - crash in Panel: tried to remove an apple...


Summary:	crash in Panel: tried to remove an apple...


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-11 02:28 UTC by Samuel Sieb
Modified:	2007-09-02 12:37 UTC

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

Description Samuel Sieb 2007-08-11 02:28:38 UTC

Version: 2.18.3

What were you doing when the application crashed?
tried to remove an applet


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.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 56451072 vsize: 56451072 resident: 33525760 share: 27844608 rss: 33525760 rss_rlim: 4294967295
CPU usage: start_time: 1185421733 rtime: 2014 utime: 1842 stime: 172 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 -1209071904 (LWP 2522)]
(no debugging symbols found)
0x00a34402 in __kernel_vsyscall ()

+ Trace 154348

Thread 1 (Thread -1209071904 (LWP 2522))

#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 ??
from /lib/libglib-2.0.so.0
#22 ??
from /usr/lib/libcairo.so.2
#23 ??
from /usr/lib/libcairo.so.2
#24 ??
from /usr/lib/libgtk-x11-2.0.so.0
#25 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libXi.so.6" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib/libasound.so.2" is not at the expected address (wrong library or version mismatch?)
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 Vincent Untz 2007-09-02 12:37:23 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 ***