Bug 600573

Summary: [abrt] crash in remmina-0.7.5-1.fc13: magazine_chain_pop_head: Process /usr/bin/remmina was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Raina Otoni <raina>
Component: remminaAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: christoph.wickert, splinux25
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:ad4bf21eef6f03900f407858b8d2e7e281e1922b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-08 16:25:54 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 Raina Otoni 2010-06-05 05:11:50 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: remmina
component: remmina
crash_function: magazine_chain_pop_head
executable: /usr/bin/remmina
global_uuid: ad4bf21eef6f03900f407858b8d2e7e281e1922b
kernel: 2.6.33.5-112.fc13.i686.PAE
package: remmina-0.7.5-1.fc13
rating: 4
reason: Process /usr/bin/remmina was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Raina Otoni 2010-06-05 05:11:52 UTC 
Created attachment 421402 [details]
File: backtrace
Comment 2 Fedora Admin XMLRPC Client 2010-07-22 11:54:10 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Christoph Wickert 2010-09-08 16:11:35 UTC 
Do you remember what you did when remmina crashed? Can you reproduce the crash reliably? If so, how?
Comment 4 Christoph Wickert 2010-09-08 16:25:54 UTC 
This is apparently a duplicate of bug 628185. If you can provide more information, please add it there.

*** This bug has been marked as a duplicate of bug 628185 ***