Bug 409867 – crash in Open Folder: tentando montar a parti??...

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 409867 - crash in Open Folder: tentando montar a parti??...


Summary:	crash in Open Folder: tentando montar a parti??...


Status:	RESOLVED DUPLICATE of bug 358172

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:	2007-02-20 03:49 UTC by neylorsousa
Modified:	2007-03-13 20:35 UTC

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

Description neylorsousa 2007-02-20 03:49:03 UTC

What were you doing when the application crashed?
tentando montar a partição hda1 na pasta kurumim que fica no caminho /home/neylor/kurumim/


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

Memory status: size: 110714880 vsize: 0 resident: 110714880 share: 0 rss: 28774400 rss_rlim: 0
CPU usage: start_time: 1171942633 rtime: 0 utime: 462 stime: 0 cutime:420 cstime: 0 timeout: 42 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 -1227147600 (LWP 4539)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 112187

Thread 1 (Thread -1227147600 (LWP 4539))

#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 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 nautilus_file_is_directory
#11 nautilus_file_is_directory
#12 nautilus_file_get_uri
#13 nautilus_file_get_uri
#14 nautilus_file_ref
#15 nautilus_directory_async_state_changed
#16 nautilus_directory_async_state_changed
#17 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
from /usr/lib/libglib-2.0.so.0
#24 ??
#25 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#26 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#28 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#29 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#30 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#31 POA_Nautilus_MetafileMonitor__init
#32 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#33 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-02-20 17:16:20 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-03-13 20:35:21 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 358172 ***