Bug 356264 – crash in Computer: I opened Nautilus from t...

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 356264 - crash in Computer: I opened Nautilus from t...


Summary:	crash in Computer: I opened Nautilus from t...


Status:	RESOLVED DUPLICATE of bug 350975

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-09-16 14:07 UTC by ken solomon
Modified:	2006-09-16 14:26 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description ken solomon 2006-09-16 14:07:04 UTC

What were you doing when the application crashed?
I opened Nautilus from the desktop icon(Home) and clicked the "Up" button, the program then crashed.


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

Memory status: size: 99336192 vsize: 0 resident: 99336192 share: 0 rss: 27586560 rss_rlim: 0
CPU usage: start_time: 1158329193 rtime: 0 utime: 3816 stime: 0 cutime:3325 cstime: 0 timeout: 491 it_real_value: 0 frequency: 0

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 -1208338736 (LWP 3785)]
(no debugging symbols found)
0x00c42402 in __kernel_vsyscall ()

+ Trace 72487

Thread 1 (Thread -1208338736 (LWP 3785))

#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 /lib/libglib-2.0.so.0
#5 g_hash_table_lookup
from /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 nautilus_undo_transaction_unregister_object
#11 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#12 g_cclosure_marshal_VOID__ENUM
#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_source_is_destroyed
from /lib/libglib-2.0.so.0
#18 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#19 g_main_context_check
from /lib/libglib-2.0.so.0
#20 g_main_loop_run
from /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 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-09-16 14:26:51 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.

Also, the maintainers need more information to fix the bug. Could you please answer the questions in the other report?


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