Opened 11 years ago
Closed 11 years ago
Last modified 11 years ago
#12068 closed Bug Report - General (Invalid)
Browse Mode Selected Channel EPG
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | major | Milestone: | 0.27.1 |
Component: | MythTV - General | Version: | 0.27-fixes |
Severity: | medium | Keywords: | Browse Mode Broken Channel Update |
Cc: | Ticket locked: | no |
Description
mythTV 0.27.0+fixes20131218 (Debian)
Browse Mode appears broken due to several issues in Live-TV.
- Browse Mode will not update to current or newly selected channel. It continues to display EPG information from the original/first selected channel from source.
As a corollary, invoking the key press "I/i" gives wrong EPG information on the current channel.
- Browse Mode becomes unresponsive after 3-4 "Up/Down?" keypresses. Work-around is to quit Live-TV and re-enter.
Change History (5)
comment:2 Changed 11 years ago by
Replying to stuartm:
Some, maybe all of this has already been fixed in 0.27. You're using a version from mid-December, can you try upgrading to the last 0.27-fixes?
0.27-fixes supercedes 0.27 but the issue is still present. 0.27.0+fixes20131218 is the latest version provided by the Debian (Stable) distro, actually it's a Backport for Debian Stable.
To recreate this issue, try turning off Browser Mode in Mythfrontend settings, and then turn Browse Mode on again. The issue will reappear. So there's an issue with Browse Mode which still needs fixing.
I don't believe these issues (1., 2.) were present in 0.26. So something has changed recently as of mythTV 0.27.
These issues are fairly important because they degrade considerably the usage experience of mythTV.
- Browse Mode needs to update it's screen to the currently selected channel.
- Browse Mode becomes non-responsive after browsing a certain number of channels.
comment:3 Changed 11 years ago by
Resolution: | → Invalid |
---|---|
Status: | infoneeded_new → closed |
You should take this up with the Debian packagers, we've already fixed these issues and they just aren't supplying up to date packages.
comment:4 Changed 11 years ago by
Specifically it as fixed in [8307dd49]
Some, maybe all of this has already been fixed in 0.27. You're using a version from mid-December, can you try upgrading to the last 0.27-fixes?