Bug 423212 – crash in Home Folder: Я переписал файл с флеш-...

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 423212 - crash in Home Folder: Я переписал файл с флеш-...


Summary:	crash in Home Folder: Я переписал файл с флеш-...


Status:	RESOLVED DUPLICATE of bug 394971

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-03-27 05:26 UTC by MKondratyev85
Modified:	2007-03-31 13:17 UTC

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

Description MKondratyev85 2007-03-27 05:26:58 UTC

What were you doing when the application crashed?
Я переписал файл с флеш-носителя Kingstone на жесткий диск Maxtor FAT


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

Memory status: size: 106278912 vsize: 0 resident: 106278912 share: 0 rss: 29810688 rss_rlim: 0
CPU usage: start_time: 1174972781 rtime: 0 utime: 3690 stime: 0 cutime:3430 cstime: 0 timeout: 260 it_real_value: 0 frequency: 262

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 -1227123024 (LWP 7633)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 122523

Thread 1 (Thread -1227123024 (LWP 7633))

#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 g_type_check_is_value_type
from /usr/lib/libgobject-2.0.so.0
#5 g_value_type_compatible
from /usr/lib/libgobject-2.0.so.0
#6 g_object_class_override_property
from /usr/lib/libgobject-2.0.so.0
#7 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#9 fm_directory_view_bump_zoom_level
#10 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#13 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#14 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#15 POA_Nautilus_MetafileMonitor__init
#16 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#17 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-03-31 13:17:40 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 394971 ***