Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Using Gimp 2 I wanted to alter an .xpm image file for use in a window-manager theme.
Gimp opened the file OK, let me work on it, but then after appearing to process the file for saving, gave me the message "Plugin could not save image."
I uninstalled Gimp and reinstalled it and everything urpmi wanted to associate with it, and got the same result.
The list of plugins shows an .xpm_open and an .xpm_save plugin, so it's not a missing plugin that's at fault.
I've created .xpm files in the past, and am pretty sure it was with The Gimp, but for some reason with this version, and under Mandrake 10.1 OE and kernel 2.6.8.1-20mdk, no go.
Has anybody else experienced this problem and solved it?
Several integer overflow flaws in the X.Org libXpm library used to decode
XPM (X PixMap) images have been found and addressed. An attacker could
create a carefully crafted XPM file which would cause an application to
crash or potentially execute arbitrary code if opened by a victim. The
Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned
the name CAN-2004-0914 to this issue.
For me it is update from xorg-x11-6.7.0-9 to xorg-x11-6.7.0-10.
On xorg-x11-6.7.0-9 this seems to work.. (different computer without update).
Here's what I get, after trying several spellings (they can't seem to decide how to spell their own name...):
Code:
[root@bodhisattva jon]# Xorg -version
Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.7
Build Operating System: Linux 2.4.19-44mdkenterprise i686 [ELF]
Current Operating System: Linux bodhisattva 2.6.8.1-20mdk #1 Mon Nov 8 12:35:22 CET 2004 i686
Build Date: 18 November 2004
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
Any idea about obtaining an update? Mandrake update doesn't list any as needed. Besides, if I understand you correctly, covex, it wouldn't solve teh problem anyway.
Edit, update: The documentation links on the xorg, or XOrg, or Xorg, or X.Org site, are all inoperative. That's hardly encouraging. I doubt that installing a new version would be within my capability anyway. So I guess I'm just stuck with not being able to handle xpm's anymore because some evildoers MIGHT send along ones that affect my system.
Sigh...
P. S. The reason I get huffy about the various spellilngs is that it does NOT help a user to do a locate, even with the -i switch, if spellings are not consistent, and especially if a dot is included sometimes and not others, as in the title of the site itself. It also raises doubts about the attention to detail given to documentation and work in general.
The only way to try it is to downgrade. I see your xorg build is from 18.11. - probably mandrake provided also an update of it.
This is mein:
Code:
Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.7
Build Operating System: Linux 2.4.21-23.ELsmp i686 [ELF]
Current Operating System: Linux all 2.6.8.1 #1 Sat Oct 23 19:36:09 CEST 2004 i686
Build Date: 16 November 2004
Build Host: bugs.build.redhat.com
I do not have a time to play with xorg downgrade now...
Originally posted by covex The only way to try it is to downgrade. I see your xorg build is from 18.11. - probably mandrake provided also an update of it.
I do not have a time to play with xorg downgrade now...
And I don't have the courage!
I wouldn't even know where/how to start. So I'll just live without the ability to edit/create .xpm images.
I read that they're very inefficient and bad in many ways anyhow and generally on their way out for widespread use; unfortunately they are also what IceWM
uses for its window decorations, as well as some other window managers (most?).
Maybe someday window managers will change over to .png images, we can all alter them to our hearts'
content, go out and buy more RAM, and be happy!
I have a high-speed connection. Perhaps I'll download the latest Knoppix and see if I can use Gimp from
it with .xpm successfully, just as an experiment.
I've submit a bug 141047 to redhat bugzilla, we will see if there is really something wrong... the strange thing is we have a different distributions but same behaviour..
Originally posted by covex I've submit a bug 141047 to redhat bugzilla, we will see if there is really something wrong... the strange thing is we have a different distributions but same behaviour..
BTW: I am more than a user of IceWM.
Thanks for the bug action! I suspect the problem's very well known by now, but surprised an easy fix doesn't seem to be available. At least for Mandrake. By poking around I find that both the X.Org and xpm libraries have been revised, apparently in response to this conflict. But I couldn't find out how to implement a fix.
Curious: when you say "more than a user," you don't happen to mean you're one of the IceWM developers, do you? Congrats if you are! Anyway, I keep coming back to IceWM though I'm enjoying Fluxbox at the moment--never could get it to work till Mandrake 10.1....
Originally posted by jonr
Thanks for the bug action! I suspect the problem's very well known by now, but surprised an easy fix doesn't seem to be available. At least for Mandrake. By poking around I find that both the X.Org and xpm libraries have been revised, apparently in response to this conflict. But I couldn't find out how to implement a fix.
There is no easy way to fix it, it is a bug in libXpm, hence without recompiling X, or atleast libXpm you can not fix it. I expect it to be fixed in next update of mandrake xorg package... but dono when it will be.
Quote:
Curious: when you say "more than a user," you don't happen to mean you're one of the IceWM developers, do you? Congrats if you are! Anyway, I keep coming back to IceWM though I'm enjoying Fluxbox at the moment--never could get it to work till Mandrake 10.1....
Only a maintainer of some docs and website.
IceWM is also a reason why I needed to work with xpm images and found I can not save them.
Originally posted by covex There is no easy way to fix it, it is a bug in libXpm, hence without recompiling X, or atleast libXpm you can not fix it. I expect it to be fixed in next update of mandrake xorg package... but dono when it will be.
Only a maintainer of some docs and website.
IceWM is also a reason why I needed to work with xpm images and found I can not save them.
Well, covex, thanks very much for the confirmation that this is not something to waste time on anymore. That's sometimes the most helpful kind of answer.
If you find out one of these days that a fix is ready (and doable by a normal user like me!), I hope you'll post a thread about it, or send me a private message.
The mirror you're using probably wasn't updated with the new packages when you checked it. Wait a couple of hours and try again.
The new packages are libxpm4-3.4k-28.2.101mdk and libxpm4-devel-3.4k-28.2.101mdk.
Originally posted by Tormented The mirror you're using probably wasn't updated with the new packages when you checked it. Wait a couple of hours and try again.
The new packages are libxpm4-3.4k-28.2.101mdk and libxpm4-devel-3.4k-28.2.101mdk.
Hey, thanks! That worked--after I got me a new "update" medium source. I'd read in another thread in LQ that the "proxad" mirror in France is very up-to-date and reliable, so I deleted my U. S. source and replaced it with proxad, and was able to get the new libraries.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.