Hello,
I upgraded from Buster stable to Bullseye stable last night, with apparent
success eventually, but it went less than smoothly and I would be grateful for
any advice as to why that may have been.
I followed the preparation advice at
https://www.debian.org/releases/bullseye/amd64/release-
On Wed 18 Aug 2021, at 00:44, Gareth Evans wrote:
> Hello,
>
> I upgraded from Buster stable to Bullseye stable last night, with
> apparent success eventually, but it went less than smoothly and I would
> be grateful for any advice as to why that may have been.
>
> I fol
On Wed 18 Aug 2021, at 23:33, piorunz wrote:
> On 18/08/2021 16:14, Gareth Evans wrote:
> > Unpacking gir1.2-gst-plugins-bad-1.0:amd64 (1.18.4-3) ...
> > [1mdpkg:[0m error processing archive
> > /tmp/apt-dpkg-install-Un4rDW/28-gir1.2-gst-plugins-bad-1.0_1.18.4-3_amd
On Thu 19 Aug 2021, at 05:50, David Wright wrote:
> On Thu 19 Aug 2021 at 04:00:04 (+0100), Gareth Evans wrote:
> > On Wed 18 Aug 2021, at 23:33, piorunz wrote:
> > > On 18/08/2021 16:14, Gareth Evans wrote:
> > > > Unpacking gir1.2-gst-plugins-bad-1.0:amd64 (1.1
On Fri 20 Aug 2021, at 12:32, Greg Wooledge wrote:
> On Thu, Aug 19, 2021 at 10:45:57PM -0500, David Wright wrote:
> > One might assume so, but only you can check that. There are two logs
> > of the upgrade. /var/log/apt/history.log (and its predecessors) shows
> > the command issued, followed by
On Fri 20 Aug 2021, at 04:45, David Wright wrote:
> On Thu 19 Aug 2021 at 07:42:56 (+0100), Gareth Evans wrote:
> > On Thu 19 Aug 2021, at 05:50, David Wright wrote:
> > > On Thu 19 Aug 2021 at 04:00:04 (+0100), Gareth Evans wrote:
> > > > On Wed 18 Aug
On Sat 21 Aug 2021, at 13:42, Sven Hartge wrote:
> Gareth Evans wrote:
>
> > So I would like to know if apt is not handling this properly, or if
> > the scenario of a file changing packages (see David's previous email)
> > is an expected exception to th
On Sun 22 Aug 2021, at 05:36, David Wright wrote:
> On Fri 20 Aug 2021 at 14:13:55 (+0100), Gareth Evans wrote:
> > On Fri 20 Aug 2021, at 04:45, David Wright wrote:
> > > On Thu 19 Aug 2021 at 07:42:56 (+0100), Gareth Evans wrote:
>
> > $ apt policy pitivi
> >
On Sun 22 Aug 2021, at 13:18, Gareth Evans wrote:
> On Sun 22 Aug 2021, at 05:36, David Wright wrote:
> > On Fri 20 Aug 2021 at 14:13:55 (+0100), Gareth Evans wrote:
> > > On Fri 20 Aug 2021, at 04:45, David Wright
> > > wrote:
> > > > On Thu 19 Aug 2021
On Sun 22 Aug 2021, at 15:37, David Wright wrote:
> On Sun 22 Aug 2021 at 13:18:38 (+0100), Gareth Evans wrote:
> > On Sun 22 Aug 2021, at 05:36, David Wright wrote:
> > > On Fri 20 Aug 2021 at 14:13:55 (+0100), Gareth Evans wrote:
>
> > > > There is also no e
On Sun 19 Sep 2021, at 05:49, David Wright wrote:
> On Sat 18 Sep 2021 at 21:56:34 (+0100), piorunz wrote:
> > On 18/09/2021 20:00, David Wright wrote:
> >
> > > A lot of hits from googling grub colemak including
> > > https://forums.debian.net//viewtopic.php?f=16&t=76833
> > > which uses dvo
On Sun 19 Sep 2021, at 06:14, Gareth Evans wrote:
> On Sun 19 Sep 2021, at 05:49, David Wright wrote:
> > On Sat 18 Sep 2021 at 21:56:34 (+0100), piorunz wrote:
> > > On 18/09/2021 20:00, David Wright wrote:
> > >
> > > > A lot of hits from googling
On Sun 19 Sep 2021, at 11:48, Gareth Evans wrote:
> On Sun 19 Sep 2021, at 06:14, Gareth Evans wrote:
> > On Sun 19 Sep 2021, at 05:49, David Wright wrote:
> > > On Sat 18 Sep 2021 at 21:56:34 (+0100), piorunz wrote:
> > > > On 18/09/2021 20:00, David Wright wrot
On Sun 19 Sep 2021, at 13:00, Gareth Evans wrote:
> On Sun 19 Sep 2021, at 11:48, Gareth Evans wrote:
> > On Sun 19 Sep 2021, at 06:14, Gareth Evans wrote:
> > > On Sun 19 Sep 2021, at 05:49, David Wright
> > > wrote:
> > > > On Sat 18 Sep 2021 at 21:56:
On Sun 19 Sep 2021, at 13:43, piorunz wrote:
> On 19/09/2021 13:26, Gareth Evans wrote:
>
> > The commands appeared to succeed (with suitable alteration of variables)
> > but my VM now boots into a grub prompt immediately - doesn't ask for LUKS
> > password.
Hello,
I've just noticed that:
$ who
and
$ users
both return nothing, with or without sudo.
$ sudo strace who
access("/var/run/utmpx", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file
or directory)
access
On Mon 24 Jan 2022, at 12:45, Greg Wooledge wrote:
> On Mon, Jan 24, 2022 at 09:51:05AM +0000, Gareth Evans wrote:
>> I've just noticed that:
>>
>> $ who
>>
>> and
>>
>> $ users
>>
>> both return nothing, with or without sudo.
&g
On Tue 25 Jan 2022, at 01:31, Gareth Evans wrote:
> On Mon 24 Jan 2022, at 12:45, Greg Wooledge wrote:
>> On Mon, Jan 24, 2022 at 09:51:05AM +0000, Gareth Evans wrote:
>>> I've just noticed that:
>>>
>>> $ who
>>>
>>> and
>>
Further to my disappearing /var/run/utmp query, I also newly can't start VMs
with virt-manager without first doing
$ sudo modprobe tun
This has also changed recently, apparently without intervention on my part.
Presumably it has stopped being autoloaded somewhere.
Should tun be in
/etc/modul
On Tue 25 Jan 2022, at 02:54, Greg Wooledge wrote:
> On Tue, Jan 25, 2022 at 01:31:35AM +0000, Gareth Evans wrote:
>> /var/run$ sudo touch utmp
>> /var/run$ sudo chown root:utmp utmp
>> /var/run$ sudo chmod 664 utmp
>> /var/run$ ls -l utmp
>> -rw-rw-r-- 1 root utm
On Tue 25 Jan 2022, at 03:02, Gareth Evans wrote:
> On Tue 25 Jan 2022, at 02:54, Greg Wooledge wrote:
>> On Tue, Jan 25, 2022 at 01:31:35AM +0000, Gareth Evans wrote:
>>> /var/run$ sudo touch utmp
>>> /var/run$ sudo chown root:utmp utmp
>>> /var/run$ sudo chm
On Tue 25 Jan 2022, at 03:28, Greg Wooledge wrote:
> On Tue, Jan 25, 2022 at 03:06:00AM +0000, Gareth Evans wrote:
>> On Tue 25 Jan 2022, at 03:02, Gareth Evans wrote:
>> > On Tue 25 Jan 2022, at 02:54, Greg Wooledge wrote:
>> >> A google search led me to <http
On Tue 25 Jan 2022, at 04:10, Polyna-Maude Racicot-Summerside
wrote:
> On 2022-01-24 23:03, Gareth Evans wrote:
>> On Tue 25 Jan 2022, at 03:28, Greg Wooledge wrote:
>>> On Tue, Jan 25, 2022 at 03:06:00AM +, Gareth Evans wrote:
>>>> On Tue 25 Jan 2022,
On Tue 25 Jan 2022, at 02:11, Gareth Evans wrote:
> Further to my disappearing /var/run/utmp query, I also newly can't
> start VMs with virt-manager without first doing
>
> $ sudo modprobe tun
>
> This has also changed recently, apparently without intervention on my part
On Tue 25 Jan 2022, at 04:50, David Wright wrote:
> On Tue 25 Jan 2022 at 04:22:39 (+), Gareth Evans wrote:
>> On Tue 25 Jan 2022, at 04:10, Polyna-Maude Racicot-Summerside
>> wrote:
>> > On 2022-01-24 23:03, Gareth Evans wrote:
>> >> Jan 25 01:46:52 qwe
On Tue 25 Jan 2022, at 10:47, Andrei POPESCU wrote:
> On Ma, 25 ian 22, 04:03:17, Gareth Evans wrote:
>>
>> Googling "Detected unsafe path transition during canonicalization" led me to
>>
>> https://bbs.archlinux.org/viewtopic.php?id=260924
>>
&
On Tue 25 Jan 2022, at 01:31, Gareth Evans wrote:
> On Mon 24 Jan 2022, at 12:45, Greg Wooledge wrote:
>> On Mon, Jan 24, 2022 at 09:51:05AM +0000, Gareth Evans wrote:
>>> I've just noticed that:
>>>
>>> $ who
>>>
>>> and
>>
On Tue 25 Jan 2022, at 13:11, Greg Wooledge wrote:
> On Tue, Jan 25, 2022 at 01:06:42PM +0000, Gareth Evans wrote:
>> Just realised I gave contradicting info earlier - I said both that I
>> upgraded from Buster (which is literally true) and that
>>
>> "But f
> On 25 Jan 2022, at 14:17, Martin McCormick wrote:
>
> This Pi is running Debian Stretch. I believe that's what version
> 9 is called. I have it capturing audio from a radio receiver and
> it's been doing that for several years now and it was doing that
> yesterday morning. Later in the d
A recent dist-upgrade on Buster (in a scripted cron job run at 01:00 daily)
failed due to apt-listbugs complaining about the boot-breaking bug in
shim-signed, and pinning v1.33 in the process.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990082
The next (manual) dist-upgrade removed shim-s
On Tue 22 Jun 2021, at 19:13, David Wright wrote:
> On Tue 22 Jun 2021 at 08:59:13 (+0100), Gareth Evans wrote:
> > A recent dist-upgrade on Buster (in a scripted cron job run at 01:00 daily)
> > failed due to apt-listbugs complaining about the boot-breaking bug in
> > shi
On Tue 29 Jun 2021, at 17:11, David Wright wrote:
> On Tue 29 Jun 2021 at 08:29:22 (+0300), Andrei POPESCU wrote:
> > On Lu, 28 iun 21, 09:46:17, David Wright wrote:
> > >
> > > But your evening run of apt-get -y dist-upgrade was unconstrained,
> > > and so shim-signed could be removed becaus
On Tue 29 Jun 2021, at 22:41, Gareth Evans wrote:
> On Tue 29 Jun 2021, at 17:11, David Wright wrote:
> > On Tue 29 Jun 2021 at 08:29:22 (+0300), Andrei POPESCU wrote:
> > > On Lu, 28 iun 21, 09:46:17, David Wright wrote:
> > > >
> > > > But your even
Hello,
I was just trying to install docker.io on Buster stable when apt-listbugs
complained about one of the open CVEs listed here:
https://security-tracker.debian.org/tracker/source-package/runc
Given that these are all fixed in Bullseye (and at least the grave apt-listbugs
issue has been fix
On Mon 2 Aug 2021, at 11:48, Dominique Dumont wrote:
> On Tuesday, 27 July 2021 18:07:53 CEST Gareth Evans wrote:
> > Given that these are all fixed in Bullseye (and at least the grave
> > apt-listbugs issue has been fixed in eg Ubuntu since March 2020 [1]) why
>
> On 28 Jan 2022, at 16:52, David Wright wrote:
>
> On Fri 28 Jan 2022 at 07:30:25 (-0600), Martin McCormick wrote:
>> David Wright writes:
>>> I've not heard of that problem. You were prevented from zeroing the
>>> entire device, which would have wiped the partition table anyway.
>>>
>>> W
> On 28 Jan 2022, at 18:16, Gareth Evans wrote:
>
>
>
>>> On 28 Jan 2022, at 16:52, David Wright wrote:
>>>
>>> On Fri 28 Jan 2022 at 07:30:25 (-0600), Martin McCormick wrote:
>>> David Wright writes:
>>>> I've not heard
> On 28 Jan 2022, at 20:40, David Wright wrote:
>
> On Fri 28 Jan 2022 at 18:22:37 (+), Gareth Evans wrote:
>>> On 28 Jan 2022, at 18:16, Gareth Evans wrote:
>>>>> On 28 Jan 2022, at 16:52, David Wright wrote:
>>>>> On Fri 28 Jan
> On 31 Jan 2022, at 14:41, Martin McCormick wrote:
>
> #I should be telling resize2fs to squeeze everything in to a 7GB
> #partition.
> sudo resize2fs /dev/loop0p2 +7G
> [...]
> then I delete P2 and then add a
> new partition which defaults to 2.
This seems to replace the partition contain
> On 31 Jan 2022, at 17:37, Andy Smith wrote:
>
> Hello,
>
> On Mon, Jan 31, 2022 at 05:27:56PM +0000, Gareth Evans wrote:
>>>> On 31 Jan 2022, at 14:41, Martin McCormick wrote:
>>>
>>> #I should be telling resize2fs to squeeze everything in
> On 31 Jan 2022, at 17:58, Gareth Evans wrote:
>
>
>
>> On 31 Jan 2022, at 17:37, Andy Smith wrote:
>>
>> Hello,
>>
>> On Mon, Jan 31, 2022 at 05:27:56PM +, Gareth Evans wrote:
>>>>>> On 31 Jan 2022, at 14:41, Martin
> On 31 Jan 2022, at 18:03, Gareth Evans wrote:
>
>
>
>> On 31 Jan 2022, at 17:58, Gareth Evans wrote:
>>
>>
>>
>>>> On 31 Jan 2022, at 17:37, Andy Smith wrote:
>>>
>>> Hello,
>>>
>>> On Mon, Ja
> On 31 Jan 2022, at 23:36, Andy Smith wrote:
> Hello,
>
> On Mon, Jan 31, 2022 at 05:57:45PM +0000, Gareth Evans wrote:
>>> On 31 Jan 2022, at 17:37, Andy Smith wrote:
>> Hi Andy, I appreciate the data doesn't go anywhere, but...
>>
>>>>
> On 31 Mar 2022, at 09:44, Dieter Rohlfing wrote:
>
> Hi,
>
> I'm just about to install Debian11/Bullseye on a host. There are several
> VMs running under QEMU/KVM to set up.
>
> With Debian9/Stretch I created a new VM via command line:
>
> /usr/bin/kvm -drive
> file=/qemu/win-70/win-70.jes
On Thu 7 Apr 2022, at 09:58, Jonathan Dowland wrote:
> On Sat, Apr 02, 2022 at 07:08:11PM +0100, Brad Rogers wrote:
>>Tools menu/Options - General; 'Printing sets "document modified" status'
>
> Does anyone have any insight into why this is an option? More
> specifically, what reason would anyon
On Mon 11 Apr 2022, at 19:23, Brian wrote:
> On Mon 11 Apr 2022 at 13:55:03 -0400, Greg Wooledge wrote:
>
>> On Mon, Apr 11, 2022 at 06:47:59PM +0100, Brian wrote:
>> > BTW. I am interested in how using /usr/lib/cups/backend/snmp went.
>> > Its drawback is that not all printers provide an snmp ser
Hello,
I have a strange printing problem which can be replicated on two identical
printers on two different networks, when printing to wireless driverless IPP
with Brother MFC-L2740DW printers from Bullseye, whether the printer is
auto-detected or manually added via ocalhost:631 or system-confi
On Mon 6 Jun 2022, at 12:19, Gareth Evans wrote:
> Hello,
>
> I have a strange printing problem which can be replicated on two
> identical printers on two different networks, when printing to wireless
> driverless IPP with Brother MFC-L2740DW printers from Bullseye, whether
&
On Mon 6 Jun 2022, at 13:05, rhkra...@gmail.com wrote:
> On Monday, June 06, 2022 07:34:07 AM Gareth Evans wrote:
>> On Mon 6 Jun 2022, at 12:19, Gareth Evans wrote:
>> > I have a strange printing problem which can be replicated on two
>> > identical printers on t
CUPS error log excerpt attached.
G
On Mon 6 Jun 2022, at 14:02, Gareth Evans wrote:
> On Mon 6 Jun 2022, at 13:05, rhkra...@gmail.com wrote:
>> On Monday, June 06, 2022 07:34:07 AM Gareth Evans wrote:
>>> On Mon 6 Jun 2022, at 12:19, Gareth Evans wrote:
>>>
On Mon 6 Jun 2022, at 14:14, Eduardo M KALINOWSKI
wrote:
> On 06/06/2022 08:19, Gareth Evans wrote:
>> Hello,
>>
>> I have a strange printing problem which can be replicated on two identical
>> printers on two different networks, when printing to wireless driverle
Recent message with screenshots didn't get through (at least yet) - text below,
plus another observation.
On Mon 6 Jun 2022, at 16:53, Gareth Evans wrote:
> On Mon 6 Jun 2022, at 16:23, Eduardo M KALINOWSKI
> wrote:
>> On 06/06/2022 10:48, Gareth Evans wrote:
>>>
On Mon 6 Jun 2022, at 17:45, Gareth Evans wrote:
> Recent message with screenshots didn't get through (at least yet) -
> text below, plus another observation.
>
> On Mon 6 Jun 2022, at 16:53, Gareth Evans wrote:
>> On Mon 6 Jun 2022, at 16:23, Eduardo M KALINOWSKI
On Thu 16 Jun 2022, at 22:13, Hans wrote:
> Hi folks,
>
> I am struggeling with a little problem, I can not explain.
>
> A friend of mine uses a printer (Samsung SL-C480FW), which is connected to
> the
> router with wireless. However, although there are no drivers and no ppd-files
> installed,
> On 17 Jun 2022, at 01:56, Gareth Evans wrote:
> On Thu 16 Jun 2022, at 22:13, Hans wrote:
>> Hi folks,
>>
>> I am struggeling with a little problem, I can not explain.
>>
>> A friend of mine uses a printer (Samsung SL-C480FW), which is connected
On Mon 6 Jun 2022, at 20:03, Gareth Evans wrote:
> On Mon 6 Jun 2022, at 17:45, Gareth Evans wrote:
>> Recent message with screenshots didn't get through (at least yet) -
>> text below, plus another observation.
>>
>> On Mon 6 Jun 2022, at 16:53, Gareth Evan
Is there a limit for message size on debian-user?
I can't find any such info on
https://lists.debian.org/
https://www.debian.org/MailingLists/
https://lists.debian.org/debian-user/
but a couple of recent large-ish messages (one ~270K with two screenshots, one
70K with log output) have neither
> On 17 Jun 2022, at 17:51, Nicolas George wrote:
>
> Gareth Evans (12022-06-17):
>> but a couple of recent large-ish messages (one ~270K with two
>> screenshots, one 70K with log output) have neither got through nor
>> bounced back.
>
> “Avoid sendi
On Fri 17 Jun 2022, at 20:00, Brian wrote:
> On Fri 17 Jun 2022 at 16:24:54 +0100, Gareth Evans wrote:
>
>> Is there a limit for message size on debian-user?
>>
>> I can't find any such info on
>>
>> https://lists.debian.org/
>>
>&
> On 17 Jun 2022, at 23:25, Bijan Soleymani wrote:
>
> On 2022-06-17 18:20, Bijan Soleymani wrote:
>>> On 2022-06-17 11:24, Gareth Evans wrote:
>>> Is there a limit for message size on debian-user?
>> I checked the data. I have been subscribed since 2003, th
> On 19 Jun 2022, at 13:56, gene heskett wrote:
>
> On 6/18/22 05:54, Hans wrote:
>> Hi Brian,
>>
>>> You were expected to execute 'lpinfo -v' and give us the output. We
>>> also expect the result of 'driverless'.
>> this is difficult, as the computer is 600km away from me and I have no acce
On Sun 19 Jun 2022, at 23:01, The Wanderer wrote:
> On 2022-06-19 at 15:47, Brian wrote:
>
>> On Sun 19 Jun 2022 at 14:54:58 -0400, The Wanderer wrote:
>>
>>> On 2022-06-19 at 14:50, Brian wrote:
>
What does being "precious" involve?
>>>
>>> I'm less certain about this, but my guess is that
On Mon 20 Jun 2022, at 17:34, The Wanderer wrote:
> On 2022-06-20 at 12:01, Brian wrote:
>
>> On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
>>
>>> On 2022-06-20 at 08:59, Brian wrote:
>
The ability to print to an IPP printer involves discovering its
URI. CUPS gets the URI vi
On Mon 20 Jun 2022, at 23:31, Gareth Evans wrote:
> On Mon 20 Jun 2022, at 17:34, The Wanderer wrote:
>> On 2022-06-20 at 12:01, Brian wrote:
>>
>>> On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
>>>
>>>> On 2022-06-20 at 08:59, Brian w
On Mon 20 Jun 2022, at 23:50, Gareth Evans wrote:
> On Mon 20 Jun 2022, at 23:31, Gareth Evans wrote:
>> On Mon 20 Jun 2022, at 17:34, The Wanderer wrote:
>>> On 2022-06-20 at 12:01, Brian wrote:
>>>
>>>> On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer
On Tue 21 Jun 2022, at 18:06, gene heskett wrote:
> On 6/21/22 12:11, Andrew M.A. Cater wrote:
>> On Tue, Jun 21, 2022 at 11:55:56AM -0400, gene heskett wrote:
>>> Greetings all;
>>>
>>> So how am I supposed to read these installed docs?
>>>
>>> Thanks all.
>>>
>>> Cheers, Gene Heskett.
>>> --
>>
On Tue 21 Jun 2022, at 20:16, gene heskett wrote:
> On 6/21/22 14:09, Gareth Evans wrote:
>> On Tue 21 Jun 2022, at 18:06, gene heskett wrote:
>>> On 6/21/22 12:11, Andrew M.A. Cater wrote:
>>>> On Tue, Jun 21, 2022 at 11:55:56AM -0400, gene heskett wrote:
>>&
> On 21 Jun 2022, at 22:12, Gareth Evans wrote:
>
> On Tue 21 Jun 2022, at 20:16, gene heskett wrote:
>>> On 6/21/22 14:09, Gareth Evans wrote:
>>> On Tue 21 Jun 2022, at 18:06, gene heskett wrote:
>>>> On 6/21/22 12:11, Andrew M.A. Cater wrote:
&
> On 21 Jun 2022, at 22:37, Gareth Evans wrote:
>
>
>
>> On 21 Jun 2022, at 22:12, Gareth Evans wrote:
>>
>> On Tue 21 Jun 2022, at 20:16, gene heskett wrote:
>>>> On 6/21/22 14:09, Gareth Evans wrote:
>>>> On Tue 21 Jun 2022,
On Wed 22 Jun 2022, at 18:22, gene heskett wrote:
> On 6/22/22 10:45, Gareth Evans wrote:
>>
>>> On 21 Jun 2022, at 22:37, Gareth Evans wrote:
>>>
>>>
>>>
>>>> On 21 Jun 2022, at 22:12, Gareth Evans wrote:
>>>>
>>>
On Wed 22 Jun 2022, at 21:16, gene heskett wrote:
> On 6/22/22 10:45, Gareth Evans wrote:
> [and I sniped a few kilobytes of.]
>
> I think I've got it, but I did find what may be a bug in mod auth_plain.
>
> Its asking for a username and pw, but nothing seems to satisfy i
On Wed 22 Jun 2022, at 22:42, gene heskett wrote:
> On 6/22/22 16:51, Gareth Evans wrote:
>> On Wed 22 Jun 2022, at 21:16, gene heskett wrote:
>>> On 6/22/22 10:45, Gareth Evans wrote:
>>> [and I sniped a few kilobytes of.]
>>>
>>> I think I'
> On 23 Jun 2022, at 01:46, gene heskett wrote:
>
> On 6/22/22 19:39, Gareth Evans wrote:
>>> On Wed 22 Jun 2022, at 22:42, gene heskett wrote:
>>> On 6/22/22 16:51, Gareth Evans wrote:
>>>> On Wed 22 Jun 2022, at 21:16, gene heskett wrote:
>
> On 23 Jun 2022, at 21:49, gene heskett wrote:
>
> On 6/23/22 16:08, Gareth Evans wrote:
>> OK. That's not something I can help with from scratch, but I will watch
>> with interest for further discussion.
>>
>> Best wishes,
>> G
> Well, it w
On Thu 16 Jun 2022, at 22:13, Hans wrote:
> Hi folks,
>
> I am struggeling with a little problem, I can not explain.
>
> A friend of mine uses a printer (Samsung SL-C480FW), which is connected to
> the
> router with wireless. However, although there are no drivers and no ppd-files
> installed,
After troubleshooting assistance from the Debian Printing team, I was advised
to report my non-printing driverless printer issue upstream, which I have done.
https://github.com/OpenPrinting/cups-filters/issues/472
Given that driverless printing works in CUPS 2.4 (on Ubuntu 22.04) are they
likel
Having found ufw suited my needs I have only dabbled with firewalld /
firewall-config / firewall-applet over the years.
Having noticed the recommendation for firewalld on the debian wiki re nftables
https://wiki.debian.org/nftables#Use_firewalld
I installed it and had a look at the default rul
On Sat 9 Jul 2022, at 07:17, Gareth Evans wrote:
[...]
> If there is no drop by default, why add "policy accept" for
> related/established as it does? Doesn't this happen anyway?
I suppose this probably modifies behaviour for otherwise closed ports (which
would make
On Sat 9 Jul 2022, at 10:05, Roger Price wrote:
> On Sat, 9 Jul 2022, Gareth Evans wrote:
>
>> Also for any good nft/netfilter overview articles etc.
>
> Have you seen "Mastering Linux Security and Hardening", 2nd Edition, Donald
> A.
> Tevault, chapter 4.
On Sun 10 Jul 2022, at 15:38, Roger Price wrote:
[...]
> I removed the ipv6.disable=1 and rebooted, but this made no difference.
I'm not sure if there may be other issues here too, but did you update-grub
before rebooting?
If not, does /etc/hosts currently contain
localhost ::1
?
If so, it
On Sun 10 Jul 2022, at 17:12, Gareth Evans wrote:
> https://unix.stackexchange.com/questions/407663/ipv6-socket-creation-failed-address-family-not-supported-by-protocol
FWIMBW, this explains how to disable ipv6 for exim4 (albeit on Deb 9) though
I'm not sure the advice re hosts
On Sun 10 Jul 2022, at 18:28, Greg Wooledge wrote:
> Mine contains these lines:
>
> unicorn:~$ grep ::1 /etc/hosts
> ::1 localhost ip6-localhost ip6-loopback
> ff02::1 ip6-allnodes
>
> They were put there by Debian. I didn't touch them.
[I got the ::1 and localhost the wrong way around in m
On Sun 10 Jul 2022, at 06:25, Gareth Evans wrote:
> Thanks Roger, that also suggests "policy drop" in its nftables examples.
As someone on firewalld-users kindly pointed out, there is
> table inet firewalld {
> chain filter_INPUT {
[...]
> reject with
On Tue 12 Jul 2022, at 10:19, Maximiliano Estudies
wrote:
> drop and reject are not equivalent.
Fair enough
[...]
> In most cases it's a best practice to configure all chains with
> _policy drop_ and then add rules for the traffic that you want to
> allow
All the nftables and PF howtos I hav
> On 12 Jul 2022, at 11:31, mick crane wrote:
> On 2022-07-12 10:33, Gareth Evans wrote:
>> On Tue 12 Jul 2022, at 10:19, Maximiliano Estudies
>
>>> In most cases it's a best practice to configure all chains with
>>> _policy drop_ and then add rules for
> On 11 Jul 2022, at 17:48, Ram Ramesh wrote:
[...]
> . However, my new machine has this daemon running which notices that $extif
> does not have much activity and disables it after some timeout idle time.
> Today I noticed that my $extif is vanishing and /var/log/daemon.log shows
> some av
On Wed 13 Jul 2022, at 01:21, Ram Ramesh wrote:
> Do you know a simple way to disable autopowerdown of
> just this usb NIC? May be there is something that I can do with ethtool?
I wonder if powertop may be of use here.
It has a "tunables" section where (I think) power-saving features can be
> On 13 Jul 2022, at 18:21, gene heskett wrote:
> I give up, the driverless printer cups installs automaticaly cannot be
> deleted and has
> taken over from the brother drivers that work, preventing me from using the
> printer at all.
>
> So how do I disable the driverless junk? Is that a se
On Wed 13 Jul 2022, at 20:36, Brian wrote:
> On Wed 13 Jul 2022 at 20:12:28 +0100, Gareth Evans wrote:
[...]
>>
>> Hi Gene,
>>
>> Out of interest, which model printer(s) has the issue?
>>
>> There are options in
>>
>> /etc/cups/cupsd.
> On 13 Jul 2022, at 22:04, gene heskett wrote:
> On 7/13/22 15:15, Gareth Evans wrote:
>> [...]
>> Out of interest, which model printer(s) has the issue?
> Brother MFC-J6920DW A huge tabloid capable printer/scanner
>> # lpinfo -v
> first off, none of that stuff i
On Thu 14 Jul 2022, at 01:03, Ram Ramesh wrote:
[...]
> I take back some of what I said. It is both - I mean usb
> autosupend+avahi_daemon. I need to keep the adaptor from autosuspending
> and tell avahi-daemon not to disable the interface in the OS.
>
> I also found the power/control entry in /
On Thu 14 Jul 2022, at 02:08, gene heskett wrote:
> it printed a test page
Good. I'm afraid I don't know of a workaround for tray selection.
This site
https://productz.com/en/brother-mfc-j6920dw/p/LZbAV
suggests the printer concerned is airprint/fax-capable, and given:
> On Wed 13 Jul 2022
Hello,
$ sudo crontab -l | grep reboot
[...]
[1] @reboot sleep 10; nmcli c up
[2] @reboot for f in $(zfs list -t snap -o name|grep reboot); do zfs destroy
$f;done
[3] @reboot zfs snap -r rpool@reboot
[1] succeeds, but [2,3] do not.
Any ideas why would be gratefully received.
Many thanks,
Gare
$ sudo crontab -l
[...]
@reboot for f in $(/usr/sbin/zfs list -t snap -o name|grep reboot); do
/usr/sbin/zfs destroy $f;done
@reboot /usr/sbin/zfs snap -r rpool@reboot
Prepending "/usr/sbin/" to "zfs" doesn't make a difference.
Thanks,
Gareth
Hi Greg,
On Sat 16 Jul 2022, at 04:07, Greg Wooledge wrote:
[...]
> "Well, read the email that cron sends you and see what the errors are."
[amongst others]
/bin/sh: 1: zfs: not found
suggests the need for /usr/sbin/zfs
It seems reasonable that /usr/sbin/* should be available to root crontab
On Sat 16 Jul 2022, at 05:30, Gareth Evans wrote:
> Why isn't root's $PATH available to root crontab? ie. including the
> link /sbin -> /usr/sbin?
By which I mean: why can't root crontab do everything sudo can do?
Thanks
G
> On 16 Jul 2022, at 14:39, Anssi Saari wrote:
>
> Tixy writes:
>
>> rc.local is still run on the latest Debian stable. You need to make
>> sure it's a proper executable, i.e. starts with a shebang like
>> '#!/bin/sh' and the file has execute permissions.
>
> Yes and that's because the sys
> On 25 Jul 2022, at 13:03, Schwibinger Michael wrote:
>
>
> Hello
> Ist the best way to repair
> the self check?
>
> HP 600
Hi Sophie, please would you confirm the exact model - eg Deskjet 600, OfficeJet
600, something else?
If you can't tell from looking at the machine, then running the
On Wed 27 Jul 2022, at 22:28, Gareth Evans wrote:
>> On 25 Jul 2022, at 13:03, Schwibinger Michael wrote:
>>
>> Hello
>> Ist the best way to repair
>> the self check?
>>
>> HP 600
>
> Hi Sophie, please would you confirm the exact model -
1 - 100 of 247 matches
Mail list logo
