Bruce Markey wrote:
This sounds too weird to be true and I wanted to get someone to
verify this before filing a bug. Before starting to compose a
message, I found this thread =).
I too was having trouble with the second invocation of live TV
but was having trouble debugging it. A little divide
This sounds too weird to be true and I wanted to get someone to
verify this before filing a bug. Before starting to compose a
message, I found this thread =).
I too was having trouble with the second invocation of live TV
but was having trouble debugging it. A little divide and conquer
led to thi
Jon Whitear wrote:
Mark Weaver wrote:
You could try running it normally, making it break and then doing
attach in gdb. You should be able to get a backtrace that way.
Thanks for the tip. I started front- and backend normally, made it
break, then ran gdb as follows:
server awstats # ps f
Mark Weaver wrote:
You could try running it normally, making it break and then doing
attach in gdb. You should be able to get a backtrace that way.
Thanks for the tip. I started front- and backend normally, made it
break, then ran gdb as follows:
server awstats # ps fax
16020 ?S
Just wanted to report that the "you should have gotten a lock" message has gone
now in svn 7376.
Cheers
david maher
___
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Ian Caulfield wrote:
On Sun, 2 Oct 2005, Torbjörn Jansson wrote:
Or is there meta data in the
broadcast signal which provides the necessary information?
WSS or whatever it's called tells what aspect it is in, but i asume
that WSS
is not accurate and/or not being transmitted otherwise there
On Sun, Oct 02, 2005 at 06:39:36PM +0100, Ian Caulfield wrote:
> On Sun, 2 Oct 2005, Torbjörn Jansson wrote:
>
> >>Or is there meta data in the
> >>broadcast signal which provides the necessary information?
> >>
> >
> >WSS or whatever it's called tells what aspect it is in, but i asume that
> >WS
On Sat, 2005-10-01 at 15:30 +0200, Adam Egger wrote:
> Hi,
>
> I still have a few issues with the latest build (r7369, dvb-t,
> debian64, Germany). I'll attach a log where all the problems should be
> included:
>
> 1. The channel it first tuned to wasn't set to fullscreen. I'm
> sometimes seeing
Yep, it looks like the backend is deadlocked. Can you update to
7372, repeat this in gdb and then hit "Ctrl-C" and get me the
results of "thread apply all bt". I'd like to know where each
thread is.
I'm afraid I can't make it break under gdb. I spent ages existing and
re-entering Live TV and it
Daniel Kristjansson wrote:
Yep, it looks like the backend is deadlocked. Can you update to
7372, repeat this in gdb and then hit "Ctrl-C" and get me the
results of "thread apply all bt". I'd like to know where each
thread is.
I'm afraid I can't make it break under gdb. I spent ages existing and
On Sun, 2 Oct 2005, Torbjörn Jansson wrote:
Or is there meta data in the
broadcast signal which provides the necessary information?
WSS or whatever it's called tells what aspect it is in, but i asume that WSS
is not accurate and/or not being transmitted otherwise there wouldn't be a
problem
> I was looking at the houskeeping table in mysql and found:
>
> 'JobQueueCleanup', '2004-10-02 12:51:48'
> 'JobQueueRecover-hostname', '2004-10-02 12:51:48'
> 'MythFillDB', '2005-10-02 04:52:47'
>
> That got me wondering why the dates for JobQueueCleanup and JobQueueRecover
> was so old.
> On 10/2/05, Daniel Kristjansson <[EMAIL PROTECTED]> wrote:
>
>> I don't know much about the EIT parsing code, but perhaps the time
>> per channel should be increased? Right now it is 60 seconds, which
>> may be a bit low. (it is on line 1210 in tv_rec...)
>
> I don't think it's the time. It also
[EMAIL PROTECTED] <> wrote:
> On 10/2/05, Daniel Kristjansson <[EMAIL PROTECTED]> wrote:
>
>> I don't know much about the EIT parsing code, but perhaps the time
>> per channel should be increased? Right now it is 60 seconds, which
>> may be a bit low. (it is on line 1210 in tv_rec...)
>
> I don't
On 10/2/05, Daniel Kristjansson <[EMAIL PROTECTED]> wrote:
> I don't know much about the EIT parsing code, but perhaps the time
> per channel should be increased? Right now it is 60 seconds, which
> may be a bit low. (it is on line 1210 in tv_rec...)
I don't think it's the time. It also doesn't c
On Sun, 2005-10-02 at 13:58 +0200, Adam Egger wrote:
> On 10/2/05, Torbjörn Jansson <[EMAIL PROTECTED]> wrote:
> > Any ideas what could be wrong?
> > Will backend logs help?
> It's a very good starting point and I'm very happy to have the
> crawler, but we just need anyone with more knowledge abo
I was looking at the houskeeping table in mysql and found:
'JobQueueCleanup', '2004-10-02 12:51:48'
'JobQueueRecover-hostname', '2004-10-02 12:51:48'
'MythFillDB', '2005-10-02 04:52:47'
That got me wondering why the dates for JobQueueCleanup and JobQueueRecover
was so old.
After a little
On 10/2/05, Torbjörn Jansson <[EMAIL PROTECTED]> wrote:
> I'm running SVN rev 7373.
>
> Previously to get EIT data inserted i had to tune to one specific channel
> and then to another channel a few times, usualy switching 2 times got all
> data inserted.
> Each time i switched back and forth i got
I'm running SVN rev 7373.
Previously to get EIT data inserted i had to tune to one specific channel
and then to another channel a few times, usualy switching 2 times got all
data inserted.
Each time i switched back and forth i got some EIT data inseted.
But now this no longer works, no matter wha
> I use dvb in australia on a 4:3 tv, and the display usually
> has black borders at the top and the bottom of the screen,
> but sometimes also on the left and right, depending on
> whether the content is broadcast in widescreen or not. It
> would be nice to have a feature which automatically selec
20 matches
Mail list logo
