 Probably more obedient.
 you also have 300lbs of bricks you have to lug around from the salt mines :P (re @tsimonq2: Nah, but I have a 100 lb Great Dane 😎)
 "LIGHT WEIGHT!" -Ronnie Coleman (re @teward001: you also have 300lbs of bricks you have to lug around from the salt mines :P)
 I'll be "in" shortly here- any word on the dailies?
 Lubuntu should have the lock screen option hard-disabled and Ubuntu Studio should have improvements across the live session including auto screen lock being disabled
 @tsimonq2: at 11:41 my time (and Steve's time), I got a ping (I was in bed/asleep): Eickmeyer: I've triggered builds of kubuntu, lubuntu, and ubuntustudio to pick up the new casper, in case that's useful for anyone to test before the time the daily builds would normally happen http://iso.qa.ubuntu.com/qatracker/milestones/446/builds
 Some general notes on the diff (and I may do some slight cleanup in an additional upload)...
 
 Suspend should not have that popup, perhaps by just running a "fake" xscreensaver process, or by substituting that binary altogether to just fake it. Maybe have a helpful pop-up saying "uh, yo, just so you know, suspend doesn't do any of that fancy locking stuff"
 
 All that KDE 4 stuff can be removed with fire (but I'll verify)
 
 As a side note, I'd really love to clean up some of those pop-ups regarding power management on bootup, to give users a cleaner UX. That could probably be done in casper too (only prompt about power management settings specifically on first actual boot/login, to direct users away from any option in power management that may trigger a screen lock on the live session)
 Thank you very much for that info (re @Eickmeyer: @tsimonq2: at 11:41 my time (and Steve's time), I got a ping (I was in bed/asleep): Eickmeyer: I've triggered builds of kubuntu, lubuntu, and ubuntustudio to pick up the new casper, in case that's useful for anyone to test before the time the daily builds would normally happen http://iso.qa.ubuntu.com/qatracker/milestones/446/builds)
 I didn't remove the KDE4 stuff, but I know that Steve wasn't too happy that you didn't put a MP in *before* doing an upload.
 But, ask for forgiveness and all..
 It was self-contained, straightforward, and obvious. This next cleanup will have an MP because there's an occasion to have an MP :)
 I mean, he committed the diff so nbd now.
 But I'm willing to concede that perhaps I'm not as used to procedure and stop gaps as I once was
 Right, I'll be on -release to respond soon
 That casper script has needed a good cleanup for ages!
 Glad to be of assistance on that front :)
 To be fair, the kf5-settings portion still works. (re @RikMills: That casper script has needed a good cleanup for ages!)
 Which is why it was not a high priority for me that kept getting forgot or pushed back (re @Eickmeyer: To be fair, the kf5-settings portion still works.)
 @RikMills Do those paths stay the same for KDE 6? Besides s/5/6/ ofc
 Considering those are arbitrary folders set as a result of appending $XDG_SETTINGS_DIRS...
 We can't trust that env var to be there that early
 There's not that huge of a difference between KF5 and KF6.
 It's a lot scarier looking than it is. The changes aren't that huge.
 Maybe. I have always thought that the settings path was a bit odd. So the switch could be a could good chance to make things more sensible (re @tsimonq2: @RikMills Do those paths stay the same for KDE 6? Besides s/5/6/ ofc)
 Could you please consult with/work with me to consult with the proper KDE people on that? Would be nice to write code that we don't have to touch again for a few years ;) (re @RikMills: Maybe. I have always thought that the settings path was a bit odd. So the switch could be a could good chance to make things more sensible)
 Steve was a bit irked that we weren't putting our settings in the same spot. (re @RikMills: Maybe. I have always thought that the settings path was a bit odd. So the switch could be a could good chance to make things more sensible)
 That's my hope, at least. In a world full of unicorns and rainbows, we would have no differences :P (re @Eickmeyer: There's not that huge of a difference between KF5 and KF6.)
 Sure, Though as that is a purely set extra path for us, and not KDE set, then how much KDE upstream can input is doubtful (re @Eickmeyer: Steve was a bit irked that we weren't putting our settings in the same spot.)
 The KDE devs learned their mistakes from KDE4 -> KDE 5. They don't want to repeat that. At least, that's what they told me. (re @tsimonq2: That's my hope, at least. In a world full of unicorns and rainbows, we would have no differences :P)
 But we can explore if there is a better way with them I guess
 In your opinion, what is the best avenue to do that in, and would you be willing to take the charge on some of that? (re @RikMills: But we can explore if there is a better way with them I guess)
 Perhaps. I may have to take a bit of a step back in the next few months, so can't commit right now
 No worries, I just want to be effective on where we're asking about it, it doesn't matter who does it as much :)
 OK. We can surely work it out. 24.04 will not likely have a huge amount of kf6 (if any if debian dither on doing it)
 Sounds good, thanks!
 I'll throw my next casper MP here
 @RikMills @Eickmeyer Votes on nuking?
 ```
 
 if [ -d /root/usr/share/kubuntu-default-settings/ ]; then
     echo "[Event]\nhideRestartNotifier=true" >> /root/usr/share/kubuntu-default-settings/kde4-profile/default/share/config/notificationhelper
 fi```
 That's not even the code anymore. You might want to pull.
 Different file altogether
 Steve redid that section.
 Ohhhhhhh
 scripts/casper-bottom/48kubuntu_disable_restart_notifications
 And that seems to be the only functional piece in the file :P
 I doubt it's even functional. 😅
 Let me clarify my question: Is there a KDE 5 equivalent that should be there?
 I don't believe so because the restart notifier is handled at the same level as the system (/var/lib/{somethingorother/can't remember})
 You know that thing that pops up that tells you a system restart is required? That's what that used to handle, and KF5 handles it differently.
 Ah, got it. Are you 100% sure?
 I'd like @RikMills to also chime-in. I'd want us to be in 100% agreement.
 Roger that :)
[15:24] <tsimonq2> So, this should solve the first part of my wishlist: echo -e "[General]\nenableIdlenessWatcher=false\nenableLidWatcher=false\nrunCheckLevel=1" | tee /home/$USERNAME/.config/lxqt/lxqt-powermanagement.conf
[15:24] <tsimonq2> (I have an appropriate mkdir command above it.)
[15:24] <tsimonq2> In English: for the LXQt Power Management settings on the live session, that disables the idleness watcher, the lid watcher, and disables that "hey configure me" prompt on boot.
[15:25] <tsimonq2> Now, for next cycle probably, I'd argue the UX should be switched on that. The user should be notified if there *is* a battery and the watcher is enabled. For users in live sessions, I could see how that would be unnecessary. Thoughts on that are welcome.
[15:26] <tsimonq2> Anyway, my next step is to look at that suspend option. What binary does it call, and can I just put a dummy Bash script in there?
[15:30] <tsimonq2> @Eickmeyer: Looks like the new daily haz old casper. Confirming, then respinning if that's the case.
[15:30] <Eickmeyer> tsimonq2: Yeah, that sounds about right, unfortunately. 
[15:31]  * Eickmeyer got hit with an upstream bugfix release
[15:32]  * tsimonq2 hits Eickmeyer upside the head with a major version release
[15:33] <Eickmeyer> tsimonq2: Denied: will have to wait until nn opens. XD
[15:34] <tsimonq2> XD
[21:32] <tsimonq2> Okay, so here's what we have:
[21:32] <tsimonq2> https://git.launchpad.net/casper/commit/?id=8673e870c4a99b33492e7a7d18816c23cb93be17
[21:32] -ubottu:#lubuntu-devel- Commit 8673e87 in casper "Pre-seed LXQt Power Management settings so the user is not prompted on the live session."
[21:32] <tsimonq2> https://git.launchpad.net/casper/commit/?id=0f2f09bcca5a6d7bb4896b5b14e38dc2c389ea4d
[21:32] -ubottu:#lubuntu-devel- Commit 0f2f09b in casper "Instead of calling xscreensaver in LXQt, call /usr/bin/true to avoid an error message."
[21:32] <tsimonq2> https://git.launchpad.net/casper/commit/?id=9a9c23b19bee0d50fbc81791cf12a21dadd1bdbb
[21:32] -ubottu:#lubuntu-devel- Commit 9a9c23b in casper "Make that section a bit prettier by putting the long path in $config."
[21:32] <tsimonq2> https://git.launchpad.net/casper/commit/?id=830ff1d71c900aacf45db7104a92bff0e9201f23
[21:32] -ubottu:#lubuntu-devel- Commit 830ff1d in casper "Upload to Mantic HEAD 1.485 main"
[21:32] <tsimonq2> I accidentally pushed to the casper repo because, as it turns out, *somehow* I have push access.
[21:32] <tsimonq2> I'm not a member of ~ubuntu-installer but I'm guessing that's an LP security bug.
[21:33] <tsimonq2> Anyway, vorlon told me to Just Upload It, and if he/someone else rejects it, they'll roll back the repo appropriately.
[21:33] <tsimonq2> So, now it's sitting in the queue.
[21:33] <tsimonq2> I think my next order of business is to figure out where that other dialog box comes from, and fix that UX.
[22:17] <tsimonq2> Alright, so I have a working patch to lxqt-powermanagement which only shows a message when the battery is actually present. @guiverc / wxl / etc. do you want to test?
[22:17] <tsimonq2> @wxl ^ XD
[22:19] <tsimonq2> If I don't hear anything in a day or two, I'll push it through. In the meantime, I'll ask upstream what they think (although I suspect they'll tell me to go die in a hole >:P).
[22:23] <tsimonq2> https://github.com/lxqt/lxqt-powermanagement/pull/382
[22:23] -ubottu:#lubuntu-devel- Pull 382 in lxqt/lxqt-powermanagement "Show a notification when the battery is present, not absent" [Open]