You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running ujust update > After it finished Flatpak System Packages checks I get this message:
── 16:28:05 - Flatpak System Packages ──────────────────────────────────────────
Looking for updates…
Nothing to do.
The application panicked (crashed).
Message: this user should exist
Location: src/steps/os/unix.rs:315
error: Recipe update failed with exit code 101
I know it finishes checking flatpak & I ran it with sudo which correctly updates everything (aside from a pip3 check which warns me about running as root, it did not update anything though)
From Sudo:
── 16:30:06 - Summary ──────────────────────────────────────────────────────────
System update: OK
distrobox: IGNORED
Firmware upgrades: OK
Flatpak: OK
pip3: OK
ClamAV Databases: OK
Mozilla GNOME Themes: OK
Third Party CSS Loader Themes: OK
What did you expect to happen?
I expected it to run correctly, maybe, asking a password instead of running the whole command with sudo since it ran correctly out of fresh install.
Output of rpm-ostree status
N/A
Hardware
Swift SF314-510G
Extra information or context
-> When running the update command, the code attempts to notify users about the update using the get_active_users() function in session.py
-> Function queries the systemd login manager (org.freedesktop.login1) for active user sessions
My user is properly registered; uid, Two active sessions (Sessions=3 2), proper path (/run/user/****, Active state)
The code in cli.py expects the data in a specific format & assumes there's always data in users["data"][0] .
Looking at the busctl output, while my user session exists, there might be an issue with how the code handles the returned data structure.
OR
Maybe I have a ublue-update package where its not properly handling certain user session states/data structure that causes a panic during user session verification, despite having valid active sessions???
The text was updated successfully, but these errors were encountered:
Describe the bug
After running
ujust update
> After it finished Flatpak System Packages checks I get this message:I know it finishes checking flatpak & I ran it with sudo which correctly updates everything (aside from a pip3 check which warns me about running as root, it did not update anything though)
From Sudo:
What did you expect to happen?
I expected it to run correctly, maybe, asking a password instead of running the whole command with
sudo
since it ran correctly out of fresh install.Output of
rpm-ostree status
Hardware
Swift SF314-510G
Extra information or context
-> When running the update command, the code attempts to notify users about the update using the
get_active_users()
function in session.py-> Function queries the systemd login manager (org.freedesktop.login1) for active user sessions
The code in cli.py expects the data in a specific format & assumes there's always data in
users["data"][0]
.Looking at the busctl output, while my user session exists, there might be an issue with how the code handles the returned data structure.
OR
Maybe I have a ublue-update package where its not properly handling certain user session states/data structure that causes a panic during user session verification, despite having valid active sessions???
The text was updated successfully, but these errors were encountered: