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 505841 - crash in Open Folder: trying to browse a folde...
crash in Open Folder: trying to browse a folde...
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 505840 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-12-27 02:48 UTC by atrvarma
Modified: 2008-02-06 10:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description atrvarma 2007-12-27 02:48:59 UTC
Version: 2.18.1

What were you doing when the application crashed?
trying to browse a folder in another partition mounted under "/" after the earlier attempt crashed,and when a new browser window opened automatically


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.21.2 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.20.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 102641664 vsize: 102641664 resident: 31756288 share: 18178048 rss: 31756288 rss_rlim: 4294967295
CPU usage: start_time: 1198723358 rtime: 2113 utime: 1935 stime: 178 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 -1209026848 (LWP 3095)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209026848 (LWP 3095))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 ??
  • #11 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #13 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #16 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 g_cclosure_marshal_VOID__BOXED
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /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 ??
  • #26 ??
  • #27 ??
  • #28 g_cclosure_marshal_VOID__ENUM
    from /lib/libglib-2.0.so.0
  • #29 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #30 g_cclosure_marshal_VOID__ENUM
    from /lib/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #32 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 main
  • #0 __kernel_vsyscall

Comment 1 Cosimo Cecchi 2007-12-27 10:01:16 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 Cosimo Cecchi 2007-12-27 10:01:40 UTC
*** Bug 505840 has been marked as a duplicate of this bug. ***
Comment 3 Akhil Laddha 2008-02-06 10:16:23 UTC
*** Bug 508835 has been marked as a duplicate of this bug. ***