[Stable Update] 2025-06-23 - Kernels, KDE, NVIDIA, Pamac, Wine, VirtualBox, PipeWire, Qt6

Here is something I don’t understand. This is on Manjaro KDE.
Output from journalctl -p 3
/usr/lib/environment.d/99-environment.conf:11: invalid variable name “export GDK_DPI_SCALE”, ignoring.
That file contains exactly the same as /etc/environment
export GDK_DPI_SCALE=1.25

From a fresh boot, Evolution has the exact same scale as when I do the following from terminal:
GDK_DPI_SCALE=1.25
GDK_BACKEND=wayland evolution
So the Scaling “takes”. Is effective.
Why is it complaining?

If I do:
GDK_DPI_SCALE=2
GDK_BACKEND=wayland evolution
That is effective too.

Another thing I have not found the error to yet is: My PC went to Sleep. Woke it up, input no longer worked, not keyboard or mouse. Had to cut the power. All AMD system. I don’t remember that happening before. My PC goes to sleep on the daily. When I sleep.
Could be an anomaly.

I have issues with bluetooth audio too, but not with the connection itself but rather that my plasma desktop doesn’t see the connected headset as an audio device in the audio settings, so I can’t use it anymore. It did still work a few days ago, so I suspect this update caused the regression…

UPDATE: a second reboot fixed that for me, or maybe it was the cold start (so really shutting the machine down in between that fixed it) - though I only shut down my laptop because the standby didn’t work :wink: - that works agian too now :partying_face:

This may be 5.83 regression: Audio device stays connected when logging out of session, stops working on login · Issue #1325 · bluez/bluez · GitHub

You need to remove the leading export. Valid syntax would be variable=value:

https://wiki.archlinux.org/title/Environment_variables#Using_shell_initialization_files

1 Like

Update: this happens only with laptop nvidia GPU’s, 6.15 works fine on PC with a similar setup.

EDIT: Nevermind, on PC it is much worse, both 6.12 and 6.15 hard lock when handing the GPU back to the host. This is completely broken, I will try to rollback some packages.

EDIT2: I tried installing the prime setup via mhwd, the computer hard locked the same way it did on VM shutdown. This left empty files everywhere where nvidia packages would have been installed. This broke d-bus which was trying to read an empty xml file and failing, as well as blocked re-installing the prime config in chroot via mhwd because the empty files in place made pacman error out. I had to manually install those nvidia packages, with the option to force overwrite files, as well as manually deleting the file d-bus was trying to parse. Afterwards, I re-installed the mhwd prime config with the -f flag to make it re-install just in case, and setup everything for the proprietary driver. Now all is working fine, but this was a solid 3 hours gone. And I am very afraid of removing the prime config without being in chroot.

I hadn’t taken any updates since Feb/Mar (2025) as there seemed to be little landmines along the way I opted to avoid… but there seemed to be good vibes with this update and installing it via TTY (sans DE) went off without a hitch.

I had some previous issues with the 6.12 kernel, but going to give the updated version a try before reverting back to 6.6.

The only questions I have are around some pacnews:

  • warning: /etc/hosts installed as /etc/hosts.pacnew
  • warning: /etc/passwd installed as /etc/passwd.pacnew
  • warning: /etc/shells installed as /etc/shells.pacnew

passwd seemed straight forward… keeping my original with groups
shells… i opted to keep my original as it seemed to be deleting the manjaro zsh options
hosts is what confuses me as it appears the pacnew removes a bunch of ip6 related entries… do I want to keep those, or purge them?

Standard host addresses

127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

Keep them.

1 Like

They haven’t removed anything–as they were never there to begin with. :wink:

The files were modified by other programs afterward. Normally do not do anything with those files unless you notice something new that was added that can be merged.

2 Likes

After experiencing the same backintime issue reported @ [Stable Update] 2025-04-12 - Kernels, Plasma, Systemd, Mesa, Grub, Wine - #114 by beermad (BiT/python coredump during restore)…

I looked for and found an official/upstream workaround until the fix release planned for BiT v1.6.0 @ Remove window-id use (was: I updated EndeavourOS on Sunday. After the update, attempting restore in BiT fails - the window closes). · Issue #2084 · bit-team/backintime · GitHub

Solution

Solution for you

Modify /usr/share/backintime/common/tools.py round about line 2045 in function inhibitSuspend().

cookie = proxy(*[(app_id, dbus.UInt32(toplevel_xid), reason, dbus.UInt32(flags))[i] for i in dbus_props['arguments']])
                          ^^^^^^^^^^^^^^^^^^^^^^^^^

Replace the second argument with a simple 0 like this:

cookie = proxy(*[(app_id, 0, reason, dbus.UInt32(flags))[i] for i in dbus_props['arguments']])
                          ^

Then your problem should be fixed. Let me know.

Urgency

Because I was not able to reproduce the problem and that no one else reported it in the past, I do assume it is a rare case. Therefore, I don’t see the need for a hotfix for the upcoming Debian 13, in one week.

I tested this on Debian 12 with Gnome and Debian 13 using Wayland. I was not able to run KDE Plasma on EndevourOS within the VM. But I can life with that.

Cause of the problem

BIT is using QWindow.winIDd() in some places. That is bad, because it is a pointer into the memory. It works in most cases, but as we can see not always.

There is also no need for this anymore.

Potential approaches for a solution

  • Based on my research and feedback from Gnome folks I can say that the window-identifier is not needed anymore today. We can use the value 0 without risk and without losing something.
  • The other point is the question if we even need to try 3 different dbus session managers (gnome, mate, freedesktop)? The freedesktop session manager does not need a window-id as method argument. We should stick it it. And to my understanding we need upower package as a dependency to be sure that this session manager exists.
  • The functions also need to be more robust and verbose, to catch potential errors and not crashing the whole application. Inhibiting hibernation is not essential to BIT. If it fails BIT can run further.

Update went fine. But from login screen to desktop loading has significant lag now. Once loaded, it’s all fine.

Don’t know if this is an update issue or a Chromebook/chrultrabook issue, but I can go from kernel 6.12 to the experiemental 6.16. But any kernel in between fails to mount the root partitions.

Just checked and it’s only on Wayland. X11 logins in just as quick as ever.

1 Like

I’ve been running kernel 6.6 lately, as the last “good” 6.12 kernel for me was 6.12.4… 6.12.10 (or was it 12) gave me some grief which I resolved by reverting to 6.6 ever since.

Seeing as 6.12 is all the way up to 6.12.34, I figured it’d be a good idea to see if the newest LTS would now prove to be grief free for me.

A few hours in I thought to launch a game via steam… Dark Souls PTDE… and everything was fine except for it no longer recognizing my controller. every other game I launched had a working controller… very odd

Long story short, seems that my Framework Laptop’s keyboard and numpad “modules” are now being detected as controllers… they were listed inside steam’s controller settings page… and seconded by KDE’s System Settings => Game Controller device list.

That coupled with a known issue in many From Software games that “thou shall have only 1 HID controller connected”… I was left with a choice:

  • go back to kernel 6.6 without attempting troubleshooting, or
  • see if I could find a solution for the 6.12+ kernel’s

… and I found my answer at https://www.reddit.com/r/linux_gaming/comments/1iym0ew/steam_detects_keyboard_as_controller_any_way_to/

Following the article I created a new UDEV rule file @

/etc/udev/rules.d/99-framework-keyboards-are-not-controllers.rules
SUBSYSTEM=="input", ATTRS{idVendor}=="32ac", ATTRS{idProduct}=="0012", ENV{ID_INPUT_JOYSTICK}=""
SUBSYSTEM=="input", ATTRS{idVendor}=="32ac", ATTRS{idProduct}=="0014", ENV{ID_INPUT_JOYSTICK}=""

ran sudo udevadm control --reload-rules && sudo udevadm trigger, rechecked KDE System Settings to confirm only my PS5 controller was listed, and relaunched Dark Souls PTDE with my controller working once again!

How did I get my Vendor & Product ID's?

short answer… via lsusb

The output of lsusb looks something like this…
Bus ### Device ### ID VVVV:PPPP Name
VVVV = Vendor
PPPP = Product

lsusb | grep Framework                                                                                                
Bus 001 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card
Bus 001 Device 007: ID 32ac:0014 Framework Laptop 16 Numpad Module
Bus 001 Device 011: ID 32ac:0012 Framework Laptop 16 Keyboard Module - ANSI

And that’s how I got the required ID’s for creating my two-lined UDEV rule file for Vendor 32ac, Products 0012 and 0014

2 Likes

Updated today via TTY, everything seems ok.
I noticed several “kernel missing headers” warnings tho… any advice?
I did a snapshot on Timeshift just in case so I can revert it if something is not right…

EDIT: I have also Kernel 5.15 installed but I checked kernel manager and it doesn’t appear, is it related with the “missing headers” warning? Should I open a support thread?

Yes. Install them. :smile:

sudo pacman -S linuxNNN-headers

… whereby NNN stands for the kernel version. For instance, for 6.12, it’d be linux612-headers.

The kernel headers for your currently running kernel are commonly needed when you are using DKMS, such as for the proprietary Nvidia driver. You will need to install those headers for every kernel version you’re using.

No, that probably has another cause.

Probably. :grin:

mhwd-kernel -li
Currently running: 6.12.34-1-MANJARO (linux612)
The following kernels are installed in your system:
   * linux515
   * linux61
   * linux612 

I swore I only had 2 kernels installed strange… My machine is all AMD.
So I have to install headers for all of them inluding the current one?
Better open a support thread then…

most important for the kernel you are running (linux612), but if you think there is a chance that you’ll swap to one of the older kernels, then it’d be a good idea to proactively install them now so you don’t need to remember to install the header later before switching kernel.

2 Likes

Yes.

sudo pacman -S linux61-headers linux612-headers linux515-headers

… unless you don’t intend to use the other installed kernels.

Well, obviously something needs those headers. Could be some proprietary WiFi drivers, or possibly virtualbox drivers. We don’t know what you’ve got in your machine or what you’ve got installed.

2 Likes

Done, I installed the headers and yes I do use VirtualBox.
Also I checked the Kernel Manager and all Kernels I have installed appear now as such so everything ok I guess…
Thank you for the guidance!

2 Likes

The update went smoothly, but after restarting and logging in, my external monitor is messed up. I have to unplug and replug it to fix it. It’s happening with kernels 6.6 and 6.12, using both HDMI and DP. Kernel 6.1 works fine.

System:
  Host: onecto Kernel: 6.6.94-1-MANJARO arch: x86_64 bits: 64 compiler: gcc
    v: 15.1.1 clocksource: hpet
  Desktop: GNOME v: 48.2 tk: GTK v: 3.24.49 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 48.0 Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 82B5 v: Lenovo Legion 5 15ARH05
    serial: PF234YKG Chassis: type: 10 v: Lenovo Legion 5 15ARH05
    serial: PF234YKG
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40688 WIN serial: PF234YKG
    part-nu: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
    uuid: 7ed64bc8-fa1a-11ea-80e7-5405db6dcccc UEFI: LENOVO v: EUCN41WW
    date: 09/20/2023
Battery:
  ID-1: BAT0 charge: 30.4 Wh (58.1%) condition: 52.3/60.0 Wh (87.2%)
    volts: 15.4 min: 15.4 model: SMP L19M4PC0 type: Li-poly serial: 1567
    status: not charging cycles: 118
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard
    serial: 93-78-fe-15 charge: 55% (should be ignored) rechargeable: yes
    status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Mouse
    serial: 00-00-00-00 charge: 55% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: 8-core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64
    type: MT MCP smt: enabled arch: Zen 2 rev: 1 cache: L1: 512 KiB L2: 4 MiB
    L3: 8 MiB
  Speed (MHz): avg: 1400 min/max: 1400/2900 boost: enabled volts: 1.2 V
    ext-clock: 100 MHz cores: 1: 1400 2: 1400 3: 1400 4: 1400 5: 1400 6: 1400
    7: 1400 8: 1400 9: 1400 10: 1400 11: 1400 12: 1400 13: 1400 14: 1400
    15: 1400 16: 1400 bogomips: 92658
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] vendor: Lenovo
    driver: nouveau v: kernel arch: Turing pcie: speed: 2.5 GT/s lanes: 8 ports:
    active: DP-1,eDP-1 empty: HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:1f95
    class-ID: 0300 temp: 31.0 C
  Device-2: IMC Networks Integrated Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-3:2 chip-ID: 13d3:56ff
    class-ID: 0e02
  Display: unspecified server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
    compositor: gnome-shell driver: X: loaded: modesetting alternate: fbdev,vesa
    gpu: nouveau display-ID: :1 screens: 1
  Screen-1: 0 s-res: 3360x1080 s-dpi: 96 s-size: 889x286mm (35.00x11.26")
    s-diag: 934mm (36.77")
  Monitor-1: DP-1 pos: primary,top-right model: Dell P2417H
    serial: FMXNR7BJ0TRT res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 93
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") modes: max: 1920x1080
    min: 720x400
  Monitor-2: eDP-1 pos: bottom-l model: BOE Display 0x08df res:
    mode: 1440x810 hz: 60 scale: 100% (1) dpi: 106 size: 344x194mm (13.54x7.64")
    diag: 395mm (15.5") modes: max: 1920x1080 min: 640x350
  API: EGL v: 1.5 platforms: device: 1 drv: swrast gbm: drv: kms_swrast
    surfaceless: drv: swrast x11: drv: swrast inactive: wayland,device-0
  API: OpenGL v: 4.5 vendor: mesa v: 25.1.4-arch1.1 glx-v: 1.4
    direct-render: yes renderer: llvmpipe (LLVM 20.1.6 256 bits)
    device-ID: ffffffff:ffffffff
  Info: Tools: api: eglinfo,glxinfo x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s
    lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:10fa class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor vendor: Lenovo
    driver: N/A pcie: speed: 16 GT/s lanes: 16 bus-ID: 05:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    vendor: Lenovo driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.6.94-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator
  Server-1: PipeWire v: 1.4.5 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 1000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eno1 state: down mac: 54:05:db:6d:cc:cc
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie:
    speed: 5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp4s0 state: up mac: a4:b1:c1:aa:9f:88
  IF-ID-1: ppp0 state: unknown speed: N/A duplex: N/A mac: N/A
  IF-ID-2: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-3:3 chip-ID: 8087:0029 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 2 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: A4:B1:C1:AA:9F:8C
Drives:
  Local Storage: total: 1.11 TiB used: 233.57 GiB (20.6%)
  ID-1: /dev/nvme0n1 vendor: Micron model: MTFDHBA256TDV size: 238.47 GiB
    speed: 31.6 Gb/s lanes: 4 tech: SSD serial: 2028299FF8C0 fw-rev: 3011P4LN
    temp: 31.9 C scheme: GPT
  ID-2: /dev/sda vendor: A-Data model: SU630 size: 894.25 GiB
    speed: 6.0 Gb/s tech: SSD serial: 2L072L1514HW fw-rev: 0A0 temp: 27 C
    scheme: GPT
Partition:
  ID-1: / size: 99.94 GiB used: 58.96 GiB (59.0%) fs: xfs dev: /dev/sda1
  ID-2: /boot/efi size: 299.4 MiB used: 17.6 MiB (5.9%) fs: vfat
    dev: /dev/sda5
  ID-3: /home size: 499.76 GiB used: 174.59 GiB (34.9%) fs: xfs
    dev: /dev/sda3
Swap:
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda2
Sensors:
  System Temperatures: cpu: 64.2 C mobo: N/A gpu: nouveau temp: 31.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 15 GiB used: 5.25 GiB (35.0%)
  Processes: 539 Power: uptime: 24m states: freeze,mem,disk suspend: deep
    wakeups: 0 hibernate: platform Init: systemd v: 257 default: graphical
  Packages: pm: pacman pkgs: 1607 Compilers: gcc: 15.1.1 Shell: Sudo (sudo)
    v: 1.9.16p2 default: Bash v: 5.2.37 running-in: guake inxi: 3.3.38

Have you tried switching to Wayland?

Since the last update, my headset connects and then immediately disconnects. I can no longer use it.