Bug 713398 - [abrt] qutim-0.2.0-8.fc13: ref: Process /usr/bin/qutim was killed by signal 11 (SIGSEGV)
Summary: [abrt] qutim-0.2.0-8.fc13: ref: Process /usr/bin/qutim was killed by signal 1...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: qutim
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Alexeev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9507fd02f6b1e76e6d6eee962d7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-15 09:58 UTC by Mitrandir
Modified: 2011-06-27 11:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 11:40:36 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (78.53 KB, text/plain)
2011-06-15 09:58 UTC, Mitrandir 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Mitrandir 2011-06-15 09:58:34 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: qutim
component: qutim
crash_function: ref
executable: /usr/bin/qutim
kernel: 2.6.34.8-68.fc13.i686.PAE
package: qutim-0.2.0-8.fc13
rating: 4
reason: Process /usr/bin/qutim was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1308131193
uid: 500

How to reproduce
-----
1. установка плагина qutIM Jabber
2. Поиск пользователя -> Fetch
3. Сбой
Comment 1 Mitrandir 2011-06-15 09:58:36 UTC 
Created attachment 504842 [details]
File: backtrace
Comment 2 Pavel Alexeev 2011-06-15 18:44:45 UTC 
How it is reproducible?
Comment 3 Bug Zapper 2011-06-27 11:40:36 UTC 
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.