mtdean at thirdcontact
May 7, 2012, 9:56 AM
Post #4 of 5
On 05/07/2012 09:04 AM, Jan Ceuleers wrote:
Re: Backtrace when running mythtv-setup over X
[In reply to]
> On 07/05/12 13:46, Michael T. Dean wrote:
>> We'd need a real backtrace, as described at
>> http://www.mythtv.org/wiki/Debugging to find out.
> Thank you, I have filed a bug in the way suggested there:
>> Also, please make sure you're using the Qt Theme Painter. If you use a
>> frontend on that system and want it to use OpenGL painter, you can pass
>> a one-time override with: -O ThemePainter=qt
> The problem occurs both with and without the above parameter.
Looking at the back trace, all the calls are occurring far below MythTV
code--specifically in Qt's X support code. But, as the glibc
"abbreviated" backtrace said, it's in a call for memory allocation,
requested by libxi (XInput support).
I'd guess (but this isn't much more than a guess) that the problem is
either with your X (and/or libxi) or is potentially caused by the X
configuration (and X doesn't handle/protect against the invalid config).
mythtv-users mailing list
mythtv-users [at] mythtv