[03:54] <qwebirc97069> Morning all
[03:55] <qwebirc97069> I have mythtv .25 fixes installed from the standard Ubuntu repos on a Mint Mate 14 x64 setup
[03:55] <qwebirc97069> I want to try .26 fixes and to this end installed mythbuntu-control-centre (MCC)
[03:56] <qwebirc97069> however using MCC gives me a Exception in captureState of plugin Repositories error at startup
[03:57] <qwebirc97069> followed by a disabling plugins message
[03:57] <qwebirc97069> running MCC from the command line......
[03:57] <tgm4883> qwebirc97069, you want to enable https://launchpad.net/~mythbuntu/+archive/0.26
[03:57] <tgm4883> qwebirc97069, it's failing because you are using mint
[04:01] <qwebirc97069> OK, it'd be useful if this was flagged on the http://www.mythbuntu.org/home/news known issues page?
[04:01] <tgm4883> qwebirc97069, that it doesn't work with mint? I think that would be kinda obvious
[04:01] <qwebirc97069> Why would that be obvious?
[04:02] <tgm4883> because mint != ubuntu?
[04:02] <qwebirc97069> Mint mate 14 is based on Ub 12.10
[04:02] <tgm4883> qwebirc97069, when you do 'lsb_release -a' in the terminal, what does it say
[04:03] <tgm4883> it should say 12.10 or something like that
[04:03] <tgm4883> possibly quantal
[04:03] <qwebirc97069> It says
[04:04] <qwebirc97069> no lsb modules avail
[04:04] <qwebirc97069> linuxmint
[04:04] <tgm4883> heh, even better
[04:04] <tgm4883> so when I query the distro in python, it says whatever mistress that mint is named after
[04:05] <qwebirc97069> Notwithstanding it would still be useful to flag this on the known issues page,
[04:05] <tgm4883> qwebirc97069, I still don't see why Mint failing to report it is 12.10 is a Mythbuntu issue
[04:05] <tgm4883> granted, i'm willing to fix the issue
[04:05] <qwebirc97069> Thanks
[04:05] <tgm4883> and it will likely be fixed for 13.10
[04:06] <qwebirc97069> I accept it's a Mint issue but still making life easier for users means we all win?
[04:06] <qwebirc97069> And mint has had great pickup over the last 12 months
[04:06] <qwebirc97069> I switched from Fedora as I couldn't live with Gnome 3
[04:07] <qwebirc97069> Anyway thanks for the info and I'll install the repo manually
[18:44] <DarthFrog> Good day folks.
[18:46] <DarthFrog> How do I enable remote connections to my Myth MySql datatbase without using mythbuntu-control-centre? (Cuz it crashes with a python/aptdaemon bug).  I've set the connection key to 0000 in mythtv-setup on the remote backend but am still getting connection refused (i.e. telnet 192.168.1.100 3306)
[18:47] <tgm4883> DarthFrog, you probably need to set mysql to accept connections on the regular interface (not localhost)
[18:48] <DarthFrog> Thanks, I'll try that.
[18:48] <tgm4883> DarthFrog, http://www.mythtv.org/wiki/Tune_MySQL
[18:48] <tgm4883> DarthFrog, if you just do the bind_address part of that, it should work
[18:54] <DarthFrog> tgm4883:  It seems to have, thanks.
[18:54] <DarthFrog> At least now I get a database schema inconsistency message. :-)
[18:56] <DarthFrog> that's when running mythfrontend.  But using mythbuntu-control-centre, the mysql test connection still fails. :-(
[18:56] <tgm4883> DarthFrog, did you do an upgrade?
[18:58] <DarthFrog> I'm running 0.27 on the backend.  Currently 0.25 on the frontend.  But i can't upgrade the frontend to 0.27 cuz when I click on the Apply button after changing repos, it bitches about mysql not being properly filled out.
[18:58] <tgm4883> wonky
[18:58] <tgm4883> personally, I've never liked the mysql tab in MCC
[18:58] <DarthFrog> I'm beginning to despise MCC.
[18:59] <DarthFrog> 2013-03-14 11:58:26.229655 E [4004] Python Database Connection Database schema mismatch: we speak 1299 but database speaks 1310
[18:59] <tgm4883> DarthFrog, IIRC it doesn't like 0000
[18:59] <tgm4883> superm1, ^
[19:03] <DarthFrog> That seems a bad behaviour.  it's not that the system can't connect, but the mismatch prevents MCC from doing anything about it.  MCC just gives a red X without any details or opportunities to solve problems.
[19:03] <DarthFrog> It should at least offer an error log.
[19:04] <DarthFrog> And since it blocks MCC from doing anything else, I can't use MCC to update the client to the correct version (which is what my end goal was to start with).
[19:06] <DarthFrog> Oh flaming hell, now I can't even do it manually!
[19:06] <Zinn> DarthFrog: Please watch your language.
[19:06] <DarthFrog> libmyth-0.27-0 : Depends: libc6 (>= 2.17) but 2.15-0ubuntu20 is to be installed
[19:06] <DarthFrog>                   Depends: libfftw3-double3 but it is not installable
[19:06] <DarthFrog>                   Depends: libfftw3-single3 but it is not installable
[19:07] <DarthFrog> Oops, PEBKAC!  :-)  In the immortal words of Emily Litella, "Nevermind!"
[19:09] <DarthFrog> It does help if I install the packages intended for Quantal, rather than Raring. :-)  Ready, Fire, Aim!
[19:19] <DarthFrog> Gack!  The IPv4 address in mythtv-setup is immutable in Raring. :-(
[19:22] <tgm4883> DarthFrog, that doesn't seem good
[19:22] <tgm4883> DarthFrog, let me test that
[19:22] <DarthFrog> it's kinda showstopper.
[19:22] <tgm4883> DarthFrog, using 0.27?
[19:22] <DarthFrog> yes
[19:22] <tgm4883> Ubuntu+mythtv?
[19:22] <DarthFrog> Did a dist-upgrade today.
[19:23] <DarthFrog> kubuntu
[19:23] <tgm4883> ok, I've got a Ubuntu 13.04 install, let me boot it
[19:23] <tgm4883> this is just in step 1 of mythtv-setup?
[19:23] <DarthFrog> Yes.
[19:23] <tgm4883> ok sec
[19:23] <DarthFrog> First field, first page.
[19:23] <DarthFrog> I could change the master backend address, but tnot the local address.
[19:25] <tgm4883> DarthFrog, ok. Installing now
[19:30] <tgm4883> DarthFrog, can you not type in the field at all, or is the info not saved?
[19:32] <DarthFrog> The field is immutable.  It does drop down a box with 127.0.0.1 as if it were offering a pick list.  But I cannot edit or change anything.   It issues a haughty laugh in my general direction.
[19:33] <tgm4883> 0.26 seems fine. Let me update to 0.27
[19:34] <tgm4883> actually, let me grab kubuntu first
[19:43] <tgm4883> kubuntu seems fine, upgrading to 0.27
[19:52] <tgm4883> DarthFrog, seems it is by design, and also probably a bug
[19:52] <DarthFrog> OK, that's odd.  the IPv6 drop-down picklist offers addresses for localhost (::1), and the IPv6 addresses on my ethernet card and VirtualBox virtual NIC.
[19:53] <DarthFrog> tgm4883:  It would seem that it's not picking up the addresses from my NICs.
[19:53] <tgm4883> DarthFrog, yea, it's suppose to list valid IP addresses
[19:54] <DarthFrog> OK, should I file a bug report?
[19:54] <DarthFrog> It's also blocking a remote mythtfrontend connection.
[19:56] <DarthFrog> tgm4883: BTW, did it behave properly with 0.27 in Quantal/Precise?
[19:56] <tgm4883> DarthFrog, yea file a bug on it. I'm looking at the code, but I only know python so probably won't be much help
[19:56]  * tgm4883 shrugs
[19:56] <DarthFrog> or whatever you're running?
[19:56] <tgm4883> i'm running 0.26 ;)
[19:56] <DarthFrog> I see. :-)
[19:57] <DarthFrog> I'm trying to get my Hauppague HD-PVRs working, so I wanted the latest 'n greatest.
[19:57] <DarthFrog> So far, it's working great. :-)
[20:00] <superm1> DarthFrog: did you not upgrade libmyth-python
[20:00] <DarthFrog> superm1: I did a dist-upgrade today.
[20:01] <superm1> DarthFrog: can you compare the libmyth-python version with the mythtv-common version then? make sure it didn't get restricticed from the upgrade for whatever reason
[20:01] <superm1> (unresolvable deps or something)
[20:05] <DarthFrog> superm1:  They're both 0.27-0
[20:05] <DarthFrog> libmyth-python      2:0.27.0~maste all            A python library to access some MythTV feat
[20:05] <DarthFrog>  mythtv-common       2:0.27.0~maste amd64          Personal video recorder application (common
[20:09] <superm1> interesting
[20:09] <superm1> well it could be a bug in mythtv 0.27 then, because we are just reusing htat API
[20:10] <DarthFrog> superm1:  It seems to be ignoring valid IPv4 addresses.
[20:10] <DarthFrog> Works for IPv6 though.
[20:10] <superm1> oh really, then that's more peculiar
[20:11] <tgm4883> superm1, I'm pinging wagnerrp on it, he might know of a bug in 0.27
[20:11] <tgm4883> superm1, mythtv-setup is ignoring valid IPv4 addresses it seems
[20:13] <superm1> if you can reproduce using http://paste.ubuntu.com/5614656/
[20:13] <superm1> then it's certainly a bug in mythtv bindings
[20:20] <DarthFrog> superm1: Your script didn't work.  http://paste.ubuntu.com/5614685/
[20:22] <tgm4883> DarthFrog, on line 3, take out 'self, '
[20:23] <DarthFrog> Returns nothing.
[20:24] <superm1> oops it was lifted from some other code
[20:24] <tgm4883> DarthFrog, try making line 20
[20:24] <tgm4883> print do_connection_test('0000')
[20:24] <superm1> yeah what tgm4883 said
[20:25] <DarthFrog> Returns "None".
[20:25] <tgm4883> I think it worked then
[20:26] <tgm4883> It would return false or an error string if it failed
[20:26] <tgm4883> superm1, it doesn't return on success?
[20:27] <tgm4883> superm1, after line 16, should it return True?
[20:27] <DarthFrog> I've tried setting the localhost address to 192.168.1.100 in /etc/hosts with no results.
[21:59] <DarthFrog> Woo hoo, a bug-fix release of aptdaemon that is supposed to fix the problem with mythbuntu-control-centre in Raring. :-)
[22:00] <DarthFrog> Not in the repos yet, darn it.