[01:36] <bluesabre> flocculant, robert uploaded a new lightdm that resolves the issue for him
[01:36] <Unit193> bluesabre: Have you filed the thunar SRU yet? ;3
[01:37] <bluesabre> Unit193, https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1512120
[01:37] <ubottu> Launchpad bug 1512120 in thunar (Ubuntu Yakkety) "[SRU] thunar crashes on file renaming" [Undecided,New]
[01:37] <bluesabre> yakkety uploaded a bit ago
[01:37] <bluesabre> working on xenial now
[01:37] <Unit193> Sweet, thanks.
[01:37] <bluesabre> np :)
[01:38] <Unit193> I wondered if we'd want to FFe notifyd, but...
[01:39] <knome> when was FF?
[01:40] <bluesabre> last week
[01:40] <knome> mhm
[01:40] <bluesabre> I'm not opposed to it
[01:40] <knome> me neither; we're far from an LTS, so we should have some wiggle room
[01:40] <knome> though you should ask QA too
[01:42] <Unit193> Well, I'm not in charge of any answers so suits me. :D
[01:59] <bluesabre> :)
[02:11] <knome> time to go to bed
[02:11] <knome> ttyl
[02:12] <bluesabre> nighty knome
[02:33] <bluesabre> was going to test thunar in xenial, but apparently xenial doesn't like kvm
[07:13] <flocculant> bluesabre: xenial liked kvm for me for a whole cycle ... 
[07:14] <flocculant> bluesabre: re lightdm - grabbed from -proposed. From Lock not managed to break it there. From Suspend, if I'm a bit quick then I get knocked back to unlock from desktop but second try works
[07:14] <flocculant> will report that on bug for Robert
[07:15] <flocculant> bluesabre: re xenial - I'll update my hardware jobby and get thunar there and do all the mad back and forth stuff I did when testing the patches
[07:32] <flocculant> once I see the verification- tags show up
[07:33] <flocculant> bug 1666803
[07:33] <ubottu> bug 1666803 in Light Display Manager "Password required twice returning from suspend" [Undecided,New] https://launchpad.net/bugs/1666803
[07:50] <flocculant> qa likes notifyd changes ... 
[07:51] <Unit193> bluesabre: ↑ Figured he'd been testing it from xfce4-gtk3 too. :D
[07:51] <flocculant> :)
[07:51] <flocculant> morning Unit193 
[07:52] <Unit193> Howdy.
[07:52] <flocculant> that was a busy start to my day ... 
[07:52] <flocculant> locking and unlocking repeatedly ... 
[08:22] <flocculant> bluesabre: in Settings in menu I currently see 3 entries for Disks - that's been reported on bug 1666693, so it's obviously not l-d-s - what is the likely suspect? gnome-disk-utility itself? I kind of assume so ...
[08:22] <ubottu> bug 1666693 in lubuntu-default-settings (Ubuntu) "gnome-disks shows three icons in menu of lxpanel " [Undecided,Confirmed] https://launchpad.net/bugs/1666693
[11:28] <bluesabre> flocculant, gnome-disk-utility seems to be at fault, commented on bug
[11:30] <bluesabre> flocculant, suspending with lock is kind of a pain... I wonder if there is something more we can do on the xfce side to make that a bit more secure/reliable
[11:31] <bluesabre> flocculant, since you're a fan of the notifyd changes, and none of us seem to be against them, we can probably start working on the FFe to get that in
[12:03] <flocculant> bluesabre: okey doke to all that - re suspend with lock, if I let the login screen settle down it unlocks fine
[12:03] <flocculant> also 
[12:03] <flocculant> of course - I am suspend - reboot - unlock - suspend - reboot - unlock
[12:04] <flocculant> with no patience - which is unlikely to be normal behaviour :)
[12:06] <flocculant> will respin our images later to get lightdm
[12:09] <bluesabre> flocculant, great, thanks!
[12:10] <flocculant> doing now - package available - will mail testers later
[12:11] <flocculant> bluesabre: so yea just quickly - I think the suspend thing for me - is I'm rapidly testing it 
[12:12] <flocculant> not that it should be a problem - but unlikely anyone would do that in normal life I guess
[12:12] <bluesabre> yeah, it seems like a less common use case
[12:12] <flocculant> :)
[12:15] <flocculant> I'll hassle jbicha re Disks when I see him about later :p
=== DalekSec_ is now known as DalekSec
[20:00] <flocculant> bluesabre: just fyi - my seeing double password from suspend appears to depend on nouveau - nvidia 'appears' slower and I can't seem to break it
[20:03] <ali1234> double password?
[20:03] <flocculant> ali1234: unlock from suspend = see desktop - flung back to unlock screen
[20:04] <ali1234> ah that
[20:04] <flocculant> yea
[20:04] <ali1234> i think the lock screen is shown on another vt
[20:04] <flocculant> another cycle - another lock issue
[20:04] <ali1234> so it has to switch - after unsuspend
[20:04] <flocculant> vt8 iirc
[20:04] <ali1234> yeah
[20:04] <ali1234> lightdm handles it all iirc
[20:04] <flocculant> yea
[20:05] <ali1234> so nouveau has KMS which means it can switch between VTs and the console without resolution switch
[20:06] <flocculant> part of an ongoing conversation since pre-beta yakkety - which stopped while it worked for a bit - then started again a few weeks ago - when it stopped unlocking again
[20:06] <wxl> flocculant: have you guys had any problem with oem mode?
[20:06] <ali1234> the proprietary driver does not have KMS so when it switches between VTs it changes the screen mode, which takes longer to process, so the picture disappears for longer and you dont see what it is really doing
[20:07] <flocculant> wxl: no - when I've tested it - it works as expected
[20:07] <flocculant> wxl and changed package in the 3 Disks bug
[20:07] <knome> we've just begun testing/looking into it seriously otoh
[20:07] <knome> sauna, bbl
[20:07] <flocculant> knome: yea
[20:07] <wxl> flocculant: great thanks. re: oem we've got this http://launchpad.net/bugs/1638473
[20:07] <ubottu> Launchpad bug 1638473 in oem-config (Ubuntu) "Blank screen after running oem-config" [Undecided,Confirmed]
[20:08] <flocculant> wxl I've definitely looked in the last week
[20:08] <flocculant> ali1234: right
[20:08] <wxl> flocculant: in kvm?
[20:08] <flocculant> wxl: yea
[20:09] <wxl> flocculant: might be vbox specific
[20:09] <flocculant> not tried on hardware - not got vbox anymore - kvm works ok
[20:12] <flocculant> second drive to hospital - back later
[21:38] <ochosi> flocculant: so the unlock bug has been resolved in lightdm..?
[21:38] <ochosi> or did i misinterpret the update on the report
[22:16] <flocculant> ochosi: pretty much sorted yep :)
[22:20] <Unit193> bluesabre: That did not work.
[22:21] <Unit193> ls -1 ~
[22:21] <Unit193> Plain Text.txt
[22:21] <Unit193> OpenDocument Spreadsheet.ods
[22:21] <Unit193> OpenDocument Text.odt
[23:02] <flocculant> ochosi: I think I might revisit that testing of gtk3 settings manager in a vanilla install here
[23:03] <flocculant> I'm rather lost about what I've got that was gtk2 and is now gtk3 and what I've got because I built it locally and/or ppa
[23:03] <bluesabre> Unit193, oh no
[23:04] <flocculant> evening bluesabre 
[23:04] <bluesabre> flocculant, hiya
[23:09] <bluesabre> Unit193, will take a look tonight... shoulda worked though :\
[23:25] <flocculant> bluesabre: nicely we have all green on the tracker
[23:25] <flocculant> hope to get enought time to sort the release note out a bit more before tomorrow evening
[23:29] <Unit193> bluesabre: :D