[00:49] <Unit193> ochosi: That's massivly crashy, yes..  I'd thought you tested it.
[07:32] <Unit193> brainwash: freshplayerplugin done anything good?
[08:20] <elfy> ochosi bluesabre - looks like end Jan/beginning Feb for systemd default 
[09:05] <ochosi> Unit193: nope, i just wanted the opportunity to test it
[09:57] <brainwash_> ochosi: this dbus call works http://lpaste.net/118360
[10:04] <brainwash_> "/org/freedesktop/ScreenSaver" instead of just "/ScreenSaver"
[10:20] <Mez> What's the best way to go about reporting xubuntu security issues these days ?
[10:28] <Mez> hello? Is this thing on?
[11:05] <ochosi> Mez: i've already replied to your bugreport
[11:07] <ochosi> brainwash: right. guess that means there'll have to be another bugreport. sucks cause i don't have kde around to try whether that works with their screensaver as well
[11:10] <ochosi> Mez: no need for private chat, that bugreport could also just as well be public btw
[11:10] <brainwash> which bug report? :)
[11:11] <Mez> ochosi: I can film that bug if you want.
[11:12] <Mez> It is definitely happening on multiple PCs here.
[11:12] <ochosi> no need to film it
[11:12] <Mez> might be something to do with multi-screen/whatever
[11:12] <ochosi> have you checked whether light-locker is running?
[11:12] <ochosi> (ps -A | grep light-locker)
[11:12] <ochosi> and how do you lock your session?
[11:13] <ochosi> brainwash: just the typical thing that we had a 1000 times already
[11:13] <Mez> ochosi: light-locker is not currently running.  I lock my session using ctrl+alt+del
[11:13] <brainwash> oh noes
[11:13] <ochosi> Mez: if it isn't running, then start it. bug fixed.
[11:13] <ochosi> how shall the locker lock the session if it isn't running?
[11:14] <Mez> if I lock my screen, it shows it's running?
[11:14] <ochosi> no,
[11:14] <Mez>  % ps -A | grep light-locker                                                                        dev/packaging one
[11:14] <Mez>  2853 ?        00:00:00 light-locker
[11:14] <Mez> Sorry, my mistake, I thought that was actually the grep it'd brought back
[11:15] <ochosi> so if you lock with light-locker-command -l from the terminal, what happens exactly?
[11:15] <ochosi> brainwash: anyway, you have more experience with taking ppl through this, feel free to take over i gotta go in 5mins anyway
[11:16] <Mez> ochosi: it switches me to a lock screen on vt8
[11:16] <Mez> ochosi, and then I hit ctrl+alt+f7, and bypass entering my password 
[11:16] <Mez> to get back to typing to you here.
[11:18] <ochosi> Mez: i can't help you to debug this now, simply cause i don't have time
[11:18] <ochosi> but it's working for pretty much everyone else, in case that helps you ;)
[11:18] <ochosi> so clean install, update all packages and it should work
[11:19] <ochosi> maybe someone else can help you get to the bottom of what's not working for you
[11:19] <Mez> ochosi: This is a clean instlal, update all packages :)
[11:19] <Mez> I'm setting up a VM to replicate it
[11:19] <ochosi> bbl
[11:21] <brainwash> Mez: kill the currently running instance of light-locker and restart it in debug mode "light-locker --debug"
[11:21] <brainwash> now lock the screen
[11:22] <brainwash> can you please link your bug report also?
[11:25] <Mez> https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1410195
[11:25] <Mez> http://paste.ubuntu.com/9728445/
[11:28] <Mez> VM seems to work with the locked screen
[11:29] <brainwash> Mez: your bug report is still not visible to all people (private)
[11:31] <brainwash> the log file contains some error messages
[11:33] <brainwash> in any case, if it's really a bug, please forward it upstream -> https://github.com/the-cavalry/light-locker
[11:39] <brainwash> Unit193: maybe, test it and you will know
[11:40] <brainwash> Unit193: I use chromium with pepperflash to view flash content, so I cannot tell
[11:58] <Mez> brainwash: I've kinda tracked it down, so that post is public now
[12:06] <knome> lderan, hullo
[12:07] <knome> people, check your work item statuses in blueprints so they are uptodate
[12:11] <brainwash> Mez: great :) and don't forget to file the upstream report
[12:57] <bluesabre> knome: ofc
[12:57] <bluesabre> Unit193: will have the new light-locker-settings released and uploaded tonight, so you can drop from the seed after that point
[12:58] <bluesabre> ochosi: if you get a chance, can you also take a look at lightdm-gtk-greeter to see if there is anything else we want to merge/add for 2.0?
[12:59] <bluesabre> elfy: would lightdm-gtk-greeter testing fit in before systemd?
[13:12] <elfy> bluesabre: don't see why not if we're missing A2 
[13:17] <ochosi> bluesabre: i guess we'd have to take a look at all those branches pending for merge against the greeter...
[13:35] <elfy> bluesabre: just so you're aware - nothing is now planned until w/c 16Feb 
[15:15] <brainwash> ali1234: can you reproduce bug 1379176 in 14.10 or 15.04 (ideally with a new user or clean profile)?
[15:18] <ali1234> no
[15:19] <brainwash> thanks for testing it :)
[18:11] <knome> elfy, i'll drop the qa process stuff in the wiki today (within the next hours) now that i've cleaned up the proessses page
[18:13] <pleia2> sorry for not doing the QA goodies blog post draft yet, came down with the flu on friday and just now starting to be less zombie today
[18:15] <elfy> sort the health out first :)
[18:15] <elfy> that's been hanging about since the middle of the last cycle another week isn't going to make a lot of difference
[18:15] <elfy> or week(s) :)
[18:19] <knome> pleia2, does that mean i can poke you about more things too? :P
[18:20] <knome> time to work on $paid_work for a while now
[18:20] <knome> but brb
[18:21] <pleia2> knome: that means I'm now buried in work I didn't do for the next four days and won't be able to  add new work for a week or so ;)
[18:22] <knome> awwh :(
[18:23] <knome> pleia2, tell hp they made me work a lot on the flyer printing because linux printing is weird and that i would like you to get compensation for that as paid hours used to contribute to xubuntu
[18:28] <pleia2> I use a Brother printer
[18:29] <knome> pleia2, i said they made *me* to work a lot... ;)
[18:29] <pleia2> heh :)
[18:29] <knome> i remember back then when brother was publicly considered the "laser printer for people who can't afford a laser printer"
[18:30] <knome> at least the people who i knew thoght that..
[18:30] <knome> including my father :P
[20:03] <Unit193> bluesabre: Wonderful, thanks.
[20:53] <ochosi> evening all
[21:07]  * dkessel spreads brother printers everywhere he installs ubuntu in the last years
[21:09] <ochosi> feel free to stop by at my place, i could really use a printer
[21:12] <brainwash> ochosi: want to take a look at some log files and comments (recently added)? bug 1307545
[21:12] <dkessel> you can get a printer only model for less than 80€
[21:13] <ochosi> brainwash: gah, not that again
[21:13] <brainwash> ochosi: I know, but it's affecting many users, so maybe we can somehow solve the mystery
[21:16] <Unit193> ochosi: Blame upower or systemd, that's always the in thing.
[21:16] <ochosi> unfortunately it's mostly true
[21:16] <brainwash> or find a way to get the correct log files
[21:17] <brainwash> sadly, people blame the power manager for not being 100% compatible
[21:19] <ochosi> for some reason the power manager says a few times that Action=org.freedesktop.upower.suspend is authorized=FALSE
[21:20] <ochosi> for #19 it's obvious
[21:20] <ochosi> the inhibit config doesn't include the lid-switch
[21:20] <ochosi> it should be
[21:20] <ochosi> Inhibiting systemd sleep: handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch
[21:20] <ochosi> but it is set to
[21:20] <ochosi> Inhibiting systemd sleep: handle-power-key:handle-suspend-key:handle-hibernate-key
[21:21] <ochosi> for b3nmore everything seems to work, so not sure i get why he's posting there
[21:21] <ochosi> and yeah, his config reflects that
[21:21] <brainwash> ah, so the logind-handle-lid-switch settings is wrong?
[21:21] <brainwash> in the first case
[21:21] <ochosi> my guess is that this is a simple update problem with old settings being kept
[21:21] <ochosi> hence logind not being inhibited correctly
[21:22] <ochosi> yeah, i would say so
[21:22] <ochosi> but this is not a setting transparent to the user, so resetting the config should add the handle-lid-switch
[21:23] <ochosi> frankly, i gave up on following that mess when it was decided to "invert the logic/naming"
[21:24] <brainwash> yeah xD TRUE or FALSE.. what the heck is going on here
[21:24] <brainwash> both options seem to have drawbacks
[21:24] <ochosi> i guess logind-handle-lid-switch should be "false"
[21:24] <ochosi> which options?
[21:25] <brainwash> true or false
[21:25] <ochosi> why?
[21:25] <ochosi> you mean because of the black screen bug?
[21:25] <brainwash> yes, it's a mess
[21:25] <ochosi> i don't think that's a problem, iirc we fixed that
[21:26] <ochosi> it just gives you control over logind but doesn't really inhibit it
[21:26] <ochosi> so if you set it to suspend on lid close it just let's logind handle the whole thing
[21:26] <brainwash> the last comment is confusing too
[21:26] <ochosi> if you set it to lock or blank, it inhibits logind
[21:26] <ochosi> so no downside
[21:26] <ochosi> and the setting should be applied by xfpm itself in the background, depending on your other settings
[21:27] <ochosi> so in b3nmore's case, logind doesn't handle the lid because he's just switching off the screen on lid-close
[21:27] <ochosi> so logind-handle-lid-switch=false
[21:28] <ochosi> (actually that *does* make sense)
[21:28] <ochosi> f-pel has some odd setup, not sure why his output says that logind handles the lid
[21:29] <ochosi> my guess is he only set "switch off screen" on battery, but has ac plugged in
[21:29] <ochosi> something like that
[21:29] <ochosi> or his config is still old and he didn't follow your instructions or managed to screw that step up
[21:29] <ochosi> so, all clear? :)
[21:35] <ochosi> well i might have to pastebin all i said for brainwash...
[21:40] <ochosi> what a mess
[21:41] <Unit193> Slightly, but you did see the global, no?
[21:41] <brainwash> ochosi: b3nmore says that FALSE -> black screen bug, TRUE -> pm settings ignored
[21:41] <brainwash> in utopic
[21:41] <brainwash> for logind-handle-lid-switch
[21:42] <brainwash> and FALSE is the default value
[21:42] <ochosi> as i said, the power manager should change that value depending on your config
[21:43] <brainwash> depending on the lid close action
[21:44] <ochosi> yeah
[21:45] <brainwash> so, the bottom line is that his black screen bug is has a different cause
[21:45] <brainwash> -is
[21:46] <ochosi> if logind handles the suspend-lid-action, then the black screen bug is not the one we fixed
[21:46] <ochosi> then yeah, he's seeing something else
[21:46] <ochosi> for instance, i consistently get that bug with the nouveau driver
[21:46] <ochosi> with nvidia, everything is fine
[21:46] <ochosi> actually i don't even get to the greeter anymore if i set lock on suspend to true
[21:48] <brainwash> uhm, that's bad
[21:51] <brainwash> hopefully this whole thing can be fixed before 16.04 :)
[21:52] <ochosi> i dunno, i'm not actively pursuing this anymore
[21:53] <ochosi> it's working for most people and we'll deactivate lock on suspend by default
[21:53] <ochosi> as far as i can see, i've done all i can
[22:02] <brainwash> ochosi: right, I'll try to close this report. the new logs and comments just confirmed that the default settings (if applied) work fine
[22:03] <ochosi> brainwash: yes, that's how i read it
[22:03] <ochosi> thing is, people will always obsess with this bug in some ways
[22:03] <ochosi> just as there are 1000 bugreports on suspend not working nicely on linux in general
[22:04] <ochosi> the only problem we have is that people think it's our fault when it isn't
[22:05] <knome> hey ochosi 
[22:05] <ochosi> hey knome 
[22:05] <ochosi> and wb
[22:05] <knome> time for a PM?
[22:07] <ochosi> yup
[23:25] <ochosi> bluesabre: not sure what/who is at fault, but the spinner in catfish's statusbar is broken in Gtk3.14 (with all themes, incl. Ambiance and Adwaita)