Bug 373970 – crash in Computer: Surfing with fedora.

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 373970 - crash in Computer: Surfing with fedora.


Summary:	crash in Computer: Surfing with fedora.


Status:	RESOLVED DUPLICATE of bug 373730

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-11 18:44 UTC by gandroul
Modified:	2006-11-12 02:12 UTC

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

Description gandroul 2006-11-11 18:44:10 UTC

Version: 2.16.2

What were you doing when the application crashed?
Surfing with fedora.


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

System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors (25167 sec old) ---------------------
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `hu'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `fi'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `mn'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `zh_TW'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `ar'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `xh'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `nso'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `zu'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `da'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `sq'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `ja'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `ms'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from locale `sr'
Uninstalled schema `/schemas/desktop/gnome/url-handlers/mailto/enabled' from l
...Too much output, ignoring rest...
--------------------------------------------------

Memory status: size: 119533568 vsize: 0 resident: 119533568 share: 0 rss: 15761408 rss_rlim: 0
CPU usage: start_time: 1163270520 rtime: 0 utime: 70 stime: 0 cutime:56 cstime: 0 timeout: 14 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 -1208404272 (LWP 6949)]
(no debugging symbols found)
0x0068b402 in __kernel_vsyscall ()

+ Trace 85510

Thread 1 (Thread -1208404272 (LWP 6949))

#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_type_check_instance_cast
from /lib/libgobject-2.0.so.0
#5 nautilus_directory_ref
#6 nautilus_directory_async_state_changed
#7 nautilus_directory_async_state_changed
#8 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#9 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#10 g_main_context_check
from /lib/libglib-2.0.so.0
#11 g_main_loop_run
from /lib/libglib-2.0.so.0
#12 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#13 POA_Nautilus_MetafileMonitor__init
#14 __libc_start_main
from /lib/libc.so.6
#15 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-11-12 02:12:56 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 373730 ***