Please apply the attached patch when updating the version of the
leptonlib package. This adds a debian/watch file to allow checking for
new upstream versionsof Leptonica automatically.
https://wiki.debian.org/debian/watch
diff -Nru leptonlib-1.82.0/debian/watch leptonlib-1.82.0/debian/watch
Source: leptonlib
Leptonica version 1.83.1 was released on January 26, 2023.
https://github.com/DanBloomberg/leptonica/releases/tag/1.83.1
https://github.com/DanBloomberg/leptonica/releases/download/1.83.1/leptonica-1.83.1.tar.gz
On 3/29/2022 8:13 AM, David Ward wrote:
The 32-bit overflow issue with the backend should be fixed now in
libsane1 1.1.1-5.
With that installed, can you please try xsane again? Is there still an
issue with colors?
If you experience segmentation faults, can you please try to obtain
Philipp,
On 2/21/2022 5:01 AM, Philipp Klaus Krause wrote:
On 12/9/2020 8:22 AM, Philipp Klaus Krause wrote:
Summary: The situation improved somewhat, but is still far from perfect:
There is still an odd waiting time when starting to scan at 2400 or 4800
(at 1200 and below the scan starts
Philipp,
On 2/21/2022 5:01 AM, Philipp Klaus Krause wrote:
On 12/9/2020 8:22 AM, Philipp Klaus Krause wrote:
Summary: The situation improved somewhat, but is still far from
perfect:
There is still an odd waiting time when starting to scan at 2400 or
4800
(at 1200 and below the scan starts
On 3/15/2022 7:15 AM, ael wrote:
In fact there are still outstanding problems which are mentioned
earlier in this bug.
Separate problems need to be tracked in separate bugs, even if they
affect the same hardware.
Please see: https://www.debian.org/Bugs/Reporting
This bug in Debian was
Jörg — a friendly reminder that this pull request is ready for review.
(See the bottom of this message).
Please refer to our earlier discussion below; I have added a comment.
On Mon, 07 Feb 2022 at 19:17:48 -0500, David Ward wrote:
> On Mon, 07 Feb 2022 at 23:35:49 +0100, Jörg Frings-Fü
tags 942176 + fixed-upstream
stop
This was a 32-bit integer overflow issue. Note that a full size, 4800 dpi color
scan produces an image that is > 6 GiB uncompressed.
On 2/27/2022 6:55 PM, David Ward wrote:
Both issues have just been reproduced upstream. Discussion at:
https://gitlab.com/sane-project/backends/-/merge_requests/374#note_856438189
Cloning this bug in Debian, since there seem to be separate issues in
the backend (libsane1) and the graphical
On 2/21/2022 5:01 AM, Philipp Klaus Krause wrote:
I have not been able to reproduce the bug using scanimage from the
command line¹ (did various scans at 2400 and 4800 dpi today, using
Debian testing). Both speed and color were fine using scanimage from
the command line.
But I can reproduce
On 2/21/2022 5:01 AM, Philipp Klaus Krause wrote:
I do get a different bug with scanimage though: For a full-size scan
at 4800 dpi, two thirds of the image are just gray.
Does the problem you see from scanimage happen with version 1.1.1 (of
libsane1, libsane-common, sane-utils, etc.)?
Package: sane-utils
Version: 1.1.1-2
Severity: serious
(The original title and description of this bug were inaccurate; please
disregard those. The existing pull request has been updated.)
When the libsane1 package is installed, a "scanner" group is created on
the system, which has access to
On 11/5/2021 1:59 PM, Bertrand Marc wrote:
After upgrading to bullseye, scanning with my HP Scanjet 5300C (ID
03f0:0701 HP, Inc ScanJet 5300c/5370c) became difficult.
Please note that it was working fine with buster, except that it
required the attached /etc/sane.d/avision.conf and works with
On 2/23/2021 8:13 AM, Martin-Éric Racine wrote:
$ sudo sane-find-scanner
found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan],
chip=LM9830) at libusb:002:003
found USB scanner (vendor=0x0411 [Ralink], product=0x00e8 [802.11 n
WLAN]) at libusb:001:004
found USB scanner
It seems very likely that the original problem is an upstream bug in
SANE. There are a few issues reported there specifically against the
Canon LiDE 220 that sound very similar:
https://gitlab.com/sane-project/backends/-/issues/439
https://gitlab.com/sane-project/backends/-/issues/518
On
On 8/29/2021 4:12 AM, alain wrote:
$ dpkg -l sane-backends
dpkg-query: aucun paquet ne correspond à sane-backends
sane-backends is the source package name. You cannot install that.
Please run "sudo apt upgrade libsane-common".
$ cat /etc/debian_version
bookworm/sid
$ dpkg-query -l 'hplip*'
changes up to ac8816eb1dabbaf4b303edf52a1c0cb4e9fd45a7:
d/*.README.Debian: Adjust to reflect current permissions
(2022-02-13 22:22:46 -0500)
David Ward (9):
Move sane-umax_pp(5) to libsane-common, and remove umax_pp(5
Package: sane-utils
Version: 1.1.1-2
SANE provides a backend driver named umax_pp to supports Umax parallel
port flatbed scanners. This is a library (libsane-umax_pp.so.1) found in
the Debian package libsane1.
SANE also includes a command-line utility named umax_pp for testing,
which is
Package: sane-utils
Version: 1.1.1-2
Debian includes a "scanner" group when the operating system is
installed. When installing the sane-utils package, the newly-created
"saned" user is added to this group by default. If the sane-utils
package is purged though, the "scanner" group is deleted
>
> Hi Jörg,
> Unlike cups, which hardly makes sense without a daemon, saned is not
> absolutely necessary.
>
That is exactly why we should split it out as a separate package.
The user should be able to choose not to install saned, without that choice
preventing the user from running
Package: sane-utils
Version: 1.1.1-1
saned is a daemon used to share scanners over the networks.
This belongs in its own package. Users should be able to install and run the
other command-line utilities - in particular, scanimage - without installing
saned (even if it is disabled). This is
On 12/9/2021 11:15 AM, Mattia Rizzolo wrote:
Source: debhelper
Version: 13.5.2
Hi Niels!
I was looking at backporting 13.5.2 all the way to ubuntu 18.04 bionic,
which ships with perl 5.26.
However, it seems that commit 3b2fe5334b88e38197fa24d9459544e50466fc92
"Dh_Lib.pm: Use state feature (by
Package: linux
Version: 5.3.7-1
Severity: important
Owner: Salvatore Bonaccorso
Tags: patch
The kernel configuration change from Debian bug 940726 is invalid,
according to Intel: https://bugzilla.kernel.org/show_bug.cgi?id=204237#c15
The options for the SST and SOF drivers for
On 11/10/19 1:05 PM, David Ward wrote:
Unfortunately, this has caused a regression. The SST and SOF drivers
cannot both be enabled for the same Intel platform in the kernel
configuration, according to Intel.
https://bugzilla.kernel.org/show_bug.cgi?id=204237#c15
To clarify, the statement
Unfortunately, this has caused a regression. The SST and SOF drivers
cannot both be enabled for the same Intel platform in the kernel
configuration, according to Intel.
https://bugzilla.kernel.org/show_bug.cgi?id=204237#c15
As described in the bug, this change causes a loss of sound on the
Package: netbase
Version: 4.45
Severity: wishlist
Please add protocol 135 (Mobility Header for IPv6) to /etc/protocols. This
entry is registered by IANA and is labeled as mobility-header in FreeBSD
and NetBSD's /etc/protocols file. iproute2's xfrm selectors have special
handling for this
and then simply quit. It seemed
to turn them on.
Not a very practical solution though.
Regards
David Ward aka DaveQB
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
27 matches
Mail list logo
