Bug 606184
Summary: | [abrt] crash in Thunar-1.0.1-7.fc13: __strcmp_ssse3: Process /usr/bin/Thunar was killed by signal 11 (SIGSEGV) | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Suvayu <fatkasuvayu> | ||||||
Component: | thunar-vcs-plugin | Assignee: | Christoph Wickert <christoph.wickert> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 13 | CC: | christoph.wickert, dtdraganov, fatkasuvayu, k_a_r_l_o_, kevin, krkhan, pertusus, projects.rg, skvlnx | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | abrt_hash:653b6725528f9d7e6c2b017f1821cfff1709907f | ||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2011-05-25 19:45:24 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
Suvayu
2010-06-21 03:43:31 UTC
Created attachment 425519 [details]
File: backtrace
Created attachment 427040 [details]
backtrace
I am getting these crashes almost every other day. Hopefully this latest backtrace will add to the information needed to resolve the issue.
Let me know if more information is required.
Update to Thunar 1.0.2 which should be in updates-release already. If this doesn't help uninstall the thunar-vcs-plugin. All people who reported this bug had the vcs-plugin installed. Hi Christoph, I already had the update installed. So I have uninstalled thunar-vcs-plugin as per your suggestion. I will report back in a couple of days whether that stabilises thunar. I was getting a crash every day or two, so I am hoping that a couple of days should be enough to decide. Thanks for the response. :) Hi Kevin and Christoph, I am happy to report I have had no crashes so far. :) Looks like the vcs-plugin was the culprit. Let me know if you need any more info, or if you want me to close the bug. Thanks a lot. Christoph: Does this look like the same vcs bug as that other one thats waiting on upstream? Or do you think we should file this seperately? Reassigning to thunar-vcs-plugin. *** Bug 625312 has been marked as a duplicate of this bug. *** Package: Thunar-1.0.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Started the application and tried to open a torrent file with it. 2.I've done this before, and it worked fine, but this time vlc player was working, and the application took longer time to start, and finally crashed. 3. Package: Thunar-1.0.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. right click in thunar 2. 3. Comment ----- vcs plugin? Package: Thunar-1.0.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. use usb flash Comment ----- use usb flash (In reply to comment #11) yum remove -y thunar-vcs-plugin Does it help? Unfortunately, the crash is not always reproducable, it seems to occur randomly. Package: Thunar-1.0.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Launch Thunar. 2. Right-click on any icon. Comment ----- Thunar crashes randomly on right-click. Package: Thunar-1.0.2-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Tried to copy a file. 2.The crash happened when I right-clicked on the file and selected Copy. 3. Nothing changed here since April, so can I guess problem solved? No, otherwise the bug would probably be closed. In fact I was just too busy to look at this closely. When I did, I figured out it's a duplicate. *** This bug has been marked as a duplicate of bug 595872 *** |