[00:06] <isthis4real57468> tomreyn i appreciate your help...but a real person who is successfully running livepatch on a flavor would be nice to hear from to confirm...its empiric knowledge, not theoretical
[00:07] <tomreyn> isthis4real57468: that's cool. i only ran it on vanilla ubuntu for a while. as folks told you in #debian you shouldn't try to play mix and mojo with those distros, though, it wont work out,
 @HMollerCl [Here is the bug, check if it's the same or different https://bugs.launchpad.net/ …], Yes, that is the problem. I've been there before. in fact it is not a pcmanfm problem which is the best file manager for my needs having tried so many. It is not clear where this comes from
 If I knew it before I stayed with the 16.04 that was not affected by this crash
 Lubuntu 16.04 is out of support
 @aptghetto [Lubuntu 16.04 is out of support], yes I know. but sometimes it's better not to update if it works 😁
[09:32] <Phodoks> Hi
[17:31] <Chunkyz> What to eat
[17:31] <Chunkyz> Hmmm
[17:31] <diogenes_> pizza
[17:52] <gaston_> asd
[21:07] <jfdid> Hi.  Looking for help to prevent Lubuntu from going into sleep or suspend.  I've tried a lot of different things and have searched for hours!
[21:07] <wxl> what version?
[21:08] <jfdid> 19.xx - I'll dig it up here now
[21:09] <jfdid> Lubuntu 19.04
[21:11] <wxl> did you go through power management and make sure it's not set to sleep or suspend under certain conditions? https://manual.lubuntu.me/stable/3/3.2/3.2.12/power_management.html
[21:11] <jfdid> Yes, all three options are disabled.
[21:11] <wxl> and did you go through the power management settings in the screensaver and make sure it's disabled? https://manual.lubuntu.me/stable/3/3.2/3.2.20/screensaver.html
[21:13] <wxl> p.s. 19.04 is supported until january. 19.10 is out. go upgrade!
[21:14] <jfdid> I'm fairly sure I checked into the screensaver settings but I'll double check here.
[21:14] <jfdid> I'm running it as a server for home automation and worried the upgrade may break something...but I suppose I'll have to do it at some point, thanks!  I'll check the ss settings here right now.  thanks for your help thus far wxl
[21:16] <wxl> jfdid: we did test the upgrade and didn't see any obvious breakage. additionally, i can tell you from years of working on development in lubuntu, i've very rarely seen any sort of breakages at all. if anything, it's one particular package that gets rarely used and isn't a standard part of the install......
[21:18] <wxl> jfdid: one more thing— if you added anything to your install it's possible SOMETHING in there may have dragged along some additional power management nonsense with it. i doubt there's any logs of /what/ triggers power management events, but you might check `dmesg` and /var/log/syslog
[21:23] <jfdid> Ok, great.  I'll give it a shot once I get the power issue figured out.
[21:24] <jfdid> As for the screensaver,  it's been on Random Screen saver after 10 minutes.  Lock Screen is disabled.  Power Management is disabled
[21:27] <wxl> yeah then check the logs to see if you can find any info. that's super bizarre.
[21:28] <jfdid> They syslog mentioned the core CPU temps above threshold, clock throttled.  At the same <time>, it then says core temp/speed normal.  The box is in a closed cabinet, which may be getting a bit warm - wondering if maybe this would shut down the unit?
[21:29] <wxl> super bizarre meaning, i can't imagine what you would have added (in regular use) that would be controlling it. those are the only two mechanisms in lubuntu proper.
[21:30] <jfdid> Gotcha.  Yeah, I don't think I've added anything along those lines.  Just HomeAssistant and deCONZ, neither of which should affect power management.
[21:31] <wxl> i've seen shutdowns with overheating before, but that's also not suspend/sleep
[21:31] <wxl> yeah well it's remotely possible they have some weird dependency on something....
[21:32] <kc2bez> jfdid: over temps will shut the system down. depending on the BIOS it may be doing it there if a sensor alarm is triggered. but wxl is right, that wouldn't suspend.
[21:32] <wxl> if you got the system in a closed cabinet and the ambient temperature is pretty hot, that's a recipe for disaster
[21:33] <kc2bez> Linux is great but it can't fix your hardware.
[21:34] <jfdid> Haha, you bet.  I've never seen it go above 43°C but maybe something's running and ramping up.  Thanks for your assistance folks.  I'll run it with the door open for a few days and see if that's the issue.  Appreciate how quick you guys are.
[21:34] <wxl> well you CAN use it to keep CPUs cool by artificially limiting them
[21:35] <wxl> um 43°C is WAAAAAAAAAAAAAAY too hot
[21:36] <wxl> personally, i'd consider anything above 25°C or so to be a bad scene
[21:38] <jfdid> Interesting.  When I run "sensors" from the terminal, the Cores list High and Critical both at 105°C
[21:39] <jfdid> It's a fanless "raw media" box, not unlike an intel NUC.  https://shop.raw-media.ca/en/hardware/31-raw-mini-2-640206931212.html
[21:39] <wxl> that's not ambient temperature
[21:40] <jfdid> wxl: sorry, that's Core temp, not ambient temp in the cabinet
[21:41] <wxl> that case design is great, but only in the sense that it pulls the heat out away from the hardware and releases it into the environment.. but if the environment is close quarters, it will just affect the hardware
[21:42] <jfdid> For sure.  I'll give it a shot for a day or two.  Does that 105°C seem like a good cutoff for a CPU or should it be lowered?
[21:44] <wxl> usually the manufacturer will publish specifications.. i'd base it off of that
[21:44] <jfdid> copy that.  Thanks again.
[21:44] <wxl> see https://www.cputemper.com/maximum-and-normal-cpu-temperature/ for example
[21:45] <wxl> in general i'd say keep it below 60-70
[21:45] <wxl> when in doubt, keep it lower. the lower you keep it, the longer the cpu will last
[21:45] <wxl> that's all the more relevant if this is running non-stop