Bug 487267 – crash in 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 487267 - crash in Computer:


Summary:	crash in Computer:


Status:	RESOLVED DUPLICATE of bug 454799

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-16 18:56 UTC by Roumano
Modified:	2007-10-17 01:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Roumano 2007-10-16 18:56:34 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Gentoo Base System release 2.0.0_rc4-r1
Gnome Release: 2.18.3 2007-09-22 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-gentoo-r8 #3 SMP PREEMPT Thu Jun 14 21:07:48 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 378605568 vsize: 378605568 resident: 320217088 share: 22556672 rss: 320217088 rss_rlim: 4294967295
CPU usage: start_time: 1192550770 rtime: 2443 utime: 2257 stime: 186 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1227654832 (LWP 2330)]
[New Thread -1338147952 (LWP 7359)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 170652

Thread 2 (Thread -1338147952 (LWP 7359))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#3 <signal handler called>
#4 *__GI_strstr
at strstr.c line 60
#5 search_visit_func
at nautilus-search-engine-simple.c line 221
#6 directory_visit_internal
at gnome-vfs-directory.c line 401
#7 directory_visit_internal
at gnome-vfs-directory.c line 426
#8 search_thread_func
at nautilus-search-engine-simple.c line 269
#9 g_thread_create_proxy
at gthread.c line 594
#10 start_thread
at pthread_create.c line 296
#11 clone
from /lib/libc.so.6



----------- .xsession-errors (10120 sec old) ---------------------
Watching directory /home/roumano/conduit/868/data/icons/hicolor/32x32/apps (total watches = 1785)
Watching directory /home/roumano/conduit/868/data/icons/hicolor/22x22/apps (total watches = 1786)
Watching directory /home/roumano/conduit/868/data/icons/hicolor/48x48/apps (total watches = 1787)
Watching directory /home/roumano/conduit/868/conduit/dataproviders/BackpackModule/backpack-1.1/data (total watches = 1788)
Watching directory /home/roumano/conduit/868/conduit/dataproviders/BackpackModule/backpack-1.1/cgi (total watches = 1789)
Watching directory /home/roumano/conduit/867/data/icons/hicolor/scalable/apps (total watches = 1790)
Watching directory /home/roumano/conduit/867/data/icons/hicolor/16x16/apps (total watches = 1791)
Watching directory /home/roumano/conduit/867/data/icons/hicolor/16x16/status (total watches = 1792)
Watching directory /home/roumano/conduit/867/data/icons/hicolor/16x16/actions (total watches = 1793)
Watching directory /home/roumano/conduit/867/data/icons/hicolor/32x32/apps (total watches = 1794)
Watching directory /home/roumano/conduit/867/data/icons/hicolor/22x22/apps (total watches = 1795)
Watching directory /home/roumano/conduit/867/data/icons/hicolor/48x48/apps (total watches = 1796)
Watching directory /home/roumano/conduit/867/conduit/dataproviders/BackpackModule/backpack-1.1/data (total watches = 1797)
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Christoph Wolk 2007-10-17 01:47:42 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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