Re: Unable to locate printer "HOSTNAME.local", help with troubleshooting CUPS and mDNS once and for all

2025-06-17 Thread Lee
1 3600 1200 604800 10800 > ``` > > Not sure what to make of that as I don't really understand the point and I'm guessing [whoever did this] is trying not to stomp all over people/orgs that are using the local. domain in DNS _and_ prevent xxx.local. name lookups from hitting t

Re: Unable to locate printer "HOSTNAME.local", help with troubleshooting CUPS and mDNS once and for all

2025-06-16 Thread Teemu Likonen
* 2025-06-16 00:31:48+0200, Uroš Mikanovič wrote: > I can't get my network discovered printer to print. CUPS finds and adds > my printer easily with "Find New Printers" on the web interface. But > every job fails with: > Unable to locate printer "BRNBCF4D4182ECD.local". That reminds me of issu

Re: Unable to locate printer "HOSTNAME.local", help with troubleshooting CUPS and mDNS once and for all

2025-06-16 Thread Max Nikulin
On 17/06/2025 00:03, Uroš Mikanovič wrote: `host -t SOA local` returns: local has SOA record local. nobody.invalid. 1 3600 1200 604800 10800 It is either from your router or from your ISP. Try to add an ISP DNS server address to the "host" command. You may try to adjust dnsmasq configuration

Re: Unable to locate printer "HOSTNAME.local", help with troubleshooting CUPS and mDNS once and for all

2025-06-16 Thread Uroš Mikanovič
Thanks for the tips, I figured something out. Seems like mdns4_minimal is "shy". In the case of the "minimal" version of `nss-mdns`, from the README: > * If the request does not end with `.local` or `.local.`, it is > rejected. Example: `example.test` is rejected. > > * If the request has more

Re: Unable to locate printer "HOSTNAME.local", help with troubleshooting CUPS and mDNS once and for all

2025-06-15 Thread Max Nikulin
On 16/06/2025 05:31, Uroš Mikanovič wrote: hosts: files mdns4_minimal [NOTFOUND=return] dns [...] `ping` can't resolve `BRNBCF4D4182ECD.local`, not sure if it's supposed to. It should (while host, dig, nslookup, and other DNS tools shouldn't). However a more direct test for libc res

Unable to locate printer "HOSTNAME.local", help with troubleshooting CUPS and mDNS once and for all

2025-06-15 Thread Uroš Mikanovič
Hi, I can't get my network discovered printer to print. CUPS finds and adds my printer easily with "Find New Printers" on the web interface. But every job fails with: ``` Unable to locate printer "BRNBCF4D4182ECD.local". ``` While researching this problem I came across other people having tr

congratulations for all debian developers

2025-06-02 Thread Mgr. Janusz Chmiel
, that he or she has installed professional operating system. Which is tuned and stable beginning from The kernel and ending with provided and prepared Debian packages. I would also like to congratulate all Debian kernel developers. Because your work is very important. Without your exhaustive and

Re: route all traffic to a internal socket

2025-05-01 Thread Dan Ritter
Mohsen Pahlevanzadeh wrote: > I don't want to use set proxy in firefox and other application, but > I want to send any packets to 127.0.0.1: and my program itself > send to eth0. > > OK, there is an underlying assumption that you are not telling > us. > > Why do you want to do

Re: route all traffic to a internal socket

2025-05-01 Thread Tim Woodall
On Thu, 1 May 2025, Tim Woodall wrote: On Wed, 30 Apr 2025, Mohsen Pahlevanzadeh wrote: On 4/30/25 4:29 PM, Jonathan Dowland wrote: On Wed Apr 30, 2025 at 10:19 AM BST, Mohsen Pahlevanzadeh wrote: I want to send any packet to 127.0.0.1: and it sends my packets to internet. my outgoing i

Re: route all traffic to a internal socket

2025-04-30 Thread Mohsen Pahlevanzadeh
On 4/30/25 11:47 PM, Dan Ritter wrote: Mohsen Pahlevanzadeh wrote: On 4/30/25 4:29 PM, Jonathan Dowland wrote: On Wed Apr 30, 2025 at 10:19 AM BST, Mohsen Pahlevanzadeh wrote: I want to send any packet to 127.0.0.1: and it se

Re: route all traffic to a internal socket

2025-04-30 Thread Tim Woodall
On Wed, 30 Apr 2025, Mohsen Pahlevanzadeh wrote: On 4/30/25 4:29 PM, Jonathan Dowland wrote: On Wed Apr 30, 2025 at 10:19 AM BST, Mohsen Pahlevanzadeh wrote: I want to send any packet to 127.0.0.1: and it sends my packets to internet. my outgoing interface is eth0. You can use socat? to

Re: route all traffic to a internal socket

2025-04-30 Thread Dan Ritter
Mohsen Pahlevanzadeh wrote: >On 4/30/25 4:29 PM, Jonathan Dowland wrote: > > On Wed Apr 30, 2025 at 10:19 AM BST, Mohsen Pahlevanzadeh wrote: > > I want to send any packet to 127.0.0.1: and it sends my packets > to internet. my outgoing interface is eth0. > > You can

Re: route all traffic to a internal socket

2025-04-30 Thread Mohsen Pahlevanzadeh
outgoing interface is eth0. You need to set up a virtual network interface, using /dev/net/tun, and configure it to be the default route. Do you know any documentation? Then you will have to encapsulate all you get from /dev/net/tun into a packet for your program

Re: route all traffic to a internal socket

2025-04-30 Thread Mohsen Pahlevanzadeh
On 4/30/25 4:29 PM, Jonathan Dowland wrote: On Wed Apr 30, 2025 at 10:19 AM BST, Mohsen Pahlevanzadeh wrote: I want to send any packet to 127.0.0.1: and it sends my packets to internet. my outgoing interface is eth0.

Re: route all traffic to a internal socket

2025-04-30 Thread Mohsen Pahlevanzadeh
On 4/30/25 4:29 PM, Jonathan Dowland wrote: On Wed Apr 30, 2025 at 10:19 AM BST, Mohsen Pahlevanzadeh wrote: I want to send any packet to 127.0.0.1: and it sends my packets to internet. my outgoing interface is eth0. You can use socat¹ to listen on a port and forward received packets el

Re: route all traffic to a internal socket

2025-04-30 Thread Jonathan Dowland
On Wed Apr 30, 2025 at 10:19 AM BST, Mohsen Pahlevanzadeh wrote: I want to send any packet to 127.0.0.1: and it sends my packets to internet. my outgoing interface is eth0. You can use socat¹ to listen on a port and forward received packets elsewhere. But… I don't want to use set proxy i

Re: route all traffic to a internal socket

2025-04-30 Thread Nicolas George
ing /dev/net/tun, and configure it to be the default route. Then you will have to encapsulate all you get from /dev/net/tun into a packet for your program listening on 127.0.0.1:7777 to attach all the headers that do not fit into UDP or TCP. But at this point you might as well realize that your ini

route all traffic to a internal socket

2025-04-30 Thread Mohsen Pahlevanzadeh
Dear all, I have a debian machine and my program listen to such as: 127.0.0.1 I want to send any packet to 127.0.0.1: and it sends my packets to internet. my outgoing interface is eth0. I don't want to use set proxy in firefox and other application, but I want to send any pa

Re: Kernel not upgrading in all systems

2025-03-15 Thread Gary Dale
On 2025-02-27 15:59, Gary Dale wrote: On 2025-02-14 22:00, Michael Stone wrote: On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote: All 3 systems have the linux-image-amd64 metapackage installed. What does apt show -a linux-image-amd64 | grep -e Version -e Sources -e Depends return

Re: Kernel not upgrading in all systems

2025-03-15 Thread David Wright
> > > On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote: > > > > All 3 systems have the linux-image-amd64 metapackage installed. On Sat 15 Mar 2025 at 10:44:40 (-0400), Gary Dale wrote: > After today's upgrades, I note that RM1 showed these autoremove >

Re: Thank you all

2025-03-08 Thread 🦓
2025-03-08[Sat]11:54 Runamile🦓Czyborra read that 2025-03-07[Fri]15:33 Maureen Thomas wrote copied your answers into a file for me to keep on hand thank you all for your help for this great grandmother. Parenting a grandparent or great at grandparenting or both?

Thank you all

2025-03-07 Thread Maureen Thomas
Thank you all for your help.  I have copied your answers into a file for me to keep on hand when it happens again.  Again, thank you all for your help for this great grandmother. Moe

Re: Kernel not upgrading in all systems

2025-02-27 Thread Gary Dale
On 2025-02-14 22:00, Michael Stone wrote: On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote: All 3 systems have the linux-image-amd64 metapackage installed. What does apt show -a linux-image-amd64 | grep -e Version -e Sources -e Depends return on each system? If you apt update on

Re: Very frustrating help and support on all channels -----------Fwd: fail message dirmanager

2025-02-18 Thread mick.crane
On 2024-12-23 17:43, koffie wrote: Forwarded Message Subject: fail message dirmanager Date: Sun, 22 Dec 2024 20:38:24 +0100 From: koffie To: debian-user@lists.debian.org Ubuntu / Oracular Hello, It is not possible to download an iso file. It takes hours to get it but it doesn

Re: Kernel not upgrading in all systems

2025-02-14 Thread Max Nikulin
On 14/02/2025 21:49, Gary Dale wrote: On 2025-02-09 11:46, Max Nikulin wrote: I recommend to compare     apt policy linux-image-amd64 and     apt policy I can't see any differences between them on the various systems. If it is true and the latest kernel is installed on all systems

Re: Kernel not upgrading in all systems

2025-02-14 Thread Michael Stone
On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote: All 3 systems have the linux-image-amd64 metapackage installed. What does apt show -a linux-image-amd64 | grep -e Version -e Sources -e Depends return on each system? If you apt update on each system, are there any error messages?

Re: Kernel not upgrading in all systems

2025-02-14 Thread Gary Dale
On 2025-02-09 11:46, Max Nikulin wrote: On 09/02/2025 00:05, Gary Dale wrote: VM1: /etc/apt/sources.list I recommend to compare     apt policy linux-image-amd64 and     apt policy I can't see any differences between them on the various systems.

Re: Kernel not upgrading in all systems

2025-02-14 Thread Gary Dale
that doesn't change the ABI version number. In this case, ls wouldn't show you that there's a newer kernel installed but not yet running. You'd have to use something like "dpkg -l linux-image\* | grep ^.i" to see the actual package version numbers, and compare that a

Re: Kernel not upgrading in all systems

2025-02-14 Thread Gary Dale
On 2025-02-09 06:22, Henrik Ahlgren wrote: On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote: I have a few systems running Debian/Stable (Bookworm). However the kernel version isn't always the same for some reason. After this morning's update, I noticed that 2 of the 3 systems upgraded the ke

Re: Kernel not upgrading in all systems

2025-02-09 Thread Max Nikulin
On 09/02/2025 00:05, Gary Dale wrote: VM1: /etc/apt/sources.list I recommend to compare apt policy linux-image-amd64 and apt policy

Re: Kernel not upgrading in all systems

2025-02-09 Thread Hans
Dis you install the package "linux-image-amd64" ? If yes, the it should always update to the newest kernel. (Same for package "linux-headers-amd64") Hans

Re: Kernel not upgrading in all systems

2025-02-09 Thread Greg Wooledge
On Sun, Feb 09, 2025 at 13:22:50 +0200, Henrik Ahlgren wrote: > On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote: > > I have a few systems running Debian/Stable (Bookworm). However the kernel > > version isn't always the same for some reason. After this morning's update, > > I noticed that 2 of

Re: Kernel not upgrading in all systems

2025-02-09 Thread Henrik Ahlgren
On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote: >   > I have a few systems running Debian/Stable (Bookworm). However the kernel > version isn't always the same for some reason. After this morning's update, I > noticed that 2 of the 3 systems upgraded the kernel but to different > versions. T

Kernel not upgrading in all systems

2025-02-08 Thread Gary Dale
anadian mirrors. /  Linux RM2 6.1.0-31-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07) x86_64 GNU/Linux / Running |/dpkg -l | grep "^hi" / and confirming with ||/dpkg --get-selections | grep "\ |The hardware (real and virtual) is similar in that they are all running AMD CPUs

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-23 Thread Marco Möller
On 1/23/25 00:14, didier gaumet wrote: Le 22/01/2025 à 23:41, Marco Möller a écrit : On 1/22/25 23:23, didier gaumet wrote: Debian provides realtime kernels in its repositories. For an AMD64 PC and Debian 12 Bookworm (without backports), the last LTS realtime kernel package is: linux-image-6.

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-22 Thread didier gaumet
Le 22/01/2025 à 23:41, Marco Möller a écrit : On 1/22/25 23:23, didier gaumet wrote: Debian provides realtime kernels in its repositories. For an AMD64 PC and Debian 12 Bookworm (without backports), the last LTS realtime kernel package is: linux-image-6.1.0-29-rt-amd64 Do I understand correc

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-22 Thread Marco Möller
On 1/22/25 23:12, Michael Stone wrote: On Wed, Jan 22, 2025 at 11:07:57PM +0100, Marco Möller wrote: You mean, linux-image-amd64 in bookworm-backports, which currently draws in  linux-image-6.12.9+bpo-amd64 (= 6.12.9-1~bpo12+1), can be expected to NOT draw in some 6.13 like 6.13~rc7+1~exp1 curr

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-22 Thread Marco Möller
On 1/22/25 23:23, didier gaumet wrote: Debian provides realtime kernels in its repositories. For an AMD64 PC and Debian 12 Bookworm (without backports), the last LTS realtime kernel package is: linux-image-6.1.0-29-rt-amd64 Do I understand correctly, that the rt-kernels like the one you ment

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-22 Thread didier gaumet
Le 22/01/2025 à 23:23, didier gaumet a écrit : [...) DAW usage and I don not think he was not using backports) [...) I did not take time to read myself before posting, sorry: "I do not think he was using backports" is more correct ;-)

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-22 Thread didier gaumet
my laptop for creative audio usage (tracking, running digital instruments, mixing, all what is commonly provided by current Digital Audio Workstations (DAW)). For this I read and understand that one important parameter of Linux optimization could be to use a real time kernel, and to use some

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-22 Thread Michael Stone
On Wed, Jan 22, 2025 at 11:07:57PM +0100, Marco Möller wrote: You mean, linux-image-amd64 in bookworm-backports, which currently draws in linux-image-6.12.9+bpo-amd64 (= 6.12.9-1~bpo12+1), can be expected to NOT draw in some 6.13 like 6.13~rc7+1~exp1 currently already having appeared in the ex

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-22 Thread Marco Möller
On 1/22/25 22:32, Michael Stone wrote: I think the problem here is a misunderstanding of how backports work: they're not "the latest kernel", they're "the latest kernel from debian testing". You're not going to see a kernel in backports that's not going to be in trixie until after the trixie re

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-22 Thread Michael Stone
On Wed, Jan 22, 2025 at 09:48:24PM +0100, Marco Möller wrote: Well, I thought that some easy receipt would pop up as an answer to my question on how to achieve such automatic upgrades. As this did not happen I conclude that the wished procedure is not so common and not readily worked out by now

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-22 Thread Marco Möller
, running digital instruments, mixing, all what is commonly provided by current Digital Audio Workstations (DAW)). For this I read and understand that one important parameter of Linux optimization could be to use a real time kernel, and to use some other more specialized audio related components

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-22 Thread Andrew M.A. Cater
6.12.9 and getting 6.12.10. But > I do not want this upgrade to step up to the 6.13 versions. > For comfortably running the upgrades in an unattended way, I expect that I > might need some pinning to allow all newer 6.12.x versions to become drawn > in when available, but to not al

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-21 Thread Max Nikulin
On 22/01/2025 03:17, Marco Möller wrote: Could you please share with me, or point me to, a howto or receipt for applying all upgrades to future kernel 6.12.x versions to appear in Bookworm Backports when doing "apt update && apt upgrade", but to not leave the 6.12 (upstream L

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-21 Thread Greg Wooledge
On Wed, Jan 22, 2025 at 01:00:49 +0100, Marco Möller wrote: > On 1/22/25 00:10, George at Clug wrote: > > I apologise, but I do not understand what it is you want to achieve or what > > it is that you are asking. > > > > Can you please give more explanation? > > I want to install the currently h

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-21 Thread Marco Möller
the upgrades in an unattended way, I expect that I might need some pinning to allow all newer 6.12.x versions to become drawn in when available, but to not allow any higher kernel version than 6.12.x, so not allowing any 6.13 to become drawn in. It seems to obvious to me, that I should not install

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-21 Thread George at Clug
ates, there will be times when you will be using a package from Testing, ... but it will be "adjusted and recompiled for usage on Debian stable", as are all backports, which is why we use backports and not just download a package from Testing and install it. Maybe you are concerned that

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-21 Thread Marco Möller
On 1/21/25 21:39, Andrew M.A. Cater wrote: On Tue, Jan 21, 2025 at 09:17:52PM +0100, Marco Möller wrote: Hello community! Could you please share with me, or point me to, a howto or receipt for applying all upgrades to future kernel 6.12.x versions to appear in Bookworm Backports when doing &quo

Re: Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-21 Thread Andrew M.A. Cater
On Tue, Jan 21, 2025 at 09:17:52PM +0100, Marco Möller wrote: > Hello community! > Could you please share with me, or point me to, a howto or receipt for > applying all upgrades to future kernel 6.12.x versions to appear in Bookworm > Backports when doing "apt update &&

Backports (bookworm), upgrade to all x for kernel 6.12.x, but not upgrade to 6.13

2025-01-21 Thread Marco Möller
Hello community! Could you please share with me, or point me to, a howto or receipt for applying all upgrades to future kernel 6.12.x versions to appear in Bookworm Backports when doing "apt update && apt upgrade", but to not leave the 6.12 (upstream LTS) branch and not upgr

Re: Very frustrating help and support on all channels -----------Fwd: fail message dirmanager

2024-12-23 Thread Bret Busby
On 24/12/24 02:10, e...@gmx.us wrote: On 12/23/24 12:43, koffie wrote: Forwarded Message Subject: fail message dirmanager Date: Sun, 22 Dec 2024 20:38:24 +0100 From: koffie To: debian-user@lists.debian.org Ubuntu / Oracular Hello, It is not possible to download an iso fil

Re: Very frustrating help and support on all channels -----------Fwd: fail message dirmanager

2024-12-23 Thread eben
On 12/23/24 12:43, koffie wrote: > > > > Forwarded Message > Subject: fail message dirmanager > Date: Sun, 22 Dec 2024 20:38:24 +0100 > From: koffie > To: debian-user@lists.debian.org > > Ubuntu / Oracular > Hello, > > It is not possible to download an iso file. From where? How

Very frustrating help and support on all channels -----------Fwd: fail message dirmanager

2024-12-23 Thread koffie
Forwarded Message Subject: fail message dirmanager Date: Sun, 22 Dec 2024 20:38:24 +0100 From: koffie To: debian-user@lists.debian.org Ubuntu / Oracular Hello, It is not possible to download an iso file. It takes hours to get it but it doesn't boot The sha is fail permanen

Re: DefinitionS sleep/suspend/hibernate/etc - was [Re: help: disable all manner of sleep/suspend/hibernate - Debian 12]

2024-11-23 Thread Andrew M.A. Cater
" : it's as used by the * The firmware and chipset in your machine * The kernel interface * Whatever the tools are in your chosen GUI/desktop environment The first two are much more important - and largely common to all Linux distributions, though these may vary as to kernel version.

Re: DefinitionS sleep/suspend/hibernate/etc - was [Re: help: disable all manner of sleep/suspend/hibernate - Debian 12]

2024-11-23 Thread Richard Owlett
On 11/22/24 5:33 PM, Andrew M.A. Cater wrote: On Fri, Nov 22, 2024 at 04:26:05AM -0600, Richard Owlett wrote: On 11/22/24 12:57 AM, Michael Paoli wrote: I recently jumped from Debian 9(w/MATE) - 12(w/MATE) in one step. My Debian 9 settings can be traced back to Debian 6(w/Gnome). I don't recall

Re: DefinitionS sleep/suspend/hibernate/etc - was [Re: help: disable all manner of sleep/suspend/hibernate - Debian 12]

2024-11-22 Thread Andrew M.A. Cater
ne what you have. > Michael mentioned https://wiki.debian.org/Suspend and I found > https://wiki.debian.org/Hibernation . > > I, and other inexperienced users, need proper definitions of > sleep/suspend/hibernate/etc to use those pages and solutions to be described > here. > > All the very best, Andy Cater (amaca...@debian.org)

Re: help: disable all manner of sleep/suspend/hibernate - Debian 12

2024-11-22 Thread Jeffrey Walton
>much as even a full second of power interruption). > > Yes, I have three laptops like that. And after a period of > non-connection/use, the BIOS settings on one of them were also > lost, eg the date/time and administrative password. > > > what it shows in the logs - abo

Re: help: disable all manner of sleep/suspend/hibernate - Debian 12

2024-11-22 Thread David Wright
tops like that. And after a period of non-connection/use, the BIOS settings on one of them were also lost, eg the date/time and administrative password. > what it shows in the logs - about all I've been able to find is this: > but without any more details as to what's triggering

Re: DefinitionS sleep/suspend/hibernate/etc - was [Re: help: disable all manner of sleep/suspend/hibernate - Debian 12]

2024-11-22 Thread Michael Paoli
Thanks. Still haven't found way to prevent sleep/hibernate/etc, but FYI: $ (cd /sys/power && grep . mem_sleep state) mem_sleep:s2idle [deep] state:freeze mem disk $ On Fri, Nov 22, 2024 at 5:15 AM wrote: > Definitions can be found at > https://docs.kernel.org/admin-guide/pm/sleep-states.html > Ot

Re: help: disable all manner of sleep/suspend/hibernate - Debian 12

2024-11-22 Thread Michael Paoli
Thanks, my responses in-line below (also restored some of the earlier that was removed from original, and included full original at tail end of this email): On Fri, Nov 22, 2024 at 5:02 AM Max Nikulin wrote: > On 22/11/2024 13:57, Michael Paoli wrote: > > all network activity ceases

Re: DefinitionS sleep/suspend/hibernate/etc - was [Re: help: disable all manner of sleep/suspend/hibernate - Debian 12]

2024-11-22 Thread debian-user
Richard Owlett wrote: > Michael mentioned https://wiki.debian.org/Suspend and I found > https://wiki.debian.org/Hibernation . > > I, and other inexperienced users, need proper definitions of > sleep/suspend/hibernate/etc to use those pages and solutions to be > described here. Definitions c

Re: help: disable all manner of sleep/suspend/hibernate - Debian 12

2024-11-22 Thread Max Nikulin
On 22/11/2024 13:57, Michael Paoli wrote: seems to be a very deep form of sleep, the only things I can do at that point that at all gets it to respond: - which does a warm reboot Does not like suspend to RAM or suspend to disk (hibernate). It resembles graphics issues. Can you

Re: DefinitionS sleep/suspend/hibernate/etc - was [Re: help: disable all manner of sleep/suspend/hibernate - Debian 12]

2024-11-22 Thread Michael Paoli
avior) when I don't at all want it to, and never successfully resuming from that. And thanks, I did also look over https://wiki.debian.org/Hibernation But alas, nothing there appears applicable to my issue/situation. Anyway, maybe at some point I'll update/that/those Debian wiki pages -

DefinitionS sleep/suspend/hibernate/etc - was [Re: help: disable all manner of sleep/suspend/hibernate - Debian 12]

2024-11-22 Thread Richard Owlett
On 11/22/24 12:57 AM, Michael Paoli wrote: How do I disable all manner of sleep/suspend/hibernate on Debian 12? [snip very detailed of his environment/symptoms] I recently jumped from Debian 9(w/MATE) - 12(w/MATE) in one step. My Debian 9 settings can be traced back to Debian 6(w/Gnome). I

help: disable all manner of sleep/suspend/hibernate - Debian 12

2024-11-21 Thread Michael Paoli
How do I disable all manner of sleep/suspend/hibernate on Debian 12? I really don't want it doing any sleep/suspend/hibernate (I'm okay with explicitly manually triggering it, but I don't even need that). Symptoms/issue/background: Was a non-issue on Debian 10 (sleep/hibernate woul

Re: Why does "apt-get upgrade {package}" upgrade all packages instead of error?

2024-10-24 Thread Aldo Maggi
Actually the english version of "man apt-get" in the case of "upgrade" writes the following: upgrade    upgrade is used to install the newest versions of all packages currently installed on the system from the sources enumerated in /etc/apt/sources.list

Re: Why does "apt-get upgrade {package}" upgrade all packages instead of error?

2024-10-24 Thread David Wright
s". However, passing a package name to > "apt-get upgrade" results in the argument being ignored and all packages > upgraded. > > Is there some reason that this is the case? Is it a bug that has > always existed and never fixed? I can't provoke this bug, so w

Why does "apt-get upgrade {package}" upgrade all packages instead of error?

2024-10-24 Thread Daniel Roberts
s in the argument being ignored and all packages upgraded. Is there some reason that this is the case? Is it a bug that has always existed and never fixed? Dan

Re: Why does "apt-get upgrade {package}" upgrade all packages instead of error?

2024-10-24 Thread Felix Miata
;. However, passing a package name to > "apt-get upgrade" results in the argument being ignored and all packages > upgraded. > Is there some reason that this is the case? Is it a bug that has > always existed and never fixed? It's not like dnf or zypper or urpmi. If you w

Re: Why does "apt-get upgrade {package}" upgrade all packages instead of error?

2024-10-24 Thread Frank Weißer
Hello Daniel, # man apt-get (german translation) doesn't tell anything else. apt-get upgrade upgrades ALL installed packages. Kind regards Frank Daniel Roberts: Hello, I've run into this a few times over the years and it can be a headache to resolve. Passing a package name t

Docker Bridge network hangs all network

2024-03-08 Thread Dustin Jenkins
ities are halted (i.e. browser, apt, etc.). When the container dies eventually, all network is restored on the machine. This is on my NVMe drive. If I specify the "--network host" option, it succeeds. With the SATA drive installation, this all succeeds as expected. The only difference b

Re: Does "LC_ALL=C" work on all shells?

2024-02-16 Thread Max Nikulin
On 16/02/2024 23:35, Franco Martelli wrote: On 16/02/24 at 03:03, Max Nikulin wrote: LC_ALL=C.UTF-8 LANGUAGE=it aptitude why firefox-esr here seems to override, tested twice with "it" and "it_IT.UTF-8": ~# env LC_ALL=C LANGUAGE=it script -T ~/test.time -a ~/test.script You tested with

Re: Does "LC_ALL=C" work on all shells?

2024-02-16 Thread Franco Martelli
wrote: To change programs' output messages to English LC_MESSAGES=C is often enough. Sometimes LC_TIME and LC_NUMERIC are required too. but it seems may have drawbacks if other variables are involved. From the manual page of "script" command the -t option is deprecated in favor o

Re: Does "LC_ALL=C" work on all shells?

2024-02-16 Thread tomas
On Fri, Feb 16, 2024 at 11:44:21AM -0500, Greg Wooledge wrote: > On Fri, Feb 16, 2024 at 05:35:04PM +0100, Franco Martelli wrote: > > It was stated here: > > https://lists.debian.org/debian-user/2024/02/msg00592.html > > "I think that a recorded session with the output of the commands in > English

Re: Does "LC_ALL=C" work on all shells?

2024-02-16 Thread Greg Wooledge
On Fri, Feb 16, 2024 at 05:35:04PM +0100, Franco Martelli wrote: > It was stated here: > https://lists.debian.org/debian-user/2024/02/msg00592.html "I think that a recorded session with the output of the commands in English is better then a localized session for debugging purposes." I have troubl

Re: Does "LC_ALL=C" work on all shells?

2024-02-16 Thread Franco Martelli
On 16/02/24 at 13:17, Greg Wooledge wrote: On Fri, Feb 16, 2024 at 09:13:40AM +0200, Teemu Likonen wrote: In my opinion it's often too much to set LC_ALL=C because it changes charset to ASCII (LC_CTYPE). It depends on what you're doing, of course. If the purpose is to normalize error messages

Re: Does "LC_ALL=C" work on all shells?

2024-02-16 Thread Greg Wooledge
On Fri, Feb 16, 2024 at 09:13:40AM +0200, Teemu Likonen wrote: > In my opinion it's often too much to set LC_ALL=C because it changes > charset to ASCII (LC_CTYPE). It depends on what you're doing, of course. If the purpose is to normalize error messages so that you can report your issue to an En

Re: Does "LC_ALL=C" work on all shells?

2024-02-15 Thread Teemu Likonen
* 2024-02-15 21:17:44+0100, Franco Martelli wrote: > Doesn't LC_ALL=C setting override LANG or LANGUAGE settings? LC_ALL overrides LC_* variables. It's easy to test: $ locale LANG=fi_FI.UTF-8 LANGUAGE=fi LC_CTYPE="fi_FI.UTF-8" LC_NUMERIC="fi_FI.UTF-8" LC_TIME="fi_FI.UTF-8

Re: Does "LC_ALL=C" work on all shells?

2024-02-15 Thread Max Nikulin
On 16/02/2024 09:34, David Wright wrote: Yes, LC_ALL=C will override all the locale variables, but LC_ALL=C.UTF-8 will not: It is documented in 2.3.3 Specifying a Priority List of Languages (info "(gettext) The LANGUAGE variable") https://www.gnu.org/software/gettext/manual/htm

Re: Does "LC_ALL=C" work on all shells?

2024-02-15 Thread David Wright
;C.UTF-8" LC_PAPER="C.UTF-8" LC_NAME="C.UTF-8" LC_ADDRESS="C.UTF-8" LC_TELEPHONE="C.UTF-8" LC_MEASUREMENT="C.UTF-8" LC_IDENTIFICATION="C.UTF-8" LC_ALL= $ > and LC_ALL=C override the LANG setting when used inlin

Re: Does "LC_ALL=C" work on all shells?

2024-02-15 Thread Max Nikulin
On 16/02/2024 03:17, Franco Martelli wrote: On 15/02/24 at 03:28, Max Nikulin wrote: LANG=C.UTF-8; LANGUAGE=; export LANG LANGUAGE Doesn't LC_ALL=C setting override LANG or LANGUAGE settings? Sorry, my bad. Of course LC_ALL=C.UTF-8; LANGUAGE=; export LC_ALL LANGUAGE and LC_ALL=C

Re: Does "LC_ALL=C" work on all shells?

2024-02-15 Thread Franco Martelli
my system I have: ~$ env | grep LANG LANGUAGE= LANG=it_IT.UTF-8 and LC_ALL=C override the LANG setting when used inline of the command. This approach is to cover all cases, my goal is to do apt/apt-get commands output in English when they are executed into a "script" session. Thank to

Re: Does "LC_ALL=C" work on all shells?

2024-02-14 Thread Max Nikulin
On 14/02/2024 23:11, Franco Martelli wrote: Well, I'll go with env command syntax for shells portability. I was asking this because I want to suggest a change to the DDP (Debian Documentation Project) members for the releases notes documentation ¹ # env LC_ALL=C script -t 2>~/upgrade-bookworms

Re: Does "LC_ALL=C" work on all shells?

2024-02-14 Thread Greg Wooledge
On Wed, Feb 14, 2024 at 09:45:52PM +0100, Franco Martelli wrote: > A new question arise spontaneously: how can csh users run a "script" saved > session using "scriptreplay" command? In the §4.4.1 "Recording the session" > paragraph ¹ I see this syntax: > > # scriptreplay ~/upgrade-bookwormstep.ti

Re: Does "LC_ALL=C" work on all shells?

2024-02-14 Thread Franco Martelli
On 14/02/24 at 17:48, Greg Wooledge wrote: On Wed, Feb 14, 2024 at 05:35:59PM +0100, Franco Martelli wrote: On 14/02/24 at 17:15, Greg Wooledge wrote: # env LC_ALL=C script -t 2>~/upgrade-bookwormstep.time -a ~/upgrade-bookwormstep.script That command is already using Bourne family shell synta

Re: Does "LC_ALL=C" work on all shells?

2024-02-14 Thread Greg Wooledge
On Wed, Feb 14, 2024 at 05:35:59PM +0100, Franco Martelli wrote: > On 14/02/24 at 17:15, Greg Wooledge wrote: > > > # env LC_ALL=C script -t 2>~/upgrade-bookwormstep.time -a > > > ~/upgrade-bookwormstep.script > > That command is already using Bourne family shell syntax (the 2> part) > > so you can

Re: Does "LC_ALL=C" work on all shells?

2024-02-14 Thread Greg Wooledge
On Wed, Feb 14, 2024 at 05:11:55PM +0100, Franco Martelli wrote: > Well, I'll go with env command syntax for shells portability. I was asking > this because I want to suggest a change to the DDP (Debian Documentation > Project) members for the releases notes documentation ¹ > > The change I want t

Re: Does "LC_ALL=C" work on all shells?

2024-02-14 Thread Franco Martelli
ange I want to suggest is to add "env LC_ALL=C" to the "script" command: # env LC_ALL=C script -t 2>~/upgrade-bookwormstep.time -a ~/upgrade-bookwormstep.script I think that a recorded session with the output of the commands in English is better then a localized session

Re: Does "LC_ALL=C" work on all shells?

2024-02-14 Thread Gremlin
On 2/13/24 22:11, Greg Wooledge wrote: On Tue, Feb 13, 2024 at 09:47:52PM -0500, Gremlin wrote: This is from a script installed by a package that does a dpkg-reconfigure locales to set the locale on the machine. What package? What script? I am working on it with a high rate a speed, should

Re: Does "LC_ALL=C" work on all shells?

2024-02-13 Thread Greg Wooledge
On Tue, Feb 13, 2024 at 09:47:52PM -0500, Gremlin wrote: > This is from a script installed by a package that does a > dpkg-reconfigure locales to set the locale on the machine. What package? What script? > BTW where is LANGUAGE defined in the "standards/conventions"? It's a GNUism. https://www

Re: Does "LC_ALL=C" work on all shells?

2024-02-13 Thread Gremlin
On 2/13/24 21:22, Max Nikulin wrote: On 14/02/2024 07:56, Gremlin wrote: Gremlin (12024-02-13): cat /etc/default/locale #  File generated by update-locale LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 Found this in a shell script: LC_ALL=$LOC LANG=$LOC LANGUAGE=$LOC update-locale LANG=$LOC LC_ALL=

Re: Does "LC_ALL=C" work on all shells?

2024-02-13 Thread Max Nikulin
On 14/02/2024 07:56, Gremlin wrote: Gremlin (12024-02-13): cat /etc/default/locale #  File generated by update-locale LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 Found this in a shell script: LC_ALL=$LOC LANG=$LOC LANGUAGE=$LOC update-locale LANG=$LOC LC_ALL=$LOC LANGUAGE=$LOC Do not do it for

Re: Does "LC_ALL=C" work on all shells?

2024-02-13 Thread Greg Wooledge
On Tue, Feb 13, 2024 at 07:56:46PM -0500, Gremlin wrote: > Found this in a shell script: > > LC_ALL=$LOC LANG=$LOC LANGUAGE=$LOC update-locale LANG=$LOC LC_ALL=$LOC > LANGUAGE=$LOC In *what* shell script?

Re: Does "LC_ALL=C" work on all shells?

2024-02-13 Thread Gremlin
On 2/13/24 19:29, Gremlin wrote: On 2/13/24 17:48, Nicolas George wrote: Gremlin (12024-02-13): Oh like debian does? cat /etc/default/locale #  File generated by update-locale LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 LC_ALL=en_US.UTF-8 I do not observe this, even after “sudo dpkg-reconfigure lo

Re: Does "LC_ALL=C" work on all shells?

2024-02-13 Thread Andy Smith
ut not actually shipped by a package will not be found by these commands. You can look in all the maintainer scripts to see where it's mentioned: $ grep -r /etc/default/locale /var/lib/dpkg/info which leads me to believe it may be most relevant to the "locales" package, but this doe

Re: Does "LC_ALL=C" work on all shells?

2024-02-13 Thread Gremlin
On 2/13/24 17:48, Nicolas George wrote: Gremlin (12024-02-13): Oh like debian does? cat /etc/default/locale # File generated by update-locale LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 LC_ALL=en_US.UTF-8 I do not observe this, even after “sudo dpkg-reconfigure locales”. Can you explain how you re

Re: Does "LC_ALL=C" work on all shells?

2024-02-13 Thread Greg Wooledge
On Tue, Feb 13, 2024 at 11:48:04PM +0100, Nicolas George wrote: > Gremlin (12024-02-13): > > Oh like debian does? > > > > cat /etc/default/locale > > # File generated by update-locale > > LANG=en_US.UTF-8 > > LANGUAGE=en_US.UTF-8 > > LC_ALL=en_US.UTF-8 > > I do not observe this, even after “sudo

Re: Does "LC_ALL=C" work on all shells?

2024-02-13 Thread Nicolas George
Gremlin (12024-02-13): > Oh like debian does? > > cat /etc/default/locale > # File generated by update-locale > LANG=en_US.UTF-8 > LANGUAGE=en_US.UTF-8 > LC_ALL=en_US.UTF-8 I do not observe this, even after “sudo dpkg-reconfigure locales”. Can you explain how you reached this state? -- Nicol

  1   2   3   4   5   6   7   8   9   10   >