In current cauldron, xsane run under a normal user reports no devices, even if the user is in the saned and scanner groups. Run as root, it runs normally (although it grouses about running as root). Probably some dbus error with the ownership or permissions of the USB device created for the scanner. This is an HP all-in-one 3030 which has been working under MGA since forever. Reproducible: Steps to Reproduce:
Possibly a reincarnation of bug#10475.
Assigning to new sane maintainer.
Assignee: bugsquad => lists.jjorge
> In current cauldron, xsane run under a normal user reports no devices, even if > the user is in the saned and scanner groups. > Run as root, it runs normally (although it grouses about running as root). Exactly same here, with HP5520 All-in-One. (Also, HPLIP reports 'Comunication Error', no status, supplies info) [In both cases, with printer switched on.]
CC: (none) => maurice
saned 1.0.25 has landed in cauldron. Does the bug still exist?
Keywords: (none) => NEEDINFOStatus: NEW => ASSIGNED
Just done Cauldron update, but rpm -qif /usr/bin/xsane shows: Name : xsane Version : 0.999 Release : 7.mga6 Architecture: x86_64 Install Date: Tue 15 Sep 2015 16:31:59 BST Group : Graphics/Scanning Size : 5130515 License : GPLv2+ Signature : RSA/SHA1, Mon 14 Sep 2015 20:55:12 BST, Key ID b742fa8b80420f66 Source RPM : xsane-0.999-7.mga6.src.rpm - and problem is still there.
Ping ?
I don't have currently a running Cauldron system. I will watch this if no one else does when an ISO will be ready.
W.r.t to Comment 3 above, I now have exactly the same situation with Mageia-5 (fully updated)! (Another recent change: Dropbox icon no longer appears in Systray...)
Also, here on 64-bit Mageia-6-dev1, system-config-printer fails to add printer: After: "Your are about to install a software package on your computer: -task-printing-server -task-printing-hp" this msg appeared: "Some requested packages cannot be installed: libgirepository1.0-1.48.0-1mga6.i586 (due to unsatisfied: gobject-introspection-1.48.0-1.mga6.i586)" After I ignored 'Abort' option it installed several packages (including CUPS) and then ended without installing printer. No sign of HP Device Manager; CUPS will not start. Attempts to re-install end without progress.
Created attachment 7613 [details] Diagnostic output from HP Device Manager
N.B. Attachment 7613 [details] above applies to the situation with same printer on desktop Mageia-5. Note also: I have now installed the same HP5520 on new laptop's fresh install of Mageia-5, fully updated. Result: (1) HP device Driver reports 'Communication Error', no status or supplies info (2) CUPS sees printer, and prints (3) Xsane finds HP5520 scanner first time, and consistently! ==========================
Created attachment 7614 [details] Laptop output from HP Device Manager diagnostics Here is similar HP diagnostics from laptop. N.B. Xsane does find same scanner!
Tried installing HP5520 printer/scanner on fresh install of latest 64-bit Mageia-6-dev1 .iso in Plasma login on real h/w (nVidia). This time it did install (using system-config-printer's 'HPLIPoption'), and prints (so CUPS happy), but xsane fails to find the scanner (as it still fails on Mageia-5). HP Device Manager still denied the existence of a printer, both before and after the install by system-config-printer!
With the 2016-5-20 Mageia-6-sta1, Xsane still fails to find the HP5520 scanner - unless run as Root. (HPLIP (HP Device Manager) does now find the printer, but its Status and Supplies options both show "Communication Error" see: https://bugs.mageia.org/show_bug.cgi?id=18507 )
Ditto with 64-bit classic Mageia-6-sta1 of 20/6. (This is on non-EFI non-GPT real h/w (nVidia).)
*** Bug 18817 has been marked as a duplicate of this bug. ***
Why is this NEEDINFO ? The problem is that the device for the scanner is created rw rw r root root. Either it should be owned by a group to which a regular user can be added, or else it should be rw rw rw.
Is there a temporary specific workaround that could be used until this is fixed. Frank? (Not clear how to get at the permissions of "the device for the scanner".)
It's pretty crude, but if you're not in a multiuser situation, chmod 666 /dev/bus/usb -R should do the trick, at least until you reboot.
(In reply to Frank Griffin from comment #19) > It's pretty crude, but if you're not in a multiuser situation, > > chmod 666 /dev/bus/usb -R > > should do the trick, at least until you reboot. Thank, but 'fraid not. :-( Tried logout/login but scanner still not found. (No problem as Root...) (This is on Mageia-5, by the way!)
Didn't work on Mageia-6-sta1, either, I'm afraid... :-(
My bad. Try 777 instead of 666, and of course it has to be done as root. 666 turns off the permission to examine directories.
Ah, that's more like it! Yes, that worked. Pity is only ephemeral...
I just did a Mga6 install and had no issue with a Samsung Xpress M2070RW. Run xsane as user accept the EULA and it's ready to begin scanning. The device is a network connected multi-function printer. I am using vendor supplied driver software.
CC: (none) => cae
The error case involves a locally-attached USB device.
Local old USB attached scanner EPSON PERFECTION 1660 PHOTO is still working perfectly on this computer after online *upgrade* from Mageia 5. ( New on mga6 is a popup saying HPLIP can not access network scanners (and i dont care) ) Anything you want me to check for reference?
CC: (none) => fri
So it looks to be HP-related...
Problem still there with latest Cauldron s/w update on 64-bit KDE Mageia-6, with HP5520 printer/scanner. No problem if start xsane as Root...
Still a problem in Magiea-5 - need to do (as Root): chmod 777 /dev/bus/usb -R Is no there no proper fix in sight yet?
Problem still there with 11/1/17 64-bit KDE Mageia-6-sta2, with HP5520 printer/scanner. No problem if start xsane as Root, or do #chmod 777 /dev/bus/usb -R
Problem still there with latest 64-bit KDE Mageia-6-sta2, with HP5520 printer/scanner. (Although other problems with that printer/scanner have now disappeared...) No problem if start xsane as Root, or do #'chmod 777 /dev/bus/usb -R' first.
For me I fixed it in mga5 by adding myself to the lp group, and loging out and in to KDE.
CC: (none) => cooker
No problem here now on Mageia-5!
Closing.
Resolution: (none) => FIXEDStatus: ASSIGNED => RESOLVED