Bug 360686 – crash in Shared Folders: try ing to share a folde...

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 360686 - crash in Shared Folders: try ing to share a folde...


Summary:	crash in Shared Folders: try ing to share a folde...


Status:	RESOLVED DUPLICATE of bug 360634

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-10-08 16:56 UTC by eiersuppe
Modified:	2006-10-08 17:04 UTC

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

Description eiersuppe 2006-10-08 16:56:53 UTC

Version: 2.15.5

What were you doing when the application crashed?
try ing to share a folder


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

Memory status: size: 57413632 vsize: 0 resident: 57413632 share: 0 rss: 9715712 rss_rlim: 0
CPU usage: start_time: 1160326592 rtime: 0 utime: 11 stime: 0 cutime:9 cstime: 0 timeout: 2 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 -1225369936 (LWP 19729)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 75266

Thread 1 (Thread -1225369936 (LWP 19729))

#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 ??
from /usr/lib/liboobs-1.so.2
#5 ??
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#0 __kernel_vsyscall

Comment 1 Elijah Newren 2006-10-08 17:04:00 UTC

Thanks for the bug report. 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?


*** This bug has been marked as a duplicate of 360634 ***