SULDR Forums Supported Printers Printing Questions Scanning Questions General Questions Samsung Installer

Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
Scanning / Re: SCX 4500 on ubuntu 18.04.01 on USB
« Last post by pat on November 28, 2018, 06:19:26 »
It's not the same scanner (SCX 4500 <> SCX 4705).
In my case I also had to install "suld-scanner-usblp-fix". You can try to change usb socket, if possible directly on the motherboard. Check this page https://www.bchemnet.com/suldr/scanning.html

2
Scanning / Re: SCX 4500 on ubuntu 18.04.01 on USB
« Last post by yanndan on November 28, 2018, 03:20:16 »
Hi pat,

Thanks for your answer but I still cannot scan with linux. I also tried with linux mint and I have the same issue. There is something that bother me: it worked yesterday but it does not work today. I did not change anything in the configuration.

Thanks for everything.
yanndan
3
Using the Repository / Re: repo broken
« Last post by parrotlarch on November 27, 2018, 07:12:52 »
Thank you so much! Repo works, and the driver installed!
After applying your tips from point 1 and 2 aptitude told me, that the package apt-transport-https is not installed (and it should be). After installing the package and updating repos everything works fine.

The thing is that only  driver from your repo let me use scanner, I tried official samsung drivers and every tip from the internet. You saved me from using Windows just because of the printer. Once again thanks for your help, and for your hard work!
4
Using the Repository / Re: repo broken
« Last post by bchemnet on November 27, 2018, 06:02:15 »
W: Failed to fetch http://www.bchemnet.com/suldr/dists/debian/extra/binary-amd64/Packages  Bad header line

When this error occurs with an otherwise apparently working repository or one that had been working, it pretty much always means some sort of network traffic error occurred.  The error should automatically clear quickly, but apt sometimes get stuck in some odd state.  Usually clearing the cache takes care of it, but obviously not this time.  Some other things you can try to force apt to find the repository again:
1. Change the "http" to "https" in the repository source line.  In some cases, it might be necessary to update the repository files, and then revert back to "http" to get it to work.
2. Comment out/deactivate (or delete) the bchemnet repository line, update apt, add the line back and update again.
3. If neither of the above works, it could be a persistent DNS or path resolution problem.  (However, I doubt this because if it was you would probably not be able to reach this forum.)  If know how, you can try changing the DNS servers being used by your computer/network, updating apt, and then changing the DNS servers back.
4. Wait 24 hours, clear the cache again, and repeat 1 or 2.
5
Using the Repository / Re: repo broken
« Last post by parrotlarch on November 27, 2018, 02:18:20 »
Tried it again,and cleared the cache, but no luck.
Great thanks, for such a quick reply!!
6
Using the Repository / Re: repo broken
« Last post by oldunixguy on November 27, 2018, 00:09:35 »
as a data point... I just ran an apt-get update and your relevant entries are failing as follows. I'm no expert on apt so I don't know whether this is expected or not:

Get:1 http://www.bchemnet.com debian Release.gpg
Err http://www.bchemnet.com debian/extra amd64 Packages
Err http://www.bchemnet.com debian/extra i386 Packages
Get:3 http://www.bchemnet.com debian/extra amd64 Packages
Get:3 http://www.bchemnet.com debian/extra amd64 Packages
Err http://www.bchemnet.com debian/extra amd64 Packages
Err http://www.bchemnet.com debian/extra i386 Packages
Get:4 http://www.bchemnet.com debian/extra amd64 Packages
Err http://www.bchemnet.com debian/extra amd64 Packages
Err http://www.bchemnet.com debian/extra i386 Packages
Err http://www.bchemnet.com debian/extra amd64 Packages
Err http://www.bchemnet.com debian/extra i386 Packages
Bad header line

W: Failed to fetch http://www.bchemnet.com/suldr/dists/debian/extra/binary-amd64/Packages  Bad header line
7
Using the Repository / Re: repo broken
« Last post by bchemnet on November 26, 2018, 21:28:52 »
The repository is up, but there may be some temporary network path issue reaching it from some locations.  If the issues persists in a day or two and clearing the cache does not solve it, reply here.
8
Using the Repository / Re: repo broken
« Last post by oldunixguy on November 26, 2018, 15:33:17 »
I see that my references to this repo are again failing....
I will try the rm -rf /var/lib/apt/lists/* again.
oldunixguy
9
Using the Repository / Re: repo broken
« Last post by parrotlarch on November 26, 2018, 08:35:46 »
I didn't wanted to create a new discussion, so I'm writing here, because as I can see the repo is broken or empty.
I have a old usb samsung scx 4521f. I've been using this repo for like forever. On a new system I added repo, installed keyring, but apt finds no packages. It finds no suldr-driver-4.00.39. Actually when I search with aptitude search suld, it finds only this installed keyring.
10
The planned shut down is canceled.  SULDR will remain active in its current form for at least a couple of more years, although I cannot promise that I will have time to perform updates or provide assistance in the forums.  The forums will remain active for users to help each other.
Pages: [1] 2 3 4 5 6 ... 10
Repository Information Legal Contact Alternative Drivers