we only really get the metadata refresh jank

K

Kamquat•1/4/24, 2:20 PM

Uhh

K

Kamquat•1/4/24, 2:20 PM

[fluffles@supernova]~$ ublue-update 
[2024-01-04 08:20:12,077] ublue_update.update_checks.system:INFO | No system update available.
Traceback (most recent call last):
  File "/usr/bin/ublue-update", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/lib/python3.12/site-packages/ublue_update/cli.py", line 238, in main
    hardware_inhibitor_checks_failed(
  File "/usr/lib/python3.12/site-packages/ublue_update/cli.py", line 86, in hardware_inhibitor_checks_failed
    raise Exception(f"update failed to pass checks: \n - {exception_log}")
Exception: update failed to pass checks: 
 - Battery less than 50.0%

[fluffles@supernova]~$ ublue-update 
[2024-01-04 08:20:12,077] ublue_update.update_checks.system:INFO | No system update available.
Traceback (most recent call last):
  File "/usr/bin/ublue-update", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/lib/python3.12/site-packages/ublue_update/cli.py", line 238, in main
    hardware_inhibitor_checks_failed(
  File "/usr/lib/python3.12/site-packages/ublue_update/cli.py", line 86, in hardware_inhibitor_checks_failed
    raise Exception(f"update failed to pass checks: \n - {exception_log}")
Exception: update failed to pass checks: 
 - Battery less than 50.0%

[fluffles@supernova]~$ ublue-update 
[2024-01-04 08:20:12,077] ublue_update.update_checks.system:INFO | No system update available.
Traceback (most recent call last):
  File "/usr/bin/ublue-update", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/lib/python3.12/site-packages/ublue_update/cli.py", line 238, in main
    hardware_inhibitor_checks_failed(
  File "/usr/lib/python3.12/site-packages/ublue_update/cli.py", line 86, in hardware_inhibitor_checks_failed
    raise Exception(f"update failed to pass checks: \n - {exception_log}")
Exception: update failed to pass checks: 
 - Battery less than 50.0%

[fluffles@supernova]~$ ublue-update 
[2024-01-04 08:20:12,077] ublue_update.update_checks.system:INFO | No system update available.
Traceback (most recent call last):
  File "/usr/bin/ublue-update", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/lib/python3.12/site-packages/ublue_update/cli.py", line 238, in main
    hardware_inhibitor_checks_failed(
  File "/usr/lib/python3.12/site-packages/ublue_update/cli.py", line 86, in hardware_inhibitor_checks_failed
    raise Exception(f"update failed to pass checks: \n - {exception_log}")
Exception: update failed to pass checks: 
 - Battery less than 50.0%

K

Kamquat•1/4/24, 2:20 PM

I'm on a desktop...

K

Kamquat•1/4/24, 2:20 PM

Battery?

K

Kamquat•1/4/24, 2:23 PM

are my updates broken or is this some other weirdness?

E

EyeCantCU•1/4/24, 2:26 PM

If you have a wireless mouse, psutil is likely polling it

K

Kamquat•1/4/24, 2:26 PM

I do, but both mouse and keyboard are above 90%

E

EyeCantCU•1/4/24, 2:31 PM

Hmm... I will look into it

EEyeCantCU Hmm... I will look into it

K

Kamquat•1/4/24, 2:34 PM

Thanks. If you need any info from me lmk. Interestingly, I rebooted, and ublue-update ran properly once, but then I ran it again, and the error happened once more.

KKamquat Thanks. If you need any info from me lmk. Interestingly, I rebooted, and ublue-u...

E

EyeCantCU•1/4/24, 2:37 PM

Definitely will. Thank you for letting us know

K

Kamquat•1/4/24, 2:38 PM

UUriyah Bazzite I had a million issues installing it to steam deck. So far loving naboro

D

dnkmmr•1/4/24, 3:02 PM

isn't nobaro steam deck version mutable?

Ddnkmmr isn't nobaro steam deck version mutable?

T

termdisc•1/4/24, 3:11 PM

yes

Ttermdisc yes

D

dnkmmr•1/4/24, 3:13 PM

that means if something went wrong with the update, the system may be unbootable

A

anoldguy•1/4/24, 3:14 PM

Sorry for the bother in advance. I see that installing on OLED means using a dock, but once installed and switched to :testing, is all of the hardware working? I read the issue in GH, and it's not clear if wifi is working after switching.

Ddnkmmr that means if something went wrong with the update, the system may be unbootable

T

termdisc•1/4/24, 3:14 PM

I wouldn't go as far as saying that

EEyeCantCU Definitely will. Thank you for letting us know

K

Kamquat•1/4/24, 3:24 PM

I've noticed that it seems to be time-based somehow. The top timestamp is a successful ublue-update run about 10 minutes after a fresh reboot. The second is just now.

[2024-01-04 08:51:04,935] ublue_update.cli:INFO | Running update script: /etc/ublue-update.d/user/99-bazzite-arch-user-update.sh
[fluffles@supernova]~$ ublue-update 
[2024-01-04 09:23:01,567] ublue_update.update_checks.system:INFO | No system update available.
Traceback (most recent call last):
  File "/usr/bin/ublue-update", line 8, in <module>

[2024-01-04 08:51:04,935] ublue_update.cli:INFO | Running update script: /etc/ublue-update.d/user/99-bazzite-arch-user-update.sh
[fluffles@supernova]~$ ublue-update 
[2024-01-04 09:23:01,567] ublue_update.update_checks.system:INFO | No system update available.
Traceback (most recent call last):
  File "/usr/bin/ublue-update", line 8, in <module>

[2024-01-04 08:51:04,935] ublue_update.cli:INFO | Running update script: /etc/ublue-update.d/user/99-bazzite-arch-user-update.sh
[fluffles@supernova]~$ ublue-update 
[2024-01-04 09:23:01,567] ublue_update.update_checks.system:INFO | No system update available.
Traceback (most recent call last):
  File "/usr/bin/ublue-update", line 8, in <module>

[2024-01-04 08:51:04,935] ublue_update.cli:INFO | Running update script: /etc/ublue-update.d/user/99-bazzite-arch-user-update.sh
[fluffles@supernova]~$ ublue-update 
[2024-01-04 09:23:01,567] ublue_update.update_checks.system:INFO | No system update available.
Traceback (most recent call last):
  File "/usr/bin/ublue-update", line 8, in <module>

KKamquat I've noticed that it seems to be time-based somehow. The top timestamp is a succ...

E

EyeCantCU•1/4/24, 3:37 PM

It's retriggered on failure. I think the issue is it sees it as a battery but it doesn't provide an ACPI path

E

EyeCantCU•1/4/24, 3:37 PM

There's an open fix but it hasn't been merged quite yet

K

Kamquat•1/4/24, 3:38 PM

Then it's got to be my logitech trackball and keyboard, cause that's the only battery-having things.

EEyeCantCU There's an open fix but it hasn't been merged quite yet

K

Kamquat•1/4/24, 3:38 PM

Ah okay. will updates working right after boot let me still get the update whenever it comes?

K

Kamquat•1/4/24, 3:38 PM

(I shut down at night, so I get a fresh boot daily)

E

EyeCantCU•1/4/24, 3:40 PM

Unfortunately I don't believe so. Will have to fix this by packaging psutil with the fix. In the meantime, ublue-update --force should do the trick

K

Kamquat•1/4/24, 3:40 PM

Okay. Thanks

K

Kamquat•1/4/24, 3:41 PM

I still haven't gotten an OS-image update since I installed (to my knowledge), but I've no idea how regular they are or aren't, and it'd only been a few days

EEyeCantCU Unfortunately I don't believe so. Will have to fix this by packaging psutil with...

K

Kamquat•1/4/24, 3:41 PM

Yep --force worked.

Jj0rge we only really get the metadata refresh jank

C

ChaiQi•1/4/24, 5:02 PM

What metadata refresh jank, exactly?

J

j0rgeOP•1/4/24, 5:06 PM

that spinner that sits there or, when you're browsing the store it immediately goes into refresh mode

Jj0rge that spinner that sits there or, when you're browsing the store it immediately g...

C

ChaiQi•1/4/24, 5:19 PM

Ahh. Yeah, the fact that it refreshes every 20 seconds or so is extremely problematic

C

ChaiQi•1/4/24, 5:24 PM

Is there any way to prevent that?

J

j0rgeOP•1/4/24, 5:39 PM

it's why remove the backends, it's way worse upstream. Someone needs to fix it or someone needs to make a flatpak-native package manager, part of the problem with older tools is they're designed to be pluggable with backends for a bunch of package management systems, etc.

J

j0rgeOP•1/4/24, 5:39 PM

there's no need for that any more

C

ChaiQi•1/4/24, 5:45 PM

Ah, hm

EEyeCantCU Unfortunately I don't believe so. Will have to fix this by packaging psutil with...

K

Kyle Gospo•1/4/24, 6:00 PM

Can you link me to that fix? I'm happy to do that

KKyle Gospo Can you link me to that fix? I'm happy to do that

E

EyeCantCU•1/4/24, 6:02 PM

That would be awesome! https://github.com/giampaolo/psutil/pull/2305

G

Geechan•1/4/24, 6:07 PM

Hey all, just have a quick question. Is it possible to enable the Steam gamescope session on the desktop build, or is it exclusive to the Deck builds? I would like to be able to have gamescope-session connect to my TV when I want to game on my desktop PC (for HDR, etc.), while also being able to use desktop mode the majority of the time. Also wondering if there's any caveats to running the deck build on a desktop setup (with AMD graphics).

I currently have this setup on Arch using gamescope-session-steam from the AUR, and it's working well for me.

GGeechan Hey all, just have a quick question. Is it possible to enable the Steam gamescop...

N

Noel•1/4/24, 6:14 PM

Someone can correct me if I'm wrong, but the main difference between the Deck build and the Desktop build is the desktop doesn't ship game scope. I believe you can run the deck version on a desktop if you want to (I tested it in a VM previously and it seemed to work fine)

NNoel Someone can correct me if I'm wrong, but the main difference between the Deck bu...

K

Kyle Gospo•1/4/24, 6:14 PM

gamescope ships (now), just not the session. Deck builds have gamescope session, autologin, and default to gamescope just as SteamOS does

K

Kyle Gospo•1/4/24, 6:15 PM

@Geechan Deck build on desktop is fine/supported, we consider that our HTPC package as well. That being said if you'd rather have control you can also just re-enable the bazzite repos in /etc/yum.repos.d/ and layer gamescope-session-plus and gamescope-session-steam

K

Kyle Gospo•1/4/24, 6:15 PM

that way you don't get the autologin stuff

G

Geechan•1/4/24, 6:16 PM

Good to know, thanks! That was the one thing that was concerning me moving over to Bazzite

G

Geechan•1/4/24, 6:17 PM

I'll likely layer on the packages then

K

Kamquat•1/4/24, 7:35 PM

So this came up - do I just reboot to apply the update?

[fluffles@supernova]~$ ublue-update --force
[2024-01-04 13:34:32,781] ublue_update.update_checks.system:INFO | System update available.

[fluffles@supernova]~$ ublue-update --force
[2024-01-04 13:34:32,781] ublue_update.update_checks.system:INFO | System update available.

[fluffles@supernova]~$ ublue-update --force
[2024-01-04 13:34:32,781] ublue_update.update_checks.system:INFO | System update available.

[fluffles@supernova]~$ ublue-update --force
[2024-01-04 13:34:32,781] ublue_update.update_checks.system:INFO | System update available.

K

Kamquat•1/4/24, 7:40 PM

Huh no, I rebooted, ublue-update still says update available. What do I need to do to get said update?

KKamquat So this came up - do I just reboot to apply the update? ```[fluffles@supernova]~...

K

Kyle Gospo•1/4/24, 7:48 PM

Rather than have you deal w/ --force to update

K

Kyle Gospo•1/4/24, 7:48 PM

I just patched the battery detection issue in the first place

K

Kyle Gospo•1/4/24, 7:48 PM

main is building now, when it's done (I can ping you)

K

Kyle Gospo•1/4/24, 7:48 PM

simply run

rpm-ostree update

rpm-ostree update

rpm-ostree update

rpm-ostree update

K

Kyle Gospo•1/4/24, 7:48 PM

and you won't have to worry about it anymore

K

Kyle Gospo•1/4/24, 7:48 PM

https://github.com/ublue-os/bazzite/actions/runs/7414094401

we only really get the metadata refresh jank

Similar Threads

Similar Threads

Similar Threads