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 483956 - crash in Open Folder: No me deja abrir como us...
crash in Open Folder: No me deja abrir como us...
Status: RESOLVED DUPLICATE of bug 485771
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-06 00:36 UTC by lemac
Modified: 2007-10-19 02:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description lemac 2007-10-06 00:36:38 UTC 
Version: 2.18.3

What were you doing when the application crashed?
No me deja abrir como user las propiedades de un HD montado en el escritorio


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.3 2007-08-03 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-gentoo #5 SMP Tue May 22 15:59:33 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango

Memory status: size: 351879168 vsize: 351879168 resident: 38248448 share: 22482944 rss: 38248448 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191630927 rtime: 109 utime: 101 stime: 8 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)
0x00002b100bae6a1f in waitpid () from /lib/libpthread.so.0

+ Trace 168178

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib/libc.so.6
  • #4 ??
  • #5 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #6 ??
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 ??
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 nautilus_file_emit_changed
  • #22 nautilus_directory_emit_change_signals
  • #23 emit_change_signals_for_all_files
  • #24 ??
  • #25 Nautilus_MetafileMonitor_metafile_ready
  • #26 ??
  • #27 ??
  • #28 ??
    from /usr/lib/libeel-2.so.2
  • #29 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #30 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #31 ??
    from /usr/lib/libglib-2.0.so.0
  • #32 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #33 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 main 


----------- .xsession-errors (6 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Christian Kirbach 2007-10-13 00:24:39 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 André Klapper 2007-10-19 02:02:44 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 485771 ***