Re: wtf just happened to my local staging web server
Le 04/05/2022 à 19:01, Gary Dale a écrit : My Apache2 file/print/web server is running Bullseye. I had to restart it yesterday evening to replace a disk drive. Otherwise the last reboot was a couple of weeks ago - I recall some updates to Jitsi - but I don't think there were any updates since then. Today I find that I can't get through to any of the sites on the server. Instead I get the Apache2 default web page. This happens with both Firefox and Chromium. This happens for all the staging sites (that I access as ".loc" through entries in my hosts file). My jitsi and nextcloud servers simply report failure to get to the server. I verified that the site files (-available and -enabled) haven't changed in months. I tried restarting the apache2 service and got an error so I tried stopping it then starting it again - same error: root@TheLibrarian:~# service apache2 start It looks like you started it, not restart, thus the running apache is not killed [...] May 04 12:16:55 TheLibrarian systemd[1]: Starting The Apache HTTP Server... May 04 12:16:55 TheLibrarian apachectl[7935]: (98)Address already in use: AH00072: make_sock: could not bind to addre> May 04 12:16:55 TheLibrarian apachectl[7935]: (98)Address already in use: AH00072: make_sock: could not bind to addre> This is consistent with former apache still running at that time, and using the wanted ports.
Re: wtf just happened to my local staging web server
On Wed, May 4, 2022 at 7:18 PM Gary Dale wrote: > May 04 12:16:55 TheLibrarian systemd[1]: Starting The Apache HTTP > Server... > May 04 12:16:55 TheLibrarian apachectl[7935]: (98)Address already in use: > AH00072: make_sock: could not bind to addre> > May 04 12:16:55 TheLibrarian apachectl[7935]: (98)Address already in use: > AH00072: make_sock: could not bind to addre> > May 04 12:16:55 TheLibrarian apachectl[7935]: no listening sockets > available, shutting down > May 04 12:16:55 TheLibrarian apachectl[7935]: AH00015: Unable to open logs > May 04 12:16:55 TheLibrarian apachectl[7932]: Action 'start' failed. > May 04 12:16:55 TheLibrarian apachectl[7932]: The Apache error log may > have more information. > May 04 12:16:55 TheLibrarian systemd[1]: apache2.service: Control process > exited, code=exited, status=1/FAILURE > May 04 12:16:55 TheLibrarian systemd[1]: apache2.service: Failed with > result 'exit-code'. > May 04 12:16:55 TheLibrarian systemd[1]: Failed to start The Apache HTTP > Server. > The errors show that Apache was unable to bind to the listener port (Address already in use). Check for other services (maybe Nginx?) which are listening on the same port as Apache tries to bind to. Run: netstat -lntup Also check /etc/apache2/ports.conf for possible misconfigurations. Are you using HTTP (Port 80) only or also HTTPS (Port 443)? Just to rule a config error out, run "apache2ctl configtest". As I said, I do get the default Apache2 page saying "It works" but that > appears to be optimistic. ps aux | grep apache2 fails to show the service, > which confirms the systemctl message that it isn't running. > That could be your browser cache tricking you. You can verify with "curl localhost".
Re: Crucial SSDs and Debian Bullseye
On 5/5/22 10:23, Borden wrote: Good to see that the issue was just mis-installation, as I recently upgraded from a Samsung 2TB EVO to a Crucial 2 TB drive without issue (well, I had PLENTY of issues with Samsung's "customer service" and Newegg's "return policy"). Resolved never to buy Samsung products again, as their "warranty" is worthless when nobody will honour it. I'll stop buying from Newegg once I use up the credit I was compelled to accept after they wouldn't let me return the drives made magically defective by Samsung's Magician. Apparently Crucial has a marginally better customer service reviews, so I've tried them and haven't had issues (so far). Korean companies are know for poor customer services. I will never buy or I just don't expect anything if I choose to buy their products.
Re: Re: Crucial SSDs and Debian Bullseye
Good to see that the issue was just mis-installation, as I recently upgraded from a Samsung 2TB EVO to a Crucial 2 TB drive without issue (well, I had PLENTY of issues with Samsung's "customer service" and Newegg's "return policy"). Resolved never to buy Samsung products again, as their "warranty" is worthless when nobody will honour it. I'll stop buying from Newegg once I use up the credit I was compelled to accept after they wouldn't let me return the drives made magically defective by Samsung's Magician. Apparently Crucial has a marginally better customer service reviews, so I've tried them and haven't had issues (so far).
[SOLVED] Re: Crucial SSDs and Debian Bullseye
On Wed, Apr 27, 2022 at 14:17 Tom Browder wrote: > On Wed, Apr 27, 2022 at 12:12 Alexander V. Makartsev > wrote: > >> On 27.04.2022 20:37, Tom Browder wrote: >> > ... >> > If either of those fail to see it, I’m afraid I toasted it. I don’t >> > think that will qualify for a return. > > > I finally got it working! I blame lack of attention to details, old age, > shaky hands, and < 100% vision. I uninstalled the ssd, looked all over > closely (again) and realized I had not really installed it at all! > Yesterday I could not see that it would fit in the space for the hard drive > carrier because I had it upside down! I finally got it together (even > missing two screws I hope I can find later) and the drive is now recognized. > > Thank you all for the support, and I cannot blame Crucial one iota. > > Debian on, my fellow Debianites! > > -Tom > >
Re: Crucial SSDs and Debian Bullseye
On 27/04/2022 18:11, Alexander V. Makartsev wrote: It is next to impossible to actually mishandle and "toast" a device simply by unpacking it and connecting to a SATA port. (Even when PC is powered on¹). SSDs are not fragile, they are electrically compatible with SATA standard, so both data and power port parts won't do any damage to a device, no matter how old or new the hardware is. Agree. On my Debian server, I've been actually hot-plugging SATA drives, both HDD and SSD for years. Never had a problem. Linux detects everything on the fly :) If new SSD cannot be detected in OP Toshiba laptop, its most likely faulty SSD or user error. Nothing to do with Debian. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: Crucial SSDs and Debian Bullseye
On 27/04/2022 12:57, Tom Browder wrote: On Wed, Apr 27, 2022 at 06:42 Christian Britz mailto:cbr...@t-online.de>> wrote: ... I have seem some indications on the web though, which suggest there might be an ISO image for updating the drive too. What is the exact model name? Crucial MX500 1000GB 2.5-INCH SOLID STATE DRIVE Thanks, Christian -Tom I've got Crucial MX500 SSDs, 250GB versions, they work perfectly fine with any system, not just Windows. I use them on Debian in RAID1 mode. Always worked fine from first start. If your SSD cannot be detected in BIOS, that's a problem with the laptop (compatibility issue, or SSD is broken, or something else). Plug the SSD to another computer to check if it works, if not, return it to the seller. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: Crucial SSDs and Debian Bullseye
On Wed, 27 Apr 2022 17:08:04 +0500 "Alexander V. Makartsev" wrote: > On 27.04.2022 16:06, Tom Browder wrote: > > I am trying to replace the original hard drive on an old Toshiba > > laptop with a 1 TB SSD from Crucial. (I had recently successfully done > > that in an old Dell Latitude and had no problems.) > > > > I first did a clean install of Debian 11 on the old drive to ensure > > the laptop works okay. Then I installed the new SSD and it can't find > > the drive. From what I can find at Crucial, I need to install their > > Storage Executive program on a Windows host, look up the SSD to a > > USB/SATA connector on that host, and configure or install the firmware > > onto the SSD. > > > I've never heard anything like that and I've worked with many > consumer-grade SSDs. > Usually all SSDs "just work". They may come pre-partitioned and > pre-formatted, but this could be reconfigured with any standard utility > programs. > The only thing I can think of, is that it could require usage of some > vendor-specific proprietary software to setup hardware encryption and/or > to update currently flashed firmware to newer versions. There's OPAL. Presumably uncommon on consumer-grade drives, but it does require special software to configure (although not necessarily vendor specific software) and can be a pain to work with (at least if one isn't familiar with them, as I wasn't when I encountered it in the wild, in a second-hand machine ;)) https://en.wikipedia.org/wiki/Opal_Storage_Specification https://wiki.archlinux.org/title/Self-encrypting_drives -- Celejar
Re: wtf just happened to my local staging web server
On Wed 04 May 2022 at 14:42:15 -0400, Greg Wooledge wrote: > On Wed, May 04, 2022 at 07:38:35PM +0100, Brian wrote: > > My young childre read -user. They asked me what "wtf" means. Please, > > explain, for the benefit of us civilised and acronymn-challenged > > users, what it stands for. > > Clearly just a really bad typo for "what". Clearly. Training the brain and fingers to avoid such typos is indictated. -- Brian.
Re: wtf just happened to my local staging web server
On Wed, May 04, 2022 at 07:38:35PM +0100, Brian wrote: > My young childre read -user. They asked me what "wtf" means. Please, > explain, for the benefit of us civilised and acronymn-challenged > users, what it stands for. Clearly just a really bad typo for "what".
Re: wtf just happened to my local staging web server
On Wed 04 May 2022 at 13:01:58 -0400, Gary Dale wrote: [...] My young childre read -user. They asked me what "wtf" means. Please, explain, for the benefit of us civilised and acronymn-challenged users, what it stands for. For extra points, knowing whether it was an essential part of your query would be interesting. -- Brian.
Re: wtf just happened to my local staging web server
On 2022-05-04 13:21, Greg Wooledge wrote: On Wed, May 04, 2022 at 01:01:58PM -0400, Gary Dale wrote: May 04 12:16:55 TheLibrarian systemd[1]: Starting The Apache HTTP Server... May 04 12:16:55 TheLibrarian apachectl[7935]: (98)Address already in use: AH00072: make_sock: could not bind to addre> May 04 12:16:55 TheLibrarian apachectl[7935]: (98)Address already in use: AH00072: make_sock: could not bind to addre> Something else is using the ports that Apache wants to use. Assuming those ports are 80 and 443, you could use commands like this to see what's using them: lsof -i :80 lsof -i :443 If your configuration is telling Apache to use some other ports, then substitute your port numbers. Thanks. Somehow nginx got installed. Wondering if jitsi or nextcloud did that because I certainly didn't (doesn't seem likely though because they both failed). I guess I should pay more attention to the packages that get installed when I do apt full-upgrade... Usually I just scan to see if there is anything that I should reboot over.
Re: wtf just happened to my local staging web server
On Wed, May 04, 2022 at 01:01:58PM -0400, Gary Dale wrote: > May 04 12:16:55 TheLibrarian systemd[1]: Starting The Apache HTTP Server... > May 04 12:16:55 TheLibrarian apachectl[7935]: (98)Address already in use: > AH00072: make_sock: could not bind to addre> > May 04 12:16:55 TheLibrarian apachectl[7935]: (98)Address already in use: > AH00072: make_sock: could not bind to addre> Something else is using the ports that Apache wants to use. Assuming those ports are 80 and 443, you could use commands like this to see what's using them: lsof -i :80 lsof -i :443 If your configuration is telling Apache to use some other ports, then substitute your port numbers.
wtf just happened to my local staging web server
My Apache2 file/print/web server is running Bullseye. I had to restart it yesterday evening to replace a disk drive. Otherwise the last reboot was a couple of weeks ago - I recall some updates to Jitsi - but I don't think there were any updates since then. Today I find that I can't get through to any of the sites on the server. Instead I get the Apache2 default web page. This happens with both Firefox and Chromium. This happens for all the staging sites (that I access as ".loc" through entries in my hosts file). My jitsi and nextcloud servers simply report failure to get to the server. I verified that the site files (-available and -enabled) haven't changed in months. I tried restarting the apache2 service and got an error so I tried stopping it then starting it again - same error: root@TheLibrarian:~# service apache2 start Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details. root@TheLibrarian:~# systemctl status apache2.service ●apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Active: failed(Result: exit-code) since Wed 2022-05-04 12:16:55 EDT; 5s ago Docs: https://httpd.apache.org/docs/2.4/ Process: 7932 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE) CPU: 29ms May 04 12:16:55 TheLibrarian systemd[1]: Starting The Apache HTTP Server... May 04 12:16:55 TheLibrarian apachectl[7935]: (98)Address already in use: AH00072: make_sock: could not bind to addre> May 04 12:16:55 TheLibrarian apachectl[7935]: (98)Address already in use: AH00072: make_sock: could not bind to addre> May 04 12:16:55 TheLibrarian apachectl[7935]: no listening sockets available, shutting down May 04 12:16:55 TheLibrarian apachectl[7935]: AH00015: Unable to open logs May 04 12:16:55 TheLibrarian apachectl[7932]: Action 'start' failed. May 04 12:16:55 TheLibrarian apachectl[7932]: The Apache error log may have more information. May 04 12:16:55 TheLibrarian systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE May 04 12:16:55 TheLibrarian systemd[1]: apache2.service: Failed with result 'exit-code'. May 04 12:16:55 TheLibrarian systemd[1]: Failed to start The Apache HTTP Server. also root@TheLibrarian:/var/log# journalctl -xe ░░The job identifier is 4527. May 04 12:50:49 TheLibrarian apachectl[8232]: (98)Address already in use: AH00072: make_sock: could not bind to addre> May 04 12:50:49 TheLibrarian apachectl[8232]: (98)Address already in use: AH00072: make_sock: could not bind to addre> May 04 12:50:49 TheLibrarian apachectl[8232]: no listening sockets available, shutting down May 04 12:50:49 TheLibrarian apachectl[8232]: AH00015: Unable to open logs May 04 12:50:49 TheLibrarian apachectl[8229]: Action 'start' failed. May 04 12:50:49 TheLibrarian apachectl[8229]: The Apache error log may have more information. May 04 12:50:49 TheLibrarian systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE ░░Subject: Unit process exited ░░Defined-By: systemd ░░Support: https://www.debian.org/support ░░ ░░An ExecStart= process belonging to unit apache2.service has exited. ░░ ░░The process' exit code is 'exited' and its exit status is 1. May 04 12:50:49 TheLibrarian systemd[1]: apache2.service: Failed with result 'exit-code'. ░░Subject: Unit failed ░░Defined-By: systemd ░░Support: https://www.debian.org/support ░░ ░░The unit apache2.service has entered the 'failed' state with result 'exit-code'. May 04 12:50:49 TheLibrarian systemd[1]: Failed to start The Apache HTTP Server. ░░Subject: A start job for unit apache2.service has failed ░░Defined-By: systemd ░░Support: https://www.debian.org/support ░░ ░░A start job for unit apache2.service has finished with a failure. ░░ ░░The job identifier is 4527 and the job result is failed. As I said, I do get the default Apache2 page saying "It works" but that appears to be optimistic. ps aux | grep apache2 fails to show the service, which confirms the systemctl message that it isn't running. There is nothing in /var/log/apache2/error.log. The .1 log ends yesterday but only contains complaints about php7. Systemctl does report (above) "unable to open logs" so that would explain the lack of additional messages. The apache2 directory and its files are root:adm with only root having write privileges. I tried giving the adm group write privileges but that didn't work. Turns out the group is empty. Adding www-data to it didn't work either. Any ideas on how to track down the cause of the failure(s)? Thanks.
Re: Networking book recommendation
On 5/3/2022 10:35 PM, Tom Browder wrote: On Tue, May 3, 2022 at 15:18 john doe wrote: On 5/3/2022 9:42 PM, Tom Browder wrote: I'm about to sign up for a fixed IPv4 address to my home. I know a bit about setting up simple internal networks, but want to make sure I'm doing it all correctly and securely. Does anyone have a good book they recommend for such use? What do you mean by "correctly and securly", the networking is never secure. Thanks, I didn't know that. Depending on what you need, you might want firewall ... I'm considering HaProxy downsteam from the router. That also brings the question, why do you need a static IPv4 address? I'm moving my webservers inside. I've learned my networking knowlage by reading on line or asking questions when I'm stuck! :) So I can not recommend a book. Here are some comments in addition to this thread: - Do not use the router capability provided by your ISP. This is mainly to avoid letting your ISP remotely control the thing and disable the firewall for example. If you can, use your own router. If your ISP requires to work with their router put the ISP thing in 'bridge'/modem only mode, this will allow to get your public IPv4 address to your own gateway. - Use VPN to access your servers remotely. I find it easier to use a VPN (responsible for public remote connection) to connect to my own network then use SSH (responsible for private remote connection) to connect to my intranet devices This also give you two layers of authentication and you have separate services. -- John Doe
Re: sane-backend for Epson EcoTank ET-2711
On Wed 04 May 2022 at 15:43:03 +0200, Dieter Rohlfing wrote: > Am Wed, 4 May 2022 12:50:14 +0100 > schrieb Brian : > > >I wonder whether the net backend is required. What happens if the > >entry is commented out? > > My fault: net was enabled, therefore I thought, that it is necessary. > According to your proposal I disabled net and access to ET2711 is > possible. So no need to enable net, airscan alone is sufficient. If you do not need more that 100dpi and 300dpi, airscan gives a user an alternative to Epson's non-free driver. > >Scanning is taking place using the WSD (Web Services for Devices) > >protocol. The eSCL protocol needs AirPrint on the device. > > I thought eSCL is just a synonym for WSD. Wrong or right? This is my > first approach to scanning and I'm not very familiar with the different > scanning protocols. They are two completely different independent protocols. See https://wiki.debian.org/SaneOverNetwork > >Would you confirm you can scan with > > > > xsnae "airscan:w0:EPSON ET-2710 Series" > > It works. Thanks. > >Unfortunately, the vendor's implementation of WSD may offer only > >a limited number of resolutions. airscan cannot do anything about > >this; it can only work with what it is told by the device. > > Agreed. eSCL would have provided a wider range of resolutions. Why in this day and age Epson chose not to provide the device with AirPrint is beyond me. > >With a USB connection, what do you get for > > lsusb -v | grep -A 3 bInterfaceClass.*7 ? > > The output is: > > > bInterfaceClass 7 Printer > > bInterfaceSubClass 1 Printer > > bInterfaceProtocol 2 Bidirectional > > iInterface 6 USB2.0 Printer The device does not provide IPP-over-USB either. Many MFPs have been offering it since soon after 2012. -- Brian.
Re: Odd reproducible problem - but is it a bug?
Anders Andersson (12022-05-04): > On this note, I've always found it annoying that debian (and likely > others) don't put /sbin in the normal user's $PATH. A lot of the tools > there have uses other than modifying the system. I have to unpack Zip files rather often, I use unzip in command-line. It has become an automatism: “unz/tmp/...”. Recently, initrd-tools complained that zstd was not installed, so I installed it. The next time I had a Zip file to unpack, I typed “unz” and was confused that it did not work: “unz” had become ambiguous between “unzip(sfx)” and “unzstd”. Every program in the search path clutters the namespace and makes the shell completion less efficient. When a program is useful for a normal user once every 36th of the month, I would rather not have it in the default search path: typing “/sb” then is cheap enough for the benefit of gaining a few keystrokes for commands I use many times a day. YMMV. Regards, -- Nicolas George signature.asc Description: PGP signature
Re: sane-backend for Epson EcoTank ET-2711
On Wed 04 May 2022 at 14:35:29 +0100, mick crane wrote: > On 2022-05-04 14:12, Dieter Rohlfing wrote: > > Am Wed, 04 May 2022 11:42:39 +0100 > > schrieb mick crane : > > > > > You can probably type "scanimage --help -A -d 'airscan:w0:EPSON > > > ET-2710 > > > Series'" > > > to get a list of capabilities. > > > > This is the ET2711 specific output: > > > > > Options specific to device `airscan:w0:EPSON ET-2710 Series': > > > Standard: > > >--resolution 100|300dpi [300] > > seems you should have 1200dpi available. > No idea why not Hint: read *all* the posts in this short thread :). -- Brian.
Re: sane-backend for Epson EcoTank ET-2711
Am Wed, 4 May 2022 12:50:14 +0100 schrieb Brian : >I wonder whether the net backend is required. What happens if the >entry is commented out? My fault: net was enabled, therefore I thought, that it is necessary. According to your proposal I disabled net and access to ET2711 is possible. So no need to enable net, airscan alone is sufficient. >Scanning is taking place using the WSD (Web Services for Devices) >protocol. The eSCL protocol needs AirPrint on the device. I thought eSCL is just a synonym for WSD. Wrong or right? This is my first approach to scanning and I'm not very familiar with the different scanning protocols. >Would you confirm you can scan with > > xsnae "airscan:w0:EPSON ET-2710 Series" It works. >Unfortunately, the vendor's implementation of WSD may offer only >a limited number of resolutions. airscan cannot do anything about >this; it can only work with what it is told by the device. Agreed. >With a USB connection, what do you get for > lsusb -v | grep -A 3 bInterfaceClass.*7 ? The output is: > bInterfaceClass 7 Printer > bInterfaceSubClass 1 Printer > bInterfaceProtocol 2 Bidirectional > iInterface 6 USB2.0 Printer Dieter
Re: sane-backend for Epson EcoTank ET-2711
On 2022-05-04 14:12, Dieter Rohlfing wrote: Am Wed, 04 May 2022 11:42:39 +0100 schrieb mick crane : You can probably type "scanimage --help -A -d 'airscan:w0:EPSON ET-2710 Series'" to get a list of capabilities. This is the ET2711 specific output: Options specific to device `airscan:w0:EPSON ET-2710 Series': Standard: --resolution 100|300dpi [300] seems you should have 1200dpi available. No idea why not mick -- Key ID4BFEBB31
Re: Odd reproducible problem - but is it a bug?
On Wed, May 04, 2022 at 07:04:52AM -0600, Charles Curley wrote: > On Wed, 4 May 2022 05:23:31 +0200 > Anders Andersson wrote: > > > On this note, I've always found it annoying that debian (and likely > > others) don't put /sbin in the normal user's $PATH. A lot of the tools > > there have uses other than modifying the system. > > It can be annoying, but for good reason. In a multi-user system (such > as Unix), it is a good security precaution to reserve programs that can > modify or even inform the user about the state of the system to trusted > users, such as root or wheel. Hence regular programs for regular users > go into directories called bin, and system programs go into directories > called sbin, and paths are set accordingly. That is the most ludicrous thing I've heard in... a long time. If a command can reveal sensitive information to an unprivileged user, then "hiding" it in /sbin is not a valid security measure. The smart user will simply run /sbin/whatever, or change their PATH variable to include /sbin. Of course, your assertion that any command *could* reveal such sensitive information is laughable. Programs can only do the things allowed by their privileges. If joe tries to read the /etc/shadow file, he can't do it, because he doesn't have the correct privileges. None of the commands in /sbin are going to be able to do it either, because they run *as joe*. (Obviously, setuid or setgid programs could exist which run with elevated privileges. Those have to be written correctly. If one of them has a security hole, just hiding it in /sbin *does not count* as a security improvement on your system.) > Even on a single user system the distinction is worth retaining. If > nothing else, one occasionally needs a reminder to be careful with > certain programs lest one shoot oneself in the foot. There are several reasons why /sbin exists, historically. On some systems, the programs in /sbin are *statically linked*. That's what the 's' actually stands for -- not 's'ecure, not 's'uperuser, but 's'tatic. They're needed during boot, at a time when the file system which contains the shared libraries used by commands in /bin may not be mounted yet. HP-UX is one such system. /bin is a symlink to /usr/bin, and there are both /usr/bin/cat and /sbin/cat commands. Shell scripts which must run during the early stages of boot can use /sbin/cat (along with redirections) to copy files, or display simple messages. On most other systems, the programs in /sbin are not statically linked, but are placed there for other reasons. One reason is simply that these programs don't *do* anything useful or helpful for ordinary users. They may not even run at all. Another reason is to reduce the size of the /usr/bin and /bin directories, for performance. It's a tiny gain, but over years of operation, it could add up to something noticeable. The main reason is "because that's where it has always been". This is both for user expectations, and for backward compatibility in case some idiot hard-coded /sbin/ifconfig in a shell script. Keeping the commands in their historic locations will prevent a few badly-written scripts from breaking.
Re: sane-backend for Epson EcoTank ET-2711
Am Wed, 04 May 2022 11:42:39 +0100 schrieb mick crane : >You can probably type "scanimage --help -A -d 'airscan:w0:EPSON ET-2710 >Series'" >to get a list of capabilities. This is the ET2711 specific output: >Options specific to device `airscan:w0:EPSON ET-2710 Series': > Standard: >--resolution 100|300dpi [300] >Sets the resolution of the scanned image. >--mode Color|Gray [Color] >Selects the scan mode (e.g., lineart, monochrome, or color). >--source Flatbed [Flatbed] >Selects the scan source (such as a document-feeder). > Geometry: >-l 0..215.9mm [0] >Top-left x position of scan area. >-t 0..297.18mm [0] >Top-left y position of scan area. >-x 0..215.9mm [215.9] >Width of scan-area. >-y 0..297.18mm [297.18] >Height of scan-area. > Enhancement: >--brightness -100..100% (in steps of 1) [0] >Controls the brightness of the acquired image. >--contrast -100..100% (in steps of 1) [0] >Controls the contrast of the acquired image. >--shadow 0..100% (in steps of 1) [0] >Selects what radiance level should be considered "black". >--highlight 0..100% (in steps of 1) [100] >Selects what radiance level should be considered "white". >--analog-gamma 0.008..4 [1] >Analog gamma-correction >--negative[=(yes|no)] [no] >Swap black and white > >All options specific to device `airscan:w0:EPSON ET-2710 Series': > Standard: >--resolution 100|300dpi [300] >Sets the resolution of the scanned image. >--mode Color|Gray [Color] >Selects the scan mode (e.g., lineart, monochrome, or color). >--source Flatbed [Flatbed] >Selects the scan source (such as a document-feeder). > Geometry: >-l 0..215.9mm [0] >Top-left x position of scan area. >-t 0..297.18mm [0] >Top-left y position of scan area. >-x 0..215.9mm [215.9] >Width of scan-area. >-y 0..297.18mm [297.18] >Height of scan-area. > Enhancement: >--brightness -100..100% (in steps of 1) [0] >Controls the brightness of the acquired image. >--contrast -100..100% (in steps of 1) [0] >Controls the contrast of the acquired image. >--shadow 0..100% (in steps of 1) [0] >Selects what radiance level should be considered "black". >--highlight 0..100% (in steps of 1) [100] >Selects what radiance level should be considered "white". >--analog-gamma 0.008..4 [1] >Analog gamma-correction >--negative[=(yes|no)] [no] >Swap black and white Dieter
Re: Odd reproducible problem - but is it a bug?
On Wed, 4 May 2022 05:23:31 +0200 Anders Andersson wrote: > On this note, I've always found it annoying that debian (and likely > others) don't put /sbin in the normal user's $PATH. A lot of the tools > there have uses other than modifying the system. It can be annoying, but for good reason. In a multi-user system (such as Unix), it is a good security precaution to reserve programs that can modify or even inform the user about the state of the system to trusted users, such as root or wheel. Hence regular programs for regular users go into directories called bin, and system programs go into directories called sbin, and paths are set accordingly. Even on a single user system the distinction is worth retaining. If nothing else, one occasionally needs a reminder to be careful with certain programs lest one shoot oneself in the foot. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: stretch with bullseye kernel?
On 4/05/22 18:57, Tixy wrote: On Wed, 2022-05-04 at 00:44 +0300, IL Ka wrote: Linux kernel is backward compatible. Linus calls it "we do not break userspace". That means _old_ applications should work on new kernel There's also the issue of what config options the kernel is built with. I'm sure there's been at least one time in the past where for a new Debian release they've had to enable a kernel feature that the new systemd (or udev?) wanted. But again, a case like that would stop a new Debian working on and old kernel, not the other way around as the OP is intending. I don't expect the Debian kernel maintainers would _remove_ kernel config options needed in a prior release. Thanks all - I thought it would probably be safe, and indeed everything seems to be working :-) Cheers, Richard
Re: sane-backend for Epson EcoTank ET-2711
On Wed 04 May 2022 at 11:51:06 +0200, Dieter Rohlfing wrote: > Am Tue, 3 May 2022 23:19:17 +0100 > schrieb Brian : > > >AirPrint is not mentioned in the device's specifications at > > > > > > https://www.epson.co.uk/products/printers/inkjet/consumer/ecotank-et-2711/p/23003 > > This website says: > > >Optical Resolution > >2,400 DPI x 1,200 DPI (Horizontal x Vertical) > > but xsane offers me only 100 dpi and 300 dpi and no higher resolution. Dealt with later on. > >Enable the net backend? Nothing else? > > The net and airscan sane-backends. I wonder whether the net backend is required. What happens if the entry is commented out? > >Please give what you get for > > > > scanimage -L > > > > airscan-discover > > System is Debian 11.3, airscan doesn't exist in previous versions. sane-airscan is in buster-backports. > scanimage -L > device `airscan:w0:EPSON ET-2710 Series' is a WSD EPSON ET-2710 Series > ip=172.16.10.91 > > airscan-discover > [devices] > EPSON ET-2710 Series = http://172.16.10.91:80/WDP/SCAN, WSD Scanning is taking place using the WSD (Web Services for Devices) protocol. The eSCL protocol needs AirPrint on the device. Would you confirm you can scan with xsnae "airscan:w0:EPSON ET-2710 Series" or simple-scan "airscan:w0:EPSON ET-2710 Series" Unfortunately, the vendor's implementation of WSD may offer only a limited number of resolutions. airscan cannot do anything about this; it can only work with what it is told by the device. With a USB connection, what do you get for lsusb -v | grep -A 3 bInterfaceClass.*7 ? -- Brian.
Re: sane-backend for Epson EcoTank ET-2711
On 2022-05-04 10:51, Dieter Rohlfing wrote: scanimage -L device `airscan:w0:EPSON ET-2710 Series' is a WSD EPSON ET-2710 Series ip=172.16.10.91 I'd have to familiarize myself with setting up scanning You can probably type "scanimage --help -A -d 'airscan:w0:EPSON ET-2710 Series'" to get a list of capabilities. mick -- Key ID4BFEBB31
Re: sane-backend for Epson EcoTank ET-2711
Am Tue, 3 May 2022 23:19:17 +0100 schrieb Brian : >AirPrint is not mentioned in the device's specifications at > > > https://www.epson.co.uk/products/printers/inkjet/consumer/ecotank-et-2711/p/23003 This website says: >Optical Resolution >2,400 DPI x 1,200 DPI (Horizontal x Vertical) but xsane offers me only 100 dpi and 300 dpi and no higher resolution. >Enable the net backend? Nothing else? The net and airscan sane-backends. >Please give what you get for > > scanimage -L > > airscan-discover System is Debian 11.3, airscan doesn't exist in previous versions. scanimage -L device `airscan:w0:EPSON ET-2710 Series' is a WSD EPSON ET-2710 Series ip=172.16.10.91 airscan-discover [devices] EPSON ET-2710 Series = http://172.16.10.91:80/WDP/SCAN, WSD Dieter
Re: Getting a patch applied with an unresponsive maintainer
On Tue, May 03, 2022 at 04:39:04PM +0100, Adam Dinwoodie wrote: Exactly what I needed, thank you! I hadn't known about the -mentors list, and I wasn't sure going straight to -devel was appropriate, but I think that gives me my next steps here :) Good luck! -- Please do not CC me for listmail. 👱🏻 Jonathan Dowland ✎j...@debian.org 🔗 https://jmtd.net
