Bug 467028 – 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 467028 - crash in Panel:


Summary:	crash in Panel:


Status:	RESOLVED DUPLICATE of bug 403377

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-15 17:23 UTC by aaa
Modified:	2007-08-25 06:20 UTC

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

Description aaa 2007-08-15 17:23:09 UTC

Version: 2.18.1

What were you doing when the application crashed?



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

System: Linux 2.6.17-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Free
Icon Theme: Lush

Memory status: size: 88215552 vsize: 88215552 resident: 14127104 share: 10182656 rss: 14127104 rss_rlim: 4294967295
CPU usage: start_time: 1187198568 rtime: 33 utime: 29 stime: 4 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/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226873152 (LWP 11452)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 155443

Thread 1 (Thread -1226873152 (LWP 11452))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/libpthread.so.0
#2 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 wnck_workspace_get_width
from /usr/lib/libwnck-1.so.18
#5 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libwnck-1.so.18
#6 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#7 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#12 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgdk-x11-2.0.so.0
#15 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#16 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#19 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libglib-2.0.so.0
#20 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#21 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#22 main
#0 __kernel_vsyscall



----------- .xsession-errors (28293 sec old) ---------------------
(amule:4300): GLib-WARNING **: poll(2) failed due to: Invalid argument.
(amule:4300): GLib-WARNING **: poll(2) failed due to: Invalid argument.
(amule:4300): GLib-WARNING **: poll(2) failed due to: Invalid argument.
(amule:4300): GLib-WARNING **: poll(2) failed due to: Invalid argument.
(amule:4300): GLib-WARNING **: poll(2) failed due to: Invalid argument.
(amule:4300): GLib-WARNING **: poll(2) failed due to: Invalid argument.
(amule:4300): GLib-WARNING **: poll(2) failed due to: Invalid argument.
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Pascal Terjan 2007-08-25 06:20:40 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 403377 ***