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 482917 - crash in Open Folder: Going up a directory/fol...
crash in Open Folder: Going up a directory/fol...
Status: RESOLVED DUPLICATE of bug 461139
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-03 12:12 UTC by elevasinen
Modified: 2007-10-21 16:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description elevasinen 2007-10-03 12:12:56 UTC
Version: 2.18.3

What were you doing when the application crashed?
Going up a directory/folder using the button (not back or backspace or up but the button like folder A button | Folder B button | Folder C button and clicking on Folder B) then rapidly trying to enter a new directory/folder


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

System: Linux 2.6.18-3-k7 #1 SMP Mon Dec 4 17:23:11 UTC 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Industrial

Memory status: size: 97931264 vsize: 97931264 resident: 33402880 share: 12505088 rss: 33402880 rss_rlim: 4294967295
CPU usage: start_time: 1190850403 rtime: 27220 utime: 24970 stime: 2250 cutime:0 cstime: 21 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 -1226594112 (LWP 579)]
(no debugging symbols found)
0xb7673bf1 in __waitpid_nocancel () from /lib/libpthread.so.0

Thread 1 (Thread -1226594112 (LWP 579))

  • #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 fm_tree_model_set_theme
  • #9 gtk_tree_model_unref_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 gtk_tree_model_sort_convert_iter_to_child_iter
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 gtk_tree_model_unref_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_tree_model_iter_nth_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_tree_model_iter_nth_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_tree_model_iter_nth_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_tree_model_iter_nth_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_tree_row_reference_free
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_tree_view_scroll_to_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_tree_view_set_cursor_on_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_tree_view_set_cursor
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 fm_tree_view_get_type
  • #21 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #25 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 main
  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0


----------- .xsession-errors (866333 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
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-10-21 16:56:14 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 461139 ***