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 355034 - crash in Shared Folders:
crash in Shared Folders:
Status: RESOLVED DUPLICATE of bug 351861
Product: gnome-system-tools
Classification: Deprecated
Component: shares-admin
2.15.x
Other All
: High critical
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
Depends on:
Blocks:
 
 
Reported: 2006-09-09 00:25 UTC by joverstreet1
Modified: 2006-09-09 00:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description joverstreet1 2006-09-09 00:25:30 UTC 
Version: 2.15.4

What were you doing when the application crashed?



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

Memory status: size: 69517312 vsize: 0 resident: 69517312 share: 0 rss: 14401536 rss_rlim: 0
CPU usage: start_time: 1157761508 rtime: 0 utime: 83 stime: 0 cutime:74 cstime: 0 timeout: 9 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 -1224689472 (LWP 7145)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71926

Thread 1 (Thread -1224689472 (LWP 7145))

  • #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 gtk_window_set_title
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall 






Comment 1


Brent Smith (smitten)





          2006-09-09 00:49:54 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 351861 ***