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 368581 - crash in CD/DVD Creator: Pushed a button represen...
crash in CD/DVD Creator: Pushed a button represen...
Status: RESOLVED DUPLICATE of bug 356672
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-31 22:14 UTC by manmathan.kumarathurai
Modified: 2006-10-31 22:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description manmathan.kumarathurai 2006-10-31 22:14:01 UTC 
What were you doing when the application crashed?
Pushed a button representing a folder on the toolbar.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 111906816 vsize: 0 resident: 111906816 share: 0 rss: 30437376 rss_rlim: 0
CPU usage: start_time: 1162325594 rtime: 0 utime: 1916 stime: 0 cutime:1770 cstime: 0 timeout: 146 it_real_value: 0 frequency: 46

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 -1208591616 (LWP 3917)]
(no debugging symbols found)
0x00e77402 in __kernel_vsyscall ()

+ Trace 81197

Thread 1 (Thread -1208591616 (LWP 3917))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/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/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 fm_directory_view_bump_zoom_level
  • #11 gtk_tree_model_unref_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_tree_model_sort_convert_iter_to_child_iter
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_tree_model_unref_node
    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_model_iter_nth_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_tree_row_reference_free
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_tree_model_sort_new_with_model
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_tree_selection_select_range
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_tree_view_scroll_to_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_tree_view_set_cursor_on_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_tree_view_set_cursor
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 fm_directory_view_bump_zoom_level
  • #24 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #25 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #26 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #28 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 POA_Nautilus_MetafileMonitor__init
  • #30 __libc_start_main
    from /lib/libc.so.6
  • #31 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall 






Comment 1


Behdad Esfahbod





          2006-10-31 22:21:24 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. Thanks in advance!
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 367701 ***






Comment 2


Karsten Bräckelmann





          2006-10-31 22:45:13 UTC
        



Actually, it's the same as this issue...

*** This bug has been marked as a duplicate of 356672 ***