Bug 478894 – crash in Panel: try to remove the applet

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 478894 - crash in Panel: try to remove the applet


Summary:	crash in Panel: try to remove the applet


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-09-21 09:48 UTC by stephan
Modified:	2007-10-11 16:16 UTC

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

Description stephan 2007-09-21 09:48:36 UTC

Version: 2.18.3

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


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.3 2007-07-19 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-gentoo-r8 #6 SMP PREEMPT Wed Aug 29 22:37:37 CST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 165253120 vsize: 165253120 resident: 24174592 share: 19886080 rss: 24174592 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190368609 rtime: 44 utime: 37 stime: 7 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)
0x00002b31fee709e5 in waitpid () from /lib/libpthread.so.0

+ Trace 164352

#0 waitpid
from /lib/libpthread.so.0
#1 ??
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 panel_profile_delete_object
#4 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#5 bonobo_closure_invoke_va_list
from /usr/lib/libbonobo-2.so.0
#6 bonobo_closure_invoke
from /usr/lib/libbonobo-2.so.0
#7 ??
from /usr/lib/libbonoboui-2.so.0
#8 ORBit_small_invoke_adaptor
from /usr/lib/libORBit-2.so.0
#9 ??
from /usr/lib/libORBit-2.so.0
#10 ??
from /usr/lib/libORBit-2.so.0
#11 ??
from /usr/lib/libORBit-2.so.0
#12 ORBit_handle_request
from /usr/lib/libORBit-2.so.0
#13 giop_connection_handle_input
from /usr/lib/libORBit-2.so.0
#14 ??
from /usr/lib/libORBit-2.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 ??
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_iteration
from /usr/lib/libglib-2.0.so.0
#18 giop_recv_buffer_get
from /usr/lib/libORBit-2.so.0
#19 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#20 Bonobo_Unknown_unref
from /usr/lib/libbonobo-activation.so.4
#21 bonobo_object_release_unref
from /usr/lib/libbonobo-2.so.0
#22 ??
#23 ??
from /usr/lib/libbonobo-2.so.0
#24 ??
from /usr/lib/libbonobo-2.so.0
#25 ??
from /usr/lib/libORBit-2.so.0
#26 giop_invoke_async
from /usr/lib/libORBit-2.so.0
#27 giop_connection_handle_input
from /usr/lib/libORBit-2.so.0
#28 ??
from /usr/lib/libORBit-2.so.0
#29 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#30 ??
from /usr/lib/libglib-2.0.so.0
#31 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#32 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#33 main



----------- .xsession-errors (14 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
(gnome-panel:31501): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 48
** (gnome-session:30857): WARNING **: Host name lookup failure on localhost.
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager;  Geben Sie die Option »--replace« an, um zu versuchen, den aktuellen Fenstermanager zu ersetzen.
--------------------------------------------------

Comment 1 Vincent Untz 2007-10-11 16:16:59 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 ***