Bug 342778 – nautilus crash with fm view

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 342778 - nautilus crash with fm view


Summary:	nautilus crash with fm view


Status:	RESOLVED DUPLICATE of bug 339605

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

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-05-24 09:11 UTC by oll
Modified:	2006-07-27 09:50 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description oll 2006-05-24 09:11:42 UTC

Distribution: Fedora Core release 5 (Bordeaux)
Package: nautilus
Severity: Normal
Version: GNOME2.14.1 2.14.1
Gnome-Distributor: Red Hat, Inc
Synopsis: nautilus crash with fm view
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.14.1
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
It just happens once.


Debugging Information:

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)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208681744 (LWP 10675)]
[New Thread -1211057248 (LWP 10713)]
(no debugging symbols found)
0x00970410 in __kernel_vsyscall ()

+ Trace 68409

Thread 1 (Thread -1208681744 (LWP 10675))

#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 g_str_hash
from /usr/lib/libglib-2.0.so.0
#5 g_hash_table_lookup
from /usr/lib/libglib-2.0.so.0
#6 nautilus_file_get_uri
#7 nautilus_file_get_uri
#8 nautilus_directory_async_state_changed
#9 nautilus_directory_async_state_changed
#10 egg_recent_item_unref
#11 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#12 ??
#13 nautilus_marshal_BOOLEAN__POINTER
#14 nautilus_marshal_BOOLEAN__POINTER
#15 eel_read_entire_file_async
from /usr/lib/libeel-2.so.2
#16 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#17 g_list_remove_link
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#20 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#21 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#22 POA_Nautilus_MetafileMonitor__init
#23 __libc_start_main
from /lib/libc.so.6
#24 ??





------- Bug created by bug-buddy at 2006-05-24 09:11 -------


Unknown version 2.14.1 in product nautilus.  Setting version to "2.14.x".

Comment 1 Fabio Bonelli 2006-05-24 09:30:01 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 with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Fabio Bonelli 2006-07-27 09:50:43 UTC

Please use bug 339605 if you can get us a stack trace with debugging symbols, thank you!

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