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 512110 - crash in File Browser:
crash in File Browser:
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-01-25 18:49 UTC by emiliano.parrinello
Modified: 2008-01-27 14:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description emiliano.parrinello 2008-01-25 18:49:01 UTC 
Version: 2.18.3

What were you doing when the application crashed?



Distribution: PCLinuxOS release 2007 (PCLinuxOS) for i586
Gnome Release: 2.18.0 2007-09-08 (%vendor)
BugBuddy Version: 2.20.1

System: Linux 2.6.22.10.tex1 #1 SMP Thu Oct 11 09:44:19 WST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Ro_Dream

Memory status: size: 86593536 vsize: 86593536 resident: 31236096 share: 18784256 rss: 31236096 rss_rlim: 4294967295
CPU usage: start_time: 1201286767 rtime: 120 utime: 110 stime: 10 cutime:1 cstime: 2 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/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227979072 (LWP 5123)]
(no debugging symbols found)
0xb7fc0410 in __kernel_vsyscall ()

+ Trace 186802

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

Thread 1 (Thread -1227979072 (LWP 5123)):
#-1 0xb7fc0410 in __kernel_vsyscall ()
No symbol table info available.


----------- .xsession-errors ---------------------
alarm-queue.c:200 (queue_midnight_refresh) - Refresh at Sat Jan 26 01:00:00 2008
 
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///root/.evolution/calendar/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///root/.evolution/calendar/local/system - Calendar Open Async... 0x80aed70
alarm-notify.c:220 (load_calendars) - Loading Calendar contacts:/// 
alarm-notify.c:462 (alarm_notify_add_calendar) contacts:/// - Calendar Open Async... 0x80bcad0
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///root/.evolution/tasks/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///root/.evolution/tasks/local/system - Calendar Open Async... 0x80bccc0
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///root/.evolution/memos/local/system 
alarm-n
** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
Backtrace limit of 200 exceeded
Backtrace limit of 200 exceeded
Backtrace limit of 200 exceeded
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-27 14:55:50 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 ***