An application using the MySQL driver may crash if the database is explicitly removed before QApplication is destroyed

[Mlt]

Binary package hint: kdebase

There are problems with the way that the QT libraries work with MySQL. This is causing great problems with MythTV packages and possibly others. However, it appears that this has been solved by the openSUSE maintainers.

The problems are described here: http://www.gossamer-threads.com/lists/mythtv/users/258369 and here: http://www.gossamer-threads.com/lists/mythtv/dev/257269#257269

The trolltech bug report is here: http://www.trolltech.com/developer/task-tracker/index_html?id=154194&method=entry

As this is a clear problem that has been solved elsewhere, would it be possible to use this solution for Feisty and not wait for Trolltech?

[Harald Sitter (apachelogger)]

Next time if you want to get something fixed - please report the bug against the right package and take the time to describe the problem. Mo one, really no one likes to read through hell long threads just to find out what problem he/she could be fixing here and how... which is also the reason no one looked at this bug.

[Michael Truscott (mltruscott)]

Sorry for the wrong call on the package - I can't claim to be any sort of
expert on package names, etc.

Thought I was helping with as much info as I could find so people wouldn't need
to ask bleedingly obvious questions...

On Saturday 23 August 2008 18:27:07 Harald Sitter wrote:
> Next time if you want to get something fixed - please report the bug
> against the right package and take the time to describe the problem. Mo
> one, really no one likes to read through hell long threads just to find
> out what problem he/she could be fixing here and how... which is also
> the reason no one looked at this bug.
>
> ** Changed in: kdebase (Ubuntu)
> Status: New => Fix Released

[Harald Sitter (apachelogger)]

You were helping, it isn't a useless report, but by definition everyone who triages bugs becomes lazy after some time, which explains why this bug didn't get any attention in over a year.

Especially in a package like kdebase the possibility that a developer will stumble upon the bug, unless it's status is confirmed/triaged, is pretty close to not existing at all.

So in order to get the fastest processing it's best to throw as many information in the description, no matter whether you understand it or not ;-)... if the bug triagers don't understand it either, but the description includes a lot of information, it's most likely that they will poke a developer right away :-)

[Michael Truscott (mltruscott)]

Cheers,

it looks like it got sorted via upstream anyway, so if you haven't anyway,
close the thing.

On Sunday 24 August 2008 21:23:04 Harald Sitter wrote:
> You were helping, it isn't a useless report, but by definition everyone
> who triages bugs becomes lazy after some time, which explains why this
> bug didn't get any attention in over a year.
>
> Especially in a package like kdebase the possibility that a developer
> will stumble upon the bug, unless it's status is confirmed/triaged, is
> pretty close to not existing at all.
>
> So in order to get the fastest processing it's best to throw as many
> information in the description, no matter whether you understand it or
> not ;-)... if the bug triagers don't understand it either, but the
> description includes a lot of information, it's most likely that they
> will poke a developer right away :-)