[06:42] <knome> Unit193, what?
[06:43] <knome> bluesabre, potentially getting it finished today, depends on the real work (tm)
[12:30] <brainwash> printer applet will eat your memory https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863227
[13:47] <Spass> first part of my beta ISO testing is done - live session, I've reported my issues (there are many, unfortunately)
[13:48] <Spass> now I'm going to install it on my secondary drive
[16:48] <flocculant> amyone planning beta testing - should wait for the respin
[17:41] <brainwash> Spass: "xflock4 command didn't work at all" light-locker is not started in the live session anymore, therefore xflock4 won't do anything
[17:42] <Spass> brainwash, ahh ok, in that case sorry, I didn't know that
[17:42] <brainwash> is locking the screen part of a test case?
[17:43] <Spass> no, but I thought it was important
[17:43] <Spass> so is that related to my "not resuming from suspend" issue also?
[17:44] <brainwash> unlikely I'd think
[17:45] <brainwash> you could test with the regular Ubuntu beta
[17:46] <brainwash> did suspend break only in the beta for you?
[17:47] <Spass> I can test that later with a regular Ubuntu LTS
[17:51] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: thunar 1.8.2 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-thunar-1-8-2-released-tp51869.html (by Alexander Schwinn)
[18:27] <flocculant> brainwash: locking screen is in fact part of a testcase - post install 
[18:31] <brainwash> flocculant: in that case it will work
[18:32] <brainwash> just not during live session
[18:32] <flocculant> yea I know 
[18:33] <Spass> so maybe, if it's possible, it would be a good idea to disable "Lock screen" button from the Whisker Menu in Live Session?
[18:33] <flocculant> why?
[18:34] <Spass> because it doesn't work at all during live session, as brainwash wrote "light-locker is not started in the live session anymore, therefore xflock4 won't do anything"
[18:34] <flocculant> at times - hardware doesn't work in the live session - do we disable the live session :p
[18:34] <Spass> I just don't see a point to that button being visible, if locking is disabled
[18:35] <flocculant> Spass: I really don't think it's that important
[18:35] <Spass> it may confuse users
[18:35] <flocculant> once
[18:35] <Spass> I'm not saying that it's critical or something
[18:35] <flocculant> ack
[18:36] <Spass> and not "once", because it doesn't show any message with information that "it is disabled in the live session, move on"
[18:36] <flocculant> I suspect it's muich too late for 18.10 anyway
[18:39] <flocculant> bluesabre: on http://iso.qa.ubuntu.com/qatracker/milestones/396/builds/181438/testcases/1303/results
[18:40] <flocculant> result from malysps, #1 - pretty sure I've seen a bug report for this - but can't find it
[18:42] <brainwash> Spass: well, maybe think of it like this: it "locks" the screen, but instantly unlocks it due not being password protected in the first place
[18:42] <brainwash> it it wasn't, what password would you type to unlock?
[18:43] <Spass> brainwash, I still don't see a point to "Lock screen" button being visible in the main menu, when locking is disabled, but I agree, not a big problem
[18:43] <Spass> flocculant, I've mentioned those disappearing buttons here: https://bugzilla.xfce.org/show_bug.cgi?id=14606 maybe that was it?
[18:43] <brainwash> that's just the default menu config
[18:44] <brainwash> you are free to run light-locker manually, and then use the button
[18:45] <Spass> brainwash, I know, and if it's not possible to change it during the live session only, that's not an issue at all
[18:46] <flocculant> Spass: thought I'd seen something 
[18:46] <flocculant> oh - now I see you're malysps lol
[18:46] <Spass> yup :)
[18:47] <Spass> you got confused, once
[18:47] <flocculant> ha ha ha 
[18:48] <Spass> new beta ISOs will be released soon? or no specific date yet?
[18:49] <flocculant> Spass: not sure when
[18:49] <flocculant> it'll definitely be before tomorrow pm as they need testing by tomorrow pm ;)
[18:50] <flocculant> they have to wait for the package fix to land before they can respin
[18:50] <Spass> ok, I'll try to test them also
[18:51] <flocculant> I'll check the manifest diff to see what changes have landed - likely none that particularly affect us
[18:51] <flocculant> apart from the obvious one
[18:51] <flocculant> live virtualbox fails
[18:52] <flocculant> so - if that's the main change all we really need to do is smokestest 
[18:53] <Spass> brainwash, Ubuntu 18.04 live session, my laptop resumed from the suspend correctly after lid close / open
[18:54] <Spass> will test that on new Xubuntu 18.10 beta again
[18:54] <brainwash> 04?
[18:54] <Spass> yes, I just wanted to check if my laptop suspend is working with LTS at all
[18:54] <brainwash> ah I see
[18:55] <Spass> to check for possible regression 
[18:55] <brainwash> I assumed that this was given
[18:56] <brainwash> and suspend only broke in 18.10, maybe just recently in the beta
[19:24] <brainwash> ochosi: you may be able to explain this one: xfce4-terminal --icon=123 is not able to find 123.png in ~/.local/share/icons/, but it can if moved to ~/.local/share/icons/<theme>/<category>/<size>/
[19:25] <brainwash> could be the intended behaviour
[19:26] <ochosi> yeah, sounds as expected
[19:26] <brainwash> alright. thanks
[19:26] <ochosi> maybe it works if you put it to ~/.local/share/icons/hicolor
[19:26] <brainwash> will try that
[19:27] <brainwash> doesn't work
[19:40] <ochosi> maybe you need to add the <category>/<size> path too
[19:40] <ochosi> cause it all depends if the index.theme file of the respective icon theme defines the path you're using
[19:40] <ochosi> (as far as i know)
[19:43] <brainwash> personally, I only remember putting icons in ~/.icons, and it just worked some years ago
[19:45] <ochosi> hmm, possible
[19:45] <ochosi> i've maintained elementary-xfce for so long, i don't clearly remember the times before ;)
[20:39] <Unit193> Oh dang, forgot to tell bluesabre that elementary-xfce is up to date in Debian.
[20:39] <Unit193> elementary-xfce 0.13.1-1 uploaded by Unit 193 <unit193@ubuntu.com>
[20:40] <ochosi> \o/
[20:40] <ochosi> thanks Unit193 
[21:51] <bluesabre> Unit193: thanks! Hopefully I get a chance to tackle that soon