Bug 306885 – nautilus crashed and needing restarting

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 306885 - nautilus crashed and needing restarting


Summary:	nautilus crashed and needing restarting


Status:	RESOLVED DUPLICATE of bug 306143

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.10.x
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-06-08 13:30 UTC by Daniel Morgan
Modified:	2005-06-10 15:13 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description Daniel Morgan 2005-06-08 13:30:20 UTC

Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Ubuntu
Synopsis: nautilus crashed and needing restarting
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
Nautilus just crashing from what appears to be an unrelated action

Steps to reproduce the crash:
1. in terminal extracting files from archives
2. ran command mv bak.mysql.2005-05=2* ../
3. ../ would be my desktop but it popped on pressing enter from above
command

Expected Results:
Files to appear on desktop

How often does this happen?
first 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)
[Thread debugging using libthread_db enabled]
[New Thread -1223891712 (LWP 7720)]
[New Thread -1248179280 (LWP 912)]
[New Thread -1237238864 (LWP 7751)]
[New Thread -1236972624 (LWP 7750)]
[New Thread -1236706384 (LWP 7749)]
[New Thread -1236046928 (LWP 7748)]
[New Thread -1225995344 (LWP 7736)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 60703

Thread 7 (Thread -1225995344 (LWP 7736))

#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-06-08 13:30 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 Daniel.Morgan@ukds.net.

Comment 1 Sebastien Bacher 2005-06-09 14:29:29 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in
determining the cause of the crash. Can you get us one
(http://live.gnome.org/GettingTraces) with the libglib2.0-0-dbg
libgnomevfs2-0-dbg nautilus-dbg packages installed?

Comment 2 Sebastien Bacher 2005-06-10 14:43:40 UTC

do you still have this crash? 

The bug seems to be a duplicate of #306143 and a debug backtrace would make
easier to fix it...

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

Comment 3 Daniel Morgan 2005-06-10 15:13:21 UTC

I will install debug packages now and try try to cause the bug again.