| Summary: | [abrt] Thunar-1.3.0-4.fc16: Process /usr/bin/Thunar was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Henry Pfeil <hpfeil> | ||||||||
| Component: | Thunar | Assignee: | Kevin Fenzi <kevin> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | cwickert, kevin, maxamillion, pertusus | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:6bdeb7dca6fb4f05d126a501f9f1af6eb58703e8 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-01-05 18:56:32 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Henry Pfeil
2012-01-05 13:07:26 UTC
Created attachment 550894 [details]
File: dso_list
Created attachment 550895 [details]
File: maps
Created attachment 550896 [details]
File: backtrace
Thunar shouldn't strickly require gvfs... but it looks like it's trying to do something with the trash. Do you have a trash icon enabled in the desktop? If you disable it does it work? Does this crash happen everytime, or is it sporadic? Every time I opened Thunar, either with exo-open or /usr/bin. Gvfs is now gone and so is this bug. I don't recall what I did yesterday in an attempt to stop gvfs and kdeinit4, and all which that entails. Ssh from a terminal window to another node in the cluster, pure text, so gnome and kde have no business starting up. Probably inherited the environment vars from the base login into the ssh session. My admin paradigm is to stop reading the manual as soon as something works, instead of checking every possible option in the config files for optimal settings. I no longer use sshfs-fuse, but neglected to expunge those packages once I got nfs and ssh working. I'm changing the status to closed/notabug. Someday I'd like to figure out what I did to generate that SIGSEGV. I apologise for submitting this pseudo-bug when the problem was the person using the mouse and keyboard. ;-> |