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 353528 - crash in Shared Folders: Clicked "Share folder" i...
crash in Shared Folders: Clicked "Share folder" i...
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
: 353722 353878 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-08-30 10:45 UTC by Bernard
Modified: 2006-09-08 15:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Bernard 2006-08-30 10:45:40 UTC 
Version: 2.15.2

What were you doing when the application crashed?
Clicked "Share folder" in Nautilus.


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

Memory status: size: 68116480 vsize: 0 resident: 68116480 share: 0 rss: 11911168 rss_rlim: 0
CPU usage: start_time: 1156934842 rtime: 0 utime: 39 stime: 0 cutime:37 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 -1225066832 (LWP 6661)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71249

Thread 1 (Thread -1225066832 (LWP 6661))

  • #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 ??
  • #0 __kernel_vsyscall 






Comment 1


Christian Kirbach





          2006-08-30 20:52:40 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


Bernard





          2006-08-31 00:47:21 UTC
        



With some -dbg packages installed, this is what I get out of bug-buddy...

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

Memory status: size: 68685824 vsize: 0 resident: 68685824 share: 0 rss: 12447744 rss_rlim: 0
CPU usage: start_time: 1156984965 rtime: 0 utime: 44 stime: 0 cutime:40 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".
[Thread debugging using libthread_db enabled]
[New Thread -1224739152 (LWP 10485)]
0xffffe410 in __kernel_vsyscall ()




+
Trace
    71290






Thread 1
          (Thread -1224739152 (LWP 10485))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/tls/i686/cmov/libpthread.so.0

    

    • 

  • 
#2
libgnomeui_segv_handle

    
                at gnome-ui-init.c
                  line
                  871

    

    • 

  • 
#3
<signal handler called>

    • 

  • 
#4
??

    • 

  • 
#5
??

    • 

  • 
#6
??

    • 

  • 
#7
??

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 3


Karsten Bräckelmann





          2006-08-31 19:34:11 UTC
        



*** Bug 353722 has been marked as a duplicate of this bug. ***






Comment 4


Christian Kirbach





          2006-08-31 20:12:42 UTC
        



Unfortunately, that stack trace is not any better since we are missing some frames. what is the console output during the crash? in order to find out, please run

# gnome-session-remove nautilus
# nautilus

in a terminal and cause the crash.







Comment 5


Bernard





          2006-08-31 20:37:21 UTC
        



Nothing special:

---------------------------------------------------
bernard@bernard:~$ gnome-session-remove nautilus
Removing 'nautilus' from the session
bernard@bernard:~$ nautilus
seahorse nautilus module initialized
Initializing nautilus-open-terminal extension
** (bug-buddy:10833): WARNING **: Kon geen pictogram laden voor Map openen
glibtop: This machine has 1 CPUs, 1 are being monitored.







Comment 6


Karsten Bräckelmann





          2006-09-01 17:39:25 UTC
        



*** Bug 353878 has been marked as a duplicate of this bug. ***






Comment 7


Sebastien Bacher





          2006-09-08 15:25:11 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 351861 ***