Bug 678959

Summary: [abrt] qutim-0.2.0-8.fc14: Process /usr/bin/qutim was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kirill <Ridd1er>
Component: qutimAssignee: Pavel Alexeev <pahan>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: dwmw2, elad, pahan
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:97fdb3b8b159568085de95cbe9c7a3d2086c2646
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-05 19:09:50 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 Flags
File: backtrace none

Description Kirill 2011-02-21 04:49:36 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: qutim
component: qutim
executable: /usr/bin/qutim
kernel: 2.6.35.11-83.fc14.i686
package: qutim-0.2.0-8.fc14
reason: Process /usr/bin/qutim was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1298262081
uid: 500

How to reproduce
-----
1. message
2.
3.
Comment 1 Kirill 2011-02-21 04:49:38 UTC 
Created attachment 479816 [details]
File: backtrace
Comment 2 Pavel Alexeev 2011-02-23 08:17:06 UTC 
How it is reproducible?

Please write steps to reproduce.
Comment 3 Elad Alfassa 2011-05-04 17:12:21 UTC 
Moving to qutim (was 0xFFFF)



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