[Unstable Update] March 2025

Kann Abhängigkeiten nicht erfüllen:
- nicht vorhandene Abhängigkeit 'libFLAC.so=12-64' benötigt von mkvtoolnix-cli

Fixed with mkvtoolnix-cli 90.0-2.

3 Likes

Recently had an issue, Steam no longer worked correctly the window is invisible but steam is running as indicated by the system tray icon, I also tried a running a few games, one immediately crashed, another was a black screen, and one worked.

At first I thought the issue was with linux613-nvidia-open, so I unstalled the open drivers and also thought I’d try an LTS kernel so I then tried linux612-nvidia but had same problem (although I did try running steam from the terminal to see what the output would be), I then tried X11 session but similar invisible screen problem and it messed up my sceen resolution, so I reinstalled the nvidia-open drivers, restarted and logged into a Plasma Wayland session.

When running steam from konsole, the output indicated that steam only found the integrated gpu (which I don’t use - never did). So I blacklisted it, rebooted and now Steam correctly finds the GPU I use as displayed below:

Running query: 1 - GpuTopology
Response: gpu_topology {
  gpus {
    id: 1
    name: "NVIDIA GeForce RTX 4070 Ti SUPER"
    vram_size_bytes: 17171480576
    driver_id: k_EGpuDriverId_NvidiaProprietary
    driver_version_major: 570
    driver_version_minor: 133
    driver_version_patch: 7
  }
  default_gpu_id: 1
}

I put this here in the unstable updates section since I am not sure if this is an: nvidia, kernel, steam, or a packaging issue.

The basic system info can be found in my profile.

:gnome: :partying_face:

4 Likes

It may be related, but according to the pacman log I upgrade lib32-mesa on March 15, and steam was working without issue for sure until March 18 (I made a purchase in the app that evening).

So after the updates today, I decided to unblacklist the integraded gpu and try running steam again.
This time it see both:

Running query: 1 - GpuTopology
Response: gpu_topology {
  gpus {
    id: 1
    name: "NVIDIA GeForce RTX 4070 Ti SUPER"
    vram_size_bytes: 17171480576
    driver_id: k_EGpuDriverId_NvidiaProprietary
    driver_version_major: 570
    driver_version_minor: 133
    driver_version_patch: 7
  }
  gpus {
    id: 2
    name: "AMD Radeon Graphics (RADV RAPHAEL_MENDOCINO)"
    vram_size_bytes: 45627949056
    driver_id: k_EGpuDriverId_MesaRadv
    driver_version_major: 25
    driver_version_minor: 0
    driver_version_patch: 2
  }
  default_gpu_id: 1
}

That being said, I’m going to re-blacklist the integrated gpu so to avoid any sort of future compute-confusion.

@weingeist @ydar

I can’t reproduce the issue. Is there any difference with Mesa 25.0.2?

no

/usr/bin/./steam-runtime %U                                                                                                                                                ✔ 
steam.sh[2100]: Running Steam on manjarolinux 25.0.0 64-bit
steam.sh[2100]: STEAM_RUNTIME is enabled automatically
setup.sh[2155]: Steam runtime environment up-to-date!
steam.sh[2100]: Log already open
steam.sh[2100]: Using supervisor /home/weingeist/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/bin/steam-runtime-supervisor
steam.sh[2100]: Steam client's requirements are satisfied
CProcessEnvironmentManager is ready, 6 preallocated environment variables.
[2025-03-22 22:00:57] Startup - updater built Jan 28 2025 00:50:36
[2025-03-22 22:00:57] Startup - Steam Client launched with: '/home/weingeist/.local/share/Steam/ubuntu12_32/steam' '-srt-logger-opened' '%U'
03/22 22:00:57 minidumps folder is set to /tmp/dumps
03/22 22:00:57 Init: Installing breakpad exception handler for appid(steam)/version(1738026274)/tid(2215)
glx: failed to create dri3 screen
failed to load driver: nouveau

4070 Ti Super

That makes no sense if one is using the NVIDIA proprietary driver–which I am.

Either way, please follow the upstream Mesa issue:

Latest update for python-gobject (3.50.0-2 => 3.52.3-2) causes eog and rhythmbox to stop working. Downgrading to prev version fixes it…

/usr/lib/python3.13/site-packages/gi/module.py:57: Warning: cannot register existing type 'GIRepository' repository = Repository.get_default()
/usr/lib/python3.13/site-packages/gi/module.py:57: Warning: g_once_init_leave_pointer: assertion 'result != 0' failed repository = Repository.get_default()
/usr/lib/python3.13/site-packages/gi/module.py:57: Warning: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed repository = Repository.get_default()

Cheers,
Eddy

I can’t reproduce with eog, however I can with rhythmbox:

/usr/lib/python3.13/site-packages/gi/module.py:57: Warning: cannot register existing type 'GIRepository'
  repository = Repository.get_default()
/usr/lib/python3.13/site-packages/gi/module.py:57: Warning: g_once_init_leave_pointer: assertion 'result != 0' failed
  repository = Repository.get_default()
/usr/lib/python3.13/site-packages/gi/module.py:57: Warning: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
  repository = Repository.get_default()

Related upstream issue:

EDIT: Seems to be a PyGobject related issue and also effects Gedit as I noted in the Known Issues above.

and so, the 614 kernel is out but ntsync support is still not enabled, there’s a reason why this is so ? I have already asked several times about its, but never received a response

2 Likes

Gnome 48 on x11: some extensions show “ERROR” although the version number
in metadata.json is “48” even after logout/login.
Solution: log out, change to wayland, login, should work now.
Go back to x11, works now.
Hint for HDR-Screens: there is a switch in monitor settings…
(But only in Wayland)

libadwaita 1.7 is required for AUR package bottles. When would it get in unstable?

It’s already there, resync your mirrors?

pacman -Qi libadwaita                                                 [1]
Name            : libadwaita
Version         : 1:1.7.0-1
2 Likes

A few issues for me:

  1. mhwd won’t let me force install video-nvidia:
# mhwd -i pci video-nvidia --force
> Removing video-nvidia...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/local/pci/video-nvidia/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
Processing classid: 0302
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing nvidia-utils breaks dependency 'nvidia-utils=570.133.07' required by linux612-nvidia
:: removing nvidia-utils breaks dependency 'nvidia-utils=570.133.07' required by linux614-nvidia
:: removing nvidia-utils breaks dependency 'nvidia-utils=570.133.07' required by linux66-nvidia
Error: pacman failed!
Error: script failed!
  1. mutter 48 causes massive mouse lag/stutter on wayland with multiple monitors.

Someone opened an issue here:

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8272

I am currently downgraded to mutter 48rc-1 which works.

  1. My system can’t suspend:
[25518.816437] Freezing user space processes failed after 20.062 seconds (1 tasks refusing to freeze, wg_busy=0).

[25526.349725] ldrm:_nv_drm_gen_mukws_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00002b00] Failed to map NvKmsKapiMemory 0x00000006fb570af7

Indeed. I just applied !4371 with mutter 48.0-4.1 and can confirm that resolves it.

2 Likes

Well, pointer: Make CursorSpriteXcursor handle multiple shapes (!4373) · Merge requests · GNOME / mutter · GitLab is suggested by now to solve the issue.

2 Likes

Well, let’s give the developers a little longer to review it. More commits were added in the last few minutes as well.

What about my mhwd issue, is that a known problem that’s being worked on or is something wrong on my system?