Re: Debian 11 upgrade to Debian 12

[Luna Jernberg]

Worked good on my Raspberry Pi 3 with Unstable today too :)

On 3/2/23, songbird  wrote:
> Timothy M Butterworth wrote:
>> All,
>>
>> I just updated my media center PC from Debian Bullseye to Debian
>> Bookworm.
>> The upgrade went alright. I initially had to download almost 2GB of 1640
>> packages. Around 600 failed to upgrade and I had to manually install them
>> in small chunks to fix the dependencies. Other than that the upgrade went
>> relatively smoothly and I am liking the new color scheme and wallpapers.
>>
>> Anyone else have any good or bad experiences upgrading to bookworm.
>
>   considering it's not released yet and has 331 RC bugs still to
> be dealt with (or ignored) that's a bit of a jumping the start
> line signal.
>
>   helping to find bugs is good though too.  :)
>
>
>   songbird
>
>

Re: does your Thunderbird for deb11 often become unresponsive?

[Jeremy Ardley]

On 3/3/23 12:02, hlyg wrote:
at first i suspect Thunderbird(TB) try to access some sites that are 
blocked in china


i disable show Start Page when it launches

i disable check email automatically for each account

but it becomes unresponsive when i File->New->Message

i really don't know cause of unresponsiveness

PS: even if blocked sites cause trouble, it's bug of TB, it shall 
timeout after it can't access sites for some time



Thunderbird for Windows often goes slow without any network problems.

I have thunderbird in deb11 go slow sometimes but that's usually from 
some connection problem to a server, including gmail.



--
Jeremy
(Lists)

Re: solution to / full

[Richard Hector]

On 2/03/23 06:00, Andy Smith wrote:

Hi,

On Wed, Mar 01, 2023 at 02:35:17PM +0100, lina wrote:

My / is almost full.

# df -h
Filesystem  Size  Used Avail Use% Mounted on
udev126G 0  126G   0% /dev
tmpfs26G  2.3M   26G   1% /run
/dev/nvme0n1p2   23G   21G  966M  96% /
tmpfs   126G   15M  126G   1% /dev/shm
tmpfs   5.0M  4.0K  5.0M   1% /run/lock
/dev/nvme0n1p6  267M   83M  166M  34% /boot
/dev/nvme0n1p1  511M  5.8M  506M   2% /boot/efi
/dev/nvme0n1p3  9.1G  3.2G  5.5G  37% /var
/dev/nvme0n1p5  1.8G   14M  1.7G   1% /tmp
/dev/nvme0n1p7  630G  116G  482G  20% /home


This is an excellent illustration of why creating tons of partitions
like it's 1999 can leave you in a difficult spot. You are bound to
make poor guesses as to what actual size you need, which leads later
situations where some partitions are hardly used while others get
full.


Of course you can also get into this situation if you had everything in 
one filesystem, and ran out of space, and had to split off /home, /var 
etc to save room ...


Richard

Re: Forcing dhclient to not ignore tun0 interface when it's available

[Tim Woodall]

On Fri, 3 Mar 2023, Max Nikulin wrote:


On 03/03/2023 10:08, Tim Woodall wrote:

New to this thread, so might be totally off-piste but openvpn has hooks
to run scripts like this:

...

This is server side but the route-up/pre-down work client side too.

Presumably you can do something here to renew dhcp leases or restore
resolv.conf.


Perhaps the opposite. dhclient running for enp2s0f0 should detect that VPN is 
active and to avoid overwriting DNS settings that direct requests to tun0.



The hook can create and delete a file like rhis:
tim@dirac:/etc/dhcp (none)$ cat dhclient-enter-hooks.d/nodnsupdate
make_resolv_conf() {
:
}

Re: Forcing dhclient to not ignore tun0 interface when it's available

[Max Nikulin]

On 03/03/2023 10:08, Tim Woodall wrote:

New to this thread, so might be totally off-piste but openvpn has hooks
to run scripts like this:

...

This is server side but the route-up/pre-down work client side too.

Presumably you can do something here to renew dhcp leases or restore
resolv.conf.


Perhaps the opposite. dhclient running for enp2s0f0 should detect that 
VPN is active and to avoid overwriting DNS settings that direct requests 
to tun0.

Re: Forcing dhclient to not ignore tun0 interface when it's available

[David Wright]

On Thu 02 Mar 2023 at 11:44:17 (+0100), daven...@tuxfamily.org wrote:
> 
> I finally had the time to dig into the logs from two days ago, when
> the problem happens again
> It seems that dhclient does it requests trying different interfaces
> EXCEPT tun0 (see syslog below)
> 
> I looked into /etc/dhcp/dhclient.conf, which mostly commented. In the
> non-commented part shown below
> I don't see anything related to which interfaces are to be used as
> arguments when dhclient is executed
> But I'm not a dhclient expert.
> 
> At boot time/without VPN, dhclient is executed with enp.* interface
> accondinng to systemctl/ps -eFH.
> But It still tries different interfaces according to logs. And I have
> no idea how it detects
> which interfaces to use for it requests and why it doesn't detect tun0.
> Maybe because tun0 is not yet exposed by the system at boot time when
> dhclient is started?
> 
> It stills try wlan interface even if it is down, which is weird, but
> doesn't seem to do harm except
> spamming syslog and spending a few additional seconds before trying
> another interface.

It's not clear what the status of your vpn was when the logs were
written, AFAICT. It's obviously not soon after booting, as you have
processes running with PIDs in the 40,000s.

It would make sense to start and stop the vnc from a terminal in which
script (bsdutils) was running, preferably with -T to add timestamps to
each command. You could then reconcile the logs with what you were doing.

> 
> dave@debian-laptop:~$ systemctl status
> 
>  ├─ifup@enp2s0f0.service
>  │ └─1093 /sbin/dhclient -4 -v -i -pf
> /run/dhclient.enp2s0f0.pid -lf /var/lib/dhcp/dhclient.enp2s0f0.leases
> -I -df /var/lib/dhcp/dhclient6.enp2s0f0.leases enp2s0f0
> 
> 

I don't know why ifupdown is running, as I thought you were
controlling the network with connman.

> dave@debian-laptop:~$ sudo ausearch --interpret --file /etc/resolv.conf
> 
> type=PROCTITLE msg=audit(28/02/2023 14:30:57.787:658) : proctitle=mv
> -f /etc/resolv.conf.dhclient-new.46082 /etc/resolv.conf
> type=PATH msg=audit(28/02/2023 14:30:57.787:658) : item=3
> name=/etc/resolv.conf inode=786809 dev=fd:01 mode=file,644 ouid=root
> ogid=root rdev=00:00 nametype=DELETE cap_fp=none cap_fi=none cap_fe=0
> cap_fver=0 cap_frootid=0
> type=PATH msg=audit(28/02/2023 14:30:57.787:658) : item=2
> name=/etc/resolv.conf.dhclient-new.46082 inode=786811 dev=fd:01
> mode=file,644 ouid=root ogid=root rdev=00:00 nametype=DELETE
> cap_fp=none cap_fi=none cap_fe=0 cap_fver=0 cap_frootid=0
> type=PATH msg=audit(28/02/2023 14:30:57.787:658) : item=1 name=/etc/
> inode=783361 dev=fd:01 mode=dir,755 ouid=root ogid=root rdev=00:00
> nametype=PARENT cap_fp=none cap_fi=none cap_fe=0 cap_fver=0
> cap_frootid=0
> type=PATH msg=audit(28/02/2023 14:30:57.787:658) : item=0 name=/etc/
> inode=783361 dev=fd:01 mode=dir,755 ouid=root ogid=root rdev=00:00
> nametype=PARENT cap_fp=none cap_fi=none cap_fe=0 cap_fver=0
> cap_frootid=0
> type=CWD msg=audit(28/02/2023 14:30:57.787:658) : cwd=/
> type=SYSCALL msg=audit(28/02/2023 14:30:57.787:658) : arch=x86_64
> syscall=rename success=no exit=EPERM(Opération non permise)
> a0=0x7ffc38ee0a9e a1=0x7ffc38ee0ac2 a2=0x0 a3=0xfa4d
> items=4 ppid=46082 pid=46093 auid=unset uid=root gid=root euid=root
> suid=root fsuid=root egid=root sgid=root fsgid=root tty=(none)
> ses=unset comm=mv exe=/usr/bin/mv subj=unconfined key=(null)
> 
> 
> Note : exit=EPERM can be ignored, because it happened while I made
> /etc/resolv.conf immutable

This appears to show mv -f /etc/resolv.conf.dhclient-new.46082 /etc/resolv.conf
failing, as expected.

> 
> 
> dave@debian-laptop:~$ less /var/log/syslog
> Feb 28 14:30:48 debian-laptop dhclient[2016]: DHCPDISCOVER on wlp3s0
> to 255.255.255.255 port 67 interval 3
> Feb 28 14:30:51 debian-laptop dhclient[39759]: DHCPDISCOVER on
> enx8c8caa616f43 to 255.255.255.255 port 67 interval 5
> Feb 28 14:30:51 debian-laptop dhclient[2016]: DHCPDISCOVER on wlp3s0
> to 255.255.255.255 port 67 interval 4
> Feb 28 14:30:55 debian-laptop dhclient[2016]: DHCPDISCOVER on wlp3s0
> to 255.255.255.255 port 67 interval 11
> Feb 28 14:30:56 debian-laptop dhclient[39759]: DHCPDISCOVER on
> enx8c8caa616f43 to 255.255.255.255 port 67 interval 9
> Feb 28 14:30:57 debian-laptop dhclient[1003]: DHCPREQUEST for
> 192.168.1.192 on enp2s0f0 to 192.168.1.1 port 67
> Feb 28 14:30:57 debian-laptop dhclient[1003]: DHCPACK of 192.168.1.192
> from 192.168.1.1
> Feb 28 14:30:57 debian-laptop connmand[1038]: enp2s0f0 {add} address
> 192.168.1.192/24 label enp2s0f0 family 2
> Feb 28 14:30:57 debian-laptop avahi-daemon[1034]: Registering new
> address record for 192.168.1.192 on enp2s0f0.IPv4.
> Feb 28 14:30:57 debian-laptop dhclient[1003]: bound to 192.168.1.192
> -- renewal in 17866 seconds.

One might expect this to be where mv -f fails.

> Feb 28 14:31:05 debian-laptop dhclient[39759]: DHCPDISCOVER on
> enx8c8caa616f43 to 

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[David Wright]

On Thu 02 Mar 2023 at 10:32:41 (+0100), daven...@tuxfamily.org wrote:
> On 2023-03-02 00:24, David Wright wrote:
> > On Tue 28 Feb 2023 at 16:05:14 (+0100), daven...@tuxfamily.org wrote:
> > > On 2023-02-28 05:27, David Wright wrote:
> > > > On Thu 23 Feb 2023 at 11:23:30 (+0100), daven...@tuxfamily.org wrote:
> > > > > On 2023-02-23 02:59, cono...@panix.com wrote:
> >  [ … ]
> > 
> > Well, it looks like cruft from an earlier installation of networking;
> > and a couple of months later, you installed ifupdown and wpasupplicant,
> > by the looks of things. I don't know whether /etc/network/interfaces
> > itself would interfere with however connman is configured.
> > 
> 
> This system never had any debian 10 or lower. It has been issued to my
> by $worksplace
> in december 2021, initially running windows.
> 
> I erased the full disk and installed à "default" (official image)
> debian 11, from an LXDE live USB image

I know nothing about LXDE (or other DEs).

> It has never had any interface named eth0. I still fail to see why
> setup conf would refer to eth0 at all

Some clues are the setup's contents, other files on the system with
contemporaneous timestamps, /var/log/installer/syslog's contents, and so on.

> Then I few month later, I finally took the time to debug why WiFi card
> didn't work/what firmware is needed
> Debian's firmware packaged started supporting the WLAN/WiFi card
> after I installed my system.
> 
> So then I installed the firmware. I most likely installed wpasuppicant
> the same day, and tested it worked.
> 
> Not sure about ifup thought. Doesn't seem to be a wpasupplicant
> dependency.
> 
> akb@akira:~$ LC_ALL=C aptitude why ifupdown
> p   netscript-2.4 Provides ifupdown
> p   netscript-2.4 Depends  bridge-utils (>= 0.9.3)
> p   bridge-utils  Suggests ifupdown
> akb@akira:~$ LC_ALL=C aptitude why netscript-2.4
> p   netscript-2.4 Provides ifupdown

This suggests that you or the installer installed ifupdown, and that
it's a top-level package. I would have expected a response more like:

  $ aptitude why apt-file
  Manually installed, current version 3.2.2, priority optional
  No dependencies require to install apt-file
  $ 

but I guess the Provides has some influence. Both ifupdown2 and
netscript can be used instead of ifupdown, though the latter is
for a more specialised scenario.

It's always possible that ifupdown was installed as an alternative
to connman, which is also in the Live image. I don't know which gets
started by default, either in Live, or the subsequent installation
from Live.

> Why openresolv wouldn't work?

That doesn't parse, and without any context, I don't know what it means.

Cheers,
David.

Re: solution to / full

[David Wright]

On Thu 02 Mar 2023 at 18:09:06 (-0500), songbird wrote:
> Joe wrote:
> ...
> > On unstable, I have a /var/cache/apt/archives directory, from which apt
> > autoclean, which I do occasionally, recently removed about 5G of
> > packages (obviously too occasionally). There's still quite a bit there
> > as it was only autoclean and I prefer to keep downloads around for a
> > while, as this is unstable.
> 
>   yes, i prefer to keep at least one version back from the
> most recent, but apt-get autoclean doesn't do that either
> so once in a while i run that manually and hope for the best.
> 
>   a Keep_Plus_One flag would be nice.  :)

apt-cacher-ng will do that, with modification to acng.conf:

  # Regular expiration algorithm finds package files which are no longer listed
  # in any index file and removes them of them after a safety period.
  # This option allows to keep more versions of a package in the cache after
  # the safety period is over.
  # 
  # KeepExtraVersions: 0

Cheers,
David.

Re: Building binary package, howto enable init.d/systemd start

[Tim Woodall]

On Thu, 2 Mar 2023, Konstantin Kletschke wrote:


In debian/rules is:

#!/usr/bin/make -f

DH_VERBOSE=1

%:
dh $@
clean:
@# Do nothing

build:
@# Do nothing

binary:
mkdir -p debian/loqitmon
mkdir -p debian/loqitmon/usr/
mkdir -p debian/loqitmon/usr/bin
cp loqitmon.py debian/loqitmon/usr/bin/loqitmon
mkdir -p debian/loqitmon/etc
cp loqitmon.ini debian/loqitmon/etc
cp loqitmonaction1 debian/loqitmon/usr/bin
cp loqitmonaction2 debian/loqitmon/usr/bin
cp loqitmonaction3 debian/loqitmon/usr/bin
cp loqitmonstep1 debian/loqitmon/usr/bin
cp loqitmonstep2 debian/loqitmon/usr/bin
cp loqitmonstep3 debian/loqitmon/usr/bin
dh_installinit
dh_installsystemd
dh_gencontrol
dh_install
dh_auto_install
dh_builddeb



I'm no expert. Have you tried manually setting up the directory
structure then using the default dh $@ instead of overriding the binary
step?

I wonder if you're missing something - the error about conffiles is
suspicious, I think that should be automatic.


This is a layout of one of my simple deb-src packages:

apt-mirror@aptmirror17:/mnt/mirror/ftp/mirror/local/pool/main/b/backup
(none)$ tar tvJf backup_1.11+tjw99r1.tar.xz
drwxr-xr-x 0/0   0 2022-05-06 17:52 package/
-rw-r--r-- 0/0 213 2022-04-29 18:02 package/Makefile
drwxr-xr-x 0/0   0 2022-10-12 06:43 package/debian/
-rw-r--r-- 0/0  57 2022-05-07 08:20 package/debian/backup.install
-rw-r--r-- 0/01499 2022-10-12 06:43 package/debian/changelog
-rw-r--r-- 0/0   3 2022-04-28 22:32 package/debian/compat
-rw-r--r-- 0/0 337 2022-04-28 22:32 package/debian/control
-rw-r--r-- 0/01307 2022-04-28 22:03 package/debian/copyright
-rwxr-xr-x 0/0 298 2021-03-13 20:40 package/debian/postinst
-rwxr-xr-x 0/0 438 2021-03-02 17:40 package/debian/postrm
-rwxr-xr-x 0/0 548 2022-04-29 17:45 package/debian/rules
drwxr-xr-x 0/0   0 2022-05-06 17:52 package/debian/source/
-rw-r--r-- 0/0  13 2021-03-02 17:40 package/debian/source/format
drwxr-xr-x 0/0   0 2021-03-02 17:40 package/src/
drwxr-xr-x 0/0   0 2021-03-02 17:40 package/src/etc/
drwxr-xr-x 0/0   0 2022-05-06 17:51 package/src/etc/backup/
-rw-r--r-- 0/02752 2021-11-07 10:46 
package/src/etc/backup/backup.conf
drwxr-xr-x 0/0   0 2022-08-20 07:09 package/src/etc/cron.d/
-rw-r--r-- 0/0 145 2021-06-22 07:00 package/src/etc/cron.d/backup
drwxr-xr-x 0/0   0 2021-03-02 17:40 package/src/usr/
drwxr-xr-x 0/0   0 2022-09-27 03:26 package/src/usr/sbin/
-rwxr-xr-x 0/04081 2022-09-27 03:21 package/src/usr/sbin/backup

This is all that that Makefile does:
apt-mirror@aptmirror17:/mnt/mirror/local-debs/main/b/backup/package (master)$ 
cat Makefile
.PHONY: all install

FILES ::= $(shell [ -d src ] && find src -mindepth 1 -maxdepth 1 )

all:

install:
ifdef FILES
mkdir -p $(DESTDIR)
for i in $(FILES); do \
  cp -dR $$i $(DESTDIR)/$${i#src/}; \
done
endif

And this is the content of debian/rules:
apt-mirror@aptmirror17:/mnt/mirror/local-debs/main/b/backup/package (master)$ 
cat debian/rules
#!/usr/bin/make -f
# See debhelper(7) (uncomment to enable)
# output every command that modifies files on the build system.
#export DH_VERBOSE = 1


# see FEATURE AREAS in dpkg-buildflags(1)
#export DEB_BUILD_MAINT_OPTIONS = hardening=+all

# see ENVIRONMENT in dpkg-buildflags(1)
# package maintainers to append CFLAGS
#export DEB_CFLAGS_MAINT_APPEND  = -Wall -pedantic
# package maintainers to append LDFLAGS
#export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed


%:
dh $@

override_dh_auto_install:
$(MAKE) install DESTDIR=$(CURDIR)/debian/tmp



And here is the .install file:
apt-mirror@aptmirror17:/mnt/mirror/local-debs/main/b/backup/package (master)$ 
cat debian/backup.install
etc/backup/backup.conf
etc/cron.d/backup
usr/sbin/backup

Re: solution to / full

[songbird]

Andy Smith wrote:
> Hello,
>
> On Wed, Mar 01, 2023 at 07:53:19PM +0100, Nicolas George wrote:
>> Andy Smith (12023-03-01):
>> > > /dev/nvme0n1p2   23G   21G  966M  96% /
>> > > /dev/nvme0n1p6  267M   83M  166M  34% /boot
>> > > /dev/nvme0n1p1  511M  5.8M  506M   2% /boot/efi
>> > > /dev/nvme0n1p3  9.1G  3.2G  5.5G  37% /var
>> > > /dev/nvme0n1p5  1.8G   14M  1.7G   1% /tmp
>> > > /dev/nvme0n1p7  630G  116G  482G  20% /home
>> > This is an excellent illustration of why creating tons of partitions
>> > like it's 1999 can leave you in a difficult spot.
>> 
>> No it is not. The /boot and /tmp partitions are superfluous, and
>> /boot/efi is too large (but at a guess it was already there), but they
>> would barely make a difference.
>
> I was talking about them going to the effort of separating /home and
> /var and ending up with completely inappropriate sizings. They would
> have been much better off just not bothering and having it all in /.
> The mere presence of all these other partitions laid out on this
> disk after the one for / makes resizing things a lot harder than it
> needs to be.

  yes, but old habits can die hard... and there weren't
these wonderful gadgets called SSDs around.  in my own more 
recent installations i got away from too much fragmentation 
and i'm glad for that as then i do have more space to work 
with.

  mainly the other partitions are now backup, pictures or
a spare bootable stable partition and that has been working 
out well.

  i do not do llvm because i don't have that much need for
that level of complexity.


>> On the other hand, in 2023, it is still a very good idea to separate the
>> system filesystem that gets written frequently from the one that gets
>> written rarely from the user data filesystem.
>
> No argument there, but not with disk partitions as they end up hard
> to resize, as seen here. OP is quite fortunate that their last
> partition is one that can be most easily shrunk as that at least
> gives them some easier options. I'd agree it would be a better
> example of a tight spot if their last partition were one they
> couldn't shrink!

  i could find a lot of space by deduping backups and pictures
but that is on my TODO list for the year 2026 at the rate i'm
going.  it may end up being much more time efficient to just
go out and buy another 2TB SSD and swap that for my smaller 
one and call it good enough.


  songbird

does your Thunderbird for deb11 often become unresponsive?

[hlyg]

at first i suspect Thunderbird(TB) try to access some sites that are 
blocked in china


i disable show Start Page when it launches

i disable check email automatically for each account

but it becomes unresponsive when i File->New->Message

i really don't know cause of unresponsiveness

PS: even if blocked sites cause trouble, it's bug of TB, it shall 
timeout after it can't access sites for some time

Re: solution to / full

[songbird]

Joe wrote:
...
> On unstable, I have a /var/cache/apt/archives directory, from which apt
> autoclean, which I do occasionally, recently removed about 5G of
> packages (obviously too occasionally). There's still quite a bit there
> as it was only autoclean and I prefer to keep downloads around for a
> while, as this is unstable.

  yes, i prefer to keep at least one version back from the
most recent, but apt-get autoclean doesn't do that either
so once in a while i run that manually and hope for the best.

  a Keep_Plus_One flag would be nice.  :)


  songbird

Re: Debian 11 upgrade to Debian 12

[songbird]

Timothy M Butterworth wrote:
> All,
>
> I just updated my media center PC from Debian Bullseye to Debian Bookworm.
> The upgrade went alright. I initially had to download almost 2GB of 1640
> packages. Around 600 failed to upgrade and I had to manually install them
> in small chunks to fix the dependencies. Other than that the upgrade went
> relatively smoothly and I am liking the new color scheme and wallpapers.
>
> Anyone else have any good or bad experiences upgrading to bookworm.

  considering it's not released yet and has 331 RC bugs still to
be dealt with (or ignored) that's a bit of a jumping the start
line signal.

  helping to find bugs is good though too.  :)


  songbird

Re: Forcing dhclient to not ignore tun0 interface when it's available

[Tim Woodall]

On Thu, 2 Mar 2023, daven...@tuxfamily.org wrote:


Hello

On 2023-02-24 10:19, daven...@tuxfamily.org wrote:

Hello,


[?]


Otherwise, when VPN is disconnected, I DO want /etc/resolv.conf to be
generated according to my home router's DHCP tells the computer


? yes, that one.

Cheers,
David.


I?finally had the time to dig into the logs from two days ago, when the 
problem happens again
It seems that dhclient does it requests trying different interfaces EXCEPT 
tun0 (see syslog below)




New to this thread, so might be totally off-piste but openvpn has hooks
to run scripts like this:

script-security 2
route-up "/etc/network/scripts/openvpn-tun0-up"
route-pre-down "/etc/network/scripts/openvpn-tun0-down"
client-connect "/etc/network/scripts/openvpn-client-connect"
client-disconnect "/etc/network/scripts/openvpn-client-disconnect"

This is server side but the route-up/pre-down work client side too.

Presumably you can do something here to renew dhcp leases or restore
resolv.conf.

I'd assume whatever vpn you're using will have similar hooks, or
possibly you xan use the default ones in /etc/network?

Tim

GNOME 43.3 performance issues after Debian Testing update (March 1)

[moura3950]

Dear Mantainer,

After the last update, the GNOME desktop animations have not been
smooth, and things only turn fluid again after setting the performance
mode. I am 100% sure that hardware isn't the problem here as this issue
didn't occur before the upgrade.

This issue however is not like the one that GNOME 3.30 had. What
happens here is that there are noticeable and random frame drops in the
animations.

It happens on Wayland and Xorg.

===
The packages that were upgraded (and probably are related to the issue)
===
manpages-dev:amd64 (6.02-1, 6.03-1),
libtss2-tcti-cmd0:amd64 (3.2.1-2, 3.2.1-3),
avahi-autoipd:amd64 (0.8-8, 0.8-9),
tzdata:amd64 (2022g-5, 2022g-7),
yt-dlp:amd64 (2023.01.06-1, 2023.02.17-1),
libpipewire-0.3-common:amd64 (0.3.65-2, 0.3.65-3),
pipewire-pulse:amd64 (0.3.65-2, 0.3.65-3),
libtss2-tcti-device0:amd64 (3.2.1-2, 3.2.1-3),
libavahi-common-data:amd64 (0.8-8, 0.8-9),
libavahi-common-data:i386 (0.8-8, 0.8-9),
libavahi-core7:amd64 (0.8-8, 0.8-9),
libmutter-11-0:amd64 (43.2-6, 43.3-3),
libtss2-tcti-swtpm0:amd64 (3.2.1-2, 3.2.1-3),
libtiffxx6:amd64 (4.5.0-4, 4.5.0-5),
linux-compiler-gcc-12-x86:amd64 (6.1.8-1, 6.1.12-1),
libtiff6:amd64 (4.5.0-4, 4.5.0-5),
libtiff6:i386 (4.5.0-4, 4.5.0-5),
linux-cpupower:amd64 (6.1.8-1, 6.1.12-1),
avahi-daemon:amd64 (0.8-8, 0.8-9),
linux-headers-amd64:amd64 (6.1.8-1, 6.1.12-1),
pipewire:amd64 (0.3.65-2, 0.3.65-3),
libtss2-mu0:amd64 (3.2.1-2, 3.2.1-3),
mutter-common:amd64 (43.2-6, 43.3-3),
libtss2-rc0:amd64 (3.2.1-2, 3.2.1-3),
linux-kbuild-6.1:amd64 (6.1.8-1, 6.1.12-1),
libfuse3-3:amd64 (3.13.0-2, 3.14.0-2),
linux-image-amd64:amd64 (6.1.8-1, 6.1.12-1),
libspa-0.2-bluetooth:amd64 (0.3.65-2, 0.3.65-3),
manpages:amd64 (6.02-1, 6.03-1),
gir1.2-mutter-11:amd64 (43.2-6, 43.3-3),
gstreamer1.0-pipewire:amd64 (0.3.65-2, 0.3.65-3),
fuse3:amd64 (3.13.0-2, 3.14.0-2),
libtss2-tctildr0:amd64 (3.2.1-2, 3.2.1-3),
libtss2-tcti-mssim0:amd64 (3.2.1-2, 3.2.1-3),
pipewire-audio:amd64 (0.3.65-2, 0.3.65-3),
pipewire-bin:amd64 (0.3.65-2, 0.3.65-3),
libavahi-common3:amd64 (0.8-8, 0.8-9),
libavahi-common3:i386 (0.8-8, 0.8-9),
libtss2-sys1:amd64 (3.2.1-2, 3.2.1-3),
libspa-0.2-modules:amd64 (0.3.65-2, 0.3.65-3),
libavahi-glib1:amd64 (0.8-8, 0.8-9),
sudo:amd64 (1.9.12p2-1, 1.9.13p1-1),
libgnutls30:amd64 (3.7.8-5, 3.7.9-1),
libgnutls30:i386 (3.7.8-5, 3.7.9-1),
libcpupower1:amd64 (6.1.8-1, 6.1.12-1),
libpipewire-0.3-modules:amd64 (0.3.65-2, 0.3.65-3),
libtss2-esys-3.0.2-0:amd64 (3.2.1-2, 3.2.1-3),
xterm:amd64 (378-1, 379-1),
libtiff-dev:amd64 (4.5.0-4, 4.5.0-5),
libavahi-client3:amd64 (0.8-8, 0.8-9),
libavahi-client3:i386 (0.8-8, 0.8-9),
intel-media-va-driver-non-free:amd64 (23.1.0+ds1-1, 23.1.1+ds1-1),
pipewire-alsa:amd64 (0.3.65-2, 0.3.65-3),
linux-libc-dev:amd64 (6.1.8-1, 6.1.12-1),
libpipewire-0.3-0:amd64 (0.3.65-2, 0.3.65-3)
===

===
Sytem Details
===
System:
  Host: moura Kernel: 6.1.0-5-amd64 arch: x86_64 bits: 64 Desktop:
GNOME
v: 43.3 Distro: Debian GNU/Linux bookworm/sid

Machine:
  Type: Laptop System: LENOVO product: 82NM v: Lenovo V14 G2 ITL
serial: 
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40688 WIN
serial:  UEFI: LENOVO v: GGCN29WW date:
08/18/2021

CPU:
  Info: quad core model: 11th Gen Intel Core i7-1165G7 bits: 64 type:
MT MCP
cache: L2: 5 MiB
  Speed (MHz): avg: 2063 min/max: 400/4700 cores: 1: 1352 2: 2800 3:
1268
4: 614 5: 2800 6: 2073 7: 2800 8: 2800

Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v:
kernel
  Device-2: NVIDIA GP107M [GeForce MX350] driver: nvidia v: 525.85.12
  Device-3: Chicony Integrated Camera type: USB driver: uvcvideo
  Display: wayland server: X.Org v: 1.22.1.8 with: Xwayland v: 22.1.8
compositor: gnome-shell driver: X: loaded: modesetting unloaded:
fbdev,vesa
dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 22.3.3 renderer: Mesa Intel Xe Graphics (TGL
GT2)
===

Re: solution to / full

[David Christensen]

On 3/2/23 15:19, Felix Miata wrote:

David Christensen composed on 2023-03-02 14:41 (UTC-0800):
  

How do I make the settings live (other than rebooting, which might hang
if there is a syntax error)?
  
I think this is one of those things that systemctl daemon-reload does.


[quote]
So, it's a "soft" reload, essentially; taking changed configurations from 
filesystem and regenerating dependency trees.
[/quote]
https://unix.stackexchange.com/questions/364782/what-does-systemctl-daemon-reload-do

I know there's a way to confirm syntax, but I never remember what to search for 
to rediscover.



STFW "reload journald.conf" I see:

https://unix.stackexchange.com/questions/253203/how-to-tell-journald-to-re-read-its-configuration


Try a reload:

2023-03-02 15:50:15 root@laalaa ~
# systemctl reload systemd-journald
Failed to reload systemd-journald.service: Job type reload is not 
applicable for unit systemd-journald.service.



Reading the above further, I see that the first answer, third comment, 
shows the same result.  The fourth comment links to:


https://unix.stackexchange.com/questions/379288/reloading-systemd-journald-config


Reading that answer is not encouraging.


Oh, well.  I guess I'll try a restart:

2023-03-02 15:52:49 root@laalaa ~
# systemctl restart systemd-journald

2023-03-02 16:05:08 root@laalaa ~
#


Looks okay (?).


Reboot.


Now I am wondering where to look for systemd errors (?).  STFW "systemd 
error message":


https://unix.stackexchange.com/questions/332886/how-to-see-error-message-in-journald

2023-03-02 16:15:14 root@laalaa ~
# journalctl -p 3 -xb --no-pager
-- Journal begins at Fri 2023-02-24 11:38:23 PST, ends at Thu 2023-03-02 
16:17:01 PST. --
Mar 02 16:06:25 laalaa kernel: iwlwifi :03:00.0: firmware: failed to 
load iwl-debug-yoyo.bin (-2)
Mar 02 16:06:25 laalaa kernel: firmware_class: See 
https://wiki.debian.org/Firmware for information about missing firmware
Mar 02 16:06:30 laalaa pipewire[1165]: Failed to receive portal pid: 
org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 
'org.freedesktop.portal.Desktop': no such name
Mar 02 16:06:36 laalaa lightdm[1227]: gkr-pam: unable to locate daemon 
control file
Mar 02 16:06:36 laalaa pipewire[1247]: Failed to receive portal pid: 
org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 
'org.freedesktop.portal.Desktop': no such name
Mar 02 16:06:38 laalaa kernel: nouveau :01:00.0: firmware: failed to 
load nouveau/nvd9_fuc084 (-2)
Mar 02 16:06:38 laalaa kernel: nouveau :01:00.0: firmware: failed to 
load nouveau/nvd9_fuc084d (-2)
Mar 02 16:06:38 laalaa kernel: nouveau :01:00.0: msvld: unable to 
load firmware data

Mar 02 16:06:38 laalaa kernel: nouveau :01:00.0: msvld: init failed, -19


Nothing about /etc/systemd/journald.conf.d/local.conf.


Check disk usage of /var/log:

2023-03-02 16:13:39 root@laalaa ~
# du -mx -d 1 /var/log | sort -rn
94  /var/log
65  /var/log/journal
15  /var/log/installer
1   /var/log/speech-dispatcher
1   /var/log/samba
1   /var/log/runit
1   /var/log/private
1   /var/log/lightdm
1   /var/log/cups
1   /var/log/apt


Check disk free of root:

2023-03-02 16:15:04 root@laalaa ~
# df /
Filesystem 1M-blocks  Used Available Use% Mounted on
/dev/mapper/sdb3_crypt12084M 6876M 4573M  61% /


It appears my /etc/systemd/journald.conf.d/local.conf is working.  :-)


David

Re: Unable to associate to mobile hotspot

[Charles Curley]

On Thu, 2 Mar 2023 22:38:36 +0100
Lucio Crusca  wrote:

> Yes, there are, but I only posted the logs you asked for (grep -i 
> networkmanager). Here is what wpa-supplicat has to say about the
> problem:

Sorry about that. You are Sid, I'm on Bullseye. Different log file
formats.

I see some lines in there that are suspicious, but I don't know enough
about wpa_supplicant to go further. Anyone else?

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: solution to / full

[Felix Miata]

David Christensen composed on 2023-03-02 14:41 (UTC-0800):
 
> How do I make the settings live (other than rebooting, which might hang 
> if there is a syntax error)?
 
I think this is one of those things that systemctl daemon-reload does.

[quote]
So, it's a "soft" reload, essentially; taking changed configurations from 
filesystem and regenerating dependency trees.
[/quote]
https://unix.stackexchange.com/questions/364782/what-does-systemctl-daemon-reload-do

I know there's a way to confirm syntax, but I never remember what to search for 
to rediscover.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: solution to / full

[David Christensen]

On 3/2/23 14:41, David Christensen wrote:


On 3/2/23 00:53, lina wrote:
 > :/usr/lib$ du -sh * | sort -nr | grep -v K  | head
 > 981M R
 > 591M rstudio
 > 591M jvm
 > 554M mega
 > 538M llvm-11
 > 343M modules
 > 313M libreoffice


So, your computer has 3911M of apps in /usr/share.


Corrections:

So, your computer has 3911M of apps in /usr/lib.



My /usr/share has a somewhat less, but /usr/share is also non-trivial:


My /usr/lib has a somewhat less


David

Re: solution to / full

[David Christensen]

On 3/1/23 05:35, lina wrote:
> My / is almost full.
>
> # df -h
> Filesystem  Size  Used Avail Use% Mounted on
> udev126G 0  126G   0% /dev
> tmpfs26G  2.3M   26G   1% /run
> /dev/nvme0n1p2   23G   21G  966M  96% /


On 3/1/23 15:03, Felix Miata wrote:
> I limit journal size this way:
> # cat /etc/systemd/journald.conf.d/local.conf
> [Journal]
> Storage=persistent
> SystemMaxFiles=10
> RuntimeMaxFiles=12


On 3/1/23 14:53, Jeffrey Walton wrote:
> You can probably reclaim a couple of GB by trimming systemd logs. It
> should get you some room to work. Something like:
>
> journalctl --vacuum-time=14d
>
> I need to clear systemd logs on some IoT gadgets on occasion. They use
> SDcards, though. Not the big, juicy disks you have.


On 3/2/23 00:48, lina wrote:
> Hi all,
>
> Thanks for your suggestions,
>
> I take the least risk way, just move the things from /opt away,
>
> I hope I can make it in the next few months, the biggest problem was
> created by the R associated package.
>
> /dev/nvme0n1p2   23G   18G  4.5G  80% /
>
> Thanks again, lina


On 3/2/23 00:53, lina wrote:
> :/usr/lib$ du -sh * | sort -nr | grep -v K  | head
> 981M R
> 591M rstudio
> 591M jvm
> 554M mega
> 538M llvm-11
> 343M modules
> 313M libreoffice


So, your computer has 3911M of apps in /usr/share.


My /usr/share has a somewhat less, but /usr/share is also non-trivial:

2023-03-02 14:27:31 root@laalaa ~
# du -m -d 2 /usr | sort -rn | head
5113/usr
3158/usr/lib
1578/usr/share
970 /usr/lib/x86_64-linux-gnu
664 /usr/lib/modules
334 /usr/share/locale
286 /usr/lib/libreoffice
252 /usr/lib/go-1.15
215 /usr/lib/firefox-esr
206 /usr/share/doc


Looking at my /var:

2023-03-02 14:29:33 root@laalaa ~
# du -m -d 2 /var | sort -rn | head
1317/var
974 /var/log
945 /var/log/journal
194 /var/lib
123 /var/lib/apt
86  /var/cache
68  /var/cache/apt
61  /var/spool
60  /var/spool/cups
60  /var/lib/dpkg


/var/log/journal is getting big.  Following Felix' and Jeffrey's 
suggestions, and RTFM journald.conf(5) and journalctl(1), I can imagine:


2023-03-02 14:40:48 root@laalaa ~
# cat /etc/systemd/journald.conf.d/local.conf
[Journal]
SystemMaxFileSize=5M
SystemMaxUse=50M
RuntimeMaxFileSize=5M
RuntimeMaxUse=50M


How do I verify the syntax?


How do I make the settings live (other than rebooting, which might hang 
if there is a syntax error)?



David

Re: Building binary package, howto enable init.d/systemd start

[Darac Marjal]

On 02/03/2023 19:56, Konstantin Kletschke wrote:

Dear debian-user Folks,

i am trying to build a binary debian package consisting of a python
script, shell scripts and a config file as daemon with either init.d or
systemd start.

The init.d script gets installed also the systemd file, but both are not
enabled.

I made a directory loqitmon-1.0 and in there are python script,
shellscripts and config file.

In debian/control is:

Source: loqitmon
Section: base
Priority: optional
Maintainer: Konstantin Kletschke 
Build-Depends: debhelper (>=9.0.0), dh-virtualenv (>= 0.8)
Standards-Version: 4.5.1

Package: loqitmon
Architecture: any
Pre-Depends: dpkg (>= 1.16.1), python3, init-system-helpers (>= 1.51~)
Depends: ${misc:Depends}
Description: LoQiT monitoring daemon
  This daemon monitors /var/log/syslog for
  device removal of card reader and removal of
  display and restarts either the X server or
  the entire system accordingly
  Derived from https://github.com/yxiao168/logmonitor.git

In debian/rules is:

#!/usr/bin/make -f

DH_VERBOSE=1

%:
dh $@
clean:
@# Do nothing

build:
@# Do nothing

binary:
mkdir -p debian/loqitmon
mkdir -p debian/loqitmon/usr/
mkdir -p debian/loqitmon/usr/bin
cp loqitmon.py debian/loqitmon/usr/bin/loqitmon
mkdir -p debian/loqitmon/etc
cp loqitmon.ini debian/loqitmon/etc
cp loqitmonaction1 debian/loqitmon/usr/bin
cp loqitmonaction2 debian/loqitmon/usr/bin
cp loqitmonaction3 debian/loqitmon/usr/bin
cp loqitmonstep1 debian/loqitmon/usr/bin
cp loqitmonstep2 debian/loqitmon/usr/bin
cp loqitmonstep3 debian/loqitmon/usr/bin
dh_installinit
dh_installsystemd


This looks relevant, have you read it's manpage?


dh_gencontrol
dh_install
dh_auto_install
dh_builddeb

When I run

# > debuild -b -us -uc

this is the output:

  dpkg-buildpackage -us -uc -ui -b
dpkg-buildpackage: info: source package loqitmon
dpkg-buildpackage: info: source version 1.0-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Konstantin Kletschke 

  dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
  fakeroot debian/rules clean
  debian/rules build
  fakeroot debian/rules binary
mkdir -p debian/loqitmon
mkdir -p debian/loqitmon/usr/
mkdir -p debian/loqitmon/usr/bin
cp loqitmon.py debian/loqitmon/usr/bin/loqitmon
mkdir -p debian/loqitmon/etc
cp loqitmon.ini debian/loqitmon/etc
cp loqitmonaction1 debian/loqitmon/usr/bin
cp loqitmonaction2 debian/loqitmon/usr/bin
cp loqitmonaction3 debian/loqitmon/usr/bin
cp loqitmonstep1 debian/loqitmon/usr/bin
cp loqitmonstep2 debian/loqitmon/usr/bin
cp loqitmonstep3 debian/loqitmon/usr/bin
dh_installinit
dh_installsystemd
dh_gencontrol
dpkg-gencontrol: warning: package loqitmon: substitution variable 
${misc:Pre-Depends} unused, but is defined
dh_install
dh_auto_install
dh_builddeb
dpkg-deb: building package 'loqitmon' in '../loqitmon_1.0-1_amd64.deb'.
  dpkg-genbuildinfo --build=binary -O../loqitmon_1.0-1_amd64.buildinfo
  dpkg-genchanges --build=binary -O../loqitmon_1.0-1_amd64.changes
dpkg-genchanges: info: binary-only upload (no source code included)
  dpkg-source --after-build .
dpkg-buildpackage: info: binary-only upload (no source included)
Now running lintian loqitmon_1.0-1_amd64.changes ...
E: loqitmon changes: bad-distribution-in-changes-file unstable
E: loqitmon: file-in-etc-not-marked-as-conffile etc/init.d/loqitmon
E: loqitmon: file-in-etc-not-marked-as-conffile etc/loqitmon.ini
E: loqitmon: no-changelog usr/share/doc/loqitmon/changelog.Debian.gz 
(non-native package)
E: loqitmon: no-copyright-file
W: loqitmon: no-manual-page usr/bin/loqitmon
W: loqitmon: no-manual-page usr/bin/loqitmonaction1
W: loqitmon: no-manual-page usr/bin/loqitmonaction2
W: loqitmon: no-manual-page usr/bin/loqitmonaction3
W: loqitmon: no-manual-page usr/bin/loqitmonstep1
W: loqitmon: no-manual-page usr/bin/loqitmonstep2
W: loqitmon: no-manual-page usr/bin/loqitmonstep3
W: loqitmon: script-in-etc-init.d-not-registered-via-update-rc.d 
etc/init.d/loqitmon
W: loqitmon: unknown-section base
Finished running lintian.

You probably want to investigate these lintian warnings, at some point.


The files
/etc/init.d/loqitmon
/lib/systemd/system/loqitmon.service
The manpage for dh_installsystemd suggests these files should be under 
debian/. Are they, or are they in etc/init.d and lib/systemd/system?


are in the package, but they are are not enabled.

I have the strange feeling the entire postinstall stuff is missing.
Is there a significant typo somewhere so obvious I am to stupid to see?

If there is a distribution like Mint Tessa for example, how does the
system decide which startmethod to choose, if init.d and systemd are
enabled successfully? I see a mix of init.d and systemd there regading
starting stuff.

Kind Regards
Konstantin




OpenPGP_signature
Description: 

Re: Unable to associate to mobile hotspot

[Lucio Crusca]

Il 02/03/23 20:22, Charles Curley ha scritto:
I would think there would be more lines from the

supplicant.


Yes, there are, but I only posted the logs you asked for (grep -i 
networkmanager). Here is what wpa-supplicat has to say about the problem:


2023-03-02T21:38:57.606785+01:00 t470 wpa_supplicant[679]: wlp4s0: 
Trying to associate with e2:2f:70:ee:a8:a9 (SSID='papospot' freq=5745 MHz)
2023-03-02T21:38:57.607570+01:00 t470 NetworkManager[678]:  
[1677789537.6074] device (wlp4s0): supplicant interface state: 
authenticating -> associating
2023-03-02T21:38:57.607738+01:00 t470 NetworkManager[678]:  
[1677789537.6075] device (p2p-dev-wlp4s0): supplicant management 
interface state: authenticating -> associating
2023-03-02T21:38:57.611072+01:00 t470 kernel: [606294.336798] wlp4s0: 
associate with e2:2f:70:ee:a8:a9 (try 1/3)
2023-03-02T21:38:57.614962+01:00 t470 kernel: [606294.343825] wlp4s0: RX 
AssocResp from e2:2f:70:ee:a8:a9 (capab=0x1131 status=0 aid=1)
2023-03-02T21:38:57.629866+01:00 t470 wpa_supplicant[679]: wlp4s0: 
Associated with e2:2f:70:ee:a8:a9
2023-03-02T21:38:57.630072+01:00 t470 wpa_supplicant[679]: wlp4s0: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
2023-03-02T21:38:57.630987+01:00 t470 kernel: [606294.358880] wlp4s0: 
associated
2023-03-02T21:38:57.635364+01:00 t470 NetworkManager[678]:  
[1677789537.6352] device (wlp4s0): supplicant interface state: 
associating -> associated
2023-03-02T21:38:57.635534+01:00 t470 NetworkManager[678]:  
[1677789537.6353] device (p2p-dev-wlp4s0): supplicant management 
interface state: associating -> associated
2023-03-02T21:38:57.666997+01:00 t470 kernel: [606294.392568] wlp4s0: 
disassociated from e2:2f:70:ee:a8:a9 (Reason: 2=PREV_AUTH_NOT_VALID)
2023-03-02T21:38:57.667599+01:00 t470 NetworkManager[678]:  
[1677789537.6675] device (wlp4s0): supplicant interface state: 
associated -> 4way_handshake
2023-03-02T21:38:57.667775+01:00 t470 NetworkManager[678]:  
[1677789537.6675] device (p2p-dev-wlp4s0): supplicant management 
interface state: associated -> 4way_handshake
2023-03-02T21:38:57.757491+01:00 t470 wpa_supplicant[679]: wlp4s0: 
CTRL-EVENT-DISCONNECTED bssid=e2:2f:70:ee:a8:a9 reason=2
2023-03-02T21:38:57.757650+01:00 t470 wpa_supplicant[679]: wlp4s0: WPA: 
4-Way Handshake failed - pre-shared key may be incorrect
2023-03-02T21:38:57.757747+01:00 t470 wpa_supplicant[679]: wlp4s0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="papospot" auth_failures=1 
duration=10 reason=WRONG_KEY
2023-03-02T21:38:57.763028+01:00 t470 NetworkManager[678]:  
[1677789537.7629] device (wlp4s0): supplicant interface state: 
4way_handshake -> disconnected
2023-03-02T21:38:57.763223+01:00 t470 NetworkManager[678]:  
[1677789537.7630] device (wlp4s0): Activation: (wifi) disconnected 
during association, asking for new key



I'm no expert, but seems to me it's complaining about wrong credentials. 
However I'm more than sure I'm entering the correct password, I even 
changed it to something dead simple like 12345678.

Re: Getting PC with Ubuntu; change to Debian?

[Patrick Wiseman]

Hello again:

I'm just getting around to firing up my new laptop (Lenovo X1 Carbon Gen
10), which came with Ubuntu installed. (By the way, I appreciate all of the
feedback I got.) Although Ubuntu is a Debian-derivative, I didn't much care
for the feel of it. This is entirely subjective, I realize, but it felt as
if it wanted to get in the way of my going "under the hood", something
which I've been doing with my computers for decades! So I resolved to
return to Debian.

After making a recovery USB stick (which I confirmed worked before doing
anything else), I tried to boot from a Debian 11 live USB. It dropped me
immediately to a grub prompt! As comfortable as I am with Debian, that
caused me some discomfort!

So I decided to try a Debian 12 net install, which worked flawlessly and
has given me a nice clean Xfce desktop. I haven't put it through any
serious paces yet, but I'm back on familiar territory.

Cheers
Patrick


On Sun, Dec 4, 2022, 9:51 PM Patrick Wiseman  wrote:

> Hello, fellow Debian users:
>
> I've had Debian on my computers for a very long time (can't remember
> exactly when but early 2000's for sure); and I've had Lenovo laptops for
> ages too. I finally need to replace my main laptop (an at least 10-year old
> ThinkPad), so I've bought an X1 from Lenovo, with Ubuntu pre-installed (to
> be delivered in January).
>
> So, a question. Should I side-grade to Debian (and, if so, how easy would
> it be to do that?)? Or will I be happy with Ubuntu (which is, after all, a
> Debian derivative)?
>
> I'm very familiar and comfortable with Debian (was happy with 'testing'
> for a long time, but have lately reverted to 'stable'). And, although I'm a
> rare participant on this list, I enjoy the lurk and would presumably need
> to go elsewhere if I had questions about my Ubuntu experience.
>
> Thoughts will be welcome.
>
> Patrick
>
>

Building binary package, howto enable init.d/systemd start

[Konstantin Kletschke]

Dear debian-user Folks,

i am trying to build a binary debian package consisting of a python
script, shell scripts and a config file as daemon with either init.d or
systemd start.

The init.d script gets installed also the systemd file, but both are not
enabled.

I made a directory loqitmon-1.0 and in there are python script,
shellscripts and config file. 

In debian/control is:

Source: loqitmon
Section: base
Priority: optional
Maintainer: Konstantin Kletschke 
Build-Depends: debhelper (>=9.0.0), dh-virtualenv (>= 0.8)
Standards-Version: 4.5.1

Package: loqitmon
Architecture: any
Pre-Depends: dpkg (>= 1.16.1), python3, init-system-helpers (>= 1.51~)
Depends: ${misc:Depends}
Description: LoQiT monitoring daemon
 This daemon monitors /var/log/syslog for
 device removal of card reader and removal of
 display and restarts either the X server or
 the entire system accordingly
 Derived from https://github.com/yxiao168/logmonitor.git

In debian/rules is:

#!/usr/bin/make -f

DH_VERBOSE=1

%:
dh $@
clean:
@# Do nothing

build:
@# Do nothing

binary:
mkdir -p debian/loqitmon
mkdir -p debian/loqitmon/usr/
mkdir -p debian/loqitmon/usr/bin
cp loqitmon.py debian/loqitmon/usr/bin/loqitmon
mkdir -p debian/loqitmon/etc
cp loqitmon.ini debian/loqitmon/etc
cp loqitmonaction1 debian/loqitmon/usr/bin
cp loqitmonaction2 debian/loqitmon/usr/bin
cp loqitmonaction3 debian/loqitmon/usr/bin
cp loqitmonstep1 debian/loqitmon/usr/bin
cp loqitmonstep2 debian/loqitmon/usr/bin
cp loqitmonstep3 debian/loqitmon/usr/bin
dh_installinit
dh_installsystemd
dh_gencontrol
dh_install
dh_auto_install
dh_builddeb

When I run 

# > debuild -b -us -uc

this is the output:

 dpkg-buildpackage -us -uc -ui -b
dpkg-buildpackage: info: source package loqitmon
dpkg-buildpackage: info: source version 1.0-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Konstantin Kletschke 

 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
 debian/rules build
 fakeroot debian/rules binary
mkdir -p debian/loqitmon
mkdir -p debian/loqitmon/usr/
mkdir -p debian/loqitmon/usr/bin
cp loqitmon.py debian/loqitmon/usr/bin/loqitmon
mkdir -p debian/loqitmon/etc
cp loqitmon.ini debian/loqitmon/etc
cp loqitmonaction1 debian/loqitmon/usr/bin
cp loqitmonaction2 debian/loqitmon/usr/bin
cp loqitmonaction3 debian/loqitmon/usr/bin
cp loqitmonstep1 debian/loqitmon/usr/bin
cp loqitmonstep2 debian/loqitmon/usr/bin
cp loqitmonstep3 debian/loqitmon/usr/bin
dh_installinit
dh_installsystemd
dh_gencontrol
dpkg-gencontrol: warning: package loqitmon: substitution variable 
${misc:Pre-Depends} unused, but is defined
dh_install
dh_auto_install
dh_builddeb
dpkg-deb: building package 'loqitmon' in '../loqitmon_1.0-1_amd64.deb'.
 dpkg-genbuildinfo --build=binary -O../loqitmon_1.0-1_amd64.buildinfo
 dpkg-genchanges --build=binary -O../loqitmon_1.0-1_amd64.changes
dpkg-genchanges: info: binary-only upload (no source code included)
 dpkg-source --after-build .
dpkg-buildpackage: info: binary-only upload (no source included)
Now running lintian loqitmon_1.0-1_amd64.changes ...
E: loqitmon changes: bad-distribution-in-changes-file unstable
E: loqitmon: file-in-etc-not-marked-as-conffile etc/init.d/loqitmon
E: loqitmon: file-in-etc-not-marked-as-conffile etc/loqitmon.ini
E: loqitmon: no-changelog usr/share/doc/loqitmon/changelog.Debian.gz 
(non-native package)
E: loqitmon: no-copyright-file
W: loqitmon: no-manual-page usr/bin/loqitmon
W: loqitmon: no-manual-page usr/bin/loqitmonaction1
W: loqitmon: no-manual-page usr/bin/loqitmonaction2
W: loqitmon: no-manual-page usr/bin/loqitmonaction3
W: loqitmon: no-manual-page usr/bin/loqitmonstep1
W: loqitmon: no-manual-page usr/bin/loqitmonstep2
W: loqitmon: no-manual-page usr/bin/loqitmonstep3
W: loqitmon: script-in-etc-init.d-not-registered-via-update-rc.d 
etc/init.d/loqitmon
W: loqitmon: unknown-section base
Finished running lintian.

The files
/etc/init.d/loqitmon
/lib/systemd/system/loqitmon.service

are in the package, but they are are not enabled.

I have the strange feeling the entire postinstall stuff is missing.
Is there a significant typo somewhere so obvious I am to stupid to see?

If there is a distribution like Mint Tessa for example, how does the
system decide which startmethod to choose, if init.d and systemd are
enabled successfully? I see a mix of init.d and systemd there regading
starting stuff.

Kind Regards
Konstantin


-- 
INSIDE M2M GmbH
Konstantin Kletschke
Berenbosteler Straße 76 B
30823 Garbsen

Telefon: +49 (0) 5137 90950136
Mobil: +49 (0) 151 15256238
Fax: +49 (0) 5137 9095010

konstantin.kletsc...@inside-m2m.de
http://www.inside-m2m.de 

Geschäftsführung: Michael Emmert, Derek Uhlig
HRB: 111204, AG Hannover

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[tomas]

On Thu, Mar 02, 2023 at 12:14:14PM -0600, David Wright wrote:
> On Thu 02 Mar 2023 at 17:23:23 (-), Curt wrote:
> > On 2023-03-02, David  wrote:

[...]

> > Those seem like antithetical concepts.
> 
> The state is identical in both cases, hence using the same letter.
> OTOH the paths to that state can be different, and that's significant
> because installing and then purging a package can have side-effects
> on the system that don't get reverted to the inital state, eg the
> installation of Depends/Recommends.

Heh, you stole my thoughts. I was going "hm, the node in the state
diagram is the same, just the edges are different" :-)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Unable to associate to mobile hotspot

[Charles Curley]

On Thu, 2 Mar 2023 19:37:59 +0100
Lucio Crusca  wrote:

> 2023-03-02T18:07:29.908378+01:00 t470 NetworkManager[678]:  
> [166849.9068] Config: added 'auth_alg' value 'OPEN'
> 2023-03-02T18:07:29.908499+01:00 t470 NetworkManager[678]:  
> [166849.9068] Config: added 'psk' value ''

Interesting. Looking at a successful login I made this morning, the
next several likes after this one are from the supplicant as it goes
through its gyrations. I would think there would be more lines from the
supplicant.

You might compare this with a successful login elsewhere.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Generar ruido inaudible

[Paynalton]

El lun, 27 feb 2023 a las 10:57, Roberto C. Sánchez ()
escribió:

> On Mon, Feb 27, 2023 at 10:06:09AM -0600, Paynalton wrote:
> >Hola a todos.
> >Alguien sabe como puedo poner un sonido inaudible para el ser humano a
> >reproducir de forma infinita??
> >Tengo un problema con una bocina bluethoot que se apaga por una
> funcion de
> >ahorro de energia que no se puede desactivar y al retornar corta
> parte del
> >audio, lo que hace que las llamadas se escuchen entrecortadas.
> >Quiero colocar un sonido a reproducir de forma permanente en el fondo
> para
> >que no se active el modo de ahorro y pueda tener conversaciones
> >mas claras.
>
> ¿Cuál applicación usas para configurar/manejar la bocina?  ¿Te permite
> cambiar los parámetros de energía?
>

No, es una funcion built-in de la bocina, no se puede alterar de forma
remota.


>
> ¿Has mirado a ver si el vendedor ofrece un firmware actualizado que
> posiblemente arregla este defecto?
>
>
Es un producto chino de bajo costo, el fabricante no tiene pagina web.


> Saludos,
>
> -Roberto
>
> --
> Roberto C. Sánchez
>
>

Gracias por su atencion. Encontre un MP3 en una pagina de test de audio
para sordera y pude ponerlo en loop infinito usando mpg123

  mpg123 --loop -1 /home/paynalton/Música/22000.mp3

De paso, cree una fake webcam con ffmpeg que genera un vector usando el
volumen del microfono y queda perfecto para las videollamadas:

ffmpeg -f pulse -ac 2 -i default -filter_complex
"[0:a]avectorscope=s=480x480:zoom=1.5:rc=0:gc=200:bc=0:rf=0:gf=40:bf=0,format=yuv420p[v];
[v]pad=854:480:187:0[out]"  -map "[out]" -vcodec rawvideo -threads 0  -f
v4l2 /dev/video0

Re: Unable to associate to mobile hotspot

[Lucio Crusca]

Il 02/03/23 18:55, Charles Curley ha scritto:

grep -i networkmanager /var/log/syslog


Thanks, I looked at the logs, but I couldn't find the problem. The SSID 
is "papospot". Here are the relevant log entries:



2023-03-02T18:07:18.857868+01:00 t470 NetworkManager[678]:  
[166838.8553] device (wlp4s0): disconnecting for new activation request.
2023-03-02T18:07:18.858078+01:00 t470 NetworkManager[678]:  
[166838.8553] device (wlp4s0): state change: activated -> 
deactivating (reason 'new-activation', sys-iface-state: 'managed')
2023-03-02T18:07:18.858172+01:00 t470 NetworkManager[678]:  
[166838.8562] manager: NetworkManager state is now CONNECTED_LOCAL
2023-03-02T18:07:18.858274+01:00 t470 NetworkManager[678]:  
[166838.8565] audit: op="connection-add-activate" 
uuid="0df150fb-e0b6-4227-bf49-a261db8257df" name="papospot" pid=2676 
uid=1000 result=

"success"
2023-03-02T18:07:18.860097+01:00 t470 dbus-daemon[622]: [system] 
Activating via systemd: service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' 
(uid=0 pid=678 comm="/usr/sbin/NetworkManager --no-daemon")
2023-03-02T18:07:18.912369+01:00 t470 systemd[1]: Starting 
NetworkManager-dispatcher.service - Network Manager Script Dispatcher 
Service...
2023-03-02T18:07:18.923258+01:00 t470 systemd[1]: Started 
NetworkManager-dispatcher.service - Network Manager Script Dispatcher 
Service.
2023-03-02T18:07:19.045740+01:00 t470 NetworkManager[678]:  
[166839.0455] device (wlp4s0): state change: deactivating -> 
disconnected (reason 'new-activation', sys-iface-state: 'managed')
2023-03-02T18:07:19.051519+01:00 t470 NetworkManager[678]:  
[166839.0488] dhcp6 (wlp4s0): canceled DHCP transaction
2023-03-02T18:07:19.051953+01:00 t470 NetworkManager[678]:  
[166839.0488] dhcp6 (wlp4s0): activation: beginning transaction 
(timeout in 45 seconds)
2023-03-02T18:07:19.052922+01:00 t470 NetworkManager[678]:  
[166839.0489] dhcp6 (wlp4s0): state changed no lease
2023-03-02T18:07:19.090338+01:00 t470 NetworkManager[678]:  
[166839.0901] device (wlp4s0): set-hw-addr: set MAC address to 
2E:D1:85:CF:A6:77 (scanning)
2023-03-02T18:07:19.146216+01:00 t470 NetworkManager[678]:  
[166839.1440] device (wlp4s0): Activation: starting connection 
'papospot' (0df150fb-e0b6-4227-bf49-a261db8257df)
2023-03-02T18:07:19.146484+01:00 t470 NetworkManager[678]:  
[166839.1445] device (wlp4s0): supplicant interface state: completed 
-> disconnected
2023-03-02T18:07:19.146680+01:00 t470 NetworkManager[678]:  
[166839.1446] device (p2p-dev-wlp4s0): supplicant management 
interface state: completed -> disconnected
2023-03-02T18:07:19.146846+01:00 t470 NetworkManager[678]:  
[166839.1452] device (wlp4s0): state change: disconnected -> prepare 
(reason 'none', sys-iface-state: 'managed')
2023-03-02T18:07:19.147050+01:00 t470 NetworkManager[678]:  
[166839.1456] manager: NetworkManager state is now CONNECTING
2023-03-02T18:07:19.178500+01:00 t470 NetworkManager[678]:  
[166839.1782] device (wlp4s0): set-hw-addr: reset MAC address to 
9C:FC:E8:B6:64:0D (preserve)
2023-03-02T18:07:19.183295+01:00 t470 NetworkManager[678]:  
[166839.1827] device (wlp4s0): state change: prepare -> config 
(reason 'none', sys-iface-state: 'managed')
2023-03-02T18:07:19.183568+01:00 t470 NetworkManager[678]:  
[166839.1831] device (wlp4s0): Activation: (wifi) access point 
'papospot' has security, but secrets are required.
2023-03-02T18:07:19.183740+01:00 t470 NetworkManager[678]:  
[166839.1831] device (wlp4s0): state change: config -> need-auth 
(reason 'none', sys-iface-state: 'managed')
2023-03-02T18:07:29.203802+01:00 t470 systemd[1]: 
NetworkManager-dispatcher.service: Deactivated successfully.
2023-03-02T18:07:29.905561+01:00 t470 NetworkManager[678]:  
[166849.9042] device (wlp4s0): state change: need-auth -> prepare 
(reason 'none', sys-iface-state: 'managed')
2023-03-02T18:07:29.906353+01:00 t470 NetworkManager[678]:  
[166849.9059] device (wlp4s0): state change: prepare -> config 
(reason 'none', sys-iface-state: 'managed')
2023-03-02T18:07:29.907611+01:00 t470 NetworkManager[678]:  
[166849.9067] device (wlp4s0): Activation: (wifi) connection 
'papospot' has security, and secrets exist.  No new secrets needed.
2023-03-02T18:07:29.907846+01:00 t470 NetworkManager[678]:  
[166849.9067] Config: added 'ssid' value 'papospot'
2023-03-02T18:07:29.908013+01:00 t470 NetworkManager[678]:  
[166849.9067] Config: added 'scan_ssid' value '1'
2023-03-02T18:07:29.908152+01:00 t470 NetworkManager[678]:  
[166849.9068] Config: added 'bgscan' value 'simple:30:-70:86400'
2023-03-02T18:07:29.908259+01:00 t470 NetworkManager[678]:  
[166849.9068] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 
FT-PSK SAE FT-SAE'
2023-03-02T18:07:29.908378+01:00 t470 NetworkManager[678]:  
[166849.9068] Config: added 'auth_alg' value 'OPEN'

Re: Unable to associate to mobile hotspot

[Charles Curley]

On Thu, 2 Mar 2023 18:08:18 +0100
Lucio Crusca  wrote:

> Can you please help me spot the problem?

This might give you some ideas. As root, run:

grep -i networkmanager /var/log/syslog

Or run "tail -f /var/log/syslog" and watch it do its thing.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[David Wright]

On Thu 02 Mar 2023 at 17:23:23 (-), Curt wrote:
> On 2023-03-02, David  wrote:
> > On Fri, 3 Mar 2023 at 00:19, Greg Wooledge  wrote:
> >
> >> Man, I really wish the aptitude(8) man page would explain how to read
> >> the output of "why".  What does the "p" mean?  Purged?  There's nothing
> >> in the man page that explains the symbols in the first 3 columns, as
> >> far as I can find.

It's easy to miss, because the key to the letters is given in running
text a hundred lines away. (man chmod is a loathsome example of this
format.) The reference below is much better, as the figure is a table
(as well as being comprehensive).

> > Yeah. It does mean purged, or never installed.
> >
> >p - the package and all its configuration files were removed, or the
> >package was never installed.
> 
> Those seem like antithetical concepts.

The state is identical in both cases, hence using the same letter.
OTOH the paths to that state can be different, and that's significant
because installing and then purging a package can have side-effects
on the system that don't get reverted to the inital state, eg the
installation of Depends/Recommends.

> >>From here (Buster):
> >   grep -A 16 'Figure.2\.9\.' /usr/share/aptitude/README

and bullseye.

Cheers,
David.

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[Curt]

On 2023-03-02, David  wrote:
> On Fri, 3 Mar 2023 at 00:19, Greg Wooledge  wrote:
>
>> Man, I really wish the aptitude(8) man page would explain how to read
>> the output of "why".  What does the "p" mean?  Purged?  There's nothing
>> in the man page that explains the symbols in the first 3 columns, as
>> far as I can find.
>
> Yeah. It does mean purged, or never installed.
>
>p - the package and all its configuration files were removed, or the
>package was never installed.

Those seem like antithetical concepts.

>>From here (Buster):
>   grep -A 16 'Figure.2\.9\.' /usr/share/aptitude/README
>
>


-- 

Unable to associate to mobile hotspot

[Lucio Crusca]

I'm using Sid/amd64 on my notebook and I have a Android smartphone. My 
notebook has no problems to associate to every WiFI access point I 
tested so far, including mobile phones hotspots, except the hotspot of 
my own smartphone.


On the other hand, another notebook I have (booted with Systemrescuecd) 
has no problems to associate to my smartphone hotspot, and the same is 
true for other notebooks of a few friends I asked to.


I'm using XFCE, though I suspect that doesn't make any difference, 
because Systemrescuecd also uses XFCE.


When I try to associate my notebook to my smartphone hotspot, the 
password dialog simply pops up again, but I'm sure I enter the correct 
password.


I've already tried changing the password, changing the SSID, removing 
the network from NetworkManager and rebooting everything: no dice.


Can you please help me spot the problem?

Boot Errors

[Michael Lee]

While running the stable branch of 64-bit Debian, rebooted into an
alternative OS, but forgot to unmount a USB device beforhand. Shutdown
was taking too long, so forced it anyway. Now when I try to start
Linux, I get these error messages: 

[1.922640] platform gpio_ich.2.auto: failed to claim resource 0:[io
0x0480-0x04ff] 
[8.934607] BTRFS error (device sdc2): parent transid verify faild on
176160768 wanted 680981 found 680979
[8.934649] BTRFS error (device sdc2): failed to read block groups 1 - 5
[8.935724] BTRFS error (device sdc2): open_ctree failed 
mount: mounting /dev/sdc2 on /root failed: invalid argument 
failed to mount /dev/sdc2 as root file system 

Then the initramfs command prompt appears. A little hard to find much
on that.  

Read in the btrfs wiki that <-o ro,usebackuproot> with the mount
command could help when the "wanted" and "found" numbers were not too
far apart. 

mount -t btrfs -o ro,usebackuproot /dev/sdc2 
TRIED with: /sysroot
GOT: mount: mounting /dev/sdc2 on /sysroot failed: invalid argument
TRIED with: / 
GOT: mount: mounting /dev/sdc2 on / failed: invalid argument 
TRIED with: /root
GOT: mount: mounting /dev/sdc2 on /root failed: invalid argument 

Is this a GRUB issue, a btrfs issue, or must I reinstall the operating
system, and if so where can I find out which files must be preserved in
order to maintain continuity? 

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[David]

On Fri, 3 Mar 2023 at 02:18,  wrote:
> On 2023-03-02 14:19, Greg Wooledge wrote:
> > On Thu, Mar 02, 2023 at 02:01:57PM +0100, daven...@tuxfamily.org wrote:

> >> > > > akb@akira:~$ LC_ALL=C aptitude why ifupdown
> >> > > > p   netscript-2.4 Provides ifupdown
> >> > > > p   netscript-2.4 Depends  bridge-utils (>= 0.9.3)
> >> > > > p   bridge-utils  Suggests ifupdown
> >> > > > akb@akira:~$ LC_ALL=C aptitude why netscript-2.4
> >> > > > p   netscript-2.4 Provides ifupdown
> >
> >> dpkg -l netscript-2.4 or even dpkg -l | grep netscript
> >>
> >> Don't return anything… Not sure why "aptitude why ifupdown" mentions
> >> netscript-2.4 at all

You could try 'aptitude -v why' to add verbosity.

/usr/share/aptitude/README has some discussion about
the behaviour of 'why' and 'why-not'. Under the heading
'why, why-not'.

Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')

[Christoph Brinkhaus]

Am Thu, Mar 02, 2023 at 09:26:33PM +0700 schrieb Max Nikulin:
> On 28/02/2023 17:25, Christoph Brinkhaus wrote:
> > I will just inform about the status. Everything is fine now. A word
> > about systemd-networkd-wait-online: With this service running there
> > has been even a delay of 1-2 seconds when switching from one console
> > to a different one (the consoles when X is not running). I have no
> > idea about that side effect.
> 
> Does it happen each time or it is getty startup time? In the latter case you
> may try (for various console numbers)
> 
> systemd-analyze critical-chain getty@tty1.service
> 
It is happening each time when changing the console.

> > Now I have disabled systemd-networkd-wait-online and I have add a
> > comment in the last line of 
> > /usr/lib/systemd/system//systemd-networkd.service
> > which is now
> > # 28.2.2023 Also=systemd-networkd-wait-online.service
> 
> Ideally the root cause of strange behavior should be debugged. Perhaps some
> dependency should be removed from e.g. multi-user.target or
> network-online.target. Probably "systemd-analyze critical-chain" may give
> some hints.

Ok, it is no problem to include the service again. It is just strange
that it is not referenced anywhere. But I will try systemd-analyze.
I have not been aware about such a tool before. But it should be worth
to learn how to use it. Thank you for the information!
> 
> Any case I would not touch files in /usr/lib/systemd. It should confuse
> tools like systemd-delta. It is possible to override specific properties by
> creating of drop-in snippets in
> /etc/systemd/system/systemd-networkd.service.d/. See systemd.unit(5), e.g.
> run
> 
>systemctl edit systemd-networkd.service
> 
> [Install]
> # Clear
> Also=
> # Add other values from the original file
> Also=systemd-networkd.socket
> 
> Check result
> 
>systemd-analyze verify systemd-networkd.service
> 
> I hope, it is a better way to apply your workaround. I can not suggest a
> better solution for tty delay issue, but I think it exists. "Also=" should
> affect "systemctl enable systemd-networkd.service" and "disable" commands,
> so I puzzled why it helps at all.

I will try that, too. I have /etc under version control using git.
That makes it easy to get informed about changes.

Kind regards,
Christoph
-- 
Ist die Katze gesund
schmeckt sie dem Hund.

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[davenull]

On 2023-03-02 14:19, Greg Wooledge wrote:

On Thu, Mar 02, 2023 at 02:01:57PM +0100, daven...@tuxfamily.org wrote:


> > > akb@akira:~$ LC_ALL=C aptitude why ifupdown
> > > p   netscript-2.4 Provides ifupdown
> > > p   netscript-2.4 Depends  bridge-utils (>= 0.9.3)
> > > p   bridge-utils  Suggests ifupdown
> > > akb@akira:~$ LC_ALL=C aptitude why netscript-2.4
> > > p   netscript-2.4 Provides ifupdown



dpkg -l netscript-2.4 or even dpkg -l | grep netscript

Don't return anything… Not sure why "aptitude why ifupdown" mentions
netscript-2.4 at all


Oh, that's reassuring.  And also confusing.

Man, I really wish the aptitude(8) man page would explain how to read
the output of "why".  What does the "p" mean?  Purged?  There's nothing
in the man page that explains the symbols in the first 3 columns, as
far as I can find.


I wonder if aptitude just uses the dpkg-query abbreviations,
so "purged" seems a reasonable guess. But yeah, it would be
much more helpful if aptitude(8) man was not that ambiguous
about those abbreviations



I have *no* idea how to interpret this:

unicorn:~$ aptitude why ifupdown
p   netscript-2.4 Provides ifupdown
p   netscript-2.4 Depends  bridge-utils (>= 0.9.3)
p   bridge-utils  Suggests ifupdown
unicorn:~$ dpkg -l ifupdown | tail -n1
ii  ifupdown   0.8.36   amd64high level tools to
configure network interfaces

Maybe "aptitude why" simply can't handle packages that are part of
the base system ("Essential", or priority "required" or "important"),
or which have been manually installed and aren't part of a 
dependency...?


unicorn:~$ aptitude why bash
i   bash-builtins Depends bash (= 5.1-2+deb11u1)
unicorn:~$ aptitude why dpkg
i   google-chrome-stable PreDepends dpkg (>= 1.14.0)
unicorn:~$ aptitude why abcde
Manually installed, current version 2.9.3-1, priority optional
No dependencies require to install abcde

OK, I guess it handles manually installed packages.  But not base
system packages... at least not in a way one would expect.

In any case, ifupdown is an "important" package, and should be present
on almost all Debian systems, regardless of what "aptitude why" says
about it.

unicorn:~$ dpkg -s ifupdown | grep Prio
Priority: important


Good to know. I'd except it to be installed by default by the way. 
Looking again at files in /etc/network, there are


drwxr-xr-x 2 root root 4096  2 déc.   2021 if-post-down.d
drwxr-xr-x 2 root root 4096  2 déc.   2021 if-pre-up.d

The laptop was installed on the 2nd December 2021, so the files existed 
from day one,

But if-down.d and if-up.d content was updated later.
Must by the reason why someone (don't remember their name) on this 
thread suggested I have installed

ifupdown a few months laters.

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[David]

On Fri, 3 Mar 2023 at 00:19, Greg Wooledge  wrote:

> Man, I really wish the aptitude(8) man page would explain how to read
> the output of "why".  What does the "p" mean?  Purged?  There's nothing
> in the man page that explains the symbols in the first 3 columns, as
> far as I can find.

Yeah. It does mean purged, or never installed.

   p - the package and all its configuration files were removed, or the
   package was never installed.

>From here (Buster):
  grep -A 16 'Figure.2\.9\.' /usr/share/aptitude/README

Re: Comment éviter la saisie de longs chemins avec /bin/bash ?

[Jean-Michel OLTRA]

Bonjour,


Le jeudi 02 mars 2023, Basile Starynkevitch a écrit...


> Une autre possibilité, si on va très souvent dans le même répertoire, c'est
> de definir dans son ~/.bashrc
> 
> 
> function md1() {
>   cd /Mon/très/long/chemin/vers/dossier1
> }

ou un alias, par exemple :

alias cdicinga2='cd /etc/icinga2/conf.d'

-- 
jm

Re: unbound and fetchmail (was: Re: Remove route '169.254.0.0/16 dev ovs-system')

[Max Nikulin]

On 28/02/2023 17:25, Christoph Brinkhaus wrote:

I will just inform about the status. Everything is fine now. A word
about systemd-networkd-wait-online: With this service running there
has been even a delay of 1-2 seconds when switching from one console
to a different one (the consoles when X is not running). I have no
idea about that side effect.


Does it happen each time or it is getty startup time? In the latter case 
you may try (for various console numbers)


systemd-analyze critical-chain getty@tty1.service


Now I have disabled systemd-networkd-wait-online and I have add a
comment in the last line of /usr/lib/systemd/system//systemd-networkd.service
which is now
# 28.2.2023 Also=systemd-networkd-wait-online.service


Ideally the root cause of strange behavior should be debugged. Perhaps 
some dependency should be removed from e.g. multi-user.target or 
network-online.target. Probably "systemd-analyze critical-chain" may 
give some hints.


Any case I would not touch files in /usr/lib/systemd. It should confuse 
tools like systemd-delta. It is possible to override specific properties 
by creating of drop-in snippets in 
/etc/systemd/system/systemd-networkd.service.d/. See systemd.unit(5), 
e.g. run


   systemctl edit systemd-networkd.service

[Install]
# Clear
Also=
# Add other values from the original file
Also=systemd-networkd.socket

Check result

   systemd-analyze verify systemd-networkd.service

I hope, it is a better way to apply your workaround. I can not suggest a 
better solution for tty delay issue, but I think it exists. "Also=" 
should affect "systemctl enable systemd-networkd.service" and "disable" 
commands, so I puzzled why it helps at all.

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[Greg Wooledge]

On Thu, Mar 02, 2023 at 02:01:57PM +0100, daven...@tuxfamily.org wrote:

> > > > akb@akira:~$ LC_ALL=C aptitude why ifupdown
> > > > p   netscript-2.4 Provides ifupdown
> > > > p   netscript-2.4 Depends  bridge-utils (>= 0.9.3)
> > > > p   bridge-utils  Suggests ifupdown
> > > > akb@akira:~$ LC_ALL=C aptitude why netscript-2.4
> > > > p   netscript-2.4 Provides ifupdown

> dpkg -l netscript-2.4 or even dpkg -l | grep netscript
> 
> Don't return anything… Not sure why "aptitude why ifupdown" mentions
> netscript-2.4 at all

Oh, that's reassuring.  And also confusing.

Man, I really wish the aptitude(8) man page would explain how to read
the output of "why".  What does the "p" mean?  Purged?  There's nothing
in the man page that explains the symbols in the first 3 columns, as
far as I can find.

I have *no* idea how to interpret this:

unicorn:~$ aptitude why ifupdown
p   netscript-2.4 Provides ifupdown   
p   netscript-2.4 Depends  bridge-utils (>= 0.9.3)
p   bridge-utils  Suggests ifupdown   
unicorn:~$ dpkg -l ifupdown | tail -n1
ii  ifupdown   0.8.36   amd64high level tools to configure 
network interfaces

Maybe "aptitude why" simply can't handle packages that are part of
the base system ("Essential", or priority "required" or "important"),
or which have been manually installed and aren't part of a dependency...?

unicorn:~$ aptitude why bash
i   bash-builtins Depends bash (= 5.1-2+deb11u1)
unicorn:~$ aptitude why dpkg
i   google-chrome-stable PreDepends dpkg (>= 1.14.0)
unicorn:~$ aptitude why abcde
Manually installed, current version 2.9.3-1, priority optional
No dependencies require to install abcde

OK, I guess it handles manually installed packages.  But not base
system packages... at least not in a way one would expect.

In any case, ifupdown is an "important" package, and should be present
on almost all Debian systems, regardless of what "aptitude why" says
about it.

unicorn:~$ dpkg -s ifupdown | grep Prio
Priority: important

Re: solution to / full

[Jonathan Dowland]

On Thu, Mar 02, 2023 at 07:25:58AM -0500, Greg Wooledge wrote:

I don't understand why you used sort -r, but then reversed it again with
tac at the end.  You could drop both of the reversals, and just change
head to tail.


The short answer is because I wrote all but the last "tac" several years
ago, and added the last "tac" in writing the mail, when I realised the
output was the other way around to how I'd prefer.

--
Please do not CC me for listmail.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[davenull]

On 2023-03-02 13:47, daven...@tuxfamily.org wrote:

On 2023-03-02 13:32, Greg Wooledge wrote:
On Thu, Mar 02, 2023 at 10:32:41AM +0100, daven...@tuxfamily.org 
wrote:
This system never had any debian 10 or lower. It has been issued to 
my by

$worksplace
in december 2021, initially running windows.



akb@akira:~$ LC_ALL=C aptitude why ifupdown
p   netscript-2.4 Provides ifupdown
p   netscript-2.4 Depends  bridge-utils (>= 0.9.3)
p   bridge-utils  Suggests ifupdown
akb@akira:~$ LC_ALL=C aptitude why netscript-2.4
p   netscript-2.4 Provides ifupdown


unicorn:~$ apt-cache show netscript-2.4
[...]
Description-en: Linux 2.4/2.6/3.x router/firewall/VM host network 
config system.
 This is a router and firewall network configuration system.  It is 
specific to
 the 2.4.x and 2.6.x kernel series. This system is in production use, 
even

 though this is an experimental version.
[...]
 DON'T use this on a pure server - it is VERY useful for a Virtual 
Machine
 server with complex networking needs.  This is because of its 
comprehensive
 network configuration capabilities.  Thus it is a tempting 
replacement

 when you have to rip out NetworkManager on a server.


That sounds pretty terrifying to me.  I'm surprised it works *at all*
with a Debian 11 (or higher?  you didn't say what you *are* running,
only what you're *not* running) kernel.


Obviously NOT those old kernels. I'm runnning kernel 5.10

~$ uname -r
5.10.0-21-amd64

Why is this paquet installed at all then?


dpkg -l netscript-2.4 or even dpkg -l | grep netscript

Don't return anything… Not sure why "aptitude why ifupdown" mentions 
netscript-2.4 at all

Re: Mutirão de tradução para o bookworm

[Paulo Henrique de Lima Santana]

Olá,

Em 01/03/2023 19:08, Atenágoras Silva escreveu:
Olá Camaradas, não pude acompanhar a tarefa de aprender a trabalhar com 
as traduções, por isso, queria saber se os vídeos estão gravados em 
algum lugar...


Não foi gravado, mas você pode ler esta página e tirar dúvidas com o 
time de tradução.


https://wiki.debian.org/Brasil/Traduzir/DDTP

Abraços,

--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
Site: http://phls.com.br
GPG ID: 0443C450


OpenPGP_signature
Description: OpenPGP digital signature

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[davenull]

On 2023-03-02 13:32, Greg Wooledge wrote:

On Thu, Mar 02, 2023 at 10:32:41AM +0100, daven...@tuxfamily.org wrote:
This system never had any debian 10 or lower. It has been issued to my 
by

$worksplace
in december 2021, initially running windows.



akb@akira:~$ LC_ALL=C aptitude why ifupdown
p   netscript-2.4 Provides ifupdown
p   netscript-2.4 Depends  bridge-utils (>= 0.9.3)
p   bridge-utils  Suggests ifupdown
akb@akira:~$ LC_ALL=C aptitude why netscript-2.4
p   netscript-2.4 Provides ifupdown


unicorn:~$ apt-cache show netscript-2.4
[...]
Description-en: Linux 2.4/2.6/3.x router/firewall/VM host network 
config system.
 This is a router and firewall network configuration system.  It is 
specific to
 the 2.4.x and 2.6.x kernel series. This system is in production use, 
even

 though this is an experimental version.
[...]
 DON'T use this on a pure server - it is VERY useful for a Virtual 
Machine
 server with complex networking needs.  This is because of its 
comprehensive

 network configuration capabilities.  Thus it is a tempting replacement
 when you have to rip out NetworkManager on a server.


That sounds pretty terrifying to me.  I'm surprised it works *at all*
with a Debian 11 (or higher?  you didn't say what you *are* running,
only what you're *not* running) kernel.


Obviously NOT those old kernels. I'm runnning kernel 5.10

~$ uname -r
5.10.0-21-amd64

Why is this paquet installed at all then?

Re: Comment éviter la saisie de longs chemins avec /bin/bash ?

[Basile Starynkevitch]

On 3/2/23 09:43, Olivier wrote:

Bonjour,

Sur mon PC sous Bullseye, j'utilise /bin/bash.
J'aimerai bénéficier d'un mécanisme m'évitant au maximum la saisie de
longs chemins vers lesquels je navigue souvent.

Plutôt que
cd /Mon/très/long/chemin/vers/dossier1



Une autre possibilité, si on va très souvent dans le même répertoire, 
c'est de definir dans son ~/.bashrc



function md1() {
  cd /Mon/très/long/chemin/vers/dossier1
}

Et ensuite il faut juste taper md1



--
Basile Starynkevitch  
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/ & refpersys.org

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[Greg Wooledge]

On Thu, Mar 02, 2023 at 10:32:41AM +0100, daven...@tuxfamily.org wrote:
> This system never had any debian 10 or lower. It has been issued to my by
> $worksplace
> in december 2021, initially running windows.

> akb@akira:~$ LC_ALL=C aptitude why ifupdown
> p   netscript-2.4 Provides ifupdown
> p   netscript-2.4 Depends  bridge-utils (>= 0.9.3)
> p   bridge-utils  Suggests ifupdown
> akb@akira:~$ LC_ALL=C aptitude why netscript-2.4
> p   netscript-2.4 Provides ifupdown

unicorn:~$ apt-cache show netscript-2.4
[...]
Description-en: Linux 2.4/2.6/3.x router/firewall/VM host network config system.
 This is a router and firewall network configuration system.  It is specific to
 the 2.4.x and 2.6.x kernel series. This system is in production use, even
 though this is an experimental version.
[...]
 DON'T use this on a pure server - it is VERY useful for a Virtual Machine
 server with complex networking needs.  This is because of its comprehensive
 network configuration capabilities.  Thus it is a tempting replacement
 when you have to rip out NetworkManager on a server.


That sounds pretty terrifying to me.  I'm surprised it works *at all*
with a Debian 11 (or higher?  you didn't say what you *are* running,
only what you're *not* running) kernel.

Re: solution to / full

[Greg Wooledge]

On Thu, Mar 02, 2023 at 09:45:38AM +, Jonathan Dowland wrote:
> --✂--✂--✂--✂--✂--✂--✂--✂--✂--✂ --✂--✂--✂--✂--✂--✂--✂--✂--✂--✂--
> 
> STATUS_FILE=/var/lib/dpkg/status
> dpigs()
> {
> TL=${1-10}
> awk -v RS='' '/Status:.*installed\n/' "$STATUS_FILE" \
> | grep -E '^(Installed-Size|Package)' \
> | cut -d: -f2- \
> | paste - -  \
> | sort -rnk2 \
> | awk '{ print $2 "\t" $1 }' \
> | head -n "$TL" \
> | tac
> }
> dpigs "$@"
> 
> --✂--✂--✂--✂--✂--✂--✂--✂--✂--✂ --✂--✂--✂--✂--✂--✂--✂--✂--✂--✂--

I don't understand why you used sort -r, but then reversed it again with
tac at the end.  You could drop both of the reversals, and just change
head to tail.

Anyway... I wrote mine in perl, quite a few years ago (timestamp says
September 2004).  There's a copy at .
I named it before I even knew that "dpigs" existed.  I can't blame past
me for not knowing... dpigs is extremely well hidden.

Re: Comment éviter la saisie de longs chemins avec /bin/bash ?

[Haricophile]

Le Thu, 2 Mar 2023 09:43:29 +0100,
Olivier  a écrit :

> Bonjour,
> 
> Sur mon PC sous Bullseye, j'utilise /bin/bash.
> J'aimerai bénéficier d'un mécanisme m'évitant au maximum la saisie de
> longs chemins vers lesquels je navigue souvent.

Si tu y navigue souvent, autojump est assez pratique, il mémorise les
chemins récents.

$ j Documents

qui t'envoie sur ton dossier (récent) /home/Documents

Évidemment il ne faut pas appeler tous ses dossiers pareils...

tu peux aussi employer les * sous zsh en tout cas, sous bash je crois
que c'est (c'était?) un peu moins performant mais fonctionne aussi.
https://thevaluable.dev/zsh-expansion-guide-example/

Re: Comment éviter la saisie de longs chemins avec /bin/bash ?

[ajh-valmer]

> On 3/2/23 09:43, Olivier wrote:
> > Sur mon PC sous Bullseye, j'utilise /bin/bash.
> > J'aimerai bénéficier d'un mécanisme m'évitant au maximum la saisie de
> > longs chemins vers lesquels je navigue souvent.
> > Plutôt que cd /Mon/très/long/chemin/vers/dossier1

Dans le fichier ".bashrc" :
PATH=$PATH:$HOME/bin:/sbin:/usr/sbin:/usr/bin:/...tous les chemins désirés...
Relancer :
$ bash
Après on fait jouer la complétion.
Bonne journée

Re: Comment éviter la saisie de longs chemins avec /bin/bash ?

[Basile Starynkevitch]

On 3/2/23 09:43, Olivier wrote:

Bonjour,

Sur mon PC sous Bullseye, j'utilise /bin/bash.
J'aimerai bénéficier d'un mécanisme m'évitant au maximum la saisie de
longs chemins vers lesquels je navigue souvent.

Plutôt que
cd /Mon/très/long/chemin/vers/dossier1

J'aimerai configurer quelque part la variable M, y associer le chemin
Mon/très/long/chemin/vers
puis n'avoir qu'à saisir
cd M/dossier1




Il me semble que *zsh* (voir https://zsh.org/ ) ou peut-être *fish* 
(voir https://fishshell.com/ ...) est mieux que bash en utilisant 
l'autocomplétion par la touche TAB


https://thevaluable.dev/zsh-completion-guide-examples/

Et si le dossier1 est unique, on peut fairecd /**/dossier1


Enfin, il y a la variable d'environment /*CDPATH*/ connu par *zsh*


*https://koenwoortman.com/zsh-cdpath/* 




*Pour toutes ces raisons, mon shell interactif favori est /bin/zsh.*


Sous Debian, installer les paquets zsh zsh-dev zsh-syntax-highlighting 
zsh-doc et peut-être fizsh



Il faut bien évidemment disposer de deux heures de son temps pour 
apprendre et configurer zsh pour vos besoins...



--
Basile Starynkevitch
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/ & refpersys.org

Forcing dhclient to not ignore tun0 interface when it's available

[davenull]

Hello

On 2023-02-24 10:19, daven...@tuxfamily.org wrote:

Hello,


[…]


Otherwise, when VPN is disconnected, I DO want /etc/resolv.conf to be
generated according to my home router's DHCP tells the computer


… yes, that one.

Cheers,
David.


I finally had the time to dig into the logs from two days ago, when the 
problem happens again
It seems that dhclient does it requests trying different interfaces 
EXCEPT tun0 (see syslog below)


I looked into /etc/dhcp/dhclient.conf, which mostly commented. In the 
non-commented part shown below
I don't see anything related to which interfaces are to be used as 
arguments when dhclient is executed

But I'm not a dhclient expert.

At boot time/without VPN, dhclient is executed with enp.* interface 
accondinng to systemctl/ps -eFH.
But It still tries different interfaces according to logs. And I have no 
idea how it detects

which interfaces to use for it requests and why it doesn't detect tun0.
Maybe because tun0 is not yet exposed by the system at boot time when 
dhclient is started?


It stills try wlan interface even if it is down, which is weird, but 
doesn't seem to do harm except
spamming syslog and spending a few additional seconds before trying 
another interface.




dave@debian-laptop:~$ cat /etc/dhcp/dhclient.conf
-
send host-name = gethostname();
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
	dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, 
dhcp6.sntp-servers,

netbios-name-servers, netbios-scope, interface-mtu,
rfc3442-classless-static-routes, ntp-servers;
-

dave@debian-laptop:~$ systemctl status

 ├─ifup@enp2s0f0.service
 │ └─1093 /sbin/dhclient -4 -v -i -pf 
/run/dhclient.enp2s0f0.pid -lf /var/lib/dhcp/dhclient.enp2s0f0.leases -I 
-df /var/lib/dhcp/dhclient6.enp2s0f0.leases enp2s0f0





dave@debian-laptop:~$ sudo ausearch --interpret --file /etc/resolv.conf

type=PROCTITLE msg=audit(28/02/2023 14:30:57.787:658) : proctitle=mv -f 
/etc/resolv.conf.dhclient-new.46082 /etc/resolv.conf
type=PATH msg=audit(28/02/2023 14:30:57.787:658) : item=3 
name=/etc/resolv.conf inode=786809 dev=fd:01 mode=file,644 ouid=root 
ogid=root rdev=00:00 nametype=DELETE cap_fp=none cap_fi=none cap_fe=0 
cap_fver=0 cap_frootid=0
type=PATH msg=audit(28/02/2023 14:30:57.787:658) : item=2 
name=/etc/resolv.conf.dhclient-new.46082 inode=786811 dev=fd:01 
mode=file,644 ouid=root ogid=root rdev=00:00 nametype=DELETE cap_fp=none 
cap_fi=none cap_fe=0 cap_fver=0 cap_frootid=0
type=PATH msg=audit(28/02/2023 14:30:57.787:658) : item=1 name=/etc/ 
inode=783361 dev=fd:01 mode=dir,755 ouid=root ogid=root rdev=00:00 
nametype=PARENT cap_fp=none cap_fi=none cap_fe=0 cap_fver=0 
cap_frootid=0
type=PATH msg=audit(28/02/2023 14:30:57.787:658) : item=0 name=/etc/ 
inode=783361 dev=fd:01 mode=dir,755 ouid=root ogid=root rdev=00:00 
nametype=PARENT cap_fp=none cap_fi=none cap_fe=0 cap_fver=0 
cap_frootid=0

type=CWD msg=audit(28/02/2023 14:30:57.787:658) : cwd=/
type=SYSCALL msg=audit(28/02/2023 14:30:57.787:658) : arch=x86_64 
syscall=rename success=no exit=EPERM(Opération non permise) 
a0=0x7ffc38ee0a9e a1=0x7ffc38ee0ac2 a2=0x0 a3=0xfa4d items=4 
ppid=46082 pid=46093 auid=unset uid=root gid=root euid=root suid=root 
fsuid=root egid=root sgid=root fsgid=root tty=(none) ses=unset comm=mv 
exe=/usr/bin/mv subj=unconfined key=(null)



Note : exit=EPERM can be ignored, because it happened while I made 
/etc/resolv.conf immutable




dave@debian-laptop:~$ less /var/log/syslog
Feb 28 14:30:48 debian-laptop dhclient[2016]: DHCPDISCOVER on wlp3s0 to 
255.255.255.255 port 67 interval 3
Feb 28 14:30:51 debian-laptop dhclient[39759]: DHCPDISCOVER on 
enx8c8caa616f43 to 255.255.255.255 port 67 interval 5
Feb 28 14:30:51 debian-laptop dhclient[2016]: DHCPDISCOVER on wlp3s0 to 
255.255.255.255 port 67 interval 4
Feb 28 14:30:55 debian-laptop dhclient[2016]: DHCPDISCOVER on wlp3s0 to 
255.255.255.255 port 67 interval 11
Feb 28 14:30:56 debian-laptop dhclient[39759]: DHCPDISCOVER on 
enx8c8caa616f43 to 255.255.255.255 port 67 interval 9
Feb 28 14:30:57 debian-laptop dhclient[1003]: DHCPREQUEST for 
192.168.1.192 on enp2s0f0 to 192.168.1.1 port 67
Feb 28 14:30:57 debian-laptop dhclient[1003]: DHCPACK of 192.168.1.192 
from 192.168.1.1
Feb 28 14:30:57 debian-laptop connmand[1038]: enp2s0f0 {add} address 
192.168.1.192/24 label enp2s0f0 family 2
Feb 28 14:30:57 debian-laptop avahi-daemon[1034]: Registering new 
address record for 192.168.1.192 on enp2s0f0.IPv4.
Feb 28 14:30:57 debian-laptop dhclient[1003]: bound to 192.168.1.192 -- 
renewal in 17866 seconds.
Feb 28 14:31:05 debian-laptop dhclient[39759]: DHCPDISCOVER on 
enx8c8caa616f43 to 255.255.255.255 port 67 interval 12
Feb 28 14:31:06 debian-laptop dhclient[2016]: DHCPDISCOVER on wlp3s0 to 
255.255.255.255 port 67 interval 11
Feb 28 14:31:17 debian-laptop dhclient[39759]: 

Re: Comment éviter la saisie de longs chemins avec /bin/bash ?

[Sébastien NOBILI]

Bonjour,

Le 2023-03-02 09:43, Olivier a écrit :

Une idée ?


J'utilise ça (dans Zsh, mais ça doit pouvoir s'adapter à Bash) : 
https://github.com/kurkale6ka/zsh/


Tu ne vois plus la navigation dans les dossiers de la même façon :)

Chaque dossier que tu visites est enregistré dans une base SQLite.
Chaque fois que tu visites un dossier son poids augmente.
La recherche floue (par FZF) te permet de trouver un dossier en tapant 
quelques caractères.


Sébastien

Re: solution to / full

[Jonathan Dowland]

On Wed, Mar 01, 2023 at 03:15:07PM +0100, Jochen Spieker wrote:

The program dpigs from the package debian-goodies can help you find the
biggest debian packages you have installed. Of course you need to check
yourself whether you need them.


It's a shame that this requires installing debian-goodies (and
associated transitive dependencies), which can be a problem when the
root filesystem is full or nearly so.

A while ago I (privately) re-wrote dpigs in standard tools for this
reason (mostly for operating inside small containers). Once I got to
feature parity I was going to submit a wishlist bug to split it out from
debian-goodies, but the last feature was awkward to implement and I
never finished it.

Anyway, for OP's purpose, what I have is good enough. Presented in case
it's useful:

--✂--✂--✂--✂--✂--✂--✂--✂--✂--✂ --✂--✂--✂--✂--✂--✂--✂--✂--✂--✂--

STATUS_FILE=/var/lib/dpkg/status
dpigs()
{
TL=${1-10}
awk -v RS='' '/Status:.*installed\n/' "$STATUS_FILE" \
| grep -E '^(Installed-Size|Package)' \
| cut -d: -f2- \
| paste - -  \
| sort -rnk2 \
| awk '{ print $2 "\t" $1 }' \
| head -n "$TL" \
| tac
}
dpigs "$@"

--✂--✂--✂--✂--✂--✂--✂--✂--✂--✂ --✂--✂--✂--✂--✂--✂--✂--✂--✂--✂--

--
Please do not CC me for listmail.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net

Re: Comment éviter la saisie de longs chemins avec /bin/bash ?

[Charles Plessy]

Le Thu, Mar 02, 2023 at 09:43:29AM +0100, Olivier a écrit :
> 
> Sur mon PC sous Bullseye, j'utilise /bin/bash.
> J'aimerai bénéficier d'un mécanisme m'évitant au maximum la saisie de
> longs chemins vers lesquels je navigue souvent.

J'ai ce genre de chose dans mon fichier bash_profile.

hopla () { pushd "/mon/long/chemin/$1"; }
_hopla () { 
local cur files
COMPREPLY=()
cur="${COMP_WORDS[COMP_CWORD]}"
files=$(ls /mon/long/chemin/) 
COMPREPLY=( $(compgen -W "${files}" -- ${cur}) )
}
complete -F _hopla hopla

J'en suis assez satisfait, sauf que la complétion avec tab n'explore pas
les sous-répertoires...

Amicalement,

Charles

-- 
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Debian Med packaging team http://www.debian.org/devel/debian-med
Tooting from home  https://framapiaf.org/@charles_plessy
- You  do not have  my permission  to use  this email  to train  an AI -

Re: solution to / full

[Jonathan Dowland]

On Wed, Mar 01, 2023 at 02:27:58PM -0700, Charles Curley wrote:

You can find the large directory culprits quickly enough with

cd /
du -h | sort -h


OP demonstrated that they know how to use ncdu, which is a far superior
way of achieving the same result.

Personally I like duc for this job (and so I took over maintaining it):
https://duc.zevv.nl/

--
Please do not CC me for listmail.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net

Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable

[davenull]

On 2023-03-02 00:24, David Wright wrote:

On Tue 28 Feb 2023 at 16:05:14 (+0100), daven...@tuxfamily.org wrote:

On 2023-02-28 05:27, David Wright wrote:
> On Thu 23 Feb 2023 at 11:23:30 (+0100), daven...@tuxfamily.org wrote:
> > On 2023-02-23 02:59, cono...@panix.com wrote:

 [ … ]

Well, it looks like cruft from an earlier installation of networking;
and a couple of months later, you installed ifupdown and wpasupplicant,
by the looks of things. I don't know whether /etc/network/interfaces
itself would interfere with however connman is configured.



This system never had any debian 10 or lower. It has been issued to my 
by $worksplace

in december 2021, initially running windows.

I erased the full disk and installed à "default" (official image) debian 
11, from an LXDE live USB image
It has never had any interface named eth0. I still fail to see why setup 
conf would refer to eth0 at all


Then I few month later, I finally took the time to debug why WiFi card 
didn't work/what firmware is needed
Debian's firmware packaged started supporting the WLAN/WiFi card 
after I installed my system.


So then I installed the firmware. I most likely installed wpasuppicant 
the same day, and tested it worked.


Not sure about ifup thought. Doesn't seem to be a wpasupplicant 
dependency.


akb@akira:~$ LC_ALL=C aptitude why ifupdown
p   netscript-2.4 Provides ifupdown
p   netscript-2.4 Depends  bridge-utils (>= 0.9.3)
p   bridge-utils  Suggests ifupdown
akb@akira:~$ LC_ALL=C aptitude why netscript-2.4
p   netscript-2.4 Provides ifupdown

Why openresolv wouldn't work?



Cheers,
David.

Re: Comment éviter la saisie de longs chemins avec /bin/bash ?

[Pierre Frenkiel]

bonjour Olivier,
pour la completion, les 2 methodes suivantes marchent pour moi:
set -o vi
ou
set -o emacs
ensuite, je fais,par exemple: 
cd .alsa

et cela complete en
cd .alsaplayer
avec:
cd .al
il me propose .alpine et .alsaplayer
et je peux choisir en ajoutant une lettre (p ous)

Cordialement
Pierre Frenkiel

Re: Comment éviter la saisie de longs chemins avec /bin/bash ?

[ptilou]

Bonjour,

ln, pour liens me semble une solution rapide, sinon .batshrc ?

Le jeudi 2 mars 2023 à 09:50:03 UTC+1, Olivier a écrit :
> Bonjour, 
> 
> Sur mon PC sous Bullseye, j'utilise /bin/bash. 
> J'aimerai bénéficier d'un mécanisme m'évitant au maximum la saisie de 
> longs chemins vers lesquels je navigue souvent. 
> 
> Plutôt que 
> cd /Mon/très/long/chemin/vers/dossier1 
> 
> J'aimerai configurer quelque part la variable M, y associer le chemin 
> Mon/très/long/chemin/vers 
> puis n'avoir qu'à saisir 
> cd M/dossier1 
> 
> J'aimerai aussi bénéficier que l'expansion automatique pour éviter 
> d'avoir grâce aux tabulations, à saisir entièrement les noms dossier1, 
> dossier2 ... 
> 
> Ainsi si dans mon répertoire M, figurent les dossiers dossier1, 
> dossier2 et foo, en saisissant cd M/d, le système complète en ajoutant 
> ossier, en saisissant cd M/f le système complète en ajoutant oo car 
> foo est le seul élément du répertoire M commençant par f. 
> 
> J'ai pu implémenter une partie en ajoutant la ligne ci-après dans ~/.profile: 
> export M=/Mon/très/long/chemin/vers 
> 
> En suivant [1] (correctement ?), j'ai ajouté dans ~/.barshrc mais la 
> complétion ne fonctionne pas. 
> shopt -s cdable_vars 
> if [ -f /etc/bash_completion ]; then 
> . /etc/bash_completion 
> fi 
> 
> Une idée ? 
> 
> [1] 
> https://unix.stackexchange.com/questions/245113/bash-tab-completion-with-cdable-vars
>  
> 
> Slts

— 
Ptilou

Re: solution to / full

[tomas]

On Thu, Mar 02, 2023 at 09:53:29AM +0100, lina wrote:
> :/usr/lib$ du -sh * | sort -nr | grep -v K  | head
> 981M R
> 591M rstudio
> 591M jvm
> 554M mega
> 538M llvm-11
> 343M modules
> 313M libreoffice

Insightful, thanks :)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Comment éviter la saisie de longs chemins avec /bin/bash ?

[hamster]

Le 02/03/2023 à 09:43, Olivier a écrit :

Bonjour,

Sur mon PC sous Bullseye, j'utilise /bin/bash.
J'aimerai bénéficier d'un mécanisme m'évitant au maximum la saisie de
longs chemins vers lesquels je navigue souvent.

Plutôt que
cd /Mon/très/long/chemin/vers/dossier1

J'aimerai configurer quelque part la variable M, y associer le chemin
Mon/très/long/chemin/vers
puis n'avoir qu'à saisir
cd M/dossier1


Fais toi des raccourcis sous forme de liens symboliques. Et ca marche 
aussi pour l'auto-complétion.


Par exemple tu te fais un lien /raccourci qui pointe vers 
/Mon/très/long/chemin/vers tu pourra alors saisir /r  d 

Re: solution to / full

[lina]

:/usr/lib$ du -sh * | sort -nr | grep -v K  | head
981M R
591M rstudio
591M jvm
554M mega
538M llvm-11
343M modules
313M libreoffice

On Thu, Mar 2, 2023 at 9:48 AM lina  wrote:

> Hi all,
>
> Thanks for your suggestions,
>
> I take the least risk way, just move the things from /opt away,
>
> I hope I can make it in the next few months, the biggest problem was
> created by the R associated package.
>
> /dev/nvme0n1p2   23G   18G  4.5G  80% /
>
> Thanks again, lina
>
> On Thu, Mar 2, 2023 at 6:40 AM  wrote:
>
>> On Wed, Mar 01, 2023 at 06:12:05PM -0500, Greg Wooledge wrote:
>> > On Wed, Mar 01, 2023 at 05:53:18PM -0500, Jeffrey Walton wrote:
>> > > On Wed, Mar 1, 2023 at 8:35 AM lina  wrote:
>> > > >
>> > > > My / is almost full.
>>
>> [...]
>>
>> > > > /dev/nvme0n1p2   23G   21G  966M  96% /
>>
>> [...]
>>
>> > > > /dev/nvme0n1p3  9.1G  3.2G  5.5G  37% /var
>>
>> [...]
>>
>> > > You can probably reclaim a couple of GB by trimming systemd logs. It
>> > > should get you some room to work. Something like:
>> > >
>> > >journalctl --vacuum-time=14d
>> >
>> > Aren't those stored in /var, though?  There's a separate /var file
>> system,
>> > which isn't low on space.
>>
>> I'd hope that. I made the same mistake abovethread :)
>>
>> Cheers
>> --
>> t
>>
>

Re: solution to / full

[lina]

Hi all,

Thanks for your suggestions,

I take the least risk way, just move the things from /opt away,

I hope I can make it in the next few months, the biggest problem was
created by the R associated package.

/dev/nvme0n1p2   23G   18G  4.5G  80% /

Thanks again, lina

On Thu, Mar 2, 2023 at 6:40 AM  wrote:

> On Wed, Mar 01, 2023 at 06:12:05PM -0500, Greg Wooledge wrote:
> > On Wed, Mar 01, 2023 at 05:53:18PM -0500, Jeffrey Walton wrote:
> > > On Wed, Mar 1, 2023 at 8:35 AM lina  wrote:
> > > >
> > > > My / is almost full.
>
> [...]
>
> > > > /dev/nvme0n1p2   23G   21G  966M  96% /
>
> [...]
>
> > > > /dev/nvme0n1p3  9.1G  3.2G  5.5G  37% /var
>
> [...]
>
> > > You can probably reclaim a couple of GB by trimming systemd logs. It
> > > should get you some room to work. Something like:
> > >
> > >journalctl --vacuum-time=14d
> >
> > Aren't those stored in /var, though?  There's a separate /var file
> system,
> > which isn't low on space.
>
> I'd hope that. I made the same mistake abovethread :)
>
> Cheers
> --
> t
>

Re: Warpinator sous Debian

[Michel Memeteau]

Bonjour

Le 28/02/2023 à 19:55, Frederic Zulian a écrit :

Donc installation de flatpak : Ok
Téléchargement de org.x.Warpinator.flatpakref : OK
Lancement via Logiciels.
Sauf que la, cela mouline avec le message "Chargements des détails de 
l'application" et puis  plus rien 



Et que dit " flatpak install org.x.Warpinator" ?

Cordialement

--
--
Michel Memeteau

Ekimia (https://ekimia.fr  )

Directeur

tel:+33(0)624808051

Address :
620 avenue de la roche fourcade
13400 Aubagne
France

Comment éviter la saisie de longs chemins avec /bin/bash ?

[Olivier]

Bonjour,

Sur mon PC sous Bullseye, j'utilise /bin/bash.
J'aimerai bénéficier d'un mécanisme m'évitant au maximum la saisie de
longs chemins vers lesquels je navigue souvent.

Plutôt que
cd /Mon/très/long/chemin/vers/dossier1

J'aimerai configurer quelque part la variable M, y associer le chemin
Mon/très/long/chemin/vers
puis n'avoir qu'à saisir
cd M/dossier1

J'aimerai aussi bénéficier que l'expansion automatique pour éviter
d'avoir grâce aux tabulations, à saisir entièrement les noms dossier1,
dossier2 ...

Ainsi si dans mon répertoire M, figurent les dossiers dossier1,
dossier2 et foo, en saisissant cd M/d, le système complète en ajoutant
ossier, en saisissant cd M/f le système complète en ajoutant oo car
foo est le seul élément du répertoire M commençant par f.

J'ai pu implémenter une partie en ajoutant la ligne ci-après dans ~/.profile:
export M=/Mon/très/long/chemin/vers

En suivant [1] (correctement ?), j'ai ajouté dans ~/.barshrc mais la
complétion ne fonctionne pas.
shopt -s cdable_vars
if [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi

Une idée ?

[1] 
https://unix.stackexchange.com/questions/245113/bash-tab-completion-with-cdable-vars

Slts

Ecole du logiciel libre a Ivry , et la video ?

[ptilou]

Slt,

Je cherche a propose a cette fabuleuse association qui donne ces cours sous 
Debian, un logiciel qui decouperai les video en une table des matieres avec des 
marqueurs temporels.

Donc youtube, y arrive, et je me demande si il existe quelque chose qui peux le 
faire par automatisme, ou si c’est a la mano ?

Merci

— 
Ptilou