Graphics Code Sites Notes

I was cautious when Slackware 12.1 came out, just like I always am. I downloaded the DVD ISO immediately, but I waited at least a month before upgrading to make sure LinuxPackages.net support caught up and that all the major kinks were gone.

Apparently I didn't wait long enough.

The upgrade went as smooth as the upgrade to 12.0. Everything seemed to function at first, although I didn't really notice anything different. Apparently the primary change was a few version numbers and some behind-the-scenes fixes. That was fine with me, improved stability never hurt anything.

However, issues quickly arose. Or, more specifically, an issue. The issue. I would be working, and spontaneously everything on the screen except my cursor would stop responding. (And how I hate the use of the word in that sense, but that's another rant). My music kept playing, Apache functioned, and I could even SSH in. From SSH, I gleaned that, for whatever reason, X was eating up 90-99% of the CPU. And yet it wasn't outputting anything or responding to input. Even if I resorte to SysRq+I, my music stopped and the cursor stopped moving, but the screen stubbornly stayed where it was. The only solution was a forced reboot by way of the power button or by Raising Elephants.

Now, not all hope was lost. For the most part, the issue only seemed to occur whenever I had Amarok open. So the solution is simple, right? Just stop listening to music, or at least stop using Amarok. But that's not so simple. Amarok is (WARNING: OPINION) the best audio player for Linux, and the only one that is capable of doing what I want. So, I tried other options. I tried 3 video drivers, and several framebuffer drivers, just in case. I tried resetting all of the settings in my home folder. I even went so far was to completely reinstall Slackware, which is a move normally reserved for desperate Windows users.

And yet the issue persists.

So, tomorrow, I plan to wipe Slackware 12.1 and return to the much less frustrating 12.0.