[02:23] <adub> hi guys is there a way to have pulse to not interfere with myth
[02:23] <adub> my hdmi sound is not working and someone said this could be the cuase
[03:06] <superm1> kees, would you mind glancing over bug 728371?
[03:06] <Zinn> Bug 728371 in mythbuntu-live-autostart (Ubuntu) "MythTV setup failed with "Cannot login"" [Critical, Confirmed] http://www.launchpad.net/bugs/728371
[03:06] <superm1> i'm at a bit^D^D^Dmajor loss what's going on.  the code for configuring a database hasn't changed in ages, but for some reason it doesn't seem to work anymore.  mysql doesn't get spawned in a chroot properly
[03:07] <superm1> all sorts of peculiar errors like non-accessible hardlink creation was attempted by: mysqld (fsuid 102)
[03:08] <superm1> this is the code in particular that's being ran: http://bazaar.launchpad.net/~mythbuntu-dev/mythbuntu/mythbuntu-live-autostart/view/head:/ubiquity/plugins/myth-install-type.py#L147
[03:08] <Zinn> [bazaar.launchpad.net] ~mythbuntu-dev/mythbuntu/mythbuntu-live-autostart : contents of ubiquity/plugins/myth-install-type.py at revision 147
[03:13] <kees> superm1: sure, in a bit. something funny must be going on. hardlink restrictions were in maverick without this problem hmmm
[03:17] <kees> why do people insist on putting things in chroots?
[03:18] <kees> superm1: that reconfigure doesn't fail if run manually?
[03:19] <kees> oh that's the install chroot. got it
[03:36] <kees> link() isn't called anywhere in the mysql code (it uses rename()). so weird
[04:07] <fluvvell> !help broadband
[04:07] <Zinn> !help broadband For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[05:32] <superm1> kees, hmm.  could this have something to do with upstart's plans to grow support for chroots in some fashion?
[05:32] <superm1> i'm not sure if that eventually happened
[05:32] <superm1> gah.... https://launchpad.net/ubuntu/+source/upstart/0.9.0-1ubuntu3
[05:32] <Zinn> [launchpad.net] 0.9.0-1ubuntu3 : âupstartâ package : Ubuntu
[05:33] <superm1> and that explains why this is a fairly recent phenomena
[05:52] <kees> superm1: it's really strange regardless. what's the easiest way for me to reproduce the issue locally?
[05:53] <superm1> kees, grab a3 mythbuntu and do an install is the easiest
[05:53] <superm1> i think what's happening is that the upstart managed job from the chroot spits it's /var/run/mysqld/mysql.sock outside the chroot
[05:53] <superm1> so stuff launchedi n the chroot doesn't know about it
[05:54] <superm1> once you've got the install done, you can reproduce at will by running those 3 commands I linked to in succession from cmdline
[05:59] <kees> superm1: okay, cool; I'll try it in the morning
[06:04] <superm1> kees, cool thanks.  i *think* this diff will fix both problems: http://paste.ubuntu.com/575327/ . but it's probably better to figure out what's really happening that hardlinks are being attempted in the first place for the first problem
[06:04] <Zinn> [paste.ubuntu.com] Ubuntu Pastebin
[14:37] <superm1> kees, well that patch I proposed last night gets the install all the way through properly consistently, but i think that sysctl thing is a bit hacky, so if you figure out what's going on that the kernel is complaining, lemme know and i'll drop that part
[15:25] <Newbuntu81> Has anyone running mythbuntu 10.10 recently updated to the 2.6.35-27-generic kernel and is now having trouble?
[15:27] <rhpot199`> Newbuntu81: what kind of trouble?
[15:32] <Newbuntu81> I used to be able to run v4l2-ctl -d /dev/video1 --set-freq=61.250, then mplayer /dev/video0 and it would show tv. I have not yet been able to get this working with myth.  After the kernel update last night, I can't tune the station in manually in mplayer anymore either.
[15:50] <kees_> superm1: yeah, that's just a work-around and shouldn't be needed. i'll get to the bottom of it today. :)
[16:39] <dewman> hey there....is there any trick to getting 6200ch.c to compile under mythbuntu? I am getting a strange error when trying to get it compiled. http://pastebin.com/gbBzcChp
[16:39] <Zinn> [pastebin.com] rob@dell:/tmp$ cc -std=gnu99 -o 6200ch 6200ch.c -lavc1394 -lrom1394 -lraw1394 - Pastebin.com
[16:43] <rhpot1991> dewman: how did you get the source?
[17:01] <Newbuntu81>  anyone have the HVR 2250 working in mythtv with Mythbuntu 10.10?
[17:35] <dewman> rhpot1991, I downloaded it from the mythtv wiki, just copied and pasted it into a txt editor.
[17:40] <rhpot1991> dewman: thinking thats your issue, you got bad characters in there
[17:47] <rhpot1991> dewman: use mythwikiscripts to get it
[17:48] <dewman> rhpot1991, got it....hehe.. the little things get you....
[17:58] <dewman> rhpot1991, do you know anything about this 6200 script for firewire?
[17:58] <dewman> it seems to default to node 1 for what ever reason.
[17:58] <rhpot1991> dewman: check the flags
[17:58] <rhpot1991> you should do it by GUID
[17:58] <rhpot1991> -g I think
[18:00] <dewman> opps...LOL, dang I am not with it today..
[18:01] <rhpot1991> dewman: if you do by GUID then it doesn't matter if it changes node or anything
[18:53] <dewman> rhpot1991, I think i got it...now....for the hard stuff..
[18:53] <dewman> how to compile video_source.cpp and firewire_device.cpp
[18:58] <rhpot1991> dewman: what are those for?
[19:00] <dewman> rhpot1991, this might help.... lol...Just trying to get firewire to work with myth and my cable box.   http://www.gossamer-threads.com/lists/mythtv/users/474069#474069
[19:00] <Zinn> [www.gossamer-threads.com] Fire-wire / Motorola DCX-3200M | MythTV | Users
[19:02] <rhpot1991> hmmmm thats rather annoying
[19:03] <rhpot1991> dewman: save yourself some trouble: http://www.amazon.com/gp/product/B0018LX0DY?ie=UTF8&tag=baablogicnet-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=B0018LX0DY
[19:03] <dewman> yeah, i was just told that I would have to recompile the entrie program....
[19:03] <rhpot1991> yep
[19:05] <rhpot1991> dewman: do you have a PPA?
[19:05] <dewman> I do..
[19:06] <rhpot1991> dewman: so easier method, pull our source, add your patch in then build it on your ppa
[19:06] <dewman> o...opps. I thought you meant, am i using the ppa
[19:07] <rhpot1991> or easiest method buy a hdpvr and don't mess with firewire cause it sucks :)
[19:07] <dewman> lol
[19:07] <dewman> I was trying to do this cheap...LOL...
[19:08] <rhpot1991> dewman: I used to use firewire and finally gave up and cut it out
[19:08] <rhpot1991> use it for channel changing now, thats it
[19:08] <rhpot1991> reliability isn't there
[19:10] <dewman> ok....I will see if I can get my hdhr to tune some of these crazy channels that charter sends down then.
[19:10] <rhpot1991> dewman: http://www.mythbuntu.org/wiki/developer-cheatsheet
[19:10] <Zinn> [www.mythbuntu.org] Developer Cheatsheet | Mythbuntu
[19:10] <rhpot1991> should help you with building
[19:23] <kees> wowo, I haven't done a myth install in a really long time. the QR code thing is cool :)
[19:31] <kees> superm1: so... my install finished without errors. where would I normally see it?
[19:31] <superm1> kees, so check /var/log/syslog
[19:32] <superm1> or if you already rebooted, you'll see that you can't connect to the DB
[19:32] <superm1> in which case, /var/log/installer/syslog is where you would look
[19:32] <kees> I haven't rebooted; it's just at the "Restart Now" problem.
[19:32]  * kees goes looking around in the install fs
[19:33] <superm1> you used a3 not today's daily right?
[19:33] <kees> ah yeah, there it is in dmesg
[19:33] <kees> yeah
[19:33] <superm1> so i believe if you don't reboot, you can also reproduce at will now by just running sudo chroot /target dpkg-reconfigure mysql-server-5.1 or so
[19:34] <kees> okay, trying now...
[19:34] <kees> it prompts for the mysql root pw... shouldn't that already be preseeded?
[19:35] <superm1> the debconf database is cleared of it at this point
[19:36] <superm1> rerunning dpkg-reconfigure is setting up a "new" password for it
[19:38] <kees> this is really weird.
[19:38] <kees> in /var/log/syslog I see the rename errors
[19:38] <kees> but looking at the files... they're totally fine
[19:38] <kees> i.e. owned by mysql:mysql
[19:42] <kees> superm1: so, one thing I noticed is that mysqld is running outside the /target chroot
[19:42] <superm1> well is it thougH?
[19:43] <kees> yeah /proc/../root points to /
[19:43] <superm1> so how can that happen?
[19:43] <superm1> something to do with upstart's chroot support?
[19:43]  * kees suspects upstart silliness
[19:44] <kees> it *still* doesn't explain the hardlink restriction issue, though
[19:52] <kees> it's the readlink call that is failing.... wtf
[19:56] <kees> superm1: the root cause of the problem is that mysqld is running outside the chroot. does the a3 upstart actually handle chrooted services starting?
[19:56] <kees> superm1: because if I kill the running mysqld, dpkg-reconfigure explodes
[19:56] <superm1> kees, yes it does, looks like it got uploaded 4 days ago
[19:57] <superm1> i'm not sure if that's how upstart is supposed to do it, or if that's actually a bug
[19:57] <kees> it looks like it's wrong
[19:57] <kees> i.e. there is only 1 init running
[19:58] <kees> and from inside the chroot, it has no idea about the mysql server
[19:58] <kees> *service
[19:58] <superm1> try sudo chroot /target status mysql
[19:58] <superm1> and compare to status mysql (ie outside the chroot)
[19:58] <superm1> upstart knows about the one in the chroot, but not the one outside
[19:58] <kees> status: Unknown job: mysql
[19:59] <kees> superm1: though this would technically explain the hardlink errors: it's treating the namespaces as separate. i.e. trying to do a link between the outside and inside of a chroot
[19:59] <kees> though I haven't proven that yet
[20:00] <superm1> i swear it was the other way around yesterday, and that I could actually run status in the chroot...
[20:02] <kees> also, no, I must be wrong about the link errors still. man... I really can't tell where that's coming from. /me studies the strace again
[20:03] <kees> there's not a single EPERM in the entire strace.
[20:04] <kees> I wonder if it's the mysqld outside the chroot triggering those...
[20:05] <superm1> well i suppose it's a matter of timing - are they showing up before start mysql gets called and it shows up outside the chroot?
[20:05] <superm1> or during the mysqld bootstrap sequence that the postinst runs
[20:06] <kees> interesting... it's entirely during "service mysql start" outside the chroot
[20:07] <kees> my head is spinning
[20:07] <superm1> glad i'm not the only crazy one here :)
[20:08] <kees> okay, so, it seems quite clear to me that upstart is not, actually, doing the right thing with the chroot
[20:08] <kees> while /etc/init/mysql.conf.disabled and /target/etc/init/mysql.conf seem to be set up right, mysqld gets started in / not /target
[20:09] <superm1> it shouldn't even be parsing /etc/init/mysql.conf.disabled though should it ?
[20:09] <kees> that's why I'm confused.
[20:09] <kees> what tells upstart to read /target/etc/init ?
[20:14] <superm1> just grepping the source briefly, i'm only seeing references to an additional stanza in upstart jobs for specifying chroots
[20:29] <kees> yeah
[20:29] <kees> have you verified that the daily actually ends up with the right password in the users table?
[20:30] <kees> I _still_ can't recreate the link error. I've found the place where it's failing (mysqld itself doing a rename) but I don't understand why it fails. doing those actions manually as mysql user succeeds *tear out hair*
[20:33] <kees> oh... reproduced it.
[20:33] <kees> still horribly confused. :)
[20:48] <kees> superm1: I think this might be an aufs bug. http://paste.ubuntu.com/575694/
[20:48] <Zinn> [paste.ubuntu.com] Ubuntu Pastebin
[20:55] <superm1> kees, cool!
[20:55] <superm1> well i'm glad i threw this your way, this is far lower level than i was about to investigate
[20:56] <kees> superm1: yeah, now that I can reproduce it, I'll dig further.
[20:56] <kees> superm1: I worry that the yama-disable work-around just papers over the real problem: mysql is running in /var/lib/mysql instead of /target/var/lib/mysql.
[20:57] <kees> superm1: but I'll continue to work on this yama-vs-aufs bug
[20:57] <superm1> at least for the purposes of setting up mysql in the chroot, it's actually an N/A
[20:57] <superm1> because mysql just gets started at the "end" of the postinst so it's ready to go
[20:58] <superm1> so it won't cause any problems on the end system (as long as it's manually respawned in the chroot)
[20:58] <kees> ah. I was worried that the preseeded passwords wouldn't make it into the final /target filesystem
[20:58] <superm1> i *think* they will
[20:58] <superm1> i'll double check
[20:59] <kees> let me open a bug in LP for the yama-vs-aufs, and can you add a link to it in the code where you disable yama during the install? should be easy to track for removal when it's fixed at some point.
[20:59] <superm1> yes, that'd be great
[20:59] <kees> one, sec sec
[21:06] <kees> superm1: okay, it's bug 729338
[21:06] <Zinn> Bug 729338 in linux (Ubuntu) "yama hardlink restriction misbehaves under aufs" [Undecided, New] http://www.launchpad.net/bugs/729338
[21:07] <superm1> k thanks.  i'll subscribe to it and add a note to the code about it