Bug#993350: [sane-devel] Epson Perfection1640 and the epson2 backend: summary
Hi, > 1) This started out with focus problems. >I appear to have confirmed that the 1640 accepts, but ignores, focus >commands, so the current version of the backend >(commit 3b47d1d26a73054b7138759fa7af57ed6c8e8e35 (HEAD -> master, > origin/master, origin/HEAD) >with dev->focusSupport = SANE_FALSE is correct. Thanks for confirming! > 2) The > --film-type Positive Film|Negative Film|Positive Slide|Negative Slide >includes the Slide options which I suspect are not available on >the 1640SU. They result in something like invalid parameter messages. Confirmed. I can reproduce this with my 1640SU. I don't really know where the "Slide" come from or what they actually do. I need to dig in a little further. In about two weeks, I can also double check if a 12000XL does support the "Slide" options. > 3) There is a failure to transfer larger scans: perhaps a counter >overflowing. So a significant bug. I still need to reproduce this one. But I'd think this is easy to reproduce. > 4) Using xsane, and [cancel]ing during a scan fails. It is usually >necessary to restart the 1640. I have only mentioned this bug in >passing in previous messages. I had this, too, on my 1640SU. I seem to recall that it worked fine on the 12000XL. I'll cross-check this as well. > I hope this is helpful in following the earlier messages, especially > the first few when things were not so clear. Thanks again for your investigations! Much appreciated! Kind regards, Wolfram signature.asc Description: PGP signature
Bug#993350: Epson Perfection1640: Slide scan fails
> I have had a very quick skim of epson2.c and a couple of other files. > I can see a DBG macro which seems to be defined in sanei_debug.h > but I am not sure how to invoke it just yet. SANE_DEBUG_EPSON2= xsane Sorry, I am stuffed with work currently. I'll try to check your other mails until the weekend. signature.asc Description: PGP signature
Bug#993350: [sane-devel] Epson Perfection1640: Operation not supported
> It is better in that it no longer crashes, but is still a > regression: I suspect that I can no longer scan films. > > So it seems that commit 580c278dcafe4159213406b4307ee8598fe08fe7 > was too simplistic? It is true that the option is not a boolean anymore but an integer. But still, if you selet the TPU the old default value for 2.5mm above glass (89) should be automatically selected. Without TPU, it should use the default of on glass (64). I tested this on an Epson 12000XL and Perfection1640. Please check if that works on your system as well. signature.asc Description: PGP signature
Bug#993350: [sane-devel] Epson Perfection1640: Operation not supported
> I tried this but I still have xsane Version: 0.999-12 so there was no > change. I couldn't find a newer version of xsane, even in Ubuntu. > Indeed in the Ubuntu pool that I checked, the xsane directory was empty. You need a newer version of libsane than debian testing. Probably packages "libsane-common" and friends. The xsane version can stay the same. But a quick look tells me that Ubuntu repos won't be useful for you because they also don't have the patch you need. Maybe your best bet is to push Debian maintainers to include the patch I mentioned. They should have it anyhow. Fedora already includes it. signature.asc Description: PGP signature
Bug#971389: seascope: Dependency to 'python3-pyqt5.qtsvg' missing, does not start
Package: seascope Version: 0.9+8a669e0e-2 Severity: grave Justification: renders package unusable Dear Maintainer, after upgrading to bullseye, starting seascope failed for me: No module named 'PyQt5.QtSvg' Error: failed to import supporting packages. Error: program aborted. After installing python3-pyqt5.qtsvg manually, the program worked fine. Kind regards, Wolfram -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages seascope depends on: ii python3 3.8.2-3 ii python3-pyqt5 5.15.0+dfsg-1+b1 ii python3-pyqt5.qsci 2.11.2+dfsg-7 Versions of packages seascope recommends: ii cscope 15.9-1 ii exuberant-ctags 1:5.9~svn20110310-13 ii id-utils 4.6.28-20200521ss15dab+b1 seascope suggests no packages. -- no debconf information
Bug#646467: supposed fix
tags 646467 patch thanks -- Pengutronix e.K. | Wolfram Sang| Industrial Linux Solutions | http://www.pengutronix.de/ | From: Wolfram Sang w.s...@pengutronix.de Subject: fix '-Werror=format-security' flaw We won't have format specifiers, so simply use fputs. This patch applies to the current debian version and upstream master as well (with offset). Signed-off-by: Wolfram Sang w.s...@pengutronix.de --- debug.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: src/debug.c === --- a/src/debug.c +++ b/src/debug.c @@ -28,7 +28,7 @@ void print_message_to_stderr(const char va_start(va, fmt); vsnprintf(msg, PATH_MAX, fmt, va); va_end(va); - fprintf(stderr, msg); + fputs(msg, stderr); } #ifdef DEBUG signature.asc Description: Digital signature
Bug#643363: fix format not a string literal and no format arguments issue
Debian has a release-critical bug filed against your project [1], because
'-Werror=format-security' [2] is used there to harden included software. The
following manually created patch is a standard way of resolving the bug, but
since I don't use your software I could not actually test it. It would be kind
of you if you could evaluate if this patch is applicable.
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643363
[2]
http://wiki.debian.org/Hardening#DEB_BUILD_HARDENING_FORMAT_.28gcc.2BAC8-g.2B-.2B-_-Wformat_-Wformat-security_-Werror.3Dformat-security.29
Signed-off-by: Wolfram Sang w.s...@pengutronix.de
--- CbcOrClpParam.cpp.orig 2011-12-03 17:15:35.0 +0100
+++ CbcOrClpParam.cpp 2011-12-03 17:16:39.0 +0100
@@ -1079,7 +1079,7 @@
}
#else
if (CbcOrClpReadCommand == stdin) {
- fprintf(stdout, coin_prompt);
+ fputs(coin_prompt, stdout);
fflush(stdout);
}
where = fgets(line, 1000, CbcOrClpReadCommand);
--
Pengutronix e.K. | Wolfram Sang|
Industrial Linux Solutions | http://www.pengutronix.de/ |
signature.asc
Description: Digital signature
Bug#593869: Can't reproduce
I can't reproduce this on my up-to-date squeeze system (with custom 2.6.36-rc4 kernel, i686). I also tried uninstalling gstreamer-alsa, still works. I do see all the warnings before the segmentation fault, but not the fault itself. What soundcard do you have (Intel 82801DB/DBL/DBM here)? Are there sound issues with other programs? Cheers, Wolfram -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538822: Bitten, too
I have also been bitten by this, although I don't know if my local modifications will classify it as a bug: I switched very early to dash by simply changing the /bin/sh-symlink by hand (it ought to be a test). I totally forgot that I did it this way until the upgrade to squeeze yesterday. The symptoms were the same as in message #5. The solution was given in message #134 (thanks a lot!). Removing the divert and restoring the original /bin/sh-symlink solved the problem for me. I could continue upgrading, although /bin/sh was pointing to bash afterwards. Regards! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509355: cpufreqd: segfault while reading acpi battery info
Hello, maybe I can add a bit of information: On Mon, Dec 22, 2008 at 06:54:56AM +0900, Mattia Dongili wrote: On Sun, Dec 21, 2008 at 04:40:28PM +0100, Jonas Zeiger wrote: Package: cpufreqd Version: 2.3.3-3 Severity: grave Justification: renders package unusable I've been trying to run cpufreqd on a Dell Latitude D530 Laptop with a Intel Core2Duo 2.00Ghz CPU, 3GB of DDR2 RAM and two attached battery units using the stock Debian kernel version 2.6.26, but the problem is exactly the same with my custom kernel 2.6.26zlinux (tuned for install on SSD). I have a pretty similar laptop (D530, 2x 2GHz, 2GB RAM, but just one battery). I am running the standard lenny kernel at the moment. I installed cpufreqd to verify this problem, but it does not occur here. So my guess is that it has to do with the second battery... acpi_battery_update : BAT1 - present acpi_battery_update : BAT1 - estimating battery life (timeout: 30.00 - status: (null)) Speicherzugriffsfehler /* german locale, it' a segfault! :( */ ... which seems to get seconded by the status: (null) above (Broken pointer?). To Jonas: What does 'cat /sys/class/power_supply/BAT1/status' print after/before you get this segfault? This is how it looks here: === acpi_battery_update : BAT0 - present acpi_battery_update : BAT0 - estimating battery life (timeout: 28.00 - status: Discharging ) acpi_battery_update : BAT0 - remaining capacity: 5199147 acpi_battery_update : battery life for BAT0 is 112% acpi_battery_update : average battery life 112% === Kind regards, Wolfram -- Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry signature.asc Description: Digital signature
Bug#505278: lockfile-progs: lockfile-create locks the file even if it already exists
Hello Manuel, I found a bug in liblockfile1, which makes a lockfile stale after 10 seconds instead of 5 minutes (#505851). So, please report if the fix mentioned there also solves your problem, then we can merge and close this bug. All the best, Wolfram -- Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry signature.asc Description: Digital signature
Bug#505851: liblockfile1: Lockfiles get stale after 10 seconds instead of 5 minutes
Package: liblockfile1 Version: 1.08-2 Severity: grave Tags: patch Justification: might cause serious data loss The lockfile_create-function still contains some debug code, which considers a lock stale after 10 seconds instead of 5 minutes. As the documentation suggests refreshing the lock every 60 seconds, programs might lose the lock unexpectedly. Found while researching #505278. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages liblockfile1 depends on: ii libc6 2.7-13 GNU C Library: Shared libraries liblockfile1 recommends no packages. liblockfile1 suggests no packages. -- no debconf information *** /home/wsa/Tools/liblockfile-1.08/patches/remove_debug_code --- lockfile.c |7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) Index: liblockfile-1.08/lockfile.c === --- liblockfile-1.08.orig/lockfile.c +++ liblockfile-1.08/lockfile.c @@ -391,13 +391,10 @@ int lockfile_check(const char *lockfile, * Without a pid in the lockfile, the lock * is valid if it is newer than 5 mins. */ -#if 0 + if (now st.st_mtime + 300) return 0; -#else - if (now st.st_mtime + 10) - return 0; -#endif + return -1; } -- Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry signature.asc Description: Digital signature
