Bug 574340 - SIGSEGV in "gtk_text_layout_get_line_display" in /home/koen/software/nicotine+-1.2.12/nicotine.py
SIGSEGV in "gtk_text_layout_get_line_display" in /home/koen/software/nicotine...
Product: Fedora
Classification: Fedora
Component: gtk2 (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
: Triaged
: 559245 573935 573950 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2010-03-17 06:02 EDT by koen
Modified: 2010-11-03 22:00 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-03 22:00:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (20.29 KB, text/plain)
2010-03-17 06:03 EDT, koen
no flags Details

  None (edit)
Description koen 2010-03-17 06:02:52 EDT
abrt 1.0.0 detected a crash.

Attached file: backtrace
cmdline: python /home/koen/software/nicotine+-1.2.12/nicotine.py
component: python
executable: /usr/bin/python
package: python-2.6.2-4.fc12
rating: 3
reason: Process was terminated by signal 11
Comment 1 koen 2010-03-17 06:03:52 EDT
Created attachment 400704 [details]
File: backtrace
Comment 2 Dave Malcolm 2010-03-18 16:35:09 EDT
*** Bug 559245 has been marked as a duplicate of this bug. ***
Comment 3 Dave Malcolm 2010-03-18 16:36:58 EDT
Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there is not a symbolic stack trace. In order to get a symbolic stack trace, the appropriate debuginfo packages need to be installed. In order to accomplish this, you can run the command:
   debuginfo-install gtk2 glib2

Please see http://fedoraproject.org/wiki/StackTraces for more information about stack traces.
Comment 4 Dave Malcolm 2010-03-18 20:22:10 EDT
*** Bug 573950 has been marked as a duplicate of this bug. ***
Comment 5 Dave Malcolm 2010-03-18 20:22:17 EDT
*** Bug 573935 has been marked as a duplicate of this bug. ***
Comment 6 Jeff Raber 2010-07-06 13:22:20 EDT
Reporter, please reply to the previous question.  If you don't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Comment 7 Bug Zapper 2010-11-03 15:26:01 EDT
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 8 Jeff Raber 2010-11-03 22:00:17 EDT
CLOSING per comment 6

Fedora Bugzappers volunteer triage team

Note You need to log in before you can comment on or make changes to this bug.