Bug 593008 - [abrt] crash in rss-glx-0.9.1.p-2.fc13: raise: Process /usr/bin/rss-glx-pixelcity was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in rss-glx-0.9.1.p-2.fc13: raise: Process /usr/bin/rss-glx-pixel...
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:f94378efa0af3644f87ca32ff82...
: 598693 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-17 15:24 UTC by Igor Katalnikov
Modified: 2011-06-27 16:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-06-27 16:26:05 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (17.38 KB, text/plain)
2010-05-17 15:24 UTC, Igor Katalnikov
no flags Details

Description Igor Katalnikov 2010-05-17 15:24:40 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: rss-glx-pixelcity -r
component: rss-glx
crash_function: raise
executable: /usr/bin/rss-glx-pixelcity
global_uuid: f94378efa0af3644f87ca32ff828786b40ceed44
package: rss-glx-0.9.1.p-2.fc13
rating: 4
reason: Process /usr/bin/rss-glx-pixelcity was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1. Install rss-gnlx-gnome-screensaver
2. Choose pixelcity

Comment 1 Igor Katalnikov 2010-05-17 15:24:42 UTC
Created attachment 414587 [details]
File: backtrace

Comment 2 Nils Philippsen 2010-05-27 14:47:31 UTC
Happens deep in hw-specific Mesa code (drm_intel_gem_bo_unreference_final()), changing component.

Please tell us which version of mesa-dri-drivers you have installed. Thanks.

Comment 3 Igor Katalnikov 2010-06-01 20:20:21 UTC
$ yum list installed mesa-dri-drivers
Loaded plugins: refresh-packagekit
Installed Packages
mesa-dri-drivers.x86_64 7.8.1-6.fc13 @anaconda-InstallationRepo-201005130101.x86_64

Comment 4 Igor Katalnikov 2010-06-01 20:47:38 UTC
*** Bug 598693 has been marked as a duplicate of this bug. ***

Comment 5 Igor Katalnikov 2010-06-02 21:56:23 UTC
Package: rss-glx-0.9.1.p-2.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)

How to reproduce
1. Ment to test new version abrt

Comment 6 Igor Katalnikov 2010-06-02 21:57:24 UTC
abrt works good

Comment 7 Bug Zapper 2011-06-02 13:55:07 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 Bug Zapper 2011-06-27 16:26:05 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.