Now that I can see the Epson printer and print to it, I would like to get the scanner to work also. When I select XSane Scanner Tool, I get a box "no devices available" --the scanner is part of the Epson printer and works manually. I wonder if this is the problem I had several years ago that required an addition to one of the driver files, but I don't know how to find out. I think I did mention it in a note to the group, but I don't know if that was for the scanner or the printer. (Also, there seem to be several email paths to the folks at OS, so I don't know which one it would have been.) --doug
Hello, In the Message; Subject : XSane Message-ID : <595bfd0e-a508-4a23-a29c-3862c4139462@optonline.net> Date & Time: Mon, 13 Sep 2021 21:40:36 -0400 [DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written: DM> Now that I can see the Epson printer and print to it, I would like to DM> get the scanner to work also. When I select XSane Scanner Tool, I DM> get a box "no devices available" --the scanner is part of the Epson DM> printer and works manually. I wonder if this is the problem I had DM> several years ago that required an addition to one of the driver files, DM> but I don't know how to find out. I think I did mention it in a note to DM> the group, but I don't know if that was for the scanner or the printer. DM> (Also, there seem to be several email paths to the folks at OS, so DM> I don't know which one it would have been.) The driver, but for Leap 15.2, is here; http://support.epson.net/linux/en/imagescanv3.php Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Tim Cook, the C.E.O. of Apple, said earlier this year that he would not let his nephew join social networks. Bill Gates banned cellphone until his children were teenagers, and Melinda Gates wrote that she wished they had waited even longer. Steve Jobs would not let his young children near iPads." -- The New York Times --
On 9/13/21 10:15 PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : XSane Message-ID : <595bfd0e-a508-4a23-a29c-3862c4139462@optonline.net> Date & Time: Mon, 13 Sep 2021 21:40:36 -0400
[DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written:
DM> Now that I can see the Epson printer and print to it, I would like to DM> get the scanner to work also. When I select XSane Scanner Tool, I DM> get a box "no devices available" --the scanner is part of the Epson DM> printer and works manually. I wonder if this is the problem I had DM> several years ago that required an addition to one of the driver files, DM> but I don't know how to find out. I think I did mention it in a note to DM> the group, but I don't know if that was for the scanner or the printer. DM> (Also, there seem to be several email paths to the folks at OS, so DM> I don't know which one it would have been.)
The driver, but for Leap 15.2, is here;
http://support.epson.net/linux/en/imagescanv3.php
Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃ Downloaded file and let the system unpack it, but zypper won't install it and rpm -Uvh file.rpm won't install it either.
linux1:~ # zypper install imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm Specified local path does not exist or is not accessible. Problem retrieving the specified RPM file: Malformed URI: Please check whether the file is accessible. Problem with the RPM file specified as 'imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm', skipping. No valid arguments specified. linux1:~ # rpm -Uvh imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm error: open of imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm failed: No such file or directory Now what? --doug
The On 9/13/21 11:12 PM, Darryl Gregorash wrote:
On 2021-09-13 8:57 p.m., Douglas McGarrett wrote:
linux1:~ # zypper install imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm Specified local path does not exist or is not accessible. You're in the home directory of the root account. Is that where you downloaded the file? The directory is /home/doug/Downloads. That's where all downloaded files go. Normally can be installed from there. --doug
On 2021-09-13 9:49 p.m., Douglas McGarrett wrote:
The
On 9/13/21 11:12 PM, Darryl Gregorash wrote:
On 2021-09-13 8:57 p.m., Douglas McGarrett wrote:
linux1:~ # zypper install imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm Specified local path does not exist or is not accessible. You're in the home directory of the root account. Is that where you downloaded the file? The directory is /home/doug/Downloads. That's where all downloaded files go. Normally can be installed from there.
Then that is the directory where you should be, to run those commands giving just a filename. As you typed them, both zypper and rpm assume the file exists in the current directory. Either change to that directory, or specify the full path/filename on the commandline.
On 2021-09-13 9:49 p.m., Douglas McGarrett wrote:
The
On 9/13/21 11:12 PM, Darryl Gregorash wrote:
On 2021-09-13 8:57 p.m., Douglas McGarrett wrote:
linux1:~ # zypper install imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm Specified local path does not exist or is not accessible. You're in the home directory of the root account. Is that where you downloaded the file? The directory is /home/doug/Downloads. That's where all downloaded files go. Normally can be installed from there. Then that is the directory where you should be, to run those commands giving just a filename.
As you typed them, both zypper and rpm assume the file exists in the current directory. Either change to that directory, or specify the full path/filename on the commandline. Yes, I was in that directory. Apparently the software is installed, as
On 9/14/21 1:31 AM, Darryl Gregorash wrote: per the previous emails. There is an icon on the screen (KDE) "XSane Scanner Tool" which should start the scanner. It does not, as yet. It cannot find the scanner. --doug
Op dinsdag 14 september 2021 09:17:16 CEST schreef Douglas McGarrett:
On 9/14/21 1:31 AM, Darryl Gregorash wrote:
On 2021-09-13 9:49 p.m., Douglas McGarrett wrote:
The
On 9/13/21 11:12 PM, Darryl Gregorash wrote:
On 2021-09-13 8:57 p.m., Douglas McGarrett wrote:
linux1:~ # zypper install imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm Specified local path does not exist or is not accessible.
You're in the home directory of the root account. Is that where you downloaded the file?
The directory is /home/doug/Downloads. That's where all downloaded files go. Normally can be installed from there.
Then that is the directory where you should be, to run those commands giving just a filename.
As you typed them, both zypper and rpm assume the file exists in the current directory. Either change to that directory, or specify the full path/filename on the commandline.
Yes, I was in that directory. Apparently the software is installed, as per the previous emails. There is an icon on the screen (KDE) "XSane Scanner Tool" which should start the scanner. It does not, as yet. It cannot find the scanner.
--doug
Is it powered on and how is it connected? -- fr.gr. member openSUSE Freek de Kruijf
On 14.09.21 09:58, Freek de Kruijf wrote:
Op dinsdag 14 september 2021 09:17:16 CEST schreef Douglas McGarrett:
On 9/14/21 1:31 AM, Darryl Gregorash wrote:
On 2021-09-13 9:49 p.m., Douglas McGarrett wrote:
The
On 9/13/21 11:12 PM, Darryl Gregorash wrote:
On 2021-09-13 8:57 p.m., Douglas McGarrett wrote:
linux1:~ # zypper install imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm Specified local path does not exist or is not accessible.
You're in the home directory of the root account. Is that where you downloaded the file?
The directory is /home/doug/Downloads. That's where all downloaded files go. Normally can be installed from there.
Then that is the directory where you should be, to run those commands giving just a filename.
As you typed them, both zypper and rpm assume the file exists in the current directory. Either change to that directory, or specify the full path/filename on the commandline.
Yes, I was in that directory. Apparently the software is installed, as per the previous emails. There is an icon on the screen (KDE) "XSane Scanner Tool" which should start the scanner. It does not, as yet. It cannot find the scanner.
--doug
Is it powered on and how is it connected?
I had a similar problem with my (USB connected) Brother ADS-2100e What does "scanimage -L" output? Here it currently outputs device `brother4:bus2;dev1' is a Brother ADS-2100e USB scanner I then use the part between ` and ' as the parameter for --device for scanimage. Josef -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
On 9/14/21 4:06 AM, Josef Moellers wrote:
/snip/
On 2021-09-13 8:57 p.m., Douglas McGarrett wrote: > linux1:~ # zypper install imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm > Specified local path does not exist or is not accessible. You're in the home directory of the root account. Is that where you downloaded the file? The directory is /home/doug/Downloads. That's where all downloaded files go. Normally can be installed from there. Then that is the directory where you should be, to run those commands giving just a filename.
As you typed them, both zypper and rpm assume the file exists in the current directory. Either change to that directory, or specify the full path/filename on the commandline. Yes, I was in that directory. Apparently the software is installed, as per the previous emails. There is an icon on the screen (KDE) "XSane Scanner Tool" which should start the scanner. It does not, as yet. It cannot find the scanner.
--doug Is it powered on and how is it connected? I had a similar problem with my (USB connected) Brother ADS-2100e
What does "scanimage -L" output?
Here it currently outputs device `brother4:bus2;dev1' is a Brother ADS-2100e USB scanner I then use the part between ` and ' as the parameter for --device for scanimage.
Josef The command scanimage -L hangs. I just get a black square on the next line. (The display is black letters on white background.) It needs ctrl-c to clear. --doug
On 14/09/2021 22.57, Douglas McGarrett wrote:
On 9/14/21 4:06 AM, Josef Moellers wrote:
What does "scanimage -L" output?
Here it currently outputs device `brother4:bus2;dev1' is a Brother ADS-2100e USB scanner I then use the part between ` and ' as the parameter for --device for scanimage.
The command scanimage -L hangs. I just get a black square on the next line. (The display is black letters on white background.) It needs ctrl-c to clear.
How long did you wait? Give it at least three minutes. make sure to drop your firewall first. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 9/14/21 5:11 PM, Carlos E. R. wrote:
On 14/09/2021 22.57, Douglas McGarrett wrote:
On 9/14/21 4:06 AM, Josef Moellers wrote:
What does "scanimage -L" output?
Here it currently outputs device `brother4:bus2;dev1' is a Brother ADS-2100e USB scanner I then use the part between ` and ' as the parameter for --device for scanimage.
The command scanimage -L hangs. I just get a black square on the next line. (The display is black letters on white background.) It needs ctrl-c to clear. How long did you wait? Give it at least three minutes.
make sure to drop your firewall first.
OK. Stopped firewall. Ran command. Printer made a small noise. Waited probably 3 minutes. Got result: linux1:~ # systemctl disable firewalld Removed /etc/systemd/system/multi-user.target.wants/firewalld.service. Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service. linux1:~ # systemctl stop firewalld linux1:~ # scanimage -L device `epson2:net:192.168.0.26' is a Epson PID 087D flatbed scanner I will turn the firewall back on now. I hope that folks who ask for a response like this give me the necessary information, like you just did. Thank you. --doug
On 15/09/2021 01.57, Douglas McGarrett wrote:
On 9/14/21 5:11 PM, Carlos E. R. wrote:
On 14/09/2021 22.57, Douglas McGarrett wrote:
On 9/14/21 4:06 AM, Josef Moellers wrote:
What does "scanimage -L" output?
Here it currently outputs device `brother4:bus2;dev1' is a Brother ADS-2100e USB scanner I then use the part between ` and ' as the parameter for --device for scanimage.
The command scanimage -L hangs. I just get a black square on the next line. (The display is black letters on white background.) It needs ctrl-c to clear. How long did you wait? Give it at least three minutes.
make sure to drop your firewall first.
OK. Stopped firewall. Ran command. Printer made a small noise. Waited probably 3 minutes. Got result: linux1:~ # systemctl disable firewalld Removed /etc/systemd/system/multi-user.target.wants/firewalld.service. Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service. linux1:~ # systemctl stop firewalld linux1:~ # scanimage -L device `epson2:net:192.168.0.26' is a Epson PID 087D flatbed scanner
I will turn the firewall back on now. I hope that folks who ask for a response like this give me the necessary information, like you just did.
Ok, so you know that the sofware works and it finds the scanner. What you have to do now is configure the firewall to give access to the scanner, that is, to open certain ports. However, I don't have this kind of hardware, I have no idea what ports you have to open. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Hello, In the Message; Subject : Re: XSane Message-ID : <d4bf6488-d1f1-0b1b-0c28-75f6f9be5ea6@optonline.net> Date & Time: Tue, 14 Sep 2021 19:57:51 -0400 [DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written: [...] DM> >> The command scanimage -L hangs. I just get a black square on the DM> >> next line. (The display is black letters on white background.) It needs DM> >> ctrl-c to clear. DM> > How long did you wait? Give it at least three minutes. DM> > DM> > make sure to drop your firewall first. DM> > DM> > DM> OK. Stopped firewall. Ran command. Printer made a small noise. DM> Waited probably 3 minutes. Got result: DM> linux1:~ # systemctl disable firewalld DM> Removed /etc/systemd/system/multi-user.target.wants/firewalld.service. DM> Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service. DM> linux1:~ # systemctl stop firewalld DM> linux1:~ # scanimage -L DM> device `epson2:net:192.168.0.26' is a Epson PID 087D flatbed scanner DM> I will turn the firewall back on now. I hope that folks who ask for a DM> response like this give me the necessary information, like you just did. 1. start YaST2 2. select "Security and Users" 3. click "Firewall" 4. select "public" 5. select "ipp" from "Services" 6. push "Add ->" Button (by this the item "ipp" move to "Allowed" area) 7. push Accecp Button Regards, --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."
Op dinsdag 14 september 2021 09:17:16 CEST schreef Douglas McGarrett:
On 2021-09-13 9:49 p.m., Douglas McGarrett wrote:
The
On 9/13/21 11:12 PM, Darryl Gregorash wrote:
On 2021-09-13 8:57 p.m., Douglas McGarrett wrote:
linux1:~ # zypper install imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm Specified local path does not exist or is not accessible. You're in the home directory of the root account. Is that where you downloaded the file? The directory is /home/doug/Downloads. That's where all downloaded files go. Normally can be installed from there. Then that is the directory where you should be, to run those commands giving just a filename.
As you typed them, both zypper and rpm assume the file exists in the current directory. Either change to that directory, or specify the full path/filename on the commandline. Yes, I was in that directory. Apparently the software is installed, as
On 9/14/21 1:31 AM, Darryl Gregorash wrote: per the previous emails. There is an icon on the screen (KDE) "XSane Scanner Tool" which should start the scanner. It does not, as yet. It cannot find the scanner.
--doug Is it powered on and how is it connected? The scanner is part of the Epson WP-4530 all-mode printer, which is connected via the lan and is always on. It does work manually--that is, I put a
On 9/14/21 3:58 AM, Freek de Kruijf wrote: piece of art of text on the glass and scan it and it prints the result, but I cannot at the moment make it scan from the computer and put the result into a file. (It worked in the past, on another Linux system.) --doug
On 2021-09-14 16:52, Douglas McGarrett wrote:
(It worked in the past, on another Linux system.) --doug
Didn't someone say something about keeping a "log book" that covered things like how you set up systems in the past? -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg
Le 15/09/2021 à 17:34, Anton Aylward a écrit :
On 2021-09-14 16:52, Douglas McGarrett wrote:
(It worked in the past, on another Linux system.) --doug
Didn't someone say something about keeping a "log book" that covered things like how you set up systems in the past?
very difficult and time consuming job. I teached that more than 10 years ago and have some notes, but nor acurate nor complete now http://www.dodin.org/wiki/pmwiki.php?n=Doc.Server-2021 http://www.dodin.org/wiki/pmwiki.php?n=Doc.OpenSUSE-small-ThirdEdition I should update it (and build the server - I already lend one machine) but family get first and is very demanding nowaday :-( jdd -- http://dodin.org
Following this is really cool. It's very nice to be taking some notes and learning. Just wanted to say thanks. 🐸 -Best Regards On 9/15/21 10:59 AM, jdd@dodin.org wrote:
Le 15/09/2021 à 17:34, Anton Aylward a écrit :
On 2021-09-14 16:52, Douglas McGarrett wrote:
(It worked in the past, on another Linux system.) --doug
Didn't someone say something about keeping a "log book" that covered things like how you set up systems in the past?
very difficult and time consuming job. I teached that more than 10 years ago and have some notes, but nor acurate nor complete now
http://www.dodin.org/wiki/pmwiki.php?n=Doc.Server-2021
http://www.dodin.org/wiki/pmwiki.php?n=Doc.OpenSUSE-small-ThirdEdition
I should update it (and build the server - I already lend one machine) but family get first and is very demanding nowaday :-(
jdd
On Thursday 16 September 2021, jdd@dodin.org wrote:
Le 15/09/2021 à 17:34, Anton Aylward a écrit :
On 2021-09-14 16:52, Douglas McGarrett wrote:
(It worked in the past, on another Linux system.) --doug
Didn't someone say something about keeping a "log book" that covered things like how you set up systems in the past?
very difficult and time consuming job. I teached that more than 10 years ago and have some notes, but nor acurate nor complete now
http://www.dodin.org/wiki/pmwiki.php?n=Doc.Server-2021
http://www.dodin.org/wiki/pmwiki.php?n=Doc.OpenSUSE-small-ThirdEdition
I should update it (and build the server - I already lend one machine) but family get first and is very demanding nowaday :-(
jdd
It doesn't have to be time consuming. Even keeping a single text file of subject headings and bullet points is a big win over keeping no notes at all. Any time I solve a tricky or infrequently encountered problem I try to add a note as a reminder for next time. Examples of some of my notes: - ext4lazyinit is slow: - "In order to 'force' ext4lazyinit to finish the thing it does with maximum priority, you need to mount the filesystem with 'init_itable=0'. By default it is 10. ..." - The lazy itable init code will wait n times the number of milliseconds it took to zero out the previous block group's inode table. - can use remount to remount with -o init_itable=0 - samba - Disable the winbind service as it is not used and it delays start of the display-manager.service (sddm login) by making it dependent on starting nmb/winbind. systemctl mask winbind - Change systemd 90s (1:30 min Stop Job) wait on logout/shutdown: Edit /etc/systemd/system.conf Uncomment/set DefaultTimeoutStopSec=20s systemctl daemon-reexec # to get systemd to reload its config - Wayland force KDE Plasma Panel onto a specific monitor Screens (monitors) are defined in $HOME/.config/plasmashellrc searched for panel, and changed lastScreen in $HOME/.config/plasma-org.kde.plasma.desktop-appletsrc changed lastScreen from 0 to 1 I never delete notes just mark them as OBSOLETE. Copy the notes to a device that can be accessed when the machine is offline. Or periodically print them. Michael
On 21/09/2021 22.27, Michael Hamilton wrote:
On Thursday 16 September 2021, jdd@dodin.org wrote:
Le 15/09/2021 à 17:34, Anton Aylward a écrit : ... It doesn't have to be time consuming. Even keeping a single text file of subject headings and bullet points is a big win over keeping no notes at all.
Absolutely right :-)
Any time I solve a tricky or infrequently encountered problem I try to add a note as a reminder for next time. Examples of some of my notes:
- ext4lazyinit is slow: - "In order to 'force' ext4lazyinit to finish the thing it does with maximum priority, you need to mount the filesystem with 'init_itable=0'. By default it is 10. ..." - The lazy itable init code will wait n times the number of milliseconds it took to zero out the previous block group's inode table. - can use remount to remount with -o init_itable=0
I had forgotten this, but it is possible I archived a mail where this was commented :-) The problem is finding it.
- samba - Disable the winbind service as it is not used and it delays start of the display-manager.service (sddm login) by making it dependent on starting nmb/winbind. systemctl mask winbind
- Change systemd 90s (1:30 min Stop Job) wait on logout/shutdown: Edit /etc/systemd/system.conf Uncomment/set DefaultTimeoutStopSec=20s systemctl daemon-reexec # to get systemd to reload its config
- Wayland force KDE Plasma Panel onto a specific monitor Screens (monitors) are defined in $HOME/.config/plasmashellrc searched for panel, and changed lastScreen in $HOME/.config/plasma-org.kde.plasma.desktop-appletsrc changed lastScreen from 0 to 1
I never delete notes just mark them as OBSOLETE. Good point.
Copy the notes to a device that can be accessed when the machine is offline. Or periodically print them.
Or to all your computers, if you have them. -- Saludos/Cheers Carlos E. R.
It doesn't have to be time consuming. Even keeping a single text file of subject headings and bullet points is a big win over keeping no notes at all. That is excellent advice. I have to start doing that for quite a few
On 9/21/2021 4:27 PM, Michael Hamilton wrote: things, not just SuSE because it seems that life just gets more complicated and harder to remember. Even my cat is a victim of that. He has cancer and I am struggling to remember everything the vet says. Damon Register
Le 22/09/2021 à 11:13, Damon Register a écrit :
It doesn't have to be time consuming. Even keeping a single text file of subject headings and bullet points is a big win over keeping no notes at all. That is excellent advice. I have to start doing that for quite a few
On 9/21/2021 4:27 PM, Michael Hamilton wrote: things, not just SuSE because it seems that life just gets more complicated and harder to remember. Even my cat is a victim of that. He has cancer and I am struggling to remember everything the vet says.
Damon Register
nextcloud notes is an excellent system if you have any internet network at hand jdd -- http://dodin.org
On 9/15/21 11:34 AM, Anton Aylward wrote:
On 2021-09-14 16:52, Douglas McGarrett wrote:
(It worked in the past, on another Linux system.) --doug
Didn't someone say something about keeping a "log book" that covered things like how you set up systems in the past? I have a big fat notebook, about 1-1/2 inches thick, but I'm not perfect. --dm
Hello, In the Message; Subject : Re: XSane Message-ID : <162cc214-62b2-982b-3083-b49c95907600@optonline.net> Date & Time: Mon, 13 Sep 2021 22:57:33 -0400 [DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written: [...] DM> Downloaded file and let the system unpack it, but zypper won't install it and DM> rpm -Uvh file.rpm won't install it either. DM> linux1:~ # zypper install imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> Specified local path does not exist or is not accessible. DM> Problem retrieving the specified RPM file: DM> Malformed URI: DM> Please check whether the file is accessible. DM> Problem with the RPM file specified as DM> 'imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm', skipping. DM> No valid arguments specified. DM> linux1:~ # rpm -Uvh imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> error: open of imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm failed: No such DM> file or directory Yes, it's just a confusing file. After taz -zxf magescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz, # cd magescan-bundle-opensuse-15.2-3.65.0.x64.rpm # ./install.sh That is, magescan-bundle-opensuse-15.2-3.65.0.x64.rpm is not a file, but a directory. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ 『「世界で一番企業が活躍しやすい国」を目指します。』 --安部晋三『第１８３回国会における安倍内閣総理大臣施政方針演説』--
On 9/13/21 11:14 PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: XSane Message-ID : <162cc214-62b2-982b-3083-b49c95907600@optonline.net> Date & Time: Mon, 13 Sep 2021 22:57:33 -0400
[DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written:
[...] DM> Downloaded file and let the system unpack it, but zypper won't install it and DM> rpm -Uvh file.rpm won't install it either.
DM> linux1:~ # zypper install imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> Specified local path does not exist or is not accessible. DM> Problem retrieving the specified RPM file: DM> Malformed URI: DM> Please check whether the file is accessible. DM> Problem with the RPM file specified as DM> 'imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm', skipping. DM> No valid arguments specified.
DM> linux1:~ # rpm -Uvh imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> error: open of imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm failed: No such DM> file or directory
Yes, it's just a confusing file.
After taz -zxf magescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz,
# cd magescan-bundle-opensuse-15.2-3.65.0.x64.rpm # ./install.sh
That is, magescan-bundle-opensuse-15.2-3.65.0.x64.rpm is not a file, but a directory. You're right! It shows as a directory in the listing: drwxr-xr-x 1 root root 62 Jan 7 2021 imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm I didn't notice that. But how do I deal with it? --doug
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ 『「世界で一番企業が活躍しやすい国」を目指します。』
--安部晋三『第１８３回国会における安倍内閣総理大臣施政方針演説』--
Hello, In the Message; Subject : Re: XSane Message-ID : <7427579f-f308-ad63-2e3b-0fa6601f59e0@optonline.net> Date & Time: Tue, 14 Sep 2021 00:04:17 -0400 [DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written: [...] DM> > # cd magescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> > # ./install.sh DM> > DM> > That is, magescan-bundle-opensuse-15.2-3.65.0.x64.rpm is not a file, DM> > but a directory. DM> You're right! It shows as a directory in the listing: DM> drwxr-xr-x 1 root root 62 Jan 7 2021 DM> imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> I didn't notice that. But how do I deal with it? How about this? # rpm -ivh imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm/core/magescan-3.65.0-1epson4opensuse15.2.x86_64.rpm Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."
Hello,
In the Message;
Subject : Re: XSane Message-ID : <7427579f-f308-ad63-2e3b-0fa6601f59e0@optonline.net> Date & Time: Tue, 14 Sep 2021 00:04:17 -0400
[DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written:
[...] DM> > # cd magescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> > # ./install.sh DM> > DM> > That is, magescan-bundle-opensuse-15.2-3.65.0.x64.rpm is not a file, DM> > but a directory. DM> You're right! It shows as a directory in the listing: DM> drwxr-xr-x 1 root root 62 Jan 7 2021 DM> imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> I didn't notice that. But how do I deal with it?
How about this?
# rpm -ivh imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm/core/imagescan-3.65.0-1epson4opensuse15.2.x86_64.rpm
On 9/14/21 12:22 AM, Masaru Nomiya wrote: linux1:/home/doug/Downloads # rpm -ivh imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm/core/imagescan-3.65.0-1epson4opensuse15.2.x86_64.rpm Preparing... ################################# [100%] package imagescan-3.65.0-1epson4opensuse15.2.x86_64 is already installed --doug
Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."
On 2021-09-14 00:39, Douglas McGarrett wrote:
On 9/14/21 12:22 AM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: XSane Message-ID : <7427579f-f308-ad63-2e3b-0fa6601f59e0@optonline.net> Date & Time: Tue, 14 Sep 2021 00:04:17 -0400
[DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written:
[...] DM> > # cd magescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> > # ./install.sh DM> > DM> > That is, magescan-bundle-opensuse-15.2-3.65.0.x64.rpm is not a file, DM> > but a directory. DM> You're right! It shows as a directory in the listing: DM> drwxr-xr-x 1 root root 62 Jan 7 2021 DM> imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> I didn't notice that. But how do I deal with it?
How about this?
# rpm -ivh imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm/core/imagescan-3.65.0-1epson4opensuse15.2.x86_64.rpm
linux1:/home/doug/Downloads # rpm -ivh imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm/core/imagescan-3.65.0-1epson4opensuse15.2.x86_64.rpm
Preparing... ################################# [100%] package imagescan-3.65.0-1epson4opensuse15.2.x86_64 is already installed --doug
Indeed. On the whole, I prefer using zypper rather than raw rpm because zypper does some sanity & consistency and dependency checks. just saying ... -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg
On 9/14/21 7:44 AM, Anton Aylward wrote:
On 2021-09-14 00:39, Douglas McGarrett wrote:
On 9/14/21 12:22 AM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: XSane Message-ID : <7427579f-f308-ad63-2e3b-0fa6601f59e0@optonline.net> Date & Time: Tue, 14 Sep 2021 00:04:17 -0400
[DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written:
[...] DM> > # cd magescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> > # ./install.sh DM> > DM> > That is, magescan-bundle-opensuse-15.2-3.65.0.x64.rpm is not a file, DM> > but a directory. DM> You're right! It shows as a directory in the listing: DM> drwxr-xr-x 1 root root 62 Jan 7 2021 DM> imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> I didn't notice that. But how do I deal with it?
How about this?
# rpm -ivh imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm/core/imagescan-3.65.0-1epson4opensuse15.2.x86_64.rpm
linux1:/home/doug/Downloads # rpm -ivh imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm/core/imagescan-3.65.0-1epson4opensuse15.2.x86_64.rpm
Preparing... ################################# [100%] package imagescan-3.65.0-1epson4opensuse15.2.x86_64 is already installed --doug
Indeed. On the whole, I prefer using zypper rather than raw rpm because zypper does some sanity & consistency and dependency checks.
just saying ... I do use zypper, altho I am comfortable using the rpm -Uvh command. The -ivh mentioned above was suggested and so I went along. I forget what the difference is between Uvh and ivh, and I'm too lazy to go look it up! --doug
On 2021-09-14 18:53, Douglas McGarrett wrote:
I forget what the difference is between Uvh and ivh, and I'm too lazy to go look it up!
Just a guess i means install U means update Now i look at the RTFM ... NSTALLING, UPGRADING, AND REMOVING PACKAGES: rpm {-i|--install} [install-options] PACKAGE_FILE ... rpm {-U|--upgrade} [install-options] PACKAGE_FILE ... rpm {-F|--freshen} [install-options] PACKAGE_FILE ... rpm {-e|--erase} [--allmatches] [--justdb] [--nodeps] [--noscripts] [--notriggers] [--test] PACKAGE_NAME ... Seems pretty intuitive to me. Perhaps the authors weren't idiots. Want to bet that 'v' means 'verbose' Experience tells me that 'h' is for hash marks -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg
On 9/15/21 1:06 PM, Anton Aylward wrote:
On 2021-09-14 18:53, Douglas McGarrett wrote:
I forget what the difference is between Uvh and ivh, and I'm too lazy to go look it up!
Just a guess i means install U means update Now i look at the RTFM ...
NSTALLING, UPGRADING, AND REMOVING PACKAGES: rpm {-i|--install} [install-options] PACKAGE_FILE ... rpm {-U|--upgrade} [install-options] PACKAGE_FILE ... rpm {-F|--freshen} [install-options] PACKAGE_FILE ... rpm {-e|--erase} [--allmatches] [--justdb] [--nodeps] [--noscripts] [--notriggers] [--test] PACKAGE_NAME ...
Seems pretty intuitive to me. Perhaps the authors weren't idiots.
Want to bet that 'v' means 'verbose' Experience tells me that 'h' is for hash marks OK, thanks. I've always used -Uvh to install and it has always worked. I was taught that by some long-ago maven. and your second example shows that -Uvh works fine as an installer. --dm
Hello, Sorry for typo. In the Message; Subject : Re: XSane Message-ID : <87fsu7alx0.wl-nomiya@galaxy.dti.ne.jp> Date & Time: Tue, 14 Sep 2021 12:14:19 +0900 [MN] == Masaru Nomiya <nomiya@galaxy.dti.ne.jp> has written: [...] MN> Yes, it's just a confusing file. MN> After taz -zxf magescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz, After tar -zxf imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz, MN> # cd magescan-bundle-opensuse-15.2-3.65.0.x64.rpm cd imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm MN> # ./install.sh Regards, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "No Windows, no gains!" ..... "Why, I am wrong?" -- Bill --
On 9/14/21 12:12 AM, Masaru Nomiya wrote:
Hello,
Sorry for typo.
In the Message;
Subject : Re: XSane Message-ID : <87fsu7alx0.wl-nomiya@galaxy.dti.ne.jp> Date & Time: Tue, 14 Sep 2021 12:14:19 +0900
[MN] == Masaru Nomiya <nomiya@galaxy.dti.ne.jp> has written:
[...] MN> Yes, it's just a confusing file.
MN> After taz -zxf magescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz,
After tar -zxf imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz,
MN> # cd magescan-bundle-opensuse-15.2-3.65.0.x64.rpm
cd imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm
MN> # ./install.sh
Regards, Yes, that did something. It claims to have installed 11 files. But XSane Scanner Tool still says it can't find a scanner.
( 1/11) Installing: libGraphicsMagick3-config-1.3.35-bp153.2.14.x86_64 ........................................................[done] ( 2/11) Installing: libboost_program_options1_66_0-1.66.0-10.1.x86_64 .........................................................[done] ( 3/11) Installing: libwmf-0_2-7-0.2.8.4-2.30.x86_64 ..........................................................................[done] ( 4/11) Installing: libjpeg62-62.2.0-5.18.1.x86_64 ............................................................................[done] ( 5/11) Installing: libGraphicsMagick-Q16-3-1.3.35-bp153.2.14.x86_64 ..........................................................[done] ( 6/11) Installing: libGraphicsMagick++-Q16-12-1.3.35-bp153.2.14.x86_64 .......................................................[done] ( 7/11) Installing: GraphicsMagick-1.3.35-bp153.2.14.x86_64 ...................................................................[done] ( 8/11) Installing: imagescan-3.65.0-1epson4opensuse15.2.x86_64 ...............................................................[done] ( 9/11) Installing: imagescan-plugin-gt-s650-1.0.3-1epson4opensuse15.2.x86_64 .................................................[done] (10/11) Installing: imagescan-plugin-ocr-engine-1.0.3-1epson4opensuse15.2.x86_64 ..............................................[done] (11/11) Installing: imagescan-plugin-networkscan-1.1.4-1epson4opensuse15.2.x86_64 .............................................[done] The process complained that there are no gpg checks, but it had no other errors. (I know there are other scanner apps, but the ones I've seen don't have the capabilities of XSane.) Suggestions? --doug
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "No Windows, no gains!" ..... "Why, I am wrong?"
-- Bill --
Hello, In the Message; Subject : Re: XSane Message-ID : <993f249c-bfc1-f716-7531-923b1887a066@optonline.net> Date & Time: Tue, 14 Sep 2021 00:29:45 -0400 [DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written: DM> Yes, that did something. It claims to have installed 11 DM> files. But XSane Scanner Tool still says it can't find a scanner. [...] DM> The process complained that there are no gpg checks, but it had DM> no other errors. (I know there are other scanner apps, but the DM> ones I've seen don't have the capabilities of XSane.) Suggestions? Did you run this command? $ imagescan Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'
On 9/14/21 12:59 AM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: XSane Message-ID : <993f249c-bfc1-f716-7531-923b1887a066@optonline.net> Date & Time: Tue, 14 Sep 2021 00:29:45 -0400
[DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written:
DM> Yes, that did something. It claims to have installed 11 DM> files. But XSane Scanner Tool still says it can't find a scanner. [...] DM> The process complained that there are no gpg checks, but it had DM> no other errors. (I know there are other scanner apps, but the DM> ones I've seen don't have the capabilities of XSane.) Suggestions?
Did you run this command?
$ imagescan
This produces "no device found' --doug
Regards.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'
Hello, In the Message; Subject : Re: XSane Message-ID : <c7189729-f77b-0282-edfa-7c91545f0454@optonline.net> Date & Time: Tue, 14 Sep 2021 03:10:49 -0400 [DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written: MN> > Did you run this command? MN> > MN> > $ imagescan DM> This produces "no device found' Sorry, it may a wrong driver. Please download the file, iscan-bundle-2.30.4.x64.rpm.tar.gz from http://support.epson.net/linux/en/iscan_c.php?version=2.30.4 I've got no idea whether you can access it directly. If not, please enter from http://support.epson.net/ Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "No Windows, no gains!" ..... "Why, I am wrong?" -- Bill --
On 9/14/21 4:32 AM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: XSane Message-ID : <c7189729-f77b-0282-edfa-7c91545f0454@optonline.net> Date & Time: Tue, 14 Sep 2021 03:10:49 -0400
[DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written:
MN> > Did you run this command? MN> > MN> > $ imagescan
DM> This produces "no device found'
Sorry, it may a wrong driver.
Please download the file, iscan-bundle-2.30.4.x64.rpm.tar.gz from
http://support.epson.net/linux/en/iscan_c.php?version=2.30.4 I downloaded this, but it comes out weird. The tar file is half a GiB. I had the system extract it and it produces a batch of stuff, some of which is still in rpm format. I attach the KFind output. I don't know what to do with this. --doug
I've got no idea whether you can access it directly. If not, please enter from
Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "No Windows, no gains!" ..... "Why, I am wrong?"
-- Bill --
Good Morning, In the Message; Subject : Re: XSane Message-ID : <5b5c4b3d-3abb-a3eb-d31d-ce52fa9037da@optonline.net> Date & Time: Tue, 14 Sep 2021 18:13:37 -0400 [DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written: [...] DM> I downloaded this, but it comes out weird. The tar file is half a GiB. I had DM> the system extract it DM> and it produces a batch of stuff, some of which is still in rpm format. I attach DM> the KFind output. DM> I don't know what to do with this. [...] DM> KFind Results File DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm.tar.gz DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm DM> file:///usr/local/include/iscan DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm DM> file:///home/doug/.local/share/RecentDocuments/iscan_c.php.desktop DM> file:///home/doug/.local/share/RecentDocuments/iscanonical.ph.desktop DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/core/iscan-2.30.4-2.x86_64.rpm DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/data/iscan-data-1.39.2-1.noarch.rpm DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/plugins/iscan-network-nt-1.1.2-1.x86_64.rpm DM> file:///usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi/bits/iscanonical.ph The proper prcedure is; 1. # rpm -e imagescan 2. # cd /tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm 3. # ./install.sh That's all. Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."
On 9/14/21 6:42 PM, Masaru Nomiya wrote:
Good Morning,
In the Message;
Subject : Re: XSane Message-ID : <5b5c4b3d-3abb-a3eb-d31d-ce52fa9037da@optonline.net> Date & Time: Tue, 14 Sep 2021 18:13:37 -0400
[DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written:
[...] DM> I downloaded this, but it comes out weird. The tar file is half a GiB. I had DM> the system extract it DM> and it produces a batch of stuff, some of which is still in rpm format. I attach DM> the KFind output. DM> I don't know what to do with this. [...] DM> KFind Results File
DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm.tar.gz DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm DM> file:///usr/local/include/iscan DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm DM> file:///home/doug/.local/share/RecentDocuments/iscan_c.php.desktop DM> file:///home/doug/.local/share/RecentDocuments/iscanonical.ph.desktop DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/core/iscan-2.30.4-2.x86_64.rpm DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/data/iscan-data-1.39.2-1.noarch.rpm DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/plugins/iscan-network-nt-1.1.2-1.x86_64.rpm DM> file:///usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi/bits/iscanonical.ph
The proper prcedure is;
1. # rpm -e imagescan I did a "find" on "imagescan" and the only place it seems to be by itself is in /tmp/mozilla_doug0/ So I ran the command there: doug@linux1:/tmp/mozilla_doug0> rpm -e imagescan error: Failed dependencies: imagescan >= 3.28.0 is needed by (installed) imagescan-plugin-gt-s650-1.0.3-1epson4opensuse15.2.x86_64 imagescan >= 3.14.0 is needed by (installed) imagescan-plugin-ocr-engine-1.0.3-1epson4opensuse15.2.x86_64 imagescan >= 3.9.0 is needed by (installed) imagescan-plugin-networkscan-1.1.4-1epson4opensuse15.2.x86_64
So now I'm in that directory, but of course, the command in #3 fails. Obviously I've missed something along the way. Whoever coded the package at Epson must have expected a sys admin to deal with it. Of course, that would be me, but I'm not trained to be one! Can this mess be untangled? I'm not going to have too much time to play with this tonite, I have a doctor's appointment tomorrow and I'll have to get to bed at a reasonable hour for a change! --doug
2. # cd /tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm
3. # ./install.sh
That's all.
Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."
Hello, In the Message; Subject : Re: XSane Message-ID : <44a7b110-247b-0464-255e-b1503921d777@optonline.net> Date & Time: Tue, 14 Sep 2021 23:59:52 -0400 [DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written: [...] DM> > [...] DM> > DM> KFind Results File DM> > DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm.tar.gz DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm DM> > DM> file:///usr/local/include/iscan DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm DM> > DM> file:///home/doug/.local/share/RecentDocuments/iscan_c.php.desktop DM> > DM> file:///home/doug/.local/share/RecentDocuments/iscanonical.ph.desktop DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/core/iscan-2.30.4-2.x86_64.rpm DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/data/iscan-data-1.39.2-1.noarch.rpm DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/plugins/iscan-network-nt-1.1.2-1.x86_64.rpm DM> > DM> file:///usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi/bits/iscanonical.ph DM> > DM> > The proper prcedure is; DM> > DM> > 1. # rpm -e imagescan DM> I did a "find" on "imagescan" and the only place it seems to be by itself is in DM> /tmp/mozilla_doug0/ DM> So I ran the command there: doug@linux1:/tmp/mozilla_doug0> rpm -e imagescan DM> error: Failed dependencies: DM> imagescan >= 3.28.0 is needed by (installed) DM> imagescan-plugin-gt-s650-1.0.3-1epson4opensuse15.2.x86_64 DM> imagescan >= 3.14.0 is needed by (installed) DM> imagescan-plugin-ocr-engine-1.0.3-1epson4opensuse15.2.x86_64 DM> imagescan >= 3.9.0 is needed by (installed) DM> imagescan-plugin-networkscan-1.1.4-1epson4opensuse15.2.x86_64 DM> So now I'm in that directory, but of course, the command in #3 fails. DM> Obviously I've missed something along the way. Whoever coded the package DM> at Epson must have expected a sys admin to DM> deal with it. Of course, that would be me, but I'm not trained to be one! DM> Can this mess be untangled? Yes, you can. # rpm -e --nodeps $(rpm -qa | grep imagescan) Then, please install the iscam modules. DM> I'm not going to have too much time to play with this tonite, I DM> have a doctor's appointment tomorrow DM> and I'll have to get to bed at a reasonable hour for a change! Take care of yourself. Regards, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'
On 9/15/21 12:50 AM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: XSane Message-ID : <44a7b110-247b-0464-255e-b1503921d777@optonline.net> Date & Time: Tue, 14 Sep 2021 23:59:52 -0400
[DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written:
[...] DM> > [...] DM> > DM> KFind Results File DM> > DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm.tar.gz DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm DM> > DM> file:///usr/local/include/iscan DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm DM> > DM> file:///home/doug/.local/share/RecentDocuments/iscan_c.php.desktop DM> > DM> file:///home/doug/.local/share/RecentDocuments/iscanonical.ph.desktop DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/core/iscan-2.30.4-2.x86_64.rpm DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/data/iscan-data-1.39.2-1.noarch.rpm DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/plugins/iscan-network-nt-1.1.2-1.x86_64.rpm DM> > DM> file:///usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi/bits/iscanonical.ph DM> > DM> > The proper prcedure is; DM> > DM> > 1. # rpm -e imagescan DM> I did a "find" on "imagescan" and the only place it seems to be by itself is in DM> /tmp/mozilla_doug0/ DM> So I ran the command there: doug@linux1:/tmp/mozilla_doug0> rpm -e imagescan DM> error: Failed dependencies: DM> imagescan >= 3.28.0 is needed by (installed) DM> imagescan-plugin-gt-s650-1.0.3-1epson4opensuse15.2.x86_64 DM> imagescan >= 3.14.0 is needed by (installed) DM> imagescan-plugin-ocr-engine-1.0.3-1epson4opensuse15.2.x86_64 DM> imagescan >= 3.9.0 is needed by (installed) DM> imagescan-plugin-networkscan-1.1.4-1epson4opensuse15.2.x86_64
DM> So now I'm in that directory, but of course, the command in #3 fails. DM> Obviously I've missed something along the way. Whoever coded the package DM> at Epson must have expected a sys admin to DM> deal with it. Of course, that would be me, but I'm not trained to be one!
DM> Can this mess be untangled?
Yes, you can.
# rpm -e --nodeps $(rpm -qa | grep imagescan)
Then, please install the iscam modules.
DM> I'm not going to have too much time to play with this tonite, I DM> have a doctor's appointment tomorrow DM> and I'll have to get to bed at a reasonable hour for a change!
Take care of yourself.
Regards,
I'm sorry, I'm completely lost. I'm pretty sure nothing is installed. Here once again is the content of /tmp/mozilla_doug0 linux1:/tmp/mozilla_doug0 # ls -la total 1280 drwx------ 1 doug users 498 Sep 14 20:20 . drwxrwxrwt 1 root root 2706 Sep 15 15:06 .. -r-------- 1 doug users 1334 Jul 19 13:28 1_88863774.ics | These files are not part of Epson communications -r-------- 1 doug users 22213 Sep 14 20:13 Greetings Email Douglas McGarrett.20210914164025585.0.docx | They deal with an insurance claim for damage from -r-------- 1 doug users 774144 Sep 14 20:10 XactContents Import Template.20210914164025433.0.xls | the lightning strike in July. drwxr-xr-x 1 doug users 90 Jan 7 2021 imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm drwxr-xr-x 1 doug users 54 Aug 20 2019 iscan-bundle-2.30.4.x64.rpm -r-------- 1 doug users 502590 Sep 14 17:44 iscan-bundle-2.30.4.x64.rpm.tar.gz -r-------- 1 doug users 2135 Sep 14 20:20 I can't read the .html file--I don't know what app reads html. (Thunderbird does, but I don't know how to open it there.) Anyway, I see the words "iscan bundle" in it, so it might be useful. __
On 15/09/2021 21.46, Douglas McGarrett wrote:
On 9/15/21 12:50 AM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: XSane Message-ID : <44a7b110-247b-0464-255e-b1503921d777@optonline.net> Date & Time: Tue, 14 Sep 2021 23:59:52 -0400
[DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written:
[...] DM> > [...] DM> > DM> KFind Results File DM> > DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm.tar.gz DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm DM> > DM> file:///usr/local/include/iscan DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm DM> > DM> file:///home/doug/.local/share/RecentDocuments/iscan_c.php.desktop DM> > DM> file:///home/doug/.local/share/RecentDocuments/iscanonical.ph.desktop DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/core/iscan-2.30.4-2.x86_64.rpm DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/data/iscan-data-1.39.2-1.noarch.rpm DM> > DM> file:///tmp/mozilla_doug0/iscan-bundle-2.30.4.x64.rpm/iscan-bundle-2.30.4.x64.rpm/plugins/iscan-network-nt-1.1.2-1.x86_64.rpm DM> > DM> file:///usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi/bits/iscanonical.ph DM> > DM> > The proper prcedure is; DM> > DM> > 1. # rpm -e imagescan DM> I did a "find" on "imagescan" and the only place it seems to be by itself is in DM> /tmp/mozilla_doug0/ DM> So I ran the command there: doug@linux1:/tmp/mozilla_doug0> rpm -e imagescan DM> error: Failed dependencies: DM> imagescan >= 3.28.0 is needed by (installed) DM> imagescan-plugin-gt-s650-1.0.3-1epson4opensuse15.2.x86_64 DM> imagescan >= 3.14.0 is needed by (installed) DM> imagescan-plugin-ocr-engine-1.0.3-1epson4opensuse15.2.x86_64 DM> imagescan >= 3.9.0 is needed by (installed) DM> imagescan-plugin-networkscan-1.1.4-1epson4opensuse15.2.x86_64
DM> So now I'm in that directory, but of course, the command in #3 fails. DM> Obviously I've missed something along the way. Whoever coded the package DM> at Epson must have expected a sys admin to DM> deal with it. Of course, that would be me, but I'm not trained to be one!
DM> Can this mess be untangled?
Yes, you can.
# rpm -e --nodeps $(rpm -qa | grep imagescan)
Then, please install the iscam modules.
DM> I'm not going to have too much time to play with this tonite, I DM> have a doctor's appointment tomorrow DM> and I'll have to get to bed at a reasonable hour for a change!
Take care of yourself.
Regards,
I'm sorry, I'm completely lost. I'm pretty sure nothing is installed. Here once again is the content of /tmp/mozilla_doug0
Irrelevant. Just run the command he told you to run: rpm -e --nodeps $(rpm -qa | grep imagescan) Then continue with what he also told you, install the iscam modules.
I can't read the .html file--I don't know what app reads html. (Thunderbird does, but I don't know how to open it there.) Anyway, I see the words "iscan bundle" in it, so it might be useful.
With firefox. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Hello, In the Message; Subject : Re: XSane Message-ID : <da16ecbb-49f1-8f5f-52bd-cae0a4a82c4f@optonline.net> Date & Time: Wed, 15 Sep 2021 15:46:48 -0400 [DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written: DM> [1 <text/plain; utf-8 (8bit)>] DM> I'm sorry, I'm completely lost. I'm pretty sure nothing is DM> installed. Here once again is DM> the content of /tmp/mozilla_doug0 DM> linux1:/tmp/mozilla_doug0 # ls -la DM> total 1280 DM> drwx------ 1 doug users 498 Sep 14 20:20 . DM> drwxrwxrwt 1 root root 2706 Sep 15 15:06 .. DM> -r-------- 1 doug users 1334 Jul 19 13:28 1_88863774.ics | These files DM> are not part of Epson communications DM> -r-------- 1 doug users 22213 Sep 14 20:13 Greetings Email Douglas DM> McGarrett.20210914164025585.0.docx | They deal with an insurance claim DM> for damage from DM> -r-------- 1 doug users 774144 Sep 14 20:10 XactContents Import DM> Template.20210914164025433.0.xls | the lightning strike in DM> July. DM> drwxr-xr-x 1 doug users 90 Jan 7 2021 DM> imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> drwxr-xr-x 1 doug users 54 Aug 20 2019 iscan-bundle-2.30.4.x64.rpm DM> -r-------- 1 doug users 502590 Sep 14 17:44 iscan-bundle-2.30.4.x64.rpm.tar.gz DM> -r-------- 1 doug users 2135 Sep 14 20:20 DM> I can't read the .html file--I don't know what app reads html. (Thunderbird DM> does, but I don't know how to open it there.) DM> Anyway, I see the words "iscan bundle" in it, so it might be useful. Sorry, I'm a little bit confused. If # rpm -qa | grep imagescan returens nothing, then please do as follows; # cd /tmp/mozilla_doug0/imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm # ./install.sh Or, # rpm -qa | grep imagescan returens files name? Regards, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."
On 16/09/2021 04.29, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: XSane Message-ID : <da16ecbb-49f1-8f5f-52bd-cae0a4a82c4f@optonline.net> Date & Time: Wed, 15 Sep 2021 15:46:48 -0400
[DM] == Douglas McGarrett <dmcgarrett@optonline.net> has written:
DM> [1 <text/plain; utf-8 (8bit)>]
DM> I'm sorry, I'm completely lost. I'm pretty sure nothing is DM> installed. Here once again is DM> the content of /tmp/mozilla_doug0
DM> linux1:/tmp/mozilla_doug0 # ls -la DM> total 1280 DM> drwx------ 1 doug users 498 Sep 14 20:20 . DM> drwxrwxrwt 1 root root 2706 Sep 15 15:06 .. DM> -r-------- 1 doug users 1334 Jul 19 13:28 1_88863774.ics | These files DM> are not part of Epson communications DM> -r-------- 1 doug users 22213 Sep 14 20:13 Greetings Email Douglas DM> McGarrett.20210914164025585.0.docx | They deal with an insurance claim DM> for damage from DM> -r-------- 1 doug users 774144 Sep 14 20:10 XactContents Import DM> Template.20210914164025433.0.xls | the lightning strike in DM> July. DM> drwxr-xr-x 1 doug users 90 Jan 7 2021 DM> imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm DM> drwxr-xr-x 1 doug users 54 Aug 20 2019 iscan-bundle-2.30.4.x64.rpm DM> -r-------- 1 doug users 502590 Sep 14 17:44 iscan-bundle-2.30.4.x64.rpm.tar.gz DM> -r-------- 1 doug users 2135 Sep 14 20:20
DM> I can't read the .html file--I don't know what app reads html. (Thunderbird DM> does, but I don't know how to open it there.) DM> Anyway, I see the words "iscan bundle" in it, so it might be useful.
Sorry, I'm a little bit confused.
He doesn't understand that "rpm -e something" works on a database, so he thinks that to uninstall "something" rpm he must first go to the directory where "something" file is, and not finding it, he is stuck. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 15/09/2021 05.59, Douglas McGarrett wrote:
On 9/14/21 6:42 PM, Masaru Nomiya wrote:
...
The proper prcedure is;
1. # rpm -e imagescan I did a "find" on "imagescan" and the only place it seems to be by itself is in /tmp/mozilla_doug0/
You do not need to do a "find" on "imagescan", it doesn't matter where you do an "rpm -e something", as long as "something" is installed. ... -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 14/09/2021 03.40, Douglas McGarrett wrote:
Now that I can see the Epson printer and print to it, I would like to get the scanner to work also. When I select XSane Scanner Tool, I get a box "no devices available" --the scanner is part of the Epson printer and works manually. I wonder if this is the problem I had several years ago that required an addition to one of the driver files, but I don't know how to find out. I think I did mention it in a note to the group, but I don't know if that was for the scanner or the printer. (Also, there seem to be several email paths to the folks at OS, so I don't know which one it would have been.)
Why don't you keep a notebook? A lab book? -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 14/09/2021 03.40, Douglas McGarrett wrote:
Now that I can see the Epson printer and print to it, I would like to get the scanner to work also. When I select XSane Scanner Tool, I get a box "no devices available" --the scanner is part of the Epson printer and works manually. I wonder if this is the problem I had several years ago that required an addition to one of the driver files, but I don't know how to find out. I think I did mention it in a note to the group, but I don't know if that was for the scanner or the printer. (Also, there seem to be several email paths to the folks at OS, so I don't know which one it would have been.) Why don't you keep a notebook? A lab book? I do, but this particular thing isn't in it. I have a number of things regarding
On 9/14/21 7:21 AM, Carlos E. R. wrote: the scanner, but (a) I don't remember the added file I needed in Tumbleweed, and (b) I didn't write it down. I'm not perfect. --doug
I did not read the whole thread, try to install the package libusb-1_0-0-32bit Regards, Francesco On Tue, Sep 14, 2021 at 3:41 AM Douglas McGarrett <dmcgarrett@optonline.net> wrote:
Now that I can see the Epson printer and print to it, I would like to get the scanner to work also. When I select XSane Scanner Tool, I get a box "no devices available" --the scanner is part of the Epson printer and works manually. I wonder if this is the problem I had several years ago that required an addition to one of the driver files, but I don't know how to find out. I think I did mention it in a note to the group, but I don't know if that was for the scanner or the printer. (Also, there seem to be several email paths to the folks at OS, so I don't know which one it would have been.) --doug
-- There is a theory which states that if ever anyone discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable. There is another theory which states that this has already happened. -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"
On 9/15/21 8:32 AM, Francesco Teodori wrote:
I did not read the whole thread, try to install the package
libusb-1_0-0-32bit
Regards,
Francesco I have been off-line for a week for medical reasons. Why would I install a 32-bit app on a 64-bit machine? --doug
On Tue, Sep 14, 2021 at 3:41 AM Douglas McGarrett <dmcgarrett@optonline.net> wrote:
Now that I can see the Epson printer and print to it, I would like to get the scanner to work also. When I select XSane Scanner Tool, I get a box "no devices available" --the scanner is part of the Epson printer and works manually. I wonder if this is the problem I had several years ago that required an addition to one of the driver files, but I don't know how to find out. I think I did mention it in a note to the group, but I don't know if that was for the scanner or the printer. (Also, there seem to be several email paths to the folks at OS, so I don't know which one it would have been.) --doug
I had a similar issue, I found it was a driver problem, I solved by installing that package. It is a 32 bit compatibility package. It is packaged for 64 bit systems. Regards, Francesco On Wed, Sep 22, 2021 at 7:57 PM Douglas McGarrett <dmcgarrett@optonline.net> wrote:
On 9/15/21 8:32 AM, Francesco Teodori wrote:
I did not read the whole thread, try to install the package
libusb-1_0-0-32bit
Regards,
Francesco I have been off-line for a week for medical reasons. Why would I install a 32-bit app on a 64-bit machine? --doug
On Tue, Sep 14, 2021 at 3:41 AM Douglas McGarrett <dmcgarrett@optonline.net> wrote:
Now that I can see the Epson printer and print to it, I would like to get the scanner to work also. When I select XSane Scanner Tool, I get a box "no devices available" --the scanner is part of the Epson printer and works manually. I wonder if this is the problem I had several years ago that required an addition to one of the driver files, but I don't know how to find out. I think I did mention it in a note to the group, but I don't know if that was for the scanner or the printer. (Also, there seem to be several email paths to the folks at OS, so I don't know which one it would have been.) --doug
-- There is a theory which states that if ever anyone discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable. There is another theory which states that this has already happened. -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"
On 9/13/21 9:40 PM, Douglas McGarrett wrote:
Now that I can see the Epson printer and print to it, I would like to get the scanner to work also. When I select XSane Scanner Tool, I get a box "no devices available" --the scanner is part of the Epson printer and works manually. I wonder if this is the problem I had several years ago that required an addition to one of the driver files, but I don't know how to find out. I think I did mention it in a note to the group, but I don't know if that was for the scanner or the printer. (Also, there seem to be several email paths to the folks at OS, so I don't know which one it would have been.) --doug
IIRC last year and the year before about this time you had problems with this printer/scanner. I seem to recall that you had downloaded driver files from the Epson site that included a shell script which you ran and which installed old proprietary drivers that did not work. You were instructed to install an openSUSE drivers package in which there was the necessary driver and then to use YaST to install it. In the other case, you had gotten a tar file, unpacked it, and borked the system trying to install pieces therein. While my memory is rusty about details in each case, I do remember that you had us going in circles for weeks/months each time. And in one instance, a solution had been provided on the Forums a couple months previous which you had not informed us of. But there apparently was a solution and the scanner was working (right?). I'm not about to try to de/reconstruct all that again. If in 2019 and/or 2020 there was a solution, maybe you should find those posts. --dg
On 9/13/21 9:40 PM, Douglas McGarrett wrote:
Now that I can see the Epson printer and print to it, I would like to get the scanner to work also. When I select XSane Scanner Tool, I get a box "no devices available" --the scanner is part of the Epson printer and works manually. I wonder if this is the problem I had several years ago that required an addition to one of the driver files, but I don't know how to find out. I think I did mention it in a note to the group, but I don't know if that was for the scanner or the printer. (Also, there seem to be several email paths to the folks at OS, so I don't know which one it would have been.) --doug
IIRC last year and the year before about this time you had problems with this printer/scanner. I seem to recall that you had downloaded driver files from the Epson site that included a shell script which you ran and which installed old proprietary drivers that did not work. You were instructed to install an openSUSE drivers package in which there was the necessary driver and then to use YaST to install it. In the other case, you had gotten a tar file, unpacked it, and borked the system trying to install pieces therein.
While my memory is rusty about details in each case, I do remember that you had us going in circles for weeks/months each time. And in one instance, a solution had been provided on the Forums a couple months previous which you had not informed us of. But there apparently was a solution and the scanner was working (right?).
I'm not about to try to de/reconstruct all that again. If in 2019 and/or 2020 there was a solution, maybe you should find those posts.
--dg Yes, I got it working in 2019. As someone already said, I should have
On 9/15/21 2:15 PM, DennisG wrote: put it in my paper logbook, but it got overlooked. If someone can tell me how to find those emails (and not a stack of completely unrelated ones from everybody about everything) I would be extremely happy to look them up! I do remember that there was a file MISSING from OpenSUSE that I had to copy from another Linux system. I don't think I have that system anymore to copy from since I had a lot of destruction recently due to lightning. --doug
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
On 9/13/21 9:40 PM, Douglas McGarrett wrote:
Now that I can see the Epson printer and print to it, I would like to get the scanner to work also. When I select XSane Scanner Tool, I get a box "no devices available" --the scanner is part of the Epson printer and works manually. I wonder if this is the problem I had several years ago that required an addition to one of the driver files, but I don't know how to find out. I think I did mention it in a note to the group, but I don't know if that was for the scanner or the printer. (Also, there seem to be several email paths to the folks at OS, so I don't know which one it would have been.) --doug
IIRC last year and the year before about this time you had problems with this printer/scanner. I seem to recall that you had downloaded driver files from the Epson site that included a shell script which you ran and which installed old proprietary drivers that did not work. You were instructed to install an openSUSE drivers package in which there was the necessary driver and then to use YaST to install it. In the other case, you had gotten a tar file, unpacked it, and borked the system trying to install pieces therein.
While my memory is rusty about details in each case, I do remember that you had us going in circles for weeks/months each time. And in one instance, a solution had been provided on the Forums a couple months previous which you had not informed us of. But there apparently was a solution and the scanner was working (right?).
I'm not about to try to de/reconstruct all that again. If in 2019 and/or 2020 there was a solution, maybe you should find those posts.
--dg Yes, I got it working in 2019. As someone already said, I should have
On 9/15/21 2:15 PM, DennisG wrote: put it in my paper logbook, but it got overlooked. If someone can tell me how to find those emails (and not a stack of completely unrelated ones from everybody about everything) I would be extremely happy to look them up! I do remember that there was a file MISSING from OpenSUSE that I had to copy from another Linux system. I don't think I have that system anymore to copy from since I had a lot of destruction recently due to lightning. --doug
IIRC one of those cases was the printer but the other case the scanner. I seem to recall there was a set of files from Epson that provided a front-end for the scanner (a bells&whistles xsane), but those wouldn't work (I don't recall why). Inside those pieces was a proprietary driver that can't be provided by opensuse. But didn't we find that there was a driver available inside a package of drivers you had not installed, once you did that you could install the scanner with YaST? (You do know that your Epson has to be installed twice, as a printer and separately as a scanner?) I don't know if there is an archive of these lists. --dg Leap 15.2 & 15.3/KDE
On 23/09/2021 00.28, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
On 9/13/21 9:40 PM, Douglas McGarrett wrote:
Now that I can see the Epson printer and print to it, I would like to get the scanner to work also. When I select XSane Scanner Tool, I get a box "no devices available" --the scanner is part of the Epson printer and works manually. I wonder if this is the problem I had several years ago that required an addition to one of the driver files, but I don't know how to find out. I think I did mention it in a note to the group, but I don't know if that was for the scanner or the printer. (Also, there seem to be several email paths to the folks at OS, so I don't know which one it would have been.) --doug
IIRC last year and the year before about this time you had problems with this printer/scanner. I seem to recall that you had downloaded driver files from the Epson site that included a shell script which you ran and which installed old proprietary drivers that did not work. You were instructed to install an openSUSE drivers package in which there was the necessary driver and then to use YaST to install it. In the other case, you had gotten a tar file, unpacked it, and borked the system trying to install pieces therein.
While my memory is rusty about details in each case, I do remember that you had us going in circles for weeks/months each time. And in one instance, a solution had been provided on the Forums a couple months previous which you had not informed us of. But there apparently was a solution and the scanner was working (right?).
I'm not about to try to de/reconstruct all that again. If in 2019 and/or 2020 there was a solution, maybe you should find those posts.
--dg Yes, I got it working in 2019. As someone already said, I should have
On 9/15/21 2:15 PM, DennisG wrote: put it in my paper logbook, but it got overlooked. If someone can tell me how to find those emails (and not a stack of completely unrelated ones from everybody about everything) I would be extremely happy to look them up! I do remember that there was a file MISSING from OpenSUSE that I had to copy from another Linux system. I don't think I have that system anymore to copy from since I had a lot of destruction recently due to lightning. --doug
IIRC one of those cases was the printer but the other case the scanner. I seem to recall there was a set of files from Epson that provided a front-end for the scanner (a bells&whistles xsane), but those wouldn't work (I don't recall why). Inside those pieces was a proprietary driver that can't be provided by opensuse. But didn't we find that there was a driver available inside a package of drivers you had not installed, once you did that you could install the scanner with YaST? (You do know that your Epson has to be installed twice, as a printer and separately as a scanner?)
I don't know if there is an archive of these lists.
Of course there is, look at the headers of your own email. Your email is archived at Archived-At: <https://lists.opensuse.org/archives/list/users@lists.opensuse.org/message/JMVKIWHCZJ6OWE74W26LQEIX6A5URXGS/> -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 9/22/21 6:50 PM, Carlos E. R. wrote:
On 23/09/2021 00.28, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
long snip
I don't know if there is an archive of these lists. Of course there is, look at the headers of your own email.
Your email is archived at
Archived-At: <https://lists.opensuse.org/archives/list/users@lists.opensuse.org/message/JMVKIWHCZJ6OWE74W26LQEIX6A5URXGS/>
Seems it's my turn to wear the dunce cap . . . I looked at the headers of the email (I use T'Bird) but I don't see a string anythink like JMVK.... What am I missing??? (I didn't know for sure whether this list is archived.) Thanks! --dg Leap 15.2 & 15.3/KDE
* DennisG <dwgallien@gmail.com> [09-23-21 11:59]:
On 9/22/21 6:50 PM, Carlos E. R. wrote:
On 23/09/2021 00.28, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
long snip
I don't know if there is an archive of these lists. Of course there is, look at the headers of your own email.
Your email is archived at
Archived-At: <https://lists.opensuse.org/archives/list/users@lists.opensuse.org/message/JMVKIWHCZJ6OWE74W26LQEIX6A5URXGS/>
Seems it's my turn to wear the dunce cap . . .
I looked at the headers of the email (I use T'Bird) but I don't see a string anythink like JMVK.... What am I missing???
(I didn't know for sure whether this list is archived.)
it most certainly is, https://lists.opensuse.org/archives/list/users@lists.opensuse.org/ but you could have found that if you looked. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
On 9/23/21 12:12 PM, Patrick Shanahan wrote:
* DennisG <dwgallien@gmail.com> [09-23-21 11:59]:
On 9/22/21 6:50 PM, Carlos E. R. wrote:
On 23/09/2021 00.28, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote: long snip
I don't know if there is an archive of these lists. Of course there is, look at the headers of your own email.
Your email is archived at
Archived-At: <https://lists.opensuse.org/archives/list/users@lists.opensuse.org/message/JMVKIWHCZJ6OWE74W26LQEIX6A5URXGS/> Seems it's my turn to wear the dunce cap . . .
I looked at the headers of the email (I use T'Bird) but I don't see a string anythink like JMVK.... What am I missing???
(I didn't know for sure whether this list is archived.)
it most certainly is, https://lists.opensuse.org/archives/list/users@lists.opensuse.org/
but you could have found that if you looked.
You have a fair complaint. I obsessed over the message string, but of course when I used the base url I found the archives. Sorry 'bout that. Thanks, Patrick. --dg 15.2/15.3/KDE
On 9/23/21 11:54 AM, DennisG wrote:
On 9/22/21 6:50 PM, Carlos E. R. wrote:
On 23/09/2021 00.28, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
long snip
I don't know if there is an archive of these lists. Of course there is, look at the headers of your own email.
Your email is archived at
Archived-At: <https://lists.opensuse.org/archives/list/users@lists.opensuse.org/message/JMVKIWHCZJ6OWE74W26LQEIX6A5URXGS/>
/snip/ Went to that site. Selected 2019, and picked a month. It looks like there is every email from everybody there. I don't know how to select just _my_ from/to email. --doug
On 23/09/2021 17.54, DennisG wrote:
On 9/22/21 6:50 PM, Carlos E. R. wrote:
On 23/09/2021 00.28, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
long snip
I don't know if there is an archive of these lists. Of course there is, look at the headers of your own email.
Your email is archived at
Archived-At: <https://lists.opensuse.org/archives/list/users@lists.opensuse.org/message/JMVKIWHCZJ6OWE74W26LQEIX6A5URXGS/>
Seems it's my turn to wear the dunce cap . . .
I looked at the headers of the email (I use T'Bird) but I don't see a string anythink like JMVK.... What am I missing???
Ctrl-U, then search for "Archived-At:".
(I didn't know for sure whether this list is archived.)
All *S[uU]SE mail lists have been archived for decades, except one, the offtopic mail list,. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 9/22/21 6:28 PM, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
On 9/15/21 2:15 PM, DennisG wrote:
On 9/13/21 9:40 PM, Douglas McGarrett wrote:
Now that I can see the Epson printer and print to it, I would like to get the scanner to work also. When I select XSane Scanner Tool, I get a box "no devices available" --the scanner is part of the Epson printer and works manually. I wonder if this is the problem I had several years ago that required an addition to one of the driver files, but I don't know how to find out. I think I did mention it in a note to the group, but I don't know if that was for the scanner or the printer. (Also, there seem to be several email paths to the folks at OS, so I don't know which one it would have been.) --doug
IIRC last year and the year before about this time you had problems with this printer/scanner. I seem to recall that you had downloaded driver files from the Epson site that included a shell script which you ran and which installed old proprietary drivers that did not work. You were instructed to install an openSUSE drivers package in which there was the necessary driver and then to use YaST to install it. In the other case, you had gotten a tar file, unpacked it, and borked the system trying to install pieces therein.
While my memory is rusty about details in each case, I do remember that you had us going in circles for weeks/months each time. And in one instance, a solution had been provided on the Forums a couple months previous which you had not informed us of. But there apparently was a solution and the scanner was working (right?).
Yes, after a lot of trouble and back-and-forth, I got the scanner to work. I need it again, somehow.
I'm not about to try to de/reconstruct all that again. If in 2019 and/or 2020 there was a solution, maybe you should find those posts.
--dg
Yes, I got it working in 2019. As someone already said, I should have put it in my paper logbook, but it got overlooked. If someone can tell me how to find those emails (and not a stack of completely unrelated ones from everybody about everything) I would be extremely happy to look them up! I do remember that there was a file MISSING from OpenSUSE that I had to copy from another Linux system. I don't think I have that system anymore to copy from since I had a lot of destruction recently due to lightning. --doug
IIRC one of those cases was the printer but the other case the scanner. I seem to recall there was a set of files from Epson that provided a front-end for the scanner (a bells&whistles xsane), but those wouldn't work (I don't recall why). Inside those pieces was a proprietary driver that can't be provided by opensuse. But didn't we find that there was a driver available inside a package of drivers you had not installed, once you did that you could install the scanner with YaST? (You do know that your Epson has to be installed twice, as a printer and separately as a scanner?)
I don't know if there is an archive of these lists.
--dg Leap 15.2 & 15.3/KDE
On 9/23/21 12:57 AM, Douglas McGarrett wrote:
On 9/22/21 6:28 PM, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
snip
Yes, after a lot of trouble and back-and-forth, I got the scanner to work. I need it again, somehow.
I'm not about to try to de/reconstruct all that again. If in 2019 and/or 2020 there was a solution, maybe you should find those posts.
--dg
Yes, I got it working in 2019. As someone already said, I should have put it in my paper logbook, but it got overlooked. If someone can tell me how to find those emails (and not a stack of completely unrelated ones from everybody about everything) I would be extremely happy to look them up! I do remember that there was a file MISSING from OpenSUSE that I had to copy from another Linux system. I don't think I have that system anymore to copy from since I had a lot of destruction recently due to lightning. --doug
snip
Ok Doug, I think I found the solution by scanning through my personal email archive . . . this was all in mid-2019. There are 3 pieces here. I think the third was the solution. First, you downloaded imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz from the Epson site and ran the install script, but it failed because there were two components that are proprietary to Epson which would not install (for several reasons, too detailed to recap here). Second, you found a firmware for the Epson V300 somewhere else which you were able to install but still left the machine not working properly. I don't think that firmware is applicable for your particular model. Third, I pointed you to the iscan package which is in the Packman repository. It provides the proprietary front-end pieces that opensuse cannot. So just run YaST/Software, search for iscan, install it, and then you should be able to install the scanner with YaST/Scanner. This worked before. NOTE: I am presuming the Epson is attached via USB, and so it is not networked on the LAN. If it is networked and YaST does not see it after installing the iscan package, you may need to install an additional package. But I'm not going to go there unless the Epson is networked _and_ the iscan package by itself does not solve the problem. Good luck. --dg Leap 15.2 & 15.3/KDE
On 23/09/2021 19.34, DennisG wrote:
On 9/23/21 12:57 AM, Douglas McGarrett wrote:
On 9/22/21 6:28 PM, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
Ok Doug, I think I found the solution by scanning through my personal email archive . . . this was all in mid-2019.
There are 3 pieces here. I think the third was the solution.
First, you downloaded imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz from the Epson site and ran the install script, but it failed because there were two components that are proprietary to Epson which would not install (for several reasons, too detailed to recap here).
Second, you found a firmware for the Epson V300 somewhere else which you were able to install but still left the machine not working properly. I don't think that firmware is applicable for your particular model.
Third, I pointed you to the iscan package which is in the Packman repository. It provides the proprietary front-end pieces that opensuse cannot. So just run YaST/Software, search for iscan, install it, and then you should be able to install the scanner with YaST/Scanner. This worked before.
Doug, see attached photo. Start "yast2", click on the "software management" module, when it opens click on "search" and type "iscan", then select the resulting package, which as you see comes from repository packman. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 9/23/21 4:56 PM, Carlos E. R. wrote:
On 23/09/2021 19.34, DennisG wrote:
On 9/23/21 12:57 AM, Douglas McGarrett wrote:
On 9/22/21 6:28 PM, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
Ok Doug, I think I found the solution by scanning through my personal email archive . . . this was all in mid-2019.
There are 3 pieces here. I think the third was the solution.
First, you downloaded imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz from the Epson site and ran the install script, but it failed because there were two components that are proprietary to Epson which would not install (for several reasons, too detailed to recap here).
Second, you found a firmware for the Epson V300 somewhere else which you were able to install but still left the machine not working properly. I don't think that firmware is applicable for your particular model.
Third, I pointed you to the iscan package which is in the Packman repository. It provides the proprietary front-end pieces that opensuse cannot. So just run YaST/Software, search for iscan, install it, and then you should be able to install the scanner with YaST/Scanner. This worked before. Doug, see attached photo.
Start "yast2", click on the "software management" module, when it opens click on "search" and type "iscan", then select the resulting package, which as you see comes from repository packman.
I think I did it right, but when it came to detecting scanners, it did not find the scanner. It looked for Epson 2 driver, which I'm pretty sure is correct, but when looking for the scanner, it couldn't find it. When snapping on the XSane Scanner Tool icon, the machine hangs up and I have to manually terminate. (Somebody a day or two ago had me do some trick that verified that the scanner CAN be found. I don't remember how that was done, or what its relevance may be.) Closer, maybe, but still no cigar! --doug
On 24/09/2021 01.42, Douglas McGarrett wrote:
On 9/23/21 4:56 PM, Carlos E. R. wrote:
On 23/09/2021 19.34, DennisG wrote:
On 9/23/21 12:57 AM, Douglas McGarrett wrote:
On 9/22/21 6:28 PM, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
Ok Doug, I think I found the solution by scanning through my personal email archive . . . this was all in mid-2019.
There are 3 pieces here. I think the third was the solution.
First, you downloaded imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz from the Epson site and ran the install script, but it failed because there were two components that are proprietary to Epson which would not install (for several reasons, too detailed to recap here).
Second, you found a firmware for the Epson V300 somewhere else which you were able to install but still left the machine not working properly. I don't think that firmware is applicable for your particular model.
Third, I pointed you to the iscan package which is in the Packman repository. It provides the proprietary front-end pieces that opensuse cannot. So just run YaST/Software, search for iscan, install it, and then you should be able to install the scanner with YaST/Scanner. This worked before. Doug, see attached photo.
Start "yast2", click on the "software management" module, when it opens click on "search" and type "iscan", then select the resulting package, which as you see comes from repository packman.
I think I did it right, but when it came to detecting scanners, it did not find the scanner. It looked for Epson 2 driver, which I'm pretty sure is correct, but when looking for the scanner, it couldn't find it. When snapping on the XSane Scanner Tool icon, the machine hangs up and I have to manually terminate. (Somebody a day or two ago had me do some trick that verified that the scanner CAN be found. I don't remember how that was done, or what its relevance may be.)
Sigh... it is in this very same thread, I'm not going to dig it our for you. If you have lost the email, we told you not 24 hours ago how to look in the web archive. Which reminds me that your scanner is on the network, so some of what DennisG told you does not apply, as he told you it was for USB.
Closer, maybe, but still no cigar! --doug
-- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 9/23/21 7:52 PM, Carlos E. R. wrote:
On 24/09/2021 01.42, Douglas McGarrett wrote:
On 9/23/21 4:56 PM, Carlos E. R. wrote:
On 23/09/2021 19.34, DennisG wrote:
On 9/22/21 6:28 PM, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote: Ok Doug, I think I found the solution by scanning through my
On 9/23/21 12:57 AM, Douglas McGarrett wrote: personal email archive . . . this was all in mid-2019.
There are 3 pieces here. I think the third was the solution.
First, you downloaded imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz from the Epson site and ran the install script, but it failed because there were two components that are proprietary to Epson which would not install (for several reasons, too detailed to recap here).
Second, you found a firmware for the Epson V300 somewhere else which you were able to install but still left the machine not working properly. I don't think that firmware is applicable for your particular model.
Third, I pointed you to the iscan package which is in the Packman repository. It provides the proprietary front-end pieces that opensuse cannot. So just run YaST/Software, search for iscan, install it, and then you should be able to install the scanner with YaST/Scanner. This worked before. Doug, see attached photo.
Start "yast2", click on the "software management" module, when it opens click on "search" and type "iscan", then select the resulting package, which as you see comes from repository packman.
I think I did it right, but when it came to detecting scanners, it did not find the scanner. It looked for Epson 2 driver, which I'm pretty sure is correct, but when looking for the scanner, it couldn't find it. When snapping on the XSane Scanner Tool icon, the machine hangs up and I have to manually terminate. (Somebody a day or two ago had me do some trick that verified that the scanner CAN be found. I don't remember how that was done, or what its relevance may be.) Sigh... it is in this very same thread, I'm not going to dig it our for you. If you have lost the email, we told you not 24 hours ago how to look in the web archive. OK, I'll find it. Not sure what good it will do. . . . --dm
Which reminds me that your scanner is on the network, so some of what DennisG told you does not apply, as he told you it was for USB.
Closer, maybe, but still no cigar! --doug
On 9/23/21 1:34 PM, DennisG wrote:
On 9/23/21 12:57 AM, Douglas McGarrett wrote:
On 9/22/21 6:28 PM, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
snip
Yes, after a lot of trouble and back-and-forth, I got the scanner to work. I need it again, somehow.
I'm not about to try to de/reconstruct all that again. If in 2019 and/or 2020 there was a solution, maybe you should find those posts.
--dg
Yes, I got it working in 2019. As someone already said, I should have put it in my paper logbook, but it got overlooked. If someone can tell me how to find those emails (and not a stack of completely unrelated ones from everybody about everything) I would be extremely happy to look them up! I do remember that there was a file MISSING from OpenSUSE that I had to copy from another Linux system. I don't think I have that system anymore to copy from since I had a lot of destruction recently due to lightning. --doug
snip
Ok Doug, I think I found the solution by scanning through my personal email archive . . . this was all in mid-2019.
There are 3 pieces here. I think the third was the solution.
First, you downloaded imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz from the Epson site and ran the install script, but it failed because there were two components that are proprietary to Epson which would not install (for several reasons, too detailed to recap here).
Second, you found a firmware for the Epson V300 somewhere else which you were able to install but still left the machine not working properly. I don't think that firmware is applicable for your particular model.
Third, I pointed you to the iscan package which is in the Packman repository. It provides the proprietary front-end pieces that opensuse cannot. So just run YaST/Software, search for iscan, install it, and then you should be able to install the scanner with YaST/Scanner. This worked before.
NOTE: I am presuming the Epson is attached via USB, and so it is not networked on the LAN. If it is networked and YaST does not see it after installing the iscan package, you may need to install an additional package. But I'm not going to go there unless the Epson is networked _and_ the iscan package by itself does not solve the problem.
Good luck.
--dg Leap 15.2 & 15.3/KDE Yes, also Leap 15.3 and KDE. Anyway, the Epson is on the lan, not usb. I have installed the iscan package. The system still can't find the scanner, altho it prints to the printer OK. I tried to look thru the past q&a on scanners, but it goes on past 70 items, and covers quite a few years. I also have not been able to find ONLY MY OWN correspondence trail on the question from 2019. (When I was running Tumbleweed, btw.) --doug
On 9/24/21 2:12 PM, Douglas McGarrett wrote:
On 9/23/21 1:34 PM, DennisG wrote:
On 9/23/21 12:57 AM, Douglas McGarrett wrote:
On 9/22/21 6:28 PM, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
snip
Yes, after a lot of trouble and back-and-forth, I got the scanner to work. I need it again, somehow.
I'm not about to try to de/reconstruct all that again. If in 2019 and/or 2020 there was a solution, maybe you should find those posts.
--dg
Yes, I got it working in 2019. As someone already said, I should have put it in my paper logbook, but it got overlooked. If someone can tell me how to find those emails (and not a stack of completely unrelated ones from everybody about everything) I would be extremely happy to look them up! I do remember that there was a file MISSING from OpenSUSE that I had to copy from another Linux system. I don't think I have that system anymore to copy from since I had a lot of destruction recently due to lightning. --doug
/snip/ Please somebody tell me how to find those posts. I have tried to find them, but I get bogged down in a slew of other emails not from or to me. In the meantime, I decided to see if the scanner really does work: I opened Windows 10, ran a query about setup, downloaded a free apparently universal driver from the Windows store, and had the scanner working in less than five minutes! It doesn't have the capabilities of XScan, but it works. It also saves in .png format, which is something new to me, but since it is Windows, I suppose most computer users can read it. I REALLY dislike Windows, but it made the job seem trivial! --doug
On 24/09/2021 21.05, Douglas McGarrett wrote:
/snip/
Please somebody tell me how to find those posts. I have tried to find them, but I get bogged down in a slew of other emails not from or to me.
It is true that the modern archive is not as good as the old one, but still... here you go, all your posts on _this_ list. <https://lists.opensuse.org/archives/search?mlist=users%40lists.opensuse.org&q=dmcgarrett%40optonline.net> You also wrote to factory@lists.opensuse.org and support@lists.opensuse.org You only have to replace the list token in the URL above: <https://lists.opensuse.org/archives/search?mlist=factory%40lists.opensuse.org&q=dmcgarrett%40optonline.net> <https://lists.opensuse.org/archives/search?mlist=support%40lists.opensuse.org&q=dmcgarrett%40optonline.net> But I got it wrong somehow in the factory case. Surely you can work it out. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2021-09-24 a las 14:12 -0400, Douglas McGarrett escribió:
On 9/23/21 1:34 PM, DennisG wrote:
On 9/23/21 12:57 AM, Douglas McGarrett wrote:
On 9/22/21 6:28 PM, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
snip
Yes, after a lot of trouble and back-and-forth, I got the scanner to work. I need it again, somehow.
I'm not about to try to de/reconstruct all that again. If in 2019 and/or 2020 there was a solution, maybe you should find those posts.
--dg
Yes, I got it working in 2019. As someone already said, I should have put it in my paper logbook, but it got overlooked. If someone can tell me how to find those emails (and not a stack of completely unrelated ones from everybody about everything) I would be extremely happy to look them up! I do remember that there was a file MISSING from OpenSUSE that I had to copy from another Linux system. I don't think I have that system anymore to copy from since I had a lot of destruction recently due to lightning. --doug
snip
Ok Doug, I think I found the solution by scanning through my personal email archive . . . this was all in mid-2019.
There are 3 pieces here. I think the third was the solution.
First, you downloaded imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz from the Epson site and ran the install script, but it failed because there were two components that are proprietary to Epson which would not install (for several reasons, too detailed to recap here).
Second, you found a firmware for the Epson V300 somewhere else which you were able to install but still left the machine not working properly. I don't think that firmware is applicable for your particular model.
Third, I pointed you to the iscan package which is in the Packman repository. It provides the proprietary front-end pieces that opensuse cannot. So just run YaST/Software, search for iscan, install it, and then you should be able to install the scanner with YaST/Scanner. This worked before.
NOTE: I am presuming the Epson is attached via USB, and so it is not networked on the LAN. If it is networked and YaST does not see it after installing the iscan package, you may need to install an additional package. But I'm not going to go there unless the Epson is networked _and_ the iscan package by itself does not solve the problem.
Good luck.
Leap 15.2 & 15.3/KDE Yes, also Leap 15.3 and KDE. Anyway, the Epson is on the lan, not usb. I have installed the iscan package. The system still can't find the scanner, altho it prints to the printer OK. I tried to look thru the past q&a on scanners, but it goes on past 70 items, and covers quite a few years. I also have not been able to find ONLY MY OWN correspondence trail on the question from 2019. (When I was running Tumbleweed, btw.)
I said yesterday that you were told why in this very same thread. Drop the firewall! <https://lists.opensuse.org/archives/list/users@lists.opensuse.org/message/JJTSJVT4XA6CMIBC4ZWKFJ435XFQDHAS/> It is a post from day 15, today is 24, about a week ago. - -- Cheers Carlos E. R. (from openSUSE Leap 15.2 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCYU4mNBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNccbcA/2/xRU+oxfGX2/OzvJan gX4bpL95q56V4zEE0UNF1NStAP4oDRS1LVfLhNB3faLoI7YUKNZ+vkhod81x92iz GsdLmA== =b97g -----END PGP SIGNATURE-----
Le 24/09/2021 à 20:12, Douglas McGarrett a écrit :
Yes, also Leap 15.3 and KDE. Anyway, the Epson is on the lan, not usb. I have installed the iscan package. The system still can't find the
I noticed that some scanner are found by sane et not by the proprietary vuescan software, and others it's the contrary, and this have nothing to do with the printer, usually found so I choose my preferred scan software and plug the printer accordingly :-( here brother printer/scanner and epson scanner... never found why jdd -- http://dodin.org
Le 24/09/2021 à 20:12, Douglas McGarrett a écrit :
Yes, also Leap 15.3 and KDE. Anyway, the Epson is on the lan, not usb. I have installed the iscan package. The system still can't find the
I noticed that some scanner are found by sane et not by the proprietary vuescan software, and others it's the contrary, and this have nothing to do with the printer, usually found
so I choose my preferred scan software and plug the printer accordingly :-(
here brother printer/scanner and epson scanner...
never found why
jdd found some noted changes from exactly one year ago in /etc and /sane.d
On 9/24/21 5:05 PM, jdd@dodin.org wrote: that added a lan address, which was missing (shown as a #example); previously updated /epcowa.conf. Now the system can't find the scanner in just a few seconds, as opposed to about a minute! Tried turning off the firewall--no change in operation. --doug
On 9/23/21 1:34 PM, DennisG wrote:
On 9/23/21 12:57 AM, Douglas McGarrett wrote:
On 9/22/21 6:28 PM, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
snip
Yes, after a lot of trouble and back-and-forth, I got the scanner to work. I need it again, somehow.
I'm not about to try to de/reconstruct all that again. If in 2019 and/or 2020 there was a solution, maybe you should find those posts.
--dg
Yes, I got it working in 2019. As someone already said, I should have put it in my paper logbook, but it got overlooked. If someone can tell me how to find those emails (and not a stack of completely unrelated ones from everybody about everything) I would be extremely happy to look them up! I do remember that there was a file MISSING from OpenSUSE that I had to copy from another Linux system. I don't think I have that system anymore to copy from since I had a lot of destruction recently due to lightning. --doug
snip
Ok Doug, I think I found the solution by scanning through my personal email archive . . . this was all in mid-2019.
There are 3 pieces here. I think the third was the solution.
First, you downloaded imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz from the Epson site and ran the install script, but it failed because there were two components that are proprietary to Epson which would not install (for several reasons, too detailed to recap here).
Second, you found a firmware for the Epson V300 somewhere else which you were able to install but still left the machine not working properly. I don't think that firmware is applicable for your particular model.
Third, I pointed you to the iscan package which is in the Packman repository. It provides the proprietary front-end pieces that opensuse cannot. So just run YaST/Software, search for iscan, install it, and then you should be able to install the scanner with YaST/Scanner. This worked before.
NOTE: I am presuming the Epson is attached via USB, and so it is not networked on the LAN. If it is networked and YaST does not see it after installing the iscan package, you may need to install an additional package. But I'm not going to go there unless the Epson is networked _and_ the iscan package by itself does not solve the problem.
Good luck.
--dg Leap 15.2 & 15.3/KDE
According to the Seiko documentation that comes with the Epson archive that qas downloaded before (#1 above), it is possible for a network scanner to work if a certain driver is used. Not knowing if that applies, the advice is to try iscan alone. This was the problem that blocked you the first time when you used the install script from the Epson download. If you had read the documentation, you would know that the script is intended to be run with parameters, including what type of connection you have. You need to install the packages iscan-plugin and sane-backends; the former which provides the proprietary network component to work with iscan. Good luck. --dg 15.2 & 15.3/KDE
On 9/25/21 12:18 AM, DennisG wrote:
On 9/23/21 1:34 PM, DennisG wrote:
On 9/23/21 12:57 AM, Douglas McGarrett wrote:
On 9/22/21 6:28 PM, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
snip
Yes, after a lot of trouble and back-and-forth, I got the scanner to work. I need it again, somehow.
I'm not about to try to de/reconstruct all that again. If in 2019 and/or 2020 there was a solution, maybe you should find those posts.
--dg
Yes, I got it working in 2019. As someone already said, I should have put it in my paper logbook, but it got overlooked. If someone can tell me how to find those emails (and not a stack of completely unrelated ones from everybody about everything) I would be extremely happy to look them up! I do remember that there was a file MISSING from OpenSUSE that I had to copy from another Linux system. I don't think I have that system anymore to copy from since I had a lot of destruction recently due to lightning. --doug
snip
Ok Doug, I think I found the solution by scanning through my personal email archive . . . this was all in mid-2019.
There are 3 pieces here. I think the third was the solution.
First, you downloaded imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz from the Epson site and ran the install script, but it failed because there were two components that are proprietary to Epson which would not install (for several reasons, too detailed to recap here).
Second, you found a firmware for the Epson V300 somewhere else which you were able to install but still left the machine not working properly. I don't think that firmware is applicable for your particular model.
Third, I pointed you to the iscan package which is in the Packman repository. It provides the proprietary front-end pieces that opensuse cannot. So just run YaST/Software, search for iscan, install it, and then you should be able to install the scanner with YaST/Scanner. This worked before.
NOTE: I am presuming the Epson is attached via USB, and so it is not networked on the LAN. If it is networked and YaST does not see it after installing the iscan package, you may need to install an additional package. But I'm not going to go there unless the Epson is networked _and_ the iscan package by itself does not solve the problem.
Good luck.
--dg Leap 15.2 & 15.3/KDE
According to the Seiko documentation that comes with the Epson archive that qas downloaded before (#1 above), it is possible for a network scanner to work if a certain driver is used. Not knowing if that applies, the advice is to try iscan alone.
This was the problem that blocked you the first time when you used the install script from the Epson download. If you had read the documentation, you would know that the script is intended to be run with parameters, including what type of connection you have.
You need to install the packages iscan-plugin and sane-backends; the former which provides the proprietary network component to work with iscan.
Thank you! Thank you! Thank you! I don't know which one did the trick--I ran zypper on each, and it gave me a lot of crap on the first one, but it finally installed all or part of it. The second one ran smoothly. And you can bet that I have already put this in my notebook! --doug
Good luck.
--dg 15.2 & 15.3/KDE
On 9/25/21 10:36 PM, Douglas McGarrett wrote:
On 9/25/21 12:18 AM, DennisG wrote:
On 9/23/21 1:34 PM, DennisG wrote:
On 9/23/21 12:57 AM, Douglas McGarrett wrote:
On 9/22/21 6:28 PM, DennisG wrote:
On 9/22/21 2:27 PM, Douglas McGarrett wrote:
snip
Yes, after a lot of trouble and back-and-forth, I got the scanner to work. I need it again, somehow.
> > I'm not about to try to de/reconstruct all that again. If in > 2019 and/or 2020 there was a solution, maybe you should find > those posts. > > --dg Yes, I got it working in 2019. As someone already said, I should have put it in my paper logbook, but it got overlooked. If someone can tell me how to find those emails (and not a stack of completely unrelated ones from everybody about everything) I would be extremely happy to look them up! I do remember that there was a file MISSING from OpenSUSE that I had to copy from another Linux system. I don't think I have that system anymore to copy from since I had a lot of destruction recently due to lightning. --doug
snip
Ok Doug, I think I found the solution by scanning through my personal email archive . . . this was all in mid-2019.
There are 3 pieces here. I think the third was the solution.
First, you downloaded imagescan-bundle-opensuse-15.2-3.65.0.x64.rpm.tar.gz from the Epson site and ran the install script, but it failed because there were two components that are proprietary to Epson which would not install (for several reasons, too detailed to recap here).
Second, you found a firmware for the Epson V300 somewhere else which you were able to install but still left the machine not working properly. I don't think that firmware is applicable for your particular model.
Third, I pointed you to the iscan package which is in the Packman repository. It provides the proprietary front-end pieces that opensuse cannot. So just run YaST/Software, search for iscan, install it, and then you should be able to install the scanner with YaST/Scanner. This worked before.
NOTE: I am presuming the Epson is attached via USB, and so it is not networked on the LAN. If it is networked and YaST does not see it after installing the iscan package, you may need to install an additional package. But I'm not going to go there unless the Epson is networked _and_ the iscan package by itself does not solve the problem.
Good luck.
--dg Leap 15.2 & 15.3/KDE
According to the Seiko documentation that comes with the Epson archive that qas downloaded before (#1 above), it is possible for a network scanner to work if a certain driver is used. Not knowing if that applies, the advice is to try iscan alone.
This was the problem that blocked you the first time when you used the install script from the Epson download. If you had read the documentation, you would know that the script is intended to be run with parameters, including what type of connection you have.
You need to install the packages iscan-plugin and sane-backends; the former which provides the proprietary network component to work with iscan.
Thank you! Thank you! Thank you! I don't know which one did the trick--I ran zypper on each, and it gave me a lot of crap on the first one, but it finally installed all or part of it. The second one ran smoothly. And you can bet that I have already put this in my notebook! --doug
Good luck.
--dg 15.2 & 15.3/KDE
Just take note that it is the package iscan-plugin which is critical; it provides the network component. I didn't think you'd need the sane-backends, but it doesn't hurt to have it. Look at the Description and the File List for the package (in YaST/Software) and you will see "network"; that is the proprietary piece you must have. --dg 15.2&15.3/KDE
participants (15)
-
-pj -
Anton Aylward -
Carlos E. R. -
Carlos E.R. -
Damon Register -
Darryl Gregorash -
DennisG -
Douglas McGarrett -
Francesco Teodori -
Freek de Kruijf -
jdd＠dodin.org -
Josef Moellers -
Masaru Nomiya -
Michael Hamilton -
Patrick Shanahan