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 477549 - crash in Show Desktop: Tranferindo arquivos de ...
crash in Show Desktop: Tranferindo arquivos de ...
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-09-16 17:43 UTC by incoquinita
Modified: 2007-09-17 07:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description incoquinita 2007-09-16 17:43:55 UTC 
Version: 2.18.0

What were you doing when the application crashed?
Tranferindo arquivos de uma area de trabalho poara outra


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 36671488 vsize: 36671488 resident: 11182080 share: 7725056 rss: 11182080 rss_rlim: 4294967295
CPU usage: start_time: 1189962856 rtime: 1221 utime: 1092 stime: 129 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 -1209121056 (LWP 3402)]
(no debugging symbols found)
0x00f46402 in __kernel_vsyscall ()

+ Trace 163379

Thread 1 (Thread -1209121056 (LWP 3402))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 cairo_rectangle
    from /usr/lib/libcairo.so.2
  • #5 ??
    from /usr/lib/libwnck-1.so.18
  • #6 ??
    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 ??
    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 ??
    from /usr/lib/libwnck-1.so.18
  • #13 ??
    from /usr/lib/libwnck-1.so.18
  • #14 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #15 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #16 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #18 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #19 ??
    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 (1622 sec old) ---------------------
localuser:erick being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3222
Loading "installonlyn" plugin
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
--------------------------------------------------
Comment 1 Vincent Untz 2007-09-17 07:34:44 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 ***