KDE 4.10.5
xorg-x11-server-Xorg.x86_64 1.13.3-3.fc18
Fedora 18 64-bit

Just recently changed my desktop wallpaper (right-click, Folder View Settings, select the file from a directory) and when clicking the Apply button, everything locked hard. I could initially PuTTY in from my Windows box and top showed X consuming typically more than 85% of CPU. Eventually, it neared if not reached 100% and finally even PuTTY disconnected. All drive activity ceased and I had no option but to power cycle the box (a laptop).

The first time it happened, it came back up normally with the newly-chosen wallpaper in place but functional. The second time, the next wallpaper (a different file) was displayed but X ran wild immediately after login and it locked up before even the KDE Wallet login prompt appeared. I was able to PuTTY in and delete the current wallpaper file, so after power cycling it again, it came functional with a black background. I chose an image, but didn't preview and it's been OK since. But then again, I've not tried it again (I need the laptop for a business trip next week and can't afford it to be non-op).

The images were nothing unusual - Some JPGs, some PNGs, all relatively small (the laptop's display is 1366x768).

Anyone else run into this?

Thanks!

The SSH connection being lost indicates the system could be suffering from memory pressures as well - can you confirm if this is the case?

I'll have to check if/when it happens again, although I have 8 GB memory and nothing else at all was running. top showed almost 6 GB free at the time via the SSH session. Thanks.

Another potential suspect here, especially as Plasma uses an effect to change between wallpapers, is the graphics libraries and driver. Which driver/card combination are you using?

According to the Catalyst Control Center:

AMD Radeon HD 7640G
Driver Packaging Version 12.104-130328a-155999C-ATI
2D Driver Version 13.15.3

However, it's been at this level for months and this issue showed up only the last time I tried to change wallpaper. It's never happened before.

Can you reproduce this behaviour under a new user?

I've not tried. I'm out of town on business right now... attending a class on a Windows backup product, if you must know

I'll try to give it a shot when I return. Thanks.