Bug 576922 - [abrt] crash in gnomeradio-1.8-5.fc13: Process /usr/bin/gnomeradio was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnomeradio-1.8-5.fc13: Process /usr/bin/gnomeradio was killed...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnomeradio
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dominik 'Rathann' Mierzejewski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2738e5a647d172792d18e48b3e8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-25 16:07 UTC by Vladimir Benes
Modified: 2010-08-03 01:13 UTC (History)
3 users (show)

Fixed In Version: gnomeradio-1.8-5.fc12
Clone Of:
Environment:
Last Closed: 2010-08-03 01:12:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (21.28 KB, text/plain)
2010-03-25 16:07 UTC, Vladimir Benes
no flags Details

Description Vladimir Benes 2010-03-25 16:07:33 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gnomeradio
component: gnomeradio
executable: /usr/bin/gnomeradio
kernel: 2.6.33-1.fc13.x86_64
package: gnomeradio-1.8-5.fc13
rating: 4
reason: Process /usr/bin/gnomeradio was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Rawhide)

How to reproduce
-----
1.open gnomeradio without radio reciever
2.click add
3.click delete > crash

Comment 1 Vladimir Benes 2010-03-25 16:07:36 UTC
Created attachment 402600 [details]
File: backtrace

Comment 2 Paulo Roma Cavalcanti 2010-07-07 16:15:46 UTC
Unfortunately, gnomeradio seems to be a dead project. 
Therefore, this bug will not be fixed. One can try
a supported radio application, such as fmtools-tkradio or kradio4.

Comment 3 Dominik 'Rathann' Mierzejewski 2010-07-08 15:45:12 UTC
I would appreciate it if you didn't close bugs assigned to me. I'm the maintainer and it's up to me to decide if I can fix this myself or not. Please don't do this in the future.

Comment 4 Dominik 'Rathann' Mierzejewski 2010-07-08 17:20:28 UTC
Vladimir: I manage to reproduce the bug on F-12, thanks for precise information.

Comment 5 Fedora Update System 2010-07-08 18:08:04 UTC
gnomeradio-1.8-6.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/gnomeradio-1.8-6.fc13

Comment 6 Fedora Update System 2010-07-08 18:08:10 UTC
gnomeradio-1.8-5.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/gnomeradio-1.8-5.fc12

Comment 7 Fedora Update System 2010-07-13 07:45:21 UTC
gnomeradio-1.8-6.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gnomeradio'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gnomeradio-1.8-6.fc13

Comment 8 Fedora Update System 2010-07-13 07:45:27 UTC
gnomeradio-1.8-5.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gnomeradio'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gnomeradio-1.8-5.fc12

Comment 9 Bug Zapper 2010-07-30 11:12:02 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Fedora Update System 2010-08-03 01:12:20 UTC
gnomeradio-1.8-6.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2010-08-03 01:13:13 UTC
gnomeradio-1.8-5.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


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