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 534963 - crash in File Browser: open red
crash in File Browser: open red
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-05-26 19:26 UTC by j-badi
Modified: 2008-05-26 22:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description j-badi 2008-05-26 19:26:48 UTC 
Version: 2.20.0

What were you doing when the application crashed?
open red


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (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: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 74825728 vsize: 74825728 resident: 27541504 share: 16314368 rss: 27541504 rss_rlim: 4294967295
CPU usage: start_time: 1211829895 rtime: 663 utime: 625 stime: 38 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 0xb6b52720 (LWP 3002)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 198710

Thread 1 (Thread 0xb6b52720 (LWP 3002))

  • #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 (22 sec old) ---------------------
Advertencia del gestor de ventanas: Ocurrió un error al leer el archivo de sesión guardado /home/jose/.metacity/sessions/default0.ms: Failed to open file '/home/jose/.metacity/sessions/default0.ms':
Initializing gnome-mount extension
seahorse nautilus module initialized
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
Initializing gnome-mount extension
seahorse nautilus module initialized
** (nautilus:3002): WARNING **: Hit unhandled case 24 (Operación no permitida) in fm_report_error_setting_permissions
** (nautilus:3002): WARNING **: Hit unhandled case 24 (Operación no permitida) in fm_report_error_setting_permissions
** (nautilus:3002): WARNING **: Hit unhandled case 24 (Operación no permitida) in fm_report_error_setting_permissions
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-26 22:17:22 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 ***