[Mageia-dev] help with update/testing needed / freeze exception for me-tv

Wed May 9 19:51:58 CEST 2012

Am 09.05.2012 12:44, schrieb Colin Guthrie:
> 'Twas brillig, and Wolfgang Bornath at 05/05/12 21:06 did gyre and gimble:
>> 2012/5/5 Wolfgang Bornath <molch.b at googlemail.com>:
>>> 2012/5/5 Florian Hubold <doktor5000 at arcor.de>:
>>>> Am 05.05.2012 21:04, schrieb Wolfgang Bornath:
>>>>> 2012/4/4 Florian Hubold <doktor5000 at arcor.de>:
>>>>>> Hi all,
>>>>>>
>>>>>> me-tv (a really nice and easy to-use DVB viewer with EPG guide)
>>>>>> totally went under my radar and it has not been updated nor
>>>>>> rebuild yet for cauldron since quite some time, seems i forgot
>>>>>> to commit my local update to 2.x branch, and me-tv was not
>>>>>> covered by check.mageia.org updates report, and i've to update
>>>>>> it when i was still apprentice.
>>>>>>
>>>>>> But as me-tv development was suspended, and now restarted
>>>>>> (2.0 branch was complete rewrite, with differing features, f.ex.
>>>>>> server/client based) so that 1.4 branch is the followup to what
>>>>>> we have in cauldron: https://launchpad.net/me-tv/+announcement/9377
>>>>>>
>>>>>> FWIW, me-tv-1.3.6 in cauldron was built last time beginning of last july.
>>>>>> I'd like to get some sort of freeze exception for me-tv, but primarily
>>>>>> help with testing this in cauldron, i've just pushed a rebuild of it,
>>>>>> could all who possess a DVB-receiver and a physical cauldron
>>>>>> installation please test it, should be available soon, rebuild went
>>>>>> through.
>>>>> What exactly do you need (sorry for picking this up so late)?
>>>>>
>>>>> Todays experience as posted in the forum:
>>>>>
>>>>> Cauldron 64-bit with all updates. KDE. "Real" installation on a Samsung R530.
>>>>> Adapter Happauge Nova-T, firmware: dvb-usb-dib0700-1.20.fw in
>>>>> /lib/firmware, plugging in the adapter gives success message in
>>>>> syslog: "Hauppauge Nova-T in warm state"
>>>>>
>>>>> Installed is me-tv (including dependencies):
>>>>>
>>>>>     me-tv-1.3.6-3.mga2
>>>>>     dvb-apps-1.1.1-8.hg1465.1.mga2
>>>>>     lib64unique1.0_0-1.1.6-6.mga2
>>>>>     lib64dvbapps-1.1.1-8.hg1465.1.mga2
>>>>>
>>>>> After installation and starting the application me-tv shows a message
>>>>> that the existing Me-Tv database is to old to be used by this version.
>>>> This sounds like complete bogus to me, as the only version of
>>>> me-tv for Mageia 1 and cauldron is 1.3.6, there should be no
>>>> difference at all.
>>> But different builds.
>>>
>>>> This cauldron install, was it upgraded from mga1, or where did
>>>> the old .me-tv config come from?
>>> Fresh Beta3 installation. The database (NOT config!) file is me-tv.db
>>> and it is installed by the package. I also tried erasing the file
>>> after installation before starting the application - the message about
>>> the old db persists. See below
>>>
>>>
>>>> But if this problem persists, mostly all me-tv users should face
>>>> it after upgrading from Mageia 1 to Mageia 2, so we probably
>>>> need some kind of fix for this ...
>>>>
>>>>> Option "Cancel" ends the whole application, clicking on "Erase old
>>>>> Me-Tv data" the messagebox runs into a freeze which crashes the whole
>>>>> application. In the konsole this looks like:
>>>>>
>>>>>     $ me-tv -v
>>>>>     Me TV 1.3.6
>>>>>     05.05.2012 15:02:55: Application constructor
>>>>>     05.05.2012 15:02:55: sqlite3_threadsafe() = 1
>>>>>     05.05.2012 15:02:55: Database 'exists'
>>>>>     05.05.2012 15:02:55: Opening database file
>>>>> '/home/alfred/.local/share/me-tv/me-tv.db'
>>>>>     05.05.2012 15:02:55: Loading UI files
>>>>>     05.05.2012 15:02:55: Application constructed
>>>>>     05.05.2012 15:02:55: Initialising table 'version'
>>>>>     05.05.2012 15:02:55: Required Database version: 6
>>>>>     05.05.2012 15:02:55: Actual Database version: 0  <<--- here the
>>>>> message box pops up and I click on "Erase old data"
>>>>>     05.05.2012 15:03:26: Dropping Me TV schema
>>>>>     05.05.2012 15:03:26: Dropping table 'channel'
>>>>>     05.05.2012 15:03:26: Dropping table 'epg_event'
>>>>>     05.05.2012 15:03:26: Dropping table 'epg_event_text'
>>>>>     05.05.2012 15:03:26: Dropping table 'scheduled_recording'
>>>>>     05.05.2012 15:03:26: Dropping table 'version'
>>>>>     05.05.2012 15:03:26: Vacuuming database
>>>>>     05.05.2012 15:03:27: Initialising table 'channel'
>>>>>     05.05.2012 15:03:27: Initialising table 'epg_event'
>>>>>     05.05.2012 15:03:27: Initialising table 'epg_event_text'
>>>>>     05.05.2012 15:03:27: Initialising table 'scheduled_recording'
>>>>>     05.05.2012 15:03:27: Initialising table 'version'
>>>>>
>>>>> and that's it.
>>>>>
>>>>> In MGA1 Me-TV works nicely with the same adapter. In MGA1 the package
>>>>> is me-tv-1.3.6-1.1.mga1 - in MGA2 the packages is me-tv-1.3.6-3.mga2
>>>>>
>>>> Can you please try again after removing ~/.local/share/me-tv/ ?
>>> - removed ~/.local/share/me-tv/ (including the me-tv.db)
>>>
>>> Result: Starting me-tv runs into a timeout. Message in konsole:
>>>
>>> (me-tv:1956) : Unique-DBUS-WARNING **: Error while sending message:
>>> Did not receive a reply. Possible causes include [followed by the
>>> generic causes ( message bus security block, reply timeout expired,
>>> network connection broke, etc.)]
>>>
>>> After reboot I started me-tv again, the message about the old database
>>> appears - ~/.local/share/me-tv/ is there again, including the
>>> database.
>>>
>>> ----------------
>>>
>>> Now I installed me-tv (plus dependencies) on a Cauldron which has been
>>> updated since Alpha stage: exactly the same result.
>> Another user posted his erg.txt for me-tv - the relevant difference is
>> clear to see. His text says:
>>
>> 05.05.2012 21:18:38: Required Database version: 6
>> 05.05.2012 21:18:38: Actual Database version: 6
>>
>> Another user and I have the following text:
>>
>> 05.05.2012 15:02:55: Required Database version: 6
>> 05.05.2012 15:02:55: Actual Database version: 0
>>
>> "How come?" is the big question. This database is generated at the
>> start of me-tv. As you can see from the previous mail I erased the
>> whole directory in my home but it was regenerated including the
>> database by starting me-tv.
> What kind of database is this? Is it sqlite maybe... there was a post
> about sqlite earlier that had some strange issues with some join
> conditions. While I wouldn't expect this to be a problem for a query
> that checks a version number... you never know.
>
> Col
>
>
I think i foung the fix, and it's not related to sqlite:
http://bazaar.launchpad.net/~me-tv-administration/me-tv/1.3/revision/786

And as the developer says that new 1.4 branch is still buggy,
i'm updating me-tv to 1.3.7 and hope it'll fix the issue.
*fingers crossed*