-
Notifications
You must be signed in to change notification settings - Fork 109
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 signal after DrmOutputManager
/DrmOutput
commits
#1124
Comments
Can confirm, same story on Mandriva. |
Since this seems GPU-specific, what GPU do you have? |
Radeon RX580 8GB, mesa 24.3.3 |
I am using an NVIDIA RTX 2070. I'm not entirely sure if this is the same issue, but I encounter a "No signal" problem when switching to tty and then returning to the desktop, or after the connection with the monitor is lost and then reconnected, when using only one monitor. In my case, I found that modifying the code below resolved the issue. If you are facing this problem, you might be able to alleviate it by either rolling back the version or modifying the code as shown below. src/backend/render/mod.rs: 569 let workspace_elements = workspace_elements(
// ...
);
if workspace_elements.is_err() {
return Ok(Vec::new());
}
let workspace_elements = workspace_elements?; From the |
This is a separate issue, can you open another issue please? |
Fixed by #1127. |
After
cosmic-comp
was updated from 9b78a2d to addcbc5, the display no longer received signal when running cosmic-comp, while TTYs still work.Plugging the HDMI cable into the motherboard, so that the iGPU is used, makes the compositor work as it should, with the monitor receiving a signal.
Happens on both Pop!_OS 24.04 and Fedora 41.
It's not related to any commits after 42af2af, so likely caused by #1020.
Logs:
Debug build:
comp-debug.log
Debug build with
RUST_BACKTRACE=1
:comp-backtrace.log
dmesg
logs (using these steps, but had to switch to a different TTY to killdmesg
):dmesg.log
System:
CPU: Intel i5 11400
GPU: AMD Radeon RX 570
Monitor: Asus VG245H
The text was updated successfully, but these errors were encountered: