Bug 349533 – crash on Computer

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 349533 - crash on Computer


Summary:	crash on Computer


Status:	RESOLVED DUPLICATE of bug 339605

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-08-01 12:33 UTC by joram.zutt
Modified:	2006-08-01 13:42 UTC

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

Description joram.zutt 2006-08-01 12:33:28 UTC

What were you doing when the application crashed?
After minimizing evolution, I tried to start Nautilus which seem 
to have crashed. Instead of Nautilus, Bug-buddy popped up :-)


Distribution: Mandriva Linux release 2007.0 (Cooker) for i586
Gnome Release: 2.15.90 2006-07-25 (Mandriva)
BugBuddy Version: 2.15.90

Memory status: size: 80793600 vsize: 0 resident: 80793600 share: 0 rss: 21741568 rss_rlim: 0
CPU usage: start_time: 1154425872 rtime: 0 utime: 386 stime: 0 cutime:358 cstime: 0 timeout: 28 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/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 -1227925296 (LWP 3634)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 69861

Thread 1 (Thread -1227925296 (LWP 3634))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/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_source_is_destroyed
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/i686/libc.so.6
#24 ??

Comment 1 Karsten Bräckelmann 2006-08-01 13:42:25 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.


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