Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: atrpms: users

Re: MythTV 0.22 bleeding

 

 

atrpms users RSS feed   Index | Next | Previous | View Threaded


disafan at aim

Jul 20, 2009, 10:04 AM

Post #1 of 6 (1189 views)
Permalink
Re: MythTV 0.22 bleeding

Would it be possible to request an update to the MythTV 0.22 packages to
the below changeset to incorporate this update, which prevents a
segfault on the part of mythtranscode?

http://svn.mythtv.org/trac/changeset/20949


_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users


Axel.Thimm at ATrpms

Jul 20, 2009, 11:53 AM

Post #2 of 6 (1136 views)
Permalink
Re: MythTV 0.22 bleeding [In reply to]

Hi,

On Mon, Jul 20, 2009 at 01:04:28PM -0400, DISAFAN wrote:
> Would it be possible to request an update to the MythTV 0.22 packages to
> the below changeset to incorporate this update, which prevents a
> segfault on the part of mythtranscode?
>
> http://svn.mythtv.org/trac/changeset/20949

I just updated the packages on July the 17th, although only up to
20931, which was the latest back then. :/

Usually I would like to wait for say a week to have this update
settled before jumping to the next one.

Looking at the bug report you may be lucky and it may be working
(uninitialized variables can break things or not depending on the
compiler used, prelinker, the moon phase and whether you liked your
lunch yesterday). Let me please know, so I have a bad feeling about
this and speed things up.
--
Axel.Thimm at ATrpms.net


disafan at aim

Jul 20, 2009, 5:36 PM

Post #3 of 6 (1128 views)
Permalink
Re: MythTV 0.22 bleeding [In reply to]

On 07/20/2009 02:53 PM, Axel Thimm wrote:
> Hi,
>
> On Mon, Jul 20, 2009 at 01:04:28PM -0400, DISAFAN wrote:
>
>> Would it be possible to request an update to the MythTV 0.22 packages to
>> the below changeset to incorporate this update, which prevents a
>> segfault on the part of mythtranscode?
>>
>> http://svn.mythtv.org/trac/changeset/20949
>>
>
> I just updated the packages on July the 17th, although only up to
> 20931, which was the latest back then. :/
>
> Usually I would like to wait for say a week to have this update
> settled before jumping to the next one.
>
> Looking at the bug report you may be lucky and it may be working
> (uninitialized variables can break things or not depending on the
> compiler used, prelinker, the moon phase and whether you liked your
> lunch yesterday). Let me please know, so I have a bad feeling about
> this and speed things up.
>
Well, technically, it isn't crashing anything. I can hold off on
transcoding for a week.


disafan at aim

Jul 23, 2009, 10:17 PM

Post #4 of 6 (1100 views)
Permalink
Re: MythTV 0.22 bleeding [In reply to]

The segfault is responsible for my inability to run mythtranscode
without an error, which means I can't compress anything I record. A week
would be today, July 24th. Is it possible you could update to 20949 to
see if this resolves the segfault?

On 07/20/2009 02:53 PM, Axel Thimm wrote:
> Hi,
>
> On Mon, Jul 20, 2009 at 01:04:28PM -0400, DISAFAN wrote:
>
>> Would it be possible to request an update to the MythTV 0.22 packages to
>> the below changeset to incorporate this update, which prevents a
>> segfault on the part of mythtranscode?
>>
>> http://svn.mythtv.org/trac/changeset/20949
>>
>
> I just updated the packages on July the 17th, although only up to
> 20931, which was the latest back then. :/
>
> Usually I would like to wait for say a week to have this update
> settled before jumping to the next one.
>
> Looking at the bug report you may be lucky and it may be working
> (uninitialized variables can break things or not depending on the
> compiler used, prelinker, the moon phase and whether you liked your
> lunch yesterday). Let me please know, so I have a bad feeling about
> this and speed things up.
>


Axel.Thimm at ATrpms

Jul 25, 2009, 5:24 AM

Post #5 of 6 (1082 views)
Permalink
Re: MythTV 0.22 bleeding [In reply to]

On Fri, Jul 24, 2009 at 01:17:56AM -0400, DISAFAN wrote:
> The segfault is responsible for my inability to run mythtranscode
> without an error, which means I can't compress anything I record. A week
> would be today, July 24th. Is it possible you could update to 20949 to
> see if this resolves the segfault?

OK, done

> On 07/20/2009 02:53 PM, Axel Thimm wrote:
>> Hi,
>>
>> On Mon, Jul 20, 2009 at 01:04:28PM -0400, DISAFAN wrote:
>>
>>> Would it be possible to request an update to the MythTV 0.22 packages to
>>> the below changeset to incorporate this update, which prevents a
>>> segfault on the part of mythtranscode?
>>>
>>> http://svn.mythtv.org/trac/changeset/20949
>>>
>>
>> I just updated the packages on July the 17th, although only up to
>> 20931, which was the latest back then. :/
>>
>> Usually I would like to wait for say a week to have this update
>> settled before jumping to the next one.
>>
>> Looking at the bug report you may be lucky and it may be working
>> (uninitialized variables can break things or not depending on the
>> compiler used, prelinker, the moon phase and whether you liked your
>> lunch yesterday). Let me please know, so I have a bad feeling about
>> this and speed things up.
>>
>

> _______________________________________________
> atrpms-users mailing list
> atrpms-users [at] atrpms
> http://lists.atrpms.net/mailman/listinfo/atrpms-users

--
Axel.Thimm at ATrpms.net


disafan at aim

Jul 26, 2009, 8:15 AM

Post #6 of 6 (1070 views)
Permalink
Re: MythTV 0.22 bleeding [In reply to]

That fixed all the problems. Transcode is back online without problems.
Thank you.


On 07/25/2009 08:24 AM, Axel Thimm wrote:
> On Fri, Jul 24, 2009 at 01:17:56AM -0400, DISAFAN wrote:
>
>> The segfault is responsible for my inability to run mythtranscode
>> without an error, which means I can't compress anything I record. A week
>> would be today, July 24th. Is it possible you could update to 20949 to
>> see if this resolves the segfault?
>>
>
> OK, done
>
>
>> On 07/20/2009 02:53 PM, Axel Thimm wrote:
>>
>>> Hi,
>>>
>>> On Mon, Jul 20, 2009 at 01:04:28PM -0400, DISAFAN wrote:
>>>
>>>
>>>> Would it be possible to request an update to the MythTV 0.22 packages to
>>>> the below changeset to incorporate this update, which prevents a
>>>> segfault on the part of mythtranscode?
>>>>
>>>> http://svn.mythtv.org/trac/changeset/20949
>>>>
>>>>
>>> I just updated the packages on July the 17th, although only up to
>>> 20931, which was the latest back then. :/
>>>
>>> Usually I would like to wait for say a week to have this update
>>> settled before jumping to the next one.
>>>
>>> Looking at the bug report you may be lucky and it may be working
>>> (uninitialized variables can break things or not depending on the
>>> compiler used, prelinker, the moon phase and whether you liked your
>>> lunch yesterday). Let me please know, so I have a bad feeling about
>>> this and speed things up.
>>>
>>>
>
>
>> _______________________________________________
>> atrpms-users mailing list
>> atrpms-users [at] atrpms
>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>>
>
>

atrpms users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.