Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ujust update; application panicked #2214

Open
mijwimufi opened this issue Jan 31, 2025 · 0 comments
Open

ujust update; application panicked #2214

mijwimufi opened this issue Jan 31, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@mijwimufi
Copy link

Describe the bug

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???

@dosubot dosubot bot added the bug Something isn't working label Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant