Mailing List Archive

Info: MythTV and QT 3.3.8
Hello MythTV-Developers!

I want to inform you that mythtranscode doesn't work with Qt 3.3.8.

An user of my openSUSE MythTV packages on packman discovered this and file a
bug on SUSE bug tracker.

Meanwhile SUSE has fixed this issue, but it may last some time until the fix
will reach the KDE:KDE3 repositiory. I think Dirk Mueller from SUSE has send
a bug report to Trolltech.

A short description of the problem: Trolltech add a cleanup of the mysql (and
proably other modules) to the QApplication destructor. If the mysql plugin is
already unloaded this will relut in a segfault. This happend with
mythtranscode, but maybe with other programs, too.

Cheers
Herbert Graeber
Packman member
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: Info: MythTV and QT 3.3.8 [ In reply to ]
On Thursday 8 March 2007 21:38:29 Herbert Graeber wrote:
> A short description of the problem: Trolltech add a cleanup of the mysql
> (and proably other modules) to the QApplication destructor. If the mysql
> plugin is already unloaded this will relut in a segfault. This happend with
> mythtranscode, but maybe with other programs, too.

Thank you for letting us know. Only yesterday I noticed a segfault in
mythfilldatabase, the backtrace indicated the QApp destructor but I'd been
able to narrow it down so you've saved me the trouble.
--
Stuart Morgan
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: Info: MythTV and QT 3.3.8 [ In reply to ]
On 3/8/07, Stuart Morgan <stuart@tase.co.uk> wrote:
> On Thursday 8 March 2007 21:38:29 Herbert Graeber wrote:
> > A short description of the problem: Trolltech add a cleanup of the mysql
> > (and proably other modules) to the QApplication destructor. If the mysql
> > plugin is already unloaded this will relut in a segfault. This happend with
> > mythtranscode, but maybe with other programs, too.
>
> Thank you for letting us know. Only yesterday I noticed a segfault in
> mythfilldatabase, the backtrace indicated the QApp destructor but I'd been
> able to narrow it down so you've saved me the trouble.

I wanted to confirm, that MythTV is almost unusable here with qt 3.3.8
on feisty. mythtranscode, mythfilldb, mythcommflag and the backend
keep crashing all the time.

Adam
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: Info: MythTV and QT 3.3.8 [ In reply to ]
On 03/10/2007 07:36 AM, Adam Egger wrote:
> On 3/8/07, Stuart Morgan <stuart@tase.co.uk> wrote:
>
>> On Thursday 8 March 2007 21:38:29 Herbert Graeber wrote:
>>
>>> A short description of the problem: Trolltech add a cleanup of the mysql
>>> (and proably other modules) to the QApplication destructor. If the mysql
>>> plugin is already unloaded this will relut in a segfault. This happend with
>>> mythtranscode, but maybe with other programs, too.
>>>
>> Thank you for letting us know. Only yesterday I noticed a segfault in
>> mythfilldatabase, the backtrace indicated the QApp destructor but I'd been
>> able to narrow it down so you've saved me the trouble.
>>
> I wanted to confirm, that MythTV is almost unusable here with qt 3.3.8
> on feisty. mythtranscode, mythfilldb, mythcommflag and the backend
> keep crashing all the time.

You sure that's the QT 3.3.8 bug and not some configuration issue on
your systems? Shouldn't the apps only segfault on shutdown (i.e. when
the QApplication destructor is run)? If the apps (especially
long-running apps like the backend) are crashing "all the time," it
would seem to indicate to me there's something else going on.

Mike
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: Info: MythTV and QT 3.3.8 [ In reply to ]
On 3/10/07, Michael T. Dean <mtdean@thirdcontact.com> wrote:
> You sure that's the QT 3.3.8 bug and not some configuration issue on
> your systems? Shouldn't the apps only segfault on shutdown (i.e. when
> the QApplication destructor is run)? If the apps (especially
> long-running apps like the backend) are crashing "all the time," it
> would seem to indicate to me there's something else going on.

Well, I use MythTv for several years now without ever having this kind
of issues. Two or three days ago the new QT 3.3.8 appeared on my
feisty and now I see crashing mythtranscode, mythfilldatabase etc all
the time (I just started the PC and see another crash report from
mythtranscode).

Adam
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: Info: MythTV and QT 3.3.8 [ In reply to ]
On Sunday 11 March 2007 19:28:50 Adam Egger wrote:
> Well, I use MythTv for several years now without ever having this kind
> of issues. Two or three days ago the new QT 3.3.8 appeared on my
> feisty and now I see crashing mythtranscode, mythfilldatabase etc all
> the time (I just started the PC and see another crash report from
> mythtranscode).

Mythtranscode and Mythfilldatabase crashing is expected but they are only
doing so after they have finished, at the point when they exit so it's not
too serious. I've not seen either mythbackend or mythfrontend segfault but
again, if they did it should be at the time they exit and not during use.

If you are seeing the backend or any other application crashing whilst in use,
then open a ticket with a backtrace.

From my understanding this is purely a QT bug and nothing to do with the way
Mythtv uses QT.
--
Stuart Morgan
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: Info: MythTV and QT 3.3.8 [ In reply to ]
Am Sonntag, 11. März 2007 schrieb Stuart Morgan:
> On Sunday 11 March 2007 19:28:50 Adam Egger wrote:
> > Well, I use MythTv for several years now without ever having this kind
> > of issues. Two or three days ago the new QT 3.3.8 appeared on my
> > feisty and now I see crashing mythtranscode, mythfilldatabase etc all
> > the time (I just started the PC and see another crash report from
> > mythtranscode).
>
> Mythtranscode and Mythfilldatabase crashing is expected but they are only
> doing so after they have finished, at the point when they exit so it's not
> too serious. I've not seen either mythbackend or mythfrontend segfault but
> again, if they did it should be at the time they exit and not during use.

In the case of mytharchive it is serious, because archiving will not continue
after mythtranscode crashes.

> If you are seeing the backend or any other application crashing whilst in
> use, then open a ticket with a backtrace.

Yes one should. In the special case handeled by this thread, it's Qts fault,
so no bug report ist neccessary and if somebody should report this, it can be
closed, with a hint to this Qt problem.

> From my understanding this is purely a QT bug and nothing to do with the
> way Mythtv uses QT.

That's how it is.

For SUSE users this has already been solved with the latest packets from the
KDE:KDE3 repositorty, the same source where you may have the bug from.

Cheers,
Herbert


_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: Info: MythTV and QT 3.3.8 [ In reply to ]
On Thursday 8 March 2007 21:38:29 Herbert Graeber wrote:
> Hello MythTV-Developers!
>
> I want to inform you that mythtranscode doesn't work with Qt 3.3.8.
>
> An user of my openSUSE MythTV packages on packman discovered this and file
> a bug on SUSE bug tracker.
>
> Meanwhile SUSE has fixed this issue, but it may last some time until the
> fix will reach the KDE:KDE3 repositiory. I think Dirk Mueller from SUSE has
> send a bug report to Trolltech.
>
> A short description of the problem: Trolltech add a cleanup of the mysql
> (and proably other modules) to the QApplication destructor. If the mysql
> plugin is already unloaded this will relut in a segfault. This happend with
> mythtranscode, but maybe with other programs, too.


The QT bug tracker page for this issue:
http://www.trolltech.com/developer/task-tracker/index_html?id=154194&method=entry

A fix is scheduled for 3.3.9 - As QT 3 reaches end of life in July they may
not release it until then? I expect some packagers will backport a fix if
asked before that release.

--
Stuart Morgan
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
Re: Info: MythTV and QT 3.3.8 [ In reply to ]
On 3/11/07, Herbert Graeber <lists@graeber-clan.de> wrote:
>
> Am Sonntag, 11. März 2007 schrieb Stuart Morgan:
> > On Sunday 11 March 2007 19:28:50 Adam Egger wrote:
> > > Well, I use MythTv for several years now without ever having this kind
> > > of issues. Two or three days ago the new QT 3.3.8 appeared on my
> > > feisty and now I see crashing mythtranscode, mythfilldatabase etc all
> > > the time (I just started the PC and see another crash report from
> > > mythtranscode).
> >
> > Mythtranscode and Mythfilldatabase crashing is expected but they are
> only
> > doing so after they have finished, at the point when they exit so it's
> not
> > too serious. I've not seen either mythbackend or mythfrontend segfault
> but
> > again, if they did it should be at the time they exit and not during
> use.
>
> In the case of mytharchive it is serious, because archiving will not
> continue
> after mythtranscode crashes.
>
> > If you are seeing the backend or any other application crashing whilst
> in
> > use, then open a ticket with a backtrace.
>
> Yes one should. In the special case handeled by this thread, it's Qts
> fault,
> so no bug report ist neccessary and if somebody should report this, it can
> be
> closed, with a hint to this Qt problem.
>
> > From my understanding this is purely a QT bug and nothing to do with the
> > way Mythtv uses QT.
>
> That's how it is.
>
> For SUSE users this has already been solved with the latest packets from
> the
> KDE:KDE3 repositorty, the same source where you may have the bug from.



Can you tell us where to exactly find this patch? Or attach it here?


Cheers,
> Herbert
>
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev@mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>



--
Doug Goldstein
Gentoo Linux Developer
http://dev.gentoo.org/~cardoe/
Re: Info: MythTV and QT 3.3.8 [ In reply to ]
Doug Goldstein schrieb:
> On 3/11/07, Herbert Graeber <lists@graeber-clan.de> wrote:
>>
>> Am Sonntag, 11. März 2007 schrieb Stuart Morgan:
>> > On Sunday 11 March 2007 19:28:50 Adam Egger wrote:
>> > > Well, I use MythTv for several years now without ever having this
>> kind
>> > > of issues. Two or three days ago the new QT 3.3.8 appeared on my
>> > > feisty and now I see crashing mythtranscode, mythfilldatabase etc all
>> > > the time (I just started the PC and see another crash report from
>> > > mythtranscode).
>> >
>> > Mythtranscode and Mythfilldatabase crashing is expected but they are
>> only
>> > doing so after they have finished, at the point when they exit so it's
>> not
>> > too serious. I've not seen either mythbackend or mythfrontend segfault
>> but
>> > again, if they did it should be at the time they exit and not during
>> use.
>>
>> In the case of mytharchive it is serious, because archiving will not
>> continue
>> after mythtranscode crashes.
>>
>> > If you are seeing the backend or any other application crashing whilst
>> in
>> > use, then open a ticket with a backtrace.
>>
>> Yes one should. In the special case handeled by this thread, it's Qts
>> fault,
>> so no bug report ist neccessary and if somebody should report this, it
>> can
>> be
>> closed, with a hint to this Qt problem.
>>
>> > From my understanding this is purely a QT bug and nothing to do with
>> the
>> > way Mythtv uses QT.
>>
>> That's how it is.
>>
>> For SUSE users this has already been solved with the latest packets from
>> the
>> KDE:KDE3 repositorty, the same source where you may have the bug from.
>
>
>
> Can you tell us where to exactly find this patch? Or attach it here?

The patch is contained in the Qt source RPM on SUSEs KDE:KDE3 repository
or form SUSE build service if you have registered there. For convenience
I attach it to this mail.

Cheers,
Herbert