[mythtv-users] mythtv-setup hangs on "Fetching lineups from Schedules Direct"

[Phil Bridges]

On Fri, Oct 10, 2008 at 1:43 PM, Paul Archer <tigger at io.com> wrote:
> Doesn't look like the message got through the first time...
>
> 7:55am, Paul Archer wrote:
>
>> Setup:
>> latest sources from SVN
>> 3 pvr-150 tuners connected to SD set-top boxes
>>
>> I noticed one of the channels in my setup was wrong (cable company had
>> shifted things around). I updated things in Schedules Direct, and then ran
>> mythfilldatabase, but the new/changed channels didn't show up. Then I backed
>> up my database and cleared out the channel and program tables in mysql, then
>> ran mythfilldatabase again, but the tables are not getting repopulated.
>> Then I went to mythtv-setup, and deleted everything: cards, sources, the
>> works. I added them back, but when I go to the video source I've setup, I get
>> nothing in the gui, and on the command line I see "Fetching lineups from
>> Schedules Direct", and it hangs. The same thing happens if I try to use the
>> "retrieve lineups" button when adding a new video source. I've tried to run
>> strace on it, but even with 'strace -f ' this is all I get:
>>
>> [pid  9485] write(1, "2008-10-10 07:51:40.691 Fetching"..., 662008-10-10
>> 07:51:40.691 Fetching lineups from Schedules Direct...
>> ) = 66
>> [pid  9485] write(6, "\0", 1)           = 1
>> [pid  9485] write(6, "\0", 1)           = 1
>> [pid  9485] write(6, "\0", 1)           = 1
>> [pid  9485] write(6, "\0", 1)           = 1
>> [pid  9485] write(6, "\0", 1)           = 1
>>
>>
>> This is from an 'ltrace':
>>
>> 2008-10-10 07:53:25.939 Fetching lineups from Schedules Direct...
>> _ZN7QString4freeEPNS_4DataE(0x9377ad8, 0x9377850, 0xbfe02450, 0, 0xbfe0246a)
>> = 409
>> _ZN7QObject10childEventEP11QChildEvent(0x81a7580, 0xbfe020e0, 0xe01b08,
>> 0xb5a6cd00, 0x9378fe0) = 0x81a7580
>> _ZN7QObject10childEventEP11QChildEvent(0x9377cb0, 0xbfe021f4, 0xbfe01d18,
>> 0xb5829bf1, 0xbfe02230) = 0x9377cb0
>> _ZN7QObject10childEventEP11QChildEvent(0x9377cb0, 0xbfe020f0, 0x9378fe0,
>> 0xb5a6cc98, 0xb60c12d8) = 0x9377cb0
>>
>>

Your message did get through the first time, and has already been replied to.

Please don't top-post.