Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=929201.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2013-03-29T13:25:33+00:00 triniton wrote:

Description of problem:

In my sistem I have one PCI TV/FM tuner card and one removable USB TV/FM
tuner.

Gnomeradio is set to use, by default /dev/radio0, device create by PCI
TV/FM card. I discover this problem when I forgotten to attach USB TV/FM
and I try to set gnomeradio to use /dev/radio1 ( device that would have
made ​​it by USB TV/FM and, of course if USB isn't connected, it does
not exist).

When I tried to change radio device to /dev/radio 1, in preferences
"Radio Device" and I press ENTER, gnomeradio crash.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Open Gnomeradio
2.Open Preferences Settings
3.Enter in "Radio Device" settings text box one that not exist ( e.g. 
/dev/radio5)
4. Press ENTER to SAVE
  
Actual results:

gnomeradio crashed with SIGABRT in __libc_message()

Expected results:

gnomeradio to display message that device not exist


Additional info:

StacktraceSource: http://bugs.debian.org/cgi-
bin/bugreport.cgi?msg=10;filename=StacktraceSource.txt;att=2;bug=704201

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnomeradio/+bug/1110660/comments/9

------------------------------------------------------------------------
On 2013-03-29T13:32:02+00:00 POJAR wrote:

PATCH: http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/raring/gnomeradio/raring/view/head:/debian/patches
/gnomeradio-device.patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnomeradio/+bug/1110660/comments/10

------------------------------------------------------------------------
On 2013-09-16T13:22:58+00:00 Fedora wrote:

This bug appears to have been reported against 'rawhide' during the Fedora 20 
development cycle.
Changing version to '20'.

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnomeradio/+bug/1110660/comments/25

------------------------------------------------------------------------
On 2015-05-29T08:57:38+00:00 Fedora wrote:

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnomeradio/+bug/1110660/comments/26

------------------------------------------------------------------------
On 2015-06-29T11:50:47+00:00 Fedora wrote:

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gnomeradio/+bug/1110660/comments/27


** Changed in: gnomeradio (Fedora)
       Status: Unknown => Won't Fix

** Changed in: gnomeradio (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1110660

Title:
  [SRU] gnomeradio crashed with SIGABRT in __libc_message()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnomeradio/+bug/1110660/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to