Bug 462181 – crash in Open Folder: tried to access bluetoot...

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 462181 - crash in Open Folder: tried to access bluetoot...


Summary:	crash in Open Folder: tried to access bluetoot...


Status:	RESOLVED DUPLICATE of bug 369824

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-31 15:46 UTC by mah
Modified:	2007-08-06 14:56 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description mah 2007-07-31 15:46:06 UTC

Version: 2.18.1

What were you doing when the application crashed?
tried to access bluetooth device sony ericson K750i


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 77647872 vsize: 77647872 resident: 28364800 share: 14114816 rss: 28364800 rss_rlim: 4294967295
CPU usage: start_time: 1185887122 rtime: 17688 utime: 16736 stime: 952 cutime:11 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227048768 (LWP 3810)]
[New Thread -1276937328 (LWP 12442)]
(no debugging symbols found)
0xb7ef47f2 in ?? () from /lib/ld-linux.so.2

+ Trace 151848

Thread 2 (Thread -1276937328 (LWP 12442))

#0 ??
from /lib/ld-linux.so.2
#1 __waitpid_nocancel
from /lib/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /lib/ld-linux.so.2
#5 raise
from /lib/i686/cmov/libc.so.6
#6 abort
from /lib/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_file_operations_empty_trash
#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/i686/cmov/libpthread.so.0
#32 clone
from /lib/i686/cmov/libc.so.6



----------- .xsession-errors (6 sec old) ---------------------
process 3810: arguments to dbus_message_iter_append_fixed_array() were incorrect, assertion "n_elements >= 0" failed in file dbus-message.c line 2304.
This is normally a bug in some application using the D-Bus library.
libgnomevfs-ERROR **: Out of memory
aborting...
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------

Comment 1 Susana 2007-08-06 14:56:34 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 ***