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 450252 - crash in Computer: The nautilus window had ...
crash in Computer: The nautilus window had ...
Status: RESOLVED DUPLICATE of bug 360750
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-23 01:56 UTC by belathus
Modified: 2007-06-23 14:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description belathus 2007-06-23 01:56:39 UTC 
What were you doing when the application crashed?
The nautilus window had been open for a while.  When activating the window again and pressing the UP button, I got this window.


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 416178176 vsize: 416178176 resident: 38010880 share: 20647936 rss: 58658816 rss_rlim: 1793285120
CPU usage: start_time: 1182143303 rtime: 1694 utime: 1360 stime: 334 cutime:3281 cstime: 328 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47200648815104 (LWP 4731)]
0x00002aedbf65ec5f in waitpid () from /lib64/libpthread.so.0

+ Trace 143042

Thread 1 (Thread 47200648815104 (LWP 4731))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 IA__g_logv
  • #6 IA__g_log
    at gmessages.c line 517
  • #7 IA__g_assert_warning
    at gmessages.c line 552
  • #8 fm_directory_view_bump_zoom_level
  • #9 gtk_tree_model_sort_convert_iter_to_child_iter
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #10 gtk_tree_model_iter_nth_child
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #11 gtk_tree_model_iter_nth_child
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #12 gtk_tree_model_iter_nth_child
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #13 gtk_tree_row_reference_free
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #14 gtk_tree_model_sort_new_with_model
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #15 gtk_tree_selection_select_range
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #16 gtk_tree_view_scroll_to_cell
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #17 gtk_tree_view_set_cursor_on_cell
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #18 fm_directory_view_bump_zoom_level
  • #19 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #20 g_main_context_iterate
    at gmain.c line 2677
  • #21 IA__g_main_loop_run
    at gmain.c line 2881
  • #22 gtk_main
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #23 POA_Nautilus_MetafileMonitor__init
  • #24 __libc_start_main
    from /lib64/libc.so.6
  • #25 g_cclosure_marshal_VOID__ENUM
    at gmarshal.c line 334
  • #26 ??
  • #27 ??
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Pedro Villavicencio





          2007-06-23 14:14:36 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 360750 ***