Some Bad Channels Require "Force Quit" Application
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| freetuxtv (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
First off, I love this application.
Some bad channels give an error message when they are not currently available. That's fine.
However, some bad channels are causing the user interface to be locked up and grayed out indefinitely.
The code needs to be a little more robust, so that no bad channel can possible lock up the application. Maybe someone should add some try catch statements that have the ability of determining when this type of thing happens, so that the application can recovery without the user having to "force quit" the applications and relaunch.
The way I can reproduce this behavior
1) Go to the channel labeled RLC 5 from the English channel's group. It wouldn't ever start playing, so
2) Change to another channel
Perhaps it is that changing channels too fast causes the lockup?
Either way, the code needs to be a little more robust, so that the User can't lock up the user interface no matter what silly thing they try.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: freetuxtv 0.6.5~dfsg1-1
ProcVersionSign
Uname: Linux 3.8.0-19-generic i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
Date: Tue May 7 00:42:54 2013
InstallationDate: Installed on 2012-12-17 (140 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: freetuxtv
UpgradeStatus: Upgraded to raring on 2013-05-06 (0 days ago)
| Lonnie Lee Best (launchpad-startport) wrote | #1 |
| Daniel van Vugt (vanvugt) wrote | #2 |
| Changed in freetuxtv (Ubuntu): | |
| status: | New → Won't Fix |
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
See this document for currently supported Ubuntu releases:
https:/
We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.