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 303451 - removing file from burn:// folder
removing file from burn:// folder
Status: RESOLVED DUPLICATE of bug 158196
Product: nautilus
Classification: Core
Component: general
2.10.x
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-05-08 10:36 UTC by mateusza
Modified: 2005-05-08 10:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description mateusza 2005-05-08 10:36:12 UTC
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Ubuntu
Synopsis: removing file from burn:// folder
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
nautilius crashed

Steps to reproduce the crash:
1. create file "test.txt" in DVD/CD Druid
2. edit it with gedit
3. close gedit
4. move file to wastebasket
5. BANG!!!!

Expected Results:
nautilius crashed

How often does this happen?
once

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 -1223887616 (LWP 6091)]
[New Thread -1246913616 (LWP 4024)]
[New Thread -1238103120 (LWP 6125)]
[New Thread -1237836880 (LWP 6124)]
[New Thread -1237570640 (LWP 6123)]
[New Thread -1237304400 (LWP 6122)]
[New Thread -1236644944 (LWP 6120)]
[New Thread -1226302544 (LWP 6112)]
(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)
(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 8 (Thread -1226302544 (LWP 6112))

  • #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-05-08 10:36 UTC -------


Unknown version 2.10.0 in product nautilus.  Setting version to "2.10.x".
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 mateusza@staszic.waw.pl.

Comment 1 Olav Vitters 2005-05-08 10:39:42 UTC
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.

Matches stacktrace in bug 172741, duped to 158196

Also, is there any chance you could get the crash to occur again and get a stack
trace with debugging symbols (see http://live.gnome.org/GettingTraces for more
information on how to do so)?

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