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 537798 - crash in File Browser: utilizar la opción "abri...
crash in File Browser: utilizar la opción "abri...
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-06-11 14:39 UTC by mettro
Modified: 2008-06-11 17:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description mettro 2008-06-11 14:39:01 UTC 
Version: 2.20.0

What were you doing when the application crashed?
utilizar la opción "abrir con" mediante el clic derecho sobre un archivo. Este archivo no tiene especificado el tipo mime.


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

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: KearonesComicons

Memory status: size: 474480640 vsize: 474480640 resident: 41439232 share: 20037632 rss: 41439232 rss_rlim: 18446744073709551615
CPU usage: start_time: 1213195075 rtime: 225 utime: 202 stime: 23 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2ae4515e2240 (LWP 10474)]
(no debugging symbols found)
0x00002ae44aad8edf in waitpid () from /lib/libpthread.so.0

+ Trace 200143

Thread 1 (Thread 0x2ae4515e2240 (LWP 10474))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 strcmp
    from /lib/libc.so.6
  • #6 g_str_equal
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
    from /usr/lib/libeel-2-2.20.so
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
  • #13 __libc_start_main
    from /lib/libc.so.6
  • #14 ??
  • #15 ??
  • #16 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
(nautilus:10474): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sjuanje\s.gnome2\snautilus-scripts\sNScripts' to action group 'ScriptsGroup'
(nautilus:10474): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sjuanje\s.gnome2\snautilus-scripts\sNScripts\sFiles' to action group 'ScriptsGroup'
(nautilus:10474): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sjuanje\s.gnome2\snautilus-scripts\sNScripts\sFiles' to action group 'ScriptsGroup'
(nautilus:10474): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sjuanje\s.gnome2\snautilus-scripts\sNScripts\sRoot' to action group 'ScriptsGroup'
(nautilus:10474): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sjuanje\s.gnome2\snautilus-scripts\sNScripts\sRoot' to action group 'ScriptsGroup'
(nautilus:10474): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sjuanje\s.gnome2\snautilus-scripts\sNScripts\sUtils' to action group 'ScriptsGroup'
(nautilus:10474): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sjuanje\s.gnome2\snautilus-scripts\sNScripts\sUtils' to action group 'ScriptsGroup'
(nautilus:10474): Eel-WARNING **: No extension, not implemented yet
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-11 17:33:54 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 ***