3 ms·
My setup: * 3 monitors * 1x 2560x1440@60Hz * 2x 1920x1200@75Hz * X99 - Broadwell chip * Fedora Workstation 38/39 * GTX 1070 *
by mroche 3y ago
My setup:
* 3 monitors
* 1x 2560x1440@60Hz
* 2x 1920x1200@75Hz
* X99 - Broadwell chip
* Fedora Workstation 38/39
* GTX 1070
* Driver 545 from RPM Fusion
* Currently on 545.29.06
Workloads:
* Excessive terminal use
* Code authoring (VSCode/Vim)
* Web browsing/app usage in Firefox/Google Chrome
* Screen sharing and recording (browser/OBS)
* Electron apps including Slack, Element, and Discord
* Occasional use of Krita^
^ Krita has a known issue with (X)Wayland, canvas acceleration, and tablet input.
I decided to give Wayland on my workstation another go when the 545 series dropped. Hilariously, the main reason being the underlying features added that enabled support for GNOME's Night Light feature.
Other than the first day of going through my apps and making sure things worked, I haven't had any real issues. For the work I do, Wayland more than covers my needs.
I have gotten a smidgen of cursor glitching after upgrading from the released 545.09.02 NFB driver to the beta-NFB 545.09.06 version. It only happens when GNOME switches to its "loading" cursor, but it's mostly been ironed out by now. I updated the driver as part of the system upgrade from Fedora 38 to 39, so that probably had a hand in causing it.
- neurostimulant 3y agoOn my nvidia system (gtx a2000) with an ultra wide monitor and Gnome, Chrome seems to be glitching if I do the following. - open a new Chrome window - snap the new window to fill half the screen by dragging it to either left or right edge of the screen - result: solitaire-like window glitches - if I resize the window a bit before snapping it, it works. I haven't seen this glitch on any other app.
- mroche 3y agoCan't say I've seen that one. I have seen Chrome have some windowing issues, but nothing that would drive me crazy. I've also added "--gtk-version=4" to my launcher to support alternate inputs (e.g. typing booster).