Re: door bell like sound effect

2023-08-29 Thread David Wright
On Tue 29 Aug 2023 at 23:54:41 (-0400), Karl Vogel wrote:
> On Tue, Aug 29, 2023 at 10:53:39PM -0400, gene heskett wrote:
> > And that is the problem, and why I read thru all those man ages trying to
> > find a way to make it log what it did. Sadly no.
> 
>   Install and configure file auditing on Debian:
> https://www.daemon.be/maarten/auditd.html
> 
>   Auditing can help you find anything trying to write to your sound device.
>   Look at these manpages:
> auditd.conf (5)
> audit.rules (7)
> audispd (8)
> ausearch (8)
> aureport (8)
> auditctl (8)
> augenrules (8)
> 
>   To find your sound cards and/or devices:
> https://wiki.debian.org/Sound
> https://wiki.debian.org/SoundCard
> https://wiki.debian.org/PulseAudio
> 
>   I don't have a Debian system to play with, but in the (good|bad) old
>   days, we had a /devices directory with all sorts of weirdness inside.
>   If you have one of those, try
> find /devices -print | grep sound
> 
>   That might point you to an actual device name.

As Gene has the habit of thoughtlessly pasting commands posted here,
it might be better instead to try:

  $ find /dev | grep snd
  /dev/snd
  /dev/snd/controlC0
  /dev/snd/hwC0D0
  /dev/snd/pcmC0D2c
  /dev/snd/pcmC0D2p
  /dev/snd/pcmC0D0c
  /dev/snd/pcmC0D0p
  /dev/snd/by-path
  /dev/snd/by-path/pci-:00:1b.0
  /dev/snd/by-path/pci-:02:00.1
  /dev/snd/controlC1
  /dev/snd/hwC1D0
  /dev/snd/pcmC1D3p
  /dev/snd/seq
  /dev/snd/timer
  $ 

Cheers,
David.



Re: door bell like sound effect

2023-08-29 Thread Karl Vogel
On Tue, Aug 29, 2023 at 10:53:39PM -0400, gene heskett wrote:
> And that is the problem, and why I read thru all those man ages trying to
> find a way to make it log what it did. Sadly no.

  Install and configure file auditing on Debian:
https://www.daemon.be/maarten/auditd.html

  Auditing can help you find anything trying to write to your sound device.
  Look at these manpages:
auditd.conf (5)
audit.rules (7)
audispd (8)
ausearch (8)
aureport (8)
auditctl (8)
augenrules (8)

  To find your sound cards and/or devices:
https://wiki.debian.org/Sound
https://wiki.debian.org/SoundCard
https://wiki.debian.org/PulseAudio

  I don't have a Debian system to play with, but in the (good|bad) old
  days, we had a /devices directory with all sorts of weirdness inside.
  If you have one of those, try
find /devices -print | grep sound

  That might point you to an actual device name.

-- 
Karl Vogel  I don't speak for anyone but myself.

Comment: One of my friends drank half a bottle of rum and refilled it
 with a bodily fluid of similar color.
Reply:   Your friend should see a doctor and drink more water.
   --seen on Reddit, 27 Aug 2023



Re: door bell like sound effect

2023-08-29 Thread gene heskett

On 8/29/23 14:54, gene heskett wrote:

On 8/29/23 12:50, zithro wrote:

On 29 Aug 2023 18:19, gene heskett wrote:

On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:



Have you checked all the cron files and the systemd timers ?


cron yes, systemd timers no, don't know how.


man systemctl ; look for "timer" (in vi(m) use "/" to search) ?

$ systemctl list-timers



Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could also 
have used xmms, audacity, VLC, mpv, etc.


tried aplay, got server dead response. htop cannot find aplay,

Its usually in the middle of the night, waking me up because it is as 
loud as the real door bell would be. Last Saturday was unusual as it 
sounded off at 2:06 and 6:58 EDT.  Never occurred while I'm sitting 
here. Most of the noises it makes are 30 db quieter.


?!
I think you didn't understand what I meant.
To play a sound, there needs to be an app launching it.
So I suggested than instead of "find"ing the sound itself, you try to 
"grep" the application/executable name.
Agreed this could be long, as you don't know where that sound is 
played from.


And that is the problem, and why I read thru all those man ages trying 
to find a way to make it log what it did. Sadly no.


Cheers, Gene Heskett.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: door bell like sound effect

2023-08-29 Thread Max Nikulin

On 30/08/2023 01:58, gene heskett wrote:

bash: pactl: command not found
gene@coyote:~$ sudo apt install pactl

...

E: Unable to locate package pactl

Next?


Either apt-file suggested earlier or if you are using it rarely and 
prefer to avoid downloading of file lists for all packages then


https://packages.debian.org/file:pactl


Thunderbird calendar, korganizer, alarm applets or applications may be 
suspected as well.

Those would all be under /home/me/.local? FWIW I am the only live user. 


At least thunderbird keeps its files in ~/.thunderbird by default. 
Perhaps KDE application might continue using legacy ~/.kde if the 
directory already contains their files. My idea is to check if you have 
accidentally scheduled events without waiting a next alarm.




Re: Error : virHostCPUGetKVMMaxVCPUs: KVM is not supported on this platform: Function not implemented

2023-08-29 Thread zithro

On 29 Aug 2023 23:48, Mario Marietto wrote:


I'm running Debian bookworm [...]


No you're not.

You're running a MODIFIED Debian version with a (rather old) MODIFIED 
kernel :



$ uname -r
5.4.244-stb-cbe

>

[removed mostly copy/paste from old posts]



Can someone give me some suggestions to fix that error ? thanks.


Yes, takes me 2 minutes too :

1. open the libvirt source code folder
2. grep the functions in error to get the file names
3. open those files and find out why the functions fail
4. edit code, recompile, test
5. do (4) till the problem is not solved

Also, it's nice to report the bug where you got the disk image, so 
others won't waste their time for the same bug.


If you solved your problem, propose a patch, so others may benefit.

HTH !

--
++
zithro / Cyril



AW: Debugging initramfs, server hangs during boot process

2023-08-29 Thread thah...@t-online.de
I cannot catch the user space output on the broken machine 

To get netconsole going I have edited  
/usr/share/initramfs-tools/scripts/init-top/udev

First to load the network module.
2nd to load the netconsole:

---snip
echo modprobe comes next ...
sleep 9
set -x
modprobe r8169
lsmod|grep r8169

modprobe netconsole 
netconsole="@192.168.178.62/enp3s0,@192.168.178.54/04:92:26:d9:4e:9e"
res=$?
if [ "$res" -eq 0 ]; then
   echo modprobe worked
else
echo modprobe failed eith $res
fi
---snap

The netconsole output from the kernel:

[   28.109866] r8169 :03:00.0: firmware: direct-loading firmware 
rtl_nic/rtl8125b-2.fw
[   28.141085] RTL8226B_RTL8221B 2.5Gbps PHY r8169-0-300:00: attached PHY 
driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC)
[   28.341236] r8169 :03:00.0 enp3s0: Link is Down
[   30.013941] r8169 :03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow 
control rx/tx
[   30.014760] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[   30.021222] printk: console [netcon0] enabled
[   30.024682] netconsole: network logging started
[   68.102701] input: Sleep Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
[   68.102771] ACPI: button: Sleep Button [SLPB]
[   68.102874] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[   68.102964] ACPI: button: Power Button [PWRB]
[   68.103014] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[   68.103079] ACPI: button: Power Button [PWRF]
[   68.158125] i801_smbus :00:1f.4: SMBus using PCI interrupt
[   68.160436] i2c i2c-0: 4/4 memory slots populated (from DMI)
[   68.160795] i2c i2c-0: Successfully instantiated SPD at 0x50
[   68.161131] i2c i2c-0: Successfully instantiated SPD at 0x51
[   68.161513] i2c i2c-0: Successfully instantiated SPD at 0x52
[   68.161895] i2c i2c-0: Successfully instantiated SPD at 0x53
[   68.166974] ACPI: bus type USB registered
[   68.166994] usbcore: registered new interface driver usbfs
[   68.166998] usbcore: registered new interface driver hub
[   68.167054] usbcore: registered new device driver usb
[   68.170281] SCSI subsystem initialized
[   68.183217] cryptd: max_cpu_qlen set to 1000
[   68.183493] ACPI: bus type drm_connector registered
[   68.195886] nvme nvme0: pci function :02:00.0
[   68.196051] xhci_hcd :00:14.0: xHCI Host Controller
[   68.196193] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 1
[   68.196443] nvme nvme1: pci function :04:00.0
[   68.197314] libata version 3.00 loaded.
[   68.197503] xhci_hcd :00:14.0: hcc params 0x20007fc1 hci version 0x120 
quirks 0x00029810
[   68.197931] xhci_hcd :00:14.0: xHCI Host Controller
[   68.198112] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 2
[   68.198305] xhci_hcd :00:14.0: Host supports USB 3.2 Enhanced SuperSpeed
[   68.198544] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.04
[   68.198762] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   68.198986] usb usb1: Product: xHCI Host Controller
[   68.199214] usb usb1: Manufacturer: Linux 6.4.0-3-amd64 xhci-hcd
[   68.199452] usb usb1: SerialNumber: :00:14.0
[   68.199775] AVX2 version of gcm_enc/dec engaged.
[   68.200044] AES CTR mode by8 optimization enabled
[   68.200049] hub 1-0:1.0: USB hub found
[   68.200580] hub 1-0:1.0: 16 ports detected
[   68.200680] nvme nvme0: missing or invalid SUBNQN field.
[   68.200681] nvme nvme1: missing or invalid SUBNQN field.
[   68.200757] nvme nvme1: Shutdown timeout set to 10 seconds
[   68.202337] nvme nvme1: 8/0/0 default/read/poll queues
[   68.203130] nvme nvme1: Ignoring bogus Namespace Identifiers
[   68.204269] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, 
bcdDevice= 6.04
[   68.204570] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   68.204625]  nvme1n1: p1 p2 p3 p4 p5 p6
[   68.204875] usb usb2: Product: xHCI Host Controller
[   68.205508] usb usb2: Manufacturer: Linux 6.4.0-3-amd64 xhci-hcd
[   68.205837] usb usb2: SerialNumber: :00:14.0
[   68.206236] hub 2-0:1.0: USB hub found
[   68.206585] hub 2-0:1.0: 6 ports detected
[   68.224577] nvme nvme0: 12/0/0 default/read/poll queues
[   68.229866]  nvme0n1: p1
[   68.235064] ahci :00:17.0: version 3.0
[   68.245738] ahci :00:17.0: AHCI 0001.0301 32 slots 6 ports 6 Gbps 0x3f 
impl SATA mode
[   68.246127] ahci :00:17.0: flags: 64bit ncq sntf clo only pio slum part 
ems deso sadm sds 
[   68.309605] scsi host0: ahci
[   68.310264] scsi host1: ahci
[   68.310866] scsi host2: ahci
[   68.311437] scsi host3: ahci
[   68.312021] scsi host4: ahci
[   68.312594] scsi host5: ahci
[   68.313025] ata1: SATA max UDMA/133 abar m2048@0x81402000 port 0x81402100 
irq 148
[   68.313454] ata2: SATA max UDMA/133 abar m2048@0x81402000 port 0x81402180 
irq 148
[   68.313869] ata3: SATA max UDMA/133 abar m2048@0x81402000 port 0x81402200 

Error : virHostCPUGetKVMMaxVCPUs: KVM is not supported on this platform: Function not implemented

2023-08-29 Thread Mario Marietto
Hello.

I'm running Debian bookworm on my ARM Chromebook,model "xe303c12" and I've
recompiled the kernel (5.4) to enable KVM,so now my system sounds like this
:


$ lsb_release -a

No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 12 (bookworm)
Release:12
Codename:   bookworm

$ uname -a
Linux chromarietto 5.4.244-stb-cbe
#8 SMP PREEMPT Sat Aug 19 22:19:32 UTC 2023 armv7l GNU/Linux

$ uname -r
5.4.244-stb-cbe

$ kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used

$ qemu-system-arm --version
QEMU emulator version 5.1.0 (v5.1.0-dirty)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers

$ python3 --version
Python 3.11.2

I have installed libvirt 9.7.0,qemu 5.1 and virt-manager from source code
with the final goal to be able to connect qemu,kvm and libvirt together to
virtualize FreeBSD 13.2 for arm 32 bit. Some useful informations about my
platform :


root@chromarietto:/home/marietto/Desktop# virt-host-validate


QEMU: Checking if device /dev/kvm exists  : PASS
QEMU: Checking if device /dev/kvm is accessible   : PASS
QEMU: Checking if device /dev/vhost-net exists: PASS
QEMU: Checking if device /dev/net/tun exists  : PASS
QEMU: Checking for cgroup 'cpu' controller support: PASS
QEMU: Checking for cgroup 'cpuacct' controller support: PASS
QEMU: Checking for cgroup 'cpuset' controller support : PASS
QEMU: Checking for cgroup 'memory' controller support : PASS
QEMU: Checking for cgroup 'devices' controller support: PASS
QEMU: Checking for cgroup 'blkio' controller support  : PASS

QEMU: Checking for device assignment IOMMU support
   : WARN
(No ACPI IORT table found, IOMMU not supported by this hardware platform)

QEMU: Checking for secure guest support
   : WARN
(Unknown if this platform has Secure Guest support)

LXC: Checking for Linux >= 2.6.26 : PASS
LXC: Checking for namespace ipc   : PASS
LXC: Checking for namespace mnt   : PASS
LXC: Checking for namespace pid   : PASS
LXC: Checking for namespace uts   : PASS
LXC: Checking for namespace net   : PASS
LXC: Checking for namespace user  : PASS
LXC: Checking for cgroup 'cpu' controller support : PASS
LXC: Checking for cgroup 'cpuacct' controller support : PASS
LXC: Checking for cgroup 'cpuset' controller support  : PASS
LXC: Checking for cgroup 'memory' controller support  : PASS
LXC: Checking for cgroup 'devices' controller support : PASS

LXC: Checking for cgroup 'freezer' controller support : FAIL
(Enable 'freezer' in kernel Kconfig file or mount/enable cgroup
controller in your system)

LXC: Checking for cgroup 'blkio' controller support   : PASS
LXC: Checking if device /sys/fs/fuse/connections exists   : PASS


# lsmod | grep kvm
no errors (I have embedded the options needed to enable KVM inside the kernel)


# virsh --connect qemu:///system capabilities | grep baselabel

+1002:+1002
+1002:+1002

The error that I'm not able to fix is the following one :


root@chromarietto:~#  virsh domcapabilities --machine virt
--emulatorbin /usr/local/bin/qemu-system-arm

2023-08-29 10:17:59.110+: 1763: error : virHostCPUGetKVMMaxVCPUs:1228 :
KVM is not supported on this platform: Function not implemented ;
error: failed to get emulator capabilities
error: KVM is not supported on this platform: Function not implemented

and this is the log that I've got when I ran libvirtd with the debug option
enabled


root@chromarietto:~# libvirtd --debug

[Tue, 29 Aug 2023 10:10:11 virt-manager 2141] DEBUG (createvm:494)
UEFI found, setting it as default.
[Tue, 29 Aug 2023 10:10:11 virt-manager 2141] DEBUG (createvm:728)
Guest type set to os_type=hvm, arch=armv7l, dom_type=kvm
[Tue, 29 Aug 2023 10:10:11 virt-manager 2141] DEBUG (guest:546) Prefer
EFI => True
2023-08-29 10:10:12.972+: 1765: error :
virHostCPUGetKVMMaxVCPUs:1228 : KVM is not supported on this platform:
Function not implemented
[Tue, 29 Aug 2023 10:10:12 virt-manager 2141] DEBUG
(domcapabilities:250) Error fetching domcapabilities XML
Traceback (most recent call last):
  File "/usr/local/share/virt-manager/virtinst/domcapabilities.py",
line 245, in build_from_params
xml = conn.getDomainCapabilities(emulator, arch,
  ^^
  File "/usr/lib/python3/dist-packages/libvirt.py", line 4612, in
getDomainCapabilities
raise 

Re: door bell like sound effect

2023-08-29 Thread zithro

On 29 Aug 2023 21:55, Greg Wooledge wrote:

On Tue, Aug 29, 2023 at 02:58:44PM -0400, gene heskett wrote:

E: Unable to locate package pactl


unicorn:~$ type pactl
pactl is /usr/bin/pactl
unicorn:~$ dpkg -S /usr/bin/pactl
pulseaudio-utils: /usr/bin/pactl



Or :

$ apt-file search pactl
[...]
pulseaudio-utils: /usr/bin/pactl
pulseaudio-utils: /usr/share/bash-completion/completions/pactl
pulseaudio-utils: /usr/share/man/man1/pactl.1.gz
[...]

It's useful when you don't have the full path of the file.
Downside, you need to install "apt-file" first.
Run "apt-file update" before using it, but iirc it warns you to do it if 
you forget.



--
++
zithro / Cyril



Re: Fallos en mi Debian

2023-08-29 Thread JavierDebian




El 29/8/23 a las 16:01, José Manuel (Abogado) escribió:


El 29/8/23 a las 7:29, Camaleón escribió:

El 2023-08-28 a las 20:51 +0100, José Manuel (Abogado) escribió:


Me aparecen dos fallos que no se porque sucede, por lo que me dirijo a
ustedes por si me pueden orientar, cosa que les agradezco de antemano.

Tengo Debian Bookworm

Primer fallo, en el arranque me aparece la palabra fallo en rojo pero al ser
rápido no me da tiempo a saber que lo que pone

Añado a lo ya indicado por Fran.

La orden «systemctl list-units --failed» te permite enumerar los
servicios fallidos.

Y con «journalctl -b | grep -i -e fallo -e failed» también podrás ver los 
registros
del arranque actual con la palabra «fallo» o «failed».
  

Segundo fallo por consola, al actualizar algún paquete al terminar a través
de sudo me aparece lo siguiente en las últimas líneas:

...

libdvd-pkg: Checking orig.tar integrity...
/usr/src/libdvd-pkg/libdvdcss_1.4.3.orig.tar.bz2: La suma coincide
libdvd-pkg: `apt-get check` failed, you may have broken packages.
Aborting...

No sé si has probado a reconfigurar el paquete con la orden «dpkg-reconfigure
libdvd-pkg».

Saludos,


Hola

Gracias por contestar a Fran y Camaleón

Poniendo los comandos que me indicas sale lo siguiente:

eb8cxw@debianPAPA:~$ systemctl list-units --failed
  UNIT    LOAD   ACTIVE SUB    DESCRIPTION
● accounts-daemon.service loaded failed failed Accounts Service

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.

eb8cxw@debianPAPA:~$ journalctl -b | grep -i -e fallo -e failed
Hint: You are currently not seeing messages from other users and the 
system.

  Users in the 'systemd-journal' group can see all messages. Pass -q to
  turn off this notice.
ago 29 15:45:45 debianPAPA wireplumber[1584]: Failed to set scheduler 
settings: Operación no permitida
ago 29 15:45:46 debianPAPA wireplumber[1584]: 
 failed to activate item: Objec

t activation aborted: proxy destroyed
ago 29 15:45:55 debianPAPA org_kde_powerdevil[1766]: org.kde.powerdevil: 
org.kde.powerdevil.chargethresholdhel
per.getthreshold failed "Charge thresholds are not supported by the 
kernel for this hardware"
ago 29 15:45:55 debianPAPA org_kde_powerdevil[1766]: org.kde.powerdevil: 
org.kde.powerdevil.backlighthelper.br

ightness failed
ago 29 15:45:57 debianPAPA org_kde_powerdevil[1766]: org.kde.powerdevil: 
org.kde.powerdevil.chargethresholdhel
per.getthreshold failed "Charge thresholds are not supported by the 
kernel for this hardware"
ago 29 15:45:57 debianPAPA kwin_x11[1715]: kf.config.core: 
"\"fsrestore1\" - conversion of \"0,0,0,0\" to QRec

t failed"
ago 29 15:45:57 debianPAPA kwin_x11[1715]: kf.config.core: 
"\"fsrestore2\" - conversion of \"0,0,0,0\" to QRec

t failed"
ago 29 15:46:02 debianPAPA kded5[1714]: org.kde.libkbolt: Failed to 
connect to Bolt manager DBus interface:
ago 29 15:47:25 debianPAPA dbus-daemon[1588]: [session uid=1000 
pid=1588] Activated service 'org.kde.KSplash'

failed: Process org.kde.KSplash exited with status 1
ago 29 16:46:47 debianPAPA plasmashell[4181]: libva error: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init

failed
ago 29 16:47:38 debianPAPA plasmashell[4181]: libva error: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init

failed
ago 29 16:47:39 debianPAPA plasmashell[4181]: libva error: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init

failed
ago 29 16:48:42 debianPAPA plasmashell[4181]: libva error: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init

failed
ago 29 16:49:02 debianPAPA plasmashell[4181]: libva error: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init

failed

No entiendo mucho pero parece que esta en el vídeo, ya me diréis,


--
Un saludo,
José Manuel
Gran Canaria/España

Si vas a escribir.. piensa en esto:
no digas nada que no sea mas precioso que el silencio!!!



Una solución posible, reinstalar todo lo relativo a intel y reiniciar el 
equipo


apt-get install --reinstall $(dpkg -l | grep ^ii | grep -i intel | awk 
'{print $2}')



JAP



Re: door bell like sound effect

2023-08-29 Thread Larry Martell
On Tue, Aug 29, 2023 at 12:59 PM Greg Wooledge  wrote:
>
> On Tue, Aug 29, 2023 at 09:29:35AM -0700, Larry Martell wrote:
> > find . -regex '.*\.snd$' -print
>
> That is an incredibly silly way to write
>
> find . -name '*.snd' -print

Gene said that was finding many files that had snd in their name and
not just as the terminal extension. So I gave a command that would
only find files that ended with .snd.

> But the bigger issue is that audio files may have MANY different
> extensions, with .snd being only one of them.

Yes, I know that - I was showing an example using what was previously posted.



Re: door bell like sound effect

2023-08-29 Thread Greg Wooledge
On Tue, Aug 29, 2023 at 09:29:35AM -0700, Larry Martell wrote:
> find . -regex '.*\.snd$' -print

That is an incredibly silly way to write

find . -name '*.snd' -print

But the bigger issue is that audio files may have MANY different
extensions, with .snd being only one of them.



Re: door bell like sound effect

2023-08-29 Thread Greg Wooledge
On Tue, Aug 29, 2023 at 02:58:44PM -0400, gene heskett wrote:
> E: Unable to locate package pactl

unicorn:~$ type pactl
pactl is /usr/bin/pactl
unicorn:~$ dpkg -S /usr/bin/pactl
pulseaudio-utils: /usr/bin/pactl



Re: Security question about daemon-init

2023-08-29 Thread Darac Marjal


On 29/08/2023 18:35, Bhasker C V wrote:

Apologies in advance for cross-group posting.

I have enabled selinux  and after carefully allowing certain 
permissions, I have put my system in enforcing mode


I do see a suspicious line like this


[  115.089395] audit: type=1400 audit(1693329979.841:11): avc:  denied 
 { getattr } for  pid=3104 comm="daemon-init" 
path="/home/bcv/.thunderbird" dev="dm-5" ino=257 
scontext=system_u:system_r:virtd_t:s0 
tcontext=system_u:object_r:thunderbird_home_t:s0 tclass=lnk_file 
permissive=0


I am not sure why on earth would daemon-init try to read .thunderbird 
directory under my homedir .


Has anyone faced this problem?

What is this daemon-init program and why does it want access to my 
home thunderbird directory ?


According to 
https://packages.debian.org/search?suite=bookworm=any=filename=contents=daemon-init 
there is no file within Debian Stable named "daemon-init".




Regards
Bhasker C V




OpenPGP_signature.asc
Description: OpenPGP digital signature


Re: Fallos en mi Debian

2023-08-29 Thread Abogado


El 29/8/23 a las 7:29, Camaleón escribió:

El 2023-08-28 a las 20:51 +0100, José Manuel (Abogado) escribió:


Me aparecen dos fallos que no se porque sucede, por lo que me dirijo a
ustedes por si me pueden orientar, cosa que les agradezco de antemano.

Tengo Debian Bookworm

Primer fallo, en el arranque me aparece la palabra fallo en rojo pero al ser
rápido no me da tiempo a saber que lo que pone

Añado a lo ya indicado por Fran.

La orden «systemctl list-units --failed» te permite enumerar los
servicios fallidos.

Y con «journalctl -b | grep -i -e fallo -e failed» también podrás ver los 
registros
del arranque actual con la palabra «fallo» o «failed».
  

Segundo fallo por consola, al actualizar algún paquete al terminar a través
de sudo me aparece lo siguiente en las últimas líneas:

...

libdvd-pkg: Checking orig.tar integrity...
/usr/src/libdvd-pkg/libdvdcss_1.4.3.orig.tar.bz2: La suma coincide
libdvd-pkg: `apt-get check` failed, you may have broken packages.
Aborting...

No sé si has probado a reconfigurar el paquete con la orden «dpkg-reconfigure
libdvd-pkg».

Saludos,


Hola

Gracias por contestar a Fran y Camaleón

Poniendo los comandos que me indicas sale lo siguiente:

eb8cxw@debianPAPA:~$ systemctl list-units --failed
 UNIT    LOAD   ACTIVE SUB    DESCRIPTION
● accounts-daemon.service loaded failed failed Accounts Service

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.

eb8cxw@debianPAPA:~$ journalctl -b | grep -i -e fallo -e failed
Hint: You are currently not seeing messages from other users and the 
system.

 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
ago 29 15:45:45 debianPAPA wireplumber[1584]: Failed to set scheduler 
settings: Operación no permitida
ago 29 15:45:46 debianPAPA wireplumber[1584]: 
 failed to activate item: Objec

t activation aborted: proxy destroyed
ago 29 15:45:55 debianPAPA org_kde_powerdevil[1766]: org.kde.powerdevil: 
org.kde.powerdevil.chargethresholdhel
per.getthreshold failed "Charge thresholds are not supported by the 
kernel for this hardware"
ago 29 15:45:55 debianPAPA org_kde_powerdevil[1766]: org.kde.powerdevil: 
org.kde.powerdevil.backlighthelper.br

ightness failed
ago 29 15:45:57 debianPAPA org_kde_powerdevil[1766]: org.kde.powerdevil: 
org.kde.powerdevil.chargethresholdhel
per.getthreshold failed "Charge thresholds are not supported by the 
kernel for this hardware"
ago 29 15:45:57 debianPAPA kwin_x11[1715]: kf.config.core: 
"\"fsrestore1\" - conversion of \"0,0,0,0\" to QRec

t failed"
ago 29 15:45:57 debianPAPA kwin_x11[1715]: kf.config.core: 
"\"fsrestore2\" - conversion of \"0,0,0,0\" to QRec

t failed"
ago 29 15:46:02 debianPAPA kded5[1714]: org.kde.libkbolt: Failed to 
connect to Bolt manager DBus interface:
ago 29 15:47:25 debianPAPA dbus-daemon[1588]: [session uid=1000 
pid=1588] Activated service 'org.kde.KSplash'

failed: Process org.kde.KSplash exited with status 1
ago 29 16:46:47 debianPAPA plasmashell[4181]: libva error: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init

failed
ago 29 16:47:38 debianPAPA plasmashell[4181]: libva error: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init

failed
ago 29 16:47:39 debianPAPA plasmashell[4181]: libva error: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init

failed
ago 29 16:48:42 debianPAPA plasmashell[4181]: libva error: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init

failed
ago 29 16:49:02 debianPAPA plasmashell[4181]: libva error: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init

failed

No entiendo mucho pero parece que esta en el vídeo, ya me diréis,


--
Un saludo,
José Manuel
Gran Canaria/España

Si vas a escribir.. piensa en esto:
no digas nada que no sea mas precioso que el silencio!!!


Re: door bell like sound effect

2023-08-29 Thread gene heskett

On 8/29/23 14:48, gene heskett wrote:

On 8/29/23 12:50, Max Nikulin wrote:

On 29/08/2023 22:41, Curt wrote:


You'd think it'd be simpler to write a script that runs overnight
checking for active audio sources (using maybe 'pacmd list-sink-inputs'
or similar) and logging them to a file when detected.


Is it possible to increase verbosity of logs of some pulseaudio module?

An attempt to react to events:

pactl subscribe  | while read -r v ; do [[ "$v" == *client* ]] && 
continue ; date; echo "$v" ; pacmd list-sink-inputs ; done


gene@coyote:~$ pactl subscribe  | while read -r v ; do [[ "$v" == 
*client* ]] && continue ; date; echo "$v" ; pacmd list-sink-inputs ; done

bash: pactl: command not found
gene@coyote:~$ sudo apt install pactl
[sudo] password for gene:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package pactl

Next?

I would not be surprised if some web application tries to notify about 
e.g. birthdays or some other events. Unsure if it is possible to do 
from a service worker or the site must be opened in a tab. The audio 
file may exist in browser cache only this case.


Thunderbird calendar, korganizer, alarm applets or applications may be 
suspected as well.



Those would all be under /home/me/.local? FWIW I am the only live user.

.


Cheers, Gene Heskett.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: door bell like sound effect

2023-08-29 Thread gene heskett

On 8/29/23 12:50, zithro wrote:

On 29 Aug 2023 18:19, gene heskett wrote:

On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:



Have you checked all the cron files and the systemd timers ?


cron yes, systemd timers no, don't know how.


man systemctl ; look for "timer" (in vi(m) use "/" to search) ?

$ systemctl list-timers



Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could also 
have used xmms, audacity, VLC, mpv, etc.


tried aplay, got server dead response. htop cannot find aplay,

Its usually in the middle of the night, waking me up because it is as 
loud as the real door bell would be. Last Saturday was unusual as it 
sounded off at 2:06 and 6:58 EDT.  Never occurred while I'm sitting 
here. Most of the noises it makes are 30 db quieter.


?!
I think you didn't understand what I meant.
To play a sound, there needs to be an app launching it.
So I suggested than instead of "find"ing the sound itself, you try to 
"grep" the application/executable name.
Agreed this could be long, as you don't know where that sound is played 
from.




Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: door bell like sound effect

2023-08-29 Thread gene heskett

On 8/29/23 12:50, Max Nikulin wrote:

On 29/08/2023 22:41, Curt wrote:


You'd think it'd be simpler to write a script that runs overnight
checking for active audio sources (using maybe 'pacmd list-sink-inputs'
or similar) and logging them to a file when detected.


Is it possible to increase verbosity of logs of some pulseaudio module?

An attempt to react to events:

pactl subscribe  | while read -r v ; do [[ "$v" == *client* ]] && 
continue ; date; echo "$v" ; pacmd list-sink-inputs ; done


I would not be surprised if some web application tries to notify about 
e.g. birthdays or some other events. Unsure if it is possible to do from 
a service worker or the site must be opened in a tab. The audio file may 
exist in browser cache only this case.


Thunderbird calendar, korganizer, alarm applets or applications may be 
suspected as well.



Those would all be under /home/me/.local? FWIW I am the only live user.

.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: door bell like sound effect

2023-08-29 Thread gene heskett

On 8/29/23 12:46, debian-u...@howorth.org.uk wrote:

gene heskett  wrote:

On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:

Greetings;

odd request:


Yeah, almost unreal ^^
   


Somewhere, for some unk reason, there is a sound file file that
plays at max volume, usually around 2 AM or slightly later, that
is very similar to the 40 yo doorbell in this house. A bing-bong
sound that differs from the real doorbell by maybe 5hz in pitch.
Wakes me up, spoiling a good nights sleep, maybe a dozen times a
year an apparently random dates.


Have you checked all the cron files and the systemd timers ?


cron yes, systemd timers no, don't know how.


To aid in finding it, what extension might that file be carrying
to indicate its a .snd fle, which according to grep on ls -lR's
output, does not exist in the thousands of files under hundreds of
random names.


The keyword above is extension, the find/grep tools seem to find a
match anywhere in a filename. getting a thousand hits, none of which
are the last 4 chars of a name.


RTFM? Or Larry's email :) And look for all the 'extensions' people have
mentioned.
  

What if you didn't use an extension when you created the audio
file ?

This file that sounds exactly like my doorbell has existed on my
24/7/365.25 on main system for at least 20 years. I'd like to A.
find it, B. find what condition uses it, fix the condition, or
even delete it.


Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which
application. With ALSA, you could have used "aplay FILE.wav", but
you could also have used xmms, audacity, VLC, mpv, etc.


Its usually in the middle of the night, waking me up because it is as
loud as the real door bell would be. Last Saturday was unusual as it
sounded off at 2:06 and 6:58 EDT.  Never occurred while I'm sitting
here. Most of the noises it makes are 30 db quieter.


So don't try to find it when it happens. Just make a note of the exact
time and look in the morning after breakfast and coffee!

.
Now there's an idea. With macular degeneration setting in, night time is 
not an ideal time to search a hi res screen for me.


Thanks

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: door bell like sound effect

2023-08-29 Thread gene heskett

On 8/29/23 12:30, Larry Martell wrote:

On Tue, Aug 29, 2023 at 9:19 AM gene heskett  wrote:


On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:

To aid in finding it, what extension might that file be carrying to
indicate its a .snd fle, which according to grep on ls -lR's output,
does not exist in the thousands of files under hundreds of random names.


The keyword above is extension, the find/grep tools seem to find a match
anywhere in a filename. getting a thousand hits, none of which are the
last 4 chars of a name.


find . -regex '.*\.snd$' -print
.
which returns nothing unless I start it at / then I get about a dozen no 
permissions because I don't allow root and ssh in the same building. 
All my other machines are mounted as me using sshfs.

And does not find anything when invoked in a suspected path.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: [IMPORTANT] Debian images no longer works for GPU driver installation with apt update

2023-08-29 Thread Andrew M.A. Cater
On Tue, Aug 29, 2023 at 10:53:35AM -0700, Wenyan Hu wrote:
> Hi Team,
> 
> Google's GPU driver installation no longer works for Debian images since
> 08/23/2023.
> 
> Google is using
> https://cloud.google.com/compute/docs/gpus/install-drivers-gpu#installation_scripts
> to
> install GPU drivers on Debian images. It executes scripts as
> https://raw.githubusercontent.com/GoogleCloudPlatform/compute-gpu-installation/main/linux/install_gpu_driver.py
> .
> 

Maybe take that up with Google - their script and their engineers to fix?

> Now for the latest images, if running scripts as below:
> 
> ```
> $ apt-cache search linux-headers | grep -i $(uname -r)
> $ apt update
> $apt install -y linux-headers-5.10.0-24-cloud-amd64
> software-properties-common pciutils gcc make dkms
> ```
> After running `apt update`, we find the package
> linux-headers-5.10.0-24-cloud-amd64 no longer exists, which results in the
> `apt install linux-headers-5.10.0-24-cloud-amd64` failure.
> 

apt update and then apt upgrade, maybe, to bring the system up to date
rather than just updating the list of available packages?

> It seems after the `apt update`, the index somehow no longer points to
> linux-headers-5.10.0-23-cloud-amd64 and linux-headers-5.10.0-24-cloud-amd64.
> 
> I know it would work if we (1) not do `apt update`, or (2) install newer
> kernel packages.

If you *only* do apt update, nothing has changed.

> But for (1), the apt update is required for our other package
> installations, (2) the kernel package update needs VM rebooting.
> 

This is always likely to be the case: if you do a kernel package update
you *should* reboot to the new kernel, since this is likely to have fixed
security or other problems.

> It is now blocking my team's image release and product functionality
> because we need the GPU driver installation without VM rebooting.
> 

As above, you will need to reboot the VM eventually.

> Could you please prioritize the issue and provide some tips or support?
> 

This is an end user support and information list: we can't provide an
immediate fix to the issue. I would have suggested the debian cloud image
team if I hadn't already suggested taking this up with Google.

> Thanks,
> Wenyan

With every good wish,

Andy Cater



Re: Debian images no longer works for GPU driver installation with apt update

2023-08-29 Thread Michael Kjörling
On 29 Aug 2023 10:53 -0700, from wen...@google.com (Wenyan Hu):
> Hi Team,

You're in the wrong place. This is a mailing list for Debian _users_
willing to help each other out. Some subscribers might be officially
involved with the Debian project in various capacities, but that's not
the primary purpose of the debian-user mailing list.


> $ apt-cache search linux-headers | grep -i $(uname -r)
> $ apt update
> $apt install -y linux-headers-5.10.0-24-cloud-amd64

It looks like you might be relying on package versions being the same
before and after running apt update. That is an invalid assumption.


> Could you please prioritize the issue and provide some tips or support?

If something within the Debian distribution is broken, see
https://www.debian.org/Bugs/ for how to file a bug report.

However, that your script is apparently expecting a specific version
of a kernel package, or making assumptions about what changes happen
as part of an apt{,-get} update, hardly seems to me as though
something in Debian is broken. That seems more likely to be a problem
with assumptions made in your script. Kernel packages are upgraded
regularly in this manner.

See also http://www.catb.org/esr/faqs/smart-questions.html#urgent

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”



Re: Thunderbird vs Claws Mail

2023-08-29 Thread Frank Lanitz

Hi,

On 15.08.23 21:48, Russell L. Harris wrote:

Consider evolution.


Tried it. Used >6GB RAM.

.f


OpenPGP_signature.asc
Description: OpenPGP digital signature


[IMPORTANT] Debian images no longer works for GPU driver installation with apt update

2023-08-29 Thread Wenyan Hu
Hi Team,

Google's GPU driver installation no longer works for Debian images since
08/23/2023.

Google is using
https://cloud.google.com/compute/docs/gpus/install-drivers-gpu#installation_scripts
to
install GPU drivers on Debian images. It executes scripts as
https://raw.githubusercontent.com/GoogleCloudPlatform/compute-gpu-installation/main/linux/install_gpu_driver.py
.

Now for the latest images, if running scripts as below:

```
$ apt-cache search linux-headers | grep -i $(uname -r)
$ apt update
$apt install -y linux-headers-5.10.0-24-cloud-amd64
software-properties-common pciutils gcc make dkms
```
After running `apt update`, we find the package
linux-headers-5.10.0-24-cloud-amd64 no longer exists, which results in the
`apt install linux-headers-5.10.0-24-cloud-amd64` failure.

It seems after the `apt update`, the index somehow no longer points to
linux-headers-5.10.0-23-cloud-amd64 and linux-headers-5.10.0-24-cloud-amd64.

I know it would work if we (1) not do `apt update`, or (2) install newer
kernel packages.
But for (1), the apt update is required for our other package
installations, (2) the kernel package update needs VM rebooting.

It is now blocking my team's image release and product functionality
because we need the GPU driver installation without VM rebooting.

Could you please prioritize the issue and provide some tips or support?

Thanks,
Wenyan


Security question about daemon-init

2023-08-29 Thread Bhasker C V
Apologies in advance for cross-group posting.

I have enabled selinux  and after carefully allowing certain permissions, I
have put my system in enforcing mode

I do see a suspicious line like this


[  115.089395] audit: type=1400 audit(1693329979.841:11): avc:  denied  {
getattr } for  pid=3104 comm="daemon-init" path="/home/bcv/.thunderbird"
dev="dm-5" ino=257 scontext=system_u:system_r:virtd_t:s0
tcontext=system_u:object_r:thunderbird_home_t:s0 tclass=lnk_file
permissive=0

I am not sure why on earth would daemon-init try to read .thunderbird
directory under my homedir .

Has anyone faced this problem?

What is this daemon-init program and why does it want access to my home
thunderbird directory ?

Regards
Bhasker C V


Re: door bell like sound effect

2023-08-29 Thread gene heskett

On 8/29/23 07:22, Greg Wooledge wrote:

On Tue, Aug 29, 2023 at 11:10:17AM +0200, Michael wrote:

On Tuesday, 29 August 2023 03:56:55 CEST, Greg Wooledge wrote:


The problem is, most Debian systems are set up to mount the core file
systems with "relatime".  This means you don't have a record of the
last time each file was accessed, so you can't ask the computer which
files were most recently opened.


hm...

i was curious about that and read the man page for 'mount(8)', in section
FILESYSTEM-INDEPENDENT MOUNT OPTIONS i found the following:

relatime
  Update inode access times relative to modify or change time.
  Access time is only updated if the previous access time was
  earlier than the current modify or change time. [...]

so my understanding is, that access time is indeed updated if 'relatime' is
used as a mount option. to prevent updating access times 'noatime' should be
used.


It's changed *only* under the specific circumstance where the file has
been modified since it was last read.  If the file hasn't been written to
(or metadata changed), atime isn't updated.

So, imagine there's a doorbell.au file somewhere in Gene's file system,
and that this file has been played, once in a while, for several years.
It hasn't been *modified* in all that time.  It's a very static file.
But every once in a while, something opens it and reads it.

In that situation, the mtime on the file is going to be "whenever it
was created" (close enough for this discussion), and the atime is going
to be "whenever it was first played", perhaps 5 or 10 or 20 years ago.
Even though it was just played a few days ago.

Long story short, sorting files by atime isn't going to reveal it.
Unless of course Gene's file systems are mounted with an overriding
option, and he's getting full historic atime behavior.


That would be nice, but I expect it would also be quite speed damaging...

.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: door bell like sound effect

2023-08-29 Thread gene heskett

On 8/28/23 23:44, Greg Wooledge wrote:

On Mon, Aug 28, 2023 at 11:32:25PM -0400, songbird wrote:

Greg Wooledge wrote:

The problem is, most Debian systems are set up to mount the core file
systems with "relatime".  This means you don't have a record of the
last time each file was accessed, so you can't ask the computer which
files were most recently opened.


   i don't have that one set at all in my fstab.


It's a default option.  It doesn't have to be visible in fstab.
Look at the *output of mount* instead.

unicorn:~$ cat /etc/fstab
[...]
# / was on /dev/sda7 during installation
UUID=c4691ccb-2090-491e-8e82-d7cc822db04a /   ext4
errors=remount-ro 0   1
[...]

unicorn:~$ mount | grep 'on / '
/dev/sda7 on / type ext4 (rw,relatime,errors=remount-ro)

.

And that's pretty universal here.  My listing is considerably longer.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: door bell like sound effect

2023-08-29 Thread gene heskett

On 8/28/23 21:32, songbird wrote:

Cindy Sue Causey wrote:
...

That triggered yet another thought: What about some kind of a file
search that narrows down "Last Accessed" data for all the various
sound file types?


   most recently accessed files could be located via find
command.  i assumed Gene would know how to do that...



Wrong.


Personal experience is that manually viewing e.g. /usr/share isn't
100% perfect. It's been a couple years, but I've also seen sound files
stored more locally within some given package's own parent/child file
hierarchy. That helps make our favorite file search programs
priceless.

Cindy :)


   if the system can't tell you what's been recently
accessed and you are on-line then you need to go
off-line until you've figured it out.

   if Gene leaves his network up and accessible to
others all night when he's sleeping then perhaps he
needs to bring it down and that will slay the
gremlins...


   songbird

.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: door bell like sound effect

2023-08-29 Thread zithro

On 29 Aug 2023 18:35, gene heskett wrote:

I have no known enemies left, I've outlived them all. And there is a PIR 
facing out that see's a 34 yo pin oak moving in the wind many times a day.


What about their families ? ^^

Joke aside, trees don't produce heat themselves (AFAIK ...), so the only 
way is to reflect the IR from the sun.

Or there is some animal walking the tree.

So your PIR is either broken or way too sensitive.
Some provide a sensitivity setting via a potentiometer, but YMMV.
Usually, sensitivity is correlated to the range (ie. meters) of the IR 
sensor.



--
++
zithro / Cyril



Re: door bell like sound effect

2023-08-29 Thread zithro

On 29 Aug 2023 18:19, gene heskett wrote:

On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:



Have you checked all the cron files and the systemd timers ?


cron yes, systemd timers no, don't know how.


man systemctl ; look for "timer" (in vi(m) use "/" to search) ?

$ systemctl list-timers



Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could also 
have used xmms, audacity, VLC, mpv, etc.


Its usually in the middle of the night, waking me up because it is as 
loud as the real door bell would be. Last Saturday was unusual as it 
sounded off at 2:06 and 6:58 EDT.  Never occurred while I'm sitting 
here. Most of the noises it makes are 30 db quieter.


?!
I think you didn't understand what I meant.
To play a sound, there needs to be an app launching it.
So I suggested than instead of "find"ing the sound itself, you try to 
"grep" the application/executable name.
Agreed this could be long, as you don't know where that sound is played 
from.


--
++
zithro / Cyril



Re: door bell like sound effect

2023-08-29 Thread Max Nikulin

On 29/08/2023 22:41, Curt wrote:


You'd think it'd be simpler to write a script that runs overnight
checking for active audio sources (using maybe 'pacmd list-sink-inputs'
or similar) and logging them to a file when detected.


Is it possible to increase verbosity of logs of some pulseaudio module?

An attempt to react to events:

pactl subscribe  | while read -r v ; do [[ "$v" == *client* ]] && 
continue ; date; echo "$v" ; pacmd list-sink-inputs ; done


I would not be surprised if some web application tries to notify about 
e.g. birthdays or some other events. Unsure if it is possible to do from 
a service worker or the site must be opened in a tab. The audio file may 
exist in browser cache only this case.


Thunderbird calendar, korganizer, alarm applets or applications may be 
suspected as well.




Re: door bell like sound effect

2023-08-29 Thread debian-user
gene heskett  wrote:
> On 8/28/23 12:20, zithro wrote:
> > On 28 Aug 2023 09:29, gene heskett wrote:  
> >> Greetings;
> >>
> >> odd request:  
> > 
> > Yeah, almost unreal ^^
> >   
> >>
> >> Somewhere, for some unk reason, there is a sound file file that
> >> plays at max volume, usually around 2 AM or slightly later, that
> >> is very similar to the 40 yo doorbell in this house. A bing-bong
> >> sound that differs from the real doorbell by maybe 5hz in pitch.
> >> Wakes me up, spoiling a good nights sleep, maybe a dozen times a
> >> year an apparently random dates.  
> > 
> > Have you checked all the cron files and the systemd timers ?  
> 
> cron yes, systemd timers no, don't know how.
> 
> >> To aid in finding it, what extension might that file be carrying
> >> to indicate its a .snd fle, which according to grep on ls -lR's
> >> output, does not exist in the thousands of files under hundreds of
> >> random names.  
> 
> The keyword above is extension, the find/grep tools seem to find a
> match anywhere in a filename. getting a thousand hits, none of which
> are the last 4 chars of a name.

RTFM? Or Larry's email :) And look for all the 'extensions' people have
mentioned.
 
> > What if you didn't use an extension when you created the audio
> > file ? 
> >> This file that sounds exactly like my doorbell has existed on my 
> >> 24/7/365.25 on main system for at least 20 years. I'd like to A.
> >> find it, B. find what condition uses it, fix the condition, or
> >> even delete it.  
> > 
> > Maybe find the script(s) where you use this sound ?
> > I mean to find HOW you played this sound, ie. with which
> > application. With ALSA, you could have used "aplay FILE.wav", but
> > you could also have used xmms, audacity, VLC, mpv, etc.  
> 
> Its usually in the middle of the night, waking me up because it is as 
> loud as the real door bell would be. Last Saturday was unusual as it 
> sounded off at 2:06 and 6:58 EDT.  Never occurred while I'm sitting 
> here. Most of the noises it makes are 30 db quieter.

So don't try to find it when it happens. Just make a note of the exact
time and look in the morning after breakfast and coffee!



Re: door bell like sound effect

2023-08-29 Thread gene heskett

On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:

Greetings;

odd request:


Yeah, almost unreal ^^



Somewhere, for some unk reason, there is a sound file file that plays 
at max volume, usually around 2 AM or slightly later, that is very 
similar to the 40 yo doorbell in this house. A bing-bong sound that 
differs from the real doorbell by maybe 5hz in pitch. Wakes me up, 
spoiling a good nights sleep, maybe a dozen times a year an apparently 
random dates.


Have you checked all the cron files and the systemd timers ?

To aid in finding it, what extension might that file be carrying to 
indicate its a .snd fle, which according to grep on ls -lR's output, 
does not exist in the thousands of files under hundreds of random names.


What if you didn't use an extension when you created the audio file ?

This file that sounds exactly like my doorbell has existed on my 
24/7/365.25 on main system for at least 20 years. I'd like to A. find 
it, B. find what condition uses it, fix the condition, or even delete it.


Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could also have 
used xmms, audacity, VLC, mpv, etc.


How can I best do that? updatedb, followed by locate door or locate 
bell reports nothing.


locate bing ; locate bong ; locate gong ? You wrote the sound was like 
"bing-bong" ^^
In this case, I would recommend to use "find" as root, rather than 
"locate", just to prevent the fact the file could not be indexed by 
updatedb for whatever reason, and as root in case you put the script 
and/or sound in a folder only accessible by root.
PS: last I used locate was on Slackware 13.37, so others may point 
errors in that thinking.


There are now 2 different PIR based devices watching that doorbell 
button, which trigger on the neighbors cat walking by but remain 
silent when this sound jacks me up in the middle of the night.


If you have ennemies, they can use a long stick to ring the bell to 
evade PIR detection ^^


I have no known enemies left, I've outlived them all. And there is a PIR 
facing out that see's a 34 yo pin oak moving in the wind many times a day.


Any help in finding this will be hugely appreciated.

Cheers, Gene Heskett.




Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: door bell like sound effect

2023-08-29 Thread Larry Martell
On Tue, Aug 29, 2023 at 9:19 AM gene heskett  wrote:
>
> On 8/28/23 12:20, zithro wrote:
> > On 28 Aug 2023 09:29, gene heskett wrote:
> >> To aid in finding it, what extension might that file be carrying to
> >> indicate its a .snd fle, which according to grep on ls -lR's output,
> >> does not exist in the thousands of files under hundreds of random names.
>
> The keyword above is extension, the find/grep tools seem to find a match
> anywhere in a filename. getting a thousand hits, none of which are the
> last 4 chars of a name.

find . -regex '.*\.snd$' -print



Re: door bell like sound effect

2023-08-29 Thread gene heskett

On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:

Greetings;

odd request:


Yeah, almost unreal ^^



Somewhere, for some unk reason, there is a sound file file that plays 
at max volume, usually around 2 AM or slightly later, that is very 
similar to the 40 yo doorbell in this house. A bing-bong sound that 
differs from the real doorbell by maybe 5hz in pitch. Wakes me up, 
spoiling a good nights sleep, maybe a dozen times a year an apparently 
random dates.


Have you checked all the cron files and the systemd timers ?


cron yes, systemd timers no, don't know how.

To aid in finding it, what extension might that file be carrying to 
indicate its a .snd fle, which according to grep on ls -lR's output, 
does not exist in the thousands of files under hundreds of random names.


The keyword above is extension, the find/grep tools seem to find a match 
anywhere in a filename. getting a thousand hits, none of which are the 
last 4 chars of a name.



What if you didn't use an extension when you created the audio file ?

This file that sounds exactly like my doorbell has existed on my 
24/7/365.25 on main system for at least 20 years. I'd like to A. find 
it, B. find what condition uses it, fix the condition, or even delete it.


Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could also have 
used xmms, audacity, VLC, mpv, etc.


Its usually in the middle of the night, waking me up because it is as 
loud as the real door bell would be. Last Saturday was unusual as it 
sounded off at 2:06 and 6:58 EDT.  Never occurred while I'm sitting 
here. Most of the noises it makes are 30 db quieter.




How can I best do that? updatedb, followed by locate door or locate 
bell reports nothing.


locate bing ; locate bong ; locate gong ? You wrote the sound was like 
"bing-bong" ^^
In this case, I would recommend to use "find" as root, rather than 
"locate", just to prevent the fact the file could not be indexed by 
updatedb for whatever reason, and as root in case you put the script 
and/or sound in a folder only accessible by root.
PS: last I used locate was on Slackware 13.37, so others may point 
errors in that thinking.


There are now 2 different PIR based devices watching that doorbell 
button, which trigger on the neighbors cat walking by but remain 
silent when this sound jacks me up in the middle of the night.


If you have ennemies, they can use a long stick to ring the bell to 
evade PIR detection ^^




Any help in finding this will be hugely appreciated.

Cheers, Gene Heskett.




Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: door bell like sound effect

2023-08-29 Thread gene heskett

On 8/28/23 05:26, Michel Verdier wrote:

On 2023-08-28, gene heskett wrote:


Any help in finding this will be hugely appreciated.


As you are awake and know the time of ringing do you check the logs
around that time ?

.
I checked them a couple minutes after the last time but nothing stood 
out as a likely suspect. Mostly cups related traffic. It has to update 
the list of available printers every 5 or so minutes.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 



Re: Not authorized to run synaptic

2023-08-29 Thread Joe
On Tue, 29 Aug 2023 10:11:01 -0300
Bruno Schneider  wrote:

> Apparently, some service needed to be restarted, because the problem
> went away after a reboot. Perhaps policykit?
> 
> Anyway, for future reference, I'm not on the sudo group and I found
> nothing interesting on changelogs. Something (I guess pkexec) asks for
> the root password (not the user's password) before allowing synaptic
> to run and doesn't care whether the user is allowed to sudo (my user
> is allowed).
> 

That agrees with my experience. I don't use a sudo group, but I am of
course in sudoers. As far as I'm aware, the only other application
asking for the root password is gparted, though there may be other
system applications that do.

-- 
Joe



Re: door bell like sound effect

2023-08-29 Thread Curt
On 2023-08-29, Greg Wooledge  wrote:
>
> There's still going to be a whole lotta searching through the haystack
> to find the needle.  Obviously, knowing the approximate date and time
> the file was last read would be of tremendous help, as you can zoom in
> on that part of the results.
>
>

You'd think it'd be simpler to write a script that runs overnight
checking for active audio sources (using maybe 'pacmd list-sink-inputs'
or similar) and logging them to a file when detected.

Easier said than done, I guess!



Re: Not authorized to run synaptic

2023-08-29 Thread Brad Rogers
On Tue, 29 Aug 2023 10:11:01 -0300
Bruno Schneider  wrote:

Hello Bruno,

>Apparently, some service needed to be restarted, because the problem
>went away after a reboot. Perhaps policykit?

Almost certainly;

Here, Synaptic required root password *until* policykit was installed
(as a dependency of another package) when things changed and Synaptic
now requires user's password.

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
Do you want to play?
Play With Me - Extreme


pgp6bJmVytVpa.pgp
Description: OpenPGP digital signature


Re: door bell like sound effect

2023-08-29 Thread David Wright
On Tue 29 Aug 2023 at 08:37:00 (-0400), Greg Wooledge wrote:
> On Tue, Aug 29, 2023 at 07:46:16AM -0400, songbird wrote:
> >   ok, i understand that but my command 
> > 
> > $ alias aq='find . -amin -30'
> > $ aq 
> > 
> > works as it should.
> 
> Oh.  I guess I should have read the *entire* section of the man page.
> 
>relatime
>[...]
>Since Linux 2.6.30, the kernel defaults to the behavior provided by
>this option (unless noatime was specified), and the strictatime
>option is required to obtain traditional semantics. In addition,
>since Linux 2.6.30, the file’s last access time is always updated
>if it is more than 1 day old.
> 
> It's that last sentence that changes everything.  So then, I guess in
> theory Gene *could* search for all of the most recently used files on
> his system, and have a snowball's chance in hell of finding the doorbell
> audio file that way.

IIRC, the d-i by default adds noatime to entries in /etc/fstab for SSDs,
which I thought Gene had now converted to. However, Gene's entries may
have been inherited from older installations, so all this might work.

> Actually doing that could be trickier than you might guess.  If we
> limit ourselves to searching one file system (or partial file system,
> e.g. the /usr directory) at a time, and therefore don't need to supply
> exclude patterns, here's a bash function that might be helpful:
> 
> rlartu() {
> local day time path
> find "${1:-.}" -type f -printf '%A@/%AY-%Am-%Ad/%AT/%p\0' | sort -zn |
> while IFS=/ read -rd '' _ day time path; do
> printf '%s %s %s\n' "$day" "${time%.*}" "$path"
> done
> }
> 
> I would suggest using this in /home and /usr first, unless Gene can
> think of more appropriate starting points.
> 
> There's still going to be a whole lotta searching through the haystack
> to find the needle.  Obviously, knowing the approximate date and time
> the file was last read would be of tremendous help, as you can zoom in
> on that part of the results.

Cheers,
David.



Re: Re : Re: Re : Re: Problème installateur Debian avancé

2023-08-29 Thread NoSpam

Bonjour

Le 29/08/2023 à 16:54, k6dedi...@free.fr a écrit :

Merci pour cette réponse.
L'utilitaire d'installation à rendu mes deux partitions EFI et boot en système 
inconnu.
Impossible de les reformater avec partition manager.
Je me replonge dans les outils sfdisk et mkfs pour voir si je peux les 
reformater.

Parted sait faire tout cela

Cassis


- Mail d'origine -
De: NoSpam 
À: debian-user-french@lists.debian.org
Envoyé: Mon, 28 Aug 2023 19:38:11 +0200 (CEST)
Objet: Re: Re : Re: Problème installateur Debian avancé

Le default login est user, MdP est live. sudo devrait fonctionner sans
mot de passe.

Le 28/08/2023 à 19:19, k6dedi...@free.fr a écrit :

Bonjour,
Merci de cette réponse.

Je suis avec une clé USB avec l'image ISO copiée par dd
Sous Debian 12 live, le système me demande un mot de passe pour le super 
utilisateur.
Avec partition manager il m'est demandé un mot de passe et je ne sais pas où il 
est indiqué.
J'ai essayé 'debian' puis 'Debian' et ça ne fonctionne pas.

Avec la console 'fdisk -l' n'est pas implémenté, et 'cfdisk' n'a pas d'option 
équivalente.

Je patauge.
Cassis




- Mail d'origine -
De: NoSpam 
À: debian-user-french@lists.debian.org
Envoyé: Mon, 28 Aug 2023 10:00:31 +0200 (CEST)
Objet: Re: Problème installateur Debian avancé

Bonjour

Le 28/08/2023 à 08:03, k6dedi...@free.fr a écrit :

Bonjour à tous,
Je cherche à installer Debian 12.
Je passe par le mode avancé.
Après avoir configuré les partitions ainsi :
partition 1   536,9 MB ESP  EFI System P
partition 2   805,3 MB ext4 /boot
partition 3 8,6 GB swap swap
partition 637,6 GB ext4 /
partition 716,1 GB ext4 /home

Puis validé cette configuration j’obtiens le message :
« La tentative de montage d’un système de fichiers vfat de SCSI2 (0,0,0). 
partition n°1 (sda) sur /boot/efi a échoué. »

La partition 1 a été reformatée par l’utilitaire de l’installateur.
Pour la partition 2 l’installateur modifié ainsi :
partition 2   805,3 MB ESP
Si je valide j’obtiens le même message.

Pouvez-vous m’aider car je peux aller plus loin dans l'installation.

Une fois démarré sur la clé, essayez de monter la partition: si cela
échoue, il y a effectivement un problème avec celle ci, il faudra la
recréer.

Un lien
https://wiki.archlinux.org/title/EFI_system_partition_(Fran%C3%A7ais)




Re : Re: Re : Re: Problème installateur Debian avancé

2023-08-29 Thread k6dedijon
Merci pour cette réponse.
L'utilitaire d'installation à rendu mes deux partitions EFI et boot en système 
inconnu.
Impossible de les reformater avec partition manager.
Je me replonge dans les outils sfdisk et mkfs pour voir si je peux les 
reformater.
Cassis


- Mail d'origine -
De: NoSpam 
À: debian-user-french@lists.debian.org
Envoyé: Mon, 28 Aug 2023 19:38:11 +0200 (CEST)
Objet: Re: Re : Re: Problème installateur Debian avancé

Le default login est user, MdP est live. sudo devrait fonctionner sans 
mot de passe.

Le 28/08/2023 à 19:19, k6dedi...@free.fr a écrit :
> Bonjour,
> Merci de cette réponse.
>
> Je suis avec une clé USB avec l'image ISO copiée par dd
> Sous Debian 12 live, le système me demande un mot de passe pour le super 
> utilisateur.
> Avec partition manager il m'est demandé un mot de passe et je ne sais pas où 
> il est indiqué.
> J'ai essayé 'debian' puis 'Debian' et ça ne fonctionne pas.
>
> Avec la console 'fdisk -l' n'est pas implémenté, et 'cfdisk' n'a pas d'option 
> équivalente.
>
> Je patauge.
> Cassis
>
>
>
>
> - Mail d'origine -
> De: NoSpam 
> À: debian-user-french@lists.debian.org
> Envoyé: Mon, 28 Aug 2023 10:00:31 +0200 (CEST)
> Objet: Re: Problème installateur Debian avancé
>
> Bonjour
>
> Le 28/08/2023 à 08:03, k6dedi...@free.fr a écrit :
>> Bonjour à tous,
>> Je cherche à installer Debian 12.
>> Je passe par le mode avancé.
>> Après avoir configuré les partitions ainsi :
>> partition 1   536,9 MB ESP  EFI System P
>> partition 2   805,3 MB ext4 /boot
>> partition 3 8,6 GB swap swap
>> partition 637,6 GB ext4 /
>> partition 716,1 GB ext4 /home
>>
>> Puis validé cette configuration j’obtiens le message :
>> « La tentative de montage d’un système de fichiers vfat de SCSI2 (0,0,0). 
>> partition n°1 (sda) sur /boot/efi a échoué. »
>>
>> La partition 1 a été reformatée par l’utilitaire de l’installateur.
>> Pour la partition 2 l’installateur modifié ainsi :
>> partition 2   805,3 MB ESP
>> Si je valide j’obtiens le même message.
>>
>> Pouvez-vous m’aider car je peux aller plus loin dans l'installation.
> Une fois démarré sur la clé, essayez de monter la partition: si cela
> échoue, il y a effectivement un problème avec celle ci, il faudra la
> recréer.
>
> Un lien
> https://wiki.archlinux.org/title/EFI_system_partition_(Fran%C3%A7ais)




Desconfiguracin

2023-08-29 Thread Darío
Hola buen día! estoy teniendo un problema con el sonido en Debian 12, y está 
pasando siempre.
Vengo de la actualización de 11 a 12 en una portatil Dell E6420 (algo viejita 
pero anda perfecto) y se me desconfigura el sonido teniendo que ir siempre al 
ícono de audio (en Mate) y encontrar a cuál corresponde, a veces siempre 
diferente a una configuración anterior incluso.
Anteriormente no pasaba con Debian 11, pero es seguido e incluso ahora que 
tengo que usar zoom no se me escucha. Cuando en OBS puede grabar con el 
micrófono.
No sé qué otra manera de configurar el audio realmente, no fue algo de 
preocuparme porque siempre anduvo perfecto, y lo solucioné con ese ícono, 
además de que nunca usé el micrófono incorporado de la portátil.

¿Cómo puedo dejar definitivamente configurado sin que se desconfigure? ¿y por 
qué puede llegar a ocurrir?

Saludos y gracias!
Darío

Re: Not authorized to run synaptic

2023-08-29 Thread Bruno Schneider
Apparently, some service needed to be restarted, because the problem
went away after a reboot. Perhaps policykit?

Anyway, for future reference, I'm not on the sudo group and I found
nothing interesting on changelogs. Something (I guess pkexec) asks for
the root password (not the user's password) before allowing synaptic
to run and doesn't care whether the user is allowed to sudo (my user
is allowed).

-- 
Bruno Schneider



Re: Mise à jours et Update Stretch - Problème de dépôt

2023-08-29 Thread Michel Verdier
Le 29 août 2023 Hugues MORIN-TRENEULE a écrit :

> Concernant les dépôts "security" et "volatile", existe-t-il aussi des
> dépôts archive que je pourrai utiliser?

Le mieux est de les commenter durant les upgrade et de les rebrancher
seulement quand tout est stabilisé pour un ultime upgrade. C'est
d'ailleurs ce qui est préconisé pour l'upgrade bullseye -> bookworm.

Et n'oublie pas l'upgrade en 2 temps.

https://www.debian.org/releases/bookworm/amd64/release-notes/ch-upgrading.fr.html#minimal-upgrade



Re: Mise à jours et Update Stretch - Problème de dépôt

2023-08-29 Thread Sébastien NOBILI

Bonjour,

Le 2023-08-29 13:53, Hugues MORIN-TRENEULE a écrit :

Pour le dépot principal (http://ftp.fr.debian.org/debian/ stretch) ,
en cherchant, j'ai trouvé le depot archive Debian:
http://archive.debian.org/debian
Est ce que vous pourriez me confirmer qu'il me permettra de mettre les
paquets de stretch à jours jusqu'à leur dernière version.


C'est ça, les paquets des vieilles versions de Debian sont transférés 
dans

archive.debian.org.

Il suffit donc de mettre à jour l'URL dans sources.list pour pouvoir y
accéder.


Concernant les dépôts "security" et "volatile", existe-t-il aussi
des dépôts archive que je pourrai utiliser?


Ça ne me paraît pas nécessaire.

security.debian.org permet de corriger les failles sur un système. 
Puisque
le système doit être mis à jour vers la (les) versions ultérieures, ça 
n'a
pas grand intérêt de le patcher (sauf pour se protéger contre une 
attaque
pendant la mise à jour, mais la probabilité est mince). Sinon, ces 
lignes

devraient faire l'affaire :

deb http://archive.debian.org/debian/ stretch main non-free contrib
deb http://archive.debian.org/debian-security/ stretch/updates main 
non-free contrib


Quant à volatile.debian.org, je n'ai jamais utilisé.

Sébastien



Re: Mise à jours et Update Stretch - Problème de dépôt

2023-08-29 Thread Haricophile
Le Tue, 29 Aug 2023 13:53:13 +0200,
Hugues MORIN-TRENEULE  a écrit :

> Pour le dépot principal (http://ftp.fr.debian.org/debian/ stretch) ,
> en cherchant, j'ai trouvé le depot archive Debian:
> http://archive.debian.org/debian
> Est ce que vous pourriez me confirmer qu'il me permettra de mettre les
> paquets de stretch à jours jusqu'à leur dernière version.

Je viens d'upgrader une machine dans ces conditions.
- J'utilise aptitude, depuis qu'il existe.
- je préfère travailler en console des fois que l'interface
  graphique se plante...
- J'utilise un câble réseau, tant pour la vitesse que pour la
  simplicité et robustesse par rapport au wifi.
- Aptitude est assez génial pour résoudre les dépendances, toutefois si
  le problème est trop complexe, je lis attentivement les retours et
  n'hésite pas a désinstaller provisoirement quelques logiciels ou à
  laisser des dépendances insatisfaites pour résoudre le problème en
  plusieurs fois.
- J'évite de sauter une version, mais si ta config est basique tu sauve
  ce qu'il y a à sauver et tu réinstalle avec la dernière version, tu
  mettra beaucoup moins de temps que pour mettre à jour plusieurs
  fois (j'ai toujours le /home sur une partition séparée, quand on ne
  mélange pas les torchons et les serviettes tout est beaucoup plus
  simple pour la maintenance).

-- 
Jérôme



Re: XFCE and Awesome WM

2023-08-29 Thread Махно
I once used this configuration. As I was using it, I realized that it
was of no use. Here and there, ugly bugs (I don't remember which ones
anymore) came out. While using it, I realized one simple truth - it is
better to use with what XFCE is designed to be used with.

2023-08-27, sk, 21:05 Tatoka  rašė:
>
> Hello again, dear debian user comunity! I just wanna ask you, will any 
> problems be if i use XFCE and Awesome wm on my Debian Linux? 2 actions can be:
>
> I use Awesome WM as defautl WM of XFCE insted of xfwm4.
> I use Awesome WM and XFCE in differents sessions.
> Can I get errors or problems with these 2 actions.
>
> P.S. I very like your XFCE and Awesome WM and I just wanna use them both but 
> possible problems stop me.



Re: door bell like sound effect

2023-08-29 Thread Greg Wooledge
On Tue, Aug 29, 2023 at 07:46:16AM -0400, songbird wrote:
>   ok, i understand that but my command 
> 
> $ alias aq='find . -amin -30'
> $ aq 
> 
> works as it should.

Oh.  I guess I should have read the *entire* section of the man page.

   relatime
   [...]
   Since Linux 2.6.30, the kernel defaults to the behavior provided by
   this option (unless noatime was specified), and the strictatime
   option is required to obtain traditional semantics. In addition,
   since Linux 2.6.30, the file’s last access time is always updated
   if it is more than 1 day old.

It's that last sentence that changes everything.  So then, I guess in
theory Gene *could* search for all of the most recently used files on
his system, and have a snowball's chance in hell of finding the doorbell
audio file that way.

Actually doing that could be trickier than you might guess.  If we
limit ourselves to searching one file system (or partial file system,
e.g. the /usr directory) at a time, and therefore don't need to supply
exclude patterns, here's a bash function that might be helpful:

rlartu() {
local day time path
find "${1:-.}" -type f -printf '%A@/%AY-%Am-%Ad/%AT/%p\0' | sort -zn |
while IFS=/ read -rd '' _ day time path; do
printf '%s %s %s\n' "$day" "${time%.*}" "$path"
done
}

I would suggest using this in /home and /usr first, unless Gene can
think of more appropriate starting points.

There's still going to be a whole lotta searching through the haystack
to find the needle.  Obviously, knowing the approximate date and time
the file was last read would be of tremendous help, as you can zoom in
on that part of the results.



Re: Not authorized to run synaptic

2023-08-29 Thread Christian Britz



Am 28.08.23 um 19:24 schrieb Joe:
> It's not obvious. I run synaptic from a standard menu launcher, where
> the command is just synaptic-pkexec. It then requests the root password
> before running. I'm on sid, which still ought to be very close to
> testing at the moment.

For me it asks for the user's password (user has sudo priviledges).
So it seems synaptic-pkexec can deal with both cases. No idea what is
going wrong in the original poster's case.


-- 
https://www.cb-fraggle.de



Mise à jours et Update Stretch - Problème de dépôt

2023-08-29 Thread Hugues MORIN-TRENEULE
Salut à tous

J'ai fait une boulette, je n'ai pas upgradé .
A force de me procrastiner l'upgrade d'une machine sous Stretch dont je me
sers occasionnellement, je me trouve un peu embêter aujourd'hui.

En voulant faire un petit check des mises à jour, je me suis aperçu que les
dépôts Stretch enregistrés dans mon source.list n'existe plus:
# deb cdrom:[Debian GNU/Linux 9.2.1 _Stretch_ - Official amd64 NETINST
20171013-13:07]/ stretch main

#deb cdrom:[Debian GNU/Linux 9.2.1 _Stretch_ - Official amd64 NETINST
20171013-13:07]/ stretch main

deb http://ftp.fr.debian.org/debian/ stretch main contrib non-free
deb-src http://ftp.fr.debian.org/debian/ stretch main contrib non-free

deb http://security.debian.org/debian-security stretch/updates main contrib
non-free
deb-src http://security.debian.org/debian-security stretch/updates main
contrib non-free

# stretch-updates, previously known as 'volatile'
deb http://ftp.fr.debian.org/debian/ stretch-updates main contrib non-free
deb-src http://ftp.fr.debian.org/debian/ stretch-updates main contrib
non-free

J'aimerai upgrader cette machine (tout d'abord vers buster) mais avant cela
il faudrait que je mette à jours les paquets de stretch pour ne pas avoir
de soucis avec les upgrade a venir.

Pour le dépot principal (http://ftp.fr.debian.org/debian/ stretch) , en
cherchant, j'ai trouvé le depot archive Debian:
http://archive.debian.org/debian
Est ce que vous pourriez me confirmer qu'il me permettra de mettre les
paquets de stretch à jours jusqu'à leur dernière version.

Concernant les dépôts "security" et "volatile", existe-t-il aussi des
dépôts archive que je pourrai utiliser?

Je ne maitrise pas bien tout ce qui est en lien avec les dépôts et les mise
à jours donc je suis ouvert à vos suggestions et conseils.

Bonne journée
Cordialement
Hugues


Re: door bell like sound effect

2023-08-29 Thread Michel Verdier
On 2023-08-29, Greg Wooledge wrote:

> It's changed *only* under the specific circumstance where the file has
> been modified since it was last read.  If the file hasn't been written to
> (or metadata changed), atime isn't updated.

Michael is right : atime is modified if it's "ealier" so you always get
the latest access time as modify and create obviously need access.
Here I set noatime to disable access time and also lazytime to speed
writes.



Re: door bell like sound effect

2023-08-29 Thread songbird
Greg Wooledge wrote:
> On Mon, Aug 28, 2023 at 11:32:25PM -0400, songbird wrote:
>> Greg Wooledge wrote:
>> > The problem is, most Debian systems are set up to mount the core file
>> > systems with "relatime".  This means you don't have a record of the
>> > last time each file was accessed, so you can't ask the computer which
>> > files were most recently opened.
>> 
>>   i don't have that one set at all in my fstab.
>
> It's a default option.  It doesn't have to be visible in fstab.
> Look at the *output of mount* instead.
>
> unicorn:~$ cat /etc/fstab
> [...]
> # / was on /dev/sda7 during installation
> UUID=c4691ccb-2090-491e-8e82-d7cc822db04a /   ext4
> errors=remount-ro 0   1
> [...]
>
> unicorn:~$ mount | grep 'on / '
> /dev/sda7 on / type ext4 (rw,relatime,errors=remount-ro)

  ok, i understand that but my command 

$ alias aq='find . -amin -30'
$ aq 

works as it should.


  songbird



Re: door bell like sound effect

2023-08-29 Thread Greg Wooledge
On Tue, Aug 29, 2023 at 11:10:17AM +0200, Michael wrote:
> On Tuesday, 29 August 2023 03:56:55 CEST, Greg Wooledge wrote:
> 
> > The problem is, most Debian systems are set up to mount the core file
> > systems with "relatime".  This means you don't have a record of the
> > last time each file was accessed, so you can't ask the computer which
> > files were most recently opened.
> 
> hm...
> 
> i was curious about that and read the man page for 'mount(8)', in section
> FILESYSTEM-INDEPENDENT MOUNT OPTIONS i found the following:
> 
> relatime
>  Update inode access times relative to modify or change time.
>  Access time is only updated if the previous access time was
>  earlier than the current modify or change time. [...]
> 
> so my understanding is, that access time is indeed updated if 'relatime' is
> used as a mount option. to prevent updating access times 'noatime' should be
> used.

It's changed *only* under the specific circumstance where the file has
been modified since it was last read.  If the file hasn't been written to
(or metadata changed), atime isn't updated.

So, imagine there's a doorbell.au file somewhere in Gene's file system,
and that this file has been played, once in a while, for several years.
It hasn't been *modified* in all that time.  It's a very static file.
But every once in a while, something opens it and reads it.

In that situation, the mtime on the file is going to be "whenever it
was created" (close enough for this discussion), and the atime is going
to be "whenever it was first played", perhaps 5 or 10 or 20 years ago.
Even though it was just played a few days ago.

Long story short, sorting files by atime isn't going to reveal it.
Unless of course Gene's file systems are mounted with an overriding
option, and he's getting full historic atime behavior.



Re: door bell like sound effect

2023-08-29 Thread Michael

On Tuesday, 29 August 2023 03:56:55 CEST, Greg Wooledge wrote:


The problem is, most Debian systems are set up to mount the core file
systems with "relatime".  This means you don't have a record of the
last time each file was accessed, so you can't ask the computer which
files were most recently opened.


hm...

i was curious about that and read the man page for 'mount(8)', in section 
FILESYSTEM-INDEPENDENT MOUNT OPTIONS i found the following:


relatime
 Update inode access times relative to modify or change time.
 Access time is only updated if the previous access time was
 earlier than the current modify or change time. [...]

so my understanding is, that access time is indeed updated if 'relatime' is 
used as a mount option. to prevent updating access times 'noatime' should 
be used.


i am happy to be corrected if i should be wrong...



Re: Fallos en mi Debian

2023-08-29 Thread Camaleón
El 2023-08-28 a las 20:51 +0100, José Manuel (Abogado) escribió:

> Me aparecen dos fallos que no se porque sucede, por lo que me dirijo a
> ustedes por si me pueden orientar, cosa que les agradezco de antemano.
> 
> Tengo Debian Bookworm
> 
> Primer fallo, en el arranque me aparece la palabra fallo en rojo pero al ser
> rápido no me da tiempo a saber que lo que pone

Añado a lo ya indicado por Fran.

La orden «systemctl list-units --failed» te permite enumerar los 
servicios fallidos.

Y con «journalctl -b | grep -i -e fallo -e failed» también podrás ver los 
registros 
del arranque actual con la palabra «fallo» o «failed».
 
> Segundo fallo por consola, al actualizar algún paquete al terminar a través
> de sudo me aparece lo siguiente en las últimas líneas:
> 
> ...
> 
> libdvd-pkg: Checking orig.tar integrity...
> /usr/src/libdvd-pkg/libdvdcss_1.4.3.orig.tar.bz2: La suma coincide
> libdvd-pkg: `apt-get check` failed, you may have broken packages.
> Aborting...

No sé si has probado a reconfigurar el paquete con la orden «dpkg-reconfigure 
libdvd-pkg».

Saludos,

-- 
Camaleón