[Bug 1215404] New: SDDM displays blank screen with 100% CPU load or corrupt screen
https://bugzilla.suse.com/show_bug.cgi?id=1215404 Bug ID: 1215404 Summary: SDDM displays blank screen with 100% CPU load or corrupt screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs@suse.de Reporter: ilgaz@ilgaz.gen.tr QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869556 --> https://bugzilla.suse.com/attachment.cgi?id=869556&action=edit journalctl -b while SDDM displaying corrupt screen. I used SDDM here with my nouveau (mcp79, nv9400) for years on this Macbook 5.1 . I started seeing corrupt fonts (totally unreadable) or 100% CPU load from sddm-greeter with black screen. I am attaching output of journalctl -b taken when it was happening. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215404 https://bugzilla.suse.com/show_bug.cgi?id=1215404#c1 Ilgaz Öcal <ilgaz@ilgaz.gen.tr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ilgaz@ilgaz.gen.tr --- Comment #1 from Ilgaz Öcal <ilgaz@ilgaz.gen.tr> --- Created attachment 869557 --> https://bugzilla.suse.com/attachment.cgi?id=869557&action=edit Photo of screen with corrupt SDDM display. I could only use my phone to take photo of this issue. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1215404 https://bugzilla.suse.com/show_bug.cgi?id=1215404#c2 Ilgaz Öcal <ilgaz@ilgaz.gen.tr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Ilgaz Öcal <ilgaz@ilgaz.gen.tr> --- This seems to have been fixed with the recent updates. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com