All perguntas(unix)

Aqui está um exemplo de level0conteúdo de diretório em um formato tipo árvore. No entanto, suponha que ele seja enorme e contenha muitos arquivos, pois estou omitindo muitos deles aqui:

$ tree level0
level0
└── level1
    └── level2
        └── sample.txt

Tentei grepverificar alguns arquivos com grep, mas esta é a saída que recebi:

$ tree /tmp/level0  | grep sample
        └── sample.txt

Entretanto, espero que a saída seja o caminho absoluto real /tmp/level0/level1/level2/sample.txt.

Como posso obter o caminho absoluto do arquivo dentro de um diretório usando um comando?

Referência: Símbolo fraco

No link é mencionada a seguinte opção de vinculador:

cc  main.o -L`pwd` -Wl,-R`pwd` -lpowerslow -o main2

O propósito de todas as sinalizações acima foi documentado no Manual do GCC, exceto -R.

O que esse sinalizador instrui o vinculador?

AIT

Vinod

Minha configuração: Pré-requisitos:

• Dual Boot Windows 10/anteriormente Ubuntu 24.04 (vindo de 22.04)
• Tabela de partição:

  /dev/nvme0n1p7                   202G   96M  202G   1% 
  /ntfs_data
  /dev/nvme0n1p3                   230G   54G  177G  24% 
  /windows
  /dev/nvme0n1p5                   3,0G  288M  2,6G  11% /boot
  /dev/mapper/ubuntu--vg-home      2,8T  1,7T  964G  64% /home
  /dev/nvme0n1p1                   256M  158M   99M  62% 
  /boot/efi
  tmpfs                            1,6G  300K  1,6G   1% /run/user/1000
  /home/xxx/.Private               2,8T  1,7T  964G  64% /home/xxx
  /dev/mapper/usb1TB_202304_crypt  938G  890G  559M 100% 
  /backup1TB
  /backup1TB/home_xxx_bck          938G  890G  559M 100% 
  /backup1TB/home_xxx_bck
  

  
• /dev/nvme0n1p6 é o dispositivo criptografado luks com LVM configurado:
  • raiz (243 GB)
  • casa (2,8 TB)
  • trocar (16 GB)

Etapas de instalação para produzir erro no initramfs:

Usei o instalador USB do Linux Mint 22 (Imagem baixada em janeiro de 2025). Consegui instalar o LVM2 e o pacote cryptsetup para obter assistência para LVM e LUKS. Configurei em 2022 no Ubuntu 22.04 o LVM como o seguinte:

# vgs
  WARNING: Couldn't find device with uuid CQVk01-WJQL-pjIi-opcT-oESN-UOb1-judhlH.
  WARNING: Couldn't find device with uuid I5OUXJ-OkxW-403c-rEVJ-BmyG-Rd4M-r7SSFs.
  WARNING: VG ubuntu-vg is missing PV CQVk01-WJQL-pjIi-opcT-oESN-UOb1-judhlH (last written to /dev/mapper/ubuntu-vg1).
  WARNING: VG ubuntu-vg is missing PV I5OUXJ-OkxW-403c-rEVJ-BmyG-Rd4M-r7SSFs (last written to /dev/mapper/ubuntu-vg2).
  VG        #PV #LV #SN Attr   VSize  VFree   
  ubuntu-vg   3   4   0 wz-pn- <6,01t <180,97g

# pvs
  WARNING: Couldn't find device with uuid CQVk01-WJQL-pjIi-opcT-oESN-UOb1-judhlH.
  WARNING: Couldn't find device with uuid I5OUXJ-OkxW-403c-rEVJ-BmyG-Rd4M-r7SSFs.
  WARNING: VG ubuntu-vg is missing PV CQVk01-WJQL-pjIi-opcT-oESN-UOb1-judhlH (last written to /dev/mapper/ubuntu-vg1).
  WARNING: VG ubuntu-vg is missing PV I5OUXJ-OkxW-403c-rEVJ-BmyG-Rd4M-r7SSFs (last written to /dev/mapper/ubuntu-vg2).
  PV                      VG        Fmt  Attr PSize  PFree   
  /dev/mapper/ubuntu-luks ubuntu-vg lvm2 a--   3,21t <180,97g
  [unknown]               ubuntu-vg lvm2 a-m  <1,40t       0 
  [unknown]               ubuntu-vg lvm2 a-m  <1,40t       0 

# lvs
  LV         VG        Attr       LSize    Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  backupHome ubuntu-vg -wi-----p-    2,79t                                                    
  home       ubuntu-vg -wi-ao----    2,78t                                                    
  root       ubuntu-vg -wi-ao---- <247,33g                                                    
  swap_1     ubuntu-vg -wi-ao----   16,00g  

Abri um bash, abri o LUKS e ativei o LVM (o LVM foi criado anteriormente na versão 22.04 em 2022):

# cryptsetup luksOpen /dev/nvmeon1p6 ubuntu-luks
# lvchange -ay ubuntu-vg

Então iniciei o aplicativo de instalação e escolhi o modo manual para atribuir as partições, que configurei conforme mostrado acima, com formatação de root e /dev/nvme0n1p5 como partição /boot (não criptografada).

Depois disso, inicializei essas novas instalações instaladas do Linux Mint 22. Mas, além disso, curiosamente, na primeira vez, o diálogo de senha gráfica na sequência de inicialização no início só apareceu uma vez e descriptografou os luks, mas não conseguiu atribuir a partição LVM corretamente. Depois disso, nem mesmo o volume criptografado LUKS foi encontrado ou detectado e em todos os casos acabei depois de um longo tempo de espera no initramfs em caixa ocupado.

Aqui eu sempre tive que repetir as duas instruções acima antes de poder sair do initramfs e continuar inicializando meu sistema.

Descobri que não havia crypttab em /etc/crypttab e instalei um como

# cat /etc/crypttab 
# <target name>         <source device>                           <key file>      <options>
# mounted /, /home, swap_1
ubuntu-luks             UUID=b910aded-9314-403f-a350-7892ba95ffd5 none            luks
# mounted as /backupHome LV part1, partial Loading (mustn't be present during boot)
ubuntu-luks_backupHome1 UUID=b1d9ec9c-7dac-445f-998b-695b2ddf6daa none            luks
#ubuntu-luks_backupHome1 UUID=b1d9ec9c-7dac-445f-998b-695b2ddf6daa none            luks,noauto
# mounted as /backupHome LV part2, partial loading (mustn't be present during boot)
ubuntu-luks_backupHome2 UUID=9c5b65e8-5785-44be-85c7-3009cbc1e02a none            luks
#ubuntu-luks_backupHome2 UUID=9c5b65e8-5785-44be-85c7-3009cbc1e02a none            luks,noauto
usb1TB_202304_luks      UUID=4c4b603f-9146-4cb0-9621-9aa098ec592c none            luks

# ubuntu-luks             UUID=b910aded-9314-403f-a350-7892ba95ffd5 none            luks  # mounted on /
# ubuntu-luks_backupHome1 UUID=b1d9ec9c-7dac-445f-998b-695b2ddf6daa none            luks,noauto  # mounted as /backupHome, part1
# ubuntu-luks_backupHome2 UUID=9c5b65e8-5785-44be-85c7-3009cbc1e02a none            luks,noauto  # mounted as /backupHome, part2

e /etc/fstab:

# cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system>                           <mount point>   <type>  <options>                 <dump>  <pass>
/dev/mapper/ubuntu--vg-root               /               ext4    errors=remount-ro         0       1
# /boot was on /dev/nvme0n1p5 during installation
UUID=712868f5-29cc-429a-b535-375a3d868fa3 /boot           ext4    defaults                  0       2
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=E079-2792                            /boot/efi       vfat    umask=0077                0       1
/dev/mapper/ubuntu--vg-home               /home           ext4    defaults                  0       2
# /ntfs_data was on /dev/nvme0n1p7 during installation
UUID=3B269E2A1843CA0B                     /ntfs_data      ntfs    defaults,umask=007,gid=46 0       0
# /windows was on /dev/nvme0n1p3 during installation
UUID=4C30FF1730FF06AC                     /windows        ntfs    defaults,umask=007,gid=46 0       0
/dev/mapper/ubuntu--vg-swap_1             none            swap    sw                        0       0
/dev/mapper/ubuntu--vg-backupHome         /backupHome     ext4    defaults,nofail           0       2

então atualizei o initramfs com $ sudo update-initramfs -k all -c

Agora eu consertei permanentemente a criptografia do luks (então o diálogo aparece toda vez durante a inicialização, como descrito), mas a ativação do lvm $ lvchange -ay ubuntu-vg não é feita no initramfs!

Como eu poderia realizar esse último passo - ativar o grupo LV?

• Observação: a mídia lvm de backup, que é uma unidade USB, normalmente não está presente durante a inicialização!!!

  # mounted as /backupHome LV part1, partial Loading (mustn't be present during boot)
  ubuntu-luks_backupHome1  UUID=xxx none            luks
  #ubuntu-luks_backupHome1 UUID=xxx none            luks,noauto
  # mounted as /backupHome LV part2, partial loading (mustn't be present during boot) 
  ubuntu-luks_backupHome2  UUID=xxx none            luks
  #ubuntu-luks_backupHome2 UUID=xxx none            luks,noauto
  

[EDIT 101502013]: Hoje ele inicializou com erro algo como

/sbin/lvchange not found

no initramfs. Uma coisa que descobri que era diferente no initrams, era que lvmos comandos do como lvs, pvs, vgs, lvchange, lvcreateetc. funcionavam apenas com o comando principal lvmcomo prefixo. Também descobri que no /sbinin initramfstem apenas um link simbólico como um alias estranho lvm -> vgchange, parece que arg0 se torna arg1 após aplicar o link. É isso que tento em seguida, colocando esse link no initramfs.

[EDIT2] Coloquei meu script lvm start e activating primeiro em local-top, depois em init-bottom, por último em local-bottom, e atualizei o initramfs de acordo, update-initramfs -k all -c mas sem sucesso, o LUKS é descriptografado, mas o script não é executado ou é executado muito cedo, e cada vez que ele acaba finalmente no console initramfs com seu busybox. Quando eu executo manualmente o script e saio, ele continua inicializando todas as vezes. Mas isso é muito desconfortável e, na mesma medida, demorado por causa dos muitos atrasos de tempo, em vez de executar o script, ele produz repetidamente esta linha de saída:

mdadm: No array found in config file or automatically

Este é o local real do meu script:

# tree /etc/initramfs-tools/
/etc/initramfs-tools/
├── conf.d
│   └── cryptsetup
├── hooks
├── initramfs.conf
├── modules
├── scripts
│   ├── init-bottom
│   ├── init-premount
│   ├── init-top
│   ├── local-bottom
│   │   └── lvm
│   ├── local-premount
│   ├── local-top
│   ├── nfs-bottom
│   ├── nfs-premount
│   ├── nfs-top
│   └── panic
└── update-initramfs.conf

14 directories, 5 files

o script parece executável assim:

#!/bin/sh
# Check and activate LVM volumes regardless of input arguments

# Log the intention to activate LVM volumes
echo "Activating LVM volumes..." > /dev/console

# Activate the volume group
if /sbin/vgchange -ay ubuntu-vg; then
    echo "Logical volume group ubuntu-vg successfully activated." > /dev/console
    /sbin/lvm lvchange -ay ubuntu-vg --activationmode partial
else
    echo "Failed to activate logical volume group ubuntu-vg." > /dev/console
fi

No meio tempo, esvaziei uma imagem initrd para ver onde o comando cryptsetup é executado, mas parece um pouco complicado: unmkinitramfs -v initrd.img-6.8.0-53-generic /tmp/initrd e pesquisei por cryptsetup :

# find /tmp/initrd/ -type f -iname "*" -exec grep -Hn "cryptsetup " {} \;
grep: /tmp/initrd/main/usr/sbin/cryptsetup: binary file matches
grep: /tmp/initrd/main/usr/lib/x86_64-linux-gnu/libcryptsetup.so.12.10.0: binary file matches
grep: /tmp/initrd/main/usr/lib/x86_64-linux-gnu/libmount.so.1.1.0: binary file matches
/tmp/initrd/main/usr/lib/cryptsetup/functions:320:        if [ -e "$CRYPTTAB_OPTION_header" ] && /sbin/cryptsetup isLuks -- "$CRYPTTAB_OPTION_header"; then
/tmp/initrd/main/usr/lib/cryptsetup/functions:324:        if /sbin/cryptsetup isLuks -- "$s"; then
/tmp/initrd/main/usr/lib/cryptsetup/functions:366:    /sbin/cryptsetup -T1 \
/tmp/initrd/main/usr/lib/cryptsetup/functions:396:    /sbin/cryptsetup -T1 \
/tmp/initrd/main/usr/bin/cryptroot-unlock:89:# birth date) of the cryptsetup process with same $CRYPTTAB_NAME.
/tmp/initrd/main/usr/bin/cryptroot-unlock:118:  # find the cryptsetup process with same $CRYPTTAB_NAME
/tmp/initrd/main/usr/bin/cryptroot-unlock:173:      echo "cryptsetup: cryptsetup failed, bad password or options?" >&2
/tmp/initrd/main/scripts/local-top/cryptroot:127:    # our `cryptroot-unlock` script searches for cryptsetup processes
/tmp/initrd/main/scripts/local-top/cryptroot:164:            cryptsetup_message "ERROR: $CRYPTTAB_NAME: cryptsetup failed, bad password or options?"
/tmp/initrd/main/scripts/local-top/cryptroot:177:                /sbin/cryptsetup remove -- "$CRYPTTAB_NAME"

**Alguma ideia? O que eu fiz errado, ou poderia ter feito diferente? **

Criei um comando makefile para automatizar um fluxo de trabalho de publicação usando o Pandoc e o Generic Preprocessor (GPP) . É o seguinte:

TODAY = $(shell date +'%Y%m%d-%H%M')
MACROS = utils/gpp/macros.md
TEMPLATE = utils/template.docx

GPP = utils/gpp/gpp.exe
MACROS = utils/gpp/_macros.pp

METADATA = metadata.yaml
FM = content/frontmatter/*.md
MM = content/mainmatter/*.md
CONTENT = $(FM) $(MM)

default: docx

docx:
    for file in $(CONTENT); do \
        fifo=$$(mktemp -u); \
        FIFOS+=("$$fifo"); \
        cat $(MACROS) "$$file" | \
        $(GPP) -DWORD -x -o "$$fifo" & \
    done; \
    pandoc metadata.yaml "$${FIFOS[@]}" -f markdown -t docx \
    --citeproc --csl $(CSL) \
    --reference-doc=$(TEMPLATE) \
    --file-scope \
    -o dist/$(TODAY).docx

Ele roda bem no terminal Git no Windows. No entanto, no meu sistema Ubuntu 24.04, estou recebendo um /bin/sh: 1: Syntax error: "(" unexpectederro, e ele aponta para a linha for file in $(CONTENT); do \. Eu tentei o seguinte sem sucesso:

1. for file in ( $(CONTENT) ); do \

2. for file in "$(CONTENT)"; do \

Por que isso está acontecendo e como posso corrigir isso? (Sim, estou ciente de que o link GPP precisa ser atualizado para o Ubuntu, mas ele nem chega a essa linha)

O repositório é público caso alguém queira experimentá-lo localmente: https://github.com/khalid-hussain/editorial-project-template

Primeiro: som virtual através de RDP ( Remote Desktop Connection ) iE NoMachine funciona brilhantemente, apenas os alto-falantes internos e fones de ouvido não emitem som. Drivers de som ( firmware aberto de som são instalados pelo github source v2.2 (antes da maioria dos últimos v2.12) ). A placa de som é intels snd_hda_intel .

Segui alguns links encontrados na net sobre Linux Mint ou Ubuntu 22, que sempre são parecidos como:

• instalar ALSA
• Reinstalando o sistema de som e reiniciando o alsa
• (re)instalar fio de tubulação
• instalar e configurar hdajackretask (esta é a maneira menos promissora na minha humilde opinião)

incl. reiniciando alsa,

# dmesg | grep snd
[  659.315312] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[  659.315388] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[  659.678692] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[  659.678695] snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[  659.678697] snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[  659.678698] snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
[  659.678699] snd_hda_codec_realtek ehdaudio0D0:    inputs:
[  659.678699] snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19

Obtendo informações sobre o sistema ( últimas duas linhas de áudio ):

# inxi -SMA
System:
  Host: HP-ENVY-Laptop-13-aq1176ng Kernel: 6.8.0-52-generic arch: x86_64
    bits: 64
  Desktop: Cinnamon v: 6.4.6 Distro: Linux Mint 22.1 Xia
Machine:
  Type: Laptop System: HP product: HP ENVY Laptop 13-aq1xxx
    v: Type1ProductConfigId serial: 8CG0165VNF
  Mobo: HP model: 86AE v: 83.18 serial: PJEKT1DHCDM061 UEFI: Insyde v: F.22
    date: 11/24/2023
Audio:
  Device-1: Intel Comet Lake PCH-LP cAVS driver: sof-audio-pci-intel-cnl
  API: ALSA v: k6.8.0-52-generic status: kernel-api

O diário que revisou as descobertas de 'snd' durante a inicialização parece bom para mim:

$ journalctl -b -x | grep -i snd
Oct 17 19:15:17 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
Oct 17 19:15:17 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    inputs:
Feb 20 00:05:30 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:    inputs:
Feb 20 01:17:31 HP-ENVY-Laptop-13-aq1176ng kernel: snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19

Até agora, nenhum resultado. A única coisa que está funcionando é que se você conectar via NoMachine o som é transferido para o computador remoto.

Então eu considero que o som é produzido, mas em algum lugar entre as camadas de Abstração do SO até o HW há um problema. Eu imploro por suas ideias, ou soluções (árvores)!

[EDITAR]

aplay -l saída

# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Saída lspci :

# lspci
00:00.0 Host bridge: Intel Corporation Comet Lake-U v1 4c Host Bridge/DRAM Controller (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation CometLake-U GT2 [UHD Graphics] (rev 02)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem
00:14.0 USB controller: Intel Corporation Comet Lake PCH-LP USB 3.1 xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Comet Lake PCH-LP Shared SRAM
00:14.3 Network controller: Intel Corporation Comet Lake PCH-LP CNVi WiFi
00:14.5 SD Host controller: Intel Corporation Comet Lake PCH-LP SCS3
00:15.0 Serial bus controller: Intel Corporation Serial IO I2C Host Controller
00:15.1 Serial bus controller: Intel Corporation Comet Lake Serial IO I2C Host Controller
00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface
00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode]
00:1c.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #1 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #5 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #13 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Comet Lake PCH-LP LPC Premium Controller/eSPI Controller
00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH-LP cAVS
00:1f.4 SMBus: Intel Corporation Comet Lake PCH-LP SMBus Host Controller
00:1f.5 Serial bus controller: Intel Corporation Comet Lake SPI (flash) Controller
02:00.0 3D controller: NVIDIA Corporation GP108BM [GeForce MX250] (rev a1)
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal]

saída de dmesg|grep audio

# dmesg |grep audio
[   15.060429] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[   15.060582] sof-audio-pci-intel-cnl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[   15.060596] sof-audio-pci-intel-cnl 0000:00:1f.3: enabling device (0000 -> 0002)
[   15.060801] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[   15.060876] sof-audio-pci-intel-cnl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[   15.067813] sof-audio-pci-intel-cnl 0000:00:1f.3: use msi interrupt mode
[   15.108086] sof-audio-pci-intel-cnl 0000:00:1f.3: hda codecs found, mask 5
[   15.108092] sof-audio-pci-intel-cnl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
[   15.108097] sof-audio-pci-intel-cnl 0000:00:1f.3: DMICs detected in NHLT tables: 2
[   15.113689] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware paths/files for ipc type 0:
[   15.113694] sof-audio-pci-intel-cnl 0000:00:1f.3:  Firmware file:     intel/sof/sof-cml.ri
[   15.113697] sof-audio-pci-intel-cnl 0000:00:1f.3:  Topology file:     intel/sof-tplg/sof-hda-generic-2ch.tplg
[   15.116471] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[   15.116474] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[   15.116481] sof-audio-pci-intel-cnl 0000:00:1f.3: unknown sof_ext_man header type 3 size 0x30
[   15.216153] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[   15.216160] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[   15.236595] sof-audio-pci-intel-cnl 0000:00:1f.3: Topology: ABI 3:22:1 Kernel ABI 3:23:0
[   15.257684] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[   15.257692] snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   15.257695] snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[   15.257697] snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
[   15.257699] snd_hda_codec_realtek ehdaudio0D0:    inputs:
[   15.257701] snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19
[ 4302.743485] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[ 4302.743565] sof-audio-pci-intel-cnl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[ 4302.744012] sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[ 4302.744080] sof-audio-pci-intel-cnl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 4302.750643] sof-audio-pci-intel-cnl 0000:00:1f.3: use msi interrupt mode
[ 4302.764441] sof-audio-pci-intel-cnl 0000:00:1f.3: hda codecs found, mask 5
[ 4302.764450] sof-audio-pci-intel-cnl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
[ 4302.764457] sof-audio-pci-intel-cnl 0000:00:1f.3: DMICs detected in NHLT tables: 2
[ 4302.766353] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware paths/files for ipc type 0:
[ 4302.766357] sof-audio-pci-intel-cnl 0000:00:1f.3:  Firmware file:     intel/sof/sof-cml.ri
[ 4302.766358] sof-audio-pci-intel-cnl 0000:00:1f.3:  Topology file:     intel/sof-tplg/sof-hda-generic-2ch.tplg
[ 4302.768019] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[ 4302.768022] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[ 4302.768029] sof-audio-pci-intel-cnl 0000:00:1f.3: unknown sof_ext_man header type 3 size 0x30
[ 4302.880559] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware info: version 2:2:0-57864
[ 4302.880569] sof-audio-pci-intel-cnl 0000:00:1f.3: Firmware: ABI 3:22:1 Kernel ABI 3:23:0
[ 4302.881182] sof-audio-pci-intel-cnl 0000:00:1f.3: Topology: ABI 3:22:1 Kernel ABI 3:23:0
[ 4302.897218] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[ 4302.897226] snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 4302.897229] snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 4302.897232] snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
[ 4302.897233] snd_hda_codec_realtek ehdaudio0D0:    inputs:
[ 4302.897235] snd_hda_codec_realtek ehdaudio0D0:      Mic=0x19

[EDIT 3] Imagem do Alsamixer. O dispositivo está mudo se estiver verde ao redor do número na coluna, ou vice-versa? Mais Lista de placas de som, que na verdade é padrão e sof-hda-default. Mas alterar o volume ou silenciar no alsamixer não altera o som ausente dos alto-falantes e as alterações feitas não sobrevivem a uma inicialização:

Meu desktop usa o Kubuntu 24.04, totalmente atualizado, com o KDE Plasma 5.27.12. Cerca de uma semana atrás, decidi dar outra chance ao Wayland, e dessa vez achei que tudo funcionou perfeitamente, exceto pelo fato de que a opção Screen Energy Saving parece não funcionar...

Para ser preciso, ele funciona inicialmente, uma vez que o tempo ocioso tenha decorrido, e a tela fique preta. Mas ele permanece preto por cerca de 10 segundos apenas, então a tela volta a ligar novamente. Obviamente, há algo substituindo as configurações definidas (por mim) em Configurações do Sistema -> Energia.

A mesma coisa acontece se eu desligar a tela via CLI ( kscreen-doctor -d off), ou seja, a tela permanece preta por cerca de 10 segundos e depois acende novamente. Se eu escolher colocar o PC no modo de suspensão/hibernação após o mesmo período de tempo, a tela não acende novamente, mas é claro que não é isso que eu quero.

Após a tela acender novamente, em System Settings -> Display and Monitor, aparecem as seguintes informações: Uma nova saída foi adicionada. As configurações foram recarregadas. Eu obtenho, de fato, a seguinte saída interessante:

tail -f /var/log/syslog
......
2025-02-14T16:15:20.425314+01:00 kaus kactivitymanagerd[2625]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.425640+01:00 kaus kded5[2563]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.425915+01:00 kaus polkit-kde-authentication-agent-1[2641]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.426185+01:00 kaus foot[2779]: warn: wayland.c:1382: unknown global removed: 0x0000004f
2025-02-14T16:15:20.426443+01:00 kaus DiscoverNotifier[2802]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.426480+01:00 kaus foot: wayland: unknown global removed: 0x0000004f
2025-02-14T16:15:20.426679+01:00 kaus plasmashell[4761]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.426909+01:00 kaus xdg-desktop-portal-kde[3113]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.446383+01:00 kaus org_kde_powerdevil[5644]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.452066+01:00 kaus org_kde_powerdevil[2642]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.456716+01:00 kaus org_kde_powerdevil[5650]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.477425+01:00 kaus org_kde_powerdevil[5644]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:20.487835+01:00 kaus org_kde_powerdevil[5650]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:20.492526+01:00 kaus plasmashell[5655]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.524998+01:00 kaus plasmashell[5655]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:20.566383+01:00 kaus plasmashell[5663]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.571856+01:00 kaus kded5[2849]: xsettingsd: Reloading configuration
2025-02-14T16:15:20.572028+01:00 kaus kded5[2849]: xsettingsd: Loaded 12 settings from /home/mario/.config/xsettingsd/xsettingsd.conf
2025-02-14T16:15:20.573351+01:00 kaus plasmashell[2599]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:20.586841+01:00 kaus plasmashell[2599]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:20.600327+01:00 kaus plasmashell[5663]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:20.602521+01:00 kaus plasmashell[2599]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:20.606076+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:20: TypeError: Cannot read property 'pluginName' of null
2025-02-14T16:15:20.606343+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:75: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.606506+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:78: TypeError: Cannot read property 'pluginName' of null
2025-02-14T16:15:20.606659+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:80: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.606797+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:81: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.606941+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:82: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.607092+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:83: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.607265+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:84: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.607421+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:16: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.607579+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:17: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.607733+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:18: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:20.700216+01:00 kaus kded5[2849]: xsettingsd: Reloading configuration
2025-02-14T16:15:20.700254+01:00 kaus kded5[2849]: xsettingsd: Loaded 12 settings from /home/mario/.config/xsettingsd/xsettingsd.conf
2025-02-14T16:15:20.816145+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL vendor string:                   Intel
2025-02-14T16:15:20.816430+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL renderer string:                 Mesa Intel(R) UHD Graphics 630 (CFL GT2)
2025-02-14T16:15:20.816557+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL version string:                  4.6 (Core Profile) Mesa 24.2.8-1ubuntu1~24.04.1
2025-02-14T16:15:20.816656+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL shading language version string: 4.60
2025-02-14T16:15:20.816745+01:00 kaus kwin_wayland_wrapper[2502]: Driver:                                 Intel
2025-02-14T16:15:20.816825+01:00 kaus kwin_wayland_wrapper[2502]: GPU class:                              Coffee Lake
2025-02-14T16:15:20.816948+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL version:                         4.6
2025-02-14T16:15:20.817030+01:00 kaus kwin_wayland_wrapper[2502]: GLSL version:                           4.60
2025-02-14T16:15:20.817110+01:00 kaus kwin_wayland_wrapper[2502]: Mesa version:                           24.2.8
2025-02-14T16:15:20.817207+01:00 kaus kwin_wayland_wrapper[2502]: X server version:                       1.23.2
2025-02-14T16:15:20.817330+01:00 kaus kwin_wayland_wrapper[2502]: Linux kernel version:                   6.8
2025-02-14T16:15:20.817448+01:00 kaus kwin_wayland_wrapper[2502]: Requires strict binding:                no
2025-02-14T16:15:20.817546+01:00 kaus kwin_wayland_wrapper[2502]: GLSL shaders:                           yes
2025-02-14T16:15:20.817643+01:00 kaus kwin_wayland_wrapper[2502]: Texture NPOT support:                   yes
2025-02-14T16:15:20.817738+01:00 kaus kwin_wayland_wrapper[2502]: Virtual Machine:                        no
2025-02-14T16:15:21.020900+01:00 kaus kwin_wayland_wrapper[2502]: BlurConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.023996+01:00 kaus kwin_wayland_wrapper[2502]: ZoomConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.025121+01:00 kaus kwin_wayland_wrapper[2502]: WindowViewConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.026215+01:00 kaus kwin_wayland_wrapper[2502]: SlidingPopupsConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.026382+01:00 kaus kwin_wayland_wrapper[2502]: SlideConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.026613+01:00 kaus kwin_wayland_wrapper[2502]: OverviewConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.027160+01:00 kaus kwin_wayland_wrapper[2502]: KscreenConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.027885+01:00 kaus kwin_wayland_wrapper[2502]: DesktopGridConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.500242+01:00 kaus org_kde_powerdevil[5682]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:21.532164+01:00 kaus plasmashell[5686]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:21.543067+01:00 kaus plasmashell[2599]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:21.543131+01:00 kaus plasmashell[2599]: Checking screens: available: (QScreen(0x5fedb26e8010, name="DP-3")) redundant: QHash() fake: QSet(QScreen(0x5fedb2832170, name="")) all: (QScreen(0x5fedb2832170, name=""), QScreen(0x5fedb26e8010, name="DP-3"))
2025-02-14T16:15:21.607762+01:00 kaus kded5[2849]: xsettingsd: Reloading configuration
2025-02-14T16:15:21.607819+01:00 kaus kded5[2849]: xsettingsd: Loaded 12 settings from /home/mario/.config/xsettingsd/xsettingsd.conf
2025-02-14T16:15:21.724534+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL vendor string:                   Intel
2025-02-14T16:15:21.724669+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL renderer string:                 Mesa Intel(R) UHD Graphics 630 (CFL GT2)
2025-02-14T16:15:21.724707+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL version string:                  4.6 (Core Profile) Mesa 24.2.8-1ubuntu1~24.04.1
2025-02-14T16:15:21.724742+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL shading language version string: 4.60
2025-02-14T16:15:21.724769+01:00 kaus kwin_wayland_wrapper[2502]: Driver:                                 Intel
2025-02-14T16:15:21.724802+01:00 kaus kwin_wayland_wrapper[2502]: GPU class:                              Coffee Lake
2025-02-14T16:15:21.724829+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL version:                         4.6
2025-02-14T16:15:21.724918+01:00 kaus kwin_wayland_wrapper[2502]: GLSL version:                           4.60
2025-02-14T16:15:21.724948+01:00 kaus kwin_wayland_wrapper[2502]: Mesa version:                           24.2.8
2025-02-14T16:15:21.724981+01:00 kaus kwin_wayland_wrapper[2502]: X server version:                       1.23.2
2025-02-14T16:15:21.725010+01:00 kaus kwin_wayland_wrapper[2502]: Linux kernel version:                   6.8
2025-02-14T16:15:21.725039+01:00 kaus kwin_wayland_wrapper[2502]: Requires strict binding:                no
2025-02-14T16:15:21.725071+01:00 kaus kwin_wayland_wrapper[2502]: GLSL shaders:                           yes
2025-02-14T16:15:21.725102+01:00 kaus kwin_wayland_wrapper[2502]: Texture NPOT support:                   yes
2025-02-14T16:15:21.725170+01:00 kaus kwin_wayland_wrapper[2502]: Virtual Machine:                        no
2025-02-14T16:15:21.732241+01:00 kaus kwin_wayland_wrapper[2502]: BlurConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.733999+01:00 kaus kwin_wayland_wrapper[2502]: ZoomConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.735218+01:00 kaus kwin_wayland_wrapper[2502]: WindowViewConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.736053+01:00 kaus kwin_wayland_wrapper[2502]: SlidingPopupsConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.736185+01:00 kaus kwin_wayland_wrapper[2502]: SlideConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.736374+01:00 kaus kwin_wayland_wrapper[2502]: OverviewConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.736800+01:00 kaus kwin_wayland_wrapper[2502]: KscreenConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.737320+01:00 kaus kwin_wayland_wrapper[2502]: DesktopGridConfig::instance called after the first use - ignoring
2025-02-14T16:15:21.807503+01:00 kaus plasmashell[2599]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:21.823266+01:00 kaus plasmashell[2599]: message repeated 3 times: [ qt.qpa.wayland: Wayland does not support QWindow::requestActivate()]
2025-02-14T16:15:22.372133+01:00 kaus DiscoverNotifier[2802]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.372448+01:00 kaus foot[2779]: warn: wayland.c:1382: unknown global removed: 0x00000051
2025-02-14T16:15:22.372711+01:00 kaus polkit-kde-authentication-agent-1[2641]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.372930+01:00 kaus kactivitymanagerd[2625]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.373094+01:00 kaus kded5[2563]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.373141+01:00 kaus foot: wayland: unknown global removed: 0x00000051
2025-02-14T16:15:22.373394+01:00 kaus xdg-desktop-portal-kde[3113]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.373731+01:00 kaus plasmashell[4761]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.397611+01:00 kaus org_kde_powerdevil[5726]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.398211+01:00 kaus org_kde_powerdevil[2642]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.404861+01:00 kaus org_kde_powerdevil[5732]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.419837+01:00 kaus org_kde_powerdevil[5726]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:22.427077+01:00 kaus org_kde_powerdevil[5732]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:22.451625+01:00 kaus plasmashell[5738]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.488961+01:00 kaus plasmashell[5738]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:22.521557+01:00 kaus kded5[2849]: xsettingsd: Reloading configuration
2025-02-14T16:15:22.524481+01:00 kaus kded5[2849]: xsettingsd: Loaded 12 settings from /home/mario/.config/xsettingsd/xsettingsd.conf
2025-02-14T16:15:22.547828+01:00 kaus plasmashell[2599]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.553843+01:00 kaus plasmashell[5745]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
2025-02-14T16:15:22.561598+01:00 kaus plasmashell[2599]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:22.576030+01:00 kaus plasmashell[2599]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:22.577459+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:20: TypeError: Cannot read property 'pluginName' of null
2025-02-14T16:15:22.577520+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:75: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577566+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:78: TypeError: Cannot read property 'pluginName' of null
2025-02-14T16:15:22.577591+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:80: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577613+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:81: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577639+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:82: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577663+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:83: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577686+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:84: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577738+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:16: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577761+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:17: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.577795+01:00 kaus plasmashell[2599]: file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:18: TypeError: Cannot read property 'configuration' of null
2025-02-14T16:15:22.582656+01:00 kaus plasmashell[5745]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:22.674442+01:00 kaus kded5[2849]: xsettingsd: Reloading configuration
2025-02-14T16:15:22.674478+01:00 kaus kded5[2849]: xsettingsd: Loaded 12 settings from /home/mario/.config/xsettingsd/xsettingsd.conf
2025-02-14T16:15:22.800943+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL vendor string:                   Intel
2025-02-14T16:15:22.801060+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL renderer string:                 Mesa Intel(R) UHD Graphics 630 (CFL GT2)
2025-02-14T16:15:22.801131+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL version string:                  4.6 (Core Profile) Mesa 24.2.8-1ubuntu1~24.04.1
2025-02-14T16:15:22.801256+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL shading language version string: 4.60
2025-02-14T16:15:22.801345+01:00 kaus kwin_wayland_wrapper[2502]: Driver:                                 Intel
2025-02-14T16:15:22.801561+01:00 kaus kwin_wayland_wrapper[2502]: GPU class:                              Coffee Lake
2025-02-14T16:15:22.801704+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL version:                         4.6
2025-02-14T16:15:22.801839+01:00 kaus kwin_wayland_wrapper[2502]: GLSL version:                           4.60
2025-02-14T16:15:22.801982+01:00 kaus kwin_wayland_wrapper[2502]: Mesa version:                           24.2.8
2025-02-14T16:15:22.802086+01:00 kaus kwin_wayland_wrapper[2502]: X server version:                       1.23.2
2025-02-14T16:15:22.802246+01:00 kaus kwin_wayland_wrapper[2502]: Linux kernel version:                   6.8
2025-02-14T16:15:22.802422+01:00 kaus kwin_wayland_wrapper[2502]: Requires strict binding:                no
2025-02-14T16:15:22.802565+01:00 kaus kwin_wayland_wrapper[2502]: GLSL shaders:                           yes
2025-02-14T16:15:22.802709+01:00 kaus kwin_wayland_wrapper[2502]: Texture NPOT support:                   yes
2025-02-14T16:15:22.802906+01:00 kaus kwin_wayland_wrapper[2502]: Virtual Machine:                        no
2025-02-14T16:15:22.970701+01:00 kaus kwin_wayland_wrapper[2502]: BlurConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.972646+01:00 kaus kwin_wayland_wrapper[2502]: ZoomConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.973338+01:00 kaus kwin_wayland_wrapper[2502]: WindowViewConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.974403+01:00 kaus kwin_wayland_wrapper[2502]: SlidingPopupsConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.974496+01:00 kaus kwin_wayland_wrapper[2502]: SlideConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.974650+01:00 kaus kwin_wayland_wrapper[2502]: OverviewConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.974989+01:00 kaus kwin_wayland_wrapper[2502]: KscreenConfig::instance called after the first use - ignoring
2025-02-14T16:15:22.975489+01:00 kaus kwin_wayland_wrapper[2502]: DesktopGridConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.144882+01:00 kaus org_kde_powerdevil[5763]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:23.187486+01:00 kaus plasmashell[5769]: Initializing  "/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
2025-02-14T16:15:23.202846+01:00 kaus plasmashell[2599]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
2025-02-14T16:15:23.202882+01:00 kaus plasmashell[2599]: Checking screens: available: (QScreen(0x5fedb2715a40, name="DP-3")) redundant: QHash() fake: QSet(QScreen(0x7058b000b3b0, name="")) all: (QScreen(0x7058b000b3b0, name=""), QScreen(0x5fedb2715a40, name="DP-3"))
2025-02-14T16:15:23.241293+01:00 kaus kded5[2849]: xsettingsd: Reloading configuration
2025-02-14T16:15:23.241339+01:00 kaus kded5[2849]: xsettingsd: Loaded 12 settings from /home/mario/.config/xsettingsd/xsettingsd.conf
2025-02-14T16:15:23.372171+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL vendor string:                   Intel
2025-02-14T16:15:23.372240+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL renderer string:                 Mesa Intel(R) UHD Graphics 630 (CFL GT2)
2025-02-14T16:15:23.372272+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL version string:                  4.6 (Core Profile) Mesa 24.2.8-1ubuntu1~24.04.1
2025-02-14T16:15:23.372302+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL shading language version string: 4.60
2025-02-14T16:15:23.372333+01:00 kaus kwin_wayland_wrapper[2502]: Driver:                                 Intel
2025-02-14T16:15:23.372393+01:00 kaus kwin_wayland_wrapper[2502]: GPU class:                              Coffee Lake
2025-02-14T16:15:23.372425+01:00 kaus kwin_wayland_wrapper[2502]: OpenGL version:                         4.6
2025-02-14T16:15:23.372460+01:00 kaus kwin_wayland_wrapper[2502]: GLSL version:                           4.60
2025-02-14T16:15:23.372498+01:00 kaus kwin_wayland_wrapper[2502]: Mesa version:                           24.2.8
2025-02-14T16:15:23.372537+01:00 kaus kwin_wayland_wrapper[2502]: X server version:                       1.23.2
2025-02-14T16:15:23.372572+01:00 kaus kwin_wayland_wrapper[2502]: Linux kernel version:                   6.8
2025-02-14T16:15:23.372624+01:00 kaus kwin_wayland_wrapper[2502]: Requires strict binding:                no
2025-02-14T16:15:23.372653+01:00 kaus kwin_wayland_wrapper[2502]: GLSL shaders:                           yes
2025-02-14T16:15:23.372686+01:00 kaus kwin_wayland_wrapper[2502]: Texture NPOT support:                   yes
2025-02-14T16:15:23.372717+01:00 kaus kwin_wayland_wrapper[2502]: Virtual Machine:                        no
2025-02-14T16:15:23.384230+01:00 kaus kwin_wayland_wrapper[2502]: BlurConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.386218+01:00 kaus kwin_wayland_wrapper[2502]: ZoomConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.386909+01:00 kaus kwin_wayland_wrapper[2502]: WindowViewConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.387691+01:00 kaus kwin_wayland_wrapper[2502]: SlidingPopupsConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.387765+01:00 kaus kwin_wayland_wrapper[2502]: SlideConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.387968+01:00 kaus kwin_wayland_wrapper[2502]: OverviewConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.388367+01:00 kaus kwin_wayland_wrapper[2502]: KscreenConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.388886+01:00 kaus kwin_wayland_wrapper[2502]: DesktopGridConfig::instance called after the first use - ignoring
2025-02-14T16:15:23.489964+01:00 kaus plasmashell[2599]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

do qual podemos ver que o kactivitymanager, por algum motivo não especificado, decide que deve criar uma tela Qt falsa para evitar que ele trave. E isso acontece várias vezes no curso de alguns segundos, até que a situação se estabilize, e não haja mais atividades relacionadas no syslog .

Outro detalhe importante é acrescentado por uma captura das conexões dbus :

date > cap.txt;  kscreen-doctor --dpms off; dbus-monitor --profile >> cap.txt

e o conteúdo do arquivo de captura, cap.txt , é:

Fri Feb 14 04:08:49 PM CET 2025
#type   timestamp       serial  sender  destination     path    interface       member
#                                       in_reply_to
sig     1739545729.278759       2       org.freedesktop.DBus    :1.68   /org/freedesktop/DBus   org.freedesktop.DBus    NameAcquired
sig     1739545729.278766       4       org.freedesktop.DBus    :1.68   /org/freedesktop/DBus   org.freedesktop.DBus    NameLost
mc      1739545730.964295       280     :1.41   :1.49   /org/freedesktop/portal/desktop org.freedesktop.impl.portal.Background  GetAppState
mr      1739545730.965055       239     :1.49   :1.41   280
mc      1739545730.966093       281     :1.41   :1.43   /org/freedesktop/impl/portal/PermissionStore    org.freedesktop.impl.portal.PermissionStore     Lookup
err     1739545730.966962       71      :1.43   :1.41   281
mc      1739545735.968323       282     :1.41   :1.49   /org/freedesktop/portal/desktop org.freedesktop.impl.portal.Background  GetAppState
mr      1739545735.969096       240     :1.49   :1.41   282
mc      1739545735.970145       283     :1.41   :1.43   /org/freedesktop/impl/portal/PermissionStore    org.freedesktop.impl.portal.PermissionStore     Lookup
err     1739545735.970998       72      :1.43   :1.41   283
sig     1739545740.179599       187     :1.26   <none>  /kwinrc org.kde.kconfig.notify  ConfigChanged
mc      1739545740.180923       389     :1.21   org.freedesktop.DBus    /org/freedesktop/DBus   org.freedesktop.DBus    AddMatch

O horário inicial da captura do dbus , 1739545729, corresponde a sexta-feira, 14 de fevereiro de 2025, 16h08min49s GMT+01:00, que também é a saída do comando date imediatamente antes do comando que desliga o monitor. Vemos que cerca de 11 segundos após o desligamento o kwin envia um sinal de que a configuração mudou, o que presumivelmente é a consequência do kded5 ter criado uma tela Qt falsa. Mas o que exatamente aciona esse comportamento engraçado?

O engraçado é que a mesma configuração funciona perfeitamente em uma sessão X11, ela só quebra em uma sessão Wayland. Mas, apesar disso, não está claro para mim se isso é um bug do Wayland ou do KDE. Eu pesquisei qt.qpa.wayland: Creating a fake screen in order for Qt not to crash , o que leva a duas escassas referências, a mais relevante das quais afirma:

O problema provavelmente está no Wayland ou no DE, pois eles não estão fechando o portal.

(qualquer que seja o portal). Mas aqui também não houve consenso sobre o verdadeiro culpado.

Alguém pode ajudar? Estou perdido, obrigado.

Temos três serviços com PrivateTmp=yes( tomcat, clamde soffice). clamde sofficedefinimos JoinsNamespaceOf=tomcat.service.

clamddeveria ser capaz de ler tudo que tomcatescreve nele /tmp, certo?

Existe uma chance (por exemplo, reinicialização de serviços) de que essa junção seja interrompida em tempo de execução (por exemplo, clamdperdendo a capacidade de leitura tomcat's /tmp)?

Como posso verificar em tempo de execução se essa junção existe (ainda está funcionando)?

Tentei usar lsnse lsns NSver alguma relação, mas não consegui reconhecer nada.

No manual do Bash, está escrito sobre a expansão til:

Cada atribuição de variável é verificada em busca de prefixos de til sem aspas imediatamente após um ':' ou o primeiro '='.

Leia o manual do Bash sobre expansão de til.

Presumi que o sinal : ao atribuir uma variável está relacionado à expansão de parâmetros e instruí um dos AIs populares a encontrar exemplos que satisfaçam as condições definidas no manual do Bash. O resumo de sua resposta é o seguinte:

• Não há um exemplo funcional válido com o til imediatamente após o :sem caracteres adicionais.

Meu pacote está instalado com umconfiguration.nix

{ config, pkgs, lib, ... }:
{
  environment.systemPackages = with pkgs; [
    my-package
  ];
}

Como posso consultar o caminho my-packageno armazenamento nix?

Estou procurando algo tão simples quanto which my_executable, mas para pacotes na loja nix.

Exemplo de uso

$ my_search my-package [--store /path/to/nix/store]
/path/to/nix/store/qpmg2piws75wmy1619ryh0dhwi9638ni-my_package-1.5.6

Notas:

• Ele tem que me dar o caminho para a geração e/ou derivação atualmente em uso
• Não deveria exigir uma conexão com a internet, nem deveria tentar construir nada. my_package pode exigir acordo com licenças específicas e precisa permitir pacotes não livres que podem atrapalhar a reconstrução. Exemplo: o pacotesegger-jlink-headless
• Se o pacote foi instalado pelo root (por exemplo no NixOS), posso ter um comando que não exija privilégios de root? Posso sempre fornecer o caminho, /nix/store/se necessário.
• which my_package_executablenão funciona se um pacote não contiver um executável no PATH.

Outras referências:

Como encontrar a versão correta de um pacote instalado em /nix/store

https://nixos.wiki/wiki/Cheatsheet

A resposta do Discourse parece desatualizada (não está funcionando para mim): https://discourse.nixos.org/t/how-to-get-a-package-path-in-nix-store-which-not-containing-a-bin-dir/4653/5 :

No meu caso, nix evalos erros aparecem quando fornecidos com o pacote que instalei (veja a etapa de instalação acima)

$ nix eval nixpkgs.my-package.outPath
error: getting status of '/home/<user>/nixpkgs.my-package.outPath': No such file or directory

Esta é a saída desudo apt install erlang

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 erlang-base : Depends: libc6 (>= 2.38) but 2.35-0ubuntu3.9 is to be installed
               Conflicts: erlang (< 1:27.2.2-1) but 1:24.2.1+dfsg-1ubuntu0.1 is to be installed
 erlang-crypto : Depends: libssl3t64 (>= 3.0.0) but it is not installable
 erlang-odbc : Depends: libc6 (>= 2.38) but 2.35-0ubuntu3.9 is to be installed
 erlang-os-mon : Depends: libc6 (>= 2.38) but 2.35-0ubuntu3.9 is to be installed
 erlang-runtime-tools : Depends: libc6 (>= 2.38) but 2.35-0ubuntu3.9 is to be installed
 erlang-wx : Depends: libstdc++6 (>= 13.1) but 12.3.0-1ubuntu1~22.04 is to be installed
             Depends: libwxbase3.2-1t64 (>= 3.2.4+dfsg) but it is not installable
             Depends: libwxgtk-gl3.2-1t64 (>= 3.2.4+dfsg) but it is not installable
             Depends: libwxgtk-webview3.2-1t64 (>= 3.2.4+dfsg) but it is not installable
             Depends: libwxgtk3.2-1t64 (>= 3.2.4+dfsg) but it is not installable
E: Unable to correct problems, you have held broken packages.

Pelo que entendi, libc6 está vinculado à sua versão do Ubuntu. Estou no PopOS e atualmente está no Jammy Jellyfish, que é o mais recente para PopOS, então libc6 está 2.35no meu sistema. Erlang depende de libc6 2.38e acima, mas não é aconselhável atualizar libc6 para uma versão superior, pois isso quebrará meu sistema. Quais são minhas opções para poder baixar Erlang e usar RabbitMQ? Além de esperar que o PopOS libere uma atualização para Noble Numbat.