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 509159 - crash in Home Folder: While attempting to umou...
crash in Home Folder: While attempting to umou...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-13 15:53 UTC by David Ayers
Modified: 2008-01-13 23:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description David Ayers 2008-01-13 15:53:22 UTC
What were you doing when the application crashed?
While attempting to umount a USB disk via GNOME's context menu, it prompted be to empty the trash.  I don't remember moving anything into the trash so I opened the trash, noticed 2 files (possibly a file and a folder).  I used the context menu in the Trash's content window to select the "properties" of the file (named Spybod S&D V1.2) and that's when the crash occurred. 

During this time Pidgeon was running and the chat window (with David Wetzel) was closed.



Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 75399168 vsize: 75399168 resident: 20156416 share: 12992512 rss: 20156416 rss_rlim: 4294967295
CPU usage: start_time: 1200203781 rtime: 445 utime: 406 stime: 39 cutime:10 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e296b0 (LWP 3844)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6e296b0 (LWP 3844))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (6 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x300003c festgelegt für 0x3000515 (David Wetz).
DOUBLE-CLICK: 400 --> -1 THRESHOLD: 8 --> -1 closing
closing
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x3e festgelegt für 0xe0073b ().
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
(nautilus:3844): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Fehler in Zeile 1: Zeichen » « ist in einem Entitätsnamen ungültig
(nautilus:3844): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Fehler in Zeile 1: Zeichen » « ist in einem Entitätsnamen ungültig
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-13 23:19:46 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 355018 ***