[mythtv-users] [ 0.25: channel scanning not working and multiple same entries in dtv_multiplex

[Angela Schmid]

> > Hello
> > I removed 0.24 and upgraded today from http://www.ubuntuupdates.org/ppa/mythtv_0.25?dist=oneiric
> >
> > version: master [v0.25-beta-65-g1558b6e], commit 1558b6e
> >
> > I started with a fresh database. Scanning blocked most the time, something I have never seen on 0.24 (I
> successfully scanned last
> > week because of channel changes). Have to kill mythtv-setup.
> >
> > Sometimes it returned after scanning one frequency and the popup windows came to save the channels, channels
> where never written to
> > the channel table. The dtv_multiplex table had multiple entries with exact the same data with different
> updatetimestamp.
> 
> I can confirm the same behaviour. I tried on Astra, 10744000 H, 22000000, FEC Auto, QPSK, Inv AUTO, Rolloff
> AUTO. I was searching ALL services, Free only unselected, Test decryptability unselected. The first time it
> found 6 channels. I assume that by pressing back and repeating the procedure it should have found the same
> channels, but it reported no channels found. This happened repeatedly. Scanning all existing transports with
> scan for new transports selected worked successfully the first time I tried, but scanning locked up and only
> CTRL-C exited (I left it with about 15 minutes inactivity).
> 
> Subsequent scans using all transports doesn't show any channels. Powering down the pc doesn't work, either.
> 
> The card is a Mantis STB08999 Multistandard DVB-S2, which was working ok 5-6 months ago (yeah, I know). Signal
> timeout is at 7000, Tuning Timeout 10000, DVB tuning delay at 1950, same as they've always been.
> 
> Yianni.

I am on DVB-C with a Digital Devices Octopus. Could you also sometime save channels, but they were not saved. Do you have multiple
entries for the same multiplex in dtv_multiplex, only with different updatetimestamp.