Bug 354065 – crash in Shared Folders:

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 354065 - crash in Shared Folders:


Summary:	crash in Shared Folders:


Status:	RESOLVED DUPLICATE of bug 351376

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-03 02:11 UTC by arons
Modified:	2006-09-03 10:53 UTC

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

Description arons 2006-09-03 02:11:41 UTC

Version: 2.15.2

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 77959168 vsize: 0 resident: 77959168 share: 0 rss: 12267520 rss_rlim: 0
CPU usage: start_time: 1157249458 rtime: 0 utime: 67 stime: 0 cutime:62 cstime: 0 timeout: 5 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 -1225455424 (LWP 5792)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71460

Thread 1 (Thread -1225455424 (LWP 5792))

#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 ??
#5 ??
#6 ??
#7 ??
#8 ??
from /usr/lib/libgtk-x11-2.0.so.0
#9 ??
#10 ??
#11 ??
#12 gtk_window_set_title
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
#14 ??
#15 _IO_stdin_used
#16 ??
#0 __kernel_vsyscall

Comment 1 Brent Smith (smitten) 2006-09-03 04:52:18 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Christian Kirbach 2006-09-03 10:53:10 UTC

actually a duplicate

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