Gentoo Archives: gentoo-amd64

From: Brett Johnson <brett@××××.com>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] mythfrontend on AMD64 - will it work with qt-4? (cannot connect to database)
Date: Tue, 15 May 2007 12:32:18
Message-Id: 20070515122943.GH11545@blzj.com
In Reply to: [gentoo-amd64] mythfrontend on AMD64 - will it work with qt-4? (cannot connect to database) by Mark Knecht
1 On Mon, May 14, 2007 at 07:59:52PM -0700, Mark Knecht wrote:
2 > Hi,
3 > I'm in the early stages of a complete MythTV update across my
4 > network. I have the backend nearly working in an IA32 machine. It runs
5 > fine but isn't getting all the channels correctly yet. In parallel
6 > with that effort I'm trying to get the frontend working again on my
7 > AMD64 machine.
8 >
9 > However when I try to start the frontend it complains like this:
10 >
11 > mark@lightning ~ $ mythfrontend --geometry 800x600
12 > 2007-05-14 19:56:19.577 Using runtime prefix = /usr
13 > 2007-05-14 19:56:19.585 DPMS is active.
14 > QSqlDatabase: QMYSQL3 driver not loaded
15 > QSqlDatabase: available drivers:
16 > 2007-05-14 19:56:19.595 New DB connection, total: 1
17 > 2007-05-14 19:56:19.595 Unable to connect to database!
18 > 2007-05-14 19:56:19.596 No error type from QSqlError? Strange...
19 > QSqlQuery::exec: database not open
20 > QSqlQuery::exec: database not open
21 > 2007-05-14 19:56:19.646 DB Error (KickDatabase):
22 > Query was:
23 > SELECT NULL;
24 > No error type from QSqlError? Strange...
25 >
26 >
27 First, I believe MythTV still required QT3. The QT package is slotted,
28 so you should be able to have both 3 and 4 installed. If you upgraded
29 MySQL on the AMD64 box, you may want to rebuild QT3 with something like
30 emerge -av =dev-libs/qt3*
31
32 If that doesn't fix it, it sounds like it could be a password encryption
33 problem. I had a similar problem when I tried using a RHEL box as a
34 front end. The RHEL distribution only supported MySQL 4.0.x and my back
35 end DB is MySQL 5.x. I could connect fine from the command line, but the
36 front end could not. After a bit of research I determined it was a
37 password encryption problem. I decided the easiest solution for me was to
38 create a second account for the mythconverg DB and encrypt the password
39 using the old_password function. You can also upgrade the client to 5.x.
40 If it's already at 5.x you may need to re-encrypt the password for the
41 account.
42
43 You may want to look at
44 http://dev.mysql.com/doc/refman/5.0/en/old-client.html
45 and try some of the suggestions.
46
47 Hope this helps.
48
49 Brett
50 --
51 gentoo-amd64@g.o mailing list

Replies