mythtv-setup: unable to connect to database

I tried a complete purge/reinstall cycle.
$ sudo aptitide --purge remove mythtv
$ sudo aptitude --purge remove mythtv-backend
$ sudo aptitude --purge remove mythtv-frontend
$ sudo aptitude --purge remove mythtv-common
$ sudo aptitude update
$ sudo aptitude upgrade
$ sudo aptitude install mythtv
$ mythtv-setup

I get the same behaviour.

NB: If I say OK to the "mythfilldatabase" popup prompt, I got the fllowing in an xterm titled "running mythfilldatabase"
-------------
2008-06-27 23:12:05.490 Using runtime prefix = /usr, libdir = /usr/lib
2008-06-27 23:12:05.491 Using localhost value of wellington
2008-06-27 23:12:05.497 New DB connection, total: 1
2008-06-27 23:12:05.500 Unable to connect to database!
2008-06-27 23:12:05.500 Driver error was [1/1045]:
QMYSQL3: Unable to connect
Database error was:
Access denied for user 'mythtv'@'localhost' (using password: YES)

QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
2008-06-27 23:12:05.550 DB Error (KickDatabase):
Query was:
SELECT NULL;
No error type from QSqlError? Strange...
QServerSocket: failed to bind or listen to the socket
2008-06-27 23:12:05.601 MCP::InitUPnP() - HttpServer Create Error
2008-06-27 23:12:05.601 Deleting UPnP client...
2008-06-27 23:12:05.601 No UPnP backends found

No UPnP backends found

Would you like to configure the database connection now? [yes]
Database host name: [localhost]
Should I test connectivity to this host using the ping command? [yes]
Database non-default port: [0]
Database name: [mythconverg]
Database user name: [mythtv]
Database password: [0ciB7wRh]
Unique identifier for this machine (if empty, the local host name will be used): [wellington]
Would you like to use Wake-On-LAN to retry database connections? [no]
2008-06-27 23:13:31.942 Unable to connect to database!
2008-06-27 23:13:31.942 Driver error was [1/1045]:
QMYSQL3: Unable to connect
Database error was:
Access denied for user 'mythtv'@'localhost' (using password: YES)

QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
2008-06-27 23:13:31.993 DB Error (KickDatabase):
Query was:
SELECT NULL;
No error type from QSqlError? Strange...
2008-06-27 23:13:32.043 Cannot login to database?
2008-06-27 23:13:32.043 Cannot login to database?

Cannot login to database?

Would you like to configure the database connection now? [yes]
------------
and so on, endlessly...

Vince McIntyre wrote:
> I tried a complete purge/reinstall cycle.
> $ sudo aptitide --purge remove mythtv
> $ sudo aptitude --purge remove mythtv-backend
> $ sudo aptitude --purge remove mythtv-frontend
> $ sudo aptitude --purge remove mythtv-common
> $ sudo aptitude update
> $ sudo aptitude upgrade
> $ sudo aptitude install mythtv
> $ mythtv-setup
>
> I get the same behaviour.
>
> NB: If I say OK to the "mythfilldatabase" popup prompt, I got the fllowing in an xterm titled "running mythfilldatabase"
> -------------
> 2008-06-27 23:12:05.490 Using runtime prefix = /usr, libdir = /usr/lib
> 2008-06-27 23:12:05.491 Using localhost value of wellington
> 2008-06-27 23:12:05.497 New DB connection, total: 1
> 2008-06-27 23:12:05.500 Unable to connect to database!
> 2008-06-27 23:12:05.500 Driver error was [1/1045]:
> QMYSQL3: Unable to connect
> Database error was:
> Access denied for user 'mythtv'@'localhost' (using password: YES)
>
> QSqlQuery::exec: database not open
> QSqlQuery::exec: database not open
> 2008-06-27 23:12:05.550 DB Error (KickDatabase):
> Query was:
> SELECT NULL;
> No error type from QSqlError? Strange...
> QServerSocket: failed to bind or listen to the socket
> 2008-06-27 23:12:05.601 MCP::InitUPnP() - HttpServer Create Error
> 2008-06-27 23:12:05.601 Deleting UPnP client...
> 2008-06-27 23:12:05.601 No UPnP backends found
>
> No UPnP backends found
>
> Would you like to configure the database connection now? [yes]
> Database host name: [localhost]
> Should I test connectivity to this host using the ping command? [yes]
> Database non-default port: [0]
> Database name: [mythconverg]
> Database user name: [mythtv]
> Database password: [0ciB7wRh]
> Unique identifier for this machine (if empty, the local host name will be used): [wellington]
> Would you like to use Wake-On-LAN to retry database connections? [no]
> 2008-06-27 23:13:31.942 Unable to connect to database!
> 2008-06-27 23:13:31.942 Driver error was [1/1045]:
> QMYSQL3: Unable to connect
> Database error was:
> Access denied for user 'mythtv'@'localhost' (using password: YES)
>
> QSqlQuery::exec: database not open
> QSqlQuery::exec: database not open
> 2008-06-27 23:13:31.993 DB Error (KickDatabase):
> Query was:
> SELECT NULL;
> No error type from QSqlError? Strange...
> 2008-06-27 23:13:32.043 Cannot login to database?
> 2008-06-27 23:13:32.043 Cannot login to database?
>
> Cannot login to database?
>
> Would you like to configure the database connection now? [yes]
> ------------
> and so on, endlessly...
>
The database is created by mythtv-database. You have to purge that and drop the
table made by that.

--
Mario Limonciello
<email address hidden>

$ sudo aptitude --purge remove mythtv-database
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages are BROKEN:
  mythtv
The following packages will be REMOVED:
  mythtv-database
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 279kB will be freed.
The following packages have unmet dependencies:
  mythtv: Depends: mythtv-database (= 0.21.0+fixes16838-0ubuntu3.1) but it is not installable
Resolving dependencies...
The following actions will resolve these dependencies:

Remove the following packages:
mythtv

Score is 119

Accept this solution? [Y/n/q/?]
The following packages are unused and will be REMOVED:
  libfame-0.9{p} libhtml-template-perl{p} liblzo1{p} libmjpegtools0c2a{p}
  libpvm3{p} mjpegtools{p} mysql-server{p} mysql-server-5.0{p}
  mythtv-backend{p} mythtv-themes{p} mythtv-transcode-utils{p} ntp{p}
  pvm{p} toolame{p} transcode{p} transcode-doc{p}
The following packages will be automatically REMOVED:
  mythtv
The following packages will be REMOVED:
  mythtv mythtv-database
0 packages upgraded, 0 newly installed, 18 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 101MB will be freed.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
(Reading database ... 150712 files and directories currently installed.)
Removing mythtv ...
(Reading database ... 150703 files and directories currently installed.)
Removing mythtv-backend ...
 * Stopping MythTV server: mythbackend [ OK ]
Purging configuration files for mythtv-backend ...
Removing mythtv-transcode-utils ...
Removing transcode ...
Removing libfame-0.9 ...
Purging configuration files for libfame-0.9 ...
Removing libhtml-template-perl ...
Removing liblzo1 ...
Purging configuration files for liblzo1 ...
Removing mjpegtools ...
Removing libmjpegtools0c2a ...
Purging configuration files for libmjpegtools0c2a ...
Removing pvm ...
Removing libpvm3 ...
Removing mysql-server ...
Removing mysql-server-5.0 ...
 * Stopping MySQL database server mysqld [ OK ]
Purging configuration files for mysql-server-5.0 ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
(Reading database ... 148202 files and directories currently installed.)
Removing mythtv-database ...
(Reading database ... 148189 files and directories currently installed.)
Removing mythtv-themes ...
Removing ntp ...
 * Stopping NTP server ntpd [ OK ]
Purging configuration files for ntp ...
Removing toolame ...
Removing transcode-doc ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
Building tag database... Done

(I said 'yes' when prompted about removing all mysql databases.)

~$ sudo aptitude install mytht...

Vince McIntyre wrote:
> $ sudo aptitude --purge remove mythtv-database
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Reading extended state information
> Initializing package states... Done
> Building tag database... Done
> The following packages are BROKEN:
> mythtv
> The following packages will be REMOVED:
> mythtv-database
> 0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> Need to get 0B of archives. After unpacking 279kB will be freed.
> The following packages have unmet dependencies:
> mythtv: Depends: mythtv-database (= 0.21.0+fixes16838-0ubuntu3.1) but it is not installable
> Resolving dependencies...
> The following actions will resolve these dependencies:
>
> Remove the following packages:
> mythtv
>
> Score is 119
>
> Accept this solution? [Y/n/q/?]
> The following packages are unused and will be REMOVED:
> libfame-0.9{p} libhtml-template-perl{p} liblzo1{p} libmjpegtools0c2a{p}
> libpvm3{p} mjpegtools{p} mysql-server{p} mysql-server-5.0{p}
> mythtv-backend{p} mythtv-themes{p} mythtv-transcode-utils{p} ntp{p}
> pvm{p} toolame{p} transcode{p} transcode-doc{p}
> The following packages will be automatically REMOVED:
> mythtv
> The following packages will be REMOVED:
> mythtv mythtv-database
> 0 packages upgraded, 0 newly installed, 18 to remove and 0 not upgraded.
> Need to get 0B of archives. After unpacking 101MB will be freed.
> Do you want to continue? [Y/n/?]
> Writing extended state information... Done
> (Reading database ... 150712 files and directories currently installed.)
> Removing mythtv ...
> (Reading database ... 150703 files and directories currently installed.)
> Removing mythtv-backend ...
> * Stopping MythTV server: mythbackend [ OK ]
> Purging configuration files for mythtv-backend ...
> Removing mythtv-transcode-utils ...
> Removing transcode ...
> Removing libfame-0.9 ...
> Purging configuration files for libfame-0.9 ...
> Removing libhtml-template-perl ...
> Removing liblzo1 ...
> Purging configuration files for liblzo1 ...
> Removing mjpegtools ...
> Removing libmjpegtools0c2a ...
> Purging configuration files for libmjpegtools0c2a ...
> Removing pvm ...
> Removing libpvm3 ...
> Removing mysql-server ...
> Removing mysql-server-5.0 ...
> * Stopping MySQL database server mysqld [ OK ]
> Purging configuration files for mysql-server-5.0 ...
> Processing triggers for libc6 ...
> ldconfig deferred processing now taking place
> (Reading database ... 148202 files and directories currently installed.)
> Removing mythtv-database ...
> (Reading database ... 148189 files and directories currently installed.)
> Removing mythtv-themes ...
> Removing ntp ...
> * Stopping NTP server ntpd [ OK ]
> Purging configuration files for ntp ...
> Removing toolame ...
> Removing transcode-doc ...
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Reading extended state information
> Initializing package states... Done
> Writing e...

I installed MythTV first time yesterday (from repository). Setup failed because mythtv user was not added into mysql users and database mythconverg was not created.

After creating user and db manually I was able to continue the setup process and go the MythTV up and running.

Ps. Oh, totally forgot that I had to start MySQL first before adding user and db manually (so installation process didn't check that).

Anylo wrote:
> Ps. Oh, totally forgot that I had to start MySQL first before adding
> user and db manually (so installation process didn't check that).
>
Please specify the answers you provided to ALL debconf questions during install,
and did you have any mysql components already installed?

Eg did you get asked for a root password, and did you skip it or give something.
 If you gave something just indicate that you gave a password with alphanumeric
characters, or a password including non alphanumeric characters or no password.

--
Mario Limonciello
<email address hidden>

I'm 98% sure that I answered all the questions during installation.

I'm not sure was the MySQL installed before or was this the first time (asking db root passwd while installing means that it was?). Anyway, MySQL was not running after installation.

When it asked root password I gave something which has numbers, letters (including capitals) and % sign.

ugh - i hate launchpad. it just lost my entire post.

I went back through my notes. They leave a little to be desired...

At the time I installed the "mythtv" metapackage, I did not have support for my DVB-T card working.
It is a Dvico model that is not yet supported by the mainline v4l tree. (I got it working with the branch
made available by Chris Pascoe back in December 2007).
So, I would probably have answered many debconf questions by taking the default.
I don't think I would have given unusable inputs.

I would not have had mysql-5.0-server installed at the time, I would have let the installation of mythtv
pull it in as a dependency.

My notes tell me:
 * I installed "mythtv" and debconf told me I need to run "mythtv-setup" as a member of the mythtv group.
 * I added my unpriviledged account to that group
 * I ran sudo /etc/init.d/mythtv-backend start
    I answered "no" to the question about "remote access"
 * I installed mythexport
 * I installed mythwe
    I did not set a mythweb password.
 * Something prompted me for a "mythtv p/w", which was stored in /etc/mythtv/mysql.txt.
    This appears to be the user for the mythtv tables in the database.
    I do not recall getting prompted for a mysql 'administrator/root' user at this time;
    my notes would have recorded the password.
 * I ran dpkg-reconfigure lirc

I also went and poked at my debconf database; below I show the output of
  debconf-get-selections | grep -A 0 -B 1 mythtv;
  debconf-get-selections | grep -A 0 -B 1 mysql
Most of these would be the original answers; the only dpkg-reconfigure changes I have made
should be in the posts I have already made to this bug.
In particular - mythtv-common:mythtv/mysql_mythtv_password was the value I have in my notes on paper,
but mythtv-database:mythtv/mysql_admin_password is the value I set when I ran dpkg-reconfigure.
I don't recall having to set it before and would not have used the same value.

Hope this sheds some light.
Vince

------------------ debconf data ---------------
$ debconf-get-selections | grep -A 0 -B 1 mythtv;
# What password should MythTV use to access its database:
mythtv-common mythtv/mysql_mythtv_password password <elided>
--
# What is the password for the MySQL administrator account 'root':
mythtv-database mythtv/mysql_admin_password password <elided>
--
# Choices: NTSC, PAL, SECAM, PAL-NC, PAL-M, PAL-N, NTSC-JP
mythtv-common mythtv/tv_format select NTSC
--
# Update the system MOTD?
mythtv-status mythtv-status/enable boolean true
--
# A backup of your database will be made
mythtv-database mythtv/backup_db note
--
# What is the name of the MySQL administrator account:
mythtv-database mythtv/mysql_admin_user string root
--
# Is it OK to create the video4linux device nodes?
mythtv-backend mythtv/create_v4l_devs boolean true
--
# Will you be using other computers running MythTV?
mythtv-database mythtv/public_bind boolean false
--
# Warning! These packages are experimental! Install?
mythtv-common mythtv/svn_warning boolean
--
# The Ubuntu MythTV packages generate a random MySQL password.
mythtv-common mythtv/display_password note
# On what host does...

I am also running into this issue of not being able to complete the backend setup. If there is any trace information that will help in capturing more information I would be happy to assist. In my case I get the following:

QMYSQL3: Unable to connect
QMYSQL3: Can't connect to MySQL server on 'bains-homepc' (111)

I checked permissions on mythconverg database for user 'mythtv' to ensure I could not login and query the database to rule out acccess issues.

During one purge and reinstall cycle I got access denied for mythtv user so I granted permissions using the command below:

mysql> grant all on mythconverg.* to mythtv@"192.168.1.%" identified by "mythtv";
mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)

Attached are screenshots of setup error and error during mythfilldatabase and the log complete removal and reinstall of mythtv.

Any assistance in helping the setup forward would be appreciated. I am trying to move away from Windows on home pc.

So in solving this:

superm1> kirkland, well so what it needs to do is first try no password, and then if it needs to (and has the ability to, say when you are in a non-noninteractive debconf frontend) ask the password question
<superm1> and if the password question fails, keep at it until the person aborts or puts the right password
<Daviey> ... and if fails - leave the package in unconfigured state
<superm1> it's important that only happens in interactive debconf frontends though... otherwise the livefs will definitely have broken mythbuntu installs too

Patch attached. Tested, seems to work for me. Should be tested to ensure that it works properly in noninteractive debconf mode.

:-Dustin

Committed to bzr. There are a few other things to fix in the
maintainer scripts, so IT will be a few more commits until this is fix
released.

On 12/12/2008, Dustin Kirkland <email address hidden> wrote:
> Patch attached. Tested, seems to work for me. Should be tested to
> ensure that it works properly in noninteractive debconf mode.
>
> :-Dustin
>
> ** Attachment added: "243504.debdiff"
> http://launchpadlibrarian.net/20392913/243504.debdiff
>
> --
> mythtv-setup: unable to connect to database
> https://bugs.launchpad.net/bugs/243504
> You received this bug notification because you are a member of MythTV
> Ubuntu Maintainers, which is subscribed to mythtv in ubuntu.
>

--
Sent from my mobile device

Mario Limonciello
<email address hidden>

This bug was fixed in the package mythtv - 0.21.0+fixes19136-0ubuntu1

---------------
mythtv (0.21.0+fixes19136-0ubuntu1) jaunty; urgency=low

  [ Thomas Mashos ]
  * Updated posters dir to /var/lib/mythtv/posters

  [ Michael Haas ]
  * New upstream snapshot.
  * Added size restriction to frontend and backend logs (10M)
    - (LP: #250776)
  * debian/patches:
    - Add 29_mythwelcome_fix.dpatch to prevent MythWelcome from quitting
      spuriously (backports revision 18671 from trunk)

  [ Dustin Kirkland ]
  * debian/mythtv-database.config: test the validity of the input mysql
    passphrase, up to 5 times (LP: #243504)

  [ Mario Limonciello ]
  * debian/mythtv-database.postinst:
    - Clean up old code calls
    - Adjust for changes to .config
    - Make sure to clear root password
  * debian/mythtv-common.config:
    - Read mysql.txt before starting
  * debian/mythtv-common.postinst:
    - Clean up old file checks that are unnecessary.

 -- Mario Limonciello <email address hidden> Sat, 13 Dec 2008 18:39:01 -0600

> This bug was fixed in the package mythtv - 0.21.0+fixes19136-0ubuntu1

Can I download a .deb containing this fix from somewhere, or do I need to update my apt repository sources?

Hi Frank:

If you are on Jaunty, you will get the fixes immediately. We'll likely do a
backport at some point too, but no ETA as to when.

On Mon, Dec 15, 2008 at 19:22, Frank Lynch <email address hidden> wrote:

> > This bug was fixed in the package mythtv - 0.21.0+fixes19136-0ubuntu1
>
> Can I download a .deb containing this fix from somewhere, or do I need
> to update my apt repository sources?
>
> --
> mythtv-setup: unable to connect to database
> https://bugs.launchpad.net/bugs/243504
> You received this bug notification because you are a member of MythTV
> Ubuntu Maintainers, which is subscribed to mythtv in ubuntu.
>

--
Mario Limonciello
<email address hidden>

Thanks Mario.
I was hoping to stay on a stable distro & myth build. I guess I'll just hack
at my config and manually setup the db for now.
Is there anything that I can do to help with the backport? I've built mythtv
from source in the past and would be happy to help do this if I can.

On Mon, Dec 15, 2008 at 8:37 PM, Mario Limonciello <email address hidden>wrote:

> Hi Frank:
>
> If you are on Jaunty, you will get the fixes immediately. We'll likely do
> a
> backport at some point too, but no ETA as to when.
>
> On Mon, Dec 15, 2008 at 19:22, Frank Lynch <email address hidden>
> wrote:
>
> > > This bug was fixed in the package mythtv - 0.21.0+fixes19136-0ubuntu1
> >
> > Can I download a .deb containing this fix from somewhere, or do I need
> > to update my apt repository sources?
> >
> > --
> > mythtv-setup: unable to connect to database
> > https://bugs.launchpad.net/bugs/243504
> > You received this bug notification because you are a member of MythTV
> > Ubuntu Maintainers, which is subscribed to mythtv in ubuntu.
> >
>
>
> --
> Mario Limonciello
> <email address hidden>
>
> --
> mythtv-setup: unable to connect to database
> https://bugs.launchpad.net/bugs/243504
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Well the DB setup should all work for the most part usually. This just
helps cover more corner cases. You should be able to get by by setting a
root password with

dpkg-reconfigure mysql-server-5.0

and then setup a db using

dpkg-reconfigure mythtv-database

On Mon, Dec 15, 2008 at 20:03, Frank Lynch <email address hidden> wrote:

> Thanks Mario.
> I was hoping to stay on a stable distro & myth build. I guess I'll just
> hack
> at my config and manually setup the db for now.
> Is there anything that I can do to help with the backport? I've built
> mythtv
> from source in the past and would be happy to help do this if I can.
>
>
> On Mon, Dec 15, 2008 at 8:37 PM, Mario Limonciello <<email address hidden>
> >wrote:
>
> > Hi Frank:
> >
> > If you are on Jaunty, you will get the fixes immediately. We'll likely
> do
> > a
> > backport at some point too, but no ETA as to when.
> >
> > On Mon, Dec 15, 2008 at 19:22, Frank Lynch <email address hidden>
> > wrote:
> >
> > > > This bug was fixed in the package mythtv - 0.21.0+fixes19136-0ubuntu1
> > >
> > > Can I download a .deb containing this fix from somewhere, or do I need
> > > to update my apt repository sources?
> > >
> > > --
> > > mythtv-setup: unable to connect to database
> > > https://bugs.launchpad.net/bugs/243504
> > > You received this bug notification because you are a member of MythTV
> > > Ubuntu Maintainers, which is subscribed to mythtv in ubuntu.
> > >
> >
> >
> > --
> > Mario Limonciello
> > <email address hidden>
> >
> > --
> > mythtv-setup: unable to connect to database
> > https://bugs.launchpad.net/bugs/243504
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> mythtv-setup: unable to connect to database
> https://bugs.launchpad.net/bugs/243504
> You received this bug notification because you are a member of MythTV
> Ubuntu Maintainers, which is subscribed to mythtv in ubuntu.
>

--
Mario Limonciello
<email address hidden>

Thanks Mario, I manually ran the mythtv sql scripts and have everthing
working nicely.
Cheers,
--Frank

On 12/16/08, Mario Limonciello <email address hidden> wrote:
> Well the DB setup should all work for the most part usually. This just
> helps cover more corner cases. You should be able to get by by setting a
> root password with
>
> dpkg-reconfigure mysql-server-5.0
>
> and then setup a db using
>
> dpkg-reconfigure mythtv-database
>
>
> On Mon, Dec 15, 2008 at 20:03, Frank Lynch <email address hidden> wrote:
>
>> Thanks Mario.
>> I was hoping to stay on a stable distro & myth build. I guess I'll just
>> hack
>> at my config and manually setup the db for now.
>> Is there anything that I can do to help with the backport? I've built
>> mythtv
>> from source in the past and would be happy to help do this if I can.
>>
>>
>> On Mon, Dec 15, 2008 at 8:37 PM, Mario Limonciello <<email address hidden>
>> >wrote:
>>
>> > Hi Frank:
>> >
>> > If you are on Jaunty, you will get the fixes immediately. We'll likely
>> do
>> > a
>> > backport at some point too, but no ETA as to when.
>> >
>> > On Mon, Dec 15, 2008 at 19:22, Frank Lynch <email address hidden>
>> > wrote:
>> >
>> > > > This bug was fixed in the package mythtv -
>> > > > 0.21.0+fixes19136-0ubuntu1
>> > >
>> > > Can I download a .deb containing this fix from somewhere, or do I need
>> > > to update my apt repository sources?
>> > >
>> > > --
>> > > mythtv-setup: unable to connect to database
>> > > https://bugs.launchpad.net/bugs/243504
>> > > You received this bug notification because you are a member of MythTV
>> > > Ubuntu Maintainers, which is subscribed to mythtv in ubuntu.
>> > >
>> >
>> >
>> > --
>> > Mario Limonciello
>> > <email address hidden>
>> >
>> > --
>> > mythtv-setup: unable to connect to database
>> > https://bugs.launchpad.net/bugs/243504
>> > You received this bug notification because you are a direct subscriber
>> > of the bug.
>> >
>>
>> --
>> mythtv-setup: unable to connect to database
>> https://bugs.launchpad.net/bugs/243504
>> You received this bug notification because you are a member of MythTV
>> Ubuntu Maintainers, which is subscribed to mythtv in ubuntu.
>>
>
>
> --
> Mario Limonciello
> <email address hidden>
>
> --
> mythtv-setup: unable to connect to database
> https://bugs.launchpad.net/bugs/243504
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Sent from my mobile device