On 10/9/20 7:49 PM, Doug McGarrett wrote:
snip
I can't find his reply at the moment, but shortly after you posted about the scanner Carlos asked if you had had a recent update. I don't recall you following up on that. In any event, of course the first logical suspect when anything like this happens, is to look into the recent update(s). Tumbleweed is IMHO of extraordinary value as it provides rigorous testing for what will become the next point release. Using a rolling release usually requires additional attention, and certainly the ability to navigate unexpected surprises anywhere in the system.
--dg I don't remember the recent update question, which is not to say that there wasn't one. Now I am thoroughly aware of the possibility of an update breaking something. I wonder if a future update will fix what broke, or what the user can do to help locate the particular problem. All I know is that the scanner which worked perfectly one day is no longer visible to the system or yast. How do the developers know what broke, and where to look for a fix--should I be reporting the scanner problem to someplace other than this forum? (As it happens, in my ignorance, I ran the update on the Leap machine also, and it doesn't recognize the scanner either! But I had not yet installed it. Only when I went to do so, did I find that yast cannot find it. I suppose one is not supposed to run update on Leap.--I will learn, I hope, before I die! --doug
You posted the scanner problem on Oct 4. In less than a day Carlos replied with the question: "Any updates to the machine?" Given your description and that there has not been other noise about printers/scanners disappearing, the most likely conclusions are pilot error or update problem or both. With any OS but especially one that is a rolling release, having a backup/recovery strategy is an absolute requirement. Sometimes it is easy to find the culprit in an update, such as with your TBird issue. Sometimes it can be very difficult to impossible, which was probably true for your scanner and is all the more so now. If your Epson's printer function still works, that points to the scanner software as a suspect. IIRC while the print driver was in the Epson driver package from openSUSE, the scanner software you downloaded from Epson and installed it. I took a look at that installation package. It is not trivial, and possibly of importance, there is a proprietary module included (hence not included in the distribution). Proprietary code is vulnerable to breakage, e.g., from a kernel update. In fact, with this problem, a first step would be to boot a previous kernel to see if that corrected the problem (I keep 3 kernel versions). A second thing to try would be to reinstall the scanner software. Third, roll the system back using your backups (but be careful to preserve any new data that you could lose in the process, like email). Beyond that, you're on a wing and a prayer. And btw, please do not include our personal email addresses in your replies to the list. --dg -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org