Re: single quote "'" in bash xterm or lxterminal
Mr. Wooledge, Long before I realized I could put /home/mike on a separate partition I started putting my stuff on a separate partition and just called it /mc. A couple of tomes I had different OS versions on the same hard drive so it made sense to keep the portions of my stuff that weren't OS specific in a place I could reach from both OS installs. Since my tower died and I replaced it with a Raspberry PI, home is on the uSD. Having /mc on a flash drive means I have it available whether I'm running debian, devuan or raspbian and if home were on that flash since those OSs are only similar things could get even more confusing than they are with my setup. A problem I've not run into but considered is how to deal with thngs if that flash drive dies. I suspect logging into a system where you have no home for your primary user might get interesting. Mr. Nikulin, I shouldn't be surprised if xterm-256color is just enough different from xterm and lxterminal that that is why you don't see a problem with the '"...": ...' syntax. If you have xterm-256color you likely have xterm too. Have you tried it? Thanks for showing me different ways of looking at my challenges. Happy New Year fellas Mike -- Happiness is not so much in having but in sharing.
Re: Printer weirdness
On 12/30/23 16:43, Greg Wooledge wrote: On Sat, Dec 30, 2023 at 10:25:27PM +0100, Hans wrote: Sorry, did I impress myself so wrong? What I meant, were the packages for the driver, which Brother provide. If you want to know, take a look at support.brother.com, see which I mean. Someone else going to a web site today is NOT necessarily going to figure out what version of what package YOU got from a web site at some unknown point in the past. Sorry Greg but as a fan of brother printers, I can't let this one go by. IF you use the script Brother provides, run it, it asks you for the exact model number of the printer you have, and then installs and sets up the latest bug fixed version of their driver for THAT printer, for in my experience any Brother product. And while the script may get updated, even a 7 year old version will still get you the latest driver they have. Brother likes linux and actually does support their products. I have 2, and both work for everything claimed on the box, but you'll probably have to remove cups-browsed to allow the brother drivers to work. The cups drivers for ipp everywhere are busted, no duplex, and no tray selection possible for the better printers. And no sharing works in the bookworm to bookworm version, but I have 3 running buster and linuxcnc,and their version of cups see's the sharing just fine. The web site may have changed. New versions of packages may be there. Different packages may be there. Packages may have been removed because the developers have ruled them obsolete, or because the managers have decided to charge money for them. We have no idea. Fud. Even if the web site hasn't changed since you went there, there might be more than one thing on the web site, and we wouldn't know which one you got. If you want people to be able to help you, it's in your best interest to be CLEAR about EXACTLY what you're using. You do that by telling us what it is -- its name, and its version number, if it has one. You do THAT by writing your email FROM THE DEBIAN SYSTEM on which you are having the problem -- or in the worst case, you write the email on the same system from which you have an ssh session to the Debian system, so that you can easily run commands and paste them and paste their output from the Debian system into the email you are writing. The most basic request for help with a printer should include: * Which version of Debian you're running. * What model of printer you're using. * How the printer is connected to the Debian system. * What printing software you're using on the Debian system. * What the problem is. (Show exact error messages if possible!) All excellent advice. I should follow it better than I do. :(> Thanks Greg. Take care & stay warm and well. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: wegvallen / uitvallen van IPv6
On Fri, 29 Dec 2023 22:54:38 +0100 Geert Stappers wrote: > Verder is mijn inschatting dat het `ip6tables`, i.p.v. `iptables`, > moet zijn. Inderdaad, uit de losse pols neergeschreven, niet getest, maar zoals je zegt: ip6tables :-) -- richard lucassen http://contact.xaq.nl/
Re: Printer weirdness
On 12/30/23 16:25, Hans wrote: I will find either another solution, or my customer just has to deal with double names. So it is not a generally problem and this file can be closed. Which packages? What are the names of all the packages? (not 'for example' '*:pp') Hope this make things clearer. I believe that the Brother drivers script installs the Brother furnished driver for the printer model. The cups/debian software scans for printers when booted and initiated therefore giving you the second printer as the scan determines it to be. HTH Eddie
Re: Printer weirdness
On Sat, Dec 30, 2023 at 10:25:27PM +0100, Hans wrote: > Sorry, did I impress myself so wrong? > > What I meant, were the packages for the driver, which Brother provide. > > If you want to know, take a look at support.brother.com, see which I mean. Someone else going to a web site today is NOT necessarily going to figure out what version of what package YOU got from a web site at some unknown point in the past. The web site may have changed. New versions of packages may be there. Different packages may be there. Packages may have been removed because the developers have ruled them obsolete, or because the managers have decided to charge money for them. We have no idea. Even if the web site hasn't changed since you went there, there might be more than one thing on the web site, and we wouldn't know which one you got. If you want people to be able to help you, it's in your best interest to be CLEAR about EXACTLY what you're using. You do that by telling us what it is -- its name, and its version number, if it has one. You do THAT by writing your email FROM THE DEBIAN SYSTEM on which you are having the problem -- or in the worst case, you write the email on the same system from which you have an ssh session to the Debian system, so that you can easily run commands and paste them and paste their output from the Debian system into the email you are writing. The most basic request for help with a printer should include: * Which version of Debian you're running. * What model of printer you're using. * How the printer is connected to the Debian system. * What printing software you're using on the Debian system. * What the problem is. (Show exact error messages if possible!)
Re: Printer weirdness
Am Samstag, 30. Dezember 2023, 21:32:01 CET schrieb debian- u...@howorth.org.uk: Sorry, did I impress myself so wrong? What I meant, were the packages for the driver, which Brother provide. If you want to know, take a look at support.brother.com, see which I mean. As I do not have the notebook here at the moment, i can not tell exactly, but the packages should not be the problem at all, as it is looking for me, that debian itself is also somehow naming the devices for itself and additionally. I guess, i will take a look for myself, when I get the notebook into my hands again. What my questions in the first mail were aimed for, if someone got into the same issue, too, or if in debian itself has something changed related to printers, as I know, some printers are natively supported by the debian repo itself (for example HP printers). So, as obviously no one knows, we can safely close this question. I will find either another solution, or my customer just has to deal with double names. So it is not a generally problem and this file can be closed. Thanks for the help either! Best wishes and a happy new year! Hans > To find out what model of printer it is look at the printer and see > what is printed on it! > > > The other question someone asked: > > > > The packages I mentioned I installed, were of course CUPS packages > > from the debian repo, as well as the needed packages supplied by > > Brother (which for example include the *:pp files). > > Which packages? What are the names of all the packages? (not 'for > example' '*:pp') > > > Hope this make things clearer. > > It's like dragging blood from a stone! > > > Best > > > > Hans
Re: Printer weirdness
Hans wrote: > Am Samstag, 30. Dezember 2023, 18:06:43 CET schrieb debian- > u...@howorth.org.uk: > > Hans wrote: > One is a Brother DCP-125j (connected via USB-cable), the other a > Brother MFC- L3750CDW (coonnected via LAN to thze router). > > The Notebook is connected via WIFI to the router. > > Both printers do NOT have WIFI. > > > > You'll probably get more help if you're more explicit about the > > configuration. You seem to be exceptionally coy! > > > > > > What version of debian? > Debian/stable > > > What specific printer models? > > See above. > > > Which printer is connected by USB? And which by LAN? > See above. > > > > > > For installation I am using CUPS and XSANE. > > > > > > Now to the issues: > > > > > > 1st question: > > > Although there are no printers configured in CUPS, LibreOffice > > > does see and can use the printers. My idea is, that Libreoffice > > > is using its owb printer drivers, can that be, does someone know > > > more? > > > > > > 2nd question: > > > When installed with CUPS, there appear TWO pronters, one (for > > > example) is called "DCP-125J" and the other one "DCP-125J_debian". > > > However, only one of the entries is working (the one without > > > "_debian". Where does it get its name? > > > > I'm guessing that the name you give is a typo? And it's actually > > DCP-J125 since that is the name of a Brother printer. And the > > obvious answer as to where it gets its name is from the printer > > driver for that printer. > > > > Dunno. The names appear twice, at each of one of them one name end > with the string "_debian" To find out what model of printer it is look at the printer and see what is printed on it! > The other question someone asked: > > The packages I mentioned I installed, were of course CUPS packages > from the debian repo, as well as the needed packages supplied by > Brother (which for example include the *:pp files). Which packages? What are the names of all the packages? (not 'for example' '*:pp') > Hope this make things clearer. It's like dragging blood from a stone! > Best > > Hans
Re: Bug on upgrade to bookworm with Apache/PHP?
On Sat, 30 Dec 2023 17:50:03 + Andrew Wood wrote: > Found the following issue when running an upgrade. > > Apache refuses to restart with error: > > apache2_reload: Your configuration is broken. Not restarting Apache 2 > apache2_reload: apache2: Syntax error on line 146 of > /etc/apache2/apache2.conf: Syntax error on line 3 of > /etc/apache2/mods-enabled/php7.4.load: Cannot load > /usr/lib/apache2/modules/libphp7.4.so into server: > /usr/lib/apache2/modules/libphp7.4.so: cannot open shared object > file: No such file or directory > > > This is because the php7.4 files have now been replaced with php8.2 > > Specifically sym linsk in /etc/apache2/mods-enabled/ which link to > /etc/apache2/mods-available/ > php7.4.conf -> ../mods-available/php7.4.conf > php7.4.load -> ../mods-available/php7.4.load > > Should be removed and replaced with a link to > > php8.2.conf -> ../mods-available/php8.2.conf > php8.2.load -> ../mods-available/php8.2.load > > > Is this known about? > > Andrew > You might want to disable any php 7.4 modules and enable php8.2.conf and php8.2.load. root@hawk:/etc/apache2# ls mods-enabled/ access_compat.load autoindex.load mpm_prefork.conf setenvif.load alias.conf deflate.confmpm_prefork.load socache_shmcb.load alias.load deflate.loadnegotiation.conf ssl.conf auth_basic.load dir.confnegotiation.load ssl.load authn_core.load dir.loadphp8.2.conf status.conf authn_file.load env.loadphp8.2.load status.load authz_core.load filter.load reqtimeout.conf userdir.conf authz_host.load headers.loadreqtimeout.load userdir.load authz_user.load mime.conf rewrite.load autoindex.conf mime.load setenvif.conf root@hawk:/etc/apache2# -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: is there an ntpsec wizard here?
On 12/30/23 13:40, Greg Wooledge wrote: On Sat, Dec 30, 2023 at 12:19:12PM -0500, gene heskett wrote: synopsis phase one: I have installed ntpsec on this, my main machine, What is its *name*? fqdn:coyote.coyote.den but see my post from a few minutes back Greg, I found it and its now working. Apparently THAT copy of ntpsec was built to do nothing w/o 4 named peers in ntp.conf. So 3 of them are debian pool members. Synopsis phase two: A QIDI X MAX-3 3d printer with a rockchip64 running armbian 22.05 (buster) as the klipper, moonraker, and fluidd web interface to control this printer. But its clock is wrong by about an hour 45 minutes and short of trying to figure out settime, which might get it within 30 seconds at best, I need to make nptsec behave like the long since deprecated ntpdate command which could slam the current timedate into the clock regardless, harmless if done in early boot but I'm told can be dangerous to a running kernel. I'm confused by "phase two". Is ntpsec installed on the printer? Or is it ntp? Or chrony? Or systemd-timesyncd? Or none of the above? ntpsec on the printer, there were traces of the other two but they are stopped and disabled now. If all you want to do is set the clock manually, you can use the "date" command. Or you could install and use "ntpdate" or "rdate". But that's a band-aid. If you want to *keep* the clock in sync, then you need to get one of the NTP packages up and running, or if it's already running, figure out why it failed. The why clue was grudgingly disclosed by ntptrace which admitted to using itself as a server, statum 16, which may as well have been on the back side of the moon... Let's set one thing straight immediately: changing the clock isn't "dangerous to a kernel". The kernel really does not care about it at all. Other programs *might* care. Things like cron are pretty obvious -- if there's a scheduled job that's supposed to run at 2:00, but 2:00 never happens because you jumped over it, then the cron job might not run. Or if 2:00 happens twice, then the job may run twice. Desktop environments may also care. If the clock jumps forward, then a screen saver might kick in. Or other weird things might happen. Log files will look weird. The latter is expected. And as you say, harmless for a fwd jump . Now its new years eve, and I need a box of self tapping 3/4" screws so I can get back to work on a new table for this printer, One with storage drawers for 16 kg of filament, but now I'm napping till Tuesday, everybody has the weekend off. Software development tools may also be affected, especially if a clock goes backward. Things like "make" compare modtimes on files to see which source files need to be recompiled. If the timestamps are messed up, then things may be recompiled unnecessarily, or worse, may *not* be recompiled when they should be. I have no idea what's running on your printer which might be sensitive to the system clock. That's for you to figure out. Absolutely. Thanks Greg & have a happier new year, the last 3 have sucked about 10-34 torr. root@mkspi:/usr/share# systemctl status ntpsec.service Which machine is "mkspi"? Is that the printer? Or is that the ntpsec server? Thats the printer. Active: active (running) since Sat 2023-12-30 09:26:32 EST; 43min ago If this is the printer (client) ... did you reboot it? Or did you try to restart ntpsec manually, at a time when the clock was already very wrong? Manually and with systemdctl, at least 40 times. I don't know the changes in ntpsec yet, but in the classic ntp package, it was only allowed to make a large clock adjustment *one* time, when first starting up during boot. Any subsequent restarts would only try to adjust the clock gradually. If you can't reboot the printer, then what you should do is stop the NTP program (ntpsec or whichever it is), set the clock by hand using "date" (or even "rdate" or "ntpdate"), then restart the NTP program. Ideally you would also ensure that any time-sensitive programs are stopped, and then restart them after the clock has been fixed. In practice, it might be better/easier just to reboot it. Of course, this will depend on the NTP program being able to reach your ntpsec server during boot, and set the clock at that moment. If THAT'S failing for some reason, then you'll need to figure out why. Yup. Take care and stay warm and well, Greg. Even if it turns out to be pebkamc (m meaning my chair) I appreciate it. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: is there an ntpsec wizard here?
On 12/30/23 12:19, gene heskett wrote: synopsis phase one: I have installed ntpsec on this, my main machine, and have successfully switched 5 of my other networked machines to use this statum 2 server instead of pestering the debian server pool. However, I have it restricted to replying only to members of my private network. Synopsis phase two: A QIDI X MAX-3 3d printer with a rockchip64 running armbian 22.05 (buster) as the klipper, moonraker, and fluidd web interface to control this printer. But its clock is wrong by about an hour 45 minutes and short of trying to figure out settime, which might get it within 30 seconds at best, I need to make nptsec behave like the long since deprecated ntpdate command which could slam the current timedate into the clock regardless, harmless if done in early boot but I'm told can be dangerous to a running kernel. Now I need to get far more familiar with systemd than I am. For those of you using ntpsec, and it is generating the proper logs in /var/log/ntpsec, I need to see how you have accomplished this in your /etc/ntpsec/ntp.conf, enabling the logging of everything it does, I'm getting nothing here in that properly configured path, and /lib/ntpsec/ntp,drift is stuck at 00.0. While: root@mkspi:/usr/share# systemctl status ntpsec.service ● ntpsec.service - Network Time Service Loaded: loaded (/lib/systemd/system/ntpsec.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2023-12-30 09:26:32 EST; 43min ago Docs: man:ntpd(8) Process: 15642 ExecStart=/usr/lib/ntp/ntp-systemd-wrapper (code=exited, status=0/SUCCESS) Main PID: 15645 (ntpd) Tasks: 1 (limit: 998) Memory: 9.0M CGroup: /system.slice/ntpsec.service └─15645 /usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec Dec 30 10:00:41 mkspi ntpd[15645]: DNS: Pool skipping: 192.168.71.3 Dec 30 10:00:41 mkspi ntpd[15645]: DNS: dns_take_status: coyote.coyote.den=>good, 8 Dec 30 10:04:57 mkspi ntpd[15645]: DNS: dns_probe: coyote.coyote.den, cast_flags:8, flags:101 Dec 30 10:04:57 mkspi ntpd[15645]: DNS: dns_check: processing coyote.coyote.den, 8, 101 Dec 30 10:04:57 mkspi ntpd[15645]: DNS: Pool skipping: 192.168.71.3 Dec 30 10:04:57 mkspi ntpd[15645]: DNS: dns_take_status: coyote.coyote.den=>good, 8 Dec 30 10:09:13 mkspi ntpd[15645]: DNS: dns_probe: coyote.coyote.den, cast_flags:8, flags:101 Dec 30 10:09:13 mkspi ntpd[15645]: DNS: dns_check: processing coyote.coyote.den, 8, 101 Dec 30 10:09:13 mkspi ntpd[15645]: DNS: Pool skipping: 192.168.71.3 Dec 30 10:09:13 mkspi ntpd[15645]: DNS: dns_take_status: coyote.coyote.den=>good, 8 root@mkspi:/usr/share# Which to me looks like it ought to be working but is obviously not working. Capturing my ntpsec server traffic on port 123 shows mmkspi is accessing the server and the server is responding at several minute intervals: 11:48:15.267912 IP mkspi.coyote.den.ntp > coyote.coyote.den.ntp: NTPv4, Client, length 48 11:49:21.274706 IP coyote.coyote.den.ntp > mkspi.coyote.den.ntp: NTPv4, Server, length 48 11:50:26.267614 IP mkspi.coyote.den.ntp > coyote.coyote.den.ntp: NTPv4, Client, length 48 11:50:26.267681 IP coyote.coyote.den.ntp > mkspi.coyote.den.ntp: NTPv4, Server, length 48 But the date 45 seconds later on mkspi is: Sat 30 Dec 2023 10:24:10 AM EST I have used systemctl to stop and disable both timesyncd.service and chrony.service since neither seems to want to access my ntpsec server. Acc the docs I've read, all 3 of these utilities s/b able to do the job. And I'm lost w/o any info to debug this, no log files at all. Those log file locations are NOT on my raid that is being so d_d cantankerous. My thanks to anyone who can help. Call in the St. Bernards, tap the cask, and have a happy new year, I found it, it jumped over 6000 seconds and the date output is now correct. And it did not crash the printer. I'm a happy camper. Cheers, Gene Heskett. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: Bug on upgrade to bookworm with Apache/PHP?
Andrew Wood wrote: > This is because the php7.4 files have now been replaced with php8.2 > > Specifically sym linsk in /etc/apache2/mods-enabled/ which link to > /etc/apache2/mods-available/ > php7.4.conf -> ../mods-available/php7.4.conf > php7.4.load -> ../mods-available/php7.4.load > > Should be removed and replaced with a link to > > php8.2.conf -> ../mods-available/php8.2.conf > php8.2.load -> ../mods-available/php8.2.load > > > Is this known about? Yes. It is not an error, per se, because it is possible that a person would want to keep the php7 system around a bit longer, and not yet install the php8 system. It is just part of the decisions that a sysadmin has to make for their systems. -dsr-
Re: is there an ntpsec wizard here?
On Sat, Dec 30, 2023 at 12:19:12PM -0500, gene heskett wrote: > synopsis phase one: > I have installed ntpsec on this, my main machine, What is its *name*? > Synopsis phase two: A QIDI X MAX-3 3d printer with a rockchip64 running > armbian 22.05 (buster) as the klipper, moonraker, and fluidd web interface > to control this printer. But its clock is wrong by about an hour 45 minutes > and short of trying to figure out settime, which might get it within 30 > seconds at best, I need to make nptsec behave like the long since deprecated > ntpdate command which could slam the current timedate into the clock > regardless, harmless if done in early boot but I'm told can be dangerous to > a running kernel. I'm confused by "phase two". Is ntpsec installed on the printer? Or is it ntp? Or chrony? Or systemd-timesyncd? Or none of the above? If all you want to do is set the clock manually, you can use the "date" command. Or you could install and use "ntpdate" or "rdate". But that's a band-aid. If you want to *keep* the clock in sync, then you need to get one of the NTP packages up and running, or if it's already running, figure out why it failed. Let's set one thing straight immediately: changing the clock isn't "dangerous to a kernel". The kernel really does not care about it at all. Other programs *might* care. Things like cron are pretty obvious -- if there's a scheduled job that's supposed to run at 2:00, but 2:00 never happens because you jumped over it, then the cron job might not run. Or if 2:00 happens twice, then the job may run twice. Desktop environments may also care. If the clock jumps forward, then a screen saver might kick in. Or other weird things might happen. Log files will look weird. Software development tools may also be affected, especially if a clock goes backward. Things like "make" compare modtimes on files to see which source files need to be recompiled. If the timestamps are messed up, then things may be recompiled unnecessarily, or worse, may *not* be recompiled when they should be. I have no idea what's running on your printer which might be sensitive to the system clock. That's for you to figure out. > root@mkspi:/usr/share# systemctl status ntpsec.service Which machine is "mkspi"? Is that the printer? Or is that the ntpsec server? >Active: active (running) since Sat 2023-12-30 09:26:32 EST; 43min ago If this is the printer (client) ... did you reboot it? Or did you try to restart ntpsec manually, at a time when the clock was already very wrong? I don't know the changes in ntpsec yet, but in the classic ntp package, it was only allowed to make a large clock adjustment *one* time, when first starting up during boot. Any subsequent restarts would only try to adjust the clock gradually. If you can't reboot the printer, then what you should do is stop the NTP program (ntpsec or whichever it is), set the clock by hand using "date" (or even "rdate" or "ntpdate"), then restart the NTP program. Ideally you would also ensure that any time-sensitive programs are stopped, and then restart them after the clock has been fixed. In practice, it might be better/easier just to reboot it. Of course, this will depend on the NTP program being able to reach your ntpsec server during boot, and set the clock at that moment. If THAT'S failing for some reason, then you'll need to figure out why.
Re: Printer weirdness
Am Samstag, 30. Dezember 2023, 18:06:43 CET schrieb debian- u...@howorth.org.uk: > Hans wrote: One is a Brother DCP-125j (connected via USB-cable), the other a Brother MFC- L3750CDW (coonnected via LAN to thze router). The Notebook is connected via WIFI to the router. Both printers do NOT have WIFI. > You'll probably get more help if you're more explicit about the > configuration. You seem to be exceptionally coy! > > What version of debian? Debian/stable > What specific printer models? See above. > Which printer is connected by USB? And which by LAN? See above. > > > For installation I am using CUPS and XSANE. > > > > Now to the issues: > > > > 1st question: > > Although there are no printers configured in CUPS, LibreOffice does > > see and can use the printers. My idea is, that Libreoffice is using > > its owb printer drivers, can that be, does someone know more? > > > > 2nd question: > > When installed with CUPS, there appear TWO pronters, one (for > > example) is called "DCP-125J" and the other one "DCP-125J_debian". > > However, only one of the entries is working (the one without > > "_debian". Where does it get its name? > > I'm guessing that the name you give is a typo? And it's actually > DCP-J125 since that is the name of a Brother printer. And the obvious > answer as to where it gets its name is from the printer driver for that > printer. > Dunno. The names appear twice, at each of one of them one name end with the string "_debian" The other question someone asked: The packages I mentioned I installed, were of course CUPS packages from the debian repo, as well as the needed packages supplied by Brother (which for example include the *:pp files). Hope this make things clearer. Best Hans
Bug on upgrade to bookworm with Apache/PHP?
Found the following issue when running an upgrade. Apache refuses to restart with error: apache2_reload: Your configuration is broken. Not restarting Apache 2 apache2_reload: apache2: Syntax error on line 146 of /etc/apache2/apache2.conf: Syntax error on line 3 of /etc/apache2/mods-enabled/php7.4.load: Cannot load /usr/lib/apache2/modules/libphp7.4.so into server: /usr/lib/apache2/modules/libphp7.4.so: cannot open shared object file: No such file or directory This is because the php7.4 files have now been replaced with php8.2 Specifically sym linsk in /etc/apache2/mods-enabled/ which link to /etc/apache2/mods-available/ php7.4.conf -> ../mods-available/php7.4.conf php7.4.load -> ../mods-available/php7.4.load Should be removed and replaced with a link to php8.2.conf -> ../mods-available/php8.2.conf php8.2.load -> ../mods-available/php8.2.load Is this known about? Andrew
is there an ntpsec wizard here?
synopsis phase one: I have installed ntpsec on this, my main machine, and have successfully switched 5 of my other networked machines to use this statum 2 server instead of pestering the debian server pool. However, I have it restricted to replying only to members of my private network. Synopsis phase two: A QIDI X MAX-3 3d printer with a rockchip64 running armbian 22.05 (buster) as the klipper, moonraker, and fluidd web interface to control this printer. But its clock is wrong by about an hour 45 minutes and short of trying to figure out settime, which might get it within 30 seconds at best, I need to make nptsec behave like the long since deprecated ntpdate command which could slam the current timedate into the clock regardless, harmless if done in early boot but I'm told can be dangerous to a running kernel. Now I need to get far more familiar with systemd than I am. For those of you using ntpsec, and it is generating the proper logs in /var/log/ntpsec, I need to see how you have accomplished this in your /etc/ntpsec/ntp.conf, enabling the logging of everything it does, I'm getting nothing here in that properly configured path, and /lib/ntpsec/ntp,drift is stuck at 00.0. While: root@mkspi:/usr/share# systemctl status ntpsec.service ● ntpsec.service - Network Time Service Loaded: loaded (/lib/systemd/system/ntpsec.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2023-12-30 09:26:32 EST; 43min ago Docs: man:ntpd(8) Process: 15642 ExecStart=/usr/lib/ntp/ntp-systemd-wrapper (code=exited, status=0/SUCCESS) Main PID: 15645 (ntpd) Tasks: 1 (limit: 998) Memory: 9.0M CGroup: /system.slice/ntpsec.service └─15645 /usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec Dec 30 10:00:41 mkspi ntpd[15645]: DNS: Pool skipping: 192.168.71.3 Dec 30 10:00:41 mkspi ntpd[15645]: DNS: dns_take_status: coyote.coyote.den=>good, 8 Dec 30 10:04:57 mkspi ntpd[15645]: DNS: dns_probe: coyote.coyote.den, cast_flags:8, flags:101 Dec 30 10:04:57 mkspi ntpd[15645]: DNS: dns_check: processing coyote.coyote.den, 8, 101 Dec 30 10:04:57 mkspi ntpd[15645]: DNS: Pool skipping: 192.168.71.3 Dec 30 10:04:57 mkspi ntpd[15645]: DNS: dns_take_status: coyote.coyote.den=>good, 8 Dec 30 10:09:13 mkspi ntpd[15645]: DNS: dns_probe: coyote.coyote.den, cast_flags:8, flags:101 Dec 30 10:09:13 mkspi ntpd[15645]: DNS: dns_check: processing coyote.coyote.den, 8, 101 Dec 30 10:09:13 mkspi ntpd[15645]: DNS: Pool skipping: 192.168.71.3 Dec 30 10:09:13 mkspi ntpd[15645]: DNS: dns_take_status: coyote.coyote.den=>good, 8 root@mkspi:/usr/share# Which to me looks like it ought to be working but is obviously not working. Capturing my ntpsec server traffic on port 123 shows mmkspi is accessing the server and the server is responding at several minute intervals: 11:48:15.267912 IP mkspi.coyote.den.ntp > coyote.coyote.den.ntp: NTPv4, Client, length 48 11:49:21.274706 IP coyote.coyote.den.ntp > mkspi.coyote.den.ntp: NTPv4, Server, length 48 11:50:26.267614 IP mkspi.coyote.den.ntp > coyote.coyote.den.ntp: NTPv4, Client, length 48 11:50:26.267681 IP coyote.coyote.den.ntp > mkspi.coyote.den.ntp: NTPv4, Server, length 48 But the date 45 seconds later on mkspi is: Sat 30 Dec 2023 10:24:10 AM EST I have used systemctl to stop and disable both timesyncd.service and chrony.service since neither seems to want to access my ntpsec server. Acc the docs I've read, all 3 of these utilities s/b able to do the job. And I'm lost w/o any info to debug this, no log files at all. Those log file locations are NOT on my raid that is being so d_d cantankerous. My thanks to anyone who can help. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: Printer weirdness
Hans wrote: > Hi folks, > > I am looking for an explanation of a strange effect. > > The issue: > I have a customer, who is using debian and has connected two printers > (one of them with an integrated scanner and LAN, the other via > USB-cable). You'll probably get more help if you're more explicit about the configuration. You seem to be exceptionally coy! What version of debian? What specific printer models? Which printer is connected by USB? And which by LAN? > For installation I am using CUPS and XSANE. > > Now to the issues: > > 1st question: > Although there are no printers configured in CUPS, LibreOffice does > see and can use the printers. My idea is, that Libreoffice is using > its owb printer drivers, can that be, does someone know more? > > 2nd question: > When installed with CUPS, there appear TWO pronters, one (for > example) is called "DCP-125J" and the other one "DCP-125J_debian". > However, only one of the entries is working (the one without > "_debian". Where does it get its name? I'm guessing that the name you give is a typo? And it's actually DCP-J125 since that is the name of a Brother printer. And the obvious answer as to where it gets its name is from the printer driver for that printer. > Both printers appear also in > CUPS, but they do NOT appear in the printer sections of the > "systemsettings" in KDE. > > So, when connected TWO printers, the user has to choose of FOUR > entries. > > How can that be fixed, ifat all? > > > 3rd question: > The same appears with the scanner. When I start XSANE, then I get > FOUR entries to chose: one name ending with the IP-addresse (the > scanner is connected by LAN) marked, one without IP, one starting > with the string "ecl:" and one starting with "ipp:". Whilst > two of them I can explain myself, only two of the entries are > working, the one starting "ecl:" and the pone with the IP. > > The IPP-entry is clear for me, it is for internet printing, but last > one is NOT explainable and is lookinbg for me as an unnecessary > double entry like it appears at the printers. > > How can I fix this? > > > Additionally I should tell, the printers and scanner are both from > Brother, who offers driver packages for the devices on his website > for debian. > > Alls needed packages are installed. Which specific packages are installed? > However, I could not find out, that debian supports Brother printers > and scanners natively, so I need to install their packages. > > This was all the time that way. Or did debian change something > related to printers and scanners during the last year? Then please > let me know, what I might have missed. > > Thank you very much for feedback, and also for all the help and hard > work during all the time!!! > > Happy new year!!! > > Best > > Hans
Re: Printer weirdness
On Sat, 30 Dec 2023 13:02:28 +0100 Hans wrote: > 1st question: > Although there are no printers configured in CUPS, LibreOffice does > see and can use the printers. My idea is, that Libreoffice is using > its owb printer drivers, can that be, does someone know more? > > 2nd question: > When installed with CUPS, there appear TWO pronters, one (for > example) is called "DCP-125J" and the other one "DCP-125J_debian". > However, only one of the entries is working (the one without > "_debian". Where does it get its name? Both printers appear also in > CUPS, but they do NOT appear in the printer sections of the > "systemsettings" in KDE. > > So, when connected TWO printers, the user has to choose of FOUR > entries. > > How can that be fixed, ifat all? > > > 3rd question: > The same appears with the scanner. When I start XSANE, then I get > FOUR entries to chose: one name ending with the IP-addresse (the > scanner is connected by LAN) marked, one without IP, one starting > with the string "ecl:" and one starting with "ipp:". Whilst > two of them I can explain myself, only two of the entries are > working, the one starting "ecl:" and the pone with the IP. > > The IPP-entry is clear for me, it is for internet printing, but last > one is NOT explainable and is lookinbg for me as an unnecessary > double entry like it appears at the printers. > > How can I fix this? I suspect that your customer's printers are so-called "driverless" printers, and that they are advertising themselves via Apple's Bonjour protocol, implemented in Linux by the avahi packages. If so, you can see what avahi has found with: avahi-browse -art or avahi-discover. If that is correct, I wouldn't worry about the duplicate entries for the printers. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
tecles mortes en aplicacions GTK
Hola, Des de l'actualització a Bookworm, les tecles mortes (accents i dièresi) generen una previsualització, que posteriorment desapareix quan la tecla morta es combina amb el caràcter següent. En algunes pàgines web, com Reddit, crea problemes. Si preferiu tornar al comportament anterior, es pot aconseguir establint la següent variable d'entorn GTK_IM_MODULE=xim (Cal re-iniciar la sessió de l'usuari després de modificar l'entorn.) Salutacions
Re: [HS] Lilo (et Grub)
On Friday 29 December 2023 09:33:52 Pierre Malard wrote: > Personnellement toutes mes VM tournent sous formatage GPT et sans UEFI mais > cela ne fait pas de différences. Effectivement il suffit d?une petite > partition au début d?environ 1 Mo non formatée mais avec le flag > « bios-grub ». > Pour mettre jour le boot, voici ce que je fais alors : > # update-grub > # grub-install --modules=part_gpt /dev/sda : Hélas, ça ne marche pas, toujours le message : "Erreur, /boot/vmlinuz-5.10.0-21-amd64 non disponible, le noyau doit d'abord être chargé". > Si on utilise UEFI il faut juste ajouter une partition VFAT > montée sur le répertoire /boot/efi : Pas de répertoire ou fichier "efi" dans /boot. > Coiffé au poteau : > Périphérique Début Fin Secteurs Taille Type > /dev/sdb1 2048 4095 2048 1M Amorçage BIOS > Problème : à partir d'un disque déjà paritionné ça suppose de décaler > le début de l'actuelle première partition d'1M ... > Faisable avec gparted je pense : Comment fait-on pour décaler le début de l'actuelle partition d'IM ? gparted ne propose pas de modifier l'étiquette en msdos, c'est fdisk : Créer une nouvelle étiquette : g créer une nouvelle table vide de partitions GPT o create a new empty MBR (DOS) partition table. Voilà le topo.
Re: Printer weirdness
On 30 Dec 2023 13:02 +0100, from hans.ullr...@loop.de (Hans): > 1st question: > Although there are no printers configured in CUPS, LibreOffice does see and > can use the > printers. My idea is, that Libreoffice is using its owb printer drivers, can > that be, does someone > know more? > > 2nd question: > When installed with CUPS, there appear TWO pronters, one (for example) is > called "DCP-125J" > and the other one "DCP-125J_debian". However, only one of the entries is > working (the one > without "_debian". Where does it get its name? Both printers appear also in > CUPS, but they do > NOT appear in the printer sections of the "systemsettings" in KDE. > > So, when connected TWO printers, the user has to choose of FOUR entries. > > How can that be fixed, ifat all? In LibreOffice, check File > Printer Settings. What does "Type" indicate for each? Also, I would suggest to double-check whether the version of LibreOffice installed and actually in use is the one packaged by Debian. I have a fairly similar setup with a network-connected printer configured in CUPS, and can quite confidently say that I have never seen any behavior in LibreOffice similar to that which you describe. That's with LibreOffice currently at 7.4.7.2 (4:7.4.7-1+deb12u1). -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Printer weirdness
Hi folks, I am looking for an explanation of a strange effect. The issue: I have a customer, who is using debian and has connected two printers (one of them with an integrated scanner and LAN, the other via USB-cable). For installation I am using CUPS and XSANE. Now to the issues: 1st question: Although there are no printers configured in CUPS, LibreOffice does see and can use the printers. My idea is, that Libreoffice is using its owb printer drivers, can that be, does someone know more? 2nd question: When installed with CUPS, there appear TWO pronters, one (for example) is called "DCP-125J" and the other one "DCP-125J_debian". However, only one of the entries is working (the one without "_debian". Where does it get its name? Both printers appear also in CUPS, but they do NOT appear in the printer sections of the "systemsettings" in KDE. So, when connected TWO printers, the user has to choose of FOUR entries. How can that be fixed, ifat all? 3rd question: The same appears with the scanner. When I start XSANE, then I get FOUR entries to chose: one name ending with the IP-addresse (the scanner is connected by LAN) marked, one without IP, one starting with the string "ecl:" and one starting with "ipp:". Whilst two of them I can explain myself, only two of the entries are working, the one starting "ecl:" and the pone with the IP. The IPP-entry is clear for me, it is for internet printing, but last one is NOT explainable and is lookinbg for me as an unnecessary double entry like it appears at the printers. How can I fix this? Additionally I should tell, the printers and scanner are both from Brother, who offers driver packages for the devices on his website for debian. Alls needed packages are installed. However, I could not find out, that debian supports Brother printers and scanners natively, so I need to install their packages. This was all the time that way. Or did debian change something related to printers and scanners during the last year? Then please let me know, what I might have missed. Thank you very much for feedback, and also for all the help and hard work during all the time!!! Happy new year!!! Best Hans
Re: Possibly broken Grub or initrd after updates on Testing
On 29 Dec 2023 23:29 +0100, from rich...@rosner-online.de (Richard Rosner): > For a fraction of a second it shows something about slot 0 open, that's it. Well, that means that GRUB at least succeeds in opening the LUKS container. That's good; it means that we can rule out that part of the chain as the cause of your problems, as well as everything before it. I still don't have any good idea what might cause GRUB to simply reboot, though. Normally, if there is a critical problem, GRUB will drop you to a built-in Unix-esque command-line interface with a "grub>" prompt. You do mention that you regenerated the initrd, but the initrd doesn't really figure into GRUB; it comes into play after the kernel is loaded into memory, which itself happens past the boot menu which you don't get to. I know it likely won't point you toward what the actual problem is, but I would suggest booting off live media (a Debian installer written to a USB stick and running in rescue mode should do), unlock/mount/chroot/shell into your root file system, and run `grub-install -v --no-nvram --recheck` (possibly with additional parameters; see grub-install(8) for details) from there to reinstall the boot loader itself. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: wegvallen / uitvallen van IPv6
On 29 December 2023 22:02 Richard Lucassen, wrote: > On Fri, 29 Dec 2023 10:57:54 +0100 > Geert Stappers wrote: > >> > Misschien dat je router advertisements op 546/udp niet accepteert? >> > >> > iptables -A INPUT -s fe80::/10 -p udp --dport 546 -j ACCEPT >> > >> > Ik roep maar wat hoor. >> >> Die aanvulling zou aanleiding moeten zijn >> om het bericht (met kletskoek) niet te versturen. > > Lees het eens anders: > > dat je router advertisements op 546/udp niet accepteert? > > "je" is het onderwerp, "je router" is dat niet. 't Is wat onduidelijk > inderdaad. Wellicht was diet beter geweest: > > dat je router-advertisements op 546/udp niet accepteert? > > Als je Linuxdoos achter een router die SLAAC doet die pakketten > weggooit krijg je dit soort problemen. Oh, dank! Dat is een richting waar ik naar ga kijken. Het is een mesh wifi netwerk, een maand terug hier neergezet door Proximus. Twee repeaters verbonden met een internetbox die met een ethernet kabel verbonden is met een router, die aan de fiber hangt. En in sommige hoeken valt IPv6 om. (Zal je net zien: het is nu alweer een paar dagen niet voorgekomen. Ik had het eerder op deze lijst moeten melden :-) ) Dank!
