I was trying to troubleshoot an issue where screen was not updating properly and it involved mucking around with display driver and changing settings. I don't recall exactly what I did but it fixed the issue and everything was great.

But now today I got on my computer and the GUI is horribly unresponsive. When I click on something I have to click several times before it registers the click, something as simple as clicking a new tab in firefox requires a lot of effort for it to open or close. Even keyboard keys I have to randomly hit some more than once before they register. It's horrible.

OS is Linux Mint 17.1 KDE. How do I get this back to normal? I'm on Nvidia driver 340. I tried using 352 but the issue is even worse. Also at random when system boots it boots VERY VERY VERY VERY VERY slow, like, I can watch each pixel line draw. When it does this, it also goes to a different login screen than normal. Please help, thanks!

After a bunch of reboots it *seems* to be gone, but I don't know, next reboot it will probably be back.

Contemplating another distro, I probably need to clean install this one given how much of a mess it is with all these issues. What's a good desktop distro now days? I want to go to something more standard, everytime I try to google for help none of the stuff I find applies because I end up not finding a file or GUI option etc.

As a side note when the GUI was being all stupid I noticed that Xorg had super high CPU usage. Like it would hit 25% at times, that's basically 1 core saturated (not sure if Xorg is multithreaded or not). This is a quad core machine (i3).

Greetings
Whenever I experience an unreasonable and sudden reduction in speed I look to hardware first and most commonly such issues are unresponsive Hard drives either beginning to fail or external drives not normally connected during boot, left in place. So I suggest running diagnostics on drives and even partitions to be sure that fstab is getting data feedback in proper time frames or at all. Of course check "dmesg" and "/var/log/Xorg.0.log" to look for clues, especially "E" and "W" error/warnings in Xorg.o.log even though it appears from lengthened boot times that the problem is not in X, but deeper. "Dmesg" is probably the best bet, combined with hardware diagnostics.

i'm pretty sure this is the real issue.

• how were you troubleshooting in the first place
• what was all this "mucking about" exactly?

(explain it to a computer)