Bug 408869 – crash in Open Folder: Tentavo di aprire un fil...

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 408869 - crash in Open Folder: Tentavo di aprire un fil...


Summary:	crash in Open Folder: Tentavo di aprire un fil...


Status:	RESOLVED DUPLICATE of bug 359350

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-17 09:56 UTC by nick
Modified:	2007-02-17 12:07 UTC

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

Description nick 2007-02-17 09:56:21 UTC

What were you doing when the application crashed?
Tentavo di aprire un file, su un hd-usb2 collegato ad una postazione windows connessa in rete, da una postazione ubuntu connessa alla stessa rete


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

Memory status: size: 147304448 vsize: 0 resident: 147304448 share: 0 rss: 41697280 rss_rlim: 0
CPU usage: start_time: 1171120804 rtime: 0 utime: 63822 stime: 0 cutime:50631 cstime: 0 timeout: 13191 it_real_value: 0 frequency: 723

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 -1226574160 (LWP 4649)]
[New Thread -1341351008 (LWP 10556)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 111457

Thread 1 (Thread -1226574160 (LWP 4649))

#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 gnome_vfs_daemon_message_iter_get_file_info
from /usr/lib/libgnomevfs-2.so.0
#11 gnome_vfs_daemon_message_iter_get_file_info
from /usr/lib/libgnomevfs-2.so.0
#12 gnome_vfs_daemon_message_iter_append_file_info
from /usr/lib/libgnomevfs-2.so.0
#13 gnome_vfs_get_file_info_uri_cancellable
from /usr/lib/libgnomevfs-2.so.0
#14 gnome_vfs_get_file_info_uri
from /usr/lib/libgnomevfs-2.so.0
#15 gnome_vfs_escape_path_string
from /usr/lib/libgnomevfs-2.so.0
#16 gnome_vfs_find_directory_cancellable
from /usr/lib/libgnomevfs-2.so.0
#17 gnome_vfs_find_directory
from /usr/lib/libgnomevfs-2.so.0
#18 eel_uri_is_trash_folder
from /usr/lib/libeel-2.so.2
#19 nautilus_file_unref
#20 fm_directory_view_bump_zoom_level
#21 fm_directory_view_bump_zoom_level
#22 fm_directory_view_bump_zoom_level
#23 fm_directory_view_bump_zoom_level
#24 fm_directory_view_update_menus
#25 fm_directory_view_bump_zoom_level
#26 g_source_get_current_time
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 André Klapper 2007-02-17 12:07:11 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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