[00:01] <knome> elfy, once you get back, ping me about your plans about social mediaizing exploratory testing
[00:05] <Unit193> ali1234: New firefox should fix that, try upgrading?
[00:05] <ali1234> i am fully up to date
[00:05] <Unit193> 36.0.1+build2-0ubuntu0.14.04.1?
[00:05] <knome> Unit193, new firefox too? are they reverting to use the parameter anyway?
[00:05] <ali1234> yes
[00:06] <Unit193>     - revert removal of the deprecated -remote command line option, as some
[00:06] <Unit193>       older software (eg, Python 2.7's webbrowser module) still depends on it
[00:06] <Unit193>       (LP: #1425972)
[00:06] <knome> aha
[00:06] <knome> well that's the right way to go with that...
[00:06] <knome> :P
[00:21] <bluesabre> other than the packages I cannot upload, xfce-4.12 is in -proposed :)
[00:28] <Unit193> Stiiiilll reviewing stuff...
[01:35] <bluesabre> knome: do you want me to add your colorschemes to -artwork and x-d-s, any other changes expected there?
[01:40] <bluesabre> along with that, do we want to set mousepad's colorscheme by default? (might be safer to keep it white)
[01:41] <Unit193> Soo, what's this do?
[01:41] <bluesabre> Unit193: http://temp.knome.fi/temp/xubuntu/colorschemes/
[01:41] <Unit193> Oh right, xfce4-pulseaudio-plugin 0.2.1 pushed, looks like it needs more testing and bug reports.
[01:42] <bluesabre> nice to see that coming along so quickly
[01:42] <bluesabre> want to kick it into -extras (or wherever we currently have it)?
[01:43] <Unit193> Already have.
[01:45]  * bluesabre needs to pay more attention
[01:53] <bluesabre> knome: other question, how would you like these colorschemes licensed?
[02:11] <Unit193> bluesabre: http://git.xfce.org/apps/orage/tree/configure.in.in?id=orage-4.10.0#n265
[02:12] <bluesabre> Unit193: fun
[02:12] <Unit193> No, it means it doesn't need gui4, which is good.  New verve doesn't either. \o/
[02:13] <bluesabre> woot
[02:13] <Unit193> xfce4-linelight-plugin and xfce4-messenger-plugin nobody cares about (heck, couldn't even find a homepage for one of them..)
[02:13] <bluesabre> I think orage already doesn't depend on gui4
[02:13] <bluesabre> maybe I'm wrong
[02:13] <Unit193> xfce4-quicklauncher-plugin is a mess I believe.
[02:13] <bluesabre> yeah
[02:13] <Unit193> bluesabre: build-dep.
[02:14] <bluesabre> silly orage
[02:14] <bluesabre> notes is really the only important one
[02:15] <Unit193> Isn't that a mess too?
[02:15] <Unit193> http://git.xfce.org/panel-plugins/xfce4-notes-plugin/commit/configure.ac.in?id=d11fe51fae95b5b4963847be76ae4a07409a6076 wonder if that'd do it.
[02:16] <Unit193> http://git.xfce.org/panel-plugins/xfce4-notes-plugin/commit/?id=d11fe51fae95b5b4963847be76ae4a07409a6076 actually.
[02:18] <bluesabre> I'd say so
[02:19] <bluesabre> its ready for a release, except it doesn't build with latest vala
[02:19] <Unit193> So, "it's ready for release, just doesn't build"?  That doesn't sound ready. :D
[02:19] <bluesabre> ;)
[02:19] <Unit193> bluesabre: Does your gui4 package build with gcc5 then?
[02:20] <bluesabre> Unit193: haven't tried
[02:20] <bluesabre> is gcc5 landing in vivid?
[02:21] <Unit193> https://bugzilla.xfce.org/show_bug.cgi?id=10087 so this?
[02:21] <Unit193> bluesabre: No, but good to get things ready, as the mail said.
[02:21] <bluesabre> yeah
[02:22] <bluesabre> I'll give it a shot
[02:22] <Unit193> http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150202-gcc5-vivid.html#xubuntu
[02:22] <Unit193> https://lists.ubuntu.com/archives/ubuntu-devel/2015-March/038714.html explains.
[02:25] <bluesabre> ah, I see
[02:25] <bluesabre> missed that mail
[02:26] <bluesabre> I'm going to guess it probably wont fix that build failure
[02:26] <bluesabre> but maybe!
[02:26]  * bluesabre hopes
[02:33] <Unit193> Several of the plugins have the setenv error.
[02:34] <Unit193> See the other plugin releases?
[02:39] <bluesabre> not yet
[07:56] <ochosi> bluesabre: btw, ever found out what that missing transmission icon was?
[07:56] <ochosi> (just remembered now)
[08:43] <dkessel> ochosi: is the next meeting on wednesday evening CEST?
[08:45] <ochosi> dkessel: sorry, no, i still need to reschedule
[10:21] <knome> bluesabre, pick a license that works best for you
[10:21] <knome> bluesabre, i can live with either
[10:22] <knome> bluesabre, and i guess the schemes in -art, defaults in x-d-s (talk with ochosi)
[10:22] <ochosi> yup, +1 on that ^
[10:23] <knome> ooh ooh, docs upload
[10:23] <slickymasterWork> but not all the translated strings though
[10:39] <bluesabre> knome: thanks, https://bazaar.launchpad.net/~xubuntu-art/xubuntu-artwork/vivid/revision/282
[10:40] <bluesabre> ochosi: I think Laney said it should be fixed by the latest gtk upload, haven't checked yet
[10:40] <ochosi> ah ok
[10:40] <ochosi> great
[10:44] <bluesabre> knome, ochosi: xubuntu-dark as the default in terminal?
[10:44] <knome> yup
[10:44] <knome> practically the same as the current theme with some improvements
[10:58] <knome> bluesabre, what about the default mousepad conf?
[10:58] <bluesabre> knome: working on that now
[10:58] <knome> ok
[10:58] <bluesabre> do we want to have xubuntu-light as the default mousepad theme?
[10:58] <knome> yeah i guess
[10:59] <knome> it's easy enough to switch to the dark one
[10:59] <bluesabre> yeah
[11:04] <bluesabre> knome: for the default font
[11:04] <bluesabre> DejaVu Sans Mono Book
[11:05] <bluesabre> but thinking we should use font size 10 instead of 9 for the editor
[11:05] <knome> weeell ;)
[11:05] <knome> i use 8
[11:05] <knome> go figure
[11:06] <knome> i guess i'm fine with 10 even though it's a bit brutal
[11:06]  * bluesabre can't squint that hard
[11:06] <bluesabre> I'll get these settings in and you guys can tweak them throughout the day to find the perfect xubuntu defaults
[11:08] <bluesabre> knome: word-wrap on|off?
[11:09] <bluesabre> or just default?
[11:10] <knome> default
[11:10] <bluesabre> we can also choose to display toolbar, statusbar, anything like that
[11:10] <knome> as long as you set the default color scheme to xubuntu light, i'm fine
[11:13] <bluesabre> k
[11:13] <bluesabre> do you know which bug is the search both directions bug?
[11:13] <bluesabre> or, I can just look that up
[11:13] <knome> i had no idea we had one :D
[11:14] <knome> or i forgot..
[11:14] <bluesabre> found it
[11:22] <bluesabre> so yeah, if there are any other desired mousepad defaults, let me know, will have these pushed to bzr in a few
[11:25] <ochosi> bluesabre: yeah, it should be linked to the bugs-blueprint
[11:26] <bluesabre> https://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/revision/558
[11:27] <bluesabre> ochosi: Use dconf-editor and see if there are any other things you want to add to that ^
[11:27] <bluesabre> and elfy, Unit193, etc
[11:27] <ochosi> maybe "show full name in titlebar" would be useful
[11:28] <bluesabre> that's one I find handy
[11:28] <ochosi> k, let's put that one in then
[11:28] <bluesabre> will do
[11:28] <bluesabre> gotta go get ready for work now
[11:29] <ochosi> line numbers maybe
[11:29] <ochosi> and then that's it
[11:29] <ochosi> (if those aren't on by default anyway)
[11:29] <ochosi> cool, so we can mark another bug fixed then
[13:48] <Greylocks> Seeing a problem with xbuntu vivid, when I close the lid on my laptop and later reopen it I get the unlock screen fine but after authenticating all I get is a blank screen.  I then have to hard restart to get back into xbuntu. Anyone else seeing this? Is it a known issue?
[13:52] <GridCube> ._. its happening again?
[13:52] <GridCube> Bug 1303736
[13:54] <Greylocks> GridCube: looking at the bug now...
[13:55] <Greylocks> Only difference is that I have mine set to lock the screen, not suspend, but otherwise yes this is the issue I am seeing
[13:56] <Greylocks> I updated yesterday, perhaps if I update again I will get the fix? Or does it have to be installed manually?
[14:02] <elfy> that fix landed a long time ago - this issue keeps coming back, possibly another more recent not fixed bug, but there's so many different permutations of it I have lost my way with them
[14:04] <Greylocks> Updating now, if it still persists I'll add a comment to the bug.
[14:04] <Greylocks> Or should I open a new one?
[14:09] <elfy> Greylocks: I'm not sure tbh - I would edge towards report it - with as much specific information on what hardware it is
[14:10] <elfy> ochosi bluesabre - just so you know, image is still not getting to desktop after Try/Install dialogue 
[14:10] <elfy> bbl
[14:10] <Greylocks> elfy: okay, it will have to be this evening I have to leave for work soon so I'll do it tonight.
[14:41] <drc> The daily image for today actually working?
[15:34] <drc> Apparently not...64bit daily would not boot thru to LiveUSB desktop, same a syesterday.
[16:48] <elfy> drc: as you have found out for yourself - no it's not :p
[16:49] <ochosi> hey elfy 
[16:49] <elfy> hi ochosi :)
[16:49] <ochosi> is that since the systemd switch?
[16:50] <elfy> yep seemingly 
[16:50] <elfy> refuses to get to the desktop
[16:50] <ochosi> :/
[16:50] <ochosi> that
[16:50] <ochosi> 's not very cool
[16:50] <ochosi> is it reported already?
[16:50] <elfy> nope
[16:50] <elfy> nope
[16:50] <ochosi> and does it affect anyone else?
[16:50] <elfy> not as such re reported
[16:50] <drc> OTOH, upgrading appears to go smoothly? (this is a question, not a statement)
[16:50] <ochosi> k
[16:51] <ochosi> well i'm using vivid for a while now and the upgrade didn't break anything
[16:51] <elfy> ochosi: I checked 4 others yesterday not affecting them
[16:51] <ochosi> my laptop still boots
[16:51] <elfy> ochosi: yea same :)
[16:53] <elfy> should we expect to see xfwm showing in ps aux 
[16:57] <elfy> you can get to the installer at least 
[16:57] <ochosi> is that a question?
[16:57] <elfy> ochosi: if you've some idea what package to report against then I'll do that from cli 
[16:57] <ochosi> i mean yeah, xfwm4 should show up
[16:58] <ochosi> what happens exactly when you hit try&install?
[16:58] <elfy> mmm well ps aux | grep xfwm4 just reports the tty string
[16:58] <elfy> ochosi: currently the install option from try/install dialogue
[16:59] <ochosi> wait, i'm confused
[16:59] <elfy> ochosi: and it was more a rhetorical question 
[16:59] <ochosi> could you start from the top and describe the problem/bug?
[16:59] <elfy> ochosi: hang on - I'll summarise
[16:59] <ochosi> ty :)
[16:59] <elfy> ha ha 
[16:59] <elfy> boot image - at the first menu ignore it
[16:59] <elfy> get to our install/try dialogue
[17:00] <ochosi> so that is the one *before* ubiquity?
[17:00] <elfy> choose try - nothing appears, xfwm4 does NOT show up in ps aux
[17:00] <elfy> choose install - installer starts - install proceeds
[17:00] <elfy> exactly the same if you choose Try or Install from the first menu
[17:01] <ochosi> so the live session doesn
[17:01] <ochosi> t start?
[17:01] <elfy> ack
[17:01] <ochosi> humm
[17:01] <elfy> I am humming now - how long for? :p
[17:01] <ochosi> haha
[17:02] <elfy> you da boss :p
[17:02] <ochosi> maybe we should try with an image of another flavor first to see whether this is a more general problem
[17:02] <ochosi> (i really hope it is)
[17:02] <elfy> ochosi: I tried MAte, Lubuntu and Studio 
[17:03] <ochosi> oh, and?
[17:03] <ochosi> same same?
[17:03] <elfy> expected Studio to bellyflop but it didn't 
[17:03] <elfy> nope - unfortunately this is just us ... 
[17:03] <ochosi> meh
[17:03] <ochosi> what have we done wrong now?? :'(
[17:06] <ochosi> i presume you don't get any worthwhile debugging output?
[17:06] <elfy> ochosi: ok - so installing from the Install option - *appears* to work
[17:06] <ochosi> kinda weird that we're having the inverse problem of b1 now
[17:07] <elfy> however xfwm4 isn't reported in ps aux in tty1 there either
[17:07] <elfy> ochosi: yea :(
[17:07] <ochosi> well the question is: is the X11 session starting and is *anything* running
[17:07] <ochosi> have you looked into your /var/log/Xorg.0.log?
[17:08] <elfy> http://pastebin.ubuntu.com/10575615/
[17:11] <ochosi> weird, why is upstart still running there..?
[17:11] <elfy> mmm good point
[17:11] <ochosi> nothing xfce related is running
[17:11] <ochosi> so obviously something went rather wrong there
[17:11] <ochosi> lightdm seems okay
[17:12] <elfy> yep checked it's log - looks normal enough
[17:12] <elfy> systemd is running, analyze gives a figure
[17:15] <ochosi> does the Xorg.0.log say anything interesting at all?
[17:17] <elfy> failed to load module vboixvideo 
[17:22] <elfy> booting image with /sbin/upstart doesn't work either
[17:22] <elfy> brb - checking something here
[17:26] <elfy> and upstart doesn't boot *this* either
[17:26] <ochosi> humm
[17:26] <ochosi> not sure
[17:27] <ochosi> i guess i'll have to try myself
[17:27] <ochosi> tonight I'm already booked, I might try and take a look tomorrow
[17:27]  * ochosi still silently hopes things will just resolve by themselves
[17:27] <elfy> heh
[17:28] <elfy> well I'm just reinstalling upstart and letting that get upgraded rather than me doing it manually 
[17:28] <drc> They will...sooner or later we'll all be dead and no one will ever know we had this problem :)
[17:28] <elfy> then I'm off to annoy -quality
[17:28] <ochosi> thanks for the fatalistic contribution, drc :)
[17:29] <drc> no more so than your comment about "fixing itself".
[17:35] <elfy> ochosi: ok this machine's ok now in both
[17:35] <elfy> still not able to boot live with upstart 
[17:35] <elfy> I'll see what gives in -qa 
[17:35] <elfy> and check again tomorrow I guess
[17:36] <ochosi> thanks elfy 
[17:36] <ochosi> gotta run
[17:36] <elfy> yep - have a good one 
[17:36] <ochosi> u2!
[17:42] <elfy> bluesabre: has something been touched that could cause this ? ^^ http://irclogs.ubuntu.com/2015/03/10/%23xubuntu-devel.html#t16:59 and on for 30 minutes or so 
[17:47] <elfy> hi brainvvash :)
[18:21] <drc> OK...dl'd B1 iso, installed, attempted to update (thru gui.  Got "Failed to remove essential system package" error, and stopped.
[18:23] <drc> Interesting times indeed :)
[19:09] <krytarik> elfy: So, just tried ISO Live session with Xubuntu, Lubuntu, and Kubuntu. In Xubuntu, starting both Xubuntu and Xfce via LightDM fails, black screen; but startxfce4 works. Lubuntu works completely, as you said too; and installing xfce4 and starting it works there too. In Kubuntu, I just get a black screen with flicker fest here, and plasmashell crashes unrecoverably - might be related to my rather old setup though.
[19:09] <Unit193> krytarik: Still have it up?  I could check logs. :P
[19:10] <krytarik> I did, nothing in there.
[19:15] <krytarik> Umm, thinking about it, I didn't check LightDM's logs though. o\
[19:15] <Unit193> How about ~/.cache/upstart/ too? :P
[19:16] <krytarik> Nope, neither. :D
[19:17] <krytarik> I'm not rebooting into that again now though. :P
[19:23] <krytarik> Unit193: On another note, could you please check if my suggested changes to language names stuff of the docs work - particularly the Makefile?
[19:23] <elfy> krytarik: I'll grab kubuntu and have a look
[19:23] <elfy> thanks for checking that out 
[19:24] <krytarik> Sure.
[19:26] <elfy> kubuntu boots
[19:27] <Unit193> Sure, link again?
[19:28] <krytarik> Yep, sec.
[19:29] <krytarik> → http://paste.openstack.org/show/dVk8SfguxHghogSNHMKj/
[19:30] <krytarik> and:  http://paste.openstack.org/show/eJKIveD6iPKkplJVj0Xo/
[19:33] <elfy> and Gnome 
[19:33] <elfy> only one I've not been able to try it Ubuntu
[19:33] <elfy> only one that doesn't work is ours
[19:34] <krytarik> Meh, that surely sucks. :P
[19:35] <elfy> yep for sure
[19:37] <Unit193> krytarik: Only thing that I don't like, the name of the file. :P
[19:38] <krytarik> Yeah, you didn't respond to my question there. ;P
[19:39] <krytarik> But the location would be fine?
[19:39] <Unit193> It's too close to the other one, IMO, but yeah location makes sense.
[19:41] <krytarik> Well, I specifically adapted it to that one - how about LANGNAMES then?
[19:49] <Unit193> Ummm.
[19:49] <Unit193> Sooo.
[19:49] <krytarik> lol
[19:51] <Unit193> No, I found what the problem was very quickly, but it doesn't make sense.  Haven't found the why.
[19:53] <knome> he's back!
[19:53] <knome> i mean i am
[19:55] <elfy> he's back
[19:55] <elfy> I mean he is :p
[19:55] <knome> hehe
[19:57] <Unit193> elfy: Did you talk to someone about this?
[19:57] <elfy> not yet - other than balloons
[19:58] <elfy> not anyone infinity like 
[19:58] <Unit193> So what I quickly found after booting, initctl was missing, but upstart-bin was installed.  Something just removed /sbin/initctl.  I don't know what still, or why, sooo...
[20:10] <elfy> so ... ?
[20:10] <elfy> so leave it for the day ? 
[20:11] <elfy> should upstart-bin be removed? I've got that here 
[20:14] <Unit193> So, drop to a tty: sudo apt-get --reinstall install upstart-bin && sudo service lightdm restart
[20:16] <elfy> ok - so that would get the live session going
[20:17] <elfy> if you ignore Try and Install - it all appears to work, you can install - the end (in vm) gets graphic corruption after it says reboot
[20:17] <elfy> rebooting - blue wallpaper and nothing else 
[20:20] <elfy> have a look in 10 minutes 
[20:32] <elfy> ok - so that's cooking, I'll see what happens after it's installed
[20:32] <elfy> Unit193: so without being completely positive - would this be likely from something we've done or ... ?
[20:33] <elfy> wb drc 
[20:33] <drc> elfy: Did you see my post earlier about trying to updates a fresh B1 install?
[20:33] <drc> and thanks :)
[20:33] <knome> bluesabre, hullo!
[20:34] <elfy> drc: yea I did thanks, food interrupted proceedings then krytarik and Unit193 made me think about something else :p
[20:35] <drc> No rest for the Wicked :)
[20:35] <drc> Any one else confirm/deny the problem? (I have had problems that 1) were of my own making and 2) peculiar to my machine.)
[20:36] <elfy> seemingly not 
[20:36] <elfy> drc: I've got b1 downloaded - will check in a vm shortly 
[20:39] <Unit193> elfy: I don't see how, quite frankly.
[20:39] <elfy> Unit193: thanks - enough for me :)
[20:39] <elfy> I just want to see what occurs with this install - then I'll see if I can wake anyone up in -release
[20:43] <elfy> Unit193: ok so after reboot - have to --reinstall upstart-bin and restart lightdm again
[20:45] <Unit193> Mhmm, because you only installed it on the overlay.
[20:46] <elfy> yea 
[20:46] <elfy> anyway - noted in -release now
[20:46] <elfy> reboots properly second time 
[20:47] <elfy> drc: trying b1 now
[20:47] <elfy> but it is only a vm 
[20:47] <drc> ...baited breath....
[20:48] <elfy> Unit193: no idea even what to try and report this against 
[20:49] <elfy> knome: how's the slideshow going now? 
[20:49] <knome> elfy, i looked at the general artwork yesterday, most likely getting into the content today :
[20:49] <knome> )
[20:49] <elfy> :)
[20:50] <elfy> still not sure about the poll on the slide 
[20:50] <knome> you?
[20:50] <elfy> me 
[20:50] <knome> well
[20:50] <knome> what about this
[20:50] <knome> don't add it and consider introducing it for 15.10
[20:51] <knome> we would still have time to act before the LTS
[20:51] <elfy> well - the reason won't change even if we leave it till 200.10 
[20:51] <knome> lol
[20:51] <knome> then don't add it now or later :)
[20:51] <elfy> mmm
[20:52] <elfy> on the other hand I guess those that aren't new would be able to answer it :)
[20:52] <knome> yeahh...
[20:52] <elfy> so that would be more info than we have now ... 
[20:52] <knome> but how many of them look at the slideshow
[20:52] <knome> i installed xubuntu today and didn't look at it...
[20:52] <knome> okay okay, i'm an exception :P
[20:52] <elfy> and as you said - others caught by media'ing it 
[20:53] <elfy> well I only look when I'm specifically asked to once a cycle ... 
[20:53] <knome> hehe
[20:53] <knome> yeah
[20:53] <knome> did i already wonder it out loud
[20:53] <knome> "i wonder if we could add some js so people could vote directly from the slideshow"
[20:53] <elfy> Unit193: and that's why I hate asking questions in -release ... 
[20:54] <elfy> don't remember you wondering that aloud
[20:54] <elfy> Unit193: thanks :p
[20:55] <Unit193> elfy: Hah, nice.  And sre.
[20:55] <elfy> :)
[20:56] <knome> elfy, technically:
[20:56] <knome> 1) check if we can connect to xubuntu.org
[20:56] <knome> 2) if we can, add buttons
[20:56] <knome> 3) when buttons are clicked, send a get request to xubuntu.org
[20:56] <knome> 3b) on the server, catch the "request" eg. the vote
[20:56] <knome> 4) hide buttons
[20:57] <knome> so basically people without internet connection can't vote
[20:57] <elfy> and the chances of that this cycle ? 0 on a 0-1 scale? :)
[20:58] <knome> 0.001
[20:58] <elfy> ok :)
[20:58] <knome> the problem with that is that we'd need to make sure the server can take those requests
[20:58] <knome> in a meaningful way, that is
[20:58] <elfy> yea
[20:58] <knome> on the slideshow side, it doesn't need much
[20:58] <knome> we can even disregard 1/2
[20:59] <knome> then if you can't connect, then your vote just isn't sent
[20:59] <knome> on a content level, i'd probably keep that REALLY simple, like one or at max two question with at max 3 predefined answers
[20:59] <elfy> mmm
[21:02] <elfy> given all that I'd prefer to revert to plan a - link to it from slideshow, social mediaise it a few times during the cycle
[21:02] <knome> yeah...
[21:02] <knome> but you aren't sure about plan a either?
[21:04] <elfy> only in as much as would be catch people then - but advertisment is free
[21:04] <elfy> and I'm surer about plan a than plan b :D
[21:04] <knome> heh
[21:04] <knome> i'm not sure about plan a either
[21:04] <knome> so maybe we should take 6 months thinking time
[21:04] <knome> slickymaster, your opinion?
[21:06] <elfy> knome: given that we really only want to do this once for a while, don't want to go off half-cock with it
[21:07] <knome> yep
[21:12] <elfy> knome: also - we going to stop the current one soon? 
[21:13] <knome> probably so :)
[21:14] <elfy> got a response today :p
[21:14] <knome> heh
[21:14] <knome> how many total?
[21:14] <elfy> 357
[21:14] <elfy> 5 since the 1st March
[21:14] <knome> yeaaah, we should probably either close it or social media it once more
[21:14] <elfy> mmm
[21:15] <elfy> maybe do one more shout then close it in enough time for us to look at the data before we start 15.10
[21:15] <elfy> perhaps
[21:15] <knome> yep
[21:15] <knome> something like that
[21:16] <elfy> maybe shout nowish - close it beta week 
[21:21] <elfy> ochosi: just so you are aware - fix uploaded by infinity 
[21:22] <ochosi> elfy: sweet
[21:22] <ochosi> just as i had hoped!
[21:22] <ochosi> go infinity!
[21:24] <elfy> we've had plenty of interaction in that channel this cycle, being polite and friendly works wonders :)
[21:26] <ochosi> indeed
[21:29] <elfy> drc: dist-upgrading it now
[21:31]  * drc has turned blue from holding his breath from earlier :)
[21:31] <ochosi> poor drc 
[21:31] <elfy> bah
[21:31] <ochosi> what's on your mind?
[21:32]  * elfy forgot again ... 
[21:32] <elfy> drc: did you upgrade or dist-upgrade to sort out systemd? 
[21:33] <drc> I installed B1 then did a regular/normal initial update (thru the gui). So, no dist-upgrade
[21:34] <elfy> ok - doing cli dist-upgrade currently
[21:36] <elfy> drc: xorg crash mid upgrade atm only
[21:37] <drc> Equal opportunity failure :)
[21:39] <elfy> mmm so has it hung setting up libc6 or not ... 
[21:40] <knome> elfy, i had that yesterday or sth in vbox on regular package updates
[21:41] <knome> elfy, i killed the process, booted and ran dist-upgrade again - apparently finished nicely then
[21:41] <elfy> knome: drc had installed b1 earlier - and it crashed upgrading
[21:42] <knome> elfy, i can't remember what my installation media was, but probably pre-b1
[21:42] <knome> s/probably/likely/
[21:44] <elfy> nope - I managed to kill it completely :D
[21:44] <knome> heh
[21:44] <elfy> completing it via recovery mode
[21:45] <elfy> drc: I assume you tried that 
[21:46] <drc> Nope...When it wonked out (after 2 installs, multiple rebooting and upgrade attemps), I just stopped.
[21:46] <bluesabre> hey all
[21:47] <bluesabre> elfy: so infinity took care of the issue then?
[21:47] <drc> I had to kill nothing...I got the error message in a dialogue box...cliked OK and eveything update related died on it's own.
[21:48] <elfy> bluesabre: yep - panic averted again :)
[21:48] <bluesabre> woot
[21:48] <elfy> drc: maybe try that 
[21:48] <elfy> I'll check tomorrow as soon as I can obv
[21:48] <elfy> but ... 
[21:48] <drc> can't, I wiped everything and replaced what I had when I decided to install the B1.
[21:49] <elfy> drc yea, but rebooted before upgrading? in which case you'll be able to get grub and recovery? 
[21:50] <elfy> bluesabre: I just get a bit jittery when I've grabbed images from everyone and it's just us not working :)
[21:50] <ochosi> evening bluesabre 
[21:50] <bluesabre> elfy: understandably :)
[21:50] <bluesabre> hey ochosi
[21:50] <elfy> drc: there'd have been kernel upgrades as well in the mix 
[21:51] <ochosi> brb
[21:51] <drc> No, I installed, booted to the B1 on the hdd, tried updtaing when it stopped.  I then rebooted (which went fine) but all updating attempts resulted in the same problem.
[21:52] <elfy> knome: re exploratory then ... 
[21:52] <elfy> drc: oh - so quite broken then 
[21:53] <elfy> knome: I thought that it got media'd when I mailed list tbh 
[21:53] <drc> Well, no...everything that was there worked fine, just no updating.  I thought about cli, but decided to report it first...and then I need to actually use the computer so I replced what was there before B!
[21:53] <elfy> might be worth a poke on that though - package reports are moribund for sure 
[21:53] <elfy> drc aah ok :)
[21:54] <drc> And updating did not crash, it reported and exited quite gracefully :)
[21:54] <elfy> :)
[21:54] <knome> elfy, i was asking because the work item for that was marked "TODO"
[21:54] <drc> The channel log should have what the error message was (I don't really remember)
[21:54] <elfy> drc: did it actually say what it had problems with though? 
[21:55] <elfy> [18:21] <drc> OK...dl'd B1 iso, installed, attempted to update (thru gui.  Got "Failed to remove essential system package" error, and stopped.
[21:55] <drc> yup.  I had a choice of OK and something else that took me back to the general setting wndow.
[21:56] <elfy> knome: ok - so that could be DONE, unless I change the item to "do it a few times during cycle" then we could media it again and make it INPROGRESS :)
[21:56] <knome> elfy, i'd keep all the "ongoing" stuff outside the work items
[21:56] <knome> elfy, because they end up just looking like there's a lot to do
[21:57] <elfy> drc: yep - what I mean is - it didn't say it failed on package x 
[21:57] <drc> nope :(
[21:57] <elfy> knome: right - but then that means that the majority of items aren't going to be on blueprint - or shouldn't be
[21:57] <drc> I looked for something like that, but if it was anywhere, I couldn't find it.
[21:58] <knome> elfy, incorrect :)
[21:58] <elfy> task doesn't go from todo to done often :)
[21:58] <knome> elfy, heh, the point isn't to make it look like we've done a lot
[21:58] <elfy> drc: yea - maybe something that should be a bug - wishlist or ... 
[21:58] <knome> elfy, but if the item is something that is done the first time at the beginning of the cycle, and the last time at the end
[21:58] <elfy> knome: I realise that 
[21:58] <knome> elfy, there is no way to accurately track it, and it being either "TODO" or "INPROGRESS" is meh
[21:59] <elfy> but - that's all b/p's give you - for detail we should use trello ... 
[21:59] <elfy> :p
[21:59] <knome> heh
[21:59] <drc> elfy: Maybe, but it also maybe just me/my machine.  I did md5/checked the media and installed twice, same outcome all the way around.
[21:59] <knome> well i'm fine with any other than the one that i moved outside the work items ;)
[22:00] <elfy> anyway ... yes that was done - but maybe we should do more than once 
[22:00] <knome> elfy, well, two; being: Ongoing tasks:
[22:00] <knome> * Social media campaigns for QA milestones
[22:00] <knome> * Social media campaings for QA contest
[22:00] <knome> elfy, things like: [xubuntu-qa] QA articles for xubuntu.org: TODO
[22:00] <elfy> mmm
[22:01] <knome> elfy, are ok, but should be split to different items when/if we know what exactly is to be done
[22:01] <elfy> well that's not going to be happening this cycle for sure
[22:01] <knome> then postpone it :)
[22:09] <elfy> THERE - FIDDLED WITH B/P'S
[22:09] <elfy> sigh
[22:09] <elfy> I need to run through testcases to check they still agree after 4.12
[22:10] <elfy> then we can do another exploratory mail and media blitz
[22:12] <elfy> drc: so eventually I got to a desktop ... 
[22:12] <drc> with the daily?
[22:14] <elfy> no 
[22:14] <elfy> b1 and upgrading it 
[22:15] <elfy> daily I got to desktop and installed and booted in the end - good old Unit193 :)
[22:15] <Unit193> \o/
[22:16] <drc> what was the secret to the update?
[22:16] <elfy> dpkg from recovery menu drc 
[22:18] <drc> So, it still doesn't work as advertised, but there is a work around?
[22:18] <elfy> oh there's something wrong 
[22:19] <elfy> but I guess we need to iron out the systemd and other issues - I'll give it run when I know the live is good to see what happens then - but I'll do it on hardware 
[22:20] <elfy> I've had oddities where you get a crash report during similar - if you say cancel it just finishes, saying report seems to stop it all dead
[22:21] <drc> My problem is 1) with only 2gig RAM, a VM is right outl 2) I have only one box (the patop) and I detest dual booting so it's a "all or nothing" situation for me.
[22:21] <elfy> yep - totally understand 
[22:22] <elfy> last cycle with the ram and cpu I had I hated running vm's 
[22:22]  * drc has been trying for a while to get the Youngest Daughter to "loan" me one of her 9 computers, but.... :)
[22:22] <elfy> ... 
[22:22] <elfy> kids 
[22:23]  * Unit193 runs VMs on 2G...
[22:23] <drc> I actually know that dual booting is not near as hard as it used to be, but old memories last :)
[22:24] <drc> Unit193: A 2gig VM or VM on a 2gig machine?
[22:25] <elfy> drc: if you're using linux only then dual boot really just works imo
[22:25] <Unit193> drc: On a 2G machine.
[22:25] <elfy> the ONLY thing I do at cycle start is install grub to partition - so old one runs main grub
[22:25] <drc> elfy: I know, but....
[22:26]  * drc wonder what dual booting a LILO and a GRUB distro(s) would be like?
[22:27] <elfy> bouncy with maggots? 
[22:27] <drc> I was thinking more slimy with slugs.
[23:18] <knome> http://temp.knome.fi/temp/xubuntu/.1504w/xubuntu-vivid.png
[23:18] <knome> ^ since it's going to be uploaded soon anyway...
[23:20] <elfy> too blue man
[23:20] <bluesabre> phoronix | xubuntu wallpaper leaked, same as old wallpaper
[23:20] <elfy> nice one knome :D
[23:20] <elfy> bluesabre: lol
[23:21] <elfy> knome: time for a comment on that one?
[23:21] <Unit193> bluesabre: Nice one.
[23:24] <knome> elfy, as bluesabre how quickly he's pushing that :D
[23:25] <knome> *ask
[23:25] <knome> but sure, comments are always welcome
[23:25] <elfy> the leak?
[23:25] <knome> oh
[23:25] <knome> haha
[23:25] <knome> no comments
[23:25] <elfy>  knome change the angle slightly
[23:26] <knome> not taking that bait :)
[23:27] <bluesabre> uploading in a bit
[23:27] <elfy> knome: lol
[23:27] <bluesabre> but knome has until thursday to fix it
[23:27] <bluesabre> so pester him!
[23:27] <bluesabre> :D
[23:27] <elfy> bluesabre: really?
[23:27] <elfy> is that a task? 
[23:28] <bluesabre> :D
[23:28] <bluesabre> we should add that to the -artwork blueprint
[23:28] <bluesabre> "pick on knome until UIF"
[23:36] <bluesabre> knome: anything else for 15.04 artwork? https://bazaar.launchpad.net/~xubuntu-art/xubuntu-artwork/vivid/revision/283
[23:37] <knome> bluesabre, no, looks good to me
[23:37] <bluesabre> cool, I'll add the last changes for mousepad and push both -artwork and x-d-s then
[23:38] <elfy> bluesabre: change blue for greyshade?
[23:38] <elfy> :p
[23:38] <bluesabre> :D
[23:38] <bluesabre> I was thinking more pink or teal myself
[23:38] <knome> greysabre
[23:38] <elfy> bad bad elfy
[23:39] <elfy> bluesabre: cyan !!!
[23:39] <knome> -ide?
[23:39] <bluesabre> -ade
[23:39] <elfy> knome: nope 
[23:39] <elfy> too much i
[23:39] <knome> i thought that would have been cyan enough :(
[23:40] <Unit193> elfy: You may have mentioned another issue with the ISOs, anything I should take a look at?
[23:41] <elfy> Unit193: I think all part of the same parcel atm
[23:41] <elfy> possibly an upgrade issue if you pick the wring day
[23:42] <knome> wring?
[23:42] <elfy> ye
[23:42] <elfy> a
[23:42] <elfy> that's like the wrong day but much more specifi
[23:42] <elfy> c
[23:43] <Unit193> Speaking of which, I need to try a core upgrade, yey.
[23:43] <elfy> knome: like yesterday or tomorrow
[23:43] <elfy> Unit193: lets make yey  a nay
[23:43] <knome> heh
[23:44] <Unit193> \o/
[23:44] <elfy> given the hoohah
[23:44] <knome> end k c end a e?
[23:44] <elfy> knome: could be ,,,, Friday perhaps
[23:44] <knome> thet wey it's mukh aesiar to follow tha diskussion
[23:45] <elfy> Unit193: wait till live works?
[23:45] <knome> elfy, you want to bore him to death?
[23:45] <elfy> do an arch each again?
[23:45] <Unit193> Might be a good plan.
[23:45] <elfy> knome: do be brief ... 
[23:45] <Unit193> elfy: Oh, well you don't have to of course, I kind of did make the mess after all.
[23:46] <elfy> silly oldu nit 193 
[23:46] <elfy> knome: trying for Thursday
[23:47] <knome> what?
[23:47] <elfy> you asked 
[23:47] <knome> heh
[23:48] <elfy> :)