Bug#454402: marked as done (libsane: HP DeskJet F380 all-in-one scanner always produces images with JPEG artifacts)
Your message dated Fri, 3 Mar 2017 18:44:20 +0000
with message-id <03032017184020.2d3f0691c194@desktop.copernicus.org.uk>
and subject line Re: Bug#454402: libsane: HP DeskJet F380 all-in-one scanner always produces images with JPEG artifacts
has caused the Debian Bug report #454402,
regarding libsane: HP DeskJet F380 all-in-one scanner always produces images with JPEG artifacts
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
454402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454402
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libsane: HP DeskJet F380 all-in-one scanner always produces images with JPEG artifacts
- From: Andrey <cmr.Pent@gmail.com>
- Date: Wed, 05 Dec 2007 09:36:41 +0300
- Message-id: <20071205063641.2545.32320.reportbug@neo.paramonovs>
Package: libsane
Version: 1.0.19~cvs20070730-1
Severity: normal
I have an HP DeskJet F380 all-in-one device. It was recognized without a
problem by my Debian system (both printer and scanner parts), but
scanned images always have annoying JPEG-like artifacts.
I used xsane and scanimage frontends, trying every format available, and
always the resulting image was affected by severe JPEG artifacts. See
for example aparamon.msk.ru/ftp/out.png . The artifacts appear on
xsane preview window as well.
My guess is that the image comes from scanner already corrupted. On
Windows and some time ago on Slackware systems I didn't notice such
problems.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-2-486
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libsane depends on:
ii adduser 3.105 add and remove users and groups
ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries
ii libexif12 0.6.16-2 library to parse EXIF files
ii libgphoto2-2 2.4.0-7 gphoto2 digital camera library
ii libgphoto2-port0 2.4.0-7 gphoto2 digital camera port librar
ii libieee1284-3 0.2.11-1 cross-platform library for paralle
ii libjpeg62 6b-14 The Independent JPEG Group's JPEG
ii libtiff4 3.8.2-7 Tag Image File Format (TIFF) libra
ii libusb-0.1-4 2:0.1.12-7 userspace USB programming library
ii makedev 2.3.1-84 creates device files in /dev
ii udev 0.114-2 /dev/ and hotplug management daemo
Versions of packages libsane recommends:
ii module-init-tools 3.3-pre11-4 tools for managing Linux kernel mo
ii sane-utils 1.0.19~cvs20070730-1 API library for scanners -- utilit
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: 454402-done@bugs.debian.org
- Subject: Re: Bug#454402: libsane: HP DeskJet F380 all-in-one scanner always produces images with JPEG artifacts
- From: Brian Potkin <claremont102@gmail.com>
- Date: Fri, 3 Mar 2017 18:44:20 +0000
- Message-id: <03032017184020.2d3f0691c194@desktop.copernicus.org.uk>
- In-reply-to: <20071205063641.2545.32320.reportbug@neo.paramonovs>
- References: <20071205063641.2545.32320.reportbug@neo.paramonovs>
On Wed 05 Dec 2007 at 09:36:41 +0300, Andrey wrote:
> I have an HP DeskJet F380 all-in-one device. It was recognized without a
> problem by my Debian system (both printer and scanner parts), but
> scanned images always have annoying JPEG-like artifacts.
>
> I used xsane and scanimage frontends, trying every format available, and
> always the resulting image was affected by severe JPEG artifacts. See
> for example aparamon.msk.ru/ftp/out.png . The artifacts appear on
> xsane preview window as well.
>
> My guess is that the image comes from scanner already corrupted. On
> Windows and some time ago on Slackware systems I didn't notice such
> problems.
In essence, upstream explain their thinking and say
> Setting to invalid because it's not likely this default will be changed.
There is no action for Debian to take on the issue. Hence closing.
Regards,
Brian.
--- End Message ---
Reply to: