https://bugzilla.novell.com/show_bug.cgi?id=680474
https://bugzilla.novell.com/show_bug.cgi?id=680474#c6
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |UPSTREAM
--- Comment #6 from Johannes Meixner 2011-03-25 08:49:01 UTC ---
How unfortunate that sane-backends-1.0.21 with the fix for bug#658017
got lost!
But fortunately the openSUSE build service has a revision control
system so that I could resurrect it:
sane-backends-1.0.21 RPMs with the fix for bug#658017
are now available for download from
http://download.opensuse.org/repositories/home:/jsmeix/
for openSUSE 11.2, 11.3, 11.4 and Factory
and for SLE_11 and SLE_11_SP1
for 32-bit i586 and 64-bit x86_64 architecture.
For example for openSUSE 11.4 for x86_64 architecture install
sane-backends-1.0.21-7.1.x86_64.rpm
sane-backends-32bit-1.0.21-7.1.x86_64.rpm
and optionally
sane-backends-autoconfig-1.0.21-7.1.x86_64.rpm
from
http://download.opensuse.org/repositories/home:/jsmeix/openSUSE_11.4/x86_64/
Do not use Factory unless you know exactly what you do.
Use the matching packages for your particular system.
The packages are
* only for testing
* without any guarantee or warranty
* without any support
As an extreme example, this means that if your complete computer
center crashes because of these packages, it is only your problem.
On the other hand this does not mean that those packages are known
to be terrible broken but they are not thoroughly tested so that
any unexpected issue can happen.
For now this is all what I can do here, see comment #3.
H. Hansen,
I think that you could help the SANE upstream authors a lot
if you get debug-messages for sane-backends-1.0.22
and then contact the upstream developers, e.g. via mail, see
http://www.sane-project.org/mailing-lists.html
or submit a bug report to SANE, see
http://www.sane-project.org/bugs.html
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
