[Bug 1220043] New: X dies when using Prism Launcher, sometimes disabling user input entirely.
https://bugzilla.suse.com/show_bug.cgi?id=1220043 Bug ID: 1220043 Summary: X dies when using Prism Launcher, sometimes disabling user input entirely. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: X.Org Assignee: gfx-bugs@suse.de Reporter: rokejulianlockhart+1674683091@outlook.com QA Contact: gfx-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Per https://forums.opensuse.org/t/where-to-report-xwayland-crash-the-cause-matte..., I've had two different types of results after a crash of X, albeit always caused when playing *Minecraft: Java Edition* via https://flathub.org/apps/org.prismlauncher.PrismLauncher, whereby Minecraft slowly becomes laggier, and eventually crashes: 1. The game became progressively slower, to the point where the game-reported 75 FPS felt like barely 30; 2. Common: 1. Firstly, the display freezes. Soon after, it becomes black. Then, the PC fans momentarily cease to operate, and the display becomes artefacted as the fans resume. 2. Although the system responds (Alt+SysReq+B performs systemctl reboot) Alt+F3 doesn't switch from the display server to a TTY. journalctl --boot=-1 -e produces the log posted to https://github.com/PrismLauncher/PrismLauncher/issues/2139#issue-2141081956. 2. Uncommon: 1. The X server actually crashed (see the last line of the log at Forge 1.19.2 Server Log [#H1b3oft] - mclo.gs). 2. Discord and Prism became 10% opacity. 3. When I logged-out, I remained in TTY3 rather than TTY2, and switching manually to TTY2 demonstrated that the handover hadn’t occurred. I had to use TTY4 to systemctl reboot. This doesn't occur on my brother's installation of Windows 11. In fact, I know of solely one *potential* report by anyone else of this. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1220043
roke beedell
https://bugzilla.suse.com/show_bug.cgi?id=1220043
https://bugzilla.suse.com/show_bug.cgi?id=1220043#c7
--- Comment #7 from roke beedell
Ok. I can understand that you switched to another distribution with such issues. Feel free to reopen in case you try TW again and can still reproduce the issue. Thanks for you feedback! Closing as "NORESPONSE" ...
For posterity, I'd like to note that this continues in a vaguely lesser state with Fedora 40. There might be a few notifications on this issue as I edit it slightly so that I can collate this with other reports at disparate places to ascertain what the commonalities are that cause it to arise. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1220043
roke beedell
https://bugzilla.suse.com/show_bug.cgi?id=1220043
roke beedell
https://bugzilla.suse.com/show_bug.cgi?id=1220043
roke beedell
https://bugzilla.suse.com/show_bug.cgi?id=1220043
https://bugzilla.suse.com/show_bug.cgi?id=1220043#c8
--- Comment #8 from roke beedell
https://bugzilla.suse.com/show_bug.cgi?id=1220043
https://bugzilla.suse.com/show_bug.cgi?id=1220043#c9
--- Comment #9 from roke beedell
https://bugzilla.suse.com/show_bug.cgi?id=1220043
roke beedell
https://bugzilla.suse.com/show_bug.cgi?id=1220043
roke beedell
https://bugzilla.suse.com/show_bug.cgi?id=1220043
roke beedell
participants (1)
-
bugzilla_noreply＠suse.com