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

no video signal on wake from suspend #1904

Open
craigers521 opened this issue Nov 21, 2024 · 3 comments
Open

no video signal on wake from suspend #1904

craigers521 opened this issue Nov 21, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@craigers521
Copy link

Describe the bug

After computer goes into suspend mode, if i attempt to wake with keyboard, mouse, or power button i can see fans and rgb come on and the monitor will wake as well but then it displays no video signal from device. This is true on multiple monitors. Ive tried power cycling monitors, input cycling, replugging DP cables. Theres nothing i can do to bring video online except to fully reboot the pc. This started happening around the version 41 release and can confirm it happens on 41.20241104 as well as 41.20241118.2

What did you expect to happen?

Video outputs normally on wake from suspend

Output of rpm-ostree status

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:a8da15feeaa1389d90769bd319ef0c3e5206b1875833099b8569060a95736ed3
                  Version: 41.20241118.2 (2024-11-19T02:53:11Z)
            LocalPackages: lact-libadwaita-0.6.0-0.x86_64

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:7d1de5a7a0fa9cd05fdd43609d7fe8af5de6cf60e53c698189c3eaf0fc2c7bf2
                  Version: 41.20241104 (2024-11-04T04:57:36Z)
            LocalPackages: lact-libadwaita-0.5.6-0.x86_64

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:ac9bdf25aa1095aa12296f7fa958286e8d3f993ef4a9d9406fd29563a76e7dce
                  Version: 40.20241014 (2024-10-15T08:55:05Z)
            LocalPackages: lact-libadwaita-0.5.6-0.x86_64
                   Pinned: yes

Hardware

Image

Extra information or context

tried to add MUTTER_DEBUG_FORCE_KMS_MODE=simple to /etc/environment based on forum post i found but that didnt work.

@dosubot dosubot bot added the bug Something isn't working label Nov 21, 2024
@evrowe
Copy link

evrowe commented Nov 27, 2024

I have intermittently experienced the same exact issue. The issue started for me on 41.20241104, but it was so pronounced/frequent on 41.20241125: Stable, I had to roll back to 41.20241119.

Output of rpm-ostree status

➜ rpm-ostree status
State: idle
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
                   Digest: sha256:6983413a64089ba365765c4da1e6b167230b97b61d2c884acfa9fc8e580e7f23
                  Version: 41.20241125 (2024-11-26T03:52:52Z)
            SecAdvisories: 1 moderate
                     Diff: 134 upgraded, 2 removed, 5 added
          LayeredPackages: goverlay p7zip-gui powerline-fonts shairport-sync sunshine zsh
            LocalPackages: 1password-8.10.48-1.x86_64 vesktop-1.5.3-1.x86_64

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
                   Digest: sha256:f6a55e7e3450f7f49c557db899f8e365dfc1b32fd60c5451cdadfe29794cf47f
                  Version: 41.20241118.2 (2024-11-19T02:58:00Z)
          LayeredPackages: goverlay powerline-fonts shairport-sync sunshine zsh
            LocalPackages: 1password-8.10.48-1.x86_64 vesktop-1.5.3-1.x86_64

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
                   Digest: sha256:6983413a64089ba365765c4da1e6b167230b97b61d2c884acfa9fc8e580e7f23
                  Version: 41.20241125 (2024-11-26T03:52:52Z)
          LayeredPackages: goverlay powerline-fonts shairport-sync sunshine zsh
            LocalPackages: 1password-8.10.48-1.x86_64 vesktop-1.5.3-1.x86_64

Hardware

Image

@craigers521
Copy link
Author

craigers521 commented Nov 27, 2024

Interesting @evrowe, that you are experiencing similar behavior on KDE Plasma and Nvidia as I am with gnome and Radeon. Definitely smells like a Wayland issue. They pulled X out of gnome at this point so I'd have to roll way back. It's mostly just a minor annoyance but I would love to see it fixed. Probably gonna have to come from upstream tho.

@evrowe
Copy link

evrowe commented Dec 12, 2024

Issue seems resolved for me as of 41.20241210; must have been an issue upstream

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

2 participants