Mailing List Archive

I can't comment on the sound but if you are running redhat 8 you can run up2date --solvedeps qt-MySQL
and that should fix the problem with QMYSQL3


----- Original Message -----
From: Justin
To: mythtv-users@snowman.net
Sent: Tuesday, March 18, 2003 8:33 PM
Subject: [mythtv-users] FW: odd error






-----Original Message-----
From: Justin [mailto:justhunt1234@rogers.com]
Sent: Tuesday, March 18, 2003 9:26 PM
To: 'mythtv-users-bounces@snowman.net'
Subject: odd error



Its just my luck to have this many problems. but here goes J when I run my mythfrontend I get a bunch of stuff about qsqldatabase and the driver not loaded. then it says it cant open db (I think I set it right.) . well heres what I get. neway



QSqlDatabase warning: QMYSQL3 driver not loaded

QSqlDatabase: available drivers:

QSqlDatabase warning: QMYSQL3 driver not loaded

QSqlDatabase: available drivers:

Couldn't open db

Mutex destroy failure: device or resource busy



? Im confused anyone help translate this to proper engrish.



Thanks allot. btw I can ping the backend and its running fine (it even runs mythfront end properly sept the sound card cant take full duplex)



Justin



------------------------------------------------------------------------------


_______________________________________________
mythtv-users mailing list
mythtv-users@snowman.net
http://www.snowman.net/mailman/listinfo/mythtv-users

Justin wrote:

> QSqlDatabase warning: QMYSQL3 driver not loaded
>
> QSqlDatabase: available drivers:
>
> QSqlDatabase warning: QMYSQL3 driver not loaded
>
> QSqlDatabase: available drivers:
>
> Couldn’t open db
>
> Mutex destroy failure: device or resource busy
>
> ? Im confused anyone help translate this to proper engrish.
>
Well, QsqlDatabase is QT's interface to databases, which MythTV uses. I
had this exact same error a couple days ago when (under gentoo) I had
compiled QT without support for MySQL. I recompiled with support for
mysql, and everything was happy.

Now, not knowing your distro, I can't say what exactly is causing this,
but it's a safe guess that it's a QT problem.

Graeme