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.

Sign up for GitHub

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

Jump to bottom

rebasing to older image broke rpm-ostree #1562

Open
randyoles opened this issue Aug 27, 2024 · 14 comments
Open

rebasing to older image broke rpm-ostree #1562

randyoles opened this issue Aug 27, 2024 · 14 comments
Labels
bug Something isn't working stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed

Comments

@randyoles
Copy link

Describe the bug

Rebased to an older image to try to troubleshoot a black screen issue by using older NVIDIA drivers. Then could no longer run any rpm-ostree commands due to daemon refusing to start.

GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer ‘org.projectatomic.rpmostree1’: startup job failed

What did you expect to happen?

I expected to rebase to an older image without losing ostree functionality

Output of rpm-ostree status

rpm-ostree status returns error message
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer ‘org.projectatomic.rpmostree1’: startup job failed
ran systemctl status rpm-ostreed.service
and got this;
pm-ostreed.service - rpm-ostree System Management Daemon
     Loaded: loaded (/usr/lib/systemd/system/rpm-ostreed.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: core-dump) since Tue 2024-08-27 13:33:06 PDT; 7min ago
       Docs: man:rpm-ostree(1)
    Process: 398605 ExecStart=rpm-ostree start-daemon (code=dumped, signal=ABRT)
   Main PID: 398605 (code=dumped, signal=ABRT)
        CPU: 49ms

Aug 27 13:33:05 bazzite systemd[1]: Starting rpm-ostreed.service - rpm-ostree System Management Daemon...
Aug 27 13:33:05 bazzite rpm-ostree[398605]: Reading config file '/etc/rpm-ostreed.conf'
Aug 27 13:33:05 bazzite rpm-ostree[398605]: **
Aug 27 13:33:05 bazzite rpm-ostree[398605]: rpm-ostreed:ERROR:src/libpriv/rpmostree-util.cxx:510:gboolean rpmostree_deployment_get_layered_info(OstreeRepo*, OstreeDeployment*, gboolean*, guint*, char**, char***>
Aug 27 13:33:05 bazzite rpm-ostree[398605]: Bail out! rpm-ostreed:ERROR:src/libpriv/rpmostree-util.cxx:510:gboolean rpmostree_deployment_get_layered_info(OstreeRepo*, OstreeDeployment*, gboolean*, guint*, char*>
Aug 27 13:33:06 bazzite systemd[1]: rpm-ostreed.service: Main process exited, code=dumped, status=6/ABRT
Aug 27 13:33:06 bazzite systemd[1]: rpm-ostreed.service: Failed with result 'core-dump'.
Aug 27 13:33:06 bazzite systemd[1]: Failed to start rpm-ostreed.service - rpm-ostree System Management Daemon.

Hardware

bazzite-nvidia:stable
Bazzite 40 (FROM Fedora Kinoite)
Linux 6.10.3-202.fsync.fc40.x86_64
AMD Ryzen 7 5700G (16) @ 5.29 GHz
NVIDIA GeForce RTX 3060 Lite Hash Rate [Discrete]
BTRFS file system

Extra information or context

No response
@dosubot dosubot bot added the bug Something isn't working label Aug 27, 2024
@KyleGospo
Copy link
Member

Are you able to select your previous image from GRUB?

@aarron-lee
Copy link
Contributor

hrm, I also have the same issue, can't manually rebase. let me try selecting the previous image from GRUB

image

@randyoles
Copy link
Author

randyoles commented Aug 27, 2024 via email

@KyleGospo
Copy link
Member

yeah, I was able to do that but I still need to be able to switch to an
older image to try to get an older Nvidia driver to see if that's what's
causing my black screen on boot.
And I can't because it will kill rpm-ostree without fixing the bug, or just
finding a workaround. And that is way beyond my noob level of tech skills

On Tue, Aug 27, 2024 at 2:16 PM Kyle Gospodnetich @.***>
wrote:

Are you able to select your previous image from GRUB?

—
Reply to this email directly, view it on GitHub
#1562 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BBN2IU47TMOU4DCMQ72J5GDZTTUBJAVCNFSM6AAAAABNG5BIR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJTGU4TGOJZGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

To be safe I would pin the working image now just in case. I will do some research and see if I can find what's going on here.

@aarron-lee
Copy link
Contributor

I can confirm that selecting the previous image via grub works fine.

I wonder if the issue could be related to rebasing to an older image without rechunk?

image

@randyoles
Copy link
Author

randyoles commented Aug 27, 2024 via email

@randyoles
Copy link
Author

randyoles commented Aug 27, 2024 via email

@KyleGospo
Copy link
Member

KyleGospo commented Aug 28, 2024 •
edited
Loading

coreos/rpm-ostree#5048

Same issue, should be fixed soon.

@KyleGospo
Copy link
Member

Now fixed in main and should be fixed in the next update. You'll need to update to the latest to restore rollback functionality.

@randyoles
Copy link
Author

Just rebased to the 40.20240828.0 image, and the rebased to the 40.20240815.0 image and it broke rpm-ostree again;
Loading sysroot: Failed to invoke RegisterClient: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.projectatomic.rpmostree1': startup job failed
going to reboot into my pinned image so I can rebase back to 8-28. Guess I just can't do any rollbacks further than the 8-21 image. Keeping that one pinned for a while.

@KyleGospo
Copy link
Member

KyleGospo commented Aug 29, 2024 •
edited
Loading

Confirmed in a VM that this is fixed, the problem is the version of rpm-ostree that was pushed upstream was creating images with a no-longer-required tag missing, and older versions of rpm-ostree require it. The fix upstream was to always make that tag, and that's in place here.

What needs to happen in your case is the image made without the tag needs to be removed. This can happen naturally by updating one more time, or by removing the old pins that didn't have this tag.

Sorry for the inconvenience, at least this is fully fixed upstream and can't happen again.

@randyoles
Copy link
Author

Sounds good,
went ahead and pinned 0.20240828.0 since it's working well, and unpinned 40.20240821.0. So after next update and a cleanup all should be good. :)
Thanks for getting this fixed so fast. Really appreciate it.
sidenote; This gave me time to figure out my kde blackscreen and get it fixed too. Turns out a typo in . bash_profile can really cause problems lol. Anyway I'm thrilled everything is working great again.
Thanks again

@castrojo
Copy link
Member

This is the kind of awesomeness that ends up on a slide someday!

@dosubot DosuBot
Copy link

dosubot bot commented Nov 29, 2024

Hi, @randyoles. I'm Dosu, and I'm helping the bazzite team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You experienced failures with rpm-ostree commands after rebasing to an older image to troubleshoot NVIDIA driver issues.
  • The rpm-ostreed.service was failing with a core dump, linked to a failure to activate the remote peer.
  • @KyleGospo and @aarron-lee suggested checking previous images via GRUB, and a related issue in rpm-ostree was identified and fixed upstream.
  • You confirmed that pinning a working image and updating resolved the issue.
  • A separate black screen issue was resolved by correcting a typo in your .bash_profile.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of the bazzite repository by commenting on this issue.
  • If there is no further activity, this issue will be automatically closed in 14 days.

Thank you for your understanding and contribution!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@castrojo @aarron-lee @KyleGospo @randyoles