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 517777 - crash in Computer: I was trying to open a d...
crash in Computer: I was trying to open a d...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-20 23:45 UTC by grunt
Modified: 2008-02-21 00:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description grunt 2008-02-20 23:45:53 UTC 
Version: 2.20.0

What were you doing when the application crashed?
I was trying to open a directory, where I had just mounted a USB device using MTP, with the mtpfs command. After running mtpfs, the directory changed from normal directory into "octet stream", wich permissions couldn't been determined. Then, when I selected "Open with another application", the application choice box started to open, and at this time the went the crash.


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-486 #1 Mon Nov 12 07:53:08 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: 74219520 vsize: 74219520 resident: 19030016 share: 11493376 rss: 19030016 rss_rlim: 4294967295
CPU usage: start_time: 1203545991 rtime: 1104 utime: 772 stime: 332 cutime:103 cstime: 46 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 0xb6bcc6c0 (LWP 3191)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 189919

Thread 1 (Thread 0xb6bcc6c0 (LWP 3191))

  • #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 g_str_equal
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
    from /usr/lib/libeel-2-2.20.so
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (16 sec old) ---------------------
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x2600710
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  18
  Minor opcode:  0
  Resource id:  0x2600710
Avertissement du gestionnaire de fenêtres : Fenêtre WM_TRANSIENT_FOR 0x47 non valide indiquée pour 0x3000007 (Informatio).
ICE default IO error handler doing an exit(), pid = 5552, errno = 0
Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600003 (Visionneur)
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(nautilus:3191): Eel-WARNING **: No extension, not implemented yet
(nautilus:3191): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-02-21 00:19:19 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 ***