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 511806 - crash in Show Desktop: I tried to add multiple ...
crash in Show Desktop: I tried to add multiple ...
Status: RESOLVED DUPLICATE of bug 403377
Product: gnome-panel
Classification: Other
Component: show-desktop-button
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-24 15:05 UTC by kaushalpatel1982
Modified: 2008-01-24 17:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description kaushalpatel1982 2008-01-24 15:05:16 UTC 
Version: 2.18.0

What were you doing when the application crashed?
I tried to add multiple webspace. I added 36 Workspace then gone to right click >> preference on workspace. I change Workspace to 1. then press close and received this message.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (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: Glossy
Icon Theme: Nuovo

Memory status: size: 46510080 vsize: 46510080 resident: 13697024 share: 9891840 rss: 13697024 rss_rlim: 4294967295
CPU usage: start_time: 1201184105 rtime: 408 utime: 367 stime: 41 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/wnck-applet'

(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 -1208658208 (LWP 2621)]
(no debugging symbols found)
0x00efc402 in __kernel_vsyscall ()

+ Trace 186634

Thread 1 (Thread -1208658208 (LWP 2621))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 wnck_workspace_get_width
    from /usr/lib/libwnck-1.so.18
  • #5 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 ??
    from /lib/libgobject-2.0.so.0
  • #7 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #8 ??
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #14 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #20 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #21 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #22 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #23 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #24 panel_applet_factory_main
    from /usr/lib/libpanel-applet-2.so.0
  • #25 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (65 sec old) ---------------------
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
animation.c: pset null at line 1688
--------------------------------------------------
Comment 1 Philip Withnall 2008-01-24 17:02:34 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 ***