[02:48] <guiverc> arraybolt3[m], I received that message with LXQt 1.1, but not default LXQt on jammy... I've not got around to exploring it though on a cleaner system yet 
[02:49] <guiverc> that's from memory anyway; reminds me of it
[02:49] <arraybolt3[m]> OK, that makes sense. I was thinking, 18.04 upgrade, maybe software got lost because of the DE switch. But what you're saying makes sense, and I forgot that LXQt was themable.
[02:49] <lubot> [telegram] <teward001> i will make a note that 18.04 -> 20.04 alone is its own form of chaos, LXDE to LXQt switch is not pretty on many systems
[02:50] <lubot> [telegram] <teward001> we noted that in the past during that switchover to LXQt by default
[02:50] <guiverc> no need to apologize, you asked a question  (LXDE was my response too at first)
[02:50] <arraybolt3[m]> I'd imagine it would be messy. Ubuntu Studio specifically said, "Hey, we switched from XFCE to KDE, DON'T TRY TO UPGRADE THIS!"
[02:50] <guiverc> this box I'm using now (primary) was LXDE to LXQt conversion.. took me ~3 weeks of *redacted* to get it working right... it wasn't fun, but other boxes were ~easy 
[02:51] <lubot> [telegram] <teward001> see i always clean install when i upgrade my systems.
[02:51] <lubot> [telegram] <teward001> usually keeps my systems from exploding or being unclean when upgraded
[02:51] <arraybolt3[m]> Me also! I have yet to ever run a do-release-upgrade.
[02:52] <lubot> [telegram] <teward001> in fact 22.04 is on my update list on this laptop.
[02:52] <guiverc> Lubuntu did not support LXDE to LXQt conversion;  I use the 20.04.2  (https://lubuntu.me/focal-2-released/) paste for the NOTE - don't do it it's unsupported
[02:52] <arraybolt3[m]> guiverc on the other hand seems to be able to waltz through a do-release-upgrade like nothing.
[02:52] <lubot> [telegram] <teward001> i have in VMs or containers, but that's because server -> server upgrades tend to *just work* heh (re @lubuntu_bot: (irc) <arraybolt3[m]> Me also! I have yet to ever run a do-release-upgrade.)
[02:52] <lubot> [telegram] <teward001> well it depends on what you use the system for.  18.04 -> 20.04 upgrade was the only upgrade I ever did on this laptop but then I nuked it and clean installed and restored data I needed because leftover crap was degrading performance
[02:53] <lubot> [telegram] <teward001> 20.04 -> 22.04 will be a clean install and restore of the data/programs/etc. I need
[02:53] <guiverc> release-upgrade was smooth even on this box.. 3 weeks to get a 'usable' Lubuntu (LXQt) session I'd not want to repeat..  
[02:55]  * guiverc thankful for my multi-desktop install though... I just used the xubuntu session whilst Lubuntu/LXQt was broken here   (or Ubuntu-MATE too, GNOME if I wanted to pull out more hair...)
[04:01] <guiverc> should the jammy -proposed (SRU) calamares be visible yet?
[04:01] <arraybolt3[m]> guiverc: Probably not - I got the paperwork done, but I submitted it for Simon and Erich to look over, and so far I've not heard anything back about it from either of them. We've planned to do it on Monday, so that's probably when it will happen.
[04:02] <arraybolt3[m]> (We tried to do it on Friday but I ran out of time just at the very end and had to leave.)
[04:02] <guiverc> thanks for reminding me... I saw that (maybe last night..) which explains what I see currently; thanks Aaron 
[04:04] <guiverc> thanks arraybolt3[m] !
[04:05] <arraybolt3[m]> 👍️
[04:05] <arraybolt3[m]> (Sorry, got distracted by cute animal videos on r/shadowtherat
[04:05] <arraybolt3[m]> https://www.reddit.com/r/Shadowtherat/
[04:06] <guiverc> :)
[05:25] <guiverc> fyi.. the message (FAILED TO RUN "XDG-SCREENSAVER LOCK") earlier in #lubuntu, I've got on jammy with lxqt 1.1 on jammy.   I've got a fresh QA-test install of jammy now so will explore a little
[05:32] <arraybolt3[m]> guiverc: I'll dig around a bit too, sounds like a fun bug to troubleshoot.
[05:39] <guiverc> i'm trying to find an easy way to re-create it; I'm not trying to debug
[05:40] <arraybolt3[m]> Yeah, that's what I was going to do. I figure you do it in a physical environment, I do it in a virtual environment, and we both do it at the same time, we'll figure it out faster and have dual confirmation in two environments.
[05:41] <guiverc> :)  yep, currently using c2d with spinning rust.. but I've got an i5-ssd with clean install too with midget keyboard... my pref. is slow & full-size keyboard!
[05:45]  * guiverc adds old desktop also has large screens; better for my old eyes..
[05:47] <arraybolt3[m]> OK, SAML single sign-on is kinda creepy. I just went to make a discourse.ubuntu.com account, it auto-populated my email and username, didn't ask for or even let me set a password, and automatically logs me in with a single click of the Log In button.
[05:47] <arraybolt3[m]> Probably because I'm signed into Ubuntu One.
[05:47] <arraybolt3[m]> (Anyway, that's random and off-topic, but was kind of surprising.)
[05:55] <guiverc> I've been unable to re-create it on dc7700 (so far anyway); fresh install (suspends without errors on waking); added backports PPA & lxqt 1.1; reboot & suspending without issues.. changing xscreensaver & still no issues..  dc7700 is nvidia/nouveau where x201 where I got it is i915 but i didn't think it'd relate to video card
[05:56] <arraybolt3[m]> Maybe it has to do with the choice of screensaver?
[05:56]  * guiverc adds errors relating to the message reported on #lubuntu... the box had errors related to hardware I ignored!
[05:57] <guiverc> I went & looked at x201; it's set to GLPlanet so I'll try that
[05:58] <arraybolt3[m]> Another thing might be if it's set to no screensaver at all.
[05:59] <guiverc> default setup didn't have LOCK ticked; I'd likely have enabled that on x201 but trying dc7700 with glplanet & lock
[06:00] <guiverc> Now the message appears on dc7700 !!  
[06:00] <arraybolt3[m]> Also of note, after jammy upgrade - maybe the upgrade from focal has something to do with it... oh but you just got it?
[06:00] <guiverc> The LOCK SCREEN AFTER needs to be checked.
[06:00] <arraybolt3[m]> OK, will reproduce on my end shortly.
[06:00] <guiverc> dc7700 was installed today from current daily
[06:00] <arraybolt3[m]> (Still running the initial full upgrade after installation.)
[06:01] <arraybolt3[m]> Current daily of Kinetic? I'm on the official Jammy ISO.
[06:01] <guiverc> current jammy daily 20220724 
[06:02] <guiverc> next release being jammy; it's my focus; ie. https://phab.lubuntu.me/w/release-team/testing-checklist/?v=893   (dailies exist for kinetic, jammy, focal..)
[06:02] <arraybolt3[m]> Ah, Jammy daily. Forgot those existed. They probably save a lot of upgrade time, right?
[06:02] <guiverc> My QA-test installs are for 22.04.1 validation..  (august 4 from memory)
[06:03] <arraybolt3[m]> OK, that makes sense.
[06:03] <arraybolt3[m]> I forget that testing is a whole world of its own in Ubuntu development.
[06:03] <guiverc> have you achieved the message yet Aaron?  (I want to reboot & use another install without LXQt 1.1 to see if I can get it on existing 22.04)
[06:04] <arraybolt3[m]> Still waiting for my install to get fully ready, sorry it's taking me so long.
[06:04] <guiverc> not a problem... benefit of the QA-test installs I did earlier today :)
[06:04] <arraybolt3[m]> (Just finished the full upgrade, now I'm going to test without LXQt 1.1.0, then again with.)
[06:04] <arraybolt3[m]> Ah, that makes sense. 3rd gen i5 plus multitasking in my typical chaotic way = kind of slow processes sometimes.
[06:04] <guiverc> alas my testing pre-this didn't achieve it, but I won't have had LOCK SCREEN AFTER ticked; being defaults for new install (unticked)
[06:05]  * guiverc away awhile.. birb feed time, so attempting to feed & not get bit again...
[06:06] <arraybolt3[m]> guiverc: Got the message on a fresh Jammy install, I did not have to install LXQt 1.1.0.
[06:06] <guiverc> that's good & bad, thanks arraybolt3[m] , want to file the bug?
[06:07] <arraybolt3[m]> Sure.
[06:07]  * arraybolt3[m] struggles to wake VM out of suspend - don't put GNOME Boxes VMs to sleep!
[06:10] <arraybolt3[m]> OK, finally had to just do a force reset :(
[06:12] <arraybolt3[m]> guiverc: The bug triggers only if I hit "Suspend" - other methods of triggering the screensaver don't do it. What package do you think that is that's causing it? lxqt-panel? xscreensaver?
[06:12] <arraybolt3[m]> (The fact that it's bound to suspend is interesting to me.)
[06:22] <arraybolt3[m]> Just looked through LXQt's source code - I'm gonna file it against lxqt-session since I think that's the part that provides the Suspend button.
[06:22] <arraybolt3[m]> In the application menu.
[06:28] <guiverc> thanks arraybolt3[m] , I'd not yet decided on what package to file against (i avoided that by going out & getting bitten once again.. feeding jaws/parrots)
[06:28] <arraybolt3[m]> Oy. Your finger OK?
[06:29] <guiverc> I've only noticed it on suspend too, but its something I do ~daily on x201; but I've not noted it on this box which I suspend nightly too
[06:29] <guiverc> right hand currently is covered in bites; I've succeeded once ~last week I think in not being bit..
[06:30] <guiverc> yeah.. box besides me was on lock & no issue with xscreensaver on unlock 
[06:31] <arraybolt3[m]> Why does he keep biting? Does he just get really excited about food?
[06:34] <guiverc> https://photos.google.com/share/AF1QipP8x-I0kfA0BMEGUtyuWw5UEOpwRwIWiVMto7s-oPH9qOM1s1z7PNOLCa6LCbHWPQ/photo/AF1QipMsFexI4wGs6RNG5gCI6SPgD4K9HGXMkKkXizp6?key=WUtKUTFmYTlzZjUzV1p2X25pWkduZXAwQzFJRkd3   you try & tell one apart from others when they're 100+  ; behavior is the easiest I find, but I often detect the 'jaws' behavior too late
[06:35] <arraybolt3[m]> Wow, they're beautiful. And you just have those, just, normally, where you're at? (In the US they're rare and only at pet stores.)
[07:09] <arraybolt3[m]> guiverc: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1982730
[07:09] <ubot93> Launchpad bug 1982730 in lxqt-session (Ubuntu) "Suspending Lubuntu when the 'Lock Screen After' box is checked in XScreenSaver results in an error message about xdg-screensaver" [Undecided, New]
[07:16] <guiverc> thanks arraybolt3[m] 
[14:38] <Eickmeyer[m]> <arraybolt3[m]> "guiverc: Probably not - I got..." <- could you uh... relink please? Got lost in the ether.
[14:47] <arraybolt3[m]> Eickmeyer: Sure, one moment...
[14:48] <arraybolt3[m]> Simon Quigley (Developer) Eickmeyer SRU paperwork draft: https://paste.ubuntu.com/p/3GzN2wGkFv/
[14:50] <Eickmeyer[m]> One question: Have you tested it in a VM with Ubuntu Studio as well? Mostly just curious, I might be able to help put it through the paces.
[14:50] <arraybolt3[m]> I believe I did, but I can't remember for certain.
[14:50] <arraybolt3[m]> I'll try it once I've gotten fully awake.
[14:51] <Eickmeyer[m]> Ok, because if that's the case I'd like more mention of Ubuntu Studio as well in the SRU as being part of this, because that will minimize the amount of sign-off I'll have to do. Otherwise they'll assume I haven't been involved in this process and will have been blindsided.
[14:53] <arraybolt3[m]> I'll reproduce the LVM bug mentioned there in Ubuntu Studio - then I can directly mention the Ubuntu Studio ISO as something that can be used for bug verification.
[14:53] <Eickmeyer[m]> That's a good plan. It's just at first glance it appears very Lubuntu-centric, and this needs to appear like a team effort. We never know who's going to be on SRU shift when it's finally submitted.
[17:17] <arraybolt3[m]> Eickmeyer Simon Quigley (Developer) Calamares SRU draft take 2: https://paste.ubuntu.com/p/QPr8m2WGCt/
[17:18] <arraybolt3[m]> Eickmeyer: The Ubuntu Studio test installation is in progress right now (but it already looks like the new Calamares is working).
[17:20] <Eickmeyer[m]> arraybolt3: In my recollection, bullet point #2 in in the Impact section was also tested by Leo K and it does impact Ubuntu Studio, so please include that as well.
[17:21] <arraybolt3[m]> Oops, missed that. Thanks! (And yes, I just tested and verified that Ubuntu Studio is affected by that bullet point.)
[17:24] <arraybolt3[m]> (Also just finished confirming that the new Calamares fixes the issue.)