Bug 734922
| Summary: | [abrt] gvfs-smb-1.9.4-1.fc16: cli_trans_recv: Process /usr/libexec/gvfsd-smb was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Nikolay Vladimirov <accounts> | ||||||
| Component: | gvfs | Assignee: | Tomáš Bžatek <tbzatek> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 16 | CC: | alexl, asearcherforever, bnocera, chmelarz, jonathanjstevens, marcosfrm, martijn.van.buul, nicolas, tbzatek, tsmetana | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:daa0b607cf7644fddc7d5f99e88330b5d2103b57 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-10-30 07:09:46 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Nikolay Vladimirov
2011-08-31 21:01:48 UTC
Created attachment 520902 [details]
File: maps
Created attachment 520903 [details]
File: backtrace
Package: gvfs-smb-1.9.4-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- trying to open samba share on nautilus Package: gvfs-smb-1.9.5-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- What happened: Problem occured after the attempt to access Samba shares. When the login credentials for samba share access are filled out, this error pops up and Nautilus is loading the content of the samba share directory for long time without any success. How to reproduce: 1. Open Nautilus to browse files 2. Chose "Connect to server" from the menu (under "file") 3. Fill IP address of the remote Samba server 4. Chose "Windows Shares" as a type of connection and click "Connect" button 5. List of shares will be listed 6. Access one of the shared folders (with required user authentication) I didn't test it with shared folder where login is not required (I don't have such share available) Tested with Fedora 16 RC2 (published on Sep 24) Affected (killed) processes: gvfsd-smb gvfsd-smb-browse Problem persists gvfs-smb-1.10.0-1.fc16.x86_64 Package: gvfs-smb-1.10.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- I just tried to mount a SMB share from a F15 machine (without password) in Nautilus. When I double click the share name, it crashes. https://bugzilla.gnome.org/show_bug.cgi?id=654999 Related? It's fixed in 1.11.0. I'm using: gvfs-smb-1.10.1-1.fc16.x86_64 and mounting samba shares is working fine. Not closing this since it was reported in #comment6 that this is still broken. Weird. I just perform a yum update using updates-testing and the bug is gone. Now it is mouting my Windows shares normally. I think there's someting releted to the recent glibc breakage, just guessing... So for me you can close the bug. I just tried to report a bug on f16 RC5, and it linked to this report. However, I'm using 1.10.10-2.fc16.x86_64... Should this be reopened? I no longer experience crashes, but some problem still remains. Sometimes all works fine and then sometimes mount doesn't complete and end with a timeout error in Nautilus. Didn't find a reproducible test case to trigger that. it's pretty consistent for me... it's pretty consistent for me... Problem still occurs for me, F16 RC5. Problem seems to have gone away after updating libsmbclient This error just popped up for me running a fresh copy of Fedora 16 (stock from live CD). The bug reported did not append this information. I don't seem to be able to upload an attachment or I'd include it myself. |