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 520091 - crash in File Browser: accediendo al sistema de...
crash in File Browser: accediendo al sistema de...
Status: RESOLVED DUPLICATE of bug 459221
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-03 13:00 UTC by manuelcaballo
Modified: 2008-03-04 09:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description manuelcaballo 2008-03-03 13:00:51 UTC 
Version: 2.18.1

What were you doing when the application crashed?
accediendo al sistema de archivos, explorando mis carpetas personales


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-mh1-misdn #4 SMP PREEMPT Tue Feb 12 17:11:06 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 77623296 vsize: 77623296 resident: 19619840 share: 13422592 rss: 19619840 rss_rlim: 4294967295
CPU usage: start_time: 1204549033 rtime: 67 utime: 62 stime: 5 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 -1227258192 (LWP 4947)]
(no debugging symbols found)
0xb75f0321 in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 191147

Thread 1 (Thread -1227258192 (LWP 4947))

  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #8 nautilus_navigation_window_show_sidebar
  • #9 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_handler_disconnect
    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_combo_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__BOXED
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_handler_disconnect
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 gtk_tree_model_row_deleted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 nautilus_navigation_window_show_sidebar
  • #24 nautilus_directory_schedule_dequeue_pending
  • #25 nautilus_directory_async_state_changed
  • #26 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #30 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 main
  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0 






Comment 1


Cosimo Cecchi





          2008-03-04 09:16:02 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 459221 ***