Timeline for X is misrendering a rectangle around my mouse pointer
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2021 at 6:34 | answer | added | Dorian Gaensslen | timeline score: 1 | |
| Aug 28, 2019 at 1:51 | answer | added | Hans | timeline score: 2 | |
| Sep 12, 2018 at 12:29 | answer | added | RedEyed | timeline score: 3 | |
| Nov 23, 2017 at 22:00 | vote | accept | Mark Dominus | ||
| Nov 23, 2017 at 21:59 | answer | added | Mark Dominus | timeline score: 1 | |
| Nov 23, 2017 at 16:05 | answer | added | int_ua | timeline score: 1 | |
| Sep 23, 2017 at 15:02 | comment | added | dirkt | I have no idea. I'd suppose one could check the ChangeLog/git log etc. to find out why they disabled rotation, and if it would be harmful to "unpatch" it. | |
| Sep 23, 2017 at 14:16 | comment | added | Mark Dominus | @dirkt I switched to the Nvidia driver because the driver I had been using doesn't support rotated displays. I found this claim that Canonical patches X to disable display rotation and this is why I switched to the proprietary driver in the first place. Do you happen to know if the Canonical build of Nouveau removes rotation support? If it does I suppose I could use a non-Canonical build. | |
| Sep 22, 2017 at 22:04 | comment | added | M J | @dirkt you are correct, I switched from nvidia driver to nouveau driver and the issue is gone. | |
| Sep 19, 2017 at 14:02 | comment | added | dirkt | From what I've understood from the link to the bugreport, it seems to be a bug in the Nvidia driver, and initializing the driver twice (by restarting the DM) causes a different code path and/or non-idempotent hardware behaviour to fix it. As the Nvidia driver is closed source, we'll never know what exactly the fault is. You can test the theory that it's the Nvidia driver by (temporarlily) switching to the open-source nouveau driver: If the problem is gone, it was the Nvidia driver. | |
| Sep 19, 2017 at 13:52 | comment | added | Mark Dominus |
@dirkt I still don't understand which component is at fault, or why restarting sddm fixes it.
|
|
| Sep 19, 2017 at 5:53 | comment | added | dirkt | Mark Dominus: Turn that into an answer and accept it? | |
| Sep 18, 2017 at 19:33 | history | edited | Mark Dominus | CC BY-SA 3.0 |
addnedum about sddm and add [sddm] tag
|
| Sep 18, 2017 at 19:25 | comment | added | Mark Dominus |
Seems relevant: askubuntu.com/questions/947375/… . The workaround suggested there works for me: run sudo systemctl restart sddm from a console fixes the problem.
|
|
| Sep 18, 2017 at 19:00 | comment | added | Mark Dominus |
@dirkt I think I'm using the Nvidia card for display; the ServerLayout of my xorg.conf file has Screen 0 "nvidia" and Inactive "intel", and Xorg.0.log contains messages that appear to come from the NVIDIA driver. I tried adding Option "SWCursor" "on" and then also Optoin "HWCursor" "off" to the Screen "nvidia" section of my xorg.conf file, with no obvious effect. The Xorg.0.log file indicates that the options are being read and recognized.
|
|
| Sep 17, 2017 at 13:11 | comment | added | dirkt |
Are you using the Intel or the Nvidia card for display? Have you tried switching between software and hardware cursor rendering using xorg.conf?
|
|
| Sep 16, 2017 at 14:01 | history | edited | Mark Dominus | CC BY-SA 3.0 |
added 77 characters in body
|
| Sep 16, 2017 at 13:56 | history | asked | Mark Dominus | CC BY-SA 3.0 |