[03:42] <OvenWerk1> zequence: re: changing the default pulse device as was talked about in the user channel. It could be difficult.
[03:42] <OvenWerk1> I don't think we would get support changing the main pulseaudio package.
[03:43] <OvenWerk1> (dual display is really nice BTW)
[03:54] <OvenWerk1> It appears that while PA does ask for RT scheduling, it does not lock it's memory (meaning the OS is allowed to swap it out to disk)
[03:57] <OvenWerk1> I am thinking that pulse as it comes stock, is setup to work best with plain desktop, higher latency audio on mostly internal cards.
[03:57] <OvenWerk1> There may well be ways of setting it so it plays better with jack.
[03:58] <OvenWerk1> If so, that would probably be one more thing for -controls to tackle.
[05:00] <eagles0513875_> hey zequence  :D
[05:55] <eagles0513875_> hey zequence im noticing the ISO respin is in progress, what version of 1.0 did you guys pull did you pull the 1.0.1 package?
[06:49] <eagles0513875_> can anyone tell me if the 1.0.1 package was pulled into the iso respin for testing?
[06:51] <elfy> eagles0513875_: I'm just booting the image - I can look there if you want
[06:51] <eagles0513875_> elfy: yes please
[06:51] <eagles0513875_> that way i can work with motu on getting it included before release
[06:51] <elfy> eagles0513875_: what package are you actually talking about though :p
[06:51] <eagles0513875_> lmms
[06:52] <eagles0513875_> sorry i knew i forgot somethign I am still waking up granted i got up almost 3 hrs ago lol
[06:52] <elfy> 1.0.0+bzr256
[07:01] <Mirv> eagles0513875_: israel's branch is not proposed for merging, and no MOTU had uploaded it otherwise (I'm not sure if someone has promised to be looking after the upload?). I'll proposed it now and mark some things "Needs Fixing" from my POV (there is no upstream 1.0.1 version, and at the minimum it should be specified which commit the orig tarball is based off)
[07:03] <eagles0513875_> Mirv: let me get you the bug that has the link to so you can update the bug report i had filed
[07:03] <elfy> zequence: I'll manage to squeeze a couple of install tests in for you today - but I'm not in any position to do more than those
[07:06] <Mirv> eagles0513875_: I've the bug, and I linked israel's branch now there too and gave my comments on the merge proposal
[07:07] <Mirv> for a MOTU to be able to review the upload, he needs to be able to verify the upstream tarball so knowing that commit is the most important thing. archive admins would probably also reject a "1.0.1" when there's no such upstream version, so renaming the version number as suggested should be done at the same time.
[07:08] <eagles0513875_> Mirv: it pulls the tarball from what we have on sourceforge
[07:08] <Mirv> eagles0513875_: no, it's not the 1.0.0 tarball, so it has to be some sort of snapshot instead?
[07:09] <Mirv> I mean, from github instead of sourceforge
[07:09] <Mirv> which is fine, but it should be just specified
[07:10] <eagles0513875_> Mirv: currently its a snapshot form master
[07:10] <eagles0513875_> which is what we dont want 
[07:10] <eagles0513875_> we have a 1.0 stable branch which is what we have bzr based off of Israel is the person working on this as I have no idea on packaging
[07:10] <eagles0513875_> tbh
[07:11] <Mirv> eagles0513875_: yeah, so the snapshot from stable should specify which commit it's based off, similar to what the master is currently specified
[07:11] <eagles0513875_> im just trying to ensure we have the right version in the repos for 14.04
[07:11] <Mirv> yep, I'm trying to help so I gave that feedback that I know is needed to be handled before MOTU can upload it
[07:11] <eagles0513875_> Mirv:  we already have a sponsor 
[07:11] <Mirv> since tarballs of unknown origin cannot enter archives
[07:11] <eagles0513875_> if you look at the bug timo seems to be sponsoring this fix
[07:12] <Mirv> eagles0513875_: ok, is he in which timezone? maybe he could finish of israel's branch
[07:12] <Mirv> eagles0513875_: I'm Timo, btw, and I don't have upload rights so I'm still just a helper, not a sponsorer :D
[07:12] <Mirv> so you need someone who has upload rights to the universe
[07:12] <eagles0513875_> oh ok :D
[07:13] <eagles0513875_> i didnt know what your irc name was :D 
[07:13] <eagles0513875_> thanks for your help on this
[07:13] <Mirv> so for example https://launchpad.net/~motu/+members
[07:13] <Mirv> SRU will be ok too, it's just more bureaucratic
[07:14] <Mirv> no problem :D
[07:14] <eagles0513875_> Mirv: any chance you can update the bug report with the above mentioned package name suggestion as israel is subscribed automatically to that bug
[07:15] <Mirv> eagles0513875_: it's there in the linked branch's merge proposal discussion that is attached to the bug. I'll comment on the bug too so that it's noticed.
[07:15] <eagles0513875_> thanks
[07:17] <eagles0513875_> Mirv: im going to post the link on the bug as I just found it :D
[07:17] <eagles0513875_> linked to the proposal
[07:18] <Mirv> eagles0513875_: you too! :)
[07:18] <Mirv> 2 seconds apart it looks (59 seconds ago, 57 seconds ago) :D
[07:20] <eagles0513875_> lol 
[07:20] <eagles0513875_> Mirv: spoke to dholbach in motu and he said a feature freeze exception would need to be filed.
[07:22] <Mirv> eagles0513875_: oh, ok, he knows better. and I think he's correct. if it's indeed a new upstream stable branch update, it's a new release. so the "leanest option" of patching out the problematic master pieces with a distro patch would not have needed FFe but be a bug fix instead.
[07:22] <eagles0513875_> ffe??
[07:23] <Mirv> but the new stable branch snapshot is probably the best option, and getting FFe not a huge problem since the master branch snapshot has problematic commits
[07:23] <Mirv> eagles0513875_: short for "Feature Freeze exception"
[07:23] <eagles0513875_> ahh ok 
[07:23] <eagles0513875_> sorry not used to the fancy short names :D
[07:23] <eagles0513875_> Mirv: are you employed by canonical out of curiosity
[07:23] <Mirv> when there are tens of FFe:s around it helps to use abbreviations :)
[07:24] <Mirv> eagles0513875_: yes, and that's why I've my hands full of other stuff :) even on free time I'm preparing my local community (ubuntu-fi) stuff so release time is quite busy..
[07:24] <Mirv> or I'm a contractor to be more precise, not employee
[07:24] <eagles0513875_> kool
[07:27] <Mirv> I started using ubuntu in 2004 and founded Ubuntu Finland in 2005, but for 7 years after that I worked on other embedded Linux stuff while staying active in the Ubuntu community
[07:28] <eagles0513875_> Mirv: do you mind if i pm you as I dont want to end up off topic in this channel
[07:28] <Mirv> eagles0513875_: yeah feel free, no Studio discussion anymore
[18:36] <zequence> OvenWerk1: Any changes to Pulseaudio need to be done in code. Either one of us digs into it, or we try getting someone involved on it. Doing a wishlist bug, or finding someone in LAD that would like to do it
[18:39] <zequence> Mirv: eagles0513875: I have someone willing to upload it fast, but as Mirv pointed out, the package needs to be fixed first
[18:39] <zequence> Since this only affects our ISO, the release team is kind to us on this
[18:42] <zequence> elfy: Thanks. I will do some testing myself today. Both ISOs. Don't stress it. Think we're fine on the most part, but if you do test, and find anything weird about the XFCE bits, please let me know
[18:42] <elfy> I did 64bit - you appear to still have the ibus issue
[18:42] <zequence> elfy: What is the issue with that?
[18:43] <zequence> I didn't touch those, since I don't know what they do, tbh
[18:43] <elfy> zequence: ok well basically the issue is - install with your keyboard layout - I used GB 
[18:44] <zequence> elfy: Ok, so just removing those from seeds would fix that? Or do we need to add something too?
[18:44] <elfy> password included a symbol - # for example, reboot - login works fine - as soon as you are at desktop it switches to US layout - so the password will fail 
[18:45] <zequence> Ah
[18:45] <elfy> I completely lost track of what we had to do in the end - it wasn't as simple as removing ibus I think
[18:46] <elfy> we still get the issue for upgrades - workround is purge ibus before and then upgrade or either set up ibus or purge it afterwards
[18:46] <elfy> and yes - ask in there :p
[18:48] <zequence> thanks elfy 
[18:49] <elfy> welcome
[19:45] <zequence> Seems like we have two indicator applets for power again
[19:54] <zequence> i can't believe i missed the ibus bug before
[19:54] <elfy> zequence: such is life :)
[19:55] <elfy> I tested on vm so wouldn't have seen power applet afaik
[19:55] <elfy> I did see bluetooth - which we removed - but not sure if you actually used it so didn't comment
[19:58] <zequence> I can live with two power applets until a possible SRU, but the login problem is quite severe
[19:58] <zequence> installing latest now, and going to remove the ibus packages to see if that solves it
[19:59] <zequence> seems like we have quite a sever bug with usb devices too
[19:59] <zequence> OvenWerk1: Have you tested your usb device on latest releases?
[20:00] <zequence> Might not affect you
[20:00] <zequence> Bug 1308628
[20:00] <zequence> Bug 1299878
[20:20] <zequence> elfy: The default keyboard layout in login manager was US english, but this time at least there was a swedish alternative. Wasn't there before, so some progress
[20:20] <zequence> The different types of English were all there before, of course
[20:21] <elfy> not here they weren't - not without setting ibus up - all that is in the list for me is US 
[20:21] <elfy> I just wanted to bring it to your attention is all :) 
[20:22] <zequence> elfy: Really? Ok. well, if purging the ibus packages is all that is needed, the fix should be simple enough
[20:22] <elfy> the first time I got hit with it - it took me a while to suss that # was showing up as \ then I saw the damned icon in the panel :)
[21:00] <zequence> ibus and indicator-power dropped from seeds
[21:00] <elfy> :)
[21:00] <zequence> Bug 1308755
[21:00] <elfy> if I'd known it was that simple I would have said 
[21:01] <zequence> elfy: I won't say I'm sure until I test the ISO, but removing them seemed to do the job
[21:01] <zequence> Bug 1284635
[21:02] <elfy> yep
[23:45] <OvenWerk1> zequence: have you thought about the USB3 with USB2 Audio bug at all? Bug 1308628
[23:47] <OvenWerk1> I would think there will be a change in the kernel module at some point to "fix" this, but getting the driver moved to a module makes sense. The question is if the generic kernel maintainers are willing I would guess... or can we just do that for low latency?
[23:49] <OvenWerk1> The change does not sound like a security problem.