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 302096 - Crash while trying to burn a CD
Crash while trying to burn a CD
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
2.10.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 302426 303094 304941 305851 305980 306818 307694 308507 308899 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-04-26 21:17 UTC by Manolo
Modified: 2006-01-11 23:56 UTC
See Also:
GNOME target: 2.12.x
GNOME version: 2.9/2.10



Description Manolo 2005-04-26 21:17:58 UTC
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Ubuntu
Synopsis: Crash while trying to burn a CD
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
While copying files in the CD-burner utility it has crashed

Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?
1st time

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223891712 (LWP 8443)]
[New Thread -1238053968 (LWP 8550)]
[New Thread -1237787728 (LWP 8549)]
[New Thread -1237521488 (LWP 8548)]
[New Thread -1236862032 (LWP 8547)]
[New Thread -1226523728 (LWP 8533)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 6 (Thread -1226523728 (LWP 8533))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_loop_get_context
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-26 21:17 -------


Unknown version 2.10.0 in product nautilus.  Setting version to "2.10.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was manolo@austrohungaro.com.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Olav Vitters 2005-04-29 18:08:17 UTC
*** Bug 302426 has been marked as a duplicate of this bug. ***
Comment 2 Sebastien Bacher 2005-05-05 16:22:29 UTC
*** Bug 303094 has been marked as a duplicate of this bug. ***
Comment 3 Sebastien Bacher 2005-05-05 16:22:50 UTC
Could you get the backtrace with libgnomevfs2-0-dbg nautilus-dbg installed?
Comment 4 Manolo 2005-05-05 17:16:28 UTC
No, those are not installed
Comment 5 Sebastien Bacher 2005-05-05 17:36:11 UTC
I know, the bug is not really useful without them (the backtrace has no debug
information). Can you install them and get the backtrace again?
Comment 6 Sebastien Bacher 2005-05-21 13:49:03 UTC
*** Bug 304941 has been marked as a duplicate of this bug. ***
Comment 7 Sebastien Bacher 2005-06-01 10:08:21 UTC
*** Bug 305980 has been marked as a duplicate of this bug. ***
Comment 8 Sebastien Bacher 2005-06-01 10:09:29 UTC
*** Bug 305851 has been marked as a duplicate of this bug. ***
Comment 9 Sebastien Bacher 2005-06-08 09:45:40 UTC
*** Bug 306818 has been marked as a duplicate of this bug. ***
Comment 10 Martin Wehner 2005-06-15 19:32:08 UTC
*** Bug 307694 has been marked as a duplicate of this bug. ***
Comment 11 Sebastien Bacher 2005-06-21 13:45:52 UTC
*** Bug 308507 has been marked as a duplicate of this bug. ***
Comment 12 Sebastien Bacher 2005-06-24 10:24:01 UTC
*** Bug 308899 has been marked as a duplicate of this bug. ***
Comment 13 Luis Villa 2005-07-27 14:18:50 UTC
Lots of dups; can't sit here in NEEDINFO. Reopening, confirming, setting
severity/priority correctly.
Comment 14 Alexander Larsson 2005-08-25 16:20:42 UTC
Here is a parially decoded backtrace:
  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_type_check_instance_is_a
    from /usr/lib/libgobject-2.0.so.0
  • #5 nautilus_window_open_location_full
  • #6 nautilus_window_info_open_location
    from /usr/lib/libnautilus-private.so.2
  • #7 fm-directory-view.c::open_location
  • #8 fm-directory-view.c::activate_callback
  • #9 nautilus-directory-async.c::ready_callback_call
    from /usr/lib/libnautilus-private.so.2
  • #10 nautilus-directory-async.c::call_ready_callbacks
    from /usr/lib/libnautilus-private.so.2
  • #11 nautilus_directory_async_state_changed
    from /usr/lib/libnautilus-private.so.2
  • #12 nautilus_directory_force_reload_internal
    from /usr/lib/libnautilus-private.so.2
  • #13 _gnome_vfs_job_complete
    from /usr/lib/libgnomevfs-2.so.0
  • #14 _gnome_vfs_job_complete
    from /usr/lib/libgnomevfs-2.so.0
  • #15 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #20 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 main

I'm not sure what called nautilus_directory_force_reload(). Maybe
nautilus-window-manage-views::begin_location_change(), which would be very early
in the loading of the window. However, I don't understand why this leads to
activation_callback being called. There should not have been an activation in
the newly loading window.
Comment 15 Alexander Larsson 2005-08-25 17:02:25 UTC
Seems to happen when browsing/opening folders, often on FAT/NTFS partitions
(summarizing the other bug reports).

I wonder if people are using spatial or browser when this happens. I.E. are we
opening a new window at this time, or replacing the location in the old window?
Comment 16 Alexander Larsson 2005-08-26 08:23:26 UTC
Actually, my decoding of frame #12 seems wrong. There are multiple other calls
that are more likely.
Comment 17 Alexander Larsson 2005-08-26 08:36:52 UTC
In fact, I think #12 one of these:
deep_count_callback, mime_list_callback, top_left_read_done (via
top_left_read_callback), get_info_callback, finish_info_provider
since these are callbacks from gnome-vfs that seems to fit with the rest of the
stack trace.
Comment 18 Alexander Larsson 2005-08-26 10:04:29 UTC
I don't quite understand this. It seems we're doing an activation of a file in a
window, and when gnome-vfs reports the information we need to do the activation
is there (type, mimetype, etc) the window pointer we have in the view is NULL or
invalid. 

However, I added code to close the parent window as soon as possible after an
activation, and the code handles that fine. Is the window getting corrupted
somewhere?
Comment 19 Alexander Larsson 2005-08-26 10:08:10 UTC
If anyone sees this, please describe exactly what you did. Browser or spatial,
new window or not, did the old one close? Did you get any debug output from
nautilus before it happened?
Comment 20 Alexander Larsson 2005-08-31 09:15:46 UTC
The decoded backtrace looks very much like the one in bug 314615, except it
crashes later in nautilus_window_open_location_full. Might be related.
Comment 21 Elijah Newren 2006-01-11 23:56:10 UTC
Each and every duplicate of this bug used nautilus 2.10.0 from Ubuntu.  A quick query shows that there have not been any more duplicates.  Might have been an Ubuntu specific patch, but either way this appears to be fixed now.  

I'm going to assume fixed for now (nautilus devs can correct me if I'm making an assumption they don't like here); if anyone can duplicate this with a more recent version of nautilus please feel free to reopen.