streamtuner crashes on stream selection

Bug #84434 reported by John Tucker
40
This bug affects 6 people
Affects Status Importance Assigned to Milestone
streamtuner (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: streamtuner

Streamtuner version 0.99.99

Crashes when one tries to select a station; or when "find" on the "search" dialogue is clicked.

Revision history for this message
Dave Morley (davmor2) wrote :

Remains unconfirmed it refuses to crash. Does it produce a crash report if so could you post it here please

Revision history for this message
John Tucker (jonti) wrote :

The attached bug report was generated by selecting a listed station, then pressing enter (same as double left click on station).

It also crashes when the "search" facility is used. I'll generate a report for that too soon, in case that has some more clues.

NB: the machine uses the VIA VT8363A Apollo KT133A motherboard.

Revision history for this message
Adam Niedling (krychek) wrote :

What version of Ubuntu are you using? Is this still an issue?

Changed in streamtuner:
status: New → Incomplete
Revision history for this message
Paul Weiss (interweiss) wrote :

I also get this bug. I am running Ubuntu 9.04 RC AMD64 and StreamTuner 0.99.99

Changed in streamtuner (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Paul Weiss (interweiss) wrote :

The error that I get when I run StreamTuner in terminal is:

Segmentation fault

Revision history for this message
Finog (finog) wrote :

I'm having the same problem in Ubuntu 9.10 (the most current release edition at the time of submission) with double-clicking streams and selecting then hitting play. Running from terminal shows a segfault.

Revision history for this message
steveshutt (steven-shutt) wrote :

Today i upgraded to Ubuntu 9.10.
I had been using streamtuner and streamripper happily until the upgrade.
Now, when i try to tune into a stream.... it simply exits.
Any hints or suggestions would be welcomed with open arms.

Best wishes

Steve.

Revision history for this message
steveshutt (steven-shutt) wrote :

I tried completely removing streamripper and streamtuner.
Then re-installing streamriper and streamtuner.... but alas, it still exits when you attempt to tune into a stream.

best wishes

Steve.

Revision history for this message
trentreviso (trentreviso) wrote :

I'm having the same problem as steveshutt in Ubuntu 9.10. Streamtuner ran fine on Ubuntu 9.04, but it crashes on 9.10 the moment a station is selected to be tuned in.

Streamripper, however (which launches from the Streamtuner graphical interface), works just fine on Ubuntu 9.10 (as it did in 9.04).

Revision history for this message
adam (asmith607) wrote :

I had the same issue, upgraded from 9.04 to 9.10 and upon "tuning in" to a station, Streamtuner would exit with a segmentation fault. The fix for me was to go to Preferences -> Applications in Streamtuner, and change references from 'audacious %q' to 'audacious2 %q' and restart Streamtuner. Now works as it once did.

Revision history for this message
trentreviso (trentreviso) wrote :

^ Thanks, Adam. That works well.

Revision history for this message
zcx2009 (zcx) wrote :

Using Streamripper 0.99.99 and Audacious 1.5.1 on Ubuntu 9.04 here. Sometimes Streamripper segfaults when you connect, but Audacious runs and plays the stream. Today couldn't get Streamripper to stay alive so followed Adam's suggestion, but of course Ubuntu doesn't what audacious2 is. But when I changed the preferences back to audacious now it all works fine again! Something flaky in Streamripper perhaps?

Revision history for this message
Finog (finog) wrote :

Adam's fix worked for me as well.
I tried deleted the ".streamtuner" directory to see if the upgrade had resulted in an incorrect legacy configuration, but this was not the case: "audacious" still appeared.

This seems as though it should be an easy fix. Anyone?

Revision history for this message
Finog (finog) wrote :

Actually, this should resolve the problem during compile time by checking whether the user is on audacious2 or audacious.
Not sure how this works in the packaging system, though and some check should still be done before assuming audacious exists.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.