Bug 386858 – crash in Open Folder: Arrancando el sistema. A...

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 386858 - crash in Open Folder: Arrancando el sistema. A...


Summary:	crash in Open Folder: Arrancando el sistema. A...


Status:	RESOLVED INCOMPLETE

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:

Duplicates:	395700 396251 403051 486660 488099 546657 (view as bug list)
Depends on:
Blocks:

Reported:	2006-12-17 17:42 UTC by jsemari
Modified:	2008-08-07 08:12 UTC

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

Description jsemari 2006-12-17 17:42:47 UTC

What were you doing when the application crashed?
Arrancando el sistema. Acababa de darle el usuario y el password


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 123510784 vsize: 0 resident: 123510784 share: 0 rss: 13774848 rss_rlim: 0
CPU usage: start_time: 1166377275 rtime: 0 utime: 40 stime: 0 cutime:37 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226590544 (LWP 4766)]
[New Thread -1321239648 (LWP 4835)]
[New Thread -1312846944 (LWP 4834)]
[New Thread -1304454240 (LWP 4833)]
[New Thread -1296061536 (LWP 4832)]
[New Thread -1287668832 (LWP 4831)]
[New Thread -1279276128 (LWP 4830)]
[New Thread -1270883424 (LWP 4829)]
[New Thread -1262490720 (LWP 4828)]
[New Thread -1254098016 (LWP 4827)]
[New Thread -1243559008 (LWP 4824)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 94897

Thread 11 (Thread -1243559008 (LWP 4824))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gnome_vfs_uri_unref
from /usr/lib/libgnomevfs-2.so.0
#5 g_list_foreach
from /usr/lib/libglib-2.0.so.0
#6 gnome_vfs_uri_list_unref
from /usr/lib/libgnomevfs-2.so.0
#7 gnome_vfs_uri_list_free
from /usr/lib/libgnomevfs-2.so.0
#8 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#9 ??
#10 ??
#11 ??
#12 async_job_callback_map_destroy
from /usr/lib/libgnomevfs-2.so.0
#13 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#14 ??
#15 ??
#16 ??
#17 ??
from /usr/lib/libgnomevfs-2.so.0
#18 ??
#19 ??
#20 ??
#21 gnome_vfs_async_set_job_limit
from /usr/lib/libgnomevfs-2.so.0
#22 gnome_vfs_async_set_job_limit
from /usr/lib/libgnomevfs-2.so.0
#23 g_thread_pool_push
from /usr/lib/libglib-2.0.so.0
#24 g_thread_create_full
from /usr/lib/libglib-2.0.so.0
#25 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#26 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 palfrey 2006-12-17 20:38:42 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 André Klapper 2007-01-14 02:44:46 UTC

*** Bug 396251 has been marked as a duplicate of this bug. ***

Comment 3 André Klapper 2007-01-14 02:44:52 UTC

*** Bug 395700 has been marked as a duplicate of this bug. ***

Comment 4 Bruno Boaventura 2007-02-01 20:48:51 UTC

*** Bug 403051 has been marked as a duplicate of this bug. ***

Comment 5 Pedro Villavicencio 2007-07-30 02:46:50 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 6 Christian Kirbach 2007-10-19 22:07:05 UTC

*** Bug 488099 has been marked as a duplicate of this bug. ***

Comment 7 Christian Kirbach 2007-10-19 22:07:12 UTC

*** Bug 486660 has been marked as a duplicate of this bug. ***

Comment 8 A. Walton 2008-08-07 08:12:44 UTC

*** Bug 546657 has been marked as a duplicate of this bug. ***