Project

General

Profile

Bug #3486

bouquet messed up

Added by glenn ch almost 9 years ago. Updated almost 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2016-01-09
Due date:
% Done:

0%

Estimated time:
Found in version:
4.08
Affected Versions:

Description

When I use my fastscan bouquet everything works fine initially.
My channels are ordered from 1 to 950.

Now, after some time (bouquet update probably),
old channels appears on channel number 960 while a correct working version of that channel is available on the correct channel number.

My setup is now running a few months without touching the channel settings and I end up with 250 non working channels on number 960.

I know that you fixed an issue when a service was deleted, but in my case the service is still present (see attachment).
https://github.com/tvheadend/tvheadend/commit/ea82d9fd9fccd09facb03c0ee8f3fadf56eaed4e

The problem is that I can not test with master as it would take weeks/months before these channels appear,
is it possible to backport fixes to 4.0x?

Thanks in advance!

Files

Schermafdruk van 2016-01-09 14_38_41.png (401 KB) Schermafdruk van 2016-01-09 14_38_41.png old channels with non working service assigned glenn ch, 2016-01-09 14:40

History

#1

Updated by Jaroslav Kysela almost 9 years ago

  • Status changed from New to Rejected

I'm sorry, the code changed a lot in 4.1, so I don't plan anything else for 4.0 except for obvious / crash fixes.

The 4.1 tree state is just before next stable 4.2 release, so perhaps a time to test it.

Also available in: Atom PDF