Bug 368078 – crash in Computer: Moving files from one fo...

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 368078 - crash in Computer: Moving files from one fo...


Summary:	crash in Computer: Moving files from one fo...


Status:	RESOLVED DUPLICATE of bug 361427

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:	2006-10-31 04:05 UTC by d0nk@y
Modified:	2006-10-31 10:42 UTC

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

Description d0nk@y 2006-10-31 04:05:49 UTC

What were you doing when the application crashed?
Moving files from one folder to another.  Dunno exactly what crashed.


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

Memory status: size: 159490048 vsize: 0 resident: 159490048 share: 0 rss: 51843072 rss_rlim: 0
CPU usage: start_time: 1162169864 rtime: 0 utime: 8806 stime: 0 cutime:8068 cstime: 0 timeout: 738 it_real_value: 0 frequency: 1110

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226778960 (LWP 5771)]
[New Thread -1313887328 (LWP 27904)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 80795

Thread 1 (Thread -1226778960 (LWP 5771))

#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 fm_icon_view_remove_file
at fm-icon-view.c line 503
#11 nautilus_marshal_VOID__OBJECT_OBJECT
at nautilus-marshal-guts.c line 469
#12 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#17 display_pending_callback
at fm-directory-view.c line 2789
#18 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#21 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#22 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#23 main
at nautilus-main.c line 372
#24 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#25 _start
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-10-31 10:42:59 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 361427 ***