Description of problem: I currently have an Epson WF-3720 AIO printer. The printing & utility packages work after installing, but is having problems with installing the scanner pkg. All files downloaded from Epson website, rpm packages. Version-Release number of selected component: lib64boost_program_options1.68.0 The downloaded pkg wants the lib64boost_program_options1.69.0 version Thanks.
> The downloaded pkg wants the lib64boost_program_options1.69.0 version It depends whether it wants exactly, or at least, this version. We seem to have already in Cauldron 'new version 1.72.0', the only one I can see since 1.68.0. Can this be made a Mageia 7 update? No clear maintainer, so assigning this globally; CC'ing Shlomi as the registered person.
Summary: Epson Scanning Pkg Need Updating => lib64boost_program_options1.68.0 for Epson Scanning Pkg Needs UpdatingSource RPM: lib64boost_program_options1.69.0 => boost-1.68.0-4.mga7.src.rpmCC: (none) => shlomifComponent: New RPM package request => RPM PackagesAssignee: bugsquad => pkg-bugs
boost is a big piece so it can't be updated in a stable release.
CC: (none) => geiger.david68210
Created attachment 11609 [details] imagescan SPEC file for Mageia Hi, To be able to use an Epson scanner, you need: 1) some binary RPMs (imagescan-plugin-*epson4centos8.x86_64.rpm) from CentOS8 2) to rebuild the imagescan package: """ cd $HOME/tmp mkdir -p imagescan/SOURCES mkdir -p imagescan/SPECS cd imagescan/SOURCES wget http://support.epson.net/linux/src/scanner/imagescanv3/fedora/imagescan-3.62.0-1epson4fedora30.src.rpm rpm2cpio imagescan-3.62.0-1epson4fedora30.src.rpm | cpio -idmvc cd ../SPECS <put here imagescan SPEC file for Mageia> <install bm package if it is not already installed> bm -l <if there are missing dependencies, install them and relaunch the previous command> cd ../RPMS/x86_64 <put here all imagescan-plugin RPMs from CentOS8> su -c "rpm -Uvh imagescan-3.62.0-1.mga7.x86_64.rpm imagescan-plugin-*epson4centos8.x86_64.rpm" """
CC: (none) => nicolas.salguero
When I said "some binary RPMs from CentOS8", I meant the RPMs you can get from Epson website by choosing the packages built for CentOS8.
Created attachment 11610 [details] imagescan logfile
Thanks Nicolas. After following your procedures it all went well, but not sure what happen with the plugin rpm. There was no errors other then installing the missing dependencies, which I did. "cd ../RPMS/x86_64 ls -l total 34896 -rw-r--r-- 1 saptech saptech 1600184 Apr 27 17:20 imagescan-3.62.0-1.mga7.x86_64.rpm -rw-r--r-- 1 saptech saptech 33842496 Apr 27 17:21 imagescan-debuginfo-3.62.0-1.mga7.x86_64.rpm -rw-r--r-- 1 saptech saptech 285644 Apr 27 17:20 imagescan-debugsource-3.62.0-1.mga7.x86_64.rpm" After running the su -c rpm command, this error appeared. "error: File not found by glob: imagescan-plugin-*epson4centos8.x86_64.rpm"
In the directory $HOME/tmp/imagescan/RPMS/x86_64, enter the following commands: """ wget https://download2.ebz.epson.net/imagescanv3/centos/latest1/rpm/x64/imagescan-bundle-centos-8-3.62.0.x64.rpm.tar.gz tar xzf imagescan-bundle-centos-8-3.62.0.x64.rpm.tar.gz mv imagescan-bundle-centos-8-3.62.0.x64.rpm/plugins/imagescan-plugin-* . su -c "rpm -Uvh imagescan-3.62.0-1.mga7.x86_64.rpm imagescan-plugin-*epson4centos8.x86_64.rpm" """
After following the second instructions, I got the plugins added. imagescan opens with scanner found but when I scan a document, it didn't show the doc while scanning but did create & save the scanned document. I had to add the device:ID to /etc/sane.d/epson.conf. simple-scan opens and find the scanner but when I press Scan, I get this message: simple-scan: symbol lookup error: /usr/lib64/utsushi/libutsushi.so.0: undefined symbol: libcnx_usb_LTX_factory xsane splash screen appears but then closes out with same message as simple-scan. When I ran sudo sane-find-scanner it found the scanner but I have a couple of "pipe errors". could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error found USB scanner (vendor=0x04b8, product=0x1127) at libusb:001:004 At this point using imagescan it works. But using simple-scan & xsane give the above errors and closes out. Thanks again.
Created attachment 11612 [details] New version of the SPEC file for Mageia Hi, Can you try rebuilding imagescan with this new version of the SPEC file to see if it solves the issue with simple-scan and xsane? To install the newly built package, run the following command in the directory $HOME/tmp/imagescan/RPMS/x86_64: su -c "rpm -Uvh --force imagescan-3.62.0-1.mga7.x86_64.rpm" Best regards, Nico.
Attachment 11609 is obsolete: 0 => 1
After installing the new Spec file, I'm getting the same issues as before, no change. Simpe-Scan & Xsane: "symbol lookup error: /usr/lib64/utsushi/libutsushi.so.0: undefined symbol: libcnx_usb_LTX_factory"
Do you have a file named "imagescan-x86_64.conf" in the directory "/etc/ld.so.conf.d"? If the file exists, can you try to run "ldconfig" as root to see if the error persists? If the file does not exist, then I think you forgot to run "bm -l" after putting the new SPEC file. After the rebuild, run again the command: su -c "rpm -Uvh --force imagescan-3.62.0-1.mga7.x86_64.rpm".
I had originally put the new Spec file in wrong location, it didn't create the imagescan-x86_64.conf. I put it in the Spec directory and reran bm -l command & the su -c "rpm -Uvh --force imagescan-3.62.0-1.mga7.x86_64.rpm" command. This time it did create the .conf file, after running "ldconfig" as root, it returns, "ldconfig: /lib/libbrcolm2.so.1 is not a symbolic link ldconfig: /lib/libbrscandec2.so.1 is not a symbolic link" Running xsane & simple-scan still show, "symbol lookup error: /usr/lib64/utsushi/libutsushi.so.0: undefined symbol: libcnx_usb_LTX_factory" Here is the output of the .conf file: cat /etc/ld.so.conf.d/imagescan-x86_64.conf /usr/lib64/utsushi Running locate libutsushi.so.0 /home/saptech/tmp/imagescan/BUILD/utsushi-0.62.0/lib/.libs/libutsushi.so.0 /home/saptech/tmp/imagescan/BUILD/utsushi-0.62.0/lib/.libs/libutsushi.so.0.0.0 /home/saptech/tmp.sav/imagescan/BUILD/utsushi-0.62.0/lib/.libs/libutsushi.so.0 /home/saptech/tmp.sav/imagescan/BUILD/utsushi-0.62.0/lib/.libs/libutsushi.so.0.0.0 /usr/lib64/utsushi/libutsushi.so.0 /usr/lib64/utsushi/libutsushi.so.0.0.0
Created attachment 11613 [details] New Scan Log-043020 I forgot to include the new imagescan log file.
Created attachment 11614 [details] Newest version of the SPEC file for Mageia
Attachment 11612 is obsolete: 0 => 1
Created attachment 11615 [details] Patch to fix link failures Hi, Can you try with the newest version of the SPEC file. You also need to put this patch in $HOME/tmp/imagescan/SOURCES before running "bm -l". Best regards, Nico.
I'm getting error when running bm -l using the new SPEC file. /tmp/imagescan/SPECS bm -l error: couldn't guess spec file in ./ Also, I am suppose to name the patch file, "utsushi-0.54.0-mga-fix-link-failures.patch"?
You need to put the SPEC file in $HOME/tmp/imagescan/SPECS and the file need to be named utsushi-0.54.0-mga-fix-link-failures.patch.
(In reply to Nicolas Salguero from comment #17) > You need to put the SPEC file in $HOME/tmp/imagescan/SPECS and the file need > to be named utsushi-0.54.0-mga-fix-link-failures.patch. That is correct. I put the SPEC file in /home/saptech/tmp/imagescan/SPECS and I named the patch file utsushi-0.54.0-mga-fix-link-failures.patch. /home/saptech/tmp/imagescan/SOURCES total 24664 -rw-r--r-- 1 saptech saptech 339 Jul 28 2016 gdk-pixbuf-format.patch -rw-r--r-- 1 saptech saptech 5824 Jul 28 2016 gtkmm-2.20-compat.patch -rw-r--r-- 1 saptech saptech 12554708 Jan 16 00:19 imagescan-3.62.0-1epson4centos8.src.rpm -rw-r--r-- 1 saptech saptech 497 Feb 27 2017 imagescan.conf -rw-r--r-- 1 saptech saptech 199 Jul 28 2016 imagescan.desktop -rw-r--r-- 1 saptech saptech 5794 Jan 14 22:33 imagescan.spec -rw-r--r-- 1 saptech saptech 6553 Nov 17 17:04 rebranding.patch -rw-r--r-- 1 saptech saptech 5420 Apr 30 19:48 utsushi-0.54.0-mga-fix-link-failures.patch -rwxrwxr-x 1 saptech saptech 12650003 Jan 14 22:31 utsushi-0.62.0.tar.gz*
You need to be in $HOME/tmp/imagescan or in $HOME/tmp/imagescan/SPECS to run "bm -l".
I may have had a corrupt SPEC file. I re-downloaded it again and put it into the $HOME/tmp/imagescan/SPECS directory and was able to build with bm -l in the $HOME/tmp/imagescan directory. Sadly, I'm getting the same error messages as before, "could not fetch string descriptor: Pipe error" and running xsane & simple-scan getting "symbol lookup error: /usr/lib64/utsushi/libutsushi.so.0: undefined symbol: libcnx_usb_LTX_factory" Running ldconfig give same message also. /etc/ld.so.conf.d ❯ su -c ldconfig Password: ldconfig: /lib/libbrcolm2.so.1 is not a symbolic link ldconfig: /lib/libbrscandec2.so.1 is not a symbolic link Any other suggestions? Thnx.
In the directory $HOME/tmp/imagescan/RPMS/x86_64, did you run: su -c "rpm -Uvh --force imagescan-3.62.0-1.mga7.x86_64.rpm" after building the new package?
Nico, you were correct, I didn't run the su -c command after the bm -l command. After running the su command, xsane & simple-scan are working. Yiiippppeeeeee!!! If you're on Mga IRC channel say hi. I'm Saptech on there. Thank you very much.
This past Saturday I was able to get another desktop, HP Compaq Elite 8300 Intel Core i5 3470 3.2GHz Processor; 8GB DDR3 RAM; 120GB SSD; Intel HD Graphics 2500. The older computer was a Dell Optiplex 760 desktop Quad Core i5 4GB 250GB HDD. After installing Mga 7 and following the same instructions listed above, I'm not able get the same scanner part working. Here are results running the scanner programs. $ imagescan opens Cannot access EPSON WF-3720_Series (esci:usb:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0) file not found Gtk-Message: 13:29:05.915: Failed to load module "canberra-gtk-module" -------------------------------------- $ simple-scan opens Failed to scan; unable to connect to scanner double free or corruption (fasttop) Aborted (core dumped) ------------------------------------- $ xsane starts Failed to open device 'imagescan:esci:usb:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0': Operation not supported. Gtk-Message: 13:28:15.535: Failed to load module "canberra-gtk-module" double free or corruption (fasttop) Aborted (core dumped) All three do have the scanner listed as available. Ideas/suggestions?
Stephen, on my system the scanner is added to /dev by udev rule /lib/udev/rules.d/60-libsane.rules ... $ ll /dev/bus/usb/005/002 crw-rw-r--+ 1 root scanner 189, 513 May 11 15:41 /dev/bus/usb/005/002 On the system where the scan program is not working, is the user a member of the scanner group? Note that the user must logout/in for changes to group membership to take effect. The memberships for the user can be modified using userdrake, which can be run from mcc.
CC: (none) => davidwhodgins
Dave, that was a good catch on the udev rule. I did add my scanner into the file and after rebooting, no changes. This is what I have listed below: $ ll /dev/bus/usb total 0 drwxr-xr-x 2 root root 100 May 11 20:05 001/ drwxr-xr-x 2 root root 80 May 11 20:05 002/ drwxr-xr-x 2 root root 140 May 11 20:05 003/ drwxr-xr-x 2 root root 60 May 11 20:05 004/ [saptech@localhost ~]$ ll /dev/bus/usb/004 total 0 crw-rw-r-- 1 root root 189, 384 May 11 20:05 001 [saptech@localhost ~]$ ll /dev/bus/usb/003 total 0 crw-rw-r-- 1 root root 189, 256 May 11 20:05 001 crw-rw-r-- 1 root root 189, 257 May 11 20:05 002 crwxrwxrwx+ 1 root root 189, 258 May 11 20:05 003 crw-rw-r-- 1 root root 189, 259 May 11 20:05 004 crw-rw-r-- 1 root root 189, 260 May 11 20:05 005 [saptech@localhost ~]$ ll /dev/bus/usb/002 total 0 crw-rw-r-- 1 root root 189, 128 May 11 20:05 001 crw-rw-r-- 1 root root 189, 129 May 11 20:05 002 [saptech@localhost ~]$ ll /dev/bus/usb/001 total 0 crw-rw-r-- 1 root root 189, 0 May 11 20:05 001 crw-rw-r-- 1 root root 189, 1 May 11 20:05 002 crw-rw-r-- 1 root root 189, 2 May 11 20:05 003 The user is a member of the scanner group. $ groups saptech adm lp wheel cdrom audio video scanner
# tree -ifaug /dev/bus/usb|grep scanner [root scanner ] /dev/bus/usb/005/007 If the device is not showing up in the scanner group, then the udev rule is not correct. In addition to setting the group for the device, the udev rule from the sane-backends package also sets access control list entries ... # getfacl /dev/bus/usb/005/007 getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/005/007 # owner: root # group: scanner user::rw- user:dave:rw- group::rw- group:lp:rw- mask::rw- other::r-- First thing I should have recommended is, with the scanner connected and turned on, run mcc, Set up scanner (drakscanner), and see if it detects it. Did you modify /lib/udev/rules.d/60-libsane.rules or add a file to /etc/udev/rules.d/ (changes to 60-libsane.rules will be overwritten by the next sane-backends update)? What change was made? # lspcidrake -v|grep -i mp150 usblp : Canon|MP150 [Printer|Printer|Bidirectional] (vendor:04a9 device:1709) As above, the lspcidrake command should show the scanner, even if there is not yet a udev rule for it. The -v option adds the showing of the vendor and device, which are needed for the udev rule. In my case it's a printer/scanner, though the print part doesn't work as I've given up replacing the ink cartridges.
When I ran MCC to seteup the scanner, it does not detect the scanner. # tree -ifaug /dev/bus/usb|grep scanner # It is blank # lspcidrake -v|grep -i epson usblp : EPSON|WF-3720 Series [Printer|Printer|Bidirectional] (vendor:04b8 device:1127) Below is the line I added to /lib/udev/rules.d/60-libsane.rules # EPSON WF-3720 Series ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="1127", MODE="0644", GROUP="usb", ENV{libsane_matched}="yes" I just noticed this and here is the results. $ ls -l /etc/udev/rules.d/ total 4 -rwxr-xr-x 1 root root 294 May 9 23:57 79-udev-epson.rules* $ cat /etc/udev/rules.d/79-udev-epson.rules # chmod device EPSON group # ACTION=="add", ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0666" ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0777" With the old computer, after following Nicolas steps, the scanner worked. I do not remember modifying /lib/udev/rules.d/60-libsane.rules or /etc/udev/rules.d/79-udev-epson.rules. At this time I can not boot up the older computer to look at these lines to see any difference. I may get a KVM switch and see what's different.
As an update on my issue: I had recently purchased a HP Compaq Elite 8300 desktop and having the scanner issue getting it to scan. I finally got a KVM switch and wanted to look at scan config files on the old Dell Optiplex 760. Now the Dell's power switch seems to not be working, it won't turn on. I'm planning on putting it into the shop and get it fix. Any more suggestions on getting the scanner running on the HP? Thanks.
When running imagescan, I receive this message: Cannot access EPSON WF-3720_Series (esci:usb:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0) file not found $ ls -l /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0 total 0 -rw-r--r-- 1 root root 4096 May 23 11:36 authorized -r--r--r-- 1 root root 4096 May 23 11:36 bAlternateSetting -r--r--r-- 1 root root 4096 May 23 11:36 bInterfaceClass -r--r--r-- 1 root root 4096 May 23 11:36 bInterfaceNumber -r--r--r-- 1 root root 4096 May 23 11:36 bInterfaceProtocol -r--r--r-- 1 root root 4096 May 23 11:36 bInterfaceSubClass -r--r--r-- 1 root root 4096 May 23 11:36 bNumEndpoints drwxr-xr-x 3 root root 0 May 23 11:36 ep_01/ drwxr-xr-x 3 root root 0 May 23 11:36 ep_82/ drwxr-xr-x 3 root root 0 May 23 11:36 ep_83/ -r--r--r-- 1 root root 4096 May 23 11:36 interface -r--r--r-- 1 root root 4096 May 23 11:36 modalias drwxr-xr-x 2 root root 0 May 23 11:36 power/ lrwxrwxrwx 1 root root 0 May 23 11:36 subsystem -> ../../../../../../bus/usb/ -r--r--r-- 1 root root 4096 May 23 11:36 supports_autosuspend -rw-r--r-- 1 root root 4096 May 23 11:36 uevent xsane show this when started: $ xsane Gtk-Message: 11:44:41.042: Failed to load module "canberra-gtk-module" usb:/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0) file not found. then when I close the program it show below: double free or corruption (fasttop) Aborted (core dumped) When I run simple-scan, I'm getting this for first time: $ simple-scan (simple-scan:31155): dbind-WARNING **: 11:47:29.597: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. double free or corruption (fasttop) Aborted (core dumped) Starting all three scanner programs, each one show the scanner listed. I get the above messages when I click the Scan button.
When trying to scan, are any messages being added to the output of the command dmesg? Compare dmesg output from before scanning to after, to see any added lines. I'm wondering if the devices is temporarily disappearing due to some sort of power issue.
Created attachment 11656 [details] dmesg before & after reboot I included dmesg after a reboot and running the scanner programs.
After a reboot: [ 1.921727] usb 1-1: new high-speed USB device number 2 using xhci_hcd [ 1.937725] usb 3-1: new high-speed USB device number 2 using ehci-pci [ 1.945712] usb 4-1: new high-speed USB device number 2 using ehci-pci [ 2.058597] usb 1-1: New USB device found, idVendor=04b8, idProduct=1127, bcdDevice= 1.00 [ 2.058600] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.058601] usb 1-1: Product: WF-3720 Series [ 2.058603] usb 1-1: Manufacturer: EPSON [ 2.058604] usb 1-1: SerialNumber: 583254463531333930 Running simple-scan, xsane & imagescan nothing different as below: [ 5716.232122] lp: driver loaded but no devices found [ 5716.233444] ppdev: user-space parallel port driver [ 5716.353642] net-fw DROP IN=eno1 OUT= MAC=10:60:4b:78:35:98:38:1a:52:8e:6e:cd:08:00 SRC=192.168.2.14 DST=192.168.2.16 LEN=104 TOS=0x00 PREC=0x00 TTL=30 ID=63603 PROTO=UDP SPT=3289 DPT=58455 LEN=84 [ 5717.378168] net-fw DROP IN=eno1 OUT= MAC=10:60:4b:78:35:98:38:1a:52:8e:6e:cd:08:00 SRC=192.168.2.14 DST=192.168.2.16 LEN=104 TOS=0x00 PREC=0x00 TTL=30 ID=63604 PROTO=UDP SPT=3289 DPT=48197 LEN=84
Another option to consider trying. Install the Fedora boost package ... https://download-ib01.fedoraproject.org/pub/fedora/linux/updates/30/Everything/x86_64/Packages/b/boost-system-1.69.0-9.fc30.x86_64.rpm May work.
Dave Hodgins, I tried the Fedora boost package and it didn't make any difference. Thanks for your help. Earlier I mention using the printer with a HP machine which is having the scanner problem and would boot up the Dell desktop to view scanner configs/files, but now the Dell seems to be Dead. It will not boot up at all. At this time I can get to the HDD, but working on it. I'll just keep trying to figure how to get the scanner working . Thanks all.
Hi Nicolas Stephen and Dave There's apparently a problem specific to Mageia I bought an Epson printer (thinking there are useable linux drivers) But, like Stephen, I found only rpm drivers for Centos Fedora OpenSuse needing a specific version of boost Googling a little I found this bug report I used the spec file proposed by Nicolas in comment 14 and the patch proposed in comment 15 I used four different sources (modifying the %define min_vers 62.0) imagescan-3.62.0-1epson4fedora30.src.rpm imagescan-3.62.0-1epson4centos8.src.rpm imagescan-3.63.0-1epson4fedora30.src.rpm imagescan-3.63.0-1epson4centos8.src.rpm and the non-free plugin for Centos or Fedora or OpenSuse I tried to build without the Nicolas' patch and saw that it is absolutely necessary for Mageia (if not for Debian, Fedora, OpenSuse etc. ) Whatever I tried it's the same problem When running imagescan, I receive this message (even after having edited the imagescan.conf file with the right network address): Cannot access EPSON XP-4105 (esci:usb:/sys/devices/pci0000:00/xxxxxx) file not found double free or corruption (fasttop) Aborted (core dumped) same thing with the network (after having edited utsushi.conf ou imagescan.conf Cannot access EPSON XP-4100-series (esci:network:xxxxxx) file not found double free or corruption (fasttop) Aborted (core dumped) I tried to not rebrand (keeping utsushi as name instead of renaming into imagescan) modifying the spec file for this When running utsushi same message Cannot access EPSON XP-4105_Series (esci:usb:/sys/devices/pci0000:00/xxxxxx) file not found double free or corruption (fasttop) Aborted (core dumped) I tried to add manually imagescan (or utsushi) in /etc/sane.d/dll.d/ and 70-image-scan-esci-rules in /udev/rules.d/ because that is not automatically done I tried to add this to the spec file : %if "true" != "%{have_sane_dll_d}" # # Modify SANE's dll.conf during (un)installation # %post dll=%{_sysconfdir}/sane.d/dll.conf if [ -n "`grep '^[ \t]*#[ \t#]*%{name}' ${dll}`" ] then # uncomment existing entry sed -i 's,^[ \t]*#[ \t#]*\(%{name}\),\1,' ${dll} elif [ -z "`grep %{name} ${dll}`" ] then # append brand new entry echo %{name} >> ${dll} fi %preun if [ $1 = 0 ] then # comment out existing entry dll=%{_sysconfdir}/sane.d/dll.conf if [ -n "`grep '^[ \t]*%{name}' ${dll}`" ] then sed -i 's,^[ \t]*\(%{name}\),#\1,' ${dll} fi fi %endif No way All the rpms (imagescan or utsushi version 3.62 or version 3.63) build OK But no one allows me to use the scanner which is recognised by imagescan (which proposes the choice between the network or the usb connexion) I gave up, will give my epson printer to a friend using a Mac and buy a HP printer whose drivers and programs are simple to get
CC: (none) => philippedidier
Summary: lib64boost_program_options1.68.0 for Epson Scanning Pkg Needs Updating => Third-party Epson Scanning software imagescan does not work
Philippe Didier, thanks for the report, I'm glad I'm not the only one having issues. I've been away from IRC for awhile but using the PC. I have to switch distros (Debian) to scan, which I need to have available. Printing is no issue and works great. I'm not giving up on the printer, since this is the only one I have. I hope Mga will find a solution. I just hate switching when time to scan. Just an update from me to the developers, that I'm still around!
Having just fixed a bug in the iscan/epkowa SANE backend (that's the one provided/supported by Epson), I noticed we have a fairly old version. I wonder if a newer one would support your device and avoid the problem with the utsushi backend.
CC: (none) => mageia
Hi Martin Unfortunately I don't think that the iscan/epkowa sane backend will bring a solution for this particular problem : The last Epson all-in-one printers need imagescan3 Imagescan3 can be downloaded here : http://download.ebz.epson.net/dsc/search/01/search/searchModule but it needs to be built for Mageia (rpms are provided for Fedora or CentOs or OpenSuse but can't be used for Mageia 7 ... (I didn't test them on Cauldron) the spec file is provided by Nicolas in comment 14 and the needed patch in comment 15 If we use the last source file you need to modify a little the spec file, but ... no way ! it doesn't work for Mageia (at least Mageia 7)
Does anyone know if this issue will ever be resolved? If not for Mga 8, maybe for 8.1 or 9? I'm not able to fix it, not enough knowledge to do it. I'm just inquiring on it.
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi Aurélien I can't say anything about this : I gave up trying to build a working rpm for Mageia : I gave my all in one Epson to a friend (ok for Windows) and bought a Hewlett Packard which was installed easily hplip is your friend ;-)
(In reply to Stephen Pettin from comment #39) > Does anyone know if this issue will ever be resolved? If not for Mga 8, > maybe for 8.1 or 9? I'm not able to fix it, not enough knowledge to do it. > > I'm just inquiring on it. So after Mageia 8 release, you experienced that this issue didn't get solved. Can you confirm it still doesn't work now? Changing "Version:" to "8", so that this report won't get closed when the Mageia 7 bug reports get closed.
Keywords: (none) => NEEDINFOVersion: 7 => 8CC: (none) => marja11
To be revisited whenever we have updated sane. Bug 30703 - Update the complete sane stack
CC: (none) => fri