Bug 559046

Summary: [abrt] crash in Miro-2.5.4-1.fc12
Product: [Fedora] Fedora Reporter: Alexey Kuznetsov <axet>
Component: MiroAssignee: Alex Lancaster <alex>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: alex, michel
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:40ebb83e695bb30a1be544cf421f4fce2e74359f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-18 19:07:17 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 Alexey Kuznetsov 2010-01-27 00:38:41 UTC 
abrt 1.0.4 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/miro.real
component: Miro
executable: /usr/bin/python
kernel: 2.6.31.9
package: Miro-2.5.4-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)
Comment 1 Alexey Kuznetsov 2010-01-27 00:38:46 UTC 
Created attachment 386951 [details]
File: backtrace
Comment 2 Alex Lancaster 2010-01-27 00:55:25 UTC 
Could you describe what you were don't at the time of the crash?  It's difficult to fix if you can't reproduce the bug reliably.  Thanks.
Comment 3 Alexey Kuznetsov 2010-01-27 02:41:32 UTC 
this is happens once per month. i do not know how to reproduce it.
Comment 4 Alex Lancaster 2010-07-18 08:48:07 UTC 
Reporter: can you still reproduce this in the current version of Miro: 3.0.2?  If not, or if I don't hear a response within 1 week, I'll close this bug.  If you can reproduce you're always free to re-open it.
Comment 5 Alexey Kuznetsov 2010-07-18 15:56:04 UTC 
seems ok
Comment 6 Alex Lancaster 2010-07-18 19:07:17 UTC 
(In reply to comment #5)
> seems ok    

Thanks, closing bug.  Feel free to re-open if you can reproduce this particular
bug.