[08:53] <dandrader> kgunn, shellRotation branch should merge fine now
[10:09] <tsdgeos> Mirv: can you land https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1418370 ? It fixes the orientation issue with qt 5.4
[10:12] <Saviq> tsdgeos, any word on refreshing the certificate for qt-project? ;)
[10:12] <Mirv> tsdgeos: ok, uploading!
[10:13] <Mirv> as well as the oxide
[10:13] <tsdgeos> Saviq: two days ago it was supposed to be fixed ...
[10:13] <Saviq> right
[10:14] <tsdgeos> Mirv: cool
[12:56] <Saviq> Cimi, relatively pressing review needed: https://code.launchpad.net/~unity-team/unity8/wizard-auto-shutdown/+merge/248902
[12:56] <Cimi> Saviq, ok
[12:57] <Saviq> Cimi, oups, wrong version, fixing
[12:59] <Saviq> Cimi, actually, need to fix a test, too :/
[13:01] <Cimi> Saviq, do we really want to shut down the phone if inactive?
[13:01] <Saviq> Cimi, in wizard only, and only if you never interacted with it
[13:01] <Saviq> Cimi, i.e. in the factory
[13:01] <Cimi> why?
[13:02] <Cimi> what does design say?
[13:02] <Saviq> Cimi, it's not about design, it's about the factory process
[13:02] <Cimi> I never seen a phone/device shutting down
[13:02] <Saviq> Cimi, you never left an android phone on the wizard for 2 minutes ;)
[13:02] <Cimi> I might switch on the phone for the first time, go and make a coffee, come back and is switched off wtf
[13:03] <Cimi> Saviq, I understand your reasons, but I think we need someone to approve this change
[13:04] <Cimi> Saviq, and in any case, we need some sort of UI feedback (i'm shutting down because of inactivity-like notification)
[13:04] <Saviq> Cimi, yeah, except you dont'
[13:04] <Saviq> Cimi, request for this change comes directly from the product team
[13:05] <Saviq> I didn't just imagine that
[13:05] <Cimi> Saviq, let me test with android, see if it switches off
[13:06] <Saviq> Cimi, http://pad.lv/1418815 for reference
[13:06] <Cimi> Saviq, ok I understand, will review code...
[13:13] <Saviq> mterry, could use your eyes on https://code.launchpad.net/~unity-team/unity8/wizard-auto-shutdown/+merge/248902 too
[13:13] <Saviq> mterry, hi btw! http://pad.lv/1418815 for reference
[13:13] <mterry>  Saviq hello!  :)
[13:14] <Saviq> mterry, I'm not totally happy about the "pageLoaded" signal, maybe you can come up with a better thing, I'm not really sane today after the sprint
[13:15] <mterry> Saviq, :)  let me see
[13:18] <mterry> Saviq, a forced wait() in one of the tests?  grumble grumble
[13:18] <Saviq> mterry, read again ;)
[13:18] <Saviq> mterry, it's a wait on the signal spy
[13:18] <mterry> Saviq, right.  But you are expecting it to timeout
[13:18] <Saviq> mterry, well, what else?
[13:19] <Saviq> mterry, I could just verify() and go with that, the expectFail just adds one more
[13:19] <mterry> Saviq, I don't like delays in the tests, they are long enough to run already.  But I understand what you're doing here
[13:19] <mterry> Saviq, I might have been satisfied with just the verify() but I can't complain about more tests I guess
[13:19] <Saviq> mterry, yeah you know... how do you verify that something doesn't happen? :)
[13:20] <mterry> Saviq, well it's quite unlikely to happen if the timer isn't running  :)
[13:20] <Saviq> mterry, is true
[13:21] <mterry> Saviq, I'm surprised we didn't already have a Session mock
[13:21] <Saviq> mterry, yeah, was surprised, too
[13:23] <mterry> Saviq, so this is for unity8... but I assume the bug really cares about rtm?   which would be system-settings?
[13:23] <Saviq> mterry, yeah, I'll backport it to system-settings
[13:23]  * Saviq fixes bug tasks
[13:24] <mterry> Saviq, well I love it, pageLoaded is fine too.  Let me just test on my device and then approve
[13:25] <Saviq> kk
[13:28] <Saviq> mterry, later we might make it more robust (i.e. Keys.onPressed; mouse and touch events, + a dialog before it goes to sleep)
[13:28] <mterry> Saviq, yeah I did wonder.  Like, what if someone is just fooling around with language list
[13:28] <mterry> Saviq, or puts phone down to read manual
[13:29] <Saviq> mterry, I really think that's edge cases, but yeah, let's cater for those at some point, I think this is good for now
[13:30] <mterry> Saviq, I think ideal would be to throw up a dialog that also times out, but warns user about impending shutdown
[13:31] <Saviq> mterry, yup, that's the plan
[13:31] <Saviq> mterry, edge case, though
[13:31] <mterry> Saviq, yes, ideally new users are so excited they race through the wizard
[13:32] <mterry> :)
[13:36] <mterry> Saviq, for that wait to really be effective, wouldn't you want to specify the delay time yourself?  To be over two minutes?  I think the default is 30s
[13:37] <Saviq> mterry, right, or change the interval
[13:37] <Saviq> mterry, don't really wanna add 2mins wait time to our test suite
[13:38] <mterry> Saviq, ah sure.  But again, if we don't trust the !running check, why do we trust changing interval and running?  :)
[13:38] <Saviq> mterry, indeed
[13:38] <Saviq> mterry, I'll just check that it's not running and that the signal didn't fire before then
[13:38] <Saviq> mterry, which is kinda what the wait() was doing anyway
[13:41] <Saviq> mterry, done
[13:42] <mterry> Saviq, hrm.
[13:42] <mterry> Saviq, you might want to move the pageLoaded signal before the checkSkip line too
[13:42] <mterry> Saviq, otherwise you could end up emitting pageLoaded(2) then pageLoaded(1) if you skip 1
[13:48] <Saviq> mterry, done
[13:49] <mterry> Saviq, it's a little odd that we emit pageList.index rather than pageStack.depth, but either situation is deceptive (in the case of a page having follow-on pages).  And especially since we don't care about it being accurate here, no biggie
[13:49] <mterry> Saviq, I'll approve, worked fine in testing too
[13:50] <Saviq> mterry, tx
[14:20] <tsdgeos> mzanetti: ohmy, you got an all green MR
[14:20] <tsdgeos> we hadn't had that in ages :D
[14:20] <mzanetti> *\o/*
[14:27] <tedg> tsdgeos, Are you going to flash phones at MWC this year? ;-)
[14:28] <tsdgeos> tedg: don't know, wasn't year last year, and people that were there said the numbers of flashings where down compared to 2 years ago since flashing is so well documented nowadays
[14:28] <tedg> tsdgeos, Ah, okay. Probably they'll want to sell phones more than flash other ones this year.
[14:29] <tedg> It is kinda a funny part of Ubuntu Phone history :-)
[14:32] <tsdgeos> yep, one of the first phones we flashed was from the firefox phone people D:
[14:33] <mzanetti> :)
[14:40] <Saviq> tedg, the volume notifications are quite intrusive recently... they show up on boot, on DTMF tones in the dialer... on music...
[14:40] <Saviq> bug #1418089
[14:40] <Saviq> that known?
[14:40] <tedg> Saviq, Do you have the i-sound that landed last night?
[14:40] <Saviq> tedg, might not
[14:42] <tedg> Saviq, bug 1416233
[14:42] <Saviq> tedg, ok, that then might be fixed
[14:42] <Saviq> tedg, right, feel free to dupe my bug
[14:44] <dandrader> mzanetti, https://code.launchpad.net/~dandrader/unity8/improveLauncherTests/+merge/248919
[14:56] <Cimi> tsdgeos, hey, is this ok for closing scopes? http://paste.ubuntu.com/10092894/
[14:57] <tsdgeos> Cimi: don't remove it from all scopes, otherwise you're going to lose the scope in the mock
[14:57] <tsdgeos> Cimi: when activating it add it to a list
[14:57] <tsdgeos> when closing it check it's on the list
[14:57] <tsdgeos> that's all
[14:57] <tsdgeos> same the m_openedScope did
[14:57] <tsdgeos> but with alist
[14:58] <Cimi> tsdgeos, openedscope?
[14:58] <Cimi> tsdgeos, but that was never changed
[14:59] <Cimi> tsdgeos, we don't call activate
[14:59] <tsdgeos> we do
[14:59] <tsdgeos> we already discussed over this
[14:59] <tsdgeos> there's a test that proves we do
[14:59] <tsdgeos> and i pasted you the code that calls activate
[15:00] <Cimi> tsdgeos, only when we click an item
[15:00] <tsdgeos> yes
[15:00] <tsdgeos> which is the only way to open a scope
[15:00] <tsdgeos> isn't it?
[15:00] <Cimi> mmm
[15:00] <tsdgeos> or maybe not
[15:01] <tsdgeos> maybe you can also though a Preview Action
[15:01] <Cimi> tsdgeos, when we move between favorite scopes?
[15:01] <Cimi> tsdgeos, yes, correct
[15:01] <Cimi> tsdgeos, like in my bug
[15:02] <tsdgeos> well that goes through previewmodel triggered then
[15:02] <Cimi> tsdgeos, I can add activate in openScope
[15:02] <tsdgeos> no
[15:02] <Cimi> inside the tempscope
[15:02] <Cimi> mmm ok
[15:02] <tsdgeos> activate calls openscope
[15:02] <tsdgeos> not the other way around
[15:02] <tsdgeos> what you can't do in your test is call openScope
[15:02] <tsdgeos> openScope is not something we call
[15:02] <tsdgeos> is something the backend calls
[15:03] <Cimi> ok
[15:03] <tsdgeos> on actions from the user
[15:03] <tsdgeos> be it acivate()
[15:03] <tsdgeos> or                         previewModel.triggered(widgetId, actionId, data);
[15:03] <tsdgeos> in qml/Dash/Previews/Preview.qml
[15:15] <Cimi> tsdgeos, in the end what  we are doing in scopes plugin https://code.launchpad.net/~stolowski/unity-scopes-shell/fix-temp-scopes/+merge/248235
[15:15] <Cimi> tsdgeos, I need the same code...
[15:16] <tsdgeos> you need something similar
[15:16] <tsdgeos> you don't need to delete the scopes
[15:16] <tsdgeos> because the mock plugin creates them all the startup
[15:16] <tsdgeos> and stopres them in allscopes
[15:16] <tsdgeos> and serves them from there
[15:16] <tsdgeos> but yes, you need something similar
[15:22] <mzanetti> Saviq: http://notyetthere.org/data/com.ubuntu.terminal_0.7.latest_amd64_rev015.click
[15:58] <MacSlow> Saviq, I've pushed a fix for the property-count failure on Jenkins, but can't trigger a rebuild on jenkins as the site is dead from my end
[15:59] <MacSlow> Saviq, ... ^ regarding the swipe-to-dismiss branch
[15:59] <Saviq> MacSlow, if you pushed a change it will notice and rebuild
[16:00] <MacSlow> Saviq, sure... local test (on my slow machine no longer failed) 50 of 50 test-runs passed... that was good enough for me to push :)
[16:00] <Saviq> MacSlow, yup, sounds sane, kicked a jenkins rebuild anyway
[16:01] <MacSlow> Saviq, thanks
[16:36] <dandrader> greyback__, does it make sense to you? mapToItem(null, Qt.point(mouse.x, mouse.y)).x;
[16:37] <dandrader> point = mapToItem(null, Qt.point(mouse.x, mouse.y)).x;
[16:38] <dandrader> point = mapToItem(null, mouse.x, mouse.y)


[07:33] <brobostigon> morning boys and girls.
[09:14] <SuperMatt> morning all
[09:14] <SuperMatt> how are we all today?
[09:28] <SuperMatt> Just tried installing corebird from a snap, and it tells me I also need to install a snap called gnome-3-26-1604 and connect it to the corebird snap. This I don't mind doing right now, and I understand why it technically needs to be done, but I don't know why it's not just automatic
[09:29] <brobostigon> morning, could be better, and you?
[09:29] <SuperMatt> I'm slightly ill, so I could be better too
[09:29] <brobostigon> hope better soon.
[09:56] <foobarry> did someone tell me that lets encypt can manage certs for sites with internal IP too?
[09:56] <SuperMatt> apparently so
[09:56] <SuperMatt> though I don't know how to get that working
[09:56] <SuperMatt> I'm certainly looking forward to wildcard certs landing
[10:35] <diplo> Morning all
[10:36] <SuperMatt> ahoy
[10:39] <diplo> How's the new job going SuperMatt ?
[10:39] <SuperMatt> going well thank you. I've been there a month right now and I haven't wanted to murder anyone
[10:40] <SuperMatt> The tech stack is brilliant
[10:40] <SuperMatt> there's lots of free food
[10:40] <SuperMatt> and fridays are a write off, which is mavellous
[10:42] <diplo> I do sometimes think I should look at something like that
[10:42] <diplo> But not sure I want to much pressure atm
[10:42] <diplo> And I guess that can be there
[10:42] <SuperMatt> Well at the moment there's no pressure because I am too new
[10:42] <SuperMatt> b
[10:43] <SuperMatt> oops
[10:43] <SuperMatt> But from what I've seen of the veterans is that there's no too much pressure either, at least not until the site goes down
[10:43] <SuperMatt> but the stack is such that the customer is rarely affected when a node or two go down
[10:44] <diplo> I'd like to run stuff like that, we probably couldn't ( very old software )
[10:46] <SuperMatt> you gotta convice the bosses that stacks with service discovery and self healing are awesome
[10:47] <diplo> I could say it's awesome, just not enough staff to do anything about it
[10:47] <diplo> Most have been here 20ish years
[10:57] <SuperMatt> eek!
[10:58] <SuperMatt> An aging staff in tech is not a good idea. It increases the chance of knowledge residing solely in brains, rather than in documents
[11:03] <diplo> There were literally 3 documents when I joined, I've written 1000's of pages now in sphinx (rst ) and also in a seperate git repo too
[11:03] <diplo> And you're right, some things are only known by 1 or 2 people, I'm trying to change that
[11:03] <SuperMatt> You need to do a bus test
[11:04] <SuperMatt> Pretend that someone has been hit by a bus and send them home for a week, fully paid
[11:04] <SuperMatt> Then see if you can get through the whole week and a DR recovery test without contacting them
[11:08] <diplo> Yeah, we can with the knowledge but it would be slow, they don't listen tbh but happy for me to start fixing the problems myself with not a lot of help
[11:08] <diplo> Gone from taking 1 1/2 days to deploy / set up our software to 20 mins with Ansible :)
[11:08] <diplo> 4-5 hours to install / setup new hardware to 5-6 mins
[11:09] <SuperMatt> good man
[11:11] <diplo> They love it now, deploy ssh keys out to clients and remove them all when someone leaves, it's just a god damn slow process and hard work
[11:11] <SuperMatt> puppet is good for ssh keys
[11:11] <diplo> I use ansible for that too
[11:12] <diplo> Just hard to keep on top of this plus doing everything else :)
[11:12] <diplo> Can't get my new Cent7 image to PXE boot either :/
[11:12] <Nafallo> why would you need ssh keys, and accounts, on the servers when you have ansible though? ;-)
[11:13] <diplo> For out staff to logon to fix application specific issues at our clients
[11:13] <diplo> Oh noticed the smiley at the end :P
[11:13]  * diplo is tired
[11:13] <Nafallo> ansible -m command -a ? :-D
[11:13] <diplo> That would take users understanding anything apart from what they've learnt over 20 years
[11:14] <Nafallo> aye :-)
[11:14] <diplo> They still use some ps commands that don't really return what they really need, but it's what they've always used
[11:14] <Nafallo> not as easy to implement as it sounds always :-)
[11:14] <diplo> We only moved to SVN about 5-6 years ago, that was HELL!
[11:14] <Nafallo> thank god my home lab is different from $WORK ;-)
[11:14] <diplo> Trying to move to git now :)
[11:15] <Nafallo> I'm considering allowing ansible to ssh to the hosts and use the lxd connection plugin to actually manage the containers... and then stop having ssh :-P
[11:15] <Nafallo> could be a fun exercise ;-)
[11:16] <Nafallo> s/stop having ssh/& in the containers/
[11:20] <SuperMatt> yeah, removing ssh is a double plus good idea
[11:29] <Nafallo> hmm. ansible automates in netherlands 14/3 :-)
[11:29] <Nafallo> tempting
[11:29] <SuperMatt> going abroad on the company dime ftw
[11:31] <czajkowski> aloha
[11:37] <Nafallo> hola czajkowski
[11:42] <czajkowski> Nafallo: howdy
[12:17] <diplo> So disabling sshd on the lxd's Nafallo ? sounds good.. may have to think about that, I use lxc currently and haven't had chance to setup/check out lxd and the slight changes
[12:18] <diplo> But I guess I ought to at some point
[12:21] <Nafallo> now I just need time to play with it ;-)
[12:25] <diplo> That's my problem too :)
[12:29] <Nafallo> ansible -m command -a "netstat -ltn" lxd <- working fine :-)
[12:29] <Nafallo> using the dynamic inventory on my laptop ;-)
[12:29] <Nafallo> did ansible -m service -a "name=ssh state=stopped" lxd before
[12:32] <diplo> I never use the single liners, how do you know what host that is being deployed against?
[12:32] <diplo> I take it that it reads /etc/ansible/hosts by default
[12:33] <Nafallo> I've specified inventory in ansible.cfg, and created a folder that contains lxd.ini lxd.py and localhost.
[12:34] <diplo> Ah right, I've never thought of playing in there, will take a look later, I've pretty much solely used playbooks so far as they suit my needs, but want to tinker some more at some point soon
[12:34] <Nafallo> localhost being a static inventory config with ansible_connection=local set, and the other files being slightly modified versions of the dynamic inventory scripts at ansible github contrib/inventory files.
[12:35] <Nafallo> the script is just set to put all the local lxd hosts in an lxd group, and tell it to use ansible_connection: lxd ;-)
[12:35] <diplo> ah OK, that sounds easy enough
[12:36] <diplo> Going to install it on my solus box as it is in the repos
[12:36] <Nafallo> obviously, running ansible binary instead of ansible-playbook above as well. just need to do one task on the lxd group quickly ;-)
[12:37] <diplo> yeah, I keep meaning to play
[12:37] <diplo> So going to try it right now
[12:39] <diplo> Also haven't tinkered with sudo yet, I have a playbook ready to do it and tinker
[12:39] <Nafallo> what are you planning for sudo? :-)
[12:39] <Nafallo> lxd connection always uses root, since that was lxc exec <machine> <command> does ;-)
[12:40] <diplo> Running commands on all our customer sites as our one user so our staff don't need root - can run same commands on all sites out of hours
[12:40] <Nafallo> other than that, I tend to work around requiring to remember setting -B for playbooks by setting them to use become: false global and use a pre-task that runs sudo -v :-)
[12:41] <diplo> As I said earlier, we had lots of issues with the way our staff did things, like can't get something working, lets 777 the home directory
[12:41] <Nafallo> obviously for that sort of deployment your best options is probably public key + sudoers.d/ file with nopasswd locally for the deploy user :-)
[12:43] <diplo> Yeah, that's my intention, just got to get all the tasks they require root for :)
[12:43] <Nafallo> ah right. I see where you're going now... you want to modularise root a bit rather than allow all for these people that prefer logging in? :-P
[13:18] <diddledan> SuperMatt: the installation of gnome-3-26-1604 is not automoatic because currently there's no way of defining that dependency, but if it is already installed then the "connect" part is done automatically - so other snaps depending on it will pick it up now you've got it installed
[15:30] <Nafallo> hrmpf. writing a module. I've spent half the day documenting it :-P
[15:31] <Nafallo> diplo, SuperMatt: if you Ansible guys use Ubuntu, I'm currently attempting to re-write https://code.launchpad.net/~tribaal/ubuntu-repository-cache/trunk in Ansible ;-)
[15:31] <Nafallo> might be helpful.
[15:32] <Nafallo> started writing and realised I need roles for apache2, squid and squid-deb-proxy as dependencies ;-)
[16:31] <diplo> Use it against CentOS boxes mainly for work, but will take a look on one of my ubuntu machines tomorrow
[16:31] <diplo> Afternoon has been manic :(
[17:28] <diddledan> gog.com freebie: https://www.gog.com/#giveaway
[23:36] <daftykins> hrmm got forward a few of the Google G Suite GDPR emails, so have to find out what the deal with that is...
[23:36] <daftykins> my instinct is that being outside of the EU, there isn't much for us rock dwellers to do
[23:45] <zmoylan-pi> you're not outside of the eu yet... and the final deal might mean it applies to you rock dwellers too?
[23:46] <daftykins> yes we are :) never been in the EU
[23:46] <zmoylan-pi> ...please send me a crate of happy sleepy sleep snoozy snooze... :-)
[23:47] <daftykins> o0


[16:54] <sebsebseb> hi
[16:54] <penguin42> hey
[16:54] <penguin42> finally starting to cool down a bit here
[16:55] <sebsebseb> penguin42: yep here  too
[17:04] <zxmpi> down to 23c here today, was over 25c yesterday
[17:07] <penguin42> it's claiming to be down to 20c accoding to the weather app on the bar
[22:17] <daftykins> aaaah... a glorious breeze!
[22:17] <daftykins> i might be hopping over to Exeter sometime soon
[22:17] <daftykins> i just found a Brewdog restaurant there, that ought to be fun
[22:32] <penguin42> hmm I think there's one here as well
[22:36] <daftykins> we drink a fair bit of their "Lost" in cans down at my dentist pal's practice
[22:36] <daftykins> out of hours, of course xD
[22:36] <daftykins> i think he'll be jealous once i mention having the chance to visit one o' these
[22:37] <daftykins> hmm of course visiting England means finding a spare phone and a UK SIM
[22:39] <penguin42> so I just spent an hour chasing something truly obscure
[22:40] <penguin42> https://cdn.mastodon.org.uk/media_attachments/files/111/042/671/143/131/984/original/468f76ad3191872c.jpeg   you see that green smudge under 'license'
[22:40] <daftykins> yep
[22:41] <penguin42> ok, where do you start debugging it
[22:41] <daftykins> probably dragging in another white window to start, to rule out the monitor
[22:42] <daftykins> then again scrolling would do that xD
[22:42] <penguin42> dragging a white window over it, the white window is fine
[22:42] <penguin42> scrolling follows the scroll
[22:43] <daftykins> hrmm, separate browsers on the same page next i'd try
[22:43] <penguin42> chromium doesn't exhibit it
[22:44] <daftykins> but the Fox can do no wrong, in my book!
[22:44] <penguin42> I will note the green is flickering and jittering
[22:44] <daftykins> ooh
[22:44] <daftykins> right click -> inspect element find anything other than background blankness?
[22:45] <penguin42> worlds most boring html
[22:46] <daftykins> wow, ok... amaze me!
[22:46] <penguin42> daftykins: OK, let me tell you another one - screenshot doesn't show it
[22:46] <daftykins> O_O
[22:47] <penguin42> daftykins: Disabling hardware acceleration doesn't help
[22:47] <penguin42> daftykins: And restarting ff doesn't help
[22:48] <penguin42> daftykins: Changing the sharpness on the monitor makes it go away
[22:48] <daftykins> oooh
[22:48] <daftykins> so it was in the display, wowzer
[22:49] <penguin42> odd isnt it
[22:49] <daftykins> that's quite the tricky one!
[22:49] <penguin42> but it's only that page it's showing it on
[22:50] <daftykins> i wonder what about that region makes your monitor go so nutty
[22:50] <daftykins> here's one for fun, what about rotating?
[22:50] <daftykins> would the pattern perfectly rotate 90 degrees to fill the same portion?
[22:51] <penguin42> my suspicion is it's an aging fault on the monitor; it seems very sensivie to the exact background colour; if I edit the background colour it goes away
[22:51] <daftykins> :D
[22:51] <penguin42> I think it's triggering on the right hand slope of the 'v' in approved
[22:51] <daftykins> i have quite a number of vertical lines when i cold power-on my 2008 CCFL backed LCDs now, after a warm-up these disappear
[22:52] <penguin42> are they black lines?
[22:52] <daftykins> oh yeah that does look like the origin
[22:52] <daftykins> they're a bit of a mix, some colours - some black so presumably unlit columns
[22:52] <penguin42> yeh
[22:54] <penguin42> I did have another Dell monitor that had settings related artifacts - but they were much larger scale and much less image specific
[22:55] <daftykins> here's how one looks - https://i.imgur.com/VcZyb35.jpg
[22:56] <penguin42> oh yeh, that's normally a connection to the panel going over time I think
[22:57] <daftykins> apparently a bit of hairdryer action between the layers can help, but since it disappears on warmup i have just accepted it
[22:57] <penguin42> yep


[07:30] <jmarsden> I've got a bzr recipe that doesn't build on LP, giving what looks like a quilt-related error.  I'd appreciate help fixing it.  https://code.launchpad.net/~lxde/+recipe/lxterminal-daily produces the error "tar: recipe-0.1.9/.pc/01_create_POTFILES.skip.patch/POTFILES.skip: Cannot open: Permission denied" in https://launchpadlibrarian.net/74175712/buildlog.txt.gz
[07:52] <maxb> jmarsden: Hmm. It's probably worth retrying the build - this smells like it could be something like a bad umask setting or something alike on the builder node that processed your build
[07:53] <jmarsden> maxb: Tried on natty and oneiric, same result: https://launchpadlibrarian.net/74174459/buildlog.txt.gz
[07:58] <jmarsden> Trying rebuilds for both now, just in case...
[08:07] <maxb> hmm
[08:07] <maxb> Failed on thallium too
[08:07] <maxb> I don't know what to make of this
[08:07] <maxb> It seems more like an infrastructure failure than anything wrong with your recipe
[08:09] <maxb> bug 760735
[08:10] <wgrant> I'm not sure that's it.
[08:10] <wgrant> It's related.
[08:11] <maxb> it looks very much the same bug as jmarsden's buildlogs
[08:12] <wgrant> ... fair point, I can't read.
[09:23] <bac> Riddell: https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html
[09:24] <bac> Riddell: it has landed here https://qastaging.launchpad.net/
[11:01] <lag> When you delete a package, does it go instantly?
[11:02] <wgrant> lag: no, it can take up to half an hour to be removed.
[11:03] <wgrant> lag: And you can't ever reupload the same version to that archive again.
[11:03] <spiv> wgrant: you missed a chance to say "lag: there's some lag" :P
[11:03] <wgrant> True.
[11:03] <wgrant> I blame jetlag.
[11:05] <lag> I always get the blame for people being tired after a sprint :(
[11:05] <lag> It's annoying that you can't use the same version number
[11:06] <wgrant> Why do you want to?
[11:06] <wgrant> To use it again would be a lie.
[11:07] <lag> Because I'm starting again
[11:07] <spiv> wgrant: so is 'bzr uncommit' :P
[11:07] <wgrant> spiv: And we don't normally do that on public branches :)
[11:08] <wgrant> Also, bzr won't get confused by identical revnos, but apt will get confused by identical versions.
[11:40] <pmjdebruijn> hi all
[11:40] <pmjdebruijn> we're considering a commercial launchpad subscription
[11:42] <pmjdebruijn> however, I'm wondering how private PPAs work? are they just publicly unlisted? or do they have long obscure URLs to "protect" them, or are they htaccessed or something?
[11:44] <lifeless> pmjdebruijn: htaccessed more or less
[11:44] <lifeless> pmjdebruijn: you subscribe people one by one
[11:44] <lifeless> they get a unique access key for that ppa subscription
[12:14] <hrw> hi
[12:14] <hrw> is it normal that launchpad is unable to set 'fix released' for debian tracked bugs?
[12:14] <hrw> bug 739151 is fixed in ubuntu (fix released status) and in debian (fix commited status)
[12:14] <hrw> and it got closed in debian on 11 May 2011 so thats why I wondered
[12:15] <lifeless> hrw: yes
[12:15] <lifeless> hrw: or rather, the tracker seems to have an issue atm
[12:15] <lifeless> we have a high pri bug to look into it
[12:15] <hrw> ok, thanks
[12:15] <lifeless> gmb: you know about this stuff :P
[12:17] <gmb> ORLY?
[12:17] <gmb> Oh godsdammit.
[12:17] <gmb> THat.
[12:48] <hrw> bye
[14:59] <czajkowski> mrevell: having fun!
[15:00] <mrevell> Hey czajkowski. It's going well so far, thanks :)
[15:00] <czajkowski> git I'm there next week
[15:00] <StevenK> Good, then most of us will be gone. :-P
[15:01] <mrevell> We don't say "git" in this channel, we say "bzr".
[15:01] <mrevell> :)
[15:01] <mrevell> czajkowski, Ah, it's a shame you're gonna miss the meet-up tomorrow.
[15:02] <czajkowski> StevenK: charming! fecker!
[15:02] <czajkowski> mrevell: yes but you are a git :)
[15:02] <mrevell> heh
[15:02] <czajkowski> mrevell: next time you're in London if you dont say hi I will throttle you
[15:02] <mrevell> haha
[15:02] <czajkowski> I live in spitting distance of millbank now
[15:02] <mrevell> Okay, it's a deal. You don't throttle me, I'll say hi.
[15:02] <mrevell> Oh yeah? Cool. I'll let you know next time I'm down.
[15:02] <czajkowski> fair deal really
[15:02] <mrevell> I think I come out of the deal pretty well.
[15:02] <czajkowski> yeah live across the water london eye from my room here
[15:03] <mrevell> Nice
[15:03] <StevenK> czajkowski: :-)
[15:05] <czajkowski> mrevell: plus my team are having a special ubuntu hr for me returning next week :) so meh :p
[15:14] <SteveExodus> the absolute bare-arsed minimum package that debuild seems to be happy to make is a directory with NEWS and README in it .. and debian
[15:16] <bjwebb> hi, is this a good place to ask about ppa builds?
[15:16] <StevenK> What about them
[15:16] <StevenK> ?
[15:17] <bjwebb> why they fail
[15:18]  * SteveExodus grins
[15:18] <bjwebb> more specifically, if there's an easy way to build my package locally in the same way, so i can debug
[15:18] <SteveExodus> fakeroot debian/rules
[15:18] <tsimpson> !pbuilder
[15:18] <StevenK> tsimpson: Thanks! I was just trawling my brain for that link.
[15:19] <bjwebb> ahh
[15:19] <tsimpson> if it builds in pbuilder, it will likely build on LP, both run in a clean chroot etc
[15:21] <bjwebb> okay
[15:22] <SteveExodus> fakeroot debian/rules is a quicker test ... doesnt setup a complete new environment
[15:23] <StevenK> But it can mask problems.
[15:23] <SteveExodus> indeed .. but maybe OP wants to solve basic problems like me and get INSTANT turnaround
[15:24] <bjwebb> i think pbuilder is what i want. building the standard way seemed to work fine
[15:25] <SteveExodus> imo it is too slow to solve newbie problems
[15:25] <SteveExodus> first fakeroot since it is instant .. then pbuilder I think for proper .. then lp for proper proper
[15:26] <tsimpson> if you start a new pbuilder for every change you make, then it's slow, but you can script pbuilder to drop you into a shell on build failure
[15:26] <tsimpson> then it's just as fast as anything else you would do
[15:27] <SteveExodus> undestood .. but fakeroot costs little or nothing to setup ... can be used to trial many things instantly
[15:28] <tsimpson> yep
[15:28] <bjwebb> is there a good way to do local mirroring on the fly?
[15:33] <tsimpson> bjwebb: I haven't used it in a while, but I did setup mini-dinstall to create a local apt repo with the packages I built
[15:34] <bjwebb> tsimpson: i don't mean for the packages i built atm. just for caching multiple hits to download packages from the main repos
[15:36] <tsimpson> bjwebb: I see a few in the archive, like approx, apt-cacher, apt-cacher-ng and apt-proxy
[15:36] <bjwebb> thanks
[16:27] <doko> jelmer: skaet did ask about the possibility of a manual import for gcc/4.6
[16:28] <jelmer> doko: We should be able to do that
[16:28] <doko> jelmer: that would be nice, avoids us uploading the new compiler after feature freeze
[16:35] <doko> jelmer: could you confirm, if/when you start the import?
[16:38] <jelmer> doko: I'm currently pulling down what's already on launchpad, will keep you informed of the progress.
[16:39] <doko> jelmer: thanks!
[16:40] <dbart> I have an account subscribed to several trees in launchpad (configured to receive branch revision notification emails), and it hasn't received any emails since yesterday (the last email it received was dated 27 Jun 2011 15:19:13 +0000 (UTC)) and I know there have been a few branch revisions since then... is there any known current issue with launchpad notification emails?
[16:45] <poolie> dbart: not that i know of
[16:53] <dbart> poolie: ok :(
[16:54] <poolie> are you getting other mail from lp?
[16:54] <dbart> this account is not
[16:54] <poolie> no mail at all?
[16:55] <poolie> i would guess it's some kind of antispam thing at some point then
[16:56] <dbart> it's a special account for our automated test system, it watches for branch revision notification emails from launchpad and runs tests after each push
[16:57] <dbart> my personal launchpad account is receiving my launchpad mailing list emails just fine (same mail server)
[17:14] <jelmer> doko: the import is now in progress (600/26k revisions at the moment)
[17:22] <SteveExodus> any pointer to the best way to package a python module .py and .so?
[17:24] <jelmer> SteveExodus, please ask in #ubuntu-packaging
[17:26] <SteveExodus> jelmer: thanks
[17:29] <pcrews> Hi - does an admin still need to directly set team / project / branch / bug privileges to private for commercial users?
[18:24] <poolie> pcrews: i think yes
[18:31] <pcrews> poolie: ack, gracias : )
[22:05] <tumbleweed> meh, hitting lots of launchpad timeouts on APIs tonight
[22:07] <mhall119> I need help writing a bzr-builder recipe
[22:07] <mhall119> I currently have http://paste.ubuntu.com/634566/
[22:08] <mhall119> but I was told I can use one reciple and one package branch to build package for multiple distros/releases
[22:09] <nigelb> mhall119: everyone except lifeless is probably in dublin ;)
[22:09] <tumbleweed> mhall119: the releases to build for are an option on the build recipe page (assuming your source packages will be buildable on all releases)
[22:10] <mhall119> tumbleweed: doesn't the release name have to be in the changelog though?
[22:10] <mhall119> or no?
[22:10] <tumbleweed> mhall119: no, it'll take care of that
[22:10] <mhall119> oh cool
[22:10] <mhall119> so what should I have in my changelog then?
[22:12] <tumbleweed> whatever you want, I think it adds an entry when it does the recipe build
[22:12] <mhall119> ok
[22:13] <mhall119> I like that loco-directory is used in the bzr-builder examples....
[22:51] <gustonegro> is there a way I can just import another package from a launchpad ppa into my launchpad ppa?
[22:51] <gustonegro> I see that this person has a package in his ppa from another lp ppa: https://launchpad.net/~xapantu/+archive/euclide
[22:55] <gustonegro> oh, +copy-packages was my friend


[00:00] <TheMarius> yea
[00:07] <Roey> anyone here do big iron stuff?  I was wondering, what is the future of datacenters and of virtualization look like?
[00:07] <Roey> hihi TheMarius
[00:08] <TheMarius> <- not me
[00:08] <Roey> lol ok :)
[00:09] <TheMarius> im not even running kubuntu atm, but mint kde on my skull canyon
[06:03] <weaponG> Hello
[06:04] <weaponG> hello
[08:14] <Guest61184> Hi, I'm in the process of installing Kubuntu, if i choose "Guided - use entire disk and set up encrypted LVM" and choose an unused drive, will my other drives be untouched?
[08:28] <zxq9> Guest61184: It will need to install a bootloader (grub2) on whatever the system boot disk is.
[08:28] <zxq9> But otherwise, yes, there will not be any changes made to any partitions on any other disks than the one(s) you select for installation.
[08:29] <zxq9> The bootloader will find whatever other systems you have installed (you should already be able to see them in your disk selection/partition editing screen), and create boot entries for them.
[08:30] <Guest61184> zxq9: Nice, thanks for info :)
[08:43] <IrcsomeBot1> Kirann ... was added by: Kirann ...
 Done updating Kubuntu
 https://i.imgur.com/PaMfk6U.jpg
 @bittin, Whare and what is this?
 @acheronuk, Linux meetup in Uppsala, Sweden was about to go there but got sick :(
 Hopefully happen in Indonesia :)
[12:18] <BluesKaj> Hi folks
[18:11] <aboogesnickle> Would this be where I could find help with a monitor issue?
[23:51] <D0U91E> is there a beta for 18.04 yet?


[09:08] <m14ed> any op in here for one of the puppy channels ?
[09:08] <m14ed> ikonia
[09:09] <m14ed> or kloeri
[09:10] <bazhang> m14ed, check the puppy channel access list
[09:10] <bazhang> that has nothing to do with ubuntu
[09:10] <Tin_man> weve had a real disruptive user on, he's also on #ubuntu
[09:10] <bazhang>  /msg chanserv access ##channel list
[09:10] <Tin_man> but behaving himself/herself there
[09:13] <m14ed> bazhang ? i see the text  , but do not  understand it
[09:13] <m14ed> i know the command /msg  ,
[09:13] <m14ed> would you explain the rest please
[09:14] <Tin_man> looks greek to me also..
[09:14] <Tin_man> do you insert his nick somewhere, or what
[09:14] <bazhang> nope
[09:14] <m14ed> easy tinz, don't laugh at the picture
[09:15] <m14ed> what i am asking ,,, the ##channel list ..... ?\
[09:15] <bazhang> lets all head to #freenode for this, departing here at the same time
[09:15] <Tin_man> i'm going to save the log, so when we do figure it out well have it..
[09:15] <m14ed> ok freenode
[09:15] <bazhang> Tin_man, m14ed #freenode
[09:16] <m14ed> gone to freenode
[09:16] <bazhang> please exit here and join there Tin_man m14ed
[09:18] <bazhang> m14ed, you can ask in #freenode, exit this channel
[09:22] <bazhang> m14ed, I can see you active there, so please exit here
[09:23] <m14ed> thank you sir, sorry for the extra head count , !!
 google's dns seems to be iffy
[09:39] <bazhang> rly
 u guys r part of my irc botnet
[18:03] <Pici> not that it actually means anything, but #python is getting close to overtaking #ubuntu in user count.
[18:04] <bazhang> I thought arch channel already was
[18:04] <Pici> probably
[18:28] <k1l> so python is the new troll target then?
[18:29] <k1l> #python, that is
[18:29] <Pici> not really
[18:29] <Pici> its +r too
[18:29] <k1l> :(
[18:48] <elky> they have enough former php devs showing up there, the trolls just need to sit and wait and watch the free show
[18:48] <k1l> hihi
 ubuntu won't run on my keyboard..
[18:59] <bazhang> the new "trying to install buntu on my bmw via the tape player"
[19:02] <genii> Probably a bluetooth keyboard or something
[19:03] <Pici> sigh
[19:04] <bazhang> no
[19:04] <bazhang> he rooted it with enlightenment
[19:04] <genii> Hm
[19:04] <bazhang> thanks k1l
[19:05] <bazhang> he and kenrifkin were tag teaming
[19:05] <k1l> the "how to install on my keyboard" sounds too familiar
 and after that, where the fuck is solitare?
[19:05] <k1l> that got me on the backlog anyway
[19:05] <bazhang> * n00buser<EMAIL_ADDRESS>has joined
[19:05] <bazhang> round 3
[19:09] <k1l> KenRifkin  was emery
[19:09] <k1l> that is a known issue troll, which was the one with the "how do i get root on ubuntu" and install ubuntu into a keyboard troll
[19:10] <bazhang> yeah
[19:10] <bazhang> I put in my photoshop disc etc etc
[19:10] <k1l> 64202 is the ban still set on his cloak


[02:48] <Xpistos> Hey guys. I had a quick question, how do formulate and if then statement where the "if" is 01,04,07,10 and then is anything
[02:48] <Xpistos> anything else sorry
[02:49] <Xpistos> Anything is else to simply do nothing, or should I just use an if statement for that
[02:57] <arraybolt3> Xpistos: I'm not sure I understand your question.
[02:57] <arraybolt3> What language is this in? Bash?
[02:57] <arraybolt3> And by "01,04,07,10", what is that? A list of integers? A string?
[02:57] <Xpistos> Bash
[02:57] <Xpistos> if [ $QUARTERLY_REPORT_CHECK == "01|04|07|10" ]
[02:57] <arraybolt3> Ah, so you want it to match any of those four.
[02:57] <Xpistos> I am checking to see if it is Jan, Apr , etc
[02:58] <arraybolt3> One moment, lemme try something...
[02:58] <Xpistos> I am not sure how to give a list in an if statement, only in case
[02:59] <arraybolt3> The best way I can think of to do this would be to use a "for" loop to iterate through the list and try each individual item in the "if" statement.
[03:00] <arraybolt3> There's also the -o switch in "test" which may help.
[03:00] <arraybolt3> But that would result in a very long and duplicate-ridden line.
[03:01] <arraybolt3> Xpistos: This might help: https://bpa.st/F47SA
[03:01] <Xpistos> that will do it
[03:02] <sergiodj> if it's bash, you can regexp-match using [[ ]] and =~
[03:02] <Xpistos> if it isn't 01 04 07 10 i want it to skip the quarterly report so that works
[03:02] <sergiodj> a=01; if [[ $a =~ 01|02|03 ]]; then echo "MATCHED"; fi;
[03:03] <arraybolt3> Xpistos: sergiodj's idea is probably lighter on resources and is a bit more concise, so it might be worth trying. (I'm not exactly a Bash expert, I just know enough to hack around and make things happen :P)
[03:04] <Xpistos> sergiodj: checking if I got it correct
[03:08] <Xpistos> sergiodj: That worked. thanks! and Thanks arraybolt3. You gave me some more options as well
[05:34] <hermit> someone pointed out a problem with phased roll out for server admin software.
[05:36] <hermit> To populate the list the upgradable switch is used.  That would mean you are bypassing the 'phasing' by selecting individual packages.  There is no indication of what would otherwise be held.
[16:25] <teward> bryceh: we might not want to push to backport SSL related things to older Ubuntu versions and nginx versions, whne stuff is added to 1.19.x it's built upon other 1.19.x stuff and that's a feature devel branch, so if we wanted that TLS 1.3 stuff we'd be better off doing a 1.20.x backport entirely.
[16:25] <teward> just saying
[16:26] <teward> cc cpaelzer as they TIL ~20 min ago - see bug #2007744
[16:26] -ubottu:#ubuntu-server- Bug 2007744 in nginx (Ubuntu) "Cannot configure openssl 1.3 ciphersuits in nginx on ubuntu 22.04" [Wishlist, Incomplete] https://launchpad.net/bugs/2007744
[16:29] <teward> cpaelzer: bryceh: we COULD do a backport of 1.22.0-* to -backports for the current LTS which would enable things
[16:30] <teward> that bypasses the SRU process and "fixes" the bug by allowing the newer version to be available (which is what -backports is teeeeeeeechnically for)


[00:03] <bluesabre> brainwash: so, what does it mean by versioned help files?
[00:05] <brainwash> xfce_dialog_show_help_with_version ()
[00:05] <brainwash> it's http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/xfce4-settings/utopic/view/head:/debian/patches/02_versioned-help-files.patch
[00:06] <brainwash> once it has been applied upstream we can drop it downstream :)
[00:07] <bluesabre> ah, gotcha
[00:07] <bluesabre> ochosi, as the other -settings guy, approve?
[00:08] <ochosi> bluesabre: +1
[00:11] <brainwash> can we cleanup the two theme patches somehow?
[00:11] <brainwash> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/xfce4-settings/utopic/files/head:/debian/patches/
[00:12] <brainwash> one is for debian and the second one overrides it once again for (x)ubuntu
[00:13] <brainwash> but what are the upstream defaults for ThemeName and IconThemeName?
[00:22] <bluesabre> blank, but I think that means Xfce and Rodent, per mr_pouit's comment: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/xfce4-settings/utopic/view/head:/debian/patches/xubuntu_vanilla-session-themes.patch
[00:23] <bluesabre> https://launchpad.net/ubuntu/utopic/+source/xubuntu-default-settings/14.10.5
[00:24] <bluesabre> ^ now in utopic, next builds should build
[00:24] <bluesabre> taking a break, bbl
[00:28] <brainwash> ah nice
[00:28] <brainwash> and I can del https://code.launchpad.net/~thad-fisch/xubuntu-default-settings/tooltip-size
[00:30] <brainwash> bluesabre: please change the status of https://bugzilla.xfce.org/show_bug.cgi?id=10740 to fixed
[00:36] <brainwash> bluesabre: can compton located /etc/xdg/xdg-xubuntu/compton.conf ?
[00:36] <brainwash> locate
[00:36] <Unit193> Aha, that makes more sense.  compton uses xdg_config_dirs.
[00:37] <brainwash> so.. it works?
[00:38] <Unit193> Not tested it, but I'd say so.
[00:38] <brainwash> even with the missing . ?
[00:39] <brainwash> should be a hidden config file I think
[00:39] <Unit193> Why?  It's not in ~/
[00:40] <brainwash> ok
[00:40] <brainwash> I had the skel scheme in mind
[00:40] <Unit193> https://github.com/chjj/compton/blob/master/src/compton.c#L5255
[00:41] <Unit193> const static char *config_filename = "/compton.conf";
[00:42] <brainwash> yea
[00:42] <Unit193> (I link to it because you should be able to read it far better than me. :) )
[00:44] <brainwash> so the next question is: does utopic still ship an outdated version of compton?
[00:44] <Unit193> Beta2, IIRC.
[00:44] <Unit193> !info compton utopic
[00:45] <brainwash> 2013-11-04
[00:45] <brainwash> old stuff
[00:45] <brainwash> :/
[00:45] <Unit193> Latest tagged.  We still aren't seeding it, just some handy config in case users want to use it.
[00:46] <brainwash> right, having a nice config helps
[00:46] <brainwash> but the user still has to deal with the outdated version of compton
[00:46] <brainwash> in case we recommend it
[00:47] <brainwash> recommend to try it -> tear free
[00:47]  * Unit193 shrugs, no newer releases.
[00:49] <brainwash> oh man, someone wants the fix for bug 1310264 to be backported to trusty
[00:50] <brainwash> can we do it?
[00:50] <Unit193> He can do it, but that's a backport of a UI change, soo.
[00:51] <brainwash> indeed, it's a ui change
[00:53] <brainwash> so the answer is NO
[06:34] <elfy> bluesabre: thanks :)
[07:22] <brainwash> bluesabre: any plans to sru/backport bug 1310264 to trusty? if no, then we should unlink the report from the 14.04.x blueprint
[07:23] <brainwash> it's just a minimal ui change after all
[07:24] <brainwash> the now visible "settings" submenu entry
[07:26] <elfy> ochosi: I asked in -release for a build of xubuntu, off out for the day - if you get chance could you do the same at some point
[07:46] <ochosi> elfy: sure thing, thanks!
[07:50] <ochosi> and thanks for updating the folks on the ML
[08:52] <Unit193> ochosi: I see you hiding, https://launchpad.net/~unit193/+archive/ubuntu/xfce will have something for you in a minute.
[09:17] <ochosi> Unit193: a-ha a-ha, what is it?
[09:17] <ochosi> ah, the dashboard?
[09:18] <Unit193> Nothing new, and yeah, the only one that was built today. :D
[09:19] <ochosi> have you tested it?
[09:21] <Unit193> Test built. :P
[09:21] <ochosi> righty, i just tested it, it works ok
[09:21] <ochosi> i'll copy it over
[09:21] <ochosi> thanks!
[09:22] <Unit193> Sure thing, doc.
[09:22] <ochosi> i'm wondering btw whether we should drop the saucy versions that we still have
[09:22] <ochosi> since it's EOL and all
[09:23] <Unit193> Outdated and can't be updated?  I've been resisting nagging you and Sean about removing it, yeah.
[09:24] <ochosi> done
[09:25] <Unit193> Danke.
[09:26] <ochosi> well thank you
[09:26] <ochosi> i guess we should write a blog post about that PPA
[09:27] <Unit193> (FWIW, Sean has access to the git repo hosting it too, in case I'm busy, in the hospital, dead, etc, etc.)
[09:27] <Unit193> Sure.
[09:27] <ochosi> righty
[09:27] <ochosi> good to know, let's hope it doesn't come to any of that (incl. you being busy ;))
[09:29] <Unit193> Meh, hospital would actually mean less busy.  When I was in last I'm pretty sure I got a chance to update a couple packages. :P
[09:29] <ochosi> hehe
[09:29] <Unit193> By the looks of it, the PPA is fairly used.
[09:29] <ochosi> what looks?
[09:29] <ochosi> (have they introduced lp statistics and i didn't notice?)
[09:36] <brainwash> gdmflexiserver is gone in 14.04, but xfswitch-plugin and the panel action buttons still require it
[09:36] <brainwash> bug 1320560
[09:37] <brainwash> we could install a wrapper to mimic gdmflexiserver
[09:37] <brainwash> see comment #4
[09:38] <brainwash> fixing the actual source would be the better option, but can we just go gdmflexiserver -> dm-tool?
[09:38] <brainwash> dm-tool is lightdm only
[09:39] <brainwash> (I think)
[09:40] <brainwash> xscreensaver should be also affected
[09:41] <brainwash> if you click on "new login" while it locks the screen
[09:51] <ochosi> the thing is that if gnome2 had really gone away, we could just drop and forget about gdmflexiserver
[09:52] <ochosi> but now that there are forks of it that seem to stick around for now, alternatives to lightdm can still easily be used outside of gnome
[09:52] <ochosi> (from what i understand, the new gdm is tightly integrated in gnome3, so it's not as easy anymore to use that with a different DE)
[09:54] <brainwash> the problem is that there has to be some sort of script for user switching via display manager
[09:55] <brainwash> I'm not sure if we can just hardcode dm-tool
[09:55]  * ochosi replied
[09:56] <brainwash> I see
[09:56] <ochosi> i guess the really best way to fix this would be to implement display-manager awareness in xfce4-session
[09:56] <ochosi> and then just provide a commandline switch for that, so that e.g. panel-plugins can safely use that
[09:57] <brainwash> yes, this could be done via a "simple" bash script
[09:57] <brainwash> like xflock4
[09:57] <ochosi> implementing this sort of DM detection in every other place is silly
[09:57] <ochosi> gdmflexiserver was such a "simple" bash script iirc
[09:57] <brainwash> indeed
[09:57] <ochosi> despite its name it worked fine with other DMs than gdm
[09:57] <ochosi> (like the "flexi" part implies)
[09:57] <brainwash> that's the reason I don't like hardcoding dm-tool into the code
[09:58] <ochosi> i think for ubuntu it's ok
[09:58] <brainwash> I think so too
[09:58] <ochosi> i suggest you prep the patch since you already figured out everything
[09:59] <brainwash> ok
[09:59] <ochosi> maybe bluesabre can push it (whenever he's back online)
[10:00] <brainwash> xscreensaver is also affected, not sure about that one? just submit a patch and hope for the best?
[10:01] <brainwash> ah bug 1309917
[10:01] <brainwash> the maintainer already replied
[10:02] <brainwash> http://anonscm.debian.org/cgit/collab-maint/xscreensaver.git/tree/debian/xscreensaver-wrapper.sh
[10:02] <brainwash> ^ :D
[10:03] <ochosi> well the same goes for xscreensaver in fact
[10:03] <ochosi> patching it in ubuntu is the okay-shortcut for now
[11:03] <ochosi> wb bluesabre
[11:04] <bluesabre> what'd I miss?
[11:04] <ochosi> one sec
[11:05] <ochosi> brainwash talked about this bug and i commented and if he comes up with a patch, he'll get in touch with you https://launchpad.net/bugs/1320560
[11:05] <ochosi> oh, and i asked in -release for a rebuild of our image
[11:05] <ochosi> but no response so far, stgraber seems to be afk
[11:06] <brainwash> and you missed to close https://bugzilla.xfce.org/show_bug.cgi?id=10740 :P
[11:06] <bluesabre> brainwash: not a bug admin for xfce4-settings, can't close it
[11:07] <brainwash> but you can commit to trunk.. strange
[11:07] <bluesabre> two separate sites :)
[11:07] <ochosi> done
[11:07] <brainwash> ochosi: thank you
[11:07] <ochosi> np
[11:08] <bluesabre> re: https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1310264 its a UI change, so nope
[11:08] <ochosi> (and it's easy enough for single users to fix themselves)
[11:08] <brainwash> can't this ui change be considered a bug fix?
[11:09] <ochosi> someone could write a blog post for xu.org about how to fix it though
[11:10] <bluesabre> maybe
[11:11] <brainwash> if the user has already messed with the menu file (menulibre), then he still won't be able to find the hidden entries
[11:11] <bluesabre> yup
[11:12] <brainwash> ok then
[11:13] <bluesabre> its still a pretty minor issue
[11:13] <ochosi> +1
[11:14] <bluesabre> ochosi: are we waiting for tonight to get our iso spun, or are we requesting an early respin?
[11:14] <brainwash> for advanced users it is, but new xubuntu users are getting confused by the missing entries
[11:14] <bluesabre> new users couldn't find menu items in the last menu either though... they still had to click on the settings manager icon
[11:15] <ochosi> bluesabre: i asked for a respin asap, but we'll see when it really happens...
[11:15] <bluesabre> ochosi: cool, thanks
[11:16] <brainwash> bluesabre: yeah, but now we do offer the search functionality of whiskermenu, and people expect to find everything with it :)
[11:16] <ochosi> they won't find files with it
[11:16] <ochosi> anyway, let it go
[11:17] <brainwash> hehe, I've already unlinked it from the 14.04.1 blueprint
[11:18] <ochosi> good
[11:18] <bluesabre> speaking of which
[11:18] <bluesabre> do we want to add the catfish shortcut?
[11:19] <ochosi> yup, that'd be nice
[11:19] <bluesabre> and what would be a good one?
[11:19] <brainwash> a general keyboard shortcut?
[11:20] <brainwash> global
[11:20] <ochosi> bluesabre: problem is "locate" or "find" might be ambiguous
[11:20] <bluesabre> as in, type into whiskermenu "find donuts" and catfish loads and immediately starts to search
[11:20] <ochosi> and "search" doesn't really cut it imo
[11:21] <bluesabre> though it might be more interested in worms or grubs
[11:21] <ochosi> maybe "ok catfish"
[11:21] <ochosi> ah well, let's go for "find". makes the most sense
[11:23] <bluesabre> brainwash: if you're running utopic and have catfish 1.2... like this: http://i.imgur.com/rCFuosC.png
[11:25] <brainwash> makes sense to add something like that
[11:26] <brainwash> "!f" would be too simple / not obvious enough, right?
[11:27] <ochosi> i think it might not be very discoverable either way, but "find" makes it sound very natural
[11:27] <elfy> asked -release re beta build again
[11:28] <ochosi> and people who frequently use it can change the shortcut easily
[11:28] <bluesabre> elfy: thanks
[11:28] <ochosi> elfy: i pinged stgraber earlier, but he doesn't seem to be about
[11:28] <elfy> bluesabre: as far as you know there's nothing else that would stop it building?
[11:28] <bluesabre> that's the only thing
[11:29] <elfy> ochosi: yea - I think he's -5 or 6 hours
[11:29] <bluesabre> if it fails this time, I'd be shocked
[11:30] <elfy> why there's only one person who can get the build running I don't know - but I bet it'd get done for ubuntu earlier
[11:30] <ochosi> possible
[11:36] <elfy> ochosi: so you got any plans/idea for what we should do if the respin is late tonight - given that release is supposed to be tomorrow?
[11:36] <elfy> knome was talking yesterday about releasing late - I'm not worried if we do or don't
[11:38] <bluesabre> I'll do as much iso testing as I am able tonight
[11:39] <elfy> bluesabre: yea - that relies on us gettting something to test :)
[11:39] <bluesabre> yup
[11:40] <elfy> I'll not be able to do hardware tests in time for tomorrow, be vm only
[11:40] <bluesabre> I get home when canonical starts going to bed, so I should be in the clear
[11:40] <elfy> :)
[11:40] <elfy> stgraber appeared mid-afternoon my time yesterday, would guess same today
[11:41] <bluesabre> ochosi: want to draft the release notes today, or is that usually somebody else?
[11:42] <ochosi> bluesabre: not sure we have a definitive person who is responsible for the release notes
[11:42] <bluesabre> (and then I can review and add things tonight)
[11:42] <bluesabre> I see
[11:42] <ochosi> actually it might be good if >1 people could work on it
[11:42] <bluesabre> yeah
[11:42] <ochosi> otherwise things might be overlooked
[11:42] <elfy> nope - generally it was knome and me previously - better to whack it on a pad or something so everyone can get to it
[11:43] <bluesabre> good idea
[11:43] <ochosi> http://pad.ubuntu.com/S030Pt7VHy
[11:43] <elfy> previoulsy we've mostly built it off of old ones
[11:43] <ochosi> yeah, feel free to paste in a skeleton
[11:47] <elfy> bbl
[11:50] <brainwash> Unit193: are you going to re-include 02-remove-unused-maximize-button.patch (xfwm4, not applied upstream)
[11:51] <brainwash> not sure if you've already answered this question
[11:52] <ochosi> bluesabre, elfy: i gotta run now, but i'll look at the release notes again a little later in the day
[11:52] <bluesabre> ok, I'm just adding notes for now which can be used to put things together
[11:52] <ochosi> yup, sounds good
[11:52] <ochosi> ttyl
[11:57] <Unit193> Don't know why I thought it was no longer needed, I normally check those well.  I would since it's my mistake, but it is easier for Sean.  Anyway, if not I'll get to it a bit later today.
[11:58] <bluesabre> Unit193: you know where to find such tools... how can I search for what I've uploaded to utopic?
[11:59] <brainwash> Unit193: alright
[11:59] <Unit193> brainwash: Sorry.
[11:59] <brainwash> nobody would have noticed it :P
[12:01] <Unit193> bluesabre: And I know how to find what packages have been sponsored for you, but not what you've uploaded since I can't do that.
[12:01] <bluesabre> ah, gotcha
[12:01] <bluesabre> I think I've got nearly everything on the pad now
[12:04] <bluesabre> feel free to add notes for the packages if there is anything that makes them special :)
[12:08] <bluesabre> bbl
[13:22] <Unit193> bluesabre: If you want to grab+edit or whatever, it's uploaded.
[14:13] <brainwash> anyone here using a dual monitor setup? if yes, please check if pkexec also triggers bug 152855
[14:14] <brainwash> ancient bug :/
[14:20] <elfy> Unit193: I suppose we need to get a core wiki page sorted for core rather than your one
[14:20] <ochosi> elfy: rebuild kicked off by stgraber
[14:22] <elfy> saw - didn't realise we could do that when there's not one there at all
[14:23] <elfy> ochosi: we couldn't have done that, nothing to select to rebuild on the beta page
[14:23] <ochosi> so a question of rights then i guess
[14:23] <elfy> you have them I think
[14:23] <elfy> http://iso.qa.ubuntu.com/qatracker/milestones/315/builds
[14:24] <elfy> that's the dailies - once you've logged in do you see what I see? http://www.zimagez.com/zimage/screenshot-270814-152435.php
[14:24] <elfy> eg the admin bit at the bottom?
[14:28] <elfy> Unit193: - draft xubuntu minimal page on xubuntu.org done
[14:33] <elfy> ochosi: did a bit with the beta pad too
[14:53] <elfy> and ... we've got some images to test now :p
[14:54] <slickymasterWork> yeaps :)
[14:54]  * slickymasterWork will comply with what is promised
[15:34] <elfy> knome: not sure who can access the social stuff - but if you can, can you get beta testing on there
[15:34]  * elfy vaguely remembers pleia2 being afk
[15:43] <slickymasterWork> brainwash: you mean in relation to the at-spi2-core (Ubuntu) package?
[15:49] <elfy> paulw2u appears on the tracker - that's one I can generally rely on to turn up :)
[17:25] <elfy> ochosi Unit193 - core is now available on the tracker for testing
[17:37] <pleia2> elfy: done
[17:38] <elfy> pleia2: awesome thanks - wasn't sure if you were about or not :)
[17:38] <pleia2> chaos day, have work and flight later :)
[17:38] <elfy> :)
[17:39]  * elfy had that for a while - 2 machines doing b tests - coudln't remember which was doing 32 and which 64 :p
[17:42]  * elfy wanders away from the tracker now
[17:42] <pleia2> hehe
[17:43] <elfy> I'm just glad we don't have alternates to test ;)
[17:56] <ochosi> elfy: i'm around now
[17:58] <ochosi> nope, i don't see that admin bit there
[17:59] <ochosi> oh, indeed, now i see it
[17:59] <ochosi> weird, when removing the filters (before i saw all products) it suddenly appeared
[17:59] <ochosi> wasn't there before
[18:00] <ochosi> that's actually quite handy that we can respin ourselves now
[18:00] <elfy> ok - cool, so to request a rebuild for 64 say, select the box next to it - then in the bottom request it :)
[18:00] <elfy> when we're ready to release - select then mark as ready
[18:01] <elfy> back in an hour ish
[18:02] <elfy> just don't practise today :p
[18:02] <ochosi> hehe
[18:02] <ochosi> ok
[18:02] <ochosi> ttyl
[18:49] <Unit193> Dang man, we have a lot of hardly started languages in the docs.  Just checked, each and every one of them validates still. \o/
[19:09] <elfy> ochosi: back for a bit if you need anything
[19:10] <Unit193> elfy: Hellos.
[19:12] <elfy> hi Unit193
[19:28] <elfy> wb Luyin :)
[19:29] <Luyin> thx elfy
[19:29] <Luyin> I'm just trying to find my way through all these websites
[19:29] <elfy> Luyin: if you've got time and can do a test install - vm's fine - we're testing the beta right now
[19:30] <elfy> http://iso.qa.ubuntu.com/qatracker/milestones/322/builds
[19:31] <brainwash> elfy: this error bug 1359439 ?
[19:33] <brainwash> most likely
[19:33] <Luyin> ok, I'm on it elfy
[19:33] <Luyin> just give me a sec to find myself around there
[19:33] <elfy> ok ... so that's random brainwash - what are you talking about :)
[19:33] <elfy> Luyin: okey doke - I'm about for a while if you need anything
[19:33] <brainwash> elfy: your report "mage fails to start try/install screen" :P
[19:33] <brainwash> Image
[19:34] <elfy> oic - that makes more sense now :)
[19:34] <Luyin> elfy: the xubuntu desktop at the bottom of the page?
[19:34] <elfy> possible - I'm not that worried about it tbh brainwash - more likely to be sorted by a ubuntu type person
[19:35] <elfy> Luyin: yep :)
[19:35] <Luyin> ok, which one? or just both?
[19:35] <elfy> Luyin: there are 5 tests in each - choose one arch and go for it :)
[19:35] <Luyin> okay, I'll take the 64bit one
[19:36] <elfy> anything that you do will have my gratitude :)
[19:36] <Luyin> hehe
[19:37]  * elfy wonders what lxpolkit actually is and if it's what it sounds like whether we could have similar
[19:38] <brainwash> that's a random thought
[19:39] <elfy> not *completely* random - saw mention of it in -quality :p
[19:39] <brainwash> we already use gnome's polkit auth agent I think
[19:40] <elfy> aah - okey doke - just wondering :)
[19:40] <Luyin> elfy: https://wiki.ubuntu.com/Testing/ISO/Walkthrough here it says one should get the iso via TestDrive, but I'm downloading it via browser atm, is that correct?
[19:40] <brainwash> elfy: yes, it's policykit-1-gnome
[19:40] <elfy> Luyin: you can use testdrive - but if you know you're way around a vm then it's not really needed - and in that case download however you want
[19:41] <Luyin> okay ^^
[19:41]  * Unit193 ponders why it'd say to use testdrive.
[19:41] <brainwash> elfy: luckily we don't hate gnome as much as LXDE does :)
[19:41] <elfy> Luyin: once you've got it - you can use zsync to update it if you want to not download the whole thing everytime - depends who long between test
[19:42] <elfy> Unit193: check the wiki page last edited by ;)
[19:42] <Unit193> elfy: I didn't have to.
[19:42] <elfy> ha ha ha
[19:42]  * elfy has no idea what testdrive even looks like
[19:43] <Unit193> Erm, requirements?  Well then.
[19:43] <elfy> :)
[19:44] <Unit193> Guess we don't support qemu, kvm, or VMware's.
[19:44] <elfy> if I was interested enough I could rip that up and start again
[19:46] <Luyin> hmm, seems my virtualbox is only able to run 32bit kernels.
[19:47] <elfy> do 32 bit then :)
[19:48] <elfy> brainwash: thanks
[20:02] <Luyin> ok, it's getting interesting :D
[20:03] <Unit193> elfy: I presume you didn't see my question the other day.  Utopic seem a bit slower to you than Trusty?
[20:04] <elfy> Unit193: nope didn't notice that - sorry. It *seems* a bit slower sometimes if I've booted systemd
[20:04] <Unit193> Hrm.
[20:04] <elfy> but generally I don't notice much with upstart
[20:04] <elfy> unless I've been using vbox - then everything seems a lot slower than it did using it in trusty or saucy
[20:06] <Unit193> systemd 214 vs systemd 214, seems to hang a couple seconds at times.
[20:07] <brainwash> 214?
[20:10] <Luyin> elfy: I've got a question about https://wiki.ubuntu.com/QATeam/Hardware this. it says one should edit the top table – but there's no button or similar to click where I can edit anything. or am I missing something?
[20:11] <Luyin> and something else: I chose the "manual partition"-version for testing. so I guess I'm allowed to partition myself in order to finish the test?
[20:11] <elfy> Luyin: none of that's really all that important tbh /Hardware
[20:12] <elfy> yep - you can choose the partitions yourself for that test
[20:13] <elfy> I tend to do it in this order, but then I tend to do the whole lot - whole disk, resize, then manual on one of the resized partitions
[20:13] <Luyin> you're kidding? when I help, I'm doing it thoroughly :P
[20:13] <elfy> Luyin: you won't see me on that list and I've been doing this for years
[20:13] <Luyin> okay, lol
[20:14] <elfy> you'll not find balloons on there either and he's the Canonical Community QA guy
[20:14] <elfy> so - you can do it if you want - but quite frankly - getting more than a couple of people testing is a LOT more important to me :)
[20:15] <Luyin> hehe okay
[20:16]  * elfy really should write a more detailed QA procedure for us rather than have to send people to ubuntu pages and then it not be *quite* what we want
[20:18] <Unit193> brainwash: What about it?
[20:18] <brainwash> Unit193: ubuntu is stuck with 208, isn't it?
[20:18] <Unit193> elfy: "core is now available on the tracker for testing" does that mean do it right now?
[20:19] <Unit193> brainwash: Yep, in utopic at least, FF and all.
[20:20] <brainwash> still don't like to boot with systemd.. it feels like voodo magic :)
[20:20] <elfy> Unit193: no - I was just letting you and ochosi know where we are :)
[20:20] <elfy> there's not much chance of me asking anyone to do that right at the moment :p
[20:20] <Unit193> brainwash: Heh, yeeeah.  I'm not sure if I like it or greatly dislike it, it's hard to tell as some of the features are nice, and some really bad.
[20:20] <Unit193> elfy: OK, great then!
[20:21] <brainwash> Unit193: exactly
[20:21] <Unit193> brainwash: systemd-analyze, the information it keeps per service, and some of that is dang nice, others not so much.
[20:33] <elfy> I wish I got the desktop as quickly as systemd says it takes :p
[20:33] <Unit193> Hah. :P
[20:33] <Unit193> elfy: Try 214! :P
[20:33] <elfy> I think I boot to desktop in about 40-50s
[20:34] <elfy> systemd ~25s
[20:35] <elfy> Unit193: did you look at the core draft on xubuntu.org yet?
[20:35] <elfy> need to get that sorted before we call
[20:35] <elfy> though I could do it in the mail if necessary
[20:37] <knome> re: release notes, i think the release team should generally take the lead on that, especially since the current setup is (by design): project lead, one person who's on top of development, one person who's on top of QA/testing/Bugs
[20:37] <knome> elfy, i can do twitter..
[20:38] <elfy> ta
[20:38] <knome> what do you want in there? probably a certain mail mentioned?
[20:38] <Unit193> elfy: Oh, we even want to mention the second one?  OK, works for me.  Seems to be about what I wrote up too.  Perhaps it'd be useful to link to http://docs.xubuntu.org/1404/appendix-packages.html ?
[20:38] <knome> oh, hmm, somebody tweeted
[20:38] <elfy> knome: pleia2 did do something though - not checked what yet
[20:39] <elfy> Unit193: it was a draft - I just copied what you wrote in yours and tacked on testing :p
[20:39] <knome> yep, she's definitely tweeted 3h ago
[20:39] <elfy> cool - thanks knome
[20:39] <knome> np
[20:40] <knome> we definitely need to involve the "other" social media admins more on this channel
[20:40] <elfy> Unit193: yea - agreed to adding that to the page
[20:40] <knome> we have *at least* pleia2 + 1 other person on each outlet
[20:40] <elfy> knome: I'm glad that doesn't involve me :p
[20:40] <ochosi> elfy: why do the release notes say "xfwm4 4.12"?
[20:40] <Unit193> elfy: Right, sounds good to me.  Figured it might be, kind of wrote it last cycle precisely for xubuntu-core.
[20:40] <knome> elfy, heh, well it should make your work easier :)
[20:41] <elfy> ochosi: was just picking up information from bluesabre's list
[20:41] <Unit193> ochosi: I have no idea if you're interested, but you are not identified.
[20:41] <ochosi> elfy: says 4.11.2 there though :)
[20:41] <ochosi> Unit193: ah, thanks
[20:41] <elfy> fat finger syndrome then I suspect ochosi :)
[20:42] <ochosi> lol
[20:42] <elfy> ochosi: and are we just going to do a release announcement or both?
[20:42] <knome> elfy, holstein is an admin of the FB group..
[20:42] <ochosi> elfy: both?
[20:43] <elfy> knome: orite - useful to know :)
[20:43] <knome> yep, will ask him to join this channel the next time i see him active (and remember)
[20:43] <elfy> ochosi: suits me - but I'll not be about morning tomorrow
[20:43] <elfy> knome: he is now
[20:44] <ochosi> elfy: no, my question was what do you mean with a release announcement *or both* ?
[20:44] <elfy> lol - sorry - announcement is on xubuntu.org release notes are on ubuntu wiki
[20:44] <ochosi> oh right
[20:44] <ochosi> well i'd probably do both
[20:45] <elfy> ok - well I'll ensure that the wiki one is ok by tomorrow afternoon
[20:45] <knome> announcement has generally been the non-technical one, notes the more technical one; and usually useful for anything else than point releases at least
[20:46] <elfy> wb boss :p
[20:46] <elfy> knome: yep
[20:48] <ochosi> knome: if you wanna help us move along a bit, that'd be much appreciated: http://pad.ubuntu.com/S030Pt7VHy
[20:50] <knome> hrrhrr
[20:52] <knome> what are we drafting? the notes or the announcement or both?
[20:54] <ochosi> i guess both
[20:55] <ochosi> bluesabre started by listing app updates
[20:55] <ochosi> and elfy added a skeleton
[20:55] <ochosi> not sure what for though tbh :)
[20:55] <elfy> I'll not bother again then
[20:56] <knome> lol
[20:56] <knome> that skeleton is okay though :P
[20:57] <ochosi> elfy: why? i think it's nice, i'm just not experienced enough with this stuff :)
[20:58] <elfy> ochosi: well basically it's a whole lot easier doing it before by a day than by 5 minutes ...
[20:58] <ochosi> right, i guess so
[21:01] <ochosi> what the heck, bluebrain??
[21:01] <Luyin> puh, finally, test is nearly done
[21:01] <elfy> Luyin: \o/
[21:02] <brainwash> ochosi: that's me... surprise
[21:02] <knome> ochosi, watch your language, sir :P
[21:03]  * ochosi will remember to never say "bluebrain" again to an old lady
[21:03] <Luyin> ok, test passed. and I'm off to bed ;)
[21:03] <brainwash> Luyin: good night
[21:04] <elfy> Luyin: don't forget to report it ;)
[21:04] <elfy> and thanks :)
[21:05] <Luyin> elfy: done ;) good night to all of you!
[21:05] <elfy> night :)
[21:05] <Luyin> elfy: might do the next one tomorrow evening if I can make it
[21:07] <knome> night and thanks Luyin
[21:07] <elfy> Luyin: if we've had sufficient results by then we'll be marking it ready - so no testing, but dailies will start again until the next beta
[21:07] <Luyin> yw
[21:08] <Unit193> bluebrain?
[21:08] <elfy> we've done that :p
[21:09] <elfy> Unit193: I added that table link - and I removed the second command line install bit
[21:09] <elfy> the testcase is just the first
[21:09] <Unit193> OK, whatever works best for you.
[21:09] <Unit193> Sounds good though.
[21:11] <elfy> oooh - didn't know alt-tab is clickable ...
[21:12] <Unit193> Mhmm, nice shiny alt+tab from ochosi, been using it since slightly before trusty was released.
[21:12] <Unit193> (PPA I made, of course.)
[21:15] <knome> elfy, i'm waiting you to bombard the known issues section :P
[21:16] <elfy> I've not noticed very much to be honest - certainly not much in the way of Xubuntu specific stuff we need to make people aware off
[21:16] <elfy> which is the result of hardly any reporting of tests
[21:17] <knome> boo
[21:17] <ochosi> or a very stable beta ;)
[21:17] <Unit193> FWIW, I think more of us are activly using utopic than before.
[21:17] <knome> do we carry bugs from 14.04 release?
[21:17] <ochosi> +1
[21:17] <ochosi> and we've been trying to sort most pressing bugs in 14.04.1
[21:18] <ochosi> (and the indicators haven't changed their API [yet])
[21:18] <Unit193> Hah, no that waits until after FF.
[21:18] <brainwash> and wait until xorg 1.16 lands (FFe)
[21:19] <Unit193> elfy: At least this is earlier than I normally update, and I've moved 3 computers (netbook counts, right?) to utopic.  It's more of a daily/weekly use than a "report test complete" type of thing though.
[21:19] <elfy> there is 1 bug reported against xubuntu and utopic bug 1330171 that I can find
[21:19] <elfy> hardly worth noting ;)
[21:19] <ochosi> yeah, slideshow hasn't even been updated yet
[21:20] <elfy> Unit193: yea - cadence/exploratory testing - that's fine, if you happen to use something - check the package testcase
[21:20] <elfy> ochosi: yep
[21:23] <knome> elfy, taking on that bug.
[21:34] <elfy> right I've got to go - I'll catch up in the morning - night all
[21:34] <Unit193> G'night.
[21:35] <knome> night elfy, and thanks :)
[21:35] <ochosi> night elfy and thanks for your help!
[21:36] <elfy> ochosi knome - in the pad I linked to the minimal install draft on xubuntu.org - it's only a simple page - be good to publish that asap - I'll be calling for testing as soon as beta is released
[21:36] <elfy> anyway - night :)
[21:53] <Unit193> Logan_: Pingalinga?
[22:15] <knome> time to go to bed. nighty!
[22:22] <ochosi> night knome
[22:23] <Unit193> bluesabre: Why you no MOTU??  I need one! :P
[23:16] <bluesabre> Unit193: D:
[23:21] <ochosi> hey bluesabre
[23:21] <ochosi> might wanna give the release notes a read
[23:22] <bluesabre> looking over them now
[23:22] <bluesabre> er, was
[23:22] <bluesabre> now disconnected
[23:22]  * bluesabre searches for link
[23:22] <bluesabre> and I'm back
[23:22] <Unit193> bluesabre: So, what'd you decide on the xfpm-plugins/lxpanel stuff?  Going to mirror for the daily ppa, and also wondering how you resolved it. :D
[23:23] <Unit193> bluesabre: also, xfwm that contains brainwash's patch is in the normal place, if you want to look and decide if you like it.
[23:23] <bluesabre> Aren't we unable to resolve until lxpanel hits the archive?
[23:23] <Unit193> Sure, but still have to fix the hard dep on xfce4-panel.
[23:23] <bluesabre> oh right
[23:24] <Unit193> :D
[23:24] <bluesabre> aaaand, brainwash's patch..?
[23:27] <Unit193> From before, no maximize if no maximize.
[23:27] <Unit193> :D
[23:27] <bluesabre> oh right
[23:28] <bluesabre> ochosi: no known issues, yet?
[23:28] <ochosi> yup
[23:28] <bluesabre> and maybe add a note with the xchat removal "If you need to reach the Xubuntu team, go to xubuntu.org/irc"?
[23:28] <bluesabre> or smth
[23:29] <bluesabre> maybe not
[23:29] <bluesabre> :D
[23:29] <ochosi> well, or use pidgin ;)
[23:29] <ochosi> btw, apt-offline doesn't really seem to be such a terribly new version
[23:29] <Unit193> /kban ochosi no
[23:30] <ochosi> or maybe i misread, but it seemed like nothing spectacular was going on there
[23:30] <bluesabre> ochosi: well, the difference is that it actually works now
[23:30] <Unit193> ochosi: The point is, it works whereas trusty doesn't.
[23:30] <ochosi> oh
[23:30] <ochosi> list that in bug fixes then please
[23:30]  * bluesabre assigns to Unit193
[23:30] <ochosi> Unit193: http://pad.ubuntu.com/S030Pt7VHy
[23:30] <Unit193> Actually a bit busy, but sure later.
[23:30] <bluesabre> k
[23:30] <bluesabre> ochosi: how long are you around?
[23:31] <ochosi> not very much longer
[23:31] <ochosi> why, what's up?
[23:31] <bluesabre> stick around for a few, I can actually test xfpm now
[23:31] <ochosi> ah
[23:31] <ochosi> okeydokey
[23:33] <bluesabre> ok
[23:33] <bluesabre> unknown state is now a dead mouse
[23:33] <bluesabre> which is better
[23:34] <ochosi> dead mouse?
[23:34] <ochosi> you mean with an empty progressbar
[23:34] <bluesabre> yes
[23:34] <ochosi> ok
[23:34] <bluesabre> 1px red tick at the bottom
[23:34] <ochosi> yeah, that's the minimum load
[23:35] <ochosi> i didn't want it to ever be actually just empty
[23:35] <ochosi> otherwise ppl might wonder what that is
[23:35] <bluesabre> right, makes sense
[23:36] <bluesabre> awesome, we already have 5/5 on both arch
[23:36] <bluesabre> good job guys!
[23:37] <ochosi> http://dpaste.com/11E7FJJ
[23:37] <ochosi> apply that pls ^
[23:38] <ochosi> and if that works, i'll reward you with a blue (?) hovering on top of your mouse ;)
[23:44] <bluesabre> building now
[23:44] <bluesabre> prefix=/usr, right?
[23:45] <Unit193> Naaaah, /libexec/usr/
[23:45] <ochosi> yup
[23:45] <Unit193> :---D
[23:47] <bluesabre> ochosi: http://paste.ubuntu.com/8163876/
[23:47] <ochosi> argh
[23:47] <ochosi> typo
[23:47] <ochosi> UNKNOWN
[23:47] <ochosi> not UKNOWN
[23:47] <bluesabre> argh!
[23:50] <bluesabre> fixed typo, looks the same
[23:50] <ochosi> right, that's what i was afraid would happen :s
[23:50] <ochosi> somehow that check doesn't work
[23:50] <ochosi> and i don't get why
[23:52] <ochosi> since i can't debug, mind to add a debug message there and print the state?
[23:53] <ochosi> iirc 0 is UNKNOWN
[23:55] <bluesabre> ochosi: any idea where to see g_prints for panel plugins?
[23:55] <ochosi> yeah, you have to start the panel with debug mode
[23:55] <ochosi> one sec
[23:56] <ochosi> PANEL_DEBUG=1 xfce4-panel
[23:58] <bluesabre> ok, next question, what do you use for printing debug msgs?
[23:58] <bluesabre> g_print goes to the void
[23:58] <ochosi> g_warning usually