Page 1 of 1
Move from MX18 to 19 stops scanner working SOLVED
Posted: Mon Mar 09, 2020 12:56 pm
by mikek
I multiboot my optiplex 7010.
My scanner an Epsom perfection v500 photo works fine on MX18.3 and Windows10.
I added MX19.1 to the computer and installed the scanner in exactly the same way as on mx18.3, using gdebi. There were no error messages.
In mx19 simple-scan and image scan for linux and gscanpdf cannot find the scanner
scanimage -L produces this:
device `epkowa:interpreter:002:005' is a Epson Perfection V500 flatbed scanner.
I installed MX19 on my laptop and had the same problem.
Is there something different about MX19 which is stopping the scanner working?
thanks
quick system info
Code: Select all
System: Host: mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/vmlinuz root=/dev/sda16
Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19.1_x64 patito feo October 21 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop System: Dell product: OptiPlex 7010 v: 01 serial: <filter> Chassis:
type: 3 serial: <filter>
Mobo: Dell model: 0773VG v: A00 serial: <filter> BIOS: Dell v: A23 date: 08/09/2016
CPU: Topology: Dual Core model: Intel Core i3-2120 bits: 64 type: MT MCP
arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F
L2 cache: 3072 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 26340
Speed: 3292 MHz min/max: 1600/3300 MHz Core speeds (MHz): 1: 2841 2: 2141 3: 3292
4: 1666
Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Dell
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0102
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Desktop v: 3.3 Mesa 18.3.6 compat-v: 3.0
direct render: Yes
Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Intel 82579LM Gigabit Network vendor: Dell driver: e1000e v: 3.2.6-k
port: f080 bus ID: 00:19.0 chip ID: 8086:1502
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 465.76 GiB used: 148.00 GiB (31.8%)
ID-1: /dev/sda vendor: Western Digital model: WD5000AAKS-42H2B0 size: 465.76 GiB
block size: physical: 512 B logical: 512 B speed: 1.5 Gb/s serial: <filter> rev: 4C07
scheme: MBR
Partition: ID-1: / raw size: 23.23 GiB size: 22.74 GiB (97.89%) used: 8.41 GiB (37.0%) fs: ext4
dev: /dev/sda16
ID-2: swap-1 size: 990.0 MiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda5
Sensors: System Temperatures: cpu: 33.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 213 Uptime: 3m Memory: 3.74 GiB used: 1.09 GiB (29.1%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3
running in: quick-system-in inxi: 3.0.36
Re: Move from MX18 to 19 stops scanner working
Posted: Mon Mar 09, 2020 4:05 pm
by gimcrack
You know what, I had the same problem. I still do, but I still have MX 18.3 on my other hard drive. So I just jump over there to scan. But if you install VueScan on MX 19, it works but this one cost. They watermark the file, until you register their software. Of course I didn't and didn't look into why on MX 19.1 it's don't scanning for me with Simple Scan or other free ones. Since your asking, I'm going to look at my again and if I fix it, I'll tell you how.
Re: Move from MX18 to 19 stops scanner working
Posted: Tue Mar 10, 2020 3:22 pm
by mikek
In a terminal, sudo simple-scan and it worked.
Well I should have tried that before.
But could someone please tell me how to get it working from the menu.
thanks
Re: Move from MX18 to 19 stops scanner working
Posted: Tue Mar 10, 2020 6:57 pm
by JayM
mikek wrote: Tue Mar 10, 2020 3:22 pm
In a terminal, sudo simple-scan and it worked.
Well I should have tried that before.
But could someone please tell me how to get it working from the menu.
thanks
Have you tried clicking on it's icon?
BTW you don't need to use sudo for simple scan. It doesn't need special privileges.
Re: Move from MX18 to 19 stops scanner working
Posted: Tue Mar 10, 2020 11:34 pm
by asqwerth
mikek wrote: Mon Mar 09, 2020 12:56 pm
I multiboot my optiplex 7010.
My scanner an Epsom perfection v500 photo works fine on MX18.3 and Windows10.
I added MX19.1 to the computer and installed the scanner in exactly the same way as on mx18.3, using gdebi. There were no error messages.....
Instead of installing with gdebi, could you right click on the deb file in Thunar and choose instead the "Install Deb Files" option from the right click context menu? In MX19, I believe that gdebi can at times not work.
Then test again after installing in that manner.
If it still doesn't work, a web search brings this up where a user had his driver for said scanner work in an older version of a distro but not the new version:
https://www.linuxliteos.com/forums/prin ... ing-ll3-2/
and
https://askubuntu.com/questions/828205/ ... 04-upgrade
...
In mx19 simple-scan and image scan for linux and gscanpdf cannot find the scanner
scanimage -L produces this:
device `epkowa:interpreter:002:005' is a Epson Perfection V500 flatbed scanner.
I installed MX19 on my laptop and had the same problem.
Is there something different about MX19 which is stopping the scanner working?.....
By the way, JayM is right. The simple-scan scanner program can be called up from Whisker menu without root or sudo password. If the menu entry doesn't even open up the program, something is wrong with your installation.
Re: Move from MX18 to 19 stops scanner working
Posted: Sun Mar 15, 2020 7:31 am
by mikek
Thank you all for your suggestions.
What I have done is this:
Because all scanning programs failed I assume the problem is in sane backend
I read up on configuring sane and file permissions and concluded this was far too complicated for me.
I tried installing 19.1, Same problem so I suppose the problem is caused by a change in 19.
MX is my favourite distro but I have to have the scanner working or go to another distro.
I documented what I did for future use. Here it is :-
1. Thunar - go to /etc/sudoers.d
file>open thunar as root
copy lsof.mx and rename it scanner
open in featherpad and amend to %users ALL=(root) NOPASSWD: /usr/bin/simple-scan
2. create a file in featherpad and save it. Mine is home/scripts/scanner.sh
Enter:
#!/bin/bash
# a file has been created in /etc/sudoers.d so that a password will not be requested
sudo /usr/bin/simple-scan
3. right click on desktop>create a launcher
command ‘sh simple.scan.sh’
working directory /home/mike/scripts
I works!
Re: Move from MX18 to 19 stops scanner working
Posted: Sun Mar 15, 2020 7:40 am
by JayM
Please edit your original post #1 at the beginnng of this topic (via the pencil icon at the top right of your post) and add [SOLVED] to its subject. This makes it easier for others when they're searching the forum looking for solutions to the same question or problem. Thanks.
Re: Move from MX18 to 19 stops scanner working
Posted: Sun Mar 15, 2020 9:10 am
by asqwerth
Thunar can be opened as root just by right clicking on the desktop and choosing the entry from the context menu.
So no need to mess with sudoers file, which is not advised.
But I still say something is wrong if you can't open simple scan without root. Was mx 19 a clean install from official iso?
Opening simple scan should be possible even if you have no working driver for your scanner. The app will simply open but just indicate that no scanner was found.
Re: Move from MX18 to 19 stops scanner working [Solved]
Posted: Sun Mar 15, 2020 1:54 pm
by ckester
JayM wrote: Sun Mar 15, 2020 7:40 am
Please edit your
original post #1 at the beginnng of this topic (via the pencil icon at the top right of your post) and add [SOLVED] to its subject. This makes it easier for others when they're searching the forum looking for solutions to the same question or problem. Thanks.
It's not clear to me what the solution to this problem actually is. Can someone please spell it out?
My scanner is a Canon CanoScan N1240U/LiDE30. I ran simple-scan from the commandline and was able to scan one page as text. But when I tried to scan the page as photo, all I got was a blank, black image; the scanner light never came on. Pressing "Start Again..." did not resolve the issue, nor did exiting simple-scan and restarting it from the commandline. It also didn't help to unplug the USB cable from the scanner and reinsert it after a 10sec delay.
I've tried xsane with similar (failing) results. Sometimes I can get one photo scan but no more. There seems to be a problem resetting the driver for the scanner so it will turn the lamp on for the next scan. Any ideas?
Also, both simple-scan and xsane take a LONG time trying to contact/locate the scanner. Is this normal?
Re: Move from MX18 to 19 stops scanner working
Posted: Wed Mar 18, 2020 1:54 pm
by ckester
ckester wrote: Sun Mar 15, 2020 1:54 pm
My scanner is a Canon CanoScan N1240U/LiDE30. I ran simple-scan from the commandline and was able to scan one page as text. But when I tried to scan the page as photo, all I got was a blank, black image; the scanner light never came on. Pressing "Start Again..." did not resolve the issue, nor did exiting simple-scan and restarting it from the commandline. It also didn't help to unplug the USB cable from the scanner and reinsert it after a 10sec delay.
I've tried xsane with similar (failing) results. Sometimes I can get one photo scan but no more. There seems to be a problem resetting the driver for the scanner so it will turn the lamp on for the next scan. Any ideas?
Also, both simple-scan and xsane take a LONG time trying to contact/locate the scanner. Is this normal?
Just to close out this issue with my (admittedly old) scanner, adding it to the USB_BLACKLIST as
described in the wiki fixed the problem with the lamp. And pruning the list of backends in /etc/sane.d/dll.conf helped speed up the time taken to contact/locate the scanner.
Re: Move from MX18 to 19 stops scanner working SOLVED
Posted: Wed Sep 02, 2020 7:00 pm
by humon
Hello folks, late to the game, but my Samsung CLX-3305FW multifunction no longer scans now that I migrated to MX 19.2.
When I first found it wouldn't work and ran some cli stuff one of the messages is that sysvinit is part of the problem and that I need systemd running in order for the scanner to be recognized.
I downladed and installed the sane backend for the CLX-3300 series both from HP and bchemnet.
Using sudo sane-find-scanner -v (and even without sudo) I see I have a USB scanner (vendor=0x0b05, product=0x7772) at libusb:001:011 but when I run sane or xsane no scanner found is the error msg.
Ideas?