Bug 358416 – crash in Shared Folders: Intentando compartir una...

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 358416 - crash in Shared Folders: Intentando compartir una...


Summary:	crash in Shared Folders: Intentando compartir una...


Status:	RESOLVED DUPLICATE of bug 358405

Product:	gnome-system-tools
Classification:	Deprecated
Component:	shares-admin
Version:	2.15.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Carlos Garnacho
QA Contact:	Carlos Garnacho

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-09-30 02:28 UTC by RaFa...eL
Modified:	2006-09-30 02:46 UTC

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

Description RaFa...eL 2006-09-30 02:28:13 UTC

Version: 2.15.4

What were you doing when the application crashed?
Intentando compartir una carpeta en un sistema FAT32.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 70684672 vsize: 0 resident: 70684672 share: 0 rss: 14266368 rss_rlim: 0
CPU usage: start_time: 1159583230 rtime: 0 utime: 49 stime: 0 cutime:45 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/shares-admin'

(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 -1225668944 (LWP 7568)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 73642

Thread 1 (Thread -1225668944 (LWP 7568))

#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 strcmp
from /lib/tls/i686/cmov/libc.so.6
#5 gtk_file_chooser_button_new
from /usr/lib/libgtk-x11-2.0.so.0
#6 gtk_file_chooser_button_new
from /usr/lib/libgtk-x11-2.0.so.0
#7 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#12 _gtk_file_chooser_set_delegate
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#18 _gtk_file_chooser_set_delegate
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#24 _gtk_file_chooser_default_new
from /usr/lib/libgtk-x11-2.0.so.0
#25 fs_module_create
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#26 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#27 ??
#28 ??
#29 ??
#30 ??
from /usr/lib/libgthread-2.0.so.0
#31 ??
#32 ??
from /usr/lib/libglib-2.0.so.0
#33 ??
#34 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#35 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#36 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#37 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#38 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#39 gtk_dialog_run
from /usr/lib/libgtk-x11-2.0.so.0
#40 ??
#41 ??
#42 ??
#43 ??
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-09-30 02:46:35 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 358405 ***