[18:32] <zurn> Hi, the other day it was recommended to me to upgrade my Ubuntu Studio 18.04 to the new 20.04 to resolve some pulse->jack bridge issues I've been having...just noticing that it says not to do so until 20.04.01 comes out in July - is there a risk of doing the upgrade now?
[18:34] <Eickmeyer> zurn: Just like with any free operating system, everything is at your own risk. You can either wait until 20.04.1 or you can run "sudo do-release-upgrade -d" in a terminal or alt-F2, "update-manager -d" now to upgrade if you wish. Considering 20.04 is stable, you should be OK.
[18:34] <zurn> Oh good... cause I've already started!
[18:34] <Eickmeyer> Also, "It says" is something I likely wrote. :)
[18:35]  * Eickmeyer goes grocery shopping
[18:35] <zurn> and for that I salute you
[18:35] <zurn> you guys are truly amazing
[21:19] <genii> Working on a friend's laptop which he just installed Ubuntu Studio 20.04 on. Cleared up some other isseues already ( screen tearing and inactive Elantech touchpad buttons). But it has this other annoying bug I can't seem to get to the bottom of yet, after inactivity whenever it goes into some other state ( not sure if lock/sleep/whatever), the screen remaqins the same, there ins no screensaver or lock screen,e tc but then there is only cursor
[21:19] <genii> movement and hovering/clicking/ etc go totally dead. The only current solution is ctrl-alt-f1 and restarting lightdm. Machine is an ASUS X555DA with AMD A10-8700 and Carrizo GPU, Latest HWE kernel and amdgpu installed
[21:19] <PLC> hi' there :)
[21:20] <Eickmeyer> genii: I'd check with #xubuntu on that, there's nothing that we have configured in regards to the screensaver that they didn't configure.
[21:21] <genii> Eickmeyer: I asked around because of the XFCE comman backend, but no good leads yet. light-locker is not installed, etc
[21:22] <Eickmeyer> genii: Right, xfce4-screensaver replaced light-locker in 19.04 and later.
[21:22] <genii> I have all the things I can possibly turn off as far as DPMS, powersaving, etc
[21:23] <Eickmeyer> genii: Could also be completely hardware related, i.e. no two ACPI interfaces are exactly alike.
[21:23] <Eickmeyer> genii: Could also be the video driver.
[21:24] <genii> ..I am starting to lean in that direction, some wonky AMD ACPI implementaion maybe
[21:24] <Eickmeyer> That's very possible. I had that problem with my AMD machine in 19.04 and had to disable the power manager when every other DE worked fine.
[21:25] <Eickmeyer> No issues with 20.04 however.
[21:25] <genii> Eickmeyer: I upgraded the driver to latest PPA, disabled compistiing, made sure DRI3 and GLX/Mesa are running fine, etc
[21:25] <genii> *compositing
[21:26] <genii> ...Yeh, Kubuntu Focal and Groovy both ran fine off liveUSB
[21:26] <Eickmeyer> Yeah, that means nothing if it's a funky ACPI. There *might* be a kernel parameter that needs to be added to the command line in grub, but I don't remember off the top of my head what that might be.
[21:26] <Eickmeyer> acpi_osi=linux or something like that.
[21:26] <genii> Hm, OK. Guess I'll just keep poking at it with a stick
[21:28] <Eickmeyer> genii: That's what I would do. Sorry I couldn't have been better assistance. There are several reasons why we're moving to KDE Plasma with 20.10, and funky power management issues are one of them.
[21:31]  * genii goes back to the stick-pokings
[21:32] <Eickmeyer> Hehe, good luck, genii
[21:32] <genii> Thanks :) I'll kepp you posted if something works
[21:33] <OvenWerks> genii: given that other DEs work for you, have you thought of installing Studio on top of one of those DEs with ubuntustudio-installer?
[21:33] <Eickmeyer> !ubuntustudio-installer
[21:36] <genii> OvenWerks: He's used to the regular version so I don't want to have to coach him through some new interface... plus I'd rather actually get to the bottom of the real issue and solve it
[21:38] <OvenWerks> ok
[23:57] <genii> Got it
[23:58] <genii> ..turns out to be a combination of:  acpi_osi=1 acpi_osi='Windows 2010' tsc=unstable clocksource=hpet
[23:58] <genii> ..for future reference