[07:15] <seb128> nicolasbock, could be the same as bug #1988315
[07:15] <seb128> nicolasbock, did you report the issue?
[11:24] <jbicha> seb128: we figured out in #ubuntu-next that things don't work well if you are using third party PPAs that modify gnome-settings-daemon etc. Getting rid of the PPAs fixed nicolas's issue
[12:01] <seb128> jbicha, hum, probably not the issue for Ken though
[12:02] <jbicha> yeah, Daniel's theory is that one of Ken's other extensions might be interfering
[12:04] <seb128> jbicha, but Ken said he had no custom extension enabled
[12:04] <seb128> only stock Ubuntu session it seems
[12:05] <jbicha> that's probably true. gsettings said he had more extensions but they likely wouldn't have been enabled because they wouldn't have had 43 in their metadata.json
[15:26] <doko> in kinetic, I'm trying to set the screen blank time from 5min to 15min, however the new value is never saved. switch to another config setting, and going back to "Power", the old value is shown again
[15:37] <jbicha> doko: that's a known gnome-control-center bug that will be fixed in 43~rc expected next week. bug 1988087
[16:05] <ogra> is the slution to get a second screen ?
[18:21] <genii> I'm on Bionic, exfatfsck version is 1.2.8, 1.3.0 onwards limited repair was introduced, should I try to compile the source from for instance Focal, or maybe a backport is already in the works
[19:14] <genii> ..well, for what it's worth, Focal's source package for exfat-utils-1.3.0-1ubuntu1 compiled and runs ok for me here on Bionic although of course lintian didn't like the resulting deb for various reasons
[19:17] <sarnold> lintian always has lots of opinions :)
[19:19] <genii> hah
[19:19]  * genii shoves the entire coffeepot in teward's direction
[19:20] <teward> *mass consumption of coffee consumes*
[19:21] <teward> anyone on the SRU team around to drop something into -proposed and review the SRU (first phase)?  Trying to fix torbrowser-launcher in Universe since it's been broken since Jammy thanks to Python 3.10 Strict Type Checking in commands.
[19:30] <rbasak> teward: isn't Browser window width/height really important for Tor users to remain anonymous?
[19:30] <teward> rbasak: yes, but the problem here is that the system pre python3.10 was working on implicit type casting
[19:31] <teward> i.e. if argument type is int, and given a float, it'll typecast it automatically.
[19:31] <teward> rbasak: the change here is just to use integer division prior to passing it in (the system already divides height/width by 2 or such) so it's an int being passed in instead of a float
[19:31] <teward> otherwise it's identical behavior where it'd be a lossy cast from float -> int
[19:32] <teward> you're right it's important for the anonymity but the launcher itself can't execute with the strict type checking in place
[19:32] <teward> so this was the (simplest) workaround that would work with the upstream code.
[19:32] <teward> and it looksl ike upstream doens't care but packagers should.
[19:34] <teward> my understanding of the code here is that it does basically the same thing - lossy conversion from a float to an int, retaining the same division/numbers in the launcher's init.
[19:34] <teward> but doing so by explicitly doing integer division to return an integer object to pass into gui.move() instead of a float
[19:34] <teward> in order to get around the strict type checking
[20:48] <rbasak> Sorry for the delay. I was in a meeting. Accepted now. Thanks!
[20:50] <nicolasbock> seb128: Yes it's fixed now. As jbicha said it was a rogue PPA :)
[21:49] <teward> rbasak: no worries :)
[21:49] <teward> rbasak: thank you kindly for the accept.  i tried to make sure this patch was as minimal as possible and as close to what pre-py3.10 was (implicit type casting vs. strict types)
[21:50] <teward> there's a lot of things that've broken with python 3.10 - old python versions and such break things when they introduce major changes.  Universe doesn't get the attention that Main does though :)
[23:15] <RikMills> bdmurray: hi. how do I get to the crash trace for this? https://errors.ubuntu.com/oops/8bd96e8c-2540-11ed-97b9-fa163e993415
[23:21] <bdmurray> RikMills: Is this from a system under your control?
[23:22] <bdmurray> I ask as the oops you've pointed at doesn't look right
[23:22] <RikMills> bdmurray: no, it is popey's
[23:23] <RikMills> he had a crash when holding down volume key in KDE and that is all he could give me
[23:25] <bdmurray> RikMills: I'd expect to see a Problem key linking to a bucket in the Error Tracker we can see an example of this here https://errors.ubuntu.com/oops/c3fede20-2a40-11ed-a628-fa163e55efd0
[23:25] <sarnold> that's much more like what I expected to see
[23:26] <RikMills> yeah, I was confused there was no way to the problem
[23:27] <RikMills> glad to know it is not me being dumb ;)
[23:27] <bdmurray> My guess would be that something happend to the core file
[23:29] <sarnold> none of the crashes from that system that I've looked at have a problem link
[23:29] <RikMills> ok, I guess we have to see if it happens again and hope for a better result?
[23:29] <bdmurray> or ask for the .crash file from the system to sort out what's going on
[23:31] <RikMills> ok, it is late here in the UK, so I think anything like that will need to wait until tomorrow. Thanks!