[01:14] <bluesabre> knome: got an email request for a wallpaper-sized monkey artwork from http://xubuntu.org/news/15-04-release/
[02:16] <OvenWerks> Unit193: I am very happy with Xubuntu-core. I am thinking Studio could very easily be based on it directly. The default theme and look/feel just work. Our menu stub just works too. I should probably take a look at the xubuntu release as well and see if we would need to take anything out at all. That may work even better.
[02:17] <Unit193> OvenWerks: Great!  Glad to hear it.  64bit should be fine too now.
[02:18] <OvenWerks> Yes 64bit is what I am playing with in fact.
[02:23] <Unit193> Great!  Glad it's confirmed, and thanks a bunch for pointing it out.
[02:23] <OvenWerks> No problem.
[03:03] <hudsonkem> hello?
[03:03] <holstein> o/
[03:04] <holstein> hudsonkem: maybe you are looking for the support channel?
[03:04] <hudsonkem> yes
[03:04] <holstein> hudsonkem: cool.. thats #xubuntu for xubuntu.. and #ubuntu as well, for general ubuntu support
[03:05] <hudsonkem> ok thx, so 
[03:06] <hudsonkem> I have a cursor inssue, invisible cursor sometimes  after reboot, im right to type here?
[03:06] <holstein> hudsonkem: well, as i said, the support channel is #xubuntu
[03:07] <hudsonkem> got it sorry. thx for all bye
[03:07] <holstein> hudsonkem: you can still right click and get a menu? its literally invisible?
[03:07] <hudsonkem> yes
[03:08] <hudsonkem> work but I can't see. and I must try 3 times reboot to this work
[03:08] <holstein> i suppose, i would look into my gpu driver, after simply updating the machine.. then, i would look at my user.. it would be helpful to note if the cursor is "invisible" at the login screen, or no..
[03:09] <hudsonkem> yes reboot with invisible cursor
[03:10] <holstein> hudsonkem: please apply all updates
[03:10] <holstein> "sudo apt-get update && sudo apt-get dist-upgrade"
[03:10] <holstein> reboot, and *note* if the cursor is there at the login screen, and as other users
[03:11] <holstein> see if the issue is isolated to just the one user account
[03:11] <hudsonkem> I found other user with this inssue, so not alone me, 
[03:12] <holstein> hudsonkem: users on *your* machine, friend
[03:12] <holstein> *not* just randomly someone else.. please try the guest user, and/or another user *account*
[03:14] <hudsonkem> well, other users around the world, in ubuntu report
[03:14] <hudsonkem> them said about org.gnome.settings-daemon.plugins.xcursor
[03:14] <holstein> hudsonkem: sure, im not denying other users, as in, people, have that issue
[03:14] <holstein> hudsonkem: what im asking you to do has *nothing* to do with other people. im talking about user accounts on your machine
[03:14] <holstein> not other users, as in, people
[03:15] <holstein> please try as another user. the *guest* user.. login to your machine in the guest account, and test that the cursor works
[03:15] <hudsonkem> but, the trouble begin after lightdm start, when display GUI cursor is invisible
[03:16] <holstein> hudsonkem: so, as i ask, do you have a cursor in the guest account? yes or no?
[03:16] <hudsonkem> no
[03:16] <holstein> hudsonkem: ok.. are you up to date with upgrades, and rebooted into the most current kernel? yes? no?
[03:17] <hudsonkem> yes
[03:17] <holstein> hudsonkem: what GPU driver are you using? with what GPU hardware?
[03:18] <hudsonkem> just onboard or generic card drive
[03:19] <holstein> hudsonkem: sure.. i'll wait as you see what GPU you have, and driver, and report to me for further voluntaryy support, in the #xubuntu support channel.. thanks
[03:20] <hudsonkem> can you tell me commads to see that because I aways forgot that.
[03:21] <holstein> http://ubuntuforums.org/showthread.php?t=1795372
[03:24] <hudsonkem> thx, so it took a long text, may I put in text file and upload it?
[03:25] <holstein> !paste
[03:25] <holstein> hudsonkem: also, please use #xubuntu for support.. thanks
[03:29] <hudsonkem> http://paste.ubuntu.com/10893230/
[03:30] <holstein> hudsonkem: ok.. now, please, again, use the #xubuntu channel
[03:30] <holstein> hudsonkem: go there *now*, ok? do you understand? yes? no?
[03:31] <hudsonkem> yes, I am just here because You are asking me so I have to answer 
[03:31] <hudsonkem> thank you bye
[03:32] <holstein> hudsonkem: just /join #xubuntu
[04:31] <OvenWerks> holstein: check if he used the start disk maker in the system menu and is running live. The problem went away when I used dd to put the image on the USB drive. It was only a problem when running live.
[04:32]  * OvenWerks guess he is a bit late...
[06:11] <elfy> Unit193: boot with image, wait for it to autologin - fruitlessly, it wanted username/password
[06:13] <elfy> could be dodgy download
[06:27] <elfy> and apparently so, works in vbox - still  issues in kvm 
[07:53] <elfy> and we has 3 winners :)
[07:54] <elfy> new person showed up during final testing - p-brada - they win that
[07:54] <elfy> for the whole cycle - removing those previous recipients - dkessel :)
[07:55] <elfy> and for the whole cycle - in team - jjfrv8 reported 138 for us - thanks jjfrv8 :)
[08:14] <elfy> knome: when you have 5 minutes - a bit of help with LP bug search-fu ... 
[08:45] <dkessel> yay, thank you guys :)
[08:45] <elfy> thank you ;)
[08:46] <elfy> not sure if you saw this or the mail first, but you have one of those too :D
[08:47] <dkessel> saw the mail first :) tbh i wouldn't have thought i would get stickers, as i have only had time to help in the beginning of the cycle. but i it still was enough number-wise :)
[08:56] <elfy> well - in this situation, it is numbers that count :)
[10:57] <brainwash> bluesabre: can we close bug 1441460 ? the actual problem can be resolved by changing one light-locker option
[10:57] <brainwash> I don't think that “When the screensaver is deactivated” should be the default, or should it?
[11:01] <bluesabre> brainwash: It sounds like a race condition
[11:02] <bluesabre> The new default we have is that light-locker doesn't autolock by default
[11:02] <bluesabre> unless suspending
[11:02] <brainwash> the problem is that locking the screen makes the user session inactive and xfpm is not able to auto suspend the system then
[11:03] <brainwash> it's the vt switching drawback
[11:03] <bluesabre> right, but sometimes the suspend signal gets through before the vt switch actually occurs, and thats (I think) the race condition
[11:05] <brainwash> uhm
[11:06] <brainwash> you mean lock on suspend
[11:06] <brainwash> the report is about auto suspending while the lock screen is active
[11:07] <bluesabre> oh, that one
[11:07] <brainwash> so, lock screen after 10min.. suspend system after 15min
[11:07] <bluesabre> I misunderstood the report
[11:07] <bluesabre> then yeah, you're right
[11:08] <brainwash> this use case is problematic, so what can be done other then telling the user to change the light-locker option?
[11:09] <brainwash> which does not solve the problem completely
[11:09] <brainwash> once you switch to the lock screen, then xfpm has not power anymore :)
[11:09] <bluesabre> nothing, we do not currently have a solution for that scenario
[11:10] <bluesabre> unless the answer is, use a different lock screen to satisfy your needs
[11:10] <brainwash> we can only hope that light-locker without the vt switch will be ready for 16.04
[11:10] <brainwash> yeah
[11:45] <brainwash> bluesabre: did you read bug 1446247 ?
[11:46] <brainwash> Unit193 has not commented yet (ninja subscribed him)
[11:46] <brainwash> I don't know what the status or process is on this issue
[12:52] <Unit193> I commented outside of the bug.
[12:54] <brainwash> what is the status?
[12:54] <brainwash> is someone taking care of this bug?
[13:50] <elfy> a rather blunt 12.04 is EOL announcement is drafted
[14:35] <elfy> pleia2: thinking about people like the mexican news report we have on x.org - do we know if there's much of an appetite out there for OEM installs? 
[14:36] <elfy> now that Vivid is old hat - I'm looking to Wibbly now ;)
[14:36] <pleia2> elfy: I've heard nothing wrt OEM installs, and they take a massive amount of work (automated testing, etc)
[14:36] <elfy> yea 
[14:37] <elfy> but we 'could' do optional OEM tests - if it even works 
[14:37] <elfy> Mate manage
[14:38] <elfy> just thinking of things here is all 
[14:42] <pleia2> I honestly don't know much about it, have just heard some of the rumblings from canonical about all the work put in to work with manufacturers
[14:43] <drc> pleia2: Rumblings or grumblings?
[14:43] <elfy> pleia2: yea I have seen the same type of thing, mostly davmor2 
[14:44] <elfy> just wondering if there is a 'market' for it generally
[14:45] <elfy> I'd rather mix it up in 15.10 and need to mail list more frequently this cycle, try and get more of a constant flow
[14:45] <elfy> anyway - as I said - just thinking :)
[14:45] <elfy> you go back to looking forward to Sunday :D
[14:48] <pleia2> drc: yes ;)
[14:48] <pleia2> elfy: short of an OEM approaching us (they haven't), I'm inclined to say it's not a good investment of our time
[14:49] <pleia2> but yay for ideas
[14:50] <elfy> but the guy installing in a bunch of places in Mexico might have like to know it was possible 
[14:50] <elfy> that was the germ of the idea :
[14:50] <elfy> )
[14:50] <elfy> blaming you :D
[14:52] <pleia2> hehe
[14:53] <drc> always blame the mouthpiece :)
[14:53] <elfy> drc: of course - I thought you were older than me and would know :D
[14:57] <drc> OK, so where's the 15.10-omega iso?
[14:58] <elfy> currently it is still called 15.04-arch.iso :)
[14:58] <elfy> not even named yet - so that's a bit of an issue for the wibbly images :p
[14:59] <drc> Isn't kinda late to be choosing a name?  I thought they usually announced that a release ahead of schedule?
[15:00] <elfy> mmm 
[15:00] <drc> Maybe the rumor about negotiating for Wascally Wabit is trye....
[15:01] <elfy> well I don't know, and I've not heard anything 
[15:01] <elfy> and if I was getting anywhere close to divulging things I shouldn't - pleia2 would !ops me :D
[15:01] <drc> Just "rumblings" on a couple of lists/channels
[15:01] <elfy> yea for sure 
[15:02] <elfy> I'm not loud enough with the Wibbly Whinocewos 
[15:02] <elfy> apart from here http://ubuntuforums.org/forumdisplay.php?f=427
[15:34] <Guest96557> hi, im sorry to interrupt the quietness here, im wondering why im not able to upgrade from 14.10 to 15.04 through update-manager -d since i thought a "devel" update is always possible
[15:51] <holstein> OvenWerks: thats a good poing
[15:51] <holstein> point*
[15:51] <elfy> wasn't sure if it was a pong or a point for a moment then :D
[16:00] <OvenWerks> perhaps wrong channel?  :)
[16:04] <holstein> for me? that was an out dated response..
[16:04] <holstein> 00:31 < OvenWerks> holstein: check if he used the start disk maker in the system menu and is running live. The problem went away when I used dd 
[16:05] <holstein> biggest issue there was language barrier..
[16:05] <OvenWerks> holstein: Ahh. It is just that I had the same problem a few days ago.
[16:09]  * dkessel happily edits the wibbly QA pad
[16:45] <Unit193> elfy: FWIW, encryption in Xubuntu vivid worked except when trying to unlock with plymouth-theme-xubuntu-logo.
[16:49] <knome> elfy, hullo
[17:07] <dkessel> uh-oh: Work with the tracker developers to get out more meaningful data: TODO
[17:07]  * dkessel hides :)
[17:22] <knome> dkessel, yes, i'm looking at you
[17:23] <knome> dinner soon
[17:23] <dkessel> knome: heh - yeah, let's see what can be done about the tracker needs the other day
[18:49] <dkessel> woooo ping notifications are working again for quassel in xubuntu 15.04 =D
[18:50] <Unit193> dkessel: Oh no, now you'll know when we're talking to you.
[18:55] <dkessel> ...if i am on the laptop, and not on the phone, where the quassel connection is really unstable ;)
[18:56] <dkessel> Unit193: yes, be careful when mentioning my name now :)
[20:01] <knome> dkessel dkessel dkessel dkessel 
[20:01] <knome> oops
[20:01] <Unit193> Wait, why are we pinging dkessel?
[20:01] <elfy> yay pinging dkessel works now I see
[20:02] <elfy> Unit193: it's sunday in dkessel world - reason enough