http://bugzilla.opensuse.org/show_bug.cgi?id=1165372 Bug ID: 1165372 Summary: Screen freezing, tearing and crashes on 24inch monitor (Intel HD 405 Braswell graphics card) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: HP OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: dextrocardiac@protonmail.com QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0 Build Identifier: I'm using an HP Notebook with 8GB of RAM, a quad core Intel Pentium N3710 CPU, and an integrated Intel HD Graphics 405 Braswell graphics card, with openSUSE Tumbleweed (kernel 5.5.6 at the time of writing) with KDE Plasma 5.18 (but was using KDE Plasma 5.17 when I first encountered the bug). Until about a month ago, I was using my laptop with an old 15 inch Acer monitor as the primary display (connected with VGA). This month, I bought a new 24 inch BenQ monitor, and plugged it into my laptop with an HDMI cable provided with the monitor. Right off the bat, I started facing issues. For starters, my mouse pointer would get stuck on the left side of the screen (only visually. I could still highlight and click stuff in that region. The pointer would just visually stay still there until I moved it away from the edge). I found the bug reported here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654. However, it seems like there was no proper fix for it. Secondly, I started getting random screen freezing when doing stuff like scrolling webpages or typing messages in Telegram Desktop (it'd freeze when an emoji suggestion was about to popup for the word I'd typed), etc. The screen would freeze for about 10 to 15 seconds before responding again. While this was somewhat manageable initially, it started becoming too common; And in some cases, it'd also cause my entire session to crash (it'd take me back to sddm's login screen). Things I've tried to resolve the issue: - Using a VGA cable: This solved the pointer getting stuck on the left edge issue. But the screen freezing and crash still persisted. - Switching the compositor's rendering back-end and scaling method: This somewhat reduced the occurrence of the freezing and crashes, but didn't entirely make it go away. - Switching to the xf86-video-intel package / Changing the driver "AccelMethod" to "sna": This again fixed the pointer getting stuck on the left edge issue, but introduced terrible screen tearing and flicker (and didn't fix the screen freezing and crashes either). - Switching to the xf86-video-intel package and configuring "DRI" and "TearFree": After setting "DRI" to "2", "TearFree" to "true", rendering back-end to Xrender and scaling method to "Smooth", my system became somewhat useable. However, the screen freezing became even worse (it'd freeze and never unfreeze. It wouldn't take me back to sddm either. I couldn't even access a TTY. A hard reboot was the only way out). - Using Wayland: Results were the same, if not worse. Screen freezing would occur even more often (even for simple things such as adjusting the volume from the panel). I'm sure this is an issue with my graphics card and driver and not my monitor, because I tried using my monitor with my laptop after installing Windows 10, and it worked perfectly. The issue only happens on Linux (regardless of the distro or DE) and it's the most noticeable on openSUSE (from what I'd tried. For example, I'd tried Manjaro, and the freezing and crashing was a little less frequent). This is the first bug report I've filed. So please let me know what other information is required. Reproducible: Always Steps to Reproduce: 1. Connect a 24 inch monitor with HDMI/VGA to a laptop with the Intel HD Graphics 405 Braswell graphics card. 2. Use any Linux distro with the modesetting/intel driver. Actual Results: Terrible screen freezing and crashes. Expected Results: No screen freezing or crashes. -- You are receiving this mail because: You are on the CC list for the bug.