[01:29] <jphilipz> not sure if others are facing this running daily, but after the lock screen and screen saver kick in, i move my mouse or press a key and then the screen goes black, so i end up having to press Ctrl+Alt+f9 and then Ctrl+Alt+f8 to be able to see the login screen.
[01:30] <jphilipz> bluesabre: is this possibly a problem with the screensaver code as this doesnt happen on 18.04
[01:50] <guiverc2> jphilipz, i've a daily running on a box now, will have a look shortly (10-15 mins); could also try it on different box but that'd require longer..
[01:55] <jphilipz> guiverc2: thanks
[01:55] <jphilipz> its been bugging me for a while, but assumed it would be fixed with the latest round updates
[01:55] <guiverc2> jphilipz, by default (live) lock screen was disabled (so selecting lock on menu did nothing until I enabled it), so could black screen be just the screensaver default to black-screen?
[01:56] <jphilipz> guiverc2: yes black is the default screensaver. i changed it to something different and it still happens
[01:57] <guiverc2> otherwise behavior on my box appears normal, but i'll keep going my 'testing'  (yeah I changed it to xfce/mice so I'm not confused)
[01:59] <guiverc2> when i finish this test; I'll boot the 'live' on a different box & re-look at lock/screensaver for you, but likely won't be for ~30+ mins
[02:09] <jphilipz> thanks
[02:24] <guiverc2> jphilipz, sorry no issues on this box either (http://iso.qa.ubuntu.com/qatracker/milestones/404/builds/196132/testcases/1303/results will list the boxes used; j3400 & hp8200)  i could test on vaio too (horrid little netbook)
[04:40] <guiverc2> jphilipz, fyi:  on vaio (now yesterday's 19.10 daily) i had no issues either with lock/screensaver
[08:58] <bluesabre> jphilipz, guiverc2, light-locker was replaced with xfce4-screensaver recently on the daily images. If you're running an installed version from before a few days ago, you may have both light-locker and xfce4-screensaver installed. If you do, try uninstalling light-locker and rebooting.
[09:00] <guiverc2> i was using daily 20190710 (yesterday's now) as the initial question mentioned "daily"
[09:02] <guiverc2> (but thanks bluesabre)
[09:03] <bluesabre> guiverc2: just thought I'd make sure, I've had people complain about the daily in the past under the assumption an updated install was equal to the daily :)
[09:04] <guiverc2> thanks again; maybe that was what was meant - I sure didn't consider that as a possibility
[11:34] <jphilipz> bluesabre, guiverc2: removal of light-locker solved it. so is not recommended that we install daily and run it as a daily driver?
[11:45] <guiverc2> jphilipz, I am running 19.10 right now on an installed system.  Daily though refers to daily images that can be installed (for QA-test purposes) and for use, but they cease being a 'daily' after installation, but an installed 19.10 system.  You originally mentioned 'daily' in the first post I read & responded to (thus I assumed uninstalled or installed today)
[11:48] <jphilipz> guiverc2: thanks for the explanation. i mentioned daily in the sense that it was updated to the latest available in the repo as of today
[11:50] <guiverc2> which is what bluesabre suspected; I read it as the 'daily' image produced each day for qa-testing - ie. http://iso.qa.ubuntu.com/qatracker/milestones/404/builds/196185/downloads  (where it's called daily-live)
[11:53] <guiverc2> sorry; because I do QA-testing using daily images; I jumped to conclusion in the term I see very often...
[11:58] <jphilipz> no i'm sorry for not knowing the correct terms to use :D
[12:07] <guiverc2> :)
[12:34] <brainwash> bluesabre: what do you think about this? bug 1835668
[12:35] <brainwash> with xfce4-screensaver it could be re-enabled again I think
[12:35] <brainwash> the user name does not need to be guessed
[12:35] <brainwash> but the blank password may still irritate some people
[12:54] <brainwash> ochosi: what is your opinion on adding more contrast to the tasklist buttons? https://paste.debian.net/1091247/
[13:01] <guiverc2> brainwash on 20190710's 19.10 daily I can set a password (passwd), then lock at menu (after enabling lock) and it won't let me unlock until I enter password
[13:02] <guiverc2> (i'm butting in I know, but I see no issue; I can respond with this info on bug you mentioned, though I don't have a 19.04 lying around to test on that version)
[13:03] <brainwash> https://git.launchpad.net/xubuntu-default-settings/commit/?id=650fd90df8d1e3e7b15fd789907fa47e9e2f68e5
[13:04] <brainwash> it can be enabled
[13:05] <brainwash> the question is if it should be enabled without user interaction
[13:06] <guiverc2> okay - I'd say leave it as it is myself; but let those that do the work decide (not me)
[13:07] <brainwash> or, how confusing is a lock screen which asks the (live) user for a blank password?
[13:08] <brainwash> previously, the user had to guess the user name ("xubuntu")
[13:08] <guiverc2> that to me would be the more confusing; but you can't win anyway; users won't like the 'lock' not working (I thought it was a bug until I discovered I can enable it...)
[13:09] <brainwash> maybe xfce4-screensaver could omit asking for the password in case it is not set
[13:09] <guiverc2> sounds like you're making more work for yourself (or the team); but sounds great
[13:09] <brainwash> maybe that is how it works already
[13:09] <brainwash> I have not tested it :)
[13:10] <brainwash> I think I remember that gnome-screensaver was behaving that way
[13:10] <guiverc2> i have tested it; why I commented that I see no issue
[13:39] <jphilipz> brainwash: blank password should be fine for most users, as they will try to click login without one if the dialog appears
[13:39] <jphilipz> had a bad experience with linux lite that the blank password wasnt accepted - https://twitter.com/jphilipz/status/1145523352225878016
[13:40] <jphilipz> though their forum clearly states there wasnt a password
[13:40] <knome> pleia2, yeah...
[13:41] <jphilipz> i tried an xfce based distro recently and when there was no password for the user, the password field was hidden
[13:43] <jphilipz> it was Galore
[13:48] <jphilipz> Galore is based of Xubuntu
[13:53] <jphilipz> account with a password - http://i.imgur.com/WYcaays.png
[13:53] <jphilipz> account with no password - http://i.imgur.com/rln4tIz.png
[14:06] <RikMills> jphilipz: 2nd of those
[14:06] <jphilipz> RikMills: thanks
[14:07] <jphilipz> re-downloading 1.5gb regularly would be a waste :D
[14:14] <jphilipz> RikMills: should i reinstall xubuntu each time i update the daily iso, as i was hoping to use it as a daily driver and get the updates through the software updater
[14:48] <brainwash> jphilipz: why would you want to reinstall it all the time?
[14:48] <jphilipz> brainwash: want to run the latest or is that not useful for QA testing
[14:50] <brainwash> you can keep updating via software updater and test with newly created user accounts I guess
[14:51] <brainwash> unneeded packages can be removed with apt autoremove
[14:51] <brainwash> thinking of the light-locker case
[14:52] <jphilipz> yes i was thinking that if software updater didnt fix the light-locker case, then i'm not really running the latest
[15:37] <jphilipz> brainwash: maybe i mistook what you were saying. would apt autoremove have removed light-locker?
[16:46] <flocculant> jphilipz: if you wanted to do it how I did for many years till I left the xubuntu team - run the 'whatever version we are expecting to release' as your daily machine (kept updated), download the actual daily iso and run it to test things you want to look at specifically - or know there is an issue with
[16:46] <flocculant> which is pretty much how I left all the QA docs
[16:47] <flocculant> also you could add the daily iso to your grub - in that case, zsync it - then reboot and run from grub - that's a bit better than running in a vm
[16:48] <flocculant> I'm still floating about - just not official anymore - a ping or freenode message to me (or in fact an e-mail) and I'll answer questions
[16:50] <flocculant> jphilipz: this is how I'd set up grub custom file > https://paste.ubuntu.com/p/J6m7M7Bqtw/
[16:51] <flocculant> obviously change path to suit
[16:57] <jphilipz> flocculant: sounds like a great idea, will try it
[16:58] <jphilipz> what is the differences between the two grub entries?
[16:58] <flocculant> jphilipz: if you've questions - ask them :D
[16:59] <flocculant> one loads the iso to ram - one doesn't - at one point loading to ram meant you could install from it - then it stopped doing that, so I stopped too hence it being cosmic
[16:59] <flocculant> and also last cycle I was moving on slowly so didn't do much 
[17:05] <jphilipz> flocculant: do i need to uncomment the non-ram entry for it to get added?
[17:06] <flocculant> if you use that - you need to uncomment stuff yea - other wise it won't - and change the path - and update update grub too once it's changed
[17:07] <flocculant> I had a script I used to grab iso's with zsync then it copied the file to that location
[17:08] <jphilipz> where do i put the bash script?
[17:08] <flocculant> I had it in my home 
[17:08] <flocculant> you want a copy of it?
[17:09] <jphilipz> no the bash script you gave on paste.ubuntu.com
[17:09] <flocculant> oh right - I had another one lol
[17:09] <flocculant> that file already exists 
[17:09] <flocculant> /etc/grub.d/40_custom
[17:10] <flocculant> edit that as root 
[17:10] <flocculant> then update grub
[17:10] <jphilipz> thanks
[17:10] <flocculant> np
[17:11] <flocculant> if you want to automate zsync a bit - I can let you have that too
[17:11] <jphilipz> okay thanks
[17:11] <flocculant> is that a yes?
[17:11] <flocculant> lol
[17:11] <jphilipz> yes
[17:11] <jphilipz> lol
[17:12] <albinard> Problem about bug reporting, need some advice
[17:12] <pleia2> ask away :)
[17:12] <flocculant> jphilipz: you want me to annotate it a bit
[17:13] <flocculant> albinard: indeed :D
[17:13] <flocculant> hi pleia2 - I'm still about - just officially unofficial now lol
[17:13] <jphilipz> flocculant: if its not to complicated, i think i could figure it out
[17:13] <pleia2> o/ flocculant 
[17:13] <pleia2> flocculant: it's like Hotel California over here ;)
[17:14] <flocculant> jphilipz: okey doke - it does a bunch of stuff I used to want to know when I ran qa for us
[17:14] <albinard> Just did a test install of Eoan ISO 0711: went okay up to first desktop appearance; file manager okay (read from USB and other partitions), but no menu at all available.
[17:14] <flocculant> jphilipz: https://paste.ubuntu.com/p/9JcQTkcMfX/
[17:15] <flocculant> albinard: ubuntu-bug thunar
[17:15] <flocculant> pleia2: lol
[17:15] <Alexdf> XFCE 4.14 pre2!
[17:15] <Alexdf> https://simon.shimmerproject.org/2019/05/19/xfce-4-14pre1-released/
[17:16] <Alexdf> https://simon.shimmerproject.org/2019/07/01/xfce-4-14pre2-released/
[17:16] <Alexdf> I<3Xubuntu :D
[17:18] <albinard> Out of my league here - what bug number to report?
[17:21] <pleia2> as flocculant suggested, you run "ubuntu-bug thunar" and that walks you through the process of submitting the bug you found for the file manager (thunar)
[17:21] <pleia2> then you use that bug number in the tracker
[17:34] <albinard> Thanks! Did it and reported. Sorry to be a pain!
[17:34] <flocculant> albinard: no worries - how else does one learn something :)
[17:43] <jphilipz> might be good to have a text file on the live desktop on how to submit a bug
[17:48] <flocculant> jphilipz: on all xubuntu test cases - there is a link that says link to bug reporting instructions ...
[17:48] <flocculant> https://pasteboard.co/InvXKyM.png
[17:49] <flocculant> the link you get pointed at is https://docs.xubuntu.org/contributors/qa-bugs.html
[17:49] <jphilipz> flocculant: is this on the daily iso?
[17:50] <flocculant> it's not on the iso - it's on the tracker
[17:51] <jphilipz> having something on the iso for the random person who decides to try out the daily iso and has no knowledge of the QA procedures might be helpful
[17:52] <flocculant> jphilipz: perhaps - but bugs should be reported on the tracker - which is where it tells people how to do it
[17:55] <jphilipz> didnt follow 'which is where it tells people how to do it'
[17:56] <flocculant> on the tracker
[17:56] <flocculant> anyway - not much to do with me now - I'm just hanging about :)
[17:57] <jphilipz> oh okay, maybe i'll propose it in an email to the team
[17:57] <jphilipz> so now that you've left as lead QA, has someone replaced you?
[17:58] <flocculant> nope
[17:58] <flocculant> someone is needed
[17:59] <jphilipz> what responsibilities and skills does a lead QA need
[18:02] <flocculant> after 6 or 7 years doing it - you need to be able to herd cats
[18:03] <flocculant> bluesabre: is probably the one to ask - team might be wanting to change things about
[18:04] <flocculant> https://docs.xubuntu.org/contributors/qa.html
[18:05] <flocculant> jphilipz: I'm off now - back in the morning fleetingly if you've questions
[18:05] <jphilipz> flocculant: thanks for the help. have a good one
[19:45] <albinard> Rebooted same test install, no other changes, now Whiskermenu responds, seems to work.  
[20:01] <albinard> Reported that on QA and Launchpad, guess it is a non-bug or an erratic.
[21:06] <albinard> Puzzled by the bug that vanished.
[21:10] <Unit193> albinard: Right, so you remind me that I owe you an email.  For the time being there won't be any more Xubuntu Core as there's still that issue booting.
[21:14] <albinard> No worries, no "owe" - but thanks for the update.  I suspect the bug I reported had something to do with xfce4-whiskermenu-plugin, because that was what didn't respond at the first time I booted the new ISO.  At the reboot, there it was , just fine.
[21:16] <albinard> And seems to be running fine ever since.