[mythtv-users] Just upgraded to 0.25 with mixed results.

[Douglas Peale]

On 07/10/2011 10:54 PM, Robert McNamara wrote:
> On Sun, Jul 10, 2011 at 10:40 PM, Douglas Peale
> <Douglas_Peale at comcast.net> wrote:
>
>> More weird stuff:
>> Can't do "Watch TV" until after I have run mythbackendsetup. The backend is
>> running on boot, but selecting "Watch TV" just causes the screen to flash.
>>
>> This appears in the backend log:
>>
>> 2011-07-10 22:30:02.942967 N [1494/1965] Expire autoexpire.cpp:263
>> (CalcParams) - AutoExpire: CalcParams(): Max required Free Space: 1.0 GB
>> w/freq: 15 min
>> 2011-07-10 22:30:25.981046 I [1494/1973] ProcessRequest mainserver.cpp:1298
>> (HandleAnnounce) - MainServer::ANN Playback
>> 2011-07-10 22:30:25.981061 I [1494/1973] ProcessRequest mainserver.cpp:1300
>> (HandleAnnounce) - adding: Compromise as a client (events: 0)
>> 2011-07-10 22:30:25.981686 I [1494/1974] ProcessRequest mainserver.cpp:1298
>> (HandleAnnounce) - MainServer::ANN Monitor
>> 2011-07-10 22:30:25.981699 I [1494/1974] ProcessRequest mainserver.cpp:1300
>> (HandleAnnounce) - adding: Compromise as a client (events: 1)
>> 2011-07-10 22:30:39.179672 I [1494/1975] ProcessRequest mainserver.cpp:1298
>> (HandleAnnounce) - MainServer::ANN Playback
>> 2011-07-10 22:30:39.179680 I [1494/1975] ProcessRequest mainserver.cpp:1300
>> (HandleAnnounce) - adding: Compromise as a client (events: 0)
>> 2011-07-10 22:30:39.196810 I [1494/1723] TVRecEvent tv_rec.cpp:989
>> (HandleStateChange) - TVRec(1): Changing from None to WatchingLiveTV
>> 2011-07-10 22:30:39.200530 I [1494/1723] TVRecEvent tv_rec.cpp:3443
>> (TuningCheckForHWChange) - TVRec(1): HW Tuner: 1->1
>> 2011-07-10 22:30:39.204281 E [1494/1723] TVRecEvent dtvmultiplex.cpp:289
>> (ParseTuningParams) - DTVMux: ParseTuningParams -- Unknown tuner type
>> 2011-07-10 22:30:39.204330 E [1494/1723] TVRecEvent dtvchannel.cpp:303
>> (SetChannelByString) - DTVChan(1016A87D-0): SetChannelByString(5.1): Failed
>> to initialize multiplex options
>> 2011-07-10 22:30:39.204341 E [1494/1723] TVRecEvent tv_rec.cpp:3647
>> (TuningFrequency) - TVRec(1): Failed to set channel to 5.1. Reverting to
>> kState_None
>> 2011-07-10 22:30:39.204372 I [1494/1723] TVRecEvent tv_rec.cpp:989
>> (HandleStateChange) - TVRec(1): Changing from WatchingLiveTV to None
> A 39 second excerpt of the backend log is not sufficient to determine
> what is wrong.
It is a 39 second excerpt that covers the entire attempt to start "Watch TV". It is 39 seconds because the mailing list will
"hold" any message that is too long. I'd be happy to send my entire log file to you directly if you'd like, just say the word.
>   Based on the "unknown tuner type," it could be a
> misconfiguration on your part, a database corruption, etc.

If it is, it is interesting that it gets temporarily fixed (until the next reboot) by running mythtv-setup.
>   It's also
> quite likely, given your reason for updating to master, your usage of
> a channel editor that does no error checking (both those in mythweb
> and in the new web setup), and possible manual database manipulation,
> that your channel and multiplex tables are no longer correct, where
> correct means "exactly the format myth writes them in, and thus
> expects to find them in."  Those manipulations are quite possibly the
> cause of your issues.
I have never edited the database directly. At most I have dumped the database to get info on the subchannel so I could figure
out which channel is which.
I have been very careful to avoid making changes using your fragile new editors knowing that they are not fully tested. So far I
have only looked at data using them, so unless they arbitrarily make changes when one is browsing the data, the data is the same
as it was when I upgraded from 0.24, and the channel info was working under 0.24 for more than six months before I upgraded.
>   I also have no idea what you mean by
> "mythbackendsetup" as we have no such thing... I will guess that you
> mean mythtv-setup, but that's just a guess.
It is a good guess. It shows up in the system->administration menu as "MythTV Backend Setup", and we lowly users never see the
"mythtv-setup" name.
> But more importantly, as Mark previously noted, you are not running a
> stable release, nor a supported one.  Posting a litany of issues is
> unlikely to generate a rush to respond as we really don't *want*
> people to be using master while we're adding new features, thus
> creating new bugs, thus chasing new bugs, and thus ultimately fixing
> new bugs.  When people use master, we generally hope/expect that they
> will be able to competently fix the bugs they find.  When we're ready
> for people to test things thoroughly, we always make a public call on
> the lists and on our web site.
>
Right now, it is between TV seasons. It is the ideal time to be testing MythTV since bugs will not affect any shows I'm following.
I have always found the best time for testing code is while the developers are still working on it. If I wait until they think
they are done, they have moved on to other things and are less likely to fix bugs that don't affect them directly.
I am posting facts about the current state of 0.25, if they are ignored, then they are ignored. Perhaps it will allow others to
make informed decisions about whether they should use it or not.
> Users of master should open thorough, informed tickets (after having
> read the ticket howto), and prepare to be prompted for extensive
> information, patch testing, backtraces, etc. if they want those issues
> resolved.  They should also be religiously following the commits list.
>
As a user I have been told that before opening a ticket, I should post any issues I have with MythTV here first to avoid
creating useless tickets.
I have been following those instructions.
> Robert


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
Url : http://www.mythtv.org/pipermail/mythtv-users/attachments/20110711/76e30b37/attachment.bin