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 554415 - crash in File Browser: open a windows folder
crash in File Browser: open a windows folder
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-30 12:12 UTC by giancarlo.stanco
Modified: 2008-10-04 09:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description giancarlo.stanco 2008-09-30 12:12:55 UTC 
Version: 2.20.0

What were you doing when the application crashed?
open a windows folder


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 82649088 vsize: 82649088 resident: 29319168 share: 16494592 rss: 29319168 rss_rlim: 4294967295
CPU usage: start_time: 1222760307 rtime: 580 utime: 538 stime: 42 cutime:0 cstime: 0 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 0xb6b1b720 (LWP 3900)]
[New Thread 0xb6258b90 (LWP 4173)]
[New Thread 0xb50ffb90 (LWP 4109)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 207562

Thread 1 (Thread 0xb6b1b720 (LWP 3900))

  • #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 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (108 sec old) ---------------------
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
Initializing gnome-mount extension
seahorse nautilus module initialized
Initializing gnome-mount extension
seahorse nautilus module initialized
(nautilus:3900): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed
(nautilus:3900): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed
** Message: Hit unexpected error "La operación no es soportada" while doing a file operation.
** Message: Hit unexpected error "La operación no es soportada" while doing a file operation.
** (nautilus:3900): WARNING **: Hit unhandled case 5 (La operación no es soportada) in fm_report_error_setting_permissions
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-10-04 09:06:37 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 522534 ***