[00:00] <ochosi> bluesabre: we could actually mention the compton config in the release notes
[00:01] <bluesabre> ochosi: not sure this is getting executed, still no output there
[00:01] <ochosi> you're opening the menu though, right
[00:01] <ochosi> ?
[00:01] <bluesabre> ochosi: maybe, but then it'd seem like we're endorsing its use
[00:01] <bluesabre> yes
[00:01] <bluesabre> so, maybe not prefix=/usr
[00:01] <bluesabre> ?
[00:02] <ochosi> nah, that should work
[00:02] <ochosi> you can uninstall the xfpm from the repos to be sure thogh
[00:02] <ochosi> though
[00:05] <bluesabre> got it
[00:06] <bluesabre> I see state = 1 and state = 0
[00:07] <ochosi> what, both?
[00:07] <ochosi> i mean that'd explain it
[00:07] <ochosi> do you have >1 device?
[00:10] <bluesabre> laptop battery
[00:10] <bluesabre> ok, mouse is 0
[00:14] <ochosi> bluesabre: right, then i still don't get why it ends up with a progressbar
[00:15] <ochosi> (also, in case of the battery, it should return too)
[00:16] <bluesabre> probably does, I have the print above the returns
[00:17] <ochosi> should for both, question is why doesn't it
[00:17] <ochosi> do you see any obvious mistake or something?
[00:18] <bluesabre> one sec
[00:21] <bluesabre> ?
[00:21] <bluesabre> now it had no progressbar
[00:21] <ochosi> woot
[00:21] <ochosi> random?
[00:22] <bluesabre> not sure, investigating
[00:23] <Unit193> bluesabre: Didja update it for me?
[00:23] <bluesabre> ochosi: I guess the patch works now
[00:23] <bluesabre> :\
[00:23] <Unit193> And do uploads, and give me powers, and coffee?
[00:23] <ochosi> bluesabre: humm, you guess..? :s
[00:23] <bluesabre> yeah, its working
[00:24] <bluesabre> no idea why it didn't before, must be user-error
[00:24] <bluesabre> well
[00:24] <ochosi> ok, in that case try the real deal: http://git.xfce.org/users/ochosi/xfce4-power-manager/log/?h=private/unknown_device_state
[00:24] <bluesabre> working as in no progressbar
[00:24] <ochosi> yeah
[00:25] <bluesabre> Unit193: I'll get it uploaded tonight or tomorrow latest
[00:26] <Unit193> OK, sure, no hurry.
[00:26] <bluesabre> ochosi: warning: remote HEAD refers to nonexistent ref, unable to checkout.
[00:27] <bluesabre> I think I really dislike the user branches
[00:29] <ochosi> well you can add the user branch to the normal repo locally
[00:29] <ochosi> then you shouldn't get that error i think
[00:32] <bluesabre> there we go
[00:32] <ochosi> we do?
[00:32] <bluesabre> maybe
[00:32] <ochosi> ah
[00:33] <bluesabre> github is easier
[00:34] <bluesabre> got it finally
[00:34] <bluesabre> building
[00:34] <bluesabre> now the plugin dies on load
[00:34] <bluesabre> yay
[00:35] <Unit193> :D
[00:35] <bluesabre> (process:28041): xfce4-panel-wrapper-CRITICAL **: Wrapper power-manager-plugin-2: Failed to open plugin module "/usr/lib/xfce4/panel/plugins/libxfce4powermanager.so": /usr/lib/xfce4/panel/plugins/libxfce4powermanager.so: undefined symbol: layout_set_font.
[00:36] <ochosi> strange
[00:37] <ochosi> layout_set_font is a rather normal function
[00:38] <ochosi> not sure why that wouldn't work, we use it in the display dialog too
[00:38] <ochosi> feel free to comment it out though
[00:38] <bluesabre> beats me
[00:38] <ochosi> it worked for eric btw
[00:39] <bluesabre> probably just a messy build env
[00:39] <ochosi> he even showed me a screenshot of that blue bubble, so i know he wasn't faking it
[00:41] <ochosi> bluesabre: wanna try "pango_layout_set_font_description" instead?
[00:45] <bluesabre> ochosi: that fixed it
[00:45] <bluesabre> pango_layout_set_font_description (layout, pango_font_description_from_string ("Sans Bold 9"));
[00:45] <ochosi> hm, maybe layout_set_font is deprecated or something
[00:46] <bluesabre> maybe
[00:46] <ochosi> so wait, does it work now as it should?
[00:46] <bluesabre> things disappear quicker than we code
[00:46] <ochosi> indeed
[00:47] <ochosi> i mean do you see the blue bubble or does it just build and run?
[00:47] <bluesabre> ochosi: http://imgur.com/JzqXM0Q
[00:47] <ochosi> hm right. so apart from the ? not being centered anymore...
[00:47] <bluesabre> getting there
[00:47] <bluesabre> :)
[00:48] <bluesabre> need me to test anything else?
[00:48] <ochosi> nope, actually that's it
[00:49] <bluesabre> sweet
[00:50] <ochosi> i'll tweak the positioning of the ?
[00:50] <ochosi> so if you could test that once more
[00:50] <ochosi> that'd be great
[00:51] <bluesabre> sure thing
[00:51] <ochosi> http://dpaste.com/38WBPV9
[00:51] <ochosi> bluesabre: ^
[00:52] <ochosi> (you can obviously ignore that one line about the font)
[00:53] <bluesabre> ochosi: http://imgur.com/2Xw9NMa
[00:53] <bluesabre> bingo
[00:54] <ochosi> yup, that's pretty much it
[00:54] <ochosi> i'm a bit afraid of the installed fonts affecting the positioning
[00:54] <ochosi> mind testing one last thing?
[00:54] <bluesabre> sure
[00:54] <ochosi> setting your system font to something else and restarting the panel
[00:54] <ochosi> then check whether it's still centered
[00:55] <bluesabre> we can load it into fedora and watch it die with that font rendering
[00:55] <bluesabre> k
[00:55] <ochosi> (iirc "Sans" falls back to whatever)
[00:55] <ochosi> (or even gets overridden)
[00:55] <bluesabre> looks the same with ubuntu font
[00:56] <ochosi> mkay, i guess that's a good sign
[00:56] <bluesabre> indeed
[00:57] <Unit193> So right, what's on the pad?
[00:57] <bluesabre> lots of scribbles
[00:57] <bluesabre> http://pad.ubuntu.com/S030Pt7VHy
[00:58] <ochosi> bluesabre: i'll tweak the colors a bit more
[00:58] <ochosi> and then i guess i'll push it
[00:58] <ochosi> not sure why it didn't just work for eric
[00:58] <ochosi> (he also got the progressbar plus the bubble)
[00:59] <Unit193> I scribbled, it's not pretty.
[01:01] <bluesabre> Unit193: works for me
[01:01] <Unit193> Great.
[01:01] <bluesabre> so, I need to update power-manager depends and restore the xfwm patch?
[01:02] <ochosi> bluesabre: ok, last nag for tonight: http://dpaste.com/3JS241C
[01:04] <bluesabre> ochosi: nicer http://imgur.com/2GgYT8Y
[01:05] <ochosi> yup, i think for now i'm happy with it
[01:05] <Unit193> bluesabre: Something like that, but not quite no.
[01:06] <bluesabre> Recommends: xfce4-panel | lxpanel
[01:06] <bluesabre> or Depends
[01:06] <bluesabre> or just look at what you did
[01:06] <bluesabre> :D
[01:07] <Unit193> It's being added by misc:Depends or shlib:Depends, so not as simple.  xfwm I have done sitting in source/
[01:08] <bluesabre> oh right
[01:08] <bluesabre> no fun, that one.
[01:16] <ochosi> bluesabre: thanks again for testing, pushed to master
[01:16] <bluesabre> ochosi: great, thanks :)
[01:17] <Unit193> He broke it.
[01:19] <ochosi> who?
[01:24] <bluesabre> skellat
[01:24] <ochosi> night everyone
[01:24] <bluesabre> night ochosi
[01:24] <ochosi> aha
[01:24] <Unit193> ochosi: Sleepy well, if you can.
[05:45] <Unit193> ochosi: http://paste.openstack.org/show/9epDPTmSpE6L5z1VfHzG/ some basic stats, been around for a while.  A bit off since the one was just updated.
[05:50] <Unit193> We need to bump 1361459?
[06:20] <elfy> bluesabre: we had 5/5 on both after I finished - what I'm interested in is seeing more than 5 results in each of the arch's - otherwise I just as well mark the damn things ready once I've finished
[07:39] <ochosi> elfy: i'm dling the image now...
[07:39] <elfy> morning ochosi 
[07:40] <ochosi> morning
[07:40] <elfy> I just added a couple of bugs to known issues - video corruption in live session boot and an intermittent fail to configure wifi
[07:40] <elfy> and thanks
[07:40] <ochosi> ah good
[07:42] <elfy> did you look at the minimal install draft on xubuntu.org ? 
[07:46] <ochosi> not yet
[07:47] <elfy> ok - we'll either need to edit the release announcement to remove the link or publish that - I don't mind which we do :)
[07:47] <elfy> off to work later today and should be back mid afternoon in time to tie things up 
[07:48] <ochosi> ok, i'll try to take a look until then
[07:49] <elfy> yea - no real rush tbh, we just need to do one or the other 
[07:50] <ochosi> elfy: hm, that seems a bit ambiguous: After getting to the boot menu, select <em>Install</em> or for more customization select <em>Command-line install</em>
[07:50] <ochosi> especially because you don't explain both cases in the description
[07:51] <elfy> where are you reading that? 
[07:52] <ochosi> Unit193: over what timespan was the data collected? since we created the PPA?
[07:52] <elfy> ochosi: nvm - got it - testcase hasn't caught up with what we're wanting, but no-one should be testing that yet anyway 
[07:52] <ochosi> elfy: second list point in xubuntu minimal install
[07:53] <ochosi> also, it's a bit brief. the first paragraph should explain a bit more what's good about it, but that only experienced users might wanna do it
[07:53] <elfy> sorry - I'm reading the <em> thing as testcase - yea - please remove that bit so it just points at Install 
[07:54] <ochosi> so only "After getting to the boot menu, select <em>Install</em>" ?
[07:54] <elfy> yep
[07:55] <elfy> sigh 
[07:55] <ochosi> ok, also adjusted the following bullet-point
[07:55] <elfy> yea - was going to say the next will be wrong too :p
[07:55] <ochosi> the last one is also a bit confusing
[07:55] <ochosi> maybe it's just the wording
[07:56] <ochosi> "if you don't get that window, after installing, run.."
[07:56] <elfy> probably - I did just copy the wording from Unit193's core page
[07:56] <ochosi> meh
[07:56] <elfy> leave it for the moment 
[07:56] <ochosi> ok
[07:56] <elfy> I'll fiddle with the pad now 
[07:57] <ochosi> bluesabre: could you review this article pls and if you're ok with it just hit publish? http://xubuntu.org/?p=2656&preview=true
[07:58] <elfy> ochosi: I'll do some detail for testing minimal in m/l early next - we can deal with the website page later
[07:59] <ochosi> ok, sounds good to me!
[07:59] <elfy> yep - enough to do right now without an extra one :p
[08:00] <ochosi> :)
[08:08] <ochosi> elfy: doing a real install btw
[08:08] <ochosi> but i'll do a vm install for the testcase later i think
[08:09] <ochosi> brb (hopefully)
[08:09] <elfy> :)
[08:13] <elfy> ochosi: if you're doiing a real install that's preferable  for the test report - but if you manage to do a vm as well - that's even better
[08:14] <ochosi> hmm, somehow usb creator messed it up i thin
[08:14] <ochosi> k
[08:14] <ochosi> in the vm the image boots fine
[08:14] <knome> that's wonky. i've never truly trusted it..
[08:14] <ochosi> on the usb stick i get "not a COM32R image" or something
[08:14] <elfy> aah
[08:15] <elfy> tab 
[08:15] <ochosi> guess there's no easy way of validating that the usb creator didn't mess things up other than trying to boot from the stick
[08:15] <ochosi> tab?
[08:15] <elfy> yea tab button - try then typing live
[08:15] <elfy> in unetbootin you'd want unetbootindefault
[08:15] <elfy> I've had that off and on
[08:16] <ochosi> ok, i'll try that after the first VM run
[08:17] <elfy> I'd report it - but more than I'd like anything that's just a general *buntu issue gets ignored so I don't bother anymore
[08:17] <ochosi> right
[08:18] <elfy> bug 1325801
[08:18] <ubottu> bug 1325801 in casper (Ubuntu) "failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:" [Critical,Triaged] https://launchpad.net/bugs/1325801
[08:19] <ochosi> ah, thanks
[08:19] <elfy> added to my results and the pad
[08:23] <ochosi> frankly, i'm myself a bit surprised by how much goodness and features b1 contains
[08:23] <ochosi> most comes from upstream, but since bluesabre and i are quite active there, it's also a xubuntu achievement
[08:23] <elfy> :)
[08:26] <ochosi> best thing about QA, you can actually do something else while pretending to do something ("It's installing...")
[08:26] <ochosi> aka http://xkcd.com/303/
[08:27] <elfy> indeed :)
[08:27] <elfy> no sticker for you :p
[08:27] <ochosi> awwwh :D
[08:27]  * ochosi remembers not to call the QA lead the king of slackers anymore
[08:28] <elfy> :|
[08:28] <elfy> lol
[08:28] <ochosi> well, i want them stickers!!!
[08:28] <ochosi> ;)
[08:29] <elfy> sent a note to list re com32 and possible graphic corruption just in case anyone else comes across them and doesn't look at the tracker first
[08:30] <ochosi> elfy: hm, for auto-resize i need to have a second system installed in my vbox, right?
[08:30] <elfy> yea 
[08:30] <ochosi> humm
[08:30] <ochosi> ok, that'll be the last one then
[08:31] <elfy> no
[08:31] <elfy> actually - what you need is a vm disk big enough to allow 2 installs
[08:31] <elfy> I make them 16Gb
[08:31] <elfy> then can do whole disk, resize and then manual on one of the resized 
[08:32] <ochosi> ah, hmm
[08:32] <ochosi> too late for that
[08:32] <elfy> can't do whole disk on hardware here - would kill little one's win7 install lol 
[08:33] <ochosi> :)
[08:33] <ochosi> btw, anything i should add to the comments?
[08:33] <ochosi> i see you added "hardware"
[08:34] <ochosi> is that a hardware profile you created for yourself?
[08:35] <elfy> I don't use hardware profiles 
[08:35] <elfy> I just try to differentiate between hardware and vm's is all
[08:36] <ochosi> ah ok
[08:36] <ochosi> so i guess i put VM in the comments then
[08:37] <knome> well, what are hardware profiles anyway.. websites.
[08:38] <elfy> knome: https://wiki.ubuntu.com/QATeam/Hardware
[08:38] <knome> i know
[08:38] <elfy> if balloons doesn't bother with that - that's good enough for me :p
[08:38] <knome> they are a website with specified output from a command
[08:39] <elfy> I guess - all seems rather pointless to me 
[08:39] <knome> well if you could save your HW profiles *in the ISO tracker*, then select one from a dropdown, it would be much useful..
[08:39] <knome> *more*
[08:40] <elfy> I'd rather see other things fixed on the tracker than that ;)
[08:40] <knome> currently it's... well, i guess there can be some good to it
[08:40] <knome> me too.
[08:40] <elfy> well - off to work for me - back mid afternoon I hope
[08:40] <elfy> cya later
[08:41] <knome> the arguments against some of the HW info gathering have been "who owns it, which server has the information", and now we've set up a community system that powers a somewhat closed community member server...
[08:42] <knome> wait, we're using something else now. hooray.
[08:42] <knome> but still it's not centralized..
[08:50] <ochosi> frankly, 14.10 is looking great
[08:52] <Unit193> Me?  Bad wording?  Surprising!
[08:52] <Unit193> :P
[08:59] <ochosi> bluesabre: i get a funny crash of xfsettingsd in the live session when enabling the 'configure new displays when connected' option btw
[08:59] <ochosi> bluesabre: http://dpaste.com/3XWVF5X
[09:00] <ochosi> i'll see whether that still applies in on a hw install
[10:05] <Unit193> http://paste.openstack.org/show/EAo9SpSNXeScCSlpbfja/ might even get fr this cycle.
[10:09] <ochosi> get fr?
[10:09] <knome> french translation of the documentation
[10:10] <ochosi> right, but is there an increase or why might we get it this cycle?
[10:10] <knome> increase obviously
[10:10] <ochosi> Luyin: i see that the docs are fairly untranslated in german, in case you feel like taking a look ;)
[10:11] <knome> same goes for silverlion @ -ot
[10:11] <Luyin> ochosi: link?
[10:11] <ochosi> knome: link?
[10:11] <ochosi> (mmm, aligning lines...)
[10:12] <knome> https://translations.launchpad.net/xubuntu-docs
[10:12] <Unit193> I can translate to gibberish.
[10:12] <ochosi> sweet!
[10:13] <ochosi> wait, where's the gib.po ?
[10:13] <knome> Unit193, any (other) readers for that one? :P
[10:13] <Unit193> Well, maybe, but not that use Xubuntu. :P
[10:14] <knome> uh, i'm out of battery. see you!
[10:14] <ochosi> ttyl knome 
[10:18] <Luyin> ochosi: I'll take a look at it tonight. at work atm ;)
[10:18] <ochosi> Luyin: sure, thanks! hf @work then ;)
[10:19] <knome> hm, who doesn't work on FOSS while at work? :P
[10:20] <Unit193> I'd bet money elfy doesn't.
[10:22] <knome> does advoacy count?
[10:22] <knome> advocacy too
[10:55] <bluesabre> ochosi: re, that article, the title could use some work, but otherwise I think it is good
[10:56] <bluesabre> elfy: got a few tests in this morning
[10:56] <ochosi> bluesabre: got any ideas up your sleeve?
[10:56] <bluesabre> schedule is tight this morning, so everything else that I promised I'd do this morning, I'll do tonight
[10:57] <bluesabre> "Laptop users, the black screen of death is fixed"?
[10:57] <bluesabre> dunno
[10:57] <Unit193> Sure, no problem.
[10:57] <ochosi> oh, let's not call it that, that might catch on
[10:57] <bluesabre> "
[10:57] <bluesabre> The nasty black screen bug is fixed in 14.04.1" doesn't jive with me
[10:57] <ochosi> i like the exclamating "laptop users"
[10:57] <bluesabre> :)
[10:58] <ochosi> problem is, some people are still experiencing some sort of black screen
[10:58] <bluesabre> I know
[10:58] <ochosi> maybe we should write
[10:58] <bluesabre> at various points
[10:58] <ochosi> "Laptop users, we have fixed one black screen bug"
[10:58] <ochosi> :]
[10:58] <bluesabre> haha
[10:59] <ochosi> more humble
[11:00] <bluesabre> "Laptop users, Fix available for the black screen on unlock bug"
[11:00] <ochosi> yeah, that's better
[11:00] <ochosi> wanna hit publish then?
[11:00] <bluesabre> sure
[11:00] <ochosi> ty
[11:01] <bluesabre> for the article content, "and Xubuntu 14.10 Beta 1"
[11:02] <ochosi> yup
[11:02] <ochosi> true
[11:02] <ochosi> when i drafted that, 14.10 was still too far away
[11:03] <bluesabre> I can't publish, "submitted for review"
[11:03] <ochosi> oh
[11:03] <ochosi> i guess i'll do that then
[11:04] <ochosi> not a member of xubuntu-website?
[11:04] <bluesabre> dunno
[11:04] <bluesabre> I think I am, able to login
[11:04] <bluesabre> ochosi: add the 14.04 and 14.10 tags, maybe?
[11:04] <ochosi> maybe just xubuntu-team is needed for that
[11:05] <ochosi> never sure
[11:05] <bluesabre> ah
[11:06] <Unit193> -team can't publish.
[11:06] <bluesabre> anyway, gotta run, bbl
[11:06] <ochosi> ok, ttyl bluesabre 
[11:06] <ochosi> thanks!
[12:27] <elfy> back
[12:27] <elfy> lol @ Unit193 
[12:28] <elfy> you'd be right :p
[12:40] <elfy> ochosi: announcement is now fleshed out - not done release note though yet
[12:40] <elfy> I'm happy to mark the beta as ready when you are
[12:55] <ochosi> elfy: i managed to run two tests today, but that's about it i'm afraid
[12:56] <ochosi> one hardware, one VM
[12:56] <elfy> thanks for doing them :)
[12:57] <elfy> we can wait a while longer - then mark them - you can do that if you want :)
[12:58] <ochosi> nah, i think it's actually fine to mark them now
[12:58] <elfy> ok - you want to do that - it'll make sure that you can do it
[12:59] <ochosi> righty
[12:59] <ochosi> note that i've never done that before, so i'd actually be greatful for you to guide me a little :)
[13:00] <elfy> ok - http://iso.qa.ubuntu.com/qatracker/milestones/322/builds
[13:00] <elfy> empty box to the left of where it says Product(Xubuntu)
[13:00] <elfy> click that - should select both our 32/64 bit
[13:01] <elfy> then in the Admin bit - Status - in the dropdown - select mark as ready
[13:01] <ochosi> yup (actually all of the products are autoselected by default for me, so it's more about unticking than ticking)
[13:01] <elfy> then update build status
[13:02] <ochosi> ok, did that
[13:02] <elfy> mmm 
[13:02] <ochosi> not sure anything happened though
[13:02] <ochosi> at least there is no visual diff
[13:03] <elfy> ochosi: hang on - http://www.zimagez.com/zimage/screenshot-280814-140252.php
[13:04] <elfy> not the products right on the left - with kubuntu etc
[13:06] <ochosi> thanks
[13:06] <ochosi> done now
[13:06] <elfy> awesome - picture paints a thousand words :p
[13:06] <ochosi> indeed
[13:06] <elfy> now - no-one can report against it 
[13:06] <ochosi> you mean iso tests?
[13:07] <elfy> or shouldn't be able to - yep 
[13:07] <ochosi> aha, why's that?
[13:07] <elfy> because we've said it's ready 
[13:07] <elfy> tomorrow it'll go back to dailies
[13:10] <elfy> https://wiki.ubuntu.com/UtopicUnicorn/Beta1/Xubuntu
[13:27] <ochosi> elfy: ok, so how do we go about creating the announcement / notes now?
[13:28] <elfy> the announcement is fleshed out on xubuntu.org - needs another set of eyes
[13:28] <elfy> the release note page is ^^ and just needs to have the pad content copied to it and fiddled with
[13:29] <elfy> we just need to wait now for stgraber - apart from checking things nothing we can really do for the moment
[13:29] <ochosi> the launchpad bugs on the announcement need links btw
[13:29] <elfy> ok - I'll do those now
[13:30] <ochosi> thanks
[13:36] <elfy> ok - that's done
[13:39] <ochosi> thanks
[13:39] <ochosi> looks much better now
[13:39] <ochosi> btw, please s/Xchat/XChat/
[13:39] <ochosi> (if you still have the edit lock)
[13:39] <elfy> I did - it says XChat 
[13:39] <ochosi> ah, good
[13:40] <elfy> or should do :p
[13:40] <ochosi> among "other changes" it's still Xchat
[13:40] <elfy> hadn't saved 
[13:44] <elfy> can't get the frist two paragraphs to look right
[13:45] <ochosi> yeah, they do look a little messed up
[13:45] <ochosi> you're using the visual editor?
[13:45] <elfy> I was
[13:45] <ochosi> (there's so many diffs there, i feel dizzy...)
[13:45] <ochosi> err, divs :)
[13:46] <elfy> lol
[13:46] <elfy> anyway - I'll not play with that page anymore
[13:47] <ochosi> suuuure, break everything and then sneak out!
[13:47] <ochosi> :D
[13:47]  * ochosi goes and cleans up
[13:47] <elfy> :)
[13:47] <elfy> common infrastructure on the wiki appears to be pointless this time
[13:52] <ochosi> ok, done
[13:53] <ochosi> so from my pov the release announcement is ready to go
[13:53] <elfy> thanks - looks better :p
[13:53] <ochosi> good
[13:53] <elfy> yep - that all looks fine to me too
[13:53] <elfy> once we get the nod we can publish that and do the wiki one
[13:53] <ochosi> are you working on the notes arleady?
[13:53] <elfy> easy now :)
[13:54] <ochosi> ah ok
[13:54] <ochosi> so we'll wait and then copy over the stuff from the pad when greenlit
[13:54] <elfy> yep :)
[13:54] <ochosi> good
[13:55] <elfy> I'm about now all day apart from food so will keep an eye on -release
[13:55] <ochosi> great, can't promise yet i'll be around when it's time
[13:55] <ochosi> so thanks for that!
[13:55] <elfy> yep - that's fine - I'm guessing sort of 1700UTC ish from what he said he other day
[15:36] <elfy> release notice is up now - if anyone wants to check it https://wiki.ubuntu.com/UtopicUnicorn/Beta1/Xubuntu
[15:36] <elfy> will publish the announcement in a few hours
[15:49] <ochosi> looks good, maybe wanna put the known issues in a list too?
[15:50] <elfy> I knew that ... 
[15:50] <elfy> :p
[15:55] <slickymasterWork> ochosi: maybe now we could publish the inxi article in the blog ^^
[15:55] <slickymasterWork> could/should
[15:57] <elfy> makes sense to me
[15:59] <ochosi> slickymasterWork: yup, sounds good!
[15:59] <slickymasterWork> you're the boss ochosi ;)
[16:00] <elfy> got page open - will publish it then
[16:01] <ochosi> ty elfy 
[16:01] <ochosi> quite the activity on our blog today
[16:01] <slickymasterWork> elfy = always helpful
[16:04] <ochosi> you mean elfy = alwaYs hELpFul
[16:05] <elfy> linked to the inxi page in the beta announcement
[16:05] <elfy> ochosi: lol
[16:05] <slickymasterWork> lol, good one ochosi :)
[16:07] <slickymasterWork> elfy: I'm getting a PAGE NOT FOUND in the beta announcement
[16:07] <elfy> ochosi: we going to put beta on the front page
[16:08] <elfy> slickymasterWork: it's not all live yet
[16:08] <ochosi> yup, should
[16:08] <slickymasterWork> oh, ok
[16:08] <slickymasterWork> thought you guys already have published it
[16:09] <elfy> no - we've not published announcement, the download link's not real yet either
[18:32] <elfy> releasing at 20:30UTC ish it seems
[20:39] <brainwash> you can use menulibre to edit the entries which are displayed in the settings manager, right?
[20:40] <elfy> brainwash: yep
[20:40] <brainwash> we got a dissatisfied customer here bug 1362734
[20:40] <ubottu> bug 1362734 in xfce4-settings (Ubuntu) "settings manager contains entries (icons) that are obsolete and cannot be fixed or removed" [Undecided,New] https://launchpad.net/bugs/1362734
[20:40] <brainwash> he also mentions the missing gksu
[20:41] <elfy> only got one nvidia-settings here, pretty sure was the same in trusty
[20:42] <brainwash> shouldn't there be too? one for tasks which require root privileges?
[20:43] <Unit193> Nah.
[20:43] <elfy> nvidia-settings calls for root rights if you ask it to amend xorg.conf
[20:44] <elfy> I've only ever seen one nvidia-settings 
[20:44] <brainwash> strange, how did he end up with two launchers? =S
[20:44] <Unit193> Playing with launchers too much?
[20:45] <brainwash> but he does not seem to have a clue at all
[20:47] <elfy> delete the useless one
[20:49] <brainwash> yea, I'll tell him about menulibre and then close the report (or tell him to reassign it do the nvidia driver package which installs the launchers in the first place)
[20:49] <brainwash> to the nvidia driver package
[20:49] <elfy> yep
[20:53] <elfy> Unit193: did you see ochosi's comments re minimal draft page earlier? "also, it's a bit brief. the first paragraph should explain a bit more what's good about it, but that only experienced users might wanna do it"
[20:55] <Unit193> Mhmm.
[21:17] <elfy> released now
[21:18] <elfy> ochosi: not done the front page of xubuntu.org though
[21:18] <elfy> night all
[21:18] <Unit193> Also, should be ready to test core when I need to.
[21:18] <Unit193> G'night.
[21:19] <elfy> Unit193: I'll sort a call out for next week for that - then we can Done that trello card and blueprint
[21:33] <ochosi> (late) evening everyone
[21:34] <ochosi> bluesabre: btw, the xfpm plugin (in git master anyway) now has the minimum brightness level for scrolling over it as well
[21:34] <ochosi> so you can't accidentally shut off your display anymore ;)
[21:41] <ochosi> lderan: had to postpone your workitem for utopic btw since we're already past freeze
[21:42] <lderan> okay, sorry for not getting it complete in time
[21:43] <ochosi> sure no worries
[21:43] <ochosi> it happens
[21:43] <ochosi> would be good to keep us (i.e. either bluesabre or me) in the loop about these things
[21:45] <lderan> aye will do so in the future
[21:46] <ochosi> thanks!
[21:46] <ochosi> did you produce anything testable though or just didn't have time to work on it at all?
[21:46] <ochosi> (just curious cause i'd really love to have that around next cycle)
[21:48] <lderan> nothing yet :(
[21:48] <ochosi> ah ok :)
[21:48] <ochosi> just wanted to avoid duplicate efforts, in case anyone else decides to hack on it
[21:50] <lderan> will hopefully make some progress soon :)
[21:52] <ochosi> cool, that'd be nice
[21:52] <ochosi> should be easier than with light-locker-settings even, less UI :)
[21:52] <lderan> \o/
[21:53] <ochosi> (and the underlying app is python, so should all integrate nicely)
[21:54] <lderan> huzzah for python :P
=== brainwash_ is now known as brainwash
[22:41] <brainwash> bluesabre: please take a look at bug 1313539
[22:41] <ubottu> bug 1313539 in xfce4-settings (Ubuntu) "monitor shows black screen and "no input signal" after turning the monitor off and on manually" [Undecided,Confirmed] https://launchpad.net/bugs/1313539
[22:41] <brainwash> "There is a regression bug between xfce4-settings 4.11.0-1ubuntu1 (saucy) and 4.11.2-1ubuntu2 (trusty)."
[22:41] <brainwash> display/monitor related
[22:41] <bluesabre> gah
[22:42] <bluesabre> we didn't change how the monitor turns on or off, just added an apply button
[22:42] <bluesabre> actually
[22:42] <bluesabre> we didn't change how monitors turn on or off, apply does not apply for that
[22:42] <brainwash> but still.. the saucy package seems to work fine for these guys
[22:43] <bluesabre> I'll take a look
[22:43] <brainwash> thank you :)
[22:43] <bluesabre> ok
[22:44] <bluesabre> so, the only other difference is two ubuntu versions
[22:44] <bluesabre> and Xorg, graphics drivers
[22:44] <bluesabre> lots of things at play here
[22:44] <bluesabre> oh right
[22:44] <bluesabre> later comments
[22:44] <brainwash> yeye
[22:44] <ochosi> why doesn't ubottu post a buglink anymore
[22:45] <ochosi> just a description
[22:45] <ochosi> bug #1313539
[22:45] <ubottu> bug 1313539 in xfce4-settings (Ubuntu) "monitor shows black screen and "no input signal" after turning the monitor off and on manually" [Undecided,Confirmed] https://launchpad.net/bugs/1313539
[22:45] <brainwash> he did
[22:45] <ochosi> awh crap, my terminal had partially moved offscreen :>
[22:45] <lderan> :P
[22:46] <Unit193> !gender
[22:46] <ubottu> yes, I can confirm I am a female bot :)
[22:46] <bluesabre> "This issue does not occurs on another computer (with nVidia gfx card+Dell U2713HM+DVI cable)"
[22:47] <bluesabre> this sounds painful to debug
[22:47] <ochosi> seems a bit random
[22:47] <ochosi> not even sure how to reproduce that
[22:48] <ochosi> luckily the easy workaround is not to turn the monitor off manually :>
[22:49] <ochosi> maybe a bug with displayport?
[22:49] <ochosi> i mean xorg + displayport
[22:49] <brainwash> mmh, but saucy package installed in trusty works fine
[22:49] <ochosi> cause the other computer he mentions uses dvi
[22:49] <brainwash> according to the comments
[22:50] <ochosi> yeah, but from the scarce information we have, this seems to be the most promising lead
[22:50] <ochosi> i for one haven't used a computer with displayport, so i guess that could be a reason why i've never seen it :>
[22:50] <bluesabre> hardware bugs are the worse, since we can't just go and reproduce
[22:50] <brainwash> :/
[22:51] <bluesabre> *worst
[22:51] <brainwash> at least we got some hints now
[22:51] <ochosi> also, note that the guy who said that 4.11.3 doesn't work for him isn't the OP
[22:51] <brainwash> right
[22:51] <bluesabre> good point
[22:52] <brainwash> but he should be also affected by this bug I'd guess
[22:52] <ochosi> well, if you could've learned anything from the black screen bug report it's that sometimes users comment on a bug because they *think* it's the same bug
[22:54] <ochosi> btw, it could be that the "new display"-listener causes that issue
[22:55] <ochosi> the one that pops up the minimal dialog
[22:56] <brainwash> asking them to run xfsettingsd in debug mode could help us
[22:57] <bluesabre> yeah
[22:57] <bluesabre> also, proposing this:
[22:57] <bluesabre> @palomino @knnniggett
[22:57] <meetingology> bluesabre: Error: "palomino" is not a valid command.
[22:57] <bluesabre> Hardware bugs are particularly difficult to diagnose since there is such a wide gamut of combinations.  Can you try loading the xubuntu 14.10 beta1 live cd (no need to install) and see if this issue persists?  xfce4-settings is built using the other xfce libraries, so you want to make sure you have the latest combinations... which the current beta provides.
[22:57] <bluesabre> If the issue does persist, can you also try switching monitors and testing again on both?  If we can narrow down the hardware combination, that might help us find a lead.
[22:57] <bluesabre> thanks meetingology!
[22:57] <ochosi> btw, the mythbuntu bugreport is really loooong
[22:58] <ochosi> i wonder why they never brought this to our attention
[22:58] <ochosi> https://bugs.launchpad.net/mythbuntu/+bug/1308105
[22:58] <ubottu> Launchpad bug 1308105 in xfce4-settings "Xfce resets TV mode to NULL when power cycled" [Medium,Confirmed]
[22:58] <bluesabre> yeah
[22:58] <brainwash> oh... I've ignored that report all the time
[22:59] <brainwash> quite a few comments there
[22:59] <bluesabre> and while not optimal, it would be nice if they could test with not-xfce as well
[22:59] <bluesabre> oh wait, older xfce4-settings is not an issue, so nvm that
[23:00] <brainwash> so 1313539 is yet another dupe
[23:00] <ochosi> yeah, also on that other report, they say they tested with gnome-shell
[23:01] <ochosi> seems that this is the upstream report: https://bugzilla.xfce.org/show_bug.cgi?id=11107
[23:01] <ubottu> bugzilla.xfce.org bug 11107 in Xfsettingsd "xfsettingsd resets TV mode to NULL on power cycle" [Normal,New]
[23:01] <ochosi> (extremely recent btw)
[23:01] <ochosi> so yeah, the code that lionel added for reactivating the internal laptop display seems to be the cause of some of this headache
[23:02] <ochosi> at least that's my superficial diagnosis
[23:02] <ochosi> although it should (note: should) only get that RandR signal of not having an active monitor connected only when unplugging the cable
[23:02] <bluesabre> good news is, this is not because of the latest 4.11.3
[23:03] <ochosi> but unfortunately these hardware things work differently it seems
[23:03] <bluesabre> :)
[23:03] <ochosi> yeah
[23:03] <ochosi> so while it fixes a very annoying problem, there seems to be a regression around in it
[23:03] <ochosi> although since it was a new feature at the time, it's not technically a regression
[23:03] <brainwash> so, we can mark the report as duplicate of the mythbuntu one?
[23:04] <ochosi> brainwash: not sure yet, i haven't tested or investigated anything, i'm just thinking out loud
[23:04] <ochosi> bluesabre: the upstream bugreport also has the debug output btw
[23:04] <bluesabre> yeah
[23:05] <brainwash> wow, so this issue isn't that small after all
[23:05] <ochosi> well, it only happens in a very specific scenario
[23:05] <ochosi> and only with hardware that sends a specific RandR signal when it shouldn't
[23:05] <ochosi> (or at least when we'd not expect it to)
[23:06] <ochosi> anyway, time to go to sleep
[23:06] <ochosi> night everyone
[23:06] <bluesabre> night ochosi
[23:07] <brainwash> good night