Re: [opensuse] printing problems--again
On 9/19/20 2:49 PM, Doug McGarrett wrote:
On 9/19/20 3:14 AM, Carlos E. R. wrote:
On 19/09/2020 09.03, Ianseeks wrote:
On Saturday, 19 September 2020 05:31:27 BST Doug McGarrett wrote:
OpenSuse TW. No lectures, please, I'm committed to this. I have been trying to install at least my epson all-mode printer, but things seem to be getting worse, not better. I finally got it to print, but it is printing code, not what it should print. It prints probably the entire driver routine, I don't know what it is! I had to turn off the printer to get it to stop wasting paper. And the error log is about the size of a book.
I'd like to de-install this printer, and start from scratch, but I don't know just where to begin. As I mentioned once before, if I can only have one printer working, it has to be this one, so that I can have color and I can scan. iow, IF I can get this to work, I will then try to install the HP laserjet. (That worked, once, until I "installed" the epson--then nothing worked.
T IA--doug
Have you tried Yast/Hardware/Printers? you can add/delete etc from there.
Unless he had to install separately files from Epson, or proprietary drivers.
I will look more carefully at the Yast system--I did not notice a delete command.
It turns out that SUSE has an Epson driver for this printer. I have downloaded the Epson driver, but I have not used it, since I found that it's in the s/w already. The Epson drivers, whether my download or the original system ones, are in
file:///opt/epson-inkjet-printer-201113w/ppds/Epson file:///etc/cups/epson-inkjet-printer-201113w/ppds/Epson file:///usr/share/cups/model/manufacturer-PPDs/epson
If one of these instances is the original system version, I would not want to delete it, but I don't know which it might be. --doug
OpenSUSE. SUSE is the commercial, enterprise system. You say you have downloaded the Epson driver but "not used it." What about the .rpm discussed in a previous thread? Or the install.sh script? So you are saying that you absolutely unequivocally did not install any printer software for that WP-4530 except via YaST/Printer??? And btw, did you try installing the epson-inkjet-printer-escpr package? Your current and earlier (but different) problem symptoms suggest having installed the wrong driver or you are missing a piece (like maybe this package). It appears (from your difficult to decipher posts) that YaST actually sees the device and you installed a driver for it. If there was no driver installed, nothing would happen. That something spits out at all indicates that the print file is being received by the printer. Printing garbage happens for example when a postscript driver is used when the printer only understands a proprietary printer language - as is the case with Epson printers that use the ESC/P-R language (that's what the above epson package is for). I think in one of your earlier posts you also said something about YaST offering print drivers but none matched your printer, right? So then, what did you install? What did YaST "recommend" (that will be shown in the suggested drivers list), and is this what you installed? You also stated earlier that the YaST driver name did not match the printer. Often manufacturers will use a single driver for a given family of printers. E.g., my F4180 uses the F4000 driver. So sometimes the driver name is not an exact match. It's even possible that it could be a generic driver like ghostscript. The manufacturer provided drivers included with openSUSE will all be found in directories under /usr/share/cups/model/. The epson directory located here that you cite above has driver files but there are also epson drivers in all 3 directories under the OpenPrintingPPDs directory, all of these come with the system too. Under /etc/cups is where YaST/Print puts the .ppd driver file. That file is pulled from a compressed .gz file under /usr/share/cups/model. It's possible there could also be a .ppd file put there via a separate installation method. /opt/your epson directory Opt is typically used by 3rd parties. I would be surprised if YaST put Epson files there, but I suppose it's possible. More likely to have been created by something else you used to install with. As far as deleting the printer: The "Delete" button is right there on the YaST/Printer face page, next to "Add" and "Edit". To reinstall, click on Add and let YaST find the printer. If it isn't shown yet, click on Detect More. Or try the Connection Wizard, it is very good. --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/09/2020 20.08, DennisG wrote:
On 9/19/20 2:49 PM, Doug McGarrett wrote:
On 9/19/20 3:14 AM, Carlos E. R. wrote:
On 19/09/2020 09.03, Ianseeks wrote:
... DM>> file:///opt/epson-inkjet-printer-201113w/ppds/Epson DM>> file:///etc/cups/epson-inkjet-printer-201113w/ppds/Epson DM>> file:///usr/share/cups/model/manufacturer-PPDs/epson
OpenSUSE. SUSE is the commercial, enterprise system.
You say you have downloaded the Epson driver but "not used it." What about the .rpm discussed in a previous thread? Or the install.sh script? So you are saying that you absolutely unequivocally did not install any printer software for that WP-4530 except via YaST/Printer???
YaST does not install on /opt, so he must have done something besides using YaST. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 9/20/20 2:17 PM, Carlos E. R. wrote:
On 20/09/2020 20.08, DennisG wrote:
On 9/19/20 2:49 PM, Doug McGarrett wrote:
On 9/19/20 3:14 AM, Carlos E. R. wrote:
On 19/09/2020 09.03, Ianseeks wrote:
...
DM>> file:///opt/epson-inkjet-printer-201113w/ppds/Epson DM>> file:///etc/cups/epson-inkjet-printer-201113w/ppds/Epson DM>> file:///usr/share/cups/model/manufacturer-PPDs/epson
OpenSUSE. SUSE is the commercial, enterprise system.
You say you have downloaded the Epson driver but "not used it." What about the .rpm discussed in a previous thread? Or the install.sh script? So you are saying that you absolutely unequivocally did not install any printer software for that WP-4530 except via YaST/Printer???
YaST does not install on /opt, so he must have done something besides using YaST. Yes, I did. I am going to try and reverse this, and the /opt point is taken and will be followed up. As I mentioned elsewhere, my initial investigation came up empty on drivers for this Epson, so I downloaded the "official" drivers in rpm form and installed the rpm. I will try to reverse that process (rpm -e filename.rpm) and see what happens. I *will* get this printer working somehow! --doug
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Doug McGarrett <dmcgarrett@optonline.net> [09-20-20 19:08]: [...]
Yes, I did. I am going to try and reverse this, and the /opt point is taken and will be followed up.
better you present what you *actually* have and ask for instruction rather that continue down a slippery slope.
As I mentioned elsewhere, my initial investigation came up empty on drivers for this Epson, so I downloaded the "official" drivers in rpm form and installed the rpm.
what is the definition of "official" as currently that has absolutely no context and does not define your current situation.
I will try to reverse that process (rpm -e filename.rpm) and see what happens.
again, present your environment and *ask* for instruciton.
I *will* get this printer working somehow!
not if you continue as is. -- (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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/09/2020 01.29, Patrick Shanahan wrote:
* Doug McGarrett <> [09-20-20 19:08]: [...]
Yes, I did. I am going to try and reverse this, and the /opt point is taken and will be followed up.
better you present what you *actually* have and ask for instruction rather that continue down a slippery slope.
As I mentioned elsewhere, my initial investigation came up empty on drivers for this Epson, so I downloaded the "official" drivers in rpm form and installed the rpm.
what is the definition of "official" as currently that has absolutely no context and does not define your current situation.
I will try to reverse that process (rpm -e filename.rpm) and see what happens.
again, present your environment and *ask* for instruciton.
I *will* get this printer working somehow!
not if you continue as is.
Agree to all. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 20/09/2020 19:29, Patrick Shanahan wrote:
* Doug McGarrett <dmcgarrett@optonline.net> [09-20-20 19:08]:
I will try to reverse that process (rpm -e filename.rpm) and see what happens.
Eh? You install a PACKAGEFILE, you remove a PACKAGENAME.
again, present your environment and *ask* for instruciton.
I *will* get this printer working somehow!
not if you continue as is.
Agreed. There's lots of small things Doug is mis-saying that indicative of wrong paths, that indicate to me a lack of understanding. Installing into /opt, for example. Sometimes going things with YaST, other times doing it 'manually', bypassing, possibly subverting Yast. Truth to tell, I never use Yast for my printer work, I always use the web interface to CUPS. OK, so after having used the Bell labs SVR4.2 printer system on a corporate network, I don't think much of CUPS, but that's a side issue. I have a Brother and one of it's modes is emulating Epson. So when I run the PPD setup that is one of the options I'm presented with. I never take it. The printer has Postscript capability built in; I got it back when Postscript, not PDF, was the *NIX printer standard. The PDF-to-Postscript translation works OK. Actually I once experimented installing the Epson interface and the PDF-to-Epson driver of CUPS works OK, too. Looking back at my notes on that I can't see why Doug is making a pigs ear out of this. Or perhaps I can: not using CUPS. By not the situation is probably so messed up that firing up CUPS management would either crash or flounder in the confused setup that ha been created. -- "The greatest of all faults is to be conscious of none. Recognizing our limitations & imperfections is the first requisite of progress. Those who believe they have "arrived" believe they have nowhere to go. Some not only have closed their minds to new truth, but they sit on the lid." -- Dale Turner. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/09/2020 14.34, Anton Aylward wrote:
On 20/09/2020 19:29, Patrick Shanahan wrote:
* Doug McGarrett <dmcgarrett@optonline.net> [09-20-20 19:08]:
I will try to reverse that process (rpm -e filename.rpm) and see what happens.
Eh?
You install a PACKAGEFILE, you remove a PACKAGENAME.
You can use: rpm -qf /path/to/filename which will respond with packagename that corresponds to that filename.
again, present your environment and *ask* for instruciton.
I *will* get this printer working somehow!
not if you continue as is.
Agreed. There's lots of small things Doug is mis-saying that indicative of wrong paths, that indicate to me a lack of understanding.
Doug should use a notebook, take notes of each step. Or keep the log from the terminal.
Installing into /opt, for example. Sometimes going things with YaST, other times doing it 'manually', bypassing, possibly subverting Yast.
/opt would be typical of a proprietary package or install program.
Truth to tell, I never use Yast for my printer work, I always use the web interface to CUPS. OK, so after having used the Bell labs SVR4.2 printer system on a corporate network, I don't think much of CUPS, but that's a side issue.
YaST is good to install printers the first time because it can automatically install missing packages. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [09-21-20 13:24]:
On 21/09/2020 14.34, Anton Aylward wrote:
On 20/09/2020 19:29, Patrick Shanahan wrote:
* Doug McGarrett <dmcgarrett@optonline.net> [09-20-20 19:08]:
I will try to reverse that process (rpm -e filename.rpm) and see what happens.
Eh?
You install a PACKAGEFILE, you remove a PACKAGENAME.
You can use:
rpm -qf /path/to/filename
which will respond with
packagename
that corresponds to that filename.
rpm -e `rpm -qf <path><to><filename>`
again, present your environment and *ask* for instruciton.
I *will* get this printer working somehow!
not if you continue as is.
Agreed. There's lots of small things Doug is mis-saying that indicative of wrong paths, that indicate to me a lack of understanding.
Doug should use a notebook, take notes of each step. Or keep the log from the terminal.
or maybe ask someone to admin his computer(s). -- (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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/09/2020 19.26, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [09-21-20 13:24]:
On 21/09/2020 14.34, Anton Aylward wrote:
On 20/09/2020 19:29, Patrick Shanahan wrote:
* Doug McGarrett <dmcgarrett@optonline.net> [09-20-20 19:08]:
I will try to reverse that process (rpm -e filename.rpm) and see what happens.
Eh?
You install a PACKAGEFILE, you remove a PACKAGENAME.
You can use:
rpm -qf /path/to/filename
which will respond with
packagename
that corresponds to that filename.
rpm -e `rpm -qf <path><to><filename>`
I prefer not to do that, in order that Doug sees the name of the package first. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 21/09/2020 13:20, Carlos E. R. wrote:
On 21/09/2020 14.34, Anton Aylward wrote:
On 20/09/2020 19:29, Patrick Shanahan wrote:
* Doug McGarrett <dmcgarrett@optonline.net> [09-20-20 19:08]:
I will try to reverse that process (rpm -e filename.rpm) and see what happens.
Eh?
You install a PACKAGEFILE, you remove a PACKAGENAME.
You can use:
rpm -qf /path/to/filename
which will respond with
packagename
that corresponds to that filename.
In this instance, yes, but you can't always rely on that. It's a convenience to name the package as the basename of the RPM file from which it is installed, but you can't use the full filename when it comes to removing the package.
Doug should use a notebook, take notes of each step. Or keep the log from the terminal.
Indeed.
Installing into /opt, for example. Sometimes going things with YaST, other times doing it 'manually', bypassing, possibly subverting Yast.
/opt would be typical of a proprietary package or install program.
Indeed, but but let's differentiate between the specific and the generic in this discussion.
Truth to tell, I never use Yast for my printer work, I always use the web interface to CUPS. OK, so after having used the Bell labs SVR4.2 printer system on a corporate network, I don't think much of CUPS, but that's a side issue.
YaST is good to install printers the first time because it can automatically install missing packages.
Which Zypper can do and the rpm programme cannot do. Another reason I don't use the rpm program. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/09/2020 19.50, Anton Aylward wrote:
On 21/09/2020 13:20, Carlos E. R. wrote:
On 21/09/2020 14.34, Anton Aylward wrote:
On 20/09/2020 19:29, Patrick Shanahan wrote:
* Doug McGarrett <> [09-20-20 19:08]:
I will try to reverse that process (rpm -e filename.rpm) and see what happens.
Eh?
You install a PACKAGEFILE, you remove a PACKAGENAME.
You can use:
rpm -qf /path/to/filename
which will respond with
packagename
that corresponds to that filename.
In this instance, yes, but you can't always rely on that. It's a convenience to name the package as the basename of the RPM file from which it is installed, but you can't use the full filename when it comes to removing the package.
In the case of the command I printed, it matches always, you can rely on it. "/path/to/filename" is one installed file, and the query answers what package it came in.
Doug should use a notebook, take notes of each step. Or keep the log from the terminal.
Indeed.
Installing into /opt, for example. Sometimes going things with YaST, other times doing it 'manually', bypassing, possibly subverting Yast.
/opt would be typical of a proprietary package or install program.
Indeed, but but let's differentiate between the specific and the generic in this discussion.
What I said is generic...
Truth to tell, I never use Yast for my printer work, I always use the web interface to CUPS. OK, so after having used the Bell labs SVR4.2 printer system on a corporate network, I don't think much of CUPS, but that's a side issue.
YaST is good to install printers the first time because it can automatically install missing packages.
Which Zypper can do and the rpm programme cannot do. Another reason I don't use the rpm program.
No, I'm talking about using the printer configuration module of YaST. You need a coffee ;-) -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 21/09/2020 14:08, Carlos E. R. wrote:
In the case of the command I printed, it matches always, you can rely on it. "/path/to/filename" is one installed file, and the query answers what package it came in.
Your point is, and my point is, that it is the entry in the RPM database that matters, not the name of the file in the file system. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/20/20 7:06 PM, Doug McGarrett wrote:
On 9/20/20 2:17 PM, Carlos E. R. wrote:
On 20/09/2020 20.08, DennisG wrote:
On 9/19/20 2:49 PM, Doug McGarrett wrote:
On 9/19/20 3:14 AM, Carlos E. R. wrote:
On 19/09/2020 09.03, Ianseeks wrote:
...
DM>> file:///opt/epson-inkjet-printer-201113w/ppds/Epson DM>> file:///etc/cups/epson-inkjet-printer-201113w/ppds/Epson DM>> file:///usr/share/cups/model/manufacturer-PPDs/epson
OpenSUSE. SUSE is the commercial, enterprise system.
You say you have downloaded the Epson driver but "not used it." What about the .rpm discussed in a previous thread? Or the install.sh script? So you are saying that you absolutely unequivocally did not install any printer software for that WP-4530 except via YaST/Printer???
YaST does not install on /opt, so he must have done something besides using YaST. Yes, I did. I am going to try and reverse this, and the /opt point is taken and will be followed up. As I mentioned elsewhere, my initial investigation came up empty on drivers for this Epson, so I downloaded the "official" drivers in rpm form and installed the rpm. I will try to reverse that process (rpm -e filename.rpm) and see what happens. I *will* get this printer working somehow! --doug
I ran the rpm -e command for the file I had downloaded, and the system told me "not installed" --I'm not sure I believe that. I ran a KFind app on Epson, and got quite a list. I will attempt to paste the result at http://paste.opensuse.org/home/doug.epson list from KFind if that didn't work, then it's because I've never done that before, and I've obviously missed something. --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/20/20 8:24 PM, Doug McGarrett wrote:
On 9/20/20 7:06 PM, Doug McGarrett wrote:
long snip
YaST does not install on /opt, so he must have done something besides using YaST. Yes, I did. I am going to try and reverse this, and the /opt point is taken and will be followed up. As I mentioned elsewhere, my initial investigation came up empty on drivers for this Epson, so I downloaded the "official" drivers in rpm form and installed the rpm. I will try to reverse that process (rpm -e filename.rpm) and see what happens. I *will* get this printer working somehow! --doug
I ran the rpm -e command for the file I had downloaded, and the system told me "not installed" --I'm not sure I believe that.
I ran a KFind app on Epson, and got quite a list. I will attempt to paste the result at http://paste.opensuse.org/home/doug.epson list from KFind
if that didn't work, then it's because I've never done that before, and I've obviously missed something. --doug
Don't bother with the list. As I wrote prev, all the supplied Epson drivers are found under /usr/share/cups/model/* We now know that the epson file under /opt was installed by you. It is also highly unlikely that it is being seen by YaST or cups, whatever it is. All that matters at the moment is what .ppd is in /etc/cups/epson-inkjet-printer-201113w/ppds/Epson. That is what YaST installed and is what cups is using for your printer. You need now to determine if that is the right driver. / /--dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 20/09/2020 20:24, Doug McGarrett wrote:
I ran the rpm -e command for the file I had downloaded, and the system told me "not installed" --I'm not sure I believe that.
Yes. You install a file, you remove a package. One of the reasons I use Zypper rather than rpm is to avoid this sort of nonsense. Zypper makes sure all the dependencies are matched up and notifies you about anything else that needs to be added or removed to maintain a stable system. A file might contain more than one package, though I can't think of an actual example off hand. If you refer to the file as you have done which package to remove? Also, the name of the file might have nothing to do with the name of the package. Suppose you have a file 'package.rpm' that contains a package named 'Package1'. Now rename the file to 'Razzamatazz.oolong'. If you run rpm -i --file Razzamatazz.oolong it will install Package1, but rpm -e --file Razzamatazz.oolong WILL NOT uninstall Package1 Yes, it's nice to have RPM file names based on the package they contain, but that's an artifice of people who know more about packaging and expect users to make use of the appropriate level of tools to match their knowledge. In many ways, using 'rpm' is like using assembler when you have high level languages like Python that check types and syntax and grammar. One line of the HLL/interpreter translates to many lines of ASM. Or in this case, many lines of which the rpm command (or its library equivalent) is just one. If we follow the analogy, Zypper is like using C or C++. It's still a HLL but you have a pretty good idea of how it 'translates' to lower level. By the time we get to Yast we're layering on top of and application written in a OO-HLL, Ruby. I've done enough Ruby-on-Rails to be familiar with Ruby, but the OO model that the Yast developers have implemented is unintelligible to me. More layering, more abstraction. Perhaps there is a flavour of 'you're not supposed to know' in all this. So I settle for using Zypper. -- "The greatest of all faults is to be conscious of none. Recognizing our limitations & imperfections is the first requisite of progress. Those who believe they have "arrived" believe they have nowhere to go. Some not only have closed their minds to new truth, but they sit on the lid." -- Dale Turner. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 21 Sep 2020 09:08:50 -0400 Anton Aylward <opensuse@antonaylward.com> wrote:
On 20/09/2020 20:24, Doug McGarrett wrote:
I ran the rpm -e command for the file I had downloaded, and the system told me "not installed" --I'm not sure I believe that.
Yes. You install a file, you remove a package.
One of the reasons I use Zypper rather than rpm is to avoid this sort of nonsense. Zypper makes sure all the dependencies are matched up and notifies you about anything else that needs to be added or removed to maintain a stable system.
A file might contain more than one package, though I can't think of an actual example off hand. If you refer to the file as you have done which package to remove?
Eh? I understand that a package might contain more than one file. But files don't contain packages at all; they are contained by packages. I think it would bevanishingly rare for the same file to be part of more than one package - in that circumstance I'd expect the packages to be split so the common file is in a third package. So what do you actually mean? Ah, maybe you're talking about RPM files? But even then, they only have a single package name.
Also, the name of the file might have nothing to do with the name of the package. Suppose you have a file 'package.rpm' that contains a package named 'Package1'. Now rename the file to 'Razzamatazz.oolong'.
If you run rpm -i --file Razzamatazz.oolong it will install Package1, but rpm -e --file Razzamatazz.oolong WILL NOT uninstall Package1
Yes, it's nice to have RPM file names based on the package they contain, but that's an artifice of people who know more about packaging and expect users to make use of the appropriate level of tools to match their knowledge.
In many ways, using 'rpm' is like using assembler when you have high level languages like Python that check types and syntax and grammar. One line of the HLL/interpreter translates to many lines of ASM. Or in this case, many lines of which the rpm command (or its library equivalent) is just one. If we follow the analogy, Zypper is like using C or C++. It's still a HLL but you have a pretty good idea of how it 'translates' to lower level.
By the time we get to Yast we're layering on top of and application written in a OO-HLL, Ruby. I've done enough Ruby-on-Rails to be familiar with Ruby, but the OO model that the Yast developers have implemented is unintelligible to me. More layering, more abstraction. Perhaps there is a flavour of 'you're not supposed to know' in all this. So I settle for using Zypper.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/09/2020 10:27, Dave Howorth wrote:
On Mon, 21 Sep 2020 09:08:50 -0400 Anton Aylward <opensuse@antonaylward.com> wrote:
On 20/09/2020 20:24, Doug McGarrett wrote:
I ran the rpm -e command for the file I had downloaded, and the system told me "not installed" --I'm not sure I believe that.
Yes. You install a file, you remove a package.
One of the reasons I use Zypper rather than rpm is to avoid this sort of nonsense. Zypper makes sure all the dependencies are matched up and notifies you about anything else that needs to be added or removed to maintain a stable system.
A file might contain more than one package, though I can't think of an actual example off hand. If you refer to the file as you have done which package to remove?
Eh? I understand that a package might contain more than one file. But files don't contain packages at all; they are contained by packages. I think it would bevanishingly rare for the same file to be part of more than one package - in that circumstance I'd expect the packages to be split so the common file is in a third package. So what do you actually mean?
You suggester "rpm -e filename.rpm" What is "filename.rpm" if not a file? Files contain packages contain files... contain ... what? What are TAR files, ZIP files and CPIO files if not structures ways of containing files that also contain the necessary metadata for unpacking and/or relocating them? What is a file system if not a way of packaging files? An RPM file might contain more than one package as far as installation goes. I look at the specs and can't see why not. Yes each package is the 'packaging' and the metadata' and might result in separate entities in the RPM database. On the face of it, yes it seems ridiculous, but it appears to be to be within the possibility of the specification. So you can't use the filename, certain not with the ".rpm" extension, to remove a package. Maybe rpm will accept the basename. Maybe. But how much of the basename? You might have installed, for example, rpm -i -f yast2-printer-4.1.1-lp151.1.1.x86_64.rpm but are you going to remove rpm -e -f yast2-printer-4.1.1-lp151.1.1.x86_64.rpm or rpm -e -f yast2-printer The first won't work, the second will. The file "yast2-printer-4.1.1-lp151.1.1.x86_64.rpm" contains the package "yast2-printer" at revision level 4.1.1 for an x86 64 bit installation of leap 15.1 The file NAME encodes the metadata so you can have multiple RPM files in a disk directory (aka folder) as some people do to organise such things. There is no mandate that you have to name your own files that way, and I suppose some vendors aren't going to follow that convention. Renaming the file 'Razzamatazz.oolong' doesn't alter what's inside it, it's the same package, but using the basename 'Razzamatazz' won't get you anywhere. Don't assume as universal things that happen to be incidental. You install FROM a file to make an entry in the database. (At that point you can safely delete the file.) You uninstall with reference to what's in the database, which is the package name.
Ah, maybe you're talking about RPM files? But even then, they only have a single package name.
Maybe. It is not a requirement, certainly not one all vendors follow. As I say...
Also, the name of the file might have nothing to do with the name of the package. Suppose you have a file 'package.rpm' that contains a package named 'Package1'. Now rename the file to 'Razzamatazz.oolong'.
If you run rpm -i --file Razzamatazz.oolong it will install Package1,
Yes, it's nice to have RPM file names based on the package they contain, but that's an artifice of people who know more about packaging and expect users to make use of the appropriate level of tools to match their knowledge.
It is also, as I mention, convenient for archiving purposes. You can store yast2-printer-4.1.1-lp151.1.1.x86_64.rpm yast2-printer-4.1.1-lp151.1.1.src.rpm yast2-printer-4.1.0-lp151.1.1.x86_64.rpm yast2-printer-4.1.0-lp151.1.1.src.rpm yast2-printer-3.8.2-lp150.1.1.x86_64.rpm yast2-printer-3.8.2-lp150.1.1.src.rpm All in the same directory. And more for other architectures and releases. But all the x86_64 packages will install a version of the package yast2-printer. that's the way upgrades work. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 21 Sep 2020 13:43:36 -0400 Anton Aylward <opensuse@antonaylward.com> wrote:
On 21/09/2020 10:27, Dave Howorth wrote:
On Mon, 21 Sep 2020 09:08:50 -0400 Anton Aylward <opensuse@antonaylward.com> wrote:
On 20/09/2020 20:24, Doug McGarrett wrote:
I ran the rpm -e command for the file I had downloaded, and the system told me "not installed" --I'm not sure I believe that.
Yes. You install a file, you remove a package.
One of the reasons I use Zypper rather than rpm is to avoid this sort of nonsense. Zypper makes sure all the dependencies are matched up and notifies you about anything else that needs to be added or removed to maintain a stable system.
A file might contain more than one package, though I can't think of an actual example off hand. If you refer to the file as you have done which package to remove?
Eh? I understand that a package might contain more than one file. But files don't contain packages at all; they are contained by packages. I think it would bevanishingly rare for the same file to be part of more than one package - in that circumstance I'd expect the packages to be split so the common file is in a third package. So what do you actually mean?
You suggester "rpm -e filename.rpm"
No I didn't.
What is "filename.rpm" if not a file?
Files contain packages contain files... contain ... what?
What are TAR files, ZIP files and CPIO files if not structures ways of containing files that also contain the necessary metadata for unpacking and/or relocating them? What is a file system if not a way of packaging files?
An RPM file might contain more than one package as far as installation goes. I look at the specs and can't see why not. Yes each package is the 'packaging' and the metadata' and might result in separate entities in the RPM database. On the face of it, yes it seems ridiculous, but it appears to be to be within the possibility of the specification.
So you can't use the filename, certain not with the ".rpm" extension, to remove a package. Maybe rpm will accept the basename. Maybe. But how much of the basename?
You might have installed, for example, rpm -i -f yast2-printer-4.1.1-lp151.1.1.x86_64.rpm but are you going to remove rpm -e -f yast2-printer-4.1.1-lp151.1.1.x86_64.rpm or rpm -e -f yast2-printer
The first won't work, the second will.
The file "yast2-printer-4.1.1-lp151.1.1.x86_64.rpm" contains the package "yast2-printer" at revision level 4.1.1 for an x86 64 bit installation of leap 15.1 The file NAME encodes the metadata so you can have multiple RPM files in a disk directory (aka folder) as some people do to organise such things.
There is no mandate that you have to name your own files that way, and I suppose some vendors aren't going to follow that convention.
Renaming the file 'Razzamatazz.oolong' doesn't alter what's inside it, it's the same package, but using the basename 'Razzamatazz' won't get you anywhere. Don't assume as universal things that happen to be incidental.
You install FROM a file to make an entry in the database. (At that point you can safely delete the file.) You uninstall with reference to what's in the database, which is the package name.
Isn't everything you wrote above this point irrelevant? I haven't read it anyway.
Ah, maybe you're talking about RPM files? But even then, they only have a single package name.
Maybe. It is not a requirement, certainly not one all vendors follow.
An example would be nice to back up this assertion. I'm just looking at https://rpm-packaging-guide.github.io and I don't see the possibility there.
As I say...
Also, the name of the file might have nothing to do with the name of the package. Suppose you have a file 'package.rpm' that contains a package named 'Package1'. Now rename the file to 'Razzamatazz.oolong'.
I agree with you but we are not talking about that.
If you run rpm -i --file Razzamatazz.oolong it will install Package1,
Yes, it's nice to have RPM file names based on the package they contain, but that's an artifice of people who know more about packaging and expect users to make use of the appropriate level of tools to match their knowledge.
It is also, as I mention, convenient for archiving purposes. You can store yast2-printer-4.1.1-lp151.1.1.x86_64.rpm yast2-printer-4.1.1-lp151.1.1.src.rpm yast2-printer-4.1.0-lp151.1.1.x86_64.rpm yast2-printer-4.1.0-lp151.1.1.src.rpm yast2-printer-3.8.2-lp150.1.1.x86_64.rpm yast2-printer-3.8.2-lp150.1.1.src.rpm
All in the same directory. And more for other architectures and releases.
But all the x86_64 packages will install a version of the package yast2-printer. that's the way upgrades work.
And again all of this is irrelevant. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/20/20 2:08 PM, DennisG wrote:
On 9/19/20 2:49 PM, Doug McGarrett wrote:
On 9/19/20 3:14 AM, Carlos E. R. wrote:
On 19/09/2020 09.03, Ianseeks wrote:
On Saturday, 19 September 2020 05:31:27 BST Doug McGarrett wrote:
OpenSuse TW. No lectures, please, I'm committed to this. I have been trying to install at least my epson all-mode printer, but things seem to be getting worse, not better. I finally got it to print, but it is printing code, not what it should print. It prints probably the entire driver routine, I don't know what it is! I had to turn off the printer to get it to stop wasting paper. And the error log is about the size of a book.
I'd like to de-install this printer, and start from scratch, but I don't know just where to begin. As I mentioned once before, if I can only have one printer working, it has to be this one, so that I can have color and I can scan. iow, IF I can get this to work, I will then try to install the HP laserjet. (That worked, once, until I "installed" the epson--then nothing worked.
T IA--doug
Have you tried Yast/Hardware/Printers? you can add/delete etc from there.
Unless he had to install separately files from Epson, or proprietary drivers.
I will look more carefully at the Yast system--I did not notice a delete command.
It turns out that SUSE has an Epson driver for this printer. I have downloaded the Epson driver, but I have not used it, since I found that it's in the s/w already. The Epson drivers, whether my download or the original system ones, are in
file:///opt/epson-inkjet-printer-201113w/ppds/Epson file:///etc/cups/epson-inkjet-printer-201113w/ppds/Epson file:///usr/share/cups/model/manufacturer-PPDs/epson
If one of these instances is the original system version, I would not want to delete it, but I don't know which it might be. --doug
I appreciate the information you folks have been providing. I am trying now to clean up the filesystem of downloaded epson files. It sort of looks like the third instance listed above is the original OpenSuse directory, but there are only unfamiliar filenames in it. A typical example: epin4000.ppd.gz. Is this an original OS file? Someone out there please look and see if this is what you have in your TW system? If it is, I will delete any epson files in the first two: /opt... and /etc/cups... I apologize for making this mess. I was used to a less automated OS, and am just getting used to yast. (In the meantime, I will utilize the remove feature of yast and delete the epson printer that is not working, and await the results of this message before continuing.) --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/09/2020 20.50, Doug McGarrett wrote: ...
I appreciate the information you folks have been providing. I am trying now to clean up the filesystem of downloaded epson files. It sort of looks like the third instance listed above is the original OpenSuse directory, but there are only unfamiliar filenames in it. A typical example: epin4000.ppd.gz. Is this an original OS file? Someone out there please look and see if this is what you have in your TW system? If it is, I will delete any epson files in the first two: /opt... and /etc/cups...
You are going the wrong way. You don't have to delete the files you see, instead you have to uninstall the rpm package they came in, whose name you do not see.
I apologize for making this mess. I was used to a less automated OS, and am just getting used to yast. (In the meantime, I will utilize the remove feature of yast and delete the epson printer that is not working, and await the results of this message before continuing.) --doug
-- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 9/21/20 4:25 PM, Carlos E. R. wrote:
On 21/09/2020 20.50, Doug McGarrett wrote:
...
I appreciate the information you folks have been providing. I am trying now to clean up the filesystem of downloaded epson files. It sort of looks like the third instance listed above is the original OpenSuse directory, but there are only unfamiliar filenames in it. A typical example: epin4000.ppd.gz. Is this an original OS file? Someone out there please look and see if this is what you have in your TW system? If it is, I will delete any epson files in the first two: /opt... and /etc/cups...
You are going the wrong way. You don't have to delete the files you see, instead you have to uninstall the rpm package they came in, whose name you do not see.
As I said in a previous note, I did "rpm -e" to the rpms listed in my download file, and got the answer that there was nothing to be done. --doug
I apologize for making this mess. I was used to a less automated OS, and am just getting used to yast. (In the meantime, I will utilize the remove feature of yast and delete the epson printer that is not working, and await the results of this message before continuing.) --doug
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Doug McGarrett <dmcgarrett@optonline.net> [09-21-20 19:21]:
On 9/21/20 4:25 PM, Carlos E. R. wrote:
On 21/09/2020 20.50, Doug McGarrett wrote:
...
I appreciate the information you folks have been providing. I am trying now to clean up the filesystem of downloaded epson files. It sort of looks like the third instance listed above is the original OpenSuse directory, but there are only unfamiliar filenames in it. A typical example: epin4000.ppd.gz. Is this an original OS file? Someone out there please look and see if this is what you have in your TW system? If it is, I will delete any epson files in the first two: /opt... and /etc/cups...
You are going the wrong way. You don't have to delete the files you see, instead you have to uninstall the rpm package they came in, whose name you do not see.
As I said in a previous note, I did "rpm -e" to the rpms listed in my download file, and got the answer that there was nothing to be done.
which was the answer you should have received as you didn't use the correct procedure. you must uninstall the rpm package, not one of the files contained withing the package. you are borking your system. and you just continue to do so. -- (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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/21/20 7:34 PM, Patrick Shanahan wrote:
* Doug McGarrett <dmcgarrett@optonline.net> [09-21-20 19:21]:
On 9/21/20 4:25 PM, Carlos E. R. wrote:
On 21/09/2020 20.50, Doug McGarrett wrote:
...
/snip/ You are going the wrong way. You don't have to delete the files you see, instead you have to uninstall the rpm package they came in, whose name you do not see.
As I said in a previous note, I did "rpm -e" to the rpms listed in my download file, and got the answer that there was nothing to be done.
which was the answer you should have received as you didn't use the correct procedure. you must uninstall the rpm package, not one of the files contained withing the package. you are borking your system. and you just continue to do so. Alright, how?
--dm
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Doug McGarrett <dmcgarrett@optonline.net> [09-21-20 21:52]:
On 9/21/20 7:34 PM, Patrick Shanahan wrote:
* Doug McGarrett <dmcgarrett@optonline.net> [09-21-20 19:21]:
On 9/21/20 4:25 PM, Carlos E. R. wrote:
On 21/09/2020 20.50, Doug McGarrett wrote:
...
/snip/ You are going the wrong way. You don't have to delete the files you see, instead you have to uninstall the rpm package they came in, whose name you do not see.
As I said in a previous note, I did "rpm -e" to the rpms listed in my download file, and got the answer that there was nothing to be done.
which was the answer you should have received as you didn't use the correct procedure. you must uninstall the rpm package, not one of the files contained withing the package. you are borking your system. and you just continue to do so. Alright, how?
su - cd / rm -rf this will erase EVERYTHING in your system insert your original openSUSE install device in subject computer follow the installation instructions and you will have a new system that most of us can relate to and then advise you. warning: this will erase everything and you will have to reinstall your desired distro. -- (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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/09/2020 21:50, Doug McGarrett wrote:
which was the answer you should have received as you didn't use the correct procedure. you must uninstall the rpm package, not one of the files contained withing the package. you are borking your system. and you just continue to do so.
Alright, how?
Carlos has told you how to identify the PACKAGE NAME given one of the files that were installed. if you read the man page on "rpm" you will see that while it uses PACKAGE FILE for installation it uses PACKAGE NAME for erasure/removal. NAME not FILE The NAMED package is what was in the FILE. That's _package_! Not files, but _package_. For ${DEITY}'s sake, why can't people who aspire to be programmers or administrators of computer system read "Alice in Wonderland" and Alfred Korzybski. "The map is not the territory". The name of the thing is not the thing. The name of a RPM file is not the content, which is a CPIO file and some metadata anyway, and it's only when processed (aka interpreted) do you get the package. The container of the thing, not matter how it is named, is not the thing either. The file is not the process. And the file _name_ certainly isn't. A reference to name of the thing isn't the thing either! the problem is that we use names, labels, references indiscriminately. And it confuses the heck out of neophytes. As this thread is demonstrating. -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/09/2020 19:34, Patrick Shanahan wrote:
* Doug McGarrett <dmcgarrett@optonline.net> [09-21-20 19:21]:
As I said in a previous note, I did "rpm -e" to the rpms listed in my download file, and got the answer that there was nothing to be done.
which was the answer you should have received as you didn't use the correct procedure. you must uninstall the rpm package, not one of the files contained withing the package. you are borking your system. and you just continue to do so.
I've flogged this horse and he doesn't see it. -- You install from a ".rpm" file -- You do NOT uninstall from that file or any other file -- You uninstall a named (and possibly version of) a _package_. Carlog has told you how to determine the name of the package based on one of the files that were created when that package was installed. Those files have nothing to do with the names of files that you downloaded A ".rpm" file contains a CPIO that has archived the files that makes up the package as well as sufficient metadata to see it installed correctly, such /dependencies and requirements.
As I said in a previous note, I did "rpm -e" to the rpms listed in my download file
Recap please. "Download file"? Where was this from? "listed in"? -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/21/20 7:14 PM, Doug McGarrett wrote:
On 9/21/20 4:25 PM, Carlos E. R. wrote:
On 21/09/2020 20.50, Doug McGarrett wrote:
...
I appreciate the information you folks have been providing. I am trying now to clean up the filesystem of downloaded epson files. It sort of looks like the third instance listed above is the original OpenSuse directory, but there are only unfamiliar filenames in it. A typical example: epin4000.ppd.gz. Is this an original OS file? Someone out there please look and see if this is what you have in your TW system? If it is, I will delete any epson files in the first two: /opt... and /etc/cups...
You are going the wrong way. You don't have to delete the files you see, instead you have to uninstall the rpm package they came in, whose name you do not see.
As I said in a previous note, I did "rpm -e" to the rpms listed in my download file, and got the answer that there was nothing to be done.
OK, I *think* I cleaned up the mess, but ? I'm trying to get yast to install my printers, but I guess I don't understand the language. Failed to set BrowsePoll value(s) 'HP-m201 epson-WP4530' in /etc/cups/cupsd.conf I have no idea what this means. Maybe I overlooked something. Trying again for the umteenth time. . . . (I tried automatic configuration, and it can't find my printers.) Print via network (I do NOT wish to share printers--the other computers on the network have their own drivers and they WORK.) (checked) Accept Printer Announcements frm CUPS Servers accept from all hosts in the local network (selected) Additional IP Addresses or Network/Netmask (separated by space) 192.168.1.26 192.168.1.29 [ first is Epson, second is HP] Qt this point, I checked "Request Printer Information from CUPS servers" and the previous input changed Polled CUPS server names or IP addresses (separated by space) Connection Wizard (selected) Connection Type (At this point, I get multiple options, which I don't know what to do with! Help!) Access Network Printer or Printserver Box via [possibilities:] TCP Port (AppSockert/JetDirect Line Printer Daemon (LPD) Protocol Internet Printing Protocol )IPP) Print via Print Server Machine (what's that?) (As a reminder to the reader, I have the Epson WP4530 all-in-one and the HP LaserJet m201, both on the LAN. They both print perfectly from other Linux computers, set up about 2015. I was fortunate to have someone to write the instructions for both printers, nothing automatic. [PCLOS].) I have been thru all of the multiple options except the last—Connection type—and generally get part way thru and the screen clears back to a blank beginning. If I had any hair left I'd tear it out! --doug
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/09/2020 20:36, Doug McGarrett wrote:
(As a reminder to the reader, I have the Epson WP4530 all-in-one and the HP LaserJet m201, both on the LAN. They both print
perfectly from other Linux computers, set up about 2015. I was fortunate to have someone to write the instructions for both
printers, nothing automatic. [PCLOS].)
More than one other Linux computer? Well there's a solution. Stop trying to print from this computer, use the print subsystem to redirect to one of the computers that does address the devices successfully. As someone once said, most problems in computing can be solved by adding a level of indirection. -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/09/2020 20:36, Doug McGarrett wrote:
(As a reminder to the reader, I have the Epson WP4530 all-in-one and the HP LaserJet m201, both on the LAN. They both print
perfectly from other Linux computers, set up about 2015. I was fortunate to have someone to write the instructions for both
printers, nothing automatic. [PCLOS].)
More than one other Linux computer? Well there's a solution. Stop trying to print from this computer, use the print subsystem to redirect to one of the computers that does address the devices successfully. You would save me a lot of trouble if you would tell me how to do that. I was just about to take the advice of a number of correspondents and wipe the whole system and restart. I would really not like to have to do so, as it took over a week just to get the things I want into the machine. It's a crutch, of course, and maybe I should just bite the bullet and do so. The crutch relies on the other computer to be on line, and
On 9/22/20 7:10 AM, Anton Aylward wrote: the one that is more nearly up-to-date is a laptop. The desktop is older and clumsier. Neither can be updated; the OS is obsolete. --doug
As someone once said, most problems in computing can be solved by adding a level of indirection.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/09/2020 13:36, Doug McGarrett wrote:
The crutch relies on the other computer to be on line, and the one that is more nearly up-to-date is a laptop. The desktop is older and clumsier. Neither can be updated; the OS is obsolete.
Please do not cc me if you are posting to the list! Doug, I think you have problems that run a lot deeper than juggling with a printer driver. -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 9/19/20 2:49 PM, Doug McGarrett wrote:
long snip
And btw, did you try installing the epson-inkjet-printer-escpr package? Your current and earlier (but different) problem symptoms suggest having installed the wrong driver or you are missing a piece (like maybe this package) . . . Printing garbage happens for example when a postscript driver is used when the printer only understands a proprietary printer language - as is the case with Epson printers that use the ESC/P-R language (that's what the above epson package is for).
Jeez, what a bloody mess this is . . . Doug, I apparently missed that you have a 2-month-long thread about this machine over on the Forums. You did mention that here, right? The solution is on page 3 of 9. You had better digest all this before taking further action or you will make the mess worse. I'm skipping over the install.sh script you ran from iscan-bundle-2.30.4.x64.rpm.tar.gz downloaded from Epson. That script installed 3 rpms, but none for the print function - the scanner only. Btw, all of that is already available from the Packman repo, same iscan version. It would be better to use the Packman package. But if you install it from Packman over the 3 rpms you ran previously, there could be problems. You could try to back out the three rpms that came along with the install.sh script. For now if the scanner is working, leave it all alone. I'm not spending any more time on this. What you installed for the print function from Epson was the epson-inkjet-printer-201113w-1.0.2-1lsb3.2.x86_64.rpm. That is the original "full-featured" driver from 2012. It is proprietary, which is why you don't find it in openSUSE. This rpm is what put the epson files you have in /opt and installed something to /etc/cups/epson-inkjet-printer-201113w/ppds/Epson that you haven't posted. The filename(s) there is probably something with 201113w in it. In any event, this directory and everything in it is wrong./ / You posted "The Epson drivers, whether my download or the original system ones, are in ... /usr/share/cups/model/manufacturer-PPDs/epson." If your 201113w downloaded rpm above is there or anything from it, get rid of it (not likely, unless you put something there manually). The openSUSE supplied package for your machine is the epson-inkjet-printer-escr package. Install it with YaST/Software and it will create the /usr/share/cups/model/manufacturer-PPDs/epson-inkjet-printer-escpr/directory which will include Epson-WP-4530_Series-epson-escpr-en.ppd.gz which is your driver installation file and is what YaST/Printer will see once you install this package. This will enable you to properly install the printer. Delete the epson directory under /opt. There is only documentation there, for the wrong driver no less. Get rid of it. What is inside /etc/cups/epson-inkjet-printer-201113w/ppds/Epson remains a problem, because YaST may see the driver there. That quite possibly is what is borking your print output. The proper way to delete it is to use rpm (zypper didn't like the file) to uninstall epson-inkjet-printer-201113w-1.0.2-1lsb3.2.x86_64.rpm that you downloaded from Epson. If you don't still have that rpm, get it again from Epson and do this. It is not a good idea to just manually delete the 201113w directory. Actually, it is quite possible that once you've installed the epson-inkjet-printer-escr package, YaST/Printer will see either only the new escpr driver, or it along with the wrong 20113w driver. If you just install the escpr driver then the 201113w directory & files under /etc/cups/ will just be ignored. I gotta say, this took waaaaay more time that it should have. And why didn't you install this package when recommended last month? If having the installed the escpr driver solves the printer problem, do no more and give it (and us) a rest. --dg // -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Anton Aylward -
Carlos E. R. -
Dave Howorth -
DennisG -
Doug McGarrett -
Patrick Shanahan