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 468970 - crash in Open Folder: Distribution: Fedora rel...
crash in Open Folder: Distribution: Fedora rel...
Status: RESOLVED DUPLICATE of bug 460524
Product: nautilus
Classification: Core
Component: general
2.19.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-21 19:29 UTC by Aurimas
Modified: 2007-08-21 20:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Aurimas 2007-08-21 19:29:51 UTC
Version: 2.19.5

What were you doing when the application crashed?
Distribution: Fedora release 7.90 (Rawhide)
Gnome Release: 2.19.5 2007-07-08 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23-0.61.rc1.git9.fc8 #1 SMP Tue Jul 31 17:23:22 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 95260672 vsize: 95260672 resident: 41357312 share: 27557888 rss: 41357312 rss_rlim: 4294967295
CPU usage: start_time: 1187722134 rtime: 981 utime: 825 stime: 156 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 -1208445168 (LWP 2875)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208445168 (LWP 2875))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_logv
    from /lib/libglib-2.0.so.0
  • #5 g_log
    from /lib/libglib-2.0.so.0
  • #6 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #10 ??
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_cclosure_marshal_VOID__BOXED
    from /lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #16 ??
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #19 gtk_tree_model_row_deleted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
    from /lib/libglib-2.0.so.0
  • #26 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #27 ??
    from /lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #29 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 main
  • #0 __kernel_vsyscall
  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_logv
    from /lib/libglib-2.0.so.0
  • #5 g_log
    from /lib/libglib-2.0.so.0
  • #6 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #10 ??
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_cclosure_marshal_VOID__BOXED
    from /lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #16 ??
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #19 gtk_tree_model_row_deleted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
    from /lib/libglib-2.0.so.0
  • #26 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #27 ??
    from /lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #29 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 main


----------- .xsession-errors (8 sec old) ---------------------
(nautilus:2875): Eel-WARNING **: no label on '(nil)'
(nautilus:2875): Eel-WARNING **: no label on '(nil)'
(nautilus:2875): Eel-WARNING **: no label on '(nil)'
warning: hunspell-lt-1.1-1.20070510cvs.fc8: Header V3 DSA signature: NOKEY, key ID 30c9ecf8
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** ERROR **: file nautilus-navigation-window.c: line 823 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
--------------------------------------------------
Comment 1 Susana 2007-08-21 20:56:22 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 460524 ***