Summary: | xsane dies with a glibc error when saving a captured image | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Hsia <xanderhsia> |
Component: | Current packages | Assignee: | Patrick Kursawe (RETIRED) <phosphan> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | normal | CC: | lu_zero |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alexander Hsia
2004-12-06 20:30:25 UTC
lu_zero/phosphan: please consider filling out your metadata.xml for this package with at least one of your details. Entered my data, but I would be happy if someone else took this. Alexander: It would be nice to know which xsane version you tried to run. The message indicates an error in xsane that should be fixed. As a workaround, you can make glibc ignore this error. Quote: By default, the program that generated this error will also be killed; however, this (and whether or not an error message is generated) can be controlled via the MALLOC_CHECK_ environment variable. The following settings are supported: * 0 = Do not generate an error message, and do not kill the program * 1 = Generate an error message, but do not kill the program * 2 = Do not generate an error message, but kill the program * 3 = Generate an error message and kill the program Sure thing Patrick, I was trying to run xsane-0.96 I just tried setting the MALLOC_CHECK_ environment var to 0 and it worked! Nice to have a workaround. I guess my question now is, who do I send this upstream to? glibc people or Oliver, the maintainer of xsane. Or should I just wait and let it get pushed upstream after some more vetting in gentoo's bugzilla? Thanks a million, (I really really hated having to restart xsane after every scan) -Alex This is no glibc but an xsane problem. I'll give the author a hint to check this bug. He can contact your for details, then if this is not a known problem. Alexander, please contact the author directly (oliver.rauch@xsane.org) and don't forget to tell him in which file format you were trying to save. Closing this as UPSTREAM. Could you perhaps try 0.96-r1 when it has hit your mirror and tell me if it solves the problem? Changing resolution to test-request I've been in contact with Oliver. He thinks he has found the bug, and will send me a patch/diff to check it out. As it turns out, it was only the pnm file format that evoked this bug; but since that is the default save format, a lot of people would probably run into this. I will try 0.96-r1 when I sync up today. And when Oliver sends me the patch, I'll test it too and forward here if it works. He told me to move two fclose() calls to another function. -r1 does exactly this. Tried xsane-0.96-r1 and it works like a charm. No more crashing out with a glibc error Thanks for testing. |