On 29/11/2024 01:35, John Goerzen wrote:
I have been using gscan2pdf for many years. My scanner is a Brother ADS-3300W,
connected by wifi, and it also has been working fine for a long time (months or
years). I use it exclusively with gscan2pdf.
Today, it started segfaulting on scan. It always
Thanks for the heads-up. Looks like something in imagemagick is
different, and thus the resulting image size is different.
OpenPGP_signature.asc
Description: OpenPGP digital signature
severity 1082810 normal
thanks
OpenPGP_signature.asc
Description: OpenPGP digital signature
, Santiago Vila wrote:
El 28/9/24 a las 12:31, Jeff escribió:
What is different about your setup?
LOGNAME=root
If that is the case, I wonder if this really should be severity=serious.
Maybe severity=normal?
OpenPGP_signature.asc
Description: OpenPGP digital signature
I can't reproduce this. The tests pass elsewhere in chroots:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gscan2pdf.html
What is different about your setup?
OpenPGP_signature.asc
Description: OpenPGP digital signature
severity 1030982 normal
thanks
Reducing the severity down to normal until the problem can be reproduced
and debugged.
On 11/02/2023 15:50, Janusz S. Bień wrote:
The failure log was
[log1 (application/octet-stream, attachment)]
That file ends with:
DEBUG - signal 'started-process' emitted with message: Scanning page 1 of 1
INFO - gscan2pdf: scanning image of size 1275x1784 pixels at 24 bits/pixel
INFO - gscan2
I still don't understand. The log you provided covered a successful
scan, with a couple of post-processing steps.
Please provide a log where the scan job failed.
OpenPGP_signature
Description: OpenPGP digital signature
In the log you provide, you seem to have a successful scan. Is the
problem therefore only the warning message?
If the other device does not work, please provide a log file created
when scanning with the other device.
OpenPGP_signature
Description: OpenPGP digital signature
There's no segfault there.
Please start gscan2pdf from the command line with the --log=log
option, if necessary, hit OK to select the crashed session, reproduce
the problem (i.e. the segfaul), quit, and post the log file, which
gscan2pdf may have compressed with xz.
OpenPGP_signature
Descript
Please start gscan2pdf from the command line with the --log=log option,
reproduce the problem, quit, and post the log file, which gscan2pdf may
have compressed with xz.
OpenPGP_signature
Description: OpenPGP digital signature
On Tue, Jan 24, 2023 at 02:32:07PM +0100, Santiago Ruano Rincón wrote:
> > Tests yesterday seem to indicate successful results, but again I've only
> > tested a few combinations in a VM (to keep the feedback loop short).
> >
> > From the installer team point of view, I'd welcome a swift upload wi
nks everybody for the inputs. I've applied Paul's solution, and the
> generated .deb can be downloaded from here:
>
> https://salsa.debian.org/debian/ifupdown/-/jobs/3841392/artifacts/raw/debian/output/ifupdown_0.8.41~1.gbp3a6fae+salsaci+20230123+42_amd64.deb
>
> Would it be
hosts diff from the buildd ones?
Thanks for your help.
Regards
Jeff
OpenPGP_signature
Description: OpenPGP digital signature
as these really shouldn't have
anything to do with gscan2pdf - maybe a dependency, e.g. gtk+.
But these also occur in runs which pass, such as:
https://ci.debian.net/data/autopkgtest/stable/amd64/g/gscan2pdf/23364484/log.gz
I'd be grateful for any suggestions
Regards
Jeff
Open
klinuxcnc, it doesn't use OpenGL and probably also doesn't use
Img. However, it's much less friendly (IMO)
Jeff
Control: tags unblock -1 by 1007752
Control: notforwarded -1
Control: tags block 1009448 by -1
OpenPGP_signature
Description: OpenPGP digital signature
Control: tags -1 - bookworm confirmed fixed-upstream ftbfs
thanks
OpenPGP_signature
Description: OpenPGP digital signature
In test 13, libpdf-builder-perl produces the attached PDF, which neither
Firefox nor Evince complains about, and prior to v9.56.0, ghostscript
accepted happily.
With v9.56.1:
$ gs -q -dNOPAUSE -dBATCH -sDEVICE=pnggray -g20x20 -dPDFFitPage
-dUseCropBox -sOutputFile=out.png out.pdf
Error: /typ
forwarded 1009448
https://github.com/PhilterPaper/Perl-PDF-Builder/issues/184
thanks
OpenPGP_signature
Description: OpenPGP digital signature
To confirm - I've just put the 3 packages for gs 9.56.1 (and nothing
else) from sid on my testing machine, and now I see the same failures.
OpenPGP_signature
Description: OpenPGP digital signature
My machine running testing currently has ghostscript 9.55.0, and there
it still builds fine. So I'm guessing the problem is between 9.55.0 and
9.56.0.
Indeed since the failure with 9.56.0, 9.56.1 has been uploaded.
I've just tried building it with 9.56.1 but it still has the same two
failures
Going through what changed between the previous successful build
https://buildd.debian.org/status/fetch.php?pkg=libpdf-builder-perl&arch=all&ver=3.023-1&stamp=1631870648&raw=0
and the failure:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpdf-builder-perl.html
I see the
Yes, I made a mistake with respect to 1.2.2. Upstream's official patch is
here. I am going to attempt a high urgency upload during the next houw with
1.2.2 + this patch. If that fails for any reason, NMU welcome without
delay.
https://chromium.googlesource.com/webm/libwebp/+/4f1839957115fa4713ed74
On Wed, 15 Dec 2021 21:08:28 +0100 Stephen Kitt wrote:
> Hi Jeff,
>
> On Tue, 14 Dec 2021 09:13:42 +0000, Jeff Blake wrote:
> [...]
> > Inspector and convertutf are the worst offenders in terms of being
> > unnecessary and complex. The disable/catapult.patch could al
On Tue, 7 Dec 2021 19:43:10 +0100 Tomas Pospisek wrote:
> On 06.12.21 20:43, Noah Meyerhans wrote:
> > On Sun, Dec 05, 2021 at 07:58:17PM +0300, Dmitry Alexandrov wrote:
> So what's happening with chromium in both sid and stable? I saw on
> d-release that it was removed from testing (#9
reopen 980202
thanks
imagemagick 8:6.9.11.60+dfsg-1 does not include the bugfix that was
promised here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980202#41
OpenPGP_signature
Description: OpenPGP digital signature
This is more or less a duplicate of #980202
To unblock gscan2pdf, in case -60 didn't fix things, I uploaded
gscan2pdf-2.11.0-1 yesterday and replaced imagemagick with
graphicsmagick for the tests in question.
However, this doesn't solve the problem in imagemagick, which is
described in #9802
On 23/01/2021 17:53, Cristy wrote:
Thanks for the problem report. We can reproduce it and will have a patch
to fix it in the GIT main branch @
https://github.com/ImageMagick/ImageMagick6 later today. The patch will
be available in the beta releases of ImageMagick @
https://imagemagick.org/down
This seems to be a bug in imagemagick preventing imagemagick from
migrating from unstable to testing:
https://tracker.debian.org/pkg/imagemagick
https://ci.debian.net/packages/g/gscan2pdf/testing/amd64/
OpenPGP_signature
Description: OpenPGP digital signature
Thanks for the head up.
I note that it built fine in sid a month ago:
https://buildd.debian.org/status/fetch.php?pkg=gscan2pdf&arch=all&ver=2.10.2-1&stamp=1608242025&raw=0
but that it didn't a couple of days ago in reproducible-builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstab
ht be better to omit it for the sake of simplicity and reduced
maintenance burden.
Regards,
Jeff Blake
hen compiling.
Looking at the last couple of commits for the file affected by the ozone
problem [1], it appears to be already fixed upstream.
[1] - https://tinyurl.com/yc8y4ah4
Regards,
Jeff
over at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973848
Jeff Blake
(or a new release is made) you could use Chromium's
bundled version of libvpx [2].
Feel free to have a look around my repo, as you might well encounter some of
the same problems that
I had in getting things to build.
Jeff Blake
[1] https://github.com/berkley4/ungoogled-chromium-debian
The changes between 2.3.0 and 2.8.0/1 (at least as far as opening the
scanner are concerned) were to cache the list of devices, in order to
save a few seconds searching for them - on most systems they are
identical every time.
On some systems, the device names change due to the USB IDs changing.
#x27;re getting back from lt_dlopen() invalid? All we can tell from this
test is that it's not NULL.
Specifically: I'm not sure that calling lt_dlerror() will return anything
meaningful if there has been no error.
--
Jeff Squyres
jsquy...@cisco.com
on of SIMD instructions like AVX2. There's been an enormous
amount of back & forth on this topic in upstream over the years, so I'd like
to take this bug there and let them weigh in.
Jeff
BACKGROUND:
Debian's wine build applies temporary-directory.patch which modifies
libwine to change the location of wineserver's temp dir.
WHAT CHANGED:
With wine commit fe13f7a3b0d0ad709676aa046cb4c9da260900cf
create_server_dir() quit depending on wine_get_server_dir() from
libwine. This was a pa
Package: src:linux
Version: 4.19.28-2
Severity: grave
Tags: security
Justification: user security hole
Dear Maintainer,
An issue was discovered in rds_tcp_kill_sock in net/rds/tcp.c in the Linux
kernel before 5.0.8.
There is a race condition leading to a use-after-free, related to net namespace
I think the right thing is to update to the latest jhove release (1.20) but
looks like the build system has changed dramatically. Would love to get a
little help from someone who works with Java packages on a more regular
basis.
Taking a look
This is just about strings, right? So something like this will fix the
problem
and resolve this bug? Or am I missing something?
char buf[L_BUF_SIZE];
- fscanf(fp, "Rootname: %s\n", buf);
+ fscanf(fp, "Rootname: %L_BUF_SIZE_MINUS_ONEs%\n", buf);
Thanks will fix ASAP.
On Sun, Feb 4, 2018 at 3:08 PM, Andreas Beckmann wrote:
> Package: tesseract-ocr-srp-latn
> Version: 4.00~git15-45ed289-5
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package is no longer
-src install python3-coverage on both
debian stable as well as ubuntu artful/bionic ( see ubuntu bug :
https://bugs.launchpad.net/ubuntu/+source/python-coverage/+bug/1744365 )
( In the case of ubuntu bionic, there is some complaining about
python3-sphinxcontrib.spelling as well but that might be out
I've just uploaded a fix attempt for bug 884903 with Tesseract
4.00~git2188-cdc35338-2. I think it will fix this problem.
We'll get this fixed upstream, and in the meantime I'll try patch enough
into
the Debian package to get the dependencies to build. For gimagereader,
that's a single string -> std::string
Taking a look.
On 10/12/17 17:24, Laurent Bigonville wrote:
> We are trying to remove the old goocanvas library out of buster.
I know:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785553#35
I've just uploaded libgoocanvas2-perl to NEW:
https://ftp-master.debian.org/new.html
Now I've got to find some cod
On Fri, Jul 14, 2017 at 08:58:17 +0200, Axel Beckert wrote:
> Hi Jeff,
>
> I'm not sure if you've already seen this bug report against guilt in
> Debian: https://bugs.debian.org/865576
I haven't. Thanks for forwarding it to me.
> But since I saw no new commits s
r: [Errno 2] No such file or directory: '/tmp/tmpZDO8j6/live'
Thanks for your attention to this matter,
Jeff
-- System Information:
Debian Release: 9.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-3-rt
Package: certbot
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
test -x /usr/bin/certbot -a \! -d /run/systemd/system && perl -e 'sleep
int(rand(3600))' && certbot -q renew
* What exactly did you do (or not do) that was effective (o
If you know who to ask and are willing, I appreciate it.
Otherwise, I'll figure it out eventually.
Yes, I concur. I also checked with upstream (myself) and he agrees too.
On Fri, Mar 10, 2017 at 9:28 AM, Mattia Rizzolo wrote:
> Source: jablicator
> Version: 1.0.1
> Severity: serious
>
> Dear maintainer,
>
> The package doesn't seem to have much popularity these days, with a
> popcon of only 2
Ubuntu may have the patch for this. If so, okay to NMU.
https://patches.ubuntu.com/libw/libwebp/libwebp_0.5.1-2ubuntu1.patch
On Sun, Oct 30, 2016 at 08:09:21PM -, Philip Oakley wrote:
> > It is documented (Documentation/git-sh-setup.txt), and this is not the
> > internal Documentation/technical section of the documentation, so my
> > default assumption would be that everything shown there is intended as
> > public.
IRC people tell me that a transition bug will fix everything. There is
an existing transition bug #815919.
jbreiden: Just report a transition bug for release.debian.org to
+transition back
So they rebuild the stuff against the old ABI again
Thanks for working with me and sorry about the trouble.
I don't know what you mean by not closing bug #815056
properly. The bug tracker says it is closed.
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=tesseract
If I look at the package tracking system, it seems to be claiming
It must be mad that there is no libtesseract4 anymore. I'm going
to try to get help for that on IRC.
Yikes. I wasn't expecting this for mhonarc 2.6.19. Patches from a perl
programmer appreciated. Will also check with upstream.
I'm in over my head, so I asked for help. The folks on debian-devel
IRC channel advised me to not bump soname and instead attempt
an ABI repair. It was supposed to be harmless to gimagereader.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815056
I'm really not sure what to do at this point.
> There was an accidental ABI breakage a while ago
> And I thought that bumping to libtesseract4 was the right thing to do
...
The important question is: How did this ABI break happen?
Upstream change or only an effect of the C++ transition?
> I had been assuming upstream change
> But actually I
Why? I was asked strongly by a Debian Developer in 794489 to
bump the libtesseract version. I suspect 742027 was related.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794489
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742027
I historically have a lot of trouble with transitions, and th
I'd like to think if this were widespread, I'd be hearing about it
from multiple sources. So any sort of confirmation (or refutation)
from others is appreciated.
That's unexpected. Can you please tell me if you also have trouble with
English using the attached image?
tesseract phototest.tif -
Using apt-rdepends -r libtesseract3, I think the affected packages are
gimagereader and libsikuli-script-jni.
>could you please comment on Juliens mail? Do you plan to
>do the proposed changes?
Depends how many packages are affected. Transitions are
a bunch of work, and I think we are also in some special
situation due to the GCC transition. So if it is just one binMNU
then I think that might be the way t
Sounds right to me. My bad.
Thanks, I'll investigate today.
Sorry, I was under the impression upsteam had integrated the patch. NMU
acceptable, or I can do it when I find time.
Thank you for the investigation, and please NMU. I'm not literally
underwater
right now, but I'm also not that far off from it.
elsewhere and then importing that
into Flumotion via the Admin UI. I'm still testing this under Ubuntu 14.04.
This of course may break things elsewhere that depend on Twisted Python too.
Cheers,
Jeff.
his exception to your version of the
| file, but you are not obligated to do so. If you do not wish to do so, delete
| this exception statement from your version.
[from http://mid.gmane.org/20140722013130.GA14673%40gauss.olasd.eu]
Jeff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.o
Thanks for escalating, I will attempt fix well before autoremoval deadline.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: openssl
Version: 1.0.1e-2+deb7u7
Severity: grave
Tags: security upstream
Justification: user security hole
Plese see
https://www.openssl.org/news/secadv_20140605.txt
for more information.
-Jeff
-- System Information:
Debian Release: 7.5
APT prefers stable
APT policy: (500
ppening with kernel 9.2? I can't see that in the
buildd logs. I only have a 9.0 kernel to test on...
Jeff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 03/31/2014 07:29 AM, Axel Beckert wrote:
> From my point of view it does not render the package generally
> unusable, just for the case where the server is an significantly older
> version.
>
> Then again, the case with Jessie and Wheezy is likely no seldom one,
> so I think if there's a chance
Package: tesseract-ocr
Version: 3.03.02-3
I can't reproduce this. Please run ldd and md5sum on /usr/bin/tesseract
and report the results.
===
$ curl
http://ftp.us.debian.org/debian/pool/main/t/tesseract/tesseract-ocr_3.03.02-3_i386.deb>
foo.deb
$ ar x foo.deb
$ tar xJvf data.tar.xz
$ ldd usr/bin
Package: tesseract-ocr
Version: 3.03.02-3
This is unexpected. The build dependency is on libleptonica-dev (>= 1.70~)
which is leptonlib4. I don't see how or where a leptonlib3 could be
sneaking in.
Thank you for the problem report.
I will adjust the dependency.
No problem. Will send it over in a few hours.
On Thu, Jan 9, 2014 at 5:14 PM, Andrew Bartlett wrote:
> On Fri, 2014-01-10 at 12:12 +1300, Andrew Bartlett wrote:
>> On Thu, 2014-01-09 at 16:04 -0600, Jeff Clark wrote:
>> > Samba needs the hdb plugin updated to sup
Samba needs the hdb plugin updated to support hdb version 8.
Heimdal needs the hdb callback function patched because even when the
plugin is registered properly, it segfaults because the pointer is never
set properly in _krb5_plugin_run_f. Looks like the plugin code was
recently updated but never
On 12/02/2013 08:37 AM, Jeff Fearn wrote:
> On 12/01/2013 06:07 AM, Raphael Hertzog wrote:
>> Hello Jeff,
>>
>> On Mon, 18 Nov 2013, Jeff Fearn wrote:
>>> Hi, I've checked in a patch for this. If someone can test it for me I'd
>>> appreciate it.
On 12/01/2013 06:07 AM, Raphael Hertzog wrote:
> Hello Jeff,
>
> On Mon, 18 Nov 2013, Jeff Fearn wrote:
>> Hi, I've checked in a patch for this. If someone can test it for me I'd
>> appreciate it.
>>
>> https://github.com/jfearn/XML-TreeBuilder/comm
Hi, I've checked in a patch for this. If someone can test it for me I'd
appreciate it.
https://github.com/jfearn/XML-TreeBuilder/commit/d81004996dae0f123a77af2c79576e7977559dc0
Cheers, Jeff.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of &q
On 11/07/2013 06:32 PM, Raphael Hertzog wrote:
> Control: reassign -1 libxml-treebuilder-perl 5.0-1
> Control: severiy -1 serious
> Control: affects -1 + publican
>
> Hi,
>
> On Thu, 07 Nov 2013, Petr Vanek wrote:
>> Thank you Jeff. Please correct me if i am wrong
).
1.7 is a "feature" release. OMPI 1.odd.x series are stable and tested; they're
just not as time-tested out in the real world as OMPI 1.even.x series.
We're anticipating 1.8 will be out in early 2014.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go
https://bugs.launchpad.net/nova/+bug/1177830/comments/21
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
t be worth
valgrinding it on Linux. (unfortunately I can't do this at the moment;
if I get a chance I'll report the results here)
Jeff
signature.asc
Description: Digital signature
m /lib/x86_64-kfreebsd-gnu/libpthread.so.0
#8 0x in ?? ()
possibly getting the segv is more common than the hang? I haven't managed to
get the hang once using this break-and-signal-in-gdb methodology (amd64
kfreebsd sid/wheezy).
Jeff
--
To UNSUBSCRIBE, email to debian-b
at package.
Jeff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
oups() and initgroups() are seen "in
the wild", programs that depend on the linux kernel behavior are
broken and should be fixed as they become known.
Personally I'm leaning towards 3 here, since these are buggy not only on
debian/kFreeBSD but on real FreeBSD as well.
't yet in
production, so if there's an alternate fix proposed soon I'll be happy
to test it out. On the other hand, I think the presence or absence of
the implicit declaration warning is enough to indicate whether the bug
is present under any given fix...
Jeff
--
To UNSUBSCRIBE
use of reallocf will result in a link
error without -lbsd.
You can't simply make the bsd header be included via #include , as
-I/usr/include/bsd on the gcc commandline leads to a recursive inclusion error.
Jeff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a s
her idea ?
>
> cupsd could temporarily drop privileges to lp when reading log files;
> with that you are restricted to reading world-readable files as well
> as cups' own files, which should be fine?
I suspect this fix would end up in a game of "whack-a-mole", as we find
int
Control: found -1 1.4.4-7+squeeze1
On 11/10/2012 06:48 AM, Didier 'OdyX' Raboud wrote:
> I have successfully used your exploit script on the Sid version, tagging as
> found there.
Just to complete the picture, I tried the exploit on squeeze, and it
works there too.
--
To UNSUBSCRIBE, email to
Tesseract uploading now. We'll see how this goes.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Leptonica upload commencing now. Tesseract coming.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Yes, I can sponsor. My goal is to not get in the way of your energy,
but also be careful to keep the level of chaos under control. The
inclusion of Leptonica and Tesseract must not be jeopardized.
Jakub, you are welcome to weigh in on this bug if you wish.
--
To UNSUBSCRIBE, email to debian-bug
1 - 100 of 228 matches
Mail list logo
