Pete Connolly wrote:

...

I put one of the files at <http://www.mrc-lmb.cam.ac.uk/dhoworth/f208c50af8a68669c364c22849f1d1de.png

...

. It's 190 kB and 820x36564 pixels. The little feedback I got on the Firefox forum was that Firefox on Windows can load the image OK, whilst Ubuntu has the same problem as me, so I'm wondering if it's a GNU/Linux library issue rather than a Mozilla core one. We're all using Firefox 1.5.0.9

Has anybody else come across this problem? Do any of you using Firefox 2 see the problem?

Strange. Firefox for Linux 2.0.0.2Pre says "The image “http://www.mrc-lmb.cam.ac.uk/dhoworth/f208c50af8a68669c364c22849f1d1de.png” cannot be displayed, because it contains errors.". Firefox 1.5.0.7 (must update that) for Windows running under Wine exits without an error, but without displaying anything. IE 6.0SP1 under wine does the same, as does IE 5.5 under wine.

another one: Firefox 2.0.0.1 on Windows shows some broken lines on the left side instead of any big picture. So it's most probably simply broken. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Dominique Leuenberger wrote:

...

...

...

On 16-02-2007 at 12:28, Wolfgang Rosenauer wrote:

...

another one: Firefox 2.0.0.1 on Windows shows some broken lines on the left side instead of any big picture. So it's most probably simply broken.

Wolfgang

Are you sure FF did not just reduce the size of the image to fit on the screen? I first thought the same.. but then when hovering over it with the mouse, I got the magnifying glasses and there the picture was.

oops, sorry. Yes, that's true. Windows Firefox 2.0.0.1 on WinXP works. So my first recommendation about filing a bug at mozilla.org is still valid ;-) Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Russell Jones wrote:

Windows actually seems to do the opposite: if you click on the image when the magnifying glass is shown, the picture disappears and the title bar says "Scaled (1%)". Looks like a cross-platform bug.

The default scaling depends on your preferences, IIRC. Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Wolfgang Rosenauer wrote:

Russell Jones wrote:

...

...

oops, sorry. Yes, that's true. Windows Firefox 2.0.0.1 on WinXP works. So my first recommendation about filing a bug at mozilla.org is still valid ;-)

Wolfgang

Windows actually seems to do the opposite: if you click on the image when the magnifying glass is shown, the picture disappears and the title bar says "Scaled (1%)". Looks like a cross-platform bug.

Russell Jones

Why? Above I wrote that FF displays an error on Linux and on Windows it works (only different behaviour for image scaling). So it's a Linux only issue probably in libpng.

Why what? ( Click on the image => image disappears and will not come back without a reload ) = bug No? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Wolfgang Rosenauer wrote:

...

...

Why? Above I wrote that FF displays an error on Linux and on Windows it works (only different behaviour for image scaling). So it's a Linux only issue probably in libpng.

Why what? ( Click on the image => image disappears and will not come back without a reload ) = bug No?

If it is one, it's another issue. I guess that there is a small stripe on the left side where you can click to descale it again but there is nothing visible.

Ah! Yes, so there is. More of an unsatisfactory behaviour than a bug (I suggest the scaler should draw at least a line of coloured pixels based on the image). I'll see what happens under OSu10.2 when I get home. I missed the bit about the "this image contains errors" notice, apologies. Russell Jones -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Wolfgang Rosenauer wrote:

Pete Connolly wrote:

...

...

I put one of the files at <http://www.mrc-lmb.cam.ac.uk/dhoworth/f208c50af8a68669c364c22849f1d1de.png

...

. It's 190 kB and 820x36564 pixels. The little feedback I got on the Firefox forum was that Firefox on Windows can load the image OK, whilst Ubuntu has the same problem as me, so I'm wondering if it's a GNU/Linux library issue rather than a Mozilla core one. We're all using Firefox 1.5.0.9

Has anybody else come across this problem? Do any of you using Firefox 2 see the problem? Strange. Firefox for Linux 2.0.0.2Pre says "The image “http://www.mrc-lmb.cam.ac.uk/dhoworth/f208c50af8a68669c364c22849f1d1de.png” cannot be displayed, because it contains errors.". Firefox 1.5.0.7 (must update that) for Windows running under Wine exits without an error, but without displaying anything. IE 6.0SP1 under wine does the same, as does IE 5.5 under wine.

another one: Firefox 2.0.0.1 on Windows shows some broken lines on the left side instead of any big picture. So it's most probably simply broken.

Sorry, what is "it" in "it's most probably simply broken"? The image file or mozilla? Somebody on the firefox forum says: Renders fine for me on W2K. Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.2pre) Gecko/20070213 BonEcho/2.0.0.2pre ID:2007021303 and somebody else said it works on XP but didn't provide a version. gimp and xv both display the file without warnings. Are there any tools to diagnose PNG errors? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ken Jennings wrote:

Can you try loading the images and re-saving them using gimp? Sometimes that cleans up any irregularities in image formats.

Interesting idea. gimp loads and saves it without any problem and the two files are different but firefox can't load either :(

"P00720 Enterobacteria phage T4 (164) Lysozyme..." And a long list of what appears to be horizontal bar charts in different shades of blue, green, and red.

I'm thinking of taking up a second career as an artist :) Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Call me a numerologist mystic if you like, but I suspect the height being >32767 pixels (the limit of a signed 16-bit integer) has something to do with it. What happens if it's resized to less than this? What if it's just saved with the same size by e.g. gimp? Russell Jones Peter Nikolic wrote:

On Friday 16 February 2007 11:51, Matthias Titeux wrote:

...

http://www.mrc-lmb.cam.ac.uk/dhoworth/f208c50af8a68669c364c22849f1d1de.png

I have just done a wget on the image and tried to view it using xv on 10.2 it displays a narrow vertical window full of alternate red white and green stripes with a few blues just for good measure .

it will not display in Konq just complains about imlib installation and Seamonkey 1.1 reports cannot be display because it contains an error

Pete .

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, Feb 16, 2007 at 03:09:43PM +0000, Dave Howorth wrote:

Russell Jones wrote:

...

Call me a numerologist mystic if you like, but I suspect the height being >32767 pixels (the limit of a signed 16-bit integer) has something to do with it. What happens if it's resized to less than this? What if it's just saved with the same size by e.g. gimp?

Call me a sucker if you like but I tried this. I'd been wondering the same thing :) It's fascinating.

When I resized it to 32768 pixels high, I got the same error message. When I resized it to 32767 pixels high, firefox crashed:

The program 'Gecko' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 23489 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

Perhaps that's useful info to add to Jan's bug report.

I seem to remember that X11 was limited to pixmaps of 32767 width and height at some point in time. Likely Firefox tries to create a larger one instead of rescaling before creation. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, 2007-02-16 at 08:25 -0800, Kai Ponte wrote:

GIMP - opened just fine.

Krita - opened just fine. That's one bizarre image.

Kwcikshow - crashed

KolourPaint - crashed with segfault - out of graphics memory message

GwenView - crashed with seg 11.

Since I'm bored - or trying to avoid digging through $128,763 in cashier reports to find a $473 discrepancy - I copied the file over to my Wintendo machine and tried it as well...

MS Paint - Opened just fine

MS Windows Picture and FAx Viewer - Opened just fine

GIMP 2.2 Windows - Opened just fine.

Go figure!

Thanks for this list. And thanks to everybody else for their contributions. I find this all quite fascinating. There's obviously a problem with FOSS software that Windows doesn't suffer from. It's probably related to X - I guess it's a question of knowing the correct idiom to use with one or other of the X libraries, since gimp et al handle things correctly. It would be interesting to know which libraries are used by the failing applications but perhaps not by gimp, gv and krita. Or maybe it's just a particular way of calling libraries. What surprises me is that this bug has apparently been recorded for nearly a year at a minimum, while it causes several applications to crash and is easily reproducible. It makes Linux look bad in comparison to Windows but it hasn't been solved! A minor aspect that I find interesting is that nobody seems to know of any technique to validate PNG image files. I'm amazed about that. BTW, hope you're into your weekend now, as I am here. Chinese New Year in 27.2 hours! Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Oh, and for what it's worth: http://lesstif.sourceforge.net/doc/super-ux/g1ae03e/part2/chap3-1.html "3.4.8. Restrictions Many programmers create a "scrolled list" by putting a List widget with many entries as a child of a Viewport widget. The List continues to create a window as big as its contents, but that big window is only visible where it intersects the parent Viewport's window. (I.e., it is "clipped.") While this is a useful technique, there is a serious drawback. X does not support windows above 32,767 pixels in width or height, but this height limit will be exceeded by a List's window when the List has many entries (i.e., with a 12 point font, about 3000 entries would be too many.)" http://sourceforge.net/mailarchive/message.php?msg_id=13925057 2005-11-21 04:23 "X11 and Win32 limit the size of windows to 32768 pixels in either direction. But the canvas widget has code in place to work around those limits. Coordinates in a canvas widget are stored as doubles and can thus be really big. Of course, I suppose there could be bugs in the code that works around the 16-bit limit of X11 and Win32. It is not a piece of code that is used that often, after all. Perhaps you could submit a bug report with a specific example that fails." http://static.kdenews.org/mirrors/qt-x11-free-3.0.0-snapshot-20010803/doc/ht... "bool QImage::create ( int width, int height, int depth, int numColors = 0, Endian bitOrder = IgnoreEndian ) Sets the image width, height, depth, its number of colors (in numColors), and bit order. Returns TRUE if successful, or FALSE if the parameters are incorrect or if memory cannot be allocated. The width and height is limited to 32767. depth must be 1, 8, or 32. If depth is 1, bitOrder must be set to either QImage::LittleEndian or QImage::BigEndian. For other depths bitOrder must be QImage::IgnoreEndian." Does this apply to QT4? Which do those in Kai's apps list use? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Friday 16 February 2007 12:47, Dave Howorth wrote:

On Fri, 2007-02-16 at 08:25 -0800, Kai Ponte wrote: <snip>

There's obviously a problem with FOSS software that Windows doesn't suffer from.

Corporate bloat? What problem would that be, exactly? Actually, I didn't use Wintendo to prove it better/worse, just to check libraries. I was curious if the same XXL .png file would load on one OS the same as the other.

It's probably related to X - I guess it's a question of knowing the correct idiom to use with one or other of the X libraries, since gimp et al handle things correctly. It would be interesting to know which libraries are used by the failing applications but perhaps not by gimp, gv and krita. Or maybe it's just a particular way of calling libraries.

What surprises me is that this bug has apparently been recorded for nearly a year at a minimum, while it causes several applications to crash and is easily reproducible. It makes Linux look bad in comparison to Windows but it hasn't been solved!

Not really. I doubt too many people run into such a monstorous .png file. That is - after all - really large, and may simply be too big for some libraries to handle. By comparison to a buffer overflow exploit, I'm sure it is a lesser priority.

A minor aspect that I find interesting is that nobody seems to know of any technique to validate PNG image files. I'm amazed about that.

BTW, hope you're into your weekend now, as I am here. Chinese New Year in 27.2 hours!

Gung Hay Fat Choy! -- kai Free Compean and Ramos http://www.perfectreign.com/?q=node/46 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Saturday 17 February 2007 06:21, Jan Engelhardt wrote:

On Feb 17 2007 06:11, Kai Ponte wrote:

...

On Friday 16 February 2007 12:47, Dave Howorth wrote:

...

On Fri, 2007-02-16 at 08:25 -0800, Kai Ponte wrote:

<snip>

...

There's obviously a problem with FOSS software that Windows doesn't suffer from.

Corporate bloat?

What problem would that be, exactly?

OpenOffice/Writer requiring like 80 MB and quite some time to load up. SMO is on the boat with roughly 7 MB, and well, I don't have any numbers for MSO (a lack of `pmap` on Windows), but given that it starts up as fast on a 16 MB RAM Win98 machine as OOO does on a multi-CPU opteron, I think that tells enough.

(SMO = Softmaker Office MSO = Microsoft Office)

Actually, I was referring to the corporate bloat in terms of slow moving monolithic application development streams that are caught up in massive amounts of red tape. Having been involved in some of the larger accounting systems implementations, I've seen the worst in IT. As for OOo, the bloat to which you're referring comes from pointy-haired managers like me who ask for more and more features. Features eventually end up as bloat. Just look at Firefox. It is/was faster because it doesn't have all the features of a full-fledged Mozilla/Seamonky. However, if you start packing on the extensions, you end up as bloated. In Firefox, I try to strike a happy balance between speed and extensions I want. OpenOffice pretty much works for me. Could we get along with vi or emacs as our editors? Yes. Do we want to? No. -- kai Free Compean and Ramos http://www.perfectreign.com/?q=node/46 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Saturday 17 February 2007 10:25, Jan Engelhardt wrote:

On Feb 17 2007 07:09, Kai Ponte wrote:

...

As for OOo, the bloat to which you're referring comes from pointy-haired managers like me who ask for more and more features. Features eventually end up as bloat. Just look at Firefox. It is/was faster because it doesn't have all the features of a full-fledged Mozilla/Seamonky. However, if you start packing on the extensions, you end up as bloated. In Firefox, I try to strike a happy balance between speed and extensions I want.

As for Seamonkey, it is actually beneficial to have it as one rather than to have Firefox and Thunderbird installed and started separately.

That may be for those of you who use Thundirbird. I don't, so I use Firefox. I have Kmail for mail Pan for news Firefox / Opera / IE for interweb. To each his own. -- kai Free Compean and Ramos http://www.perfectreign.com/?q=node/46 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Saturday 17 February 2007 12:02, David Brodbeck wrote:

Jan Engelhardt wrote:

...

OpenOffice/Writer requiring like 80 MB and quite some time to load up. SMO is on the boat with roughly 7 MB, and well, I don't have any numbers for MSO (a lack of `pmap` on Windows), but given that it starts up as fast on a 16 MB RAM Win98 machine as OOO does on a multi-CPU opteron, I think that tells enough.

MS Office pre-loads a fair amount of stuff at system boot, IIRC. So you're trading off longer boot time and more idle memory consumption for shorter application start up time. It also kind of depends on what version of MS Office you're using. Word 2003 seems to take about as long to load as OpenOffice Writer, for me, on machines with similar resources. If you're running Office on Windows 98, you're probably comparing an older, smaller version of MS Office to a newer version of OpenOffice. Both applications have gotten bigger over time as they became expected to do more.

Yes, they have. I have Office 97 on some machines and Office XP on this machine (under CX Office) and Office 2003 on a few machines, while I have that abomination Office 2007 on one test machine. (Yuck!) They all appear to load faster than OOo because they - well - load in memory when the Window manager (XP/2k/2K3) loads. You can do the same thing with OOo on KDE. I have the OpenOffice Quickstarter loaded on startup. It doesn't seem to take much in time to load overall and only takes about 30MB of RAM. On all my systems, I have at least 1GB or more of RAM so 30MB is not a big deal. (Still don't know what to do with all those 256K and 512K SIMM cards I have lying around...) I just checked on my laptop and OOo Writer took three seconds to load.

Sometimes I get nostalgic for the days when documents didn't have to be so fancy. I still remember when it was socially acceptable to buzz out a business report in 12-point Elite on a dot-matrix printer, rip off the tractor-feed tracks, and turn it in. ;)

I miss that cool noise! -- kai Free Compean and Ramos http://www.perfectreign.com/?q=node/46 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Peter Nikolic schrieb:

I have just done a wget on the image and tried to view it using xv on 10.2 it displays a narrow vertical window full of alternate red white and green stripes with a few blues just for good measure .

On my SLED10 system only konqueror displays that file. Neither Firefox 1.5.09 nor latest gimpshop will open that file correctly. I hope it helps. Thx Jan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Le Vendredi 16 Février 2007 14:37, Peter Nikolic a écrit :

On Friday 16 February 2007 11:51, Matthias Titeux wrote:

...

http://www.mrc-lmb.cam.ac.uk/dhoworth/f208c50af8a68669c364c22849f1d1de.pn g

I have just done a wget on the image and tried to view it using xv on 10.2 it displays a narrow vertical window full of alternate red white and green stripes with a few blues just for good measure .

it will not display in Konq just complains about imlib installation and Seamonkey 1.1 reports cannot be display because it contains an error

Pete .

Hi, Using OpenSuse 10.0, i586. I had the same complaint about imlib when I clicked on the link, but if I open the URL direclty in konq (copy paste the URL from the mail), it worked. I went a little further, and downloaded the file : Kwickshow = complaints about imlib Gwenview=starts to display the picture then crash Kview=displays only a black picture Showfoto=crash The Gimp (2.2)=displays it and precise that the background is transparent koulourpaint=complaint about to low graphic memory (?) Dunno if it helps Cheers Matthias -- __________________________________________________________ Matthias Titeux, PhD Département de génétique des maladies cutanées et allergiques dans des modèles animaux et chez l'homme. INSERM U563 - CPTP Pavillon Lefebvre, 5ème étage CHU Purpan BP3028 31024 Toulouse cedex 03 __________________________________________________________ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org