I use display from Imagemagic to resize jpeg images. When I do this the image flickers rapidly and I have to kill the app. This happens on two different machines (desktop and laptop). It has started quite recently. I thought it was a problem with Imagemagick but the maintainer for that can't reproduce it and when I use different WMs (aewm, twm) it is not there. It doesn't happen with gif images, including those I convert from the jpeg ones causing the problem. I can't be sure it is icewm that does this but, as I say, changing the wm makes it go away.
#include <hallo.h> * Anthony Campbell [Fri, Oct 02 2009, 10:34:15AM]: How? What do you run? What and where is the test data? I have no time for puzzles. In a quick test with my own data, I cannot reproduce it. What's "rapidly"? Once per second? 2fps? 10fps? Maybe you changed something else along with the WM, which triggered the problem? Regards, Eduard.
I don't know what else you want besides what is in the data generated by reportbug. Both machines are running Sid with no desktop manager. I'm not trying to set puzzles; it's not a major issue for me because I can get round the problem by converting jpeg files to gif or by using gimp, but I thought it was worth flagging up a bug report about it. If I fire up "display", load the image, select "view" and then resize to half size the flicker appears. I attach a sample jpeg file but it seems to happen with all of them. The flicker frequency is at least 10/sec. I've been using icewm for years (literally) and haven't seen this before. As I said in my original post, it may well not be icewm per se that causes the problem; there have been various issues with X recently, but I have no means of knowing if it is that. But since it happens with icewm and not other WMs I assume it is connected in some way. I tried running icewm without any config files but the same thing happens. Anthony
The problem is not there if I use graphicsmagick instead of imagemagick.
Recently I stared seing things with the nouveau driver where I'd never think it's possible to happen with X11, creepy rendering artifacts all over the place. Maybe you had something similar. In case you are still using IceWM, can you still reproduce this issue? If you are not using IceWM, would you mind if I just close this report as a temporary glitch? Thanks for reporting anyway, Eduard.