Bug 436436 – crash in Home Folder: pasava un fitxer a trave...

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 436436 - crash in Home Folder: pasava un fitxer a trave...


Summary:	crash in Home Folder: pasava un fitxer a trave...


Status:	RESOLVED DUPLICATE of bug 369824

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-05-06 20:25 UTC by pepeberenguer
Modified:	2007-05-07 20:16 UTC

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

Description pepeberenguer 2007-05-06 20:25:48 UTC

What were you doing when the application crashed?
pasava un fitxer a traves de la xarxa desde el ordinador conectat al router per cable de red fins al portàtil que ho fa per wifi


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

Memory status: size: 86990848 vsize: 0 resident: 86990848 share: 0 rss: 30408704 rss_rlim: 0
CPU usage: start_time: 1178481637 rtime: 0 utime: 1642 stime: 0 cutime:1535 cstime: 0 timeout: 107 it_real_value: 0 frequency: 197

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 -1226742096 (LWP 4982)]
[New Thread -1289688160 (LWP 5476)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 132770

Thread 2 (Thread -1289688160 (LWP 5476))

#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 gnome_vfs_daemon_message_iter_append_file_info
from /usr/lib/libgnomevfs-2.so.0
#10 gnome_vfs_daemon_message_iter_append_file_info
from /usr/lib/libgnomevfs-2.so.0
#11 gnome_vfs_daemon_message_iter_append_file_info
from /usr/lib/libgnomevfs-2.so.0
#12 gnome_vfs_find_directory
from /usr/lib/libgnomevfs-2.so.0
#13 gnome_vfs_write_cancellable
from /usr/lib/libgnomevfs-2.so.0
#14 gnome_vfs_write
from /usr/lib/libgnomevfs-2.so.0
#15 gnome_vfs_xfer_delete_list
from /usr/lib/libgnomevfs-2.so.0
#16 gnome_vfs_xfer_delete_list
from /usr/lib/libgnomevfs-2.so.0
#17 gnome_vfs_xfer_delete_list
from /usr/lib/libgnomevfs-2.so.0
#18 gnome_vfs_xfer_uri
from /usr/lib/libgnomevfs-2.so.0
#19 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#26 ??
#27 nautilus_directory_ref
#28 gnome_vfs_async_set_job_limit
from /usr/lib/libgnomevfs-2.so.0
#29 g_thread_pool_push
from /usr/lib/libglib-2.0.so.0
#30 g_thread_create_full
from /usr/lib/libglib-2.0.so.0
#31 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#32 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 Christian Kirbach 2007-05-07 20:16:24 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 369824 ***