Bug 641300

Summary: [abrt] thunar-volman-0.3.80-2.fc12: raise: Process /usr/bin/thunar-volman was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Vivekanand Saraswati <vivekanand.saraswati>
Component: thunar-volmanAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: any0n3, christoph.wickert, dbuggzie, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:8bc6e119f4519137d8aa6376391980138ce05ccf
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-28 00:33:55 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 Flags
File: backtrace none

Description Vivekanand Saraswati 2010-10-08 10:46:09 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: thunar-volman --configure
component: thunar-volman
crash_function: raise
executable: /usr/bin/thunar-volman
kernel: 2.6.34.7-56.fc13.i686.PAE
package: thunar-volman-0.3.80-2.fc12
rating: 4
reason: Process /usr/bin/thunar-volman was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1286529828
uid: 500

Comment 1 Vivekanand Saraswati 2010-10-08 10:46:13 UTC
Created attachment 452315 [details]
File: backtrace

Comment 2 Michael Spahn 2010-10-08 13:29:40 UTC
Reporter, could you please describe us what you have done to get to this point, and how we can reproduce this issue here? Is there anything special about your system, network, configuration which we need to replicate here in order to reproduce your problem please?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 Michael Spahn 2010-10-14 12:03:13 UTC
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Christoph Wickert 2010-10-30 23:30:20 UTC
Vivekanand, can you please give us more info about this crash? Does the crash happen often or only rarely? Can you reproduce it reliably?

Michael, I don't think that closing the bug INSUFFICIENT_DATA is the right approach. Even if the bug reporter does not reply we do have a valid backtrace that we should forward to the upstream developers.

Comment 5 Christoph Wickert 2010-11-16 19:45:03 UTC
*** Bug 654051 has been marked as a duplicate of this bug. ***

Comment 6 Christoph Wickert 2010-11-16 19:51:23 UTC
Thanks to Dale we now have a detailed description of the bug. Copying over the relevant info form bug 654051 comment 0:

comment
-----
The crash only occured once, and I haven't been able to make it crash again. 
The program took my changes; there seems to have been no problem there.  I've
tried changing them again, but now everything works.

How to reproduce
-----
1.  I entered my preferences in the Thunar Volume Manager configuration manager
2.  Clicked on Close
3.  Thud.

Comment 7 Christoph Wickert 2010-11-28 00:33:55 UTC
I have forwarded the bug report with Dale's comments to the Xfce bugtracker at
http://bugzilla.xfce.org/show_bug.cgi?id=6888

Further investigation of this crash will take place upstream, therefor this bug will be closed now. Feel free to subscribe to the bug in the Xfce tracker to track changes. I will get back to you if I need more info and inform you once this issue is resolved in Fedora.

Thanks for reporting this bug. Big thanks to Dale for his detailed instructions.