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 458742 - crash in Show Desktop:
crash in Show Desktop:
Status: RESOLVED DUPLICATE of bug 420713
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: 2007-07-20 18:54 UTC by Pham Tan Tien
Modified: 2007-07-21 20:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Pham Tan Tien 2007-07-20 18:54:56 UTC 
Version: 2.18.0

What were you doing when the application crashed?



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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 40407040 vsize: 40407040 resident: 8458240 share: 6676480 rss: 8458240 rss_rlim: 4294967295
CPU usage: start_time: 1184957229 rtime: 32 utime: 26 stime: 6 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208146208 (LWP 3187)]
(no debugging symbols found)
0x009bf402 in __kernel_vsyscall ()

+ Trace 149420

Thread 1 (Thread -1208146208 (LWP 3187))

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


----------- .xsession-errors (273 sec old) ---------------------
no fault of your own.
If you can reproduce the crash, please notify the Pidgin
developers by reporting a bug at
http://pidgin.im/bug.php
Please make sure to specify what you were doing at the time
and post the backtrace from the core file.  If you do not know
how to get the backtrace, please read the instructions at
http://pidgin.im/gdb.php
If you need further assistance, please IM either SeanEgn or 
LSchiere (via AIM).  Contact information for Sean and Luke 
on other protocols is at
http://pidgin.im/contactinfo.php
--------------------------------------------------
Comment 1 André Klapper 2007-07-21 20:05:08 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 420713 ***