arraybolt3[m]Dan Simmons: If you don't mind, could you look over the XScreenSaver file I have here and give it a final thumbs-up so I can throw it into the packaging and upload it, and maybe also work on getting it SRU'd into Kinetic?00:32
arraybolt3[m]I did make one change more since last I submitted it for review, which is I changed the URL that the Help button on the XScreenSaver splash screen goes to (it now points to a man page on manpages.ubuntu.com rather than to XScreenSaver's website). I changed that because the guy who wrote XScreenSaver is... uh... intense and highly opinionated, and I'm not sure users want to get a face full of that if they click the Help button.00:38
arraybolt3[m]This renders the button still helpful, but avoids pointing to that website. This is a matter of taste, so it really needs input from others who may have different ideas than I do about this.00:38
arraybolt3[m]Anyway, here's the file: https://termbin.com/bpiu00:38
lubot[matrix] <arraybolt3> If no one objects, I'd also like to have the XFlame screensaver disabled by default since it appears possibly offensive to some users (I noticed it the other day and did not like it).00:49
lubot[matrix] <arraybolt3> That would also be a change made to the XScreenSaver configuration file.00:49
* guiverc has never liked xflame either, but I've never seen it as offensive00:53
arraybolt3Again, it's just a matter of taste - if I don't like it, I'll just turn it off on my own system. I mention it since I think it might be helpful to others to have it off, but if that's not a good idea, no problem.00:54
* guiverc doesn't like flurry either (default), a couple of video cards I QA on 'glitch' with it & as I result I fear it looks 'buggy'...00:56
arraybolt3Heh, that happens to my systems too (particularly slower ones). I just chalked it up to the system's speed. But if we're rewriting the file anyway, we could disable it by default and switch to a different default. (Also, it looks like I may have accidentally made a change that caused arbitrary screen savers that were enabled to be selected, rather than defaulting to just one? I should00:57
arraybolt3definitely change that too.)00:57
guivercmaybe related to system speed; I do use a few core2duo00:58
arraybolt3If any Ubuntu distro is going to be used on a slow system, it will likely be Lubuntu, so slow speed problems are definitely a concern here.00:59
guivercSomeone chose that default (I have a bug report) feeling it was best for us.. I don't mind what it is though00:59
guiverchttps://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1855220  I think01:01
-ubot93:#lubuntu-devel- Launchpad bug 1855220 in xserver-xorg-video-nouveau (Ubuntu) "xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)" [Undecided, New]01:01
guivercHey thanks arraybolt3 for noticing that other xscreensaver bug & commenting....01:02
arraybolt3If we wanted a different one, I particularly like Beats, that might be a good default.01:02
arraybolt3(Noticed it in my email, glad to help! Also I just commented on the one you linked to.)01:03
guivercI think it was the "one you linked to" I just noted & caused me to comment01:03
arraybolt3OK, well since I accidentally regressed default behavior with this new file, I guess I'm retracting my request for approval since I need to fix what I broke :P01:16
lubot[matrix] <kc2bez> XD03:19
lubot[matrix] <kc2bez> Let me know when you want me to look at it again.03:19
lubot[matrix] <kc2bez> What you said above makes sense.03:19
lubot[matrix] <arraybolt3> Thanks :) Currently doing other stuff, but I'll revisit that soon.03:20
lubot[matrix] <kc2bez> No rush. I am heading horizontal here shortly. 4 am comes, uh, early.03:21
arraybolt3I said earlier I liked the Beats screensaver and that it might be good as a default, but I've noticed it also has some glitches in it, so that's probably not a good default option after all.08:29
lubot[telegram] <lynorian> I use matrix screensaver08:30
arraybolt3That's a pretty good one.08:31
arraybolt3XMatrix is a bit startling and the "SYSTEM FAILURE" message in it looks alarming, but GLMatrix is really nice IMO.08:32
lubot[matrix] <kc2bez> I use the black screen. That might be a little boring. :P09:05
lubot[matrix] <arraybolt3> I dunno, that's the same one all the other screensaverless flavors use, and it's the one I use on my main desktop to avoid it being too distracting.16:32
lubot[matrix] <arraybolt3> Maybe we should select some candidate, non-glitchy screensavers, and then vote on which one should be the default?16:33
lubot[matrix] <arraybolt3> Uno momento, switching Element Nightly to matrix.org and Element Web to lubuntu.me...16:40
lubot[matrix] <roberalz> Perfecto16:42
lubot[matrix] <arraybolt3> Bah, Nheko mangled my security key somehow, so I just had to reset it :(16:43
lubot[matrix] <arraybolt3> Thankfully I only had one encrypted chat that I lost, and it wasn't really important.16:44
arraybolt3[m]Well, bad news. PPA tests show that using a Breaks or Replaces line in apt does not convince it to install lubuntu-update-notifier first. It just keeps insisting on doing SDDM first.17:45
arraybolt3[m]I guess that was probably our last easy way out. I don't think we can have everyone who needs to replace a config file also add a lubuntu-update-notifier-workaround script to their packaging. And this isn't a regression in anything, it's just a bug being uncovered that we didn't know about before.17:47
arraybolt3[m]If no one else objects, I'll get the SRU for our fix into Kinetic, Jammy, and Focal, and then we'll see where we can go from there.17:48
* arraybolt3[m] needs to go afk again17:48
arraybolt3[m]Actually, I wonder if a preinst script would help here.17:53
arraybolt3[m]Yeah, preinst won't help here, the package won't be unpacked.17:58
Eickmeyer[m]arraybolt3: I can delay the SDDM SRU until a week after the lubuntu-update-notifier update gets released, hopefully giving people enough time.18:06
Eickmeyer[m]Can't guarantee other updates won't cause the bug to surface in the meantime, though.18:07
Eickmeyer[m]Just doing my part.18:07
arraybolt3[m]I think we should add a "fix a broken upgrade" feature to lubuntu-update-notifier before SRU-ing. That way:18:23
arraybolt3[m]1. The user attempts to update and breaks the system.18:23
arraybolt3[m]2. The user reboots trying to fix it.18:23
arraybolt3[m]3. The updater pops back up, fixes the broken update, and then everything works.18:24
arraybolt3[m]That way at least "turn it off and back on" will work.18:24
arraybolt3[m]The upgrader managed to unpack before SDDM configures and causes the problem, I believe, so it will be available on the next boot if all goes as expected.18:28
arraybolt3[m]Anyway, that's going to be my next test.18:52
arraybolt3[m]Alright, I have a working prototype. It ends up keeping the old version of /usr/share/sddm/scripts/Xsetup, which isn't quite what we want, BUT, it does allow the user to unbreak the system without the use of the command line in a fairly intuitive way.20:02
arraybolt3[m]The PPA with the fix is here: https://launchpad.net/~arraybolt3/+archive/ubuntu/lubuntu-upgrader-test2 (Warning to log readers, do not use this on a system you care about!)20:04
arraybolt3[m](It also displays no progress, and doesn't even allow the window to pop up until after it finishes fixing things, so it really needs help.)20:36
arraybolt3[m]I think all this needs now is GUI-ified, and then that's a working solution! Then we can SRU it and be done.22:44

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!