aednichols
aednichols
PostsComments
UBUniversal Blue
Created by aednichols on 5/29/2024 in #🛟bazzite-help
View update schedule
OK sweet, this led me to what I was looking for. Thanks! 
aednichols@spatium ~> systemctl status ublue-update
○ ublue-update.service - Universal Blue Update Oneshot Service
     Loaded: loaded (/usr/lib/systemd/system/ublue-update.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead) since Wed 2024-05-29 02:19:23 EDT; 2min 36s ago
TriggeredBy: ● ublue-update.timer
    Process: 221545 ExecStart=/usr/bin/ublue-update (code=exited, status=0/SUCCESS)
   Main PID: 221545 (code=exited, status=0/SUCCESS)
        CPU: 409ms

May 29 02:19:12 spatium systemd[1]: Starting ublue-update.service - Universal Blue Update Oneshot Service...
May 29 02:19:14 spatium ublue-update[221545]: [2024-05-29 02:19:14,333] ublue_update.update_checks.system:INFO | No system update available.
May 29 02:19:14 spatium ublue-update[221545]: [2024-05-29 02:19:14,333] ublue_update.update_inhibitors.hardware:INFO | System passed hardware checks
May 29 02:19:14 spatium ublue-update[221545]: [2024-05-29 02:19:14,334] ublue_update.cli:INFO | System passed all update checks
May 29 02:19:15 spatium ublue-update[221545]: [2024-05-29 02:19:15,663] ublue_update.cli:INFO | Running update for user: 'aednichols'
May 29 02:19:15 spatium sudo[221757]:     root : PWD=/ ; USER=aednichols ; ENV=DISPLAY=:0 XDG_RUNTIME_DIR=/run/user/1000 DBUS_SESSION_BUS_ADDRESS=unix:path=/ru>
May 29 02:19:23 spatium ublue-update[221545]: [2024-05-29 02:19:23,262] ublue_update.cli:INFO | System update complete
May 29 02:19:23 spatium systemd[1]: ublue-update.service: Deactivated successfully.
May 29 02:19:23 spatium systemd[1]: Finished ublue-update.service - Universal Blue Update Oneshot Service.
aednichols@spatium ~> systemctl status ublue-update
○ ublue-update.service - Universal Blue Update Oneshot Service
     Loaded: loaded (/usr/lib/systemd/system/ublue-update.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead) since Wed 2024-05-29 02:19:23 EDT; 2min 36s ago
TriggeredBy: ● ublue-update.timer
    Process: 221545 ExecStart=/usr/bin/ublue-update (code=exited, status=0/SUCCESS)
   Main PID: 221545 (code=exited, status=0/SUCCESS)
        CPU: 409ms

May 29 02:19:12 spatium systemd[1]: Starting ublue-update.service - Universal Blue Update Oneshot Service...
May 29 02:19:14 spatium ublue-update[221545]: [2024-05-29 02:19:14,333] ublue_update.update_checks.system:INFO | No system update available.
May 29 02:19:14 spatium ublue-update[221545]: [2024-05-29 02:19:14,333] ublue_update.update_inhibitors.hardware:INFO | System passed hardware checks
May 29 02:19:14 spatium ublue-update[221545]: [2024-05-29 02:19:14,334] ublue_update.cli:INFO | System passed all update checks
May 29 02:19:15 spatium ublue-update[221545]: [2024-05-29 02:19:15,663] ublue_update.cli:INFO | Running update for user: 'aednichols'
May 29 02:19:15 spatium sudo[221757]:     root : PWD=/ ; USER=aednichols ; ENV=DISPLAY=:0 XDG_RUNTIME_DIR=/run/user/1000 DBUS_SESSION_BUS_ADDRESS=unix:path=/ru>
May 29 02:19:23 spatium ublue-update[221545]: [2024-05-29 02:19:23,262] ublue_update.cli:INFO | System update complete
May 29 02:19:23 spatium systemd[1]: ublue-update.service: Deactivated successfully.
May 29 02:19:23 spatium systemd[1]: Finished ublue-update.service - Universal Blue Update Oneshot Service.
7 replies
UBUniversal Blue
Created by aednichols on 5/29/2024 in #🛟bazzite-help
View update schedule
I did start with the docs [0] 😄 but struck out [0] https://universal-blue.discourse.group/t/updates-rollback-and-rebasing-on-bazzite/36#desktop-images-4
7 replies
UBUniversal Blue
Created by aednichols on 5/29/2024 in #🛟bazzite-help
`ujust jetbrains-toolbox` on Bazzite?
Thanks!
10 replies
UBUniversal Blue
Created by aednichols on 5/29/2024 in #🛟bazzite-help
`ujust jetbrains-toolbox` on Bazzite?
But good to know where those scripts live for future reference
10 replies
UBUniversal Blue
Created by aednichols on 5/29/2024 in #🛟bazzite-help
`ujust jetbrains-toolbox` on Bazzite?
I just ended up installing it manually
10 replies
UBUniversal Blue
Created by aednichols on 5/29/2024 in #🛟bazzite-help
`ujust jetbrains-toolbox` on Bazzite?
Ah OK
10 replies
UBUniversal Blue
Created by kade on 4/23/2024 in #🛟bazzite-help
Slow boot times.
At least something very similar, yeah
106 replies
UBUniversal Blue
Created by kade on 4/23/2024 in #🛟bazzite-help
Slow boot times.
I thought I had fixed it but it came back
106 replies
UBUniversal Blue
Created by kade on 4/23/2024 in #🛟bazzite-help
Slow boot times.
And I'm on Gnome
106 replies
UBUniversal Blue
Created by kade on 4/23/2024 in #🛟bazzite-help
Slow boot times.
Seeing something very similar with ~25s firmware times. I can make it go away with a fresh install, but today I rebooted from Fedora 39 to 40 and it was back
106 replies
UBUniversal Blue
Created by kade on 4/23/2024 in #🛟bazzite-help
Slow boot times.
https://discord.com/channels/1072614816579063828/1229478191786098791/1231678147922100265
106 replies
UBUniversal Blue
Created by aednichols on 4/15/2024 in #🛟bazzite-help
Slow shutdown & boot
Same drive behaves totally normally now
26 replies
UBUniversal Blue
Created by aednichols on 4/15/2024 in #🛟bazzite-help
Slow shutdown & boot
I seemed to have fixed it through some combination of reinstalls, switching OS, and BIOS update
26 replies
UBUniversal Blue
Created by aednichols on 4/15/2024 in #🛟bazzite-help
Slow shutdown & boot
Win11 gets through BIOS basically instantly, it's something to do with the bootloader? Or secure boot?
26 replies
UBUniversal Blue
Created by aednichols on 4/15/2024 in #🛟bazzite-help
Slow shutdown & boot
Actually it seems tied to power. First boot after disconnecting power is fast. 
# systemd-analyze
Startup finished in 13.539s (firmware) + 2.353s (loader) + 1.935s (kernel) + 2.800s (initrd) + 7.564s (userspace) = 28.193s 
graphical.target reached after 7.531s in userspace.
# systemd-analyze
Startup finished in 13.539s (firmware) + 2.353s (loader) + 1.935s (kernel) + 2.800s (initrd) + 7.564s (userspace) = 28.193s 
graphical.target reached after 7.531s in userspace.
26 replies
UBUniversal Blue
Created by aednichols on 4/15/2024 in #🛟bazzite-help
Slow shutdown & boot
Also, the first boot after a CMOS clear is fast
26 replies
UBUniversal Blue
Created by aednichols on 4/15/2024 in #🛟bazzite-help
Slow shutdown & boot
# systemd-analyze
Startup finished in 1min 5.746s (firmware) + 2.342s (loader) + 1.783s (kernel) + 1min 6.431s (initrd) + 8.114s (userspace) = 2min 24.418s 
graphical.target reached after 8.084s in userspace.
# systemd-analyze
Startup finished in 1min 5.746s (firmware) + 2.342s (loader) + 1.783s (kernel) + 1min 6.431s (initrd) + 8.114s (userspace) = 2min 24.418s 
graphical.target reached after 8.084s in userspace.
26 replies
UBUniversal Blue
Created by aednichols on 4/15/2024 in #🛟bazzite-help
Slow shutdown & boot
$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @8.084s
└─multi-user.target @8.084s
  └─plymouth-quit-wait.service @6.019s +2.044s
    └─systemd-user-sessions.service @5.938s +62ms
      └─remote-fs.target @5.935s
        └─remote-fs-pre.target @3.120s
          └─nfs-client.target @3.120s
            └─gssproxy.service @3.108s +11ms
              └─network.target @3.094s
                └─wpa_supplicant.service @3.719s +5ms
                  └─basic.target @2.294s
                    └─dbus-broker.service @2.262s +30ms
                      └─dbus.socket @2.255s
                        └─sysinit.target @2.246s
                          └─systemd-update-utmp.service @2.217s +28ms
                            └─auditd.service @2.048s +131ms
                              └─systemd-tmpfiles-setup.service @1.792s +237ms
                                └─local-fs.target @1.763s
                                  └─usr-lib-waydroid.mount @2.704s
                                    └─dev-nvme0n1p3.device @584542y 2w 2d 20h 43.461s +1min 7.495s
$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @8.084s
└─multi-user.target @8.084s
  └─plymouth-quit-wait.service @6.019s +2.044s
    └─systemd-user-sessions.service @5.938s +62ms
      └─remote-fs.target @5.935s
        └─remote-fs-pre.target @3.120s
          └─nfs-client.target @3.120s
            └─gssproxy.service @3.108s +11ms
              └─network.target @3.094s
                └─wpa_supplicant.service @3.719s +5ms
                  └─basic.target @2.294s
                    └─dbus-broker.service @2.262s +30ms
                      └─dbus.socket @2.255s
                        └─sysinit.target @2.246s
                          └─systemd-update-utmp.service @2.217s +28ms
                            └─auditd.service @2.048s +131ms
                              └─systemd-tmpfiles-setup.service @1.792s +237ms
                                └─local-fs.target @1.763s
                                  └─usr-lib-waydroid.mount @2.704s
                                    └─dev-nvme0n1p3.device @584542y 2w 2d 20h 43.461s +1min 7.495s
26 replies
UBUniversal Blue
Created by aednichols on 4/15/2024 in #🛟bazzite-help
Slow shutdown & boot
Waiting for some parts to come in
26 replies
UBUniversal Blue
Created by aednichols on 4/15/2024 in #🛟bazzite-help
Slow shutdown & boot
I’ll give it another shot this weekend
26 replies