Bug#730539: libsane: HP psc 750 no longer being recognized
reassign 730539 hplip
tags 730539 patch
thanks
Lawrence Woodman lwood...@vlifesystems.com writes:
Can you remove the scanner device, and reinsert it while running
strace -o /tmp/udev-strace.out -f -p UDEVDPROCESSID
where, of course, UDEVDPROCESSID is the pid of udevd, and send
/tmp/udev-strace.out. I have three udevd's running on my system, though,
and I'm not sure why or which one does what...
I only have the one udevd and have attached the output of this command.
The problem is that the hp-config_usb_printer command is taking too
long, and udevd kills the worker handling the device insertion, so it
never gets to the part of the udev rules that allow access by the
scanner group or, for that matter, the active console user. See
https://bugs.launchpad.net/hplip/+bug/1185866 for more details.
A fix given there is to modify /lib/udev/rules.d/56-hpmud.rules to
change
/usr/bin/hp-config_usb_printer $env{BUSNUM}:$env{DEVNUM} ; fi
to
/usr/bin/hp-config_usb_printer $env{BUSNUM}:$env{DEVNUM} /dev/null 21
/dev/null fi
Patch from Gentoo attached.
--
Mark Buda her...@acm.org
I get my monkeys for nothing and my chimps for free.
--- data/rules/56-hpmud.rules 2013-11-30 10:17:19.113763341 +0100
+++ data/rules/56-hpmud.rules 2013-11-30 10:18:53.530770075 +0100
@@ -12,7 +12,7 @@
# This rule will add the printer and install plugin
-ENV{hp_test}==yes, PROGRAM=/bin/sh -c 'logger -p user.info loading HP Device $env{BUSNUM} $env{DEVNUM}', RUN+=/bin/sh -c 'if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start hplip-printer@$env{BUSNUM}:$env{DEVNUM}.service; else /usr/bin/nohup /usr/bin/hp-config_usb_printer $env{BUSNUM}:$env{DEVNUM} ; fi'
+ENV{hp_test}==yes, PROGRAM=/bin/sh -c 'logger -p user.info loading HP Device $env{BUSNUM} $env{DEVNUM}', RUN+=/bin/sh -c 'if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start hplip-printer@$env{BUSNUM}:$env{DEVNUM}.service; else /usr/bin/nohup /usr/bin/hp-config_usb_printer $env{BUSNUM}:$env{DEVNUM} /dev/null 21 /dev/null fi'
# If sane-bankends is installed add hpaio backend support to dll.conf if needed.
ENV{sane_hpaio}==yes, RUN+=/bin/sh -c 'grep -q ^#hpaio /etc/sane.d/dll.conf;if [ $$? -eq 0 ];then sed -i -e s/^#hpaio/hpaio/ /etc/sane.d/dll.conf;else grep -q ^hpaio /etc/sane.d/dll.conf;if [ $$? -ne 0 ];then echo hpaio /etc/sane.d/dll.conf;fi;fi'
Bug#730539: libsane: HP psc 750 no longer being recognized
Lawrence Woodman lwood...@vlifesystems.com writes: strace -o /tmp/udev-strace.out -f -p UDEVDPROCESSID where, of course, UDEVDPROCESSID is the pid of udevd, and send /tmp/udev-strace.out. I have three udevd's running on my system, though, and I'm not sure why or which one does what... I only have the one udevd and have attached the output of this command. udevd appears to be killing the child process handling the device insertion at or near line 1352 of udev.c (current jessie version) before it ever gets to running setfacl. I don't know why yet, but this is probably the root of the problem. -- Mark Buda her...@acm.org I get my monkeys for nothing and my chimps for free. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738592: /usr/bin/scanimage: Canon LiDE 30 not working on Jessie (is working on wheezy)
Tuxicoman deb...@jesuislibre.net writes: Unfortunately i don't have any usb2 hub Even if you had a USB 2 hub, if you connected it to a USB 3 port it would still have the same problem, from what I have read. I'm unable to scan on any of my USB port. I tested all USB ports on a new laptop which has Jessie up to date and I can't scan neither. There is a kernel patch here which has been reported by some people to fix the issue, but it is not well tested and apparently has some problems: http://www.mail-archive.com/linux-usb@vger.kernel.org/msg30015.html Sarah Sharp on the linux-usb list seems to have taken on the task of finishing it. -- Mark Buda her...@acm.org I get my monkeys for nothing and my chimps for free. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738592: /usr/bin/scanimage: Canon LiDE 30 not working on Jessie (is working on wheezy)
Tuxicoman deb...@jesuislibre.net writes: [stuff...] [261225.271449] usb 1-11: new full-speed USB device number 11 using xhci_hcd [stuff...] There is a reported bug in SANE 1.0.24 with the plustek backend not working with USB 3.0. This is SANE bug 314545 and also seems to be Ubuntu Launchpad bug 1250196. A similar issue may be in Fedora 19: http://zurlinux.com/?p=1733. If you could run export SANE_DEBUG_PLUSTEK=128 export SANE_DEBUG_DLL=128 export SANE_DEBUG_USB=128 scanimage -L /tmp/scanimage.out 21 then if egrep could not read version register /tmp/scanimage.out finds anything, that would confirm that you are experiencing the same issue. Otherwise, please provide the scanimage.out file. Also, if you could try the scanner with a USB 2.0 hub and sane-backends 1.0.24, that would be good information. -- Mark Buda her...@acm.org I get my monkeys for nothing and my chimps for free. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730539: libsane: HP psc 750 no longer being recognized
Lawrence Woodman lwood...@vlifesystems.com writes: On 08/02/14 02:13, Mark Buda wrote: Or, it *did* happen, but something else changed it. What version of the hal package do you have installed? I'm using version: 0.5.14-8 Well now I am really confused. The ACLs on the USB device do not include group:scanner:rw- or user:whoeveryouare:rw-, which means that either (a) both the call to setfacl and the internal uaccess builtin failed, or (b) something afterwards reset the ACL. But the only thing after that is the HAL notification. But according to the changelog, they dropped ACL support in HAL in 0.5.13-4. Squeeze had 0.5.14-3, so the only thing I can think of is that you originally installed a pre-squeeze release, upgraded, and during the course of the upgrade, the hal-acl-tool program (which is no longer included) didn't get deleted, nor did the configuration files that tell HAL to run it and (if I'm reading the code correctly) delete pre-existing ACLs. I'm pretty sure this is not a SANE bug, but I don't know whose it is. Did you originally install a pre-squeeze release on this system? Do the files hal-acl-tool or 20-acl-management.fdi exist on your system? I'm not sure where they would live. Can you remove the scanner device, and reinsert it while running strace -o /tmp/udev-strace.out -f -p UDEVDPROCESSID where, of course, UDEVDPROCESSID is the pid of udevd, and send /tmp/udev-strace.out. I have three udevd's running on my system, though, and I'm not sure why or which one does what... I will set up a VM running an old-enough Debian release and see what happens regarding HAL's ACL treatment when I upgrade. -- Mark Buda her...@acm.org I get my monkeys for nothing and my chimps for free. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730539: libsane: HP psc 750 no longer being recognized
On 31/01/14 13:07, Mark Buda wrote: The group id for the scanner device should be 'lp', but there should be a read/write ACL entry for 'scanner', and there isn't. The udevadm test output showed that it should have tried to make one, but apparently that didn't happen for some reason. Or, it *did* happen, but something else changed it. What version of the hal package do you have installed? -- Mark Buda her...@acm.org I get my monkeys for nothing and my chimps for free. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730539: libsane: HP psc 750 no longer being recognized
Adding the bug back into the Cc: list. Lawrence Woodman lwood...@vlifesystems.com writes: Funnily enough I meant to include the stderr output but forgot. The full output is attached. Also helpful would be the output of ls -lL /dev/bus/usb/002/005 devname changed so: crw-rw-r-- 1 root lp 189, 133 Jan 30 14:16 /dev/bus/usb/002/006 and getfacl /dev/bus/usb/002/005 getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/002/006 # owner: root # group: lp user::rw- group::rw- other::r-- From the above I could see that the group for the device was 'lp', which my user wasn't a member of. I put my user into this group and it all works fine now. So an open question for me is why this should suddenly become an issue and whether the group for the scanner usb device should be 'lp' or 'scanner'. The group id for the scanner device should be 'lp', but there should be a read/write ACL entry for 'scanner', and there isn't. The udevadm test output showed that it should have tried to make one, but apparently that didn't happen for some reason. Try running as root setfacl -m g:scanner:rw /dev/bus/usb/002/006 getfacl /dev/bus/usb/002/006 or whatever the devname currently is. If it shows a line like group:scanner:rw- then the problem is that udev isn't running setfacl for some reason or that it is failing due to something different in its environment. If it produces an error, then that's probably the cause. -- Mark Buda her...@acm.org I get my monkeys for nothing and my chimps for free. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730539: libsane: HP psc 750 no longer being recognized
Lawrence Woodman lawre...@intheforest.plus.com writes: I just did a scan as root, which worked perfectly. Make sure the user you are scanning as is a member of the scanner group. If that doesn't resolve it, please provide the output of this command, run as root, with the scanner connected, so I can (hopefully) figure out what udev rule is causing the permissions problem: udevadm test $(dirname $(egrep -l 1511 /sys/bus/usb/devices/*/idProduct)) -- Mark Buda her...@acm.org I get my monkeys for nothing and my chimps for free. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736820: libnet-frame-perl: package seems to depend on things that are not packaged
Package: libnet-frame-perl Version: 1.09-1 Severity: grave Justification: renders package unusable This package seems to expect Net::Frame::Device and Net::Frame::Simple (at least) to exist, but they are not packaged as far as I can tell. -- System Information: Debian Release: 7.3 APT prefers stable APT policy: (990, 'stable'), (800, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnet-frame-perl depends on: ii dpkg 1.16.12 ii libbit-vector-perl7.3-1+b1 ii libclass-gomor-perl 1.02-1 ii libnet-ipv6addr-perl 0.2.dfsg.1-3 ii libsocket6-perl 0.23+ds-0+nmu1 ii perl 5.18.2-2 libnet-frame-perl recommends no packages. libnet-frame-perl suggests no packages. -- no debconf information -- Mark Buda her...@acm.org I get my monkeys for nothing and my chimps for free. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729605: isc-dhcp-client: under kfreebsd, can't have two interfaces configured with dhcp
Package: isc-dhcp-client Version: 4.2.4-7 Severity: normal Tags: upstream Dear Maintainer, Under kfreebsd, if I configure a second interface to use DHCP, the client fails because it can't bind a socket to port 68, because it's in use. The code sets the SO_REUSEADDR socket option, which works fine under Linux, but FreeBSD requires that the SO_REUSEPORT option be set. (I'm not sure whether they are both required, or just the latter.) This is still the case in the current upstream version, 4.2.5-P1. Script started on Thu 14 Nov 2013 04:35:10 PM EST hermit@gammaflex:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo0 iface lo0 inet loopback # The primary network interface auto em0 iface em0 inet dhcp iface em1 inet dhcp hermit@gammaflex:~$ sudo ifup em1 [sudo] password for hermit: Internet Systems Consortium DHCP Client 4.2.4 Copyright 2004-2012 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on BPF/em1/00:0c:29:77:90:47 Sending on BPF/em1/00:0c:29:77:90:47 Can't bind to dhcp address: Address already in use Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. Failed to bring up em1. hermit@gammaflex:~$ netstat -an | egrep '\.68' udp4 0 0 *.68 *.* hermit@gammaflex:~$ ps auwwx | egrep dhclient hermit1953 0.0 0.6 7736 1568 ?S+ 16:35 0:00 egrep dhclient root 968 0.0 1.9 9712 4568 ?Ss 16:27 0:00 dhclient -v -pf /run/dhclient.em0.pid -lf /var/lib/dhcp/dhclient.em0.leases em0 hermit@gammaflex:~$ Script done on Thu 14 Nov 2013 04:35:49 PM EST -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.2-1-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages isc-dhcp-client depends on: ii debianutils 4.4 ii inetutils-ping 2:1.9.1.306-0a482-1 ii isc-dhcp-common 4.2.4-7 ii libc0.1 2.17-93 isc-dhcp-client recommends no packages. Versions of packages isc-dhcp-client suggests: pn avahi-autoipd none pn resolvconf none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728292: RFS: sane-backends/1.0.24-1 [ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package sane-backends Package name: sane-backends Version : 1.0.24-1 Upstream Author : numerous * URL : http://www.sane-project.org * License : GPL, with exceptions for some code that makes it less restrictive Section : graphics It builds those binary packages: libsane- API library for scanners libsane-common - API library for scanners -- documentation and support files libsane-dbg - API development library for scanners [debug symbols] libsane-dev - API development library for scanners [development files] sane-utils - API library for scanners -- utilities To access further information about this package, please visit the following URL: http://mentors.debian.net/package/sane-backends Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/sane-backends/sane-backends_1.0.24-1.dsc More information about sane-backends can be obtained from http://www.sane-project.org. Changes since the last upload: sane-backends (1.0.24-1) unstable; urgency=low * New upstream version. * New maintainer (Closes: 688531) -- Mark Buda her...@acm.org Sat, 26 Oct 2013 13:04:13 -0400 Regards, Mark Buda -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688531: ITA: sane-backends -- API library for scanners -- utilities
package wnpp retitle 688531 ITA: sane-backends -- API library for scanners -- utilities quit Sent from my iPad
Bug#725338: libsane: new upstream release (1.0.24) available
Package: libsane Version: 1.0.23-3 Severity: wishlist Tags: upstream Since the package appears to be orphaned and I want my fancy new Canon multifunction printer scanning over the network, I'll get the new release working and see about getting it uploaded if no one else is doing it. Maybe even adopt it. I know a thing or two about scanners. I've wanted to contribute to Debian for years, but just about every time I wanted something done, somebody else had already done it. -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (990, 'stable'), (800, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libsane depends on: ii acl2.2.51-8 ii adduser3.113+nmu3 ii libavahi-client3 0.6.31-2 ii libavahi-common3 0.6.31-2 ii libc6 2.17-92 ii libcups2 1.6.3-1 ii libexif12 0.6.20-3 ii libgphoto2-2 2.4.14-2 ii libgphoto2-port0 2.4.14-2 ii libieee1284-3 0.2.11-10 ii libjpeg8 8d-1 ii libsane-common 1.0.23-3 ii libtiff4 3.9.6-11 ii libusb-1.0-0 2:1.0.11-1 ii libv4l-0 0.8.8-3 ii multiarch-support 2.13-38 ii udev 175-7.2 Versions of packages libsane recommends: pn libsane-extras none ii sane-utils 1.0.23-3 Versions of packages libsane suggests: ii avahi-daemon 0.6.31-2 pn hplip none pn hpoj none -- Configuration Files: /etc/sane.d/pixma.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#257142: makedepend appears to hardcode gcc-version-dependent include paths
I hit this problem with xutils 4.3.0.dfsg.1-14, only it was complaining about not being able to find /usr/lib/gcc-lib/i486-linux/3.3.6/include/stddef.h when the file was actually in /usr/lib/gcc-lib/i486-linux/3.3.5/include/stddef.h. % strings `which makedepend` | egrep gcc-lib /usr/lib/gcc-lib/i486-linux/3.3.6/include After upgrading to xutils 4.3.0.dfsg.1-14sarge1: % strings `which makedepend` | egrep gcc-lib /usr/lib/gcc-lib/i486-linux/3.3.5/include It looks like makedepend figures out the gcc include path at compile time. Also, although this is tagged upstream, a search for makedepend on bugs.xfree86.org didn't yield anything that looks like this bug. -- Mark Buda [EMAIL PROTECTED] I get my monkeys for nothing and my chimps for free. pgpzh78O0x60e.pgp Description: PGP signature
Bug#352447: blackbox: can't rename workspaces
Package: blackbox Version: 0.70.1-1 Severity: normal blackbox(1) says: To name a workspace the user must right click on the toolbar, select Edit current workspace name, type the workspace name, And_Press_Enter to finish. When I right click on the toolbar, I get a Toolbar Options menu with no such entry, and when I look at the source, it doesn't appear to be implemented at all. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (400, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.11-1-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages blackbox depends on: ii libc62.3.5-8 GNU C Library: Shared libraries an ii libfontconfig1 2.3.1-2 generic font configuration library ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib ii libgcc1 1:4.0.2-5 GCC support library ii libstdc++6 4.0.2-5 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14 X Window System miscellaneous exte ii libxft2 2.1.7-1 FreeType-based font drawing librar ii libxrender1 1:0.9.0.2-1 X Rendering Extension client libra ii xlibs4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime -- no debconf information -- Mark Buda [EMAIL PROTECTED] I get my monkeys for nothing and my chimps for free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
