Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
gscan2pdf worked well when initially installing it. However, today, as soon as I launch it, I get these error messages. Note: It is connected to power & usb cords properly...
After doing a bit of searching and looking at both your image and mine I saw the same thing.
`Cache device list` was checked.
I found that since I had recently changed ISP and my local network subnet had changed, the cached address for the network scanner was different than expected so it refused to connect. Xsane also would not connect for the same reason. I turned off the `cache device list` as well so gscan2pdf now always scans for devices instead of only using the cached device.
I had to do 2 things.
1. I had to reconfigure the printer since the config still showed the old address, even though dhcp had been managed and had assigned the new address.
2. I had to manually edit the ~/.config/gscan2pdfrc file and change the saved IP address there to match the new printer IP. That file contains the cached data for gscan2pdf.
Once I fixed those 2 hanging changes that I had overlooked then the printer would now work again and the scanner worked again for both Xsane and gscan2pdf.
Last edited by computersavvy; 12-16-2022 at 12:34 PM.
After doing a bit of searching and looking at both your image and mine I saw the same thing.
`Cache device list` was checked.
I found that since I had recently changed ISP and my local network subnet had changed, the cached address for the network scanner was different than expected so it refused to connect. Xsane also would not connect for the same reason. I turned off the `cache device list` as well so gscan2pdf now always scans for devices instead of only using the cached device.
I had to do 2 things.
1. I had to reconfigure the printer since the config still showed the old address, even though dhcp had been managed and had assigned the new address.
2. I had to manually edit the ~/.config/gscan2pdfrc file and change the saved IP address there to match the new printer IP. That file contains the cached data for gscan2pdf.
Once I fixed those 2 hanging changes that I had overlooked then the printer would now work again and the scanner worked again for both Xsane and gscan2pdf.
Would be nice if someone would incorporate these fixes into an update.... I suspect a lot of non-technical users, such as myself, are having problems....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.