AV-Linux Enlightenment Pipewire Metadata Settings  [Solved]

Help on all MX Re-spins
Message
Author
pffftdwarf
Posts: 16
Joined: Fri Nov 11, 2022 3:48 am

AV-Linux Enlightenment Pipewire Metadata Settings

#1 Post by pffftdwarf »

Hi,
I have a question about the "PW-Tools Metadata Settings" Tool. When I change settings there, they are not permanent. After a reboot they are reverted to "0" and I have to set them again.
Is that the default behavior or should they normally stay "where I left them"?
I have to mention that I switched back to XFCE as Desktop, is that maybe an issue here?

User avatar
siamhie
Global Moderator
Posts: 3698
Joined: Fri Aug 20, 2021 5:45 pm

Re: AV-Linux Enlightenment Pipewire Metadata Settings

#2 Post by siamhie »

Do you have a dual desktop setup booting to systemd by any chance?


Also, always include your QSI (Quick System Info) when asking for help. It helps to narrow down things.
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.

pffftdwarf
Posts: 16
Joined: Fri Nov 11, 2022 3:48 am

Re: AV-Linux Enlightenment Pipewire Metadata Settings

#3 Post by pffftdwarf »

Here's the QSI:

Code: Select all

System:
  Kernel: 6.7.8-1-liquorix-amd64 [6.7-12~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.7.8-1-liquorix-amd64
    root=UUID=<filter> ro threadirqs quiet
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel, plank wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: AVL_MXE-23.1-20240115_x64 Enlightened January 15  2024 base: Debian
    GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: HP product: HP Z2 Tower G4 Workstation v: SBKPF
    serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: HP model: 8455 v: KBC Version 07.D2.00 serial: <superuser required> UEFI: HP
    v: Q50 Ver. 01.08.08 date: 10/12/2023
CPU:
  Info: model: Intel Core i7-8700 bits: 64 type: MT MCP arch: Coffee Lake gen: core 8 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xA (10)
    microcode: 0xF4
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 3279 high: 4141 min/max: 800/3201 boost: enabled scaling:
    driver: acpi-cpufreq governor: performance cores: 1: 3200 2: 3200 3: 3201 4: 3201 5: 3201 6: 3201
    7: 3201 8: 3201 9: 3201 10: 4141 11: 3201 12: 3201 bogomips: 76799
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA GP106GL [Quadro P2000] driver: nouveau v: kernel non-free: 530.xx+
    status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm built: 2016-21 pcie:
    gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: DP-1,DP-2
    empty: DP-3,DP-4 bus-ID: 01:00.0 chip-ID: 10de:1c30 class-ID: 0300 temp: 33.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 4480x1440 s-dpi: 96 s-size: 1185x381mm (46.65x15.00")
    s-diag: 1245mm (49.01")
  Monitor-1: DP-1 pos: primary,left model: Fujitsu Siemens B27-9 TE QHD serial: <filter>
    built: 2022 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23")
    diag: 685mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400
  Monitor-2: DP-2 pos: right model: Asus VX279 serial: <filter> built: 2014 res: 1920x1080 hz: 60
    dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 4.3 Mesa 23.1.2-1~mx23ahs renderer: NV136 direct-render: Yes
Audio:
  Device-1: NVIDIA GP106 High Definition Audio driver: N/A alternate: snd_hda_intel pcie:
    bus-ID: 1-12:6 chip-ID: 1397:0508 gen: 1 class-ID: fe01 speed: 2.5 GT/s lanes: 16 link-max:
    gen: 3 speed: 8 GT/s bus-ID: 01:00.1 chip-ID: 10de:10f1 class-ID: 0403
  Device-2: BEHRINGER GmbH UMC204HD 192k type: USB driver: snd-usb-audio
  API: ALSA v: k6.7.8-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-LM vendor: Hewlett-Packard driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15bb class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
    bus-ID: 1-13:7 chip-ID: 0a12:0001 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
    hardware: no software: yes address: <filter>
  Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
    link-mode: peripheral accept
RAID:
  Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: 4020 bus-ID: 00:17.0
    chip-ID: 8086:2822 rev: N/A class-ID: 0104
Drives:
  Local Storage: total: 5.94 TiB used: 182.79 GiB (3.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 033
    scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD40EZRZ-00WN9B0 size: 3.64 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 0A80 scheme: GPT
  ID-4: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 870 EVO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q
    scheme: GPT
  ID-5: /dev/sdi maj-min: 8:128 type: USB vendor: SanDisk model: Ultra Fit size: 28.64 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 88.48 GiB size: 86.03 GiB (97.24%) used: 19.98 GiB (23.2%) fs: ext4
    dev: /dev/sdd2 maj-min: 8:50
  ID-2: /home raw-size: 204.49 GiB size: 200.23 GiB (97.91%) used: 15.81 GiB (7.9%) fs: ext4
    dev: /dev/sdd4 maj-min: 8:52
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 10.74 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb4
    maj-min: 8:20
Sensors:
  System Temperatures: cpu: 33.0 C pch: 33.0 C mobo: N/A gpu: nouveau temp: 33.0 C
  Fan Speeds (RPM): N/A gpu: nouveau fan: 2084
Repos:
  Packages: pm: dpkg pkgs: 2562 libs: 1450 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mirror.23m.com/mx-packages/mx/repo/ bookworm main non-free
    2: deb https://mirror.23m.com/mx-packages/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/nala-sources.list
    1: deb http://ftp.es.debian.org/debian/ bookworm main
    2: deb http://ftp.nl.debian.org/debian/ bookworm main
Info:
  Processes: 501 Uptime: 44m wakeups: 0 Memory: 31.23 GiB used: 1.64 GiB (5.2%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
I think you can name it a dual desktop, since i did not delete Enlightenment, or did I get you wrong here?
And yes, its booting into systemd.

User avatar
AVLinux
Posts: 3125
Joined: Wed Jul 15, 2020 1:15 am

Re: AV-Linux Enlightenment Pipewire Metadata Settings  [Solved]

#4 Post by AVLinux »

Hi,

The metadata tool is in a very early iteration at this point and currently isn't persistent and has no conf file. I thought most often Users would probably want the PipeWire defaults for regular computer use and would see the tool as a dynamic 'as-needed' way when changes were required.

*Note that the "System Editor" in the Accessories menu gives access the the main PipeWire configs if you want to make permanent global changes there:
shot-2024-03-09_14-54-04.jpg
You do not have the required permissions to view the files attached to this post.

pffftdwarf
Posts: 16
Joined: Fri Nov 11, 2022 3:48 am

Re: AV-Linux Enlightenment Pipewire Metadata Settings

#5 Post by pffftdwarf »

Ah, good to know! Thanks for the Info!

Post Reply

Return to “MX Respins”