[Stable Update] 2025-04-12 - Kernels, Plasma, Systemd, Mesa, Grub, Wine

[D.Dave]

@obdegirmenci

Sounds like it’s the end of way for this kind of outdated hardware

So I’m lucky (I don’t know for how much time in the future); by executing inxi -G --verbosity=3 | grep Gen | tail -1 I get:
driver: i915 v: kernel arch: Gen-7; I am on Ivy Bridge, and the graphic card is an Intel HD4000.
And glxinfo | grep renderer reports:

    GLX_MESA_copy_sub_buffer, GLX_MESA_gl_interop, GLX_MESA_query_renderer, 
    GLX_MESA_gl_interop, GLX_MESA_query_renderer, GLX_MESA_swap_control, 
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Mesa Intel(R) HD Graphics 4000 (IVB GT2)

On which platform are you on?

[beermad]

I can’t work out what, but something in this update is causing file restoration from the Backintime GUI to crash.

Traceback (most recent call last):
File "/usr/share/backintime/qt/app.py", line 1651, in restoreThisTo
rd.exec()
~~~~~~~^^
File "/usr/share/backintime/qt/restoredialog.py", line 82, in exec
self.config.inhibitCookie = tools.inhibitSuspend(toplevel_xid = self.config.xWindowId, reason = 'restoring')
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/backintime/common/tools.py", line 2045, in inhibitSuspend
cookie = proxy(*[(app_id, dbus.UInt32(toplevel_xid), reason, dbus.UInt32(flags))[i] for i in dbus_props['arguments']])
~~~~~~~~~~~^^^^^^^^^^^^^^
OverflowError: Value -515549088 out of range for UInt32
/bin/backintime-qt: line 26:  9636 Aborted                 (core dumped) /usr/bin/python -Es ${APP_PATH}/app.py "$@"

Backintime & backintime-qt themselves weren’t updated in this (nor were any of the Python dependencies), so it seems to be something at the DBUS level.

After a little bit of digging, I’ve found that this crash can be prevented by commenting out line 82 of /usr/share/backintime/qt/restoredialog.py, which seems to be there to inhibit system suspend via DBUS. I assume this may be a problem for some users but the implications don’t appear bad on my machine.

[D.Dave]

@beermad

Backintime GUI crash

Back In Time (Qt) crashes on Gnome Wayland

Hi everybody, I just tried to run Back In Time with its Qt frontend on my Manjaro Unstable notebook with Gnome Wayland DE. While at first everything looks decent and this dialog occurs, asking me if i want to import an existing profile (which i don’t have), as soon as i press “Nein” the application crashes with the following error: removed unnecessary image backintime-qt  Back In Time Version: 1.5.4 Back In Time comes with ABSOLUTELY NO…

(note: also occurs for me on Xfce, X11.)

[obdegirmenci]

Ivy Bridge still has way to go…

It says G33, but actually it’s G31 Bearlake, which is almost the same. The iGPU is GMA 3100.

Before update (Yonada)
inxi -G

Graphics:
  Device-1: Intel 82G33/G31 Express Integrated Graphics driver: i915 v: kernel
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4 driver: X:
    loaded: intel unloaded: modesetting dri: i915 gpu: i915
    resolution: 1920x1080~60Hz
  API: EGL v: 1.4,1.5 drivers: i915,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.5 compat-v: 2.1 vendor: mesa v: 24.2.8-arch1.1
    renderer: i915 (: G33)
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr

After update (Zetar)

Summary

Graphics:
  Device-1: Intel 82G33/G31 Express Integrated Graphics driver: i915 v: kernel
  Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6 driver: X:
    loaded: intel unloaded: modesetting dri: i915 gpu: i915
    resolution: 1920x1080~60Hz
  API: EGL v: 1.4,1.5 drivers: i915,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.5 compat-v: 2.1 vendor: mesa v: 25.0.3-arch1.1
    renderer: llvmpipe (LLVM 19.1.7 128 bits)
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr

Mesa Amber

Summary

Graphics:
  Device-1: Intel 82G33/G31 Express Integrated Graphics driver: i915 v: kernel
  Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6 driver: X:
    loaded: intel unloaded: modesetting dri: i915 gpu: i915
    resolution: 1920x1080~60Hz
  API: EGL v: 1.4 drivers: i915,swrast platforms: x11,surfaceless,device
  API: OpenGL v: 3.3 compat-v: 1.4 vendor: intel mesa v: 21.3.9-arch.6
    renderer: Mesa DRI Intel G33
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr

[Jangadance]

I’ll give it a try, but trying to go into my Windows drive from my ASUS BIOS still prompts GRUB to start.

[Fux]

Manjaro enjoys me. Thank you all for your Work and Infos in this Forum.
It helped me a lot - since now I was a “silent Reader”. If post is at wrong place, feel free to split to a new topic. The Problem I got solved, the Description may help others.
Usually all the Updates went without attracting Attention, which is fine.
This Time I tried to push grub/Bootloader too - as suggested:

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
sudo grub-mkconfig -o /boot/grub/grub.cfg

shortly after giving the Password to Luks Encryption:
Error symbol "grub-is-cli-auth-need-auth" not found
Cause: System here: Luks/encrypted, btrfs with Subvolumes

A Downgrade after chrooting gave...

Error symbol grub_is_shimlock_enabled not found
Booting with supergrubdisk or Ventoy (Browse/Boot Files In Local Disk) was for me easier then chrooting ino btrfs - also it finds most existing Bootloader on your Disk
You may first backup your /boot/grub/grub.cfg due to uuid`s of encrypted Partitions inside

sudo grub-install ... --recheck

seems not to notice Encryption on GPT2, writes GPT1 in my UEFI-Bootmenu
and does not update the generic EFI-Bootloader in /boot/efi/EFI/boot/bootx64.efi

sudo  tree  /boot/efi             
# should give:
/boot/efi
  └── EFI
    ├── boot
     │   └── bootx64.efi       # generic, fallback EFI-Bootloader
    └── Manjaro
        └── grubx64.efi

Sync the fallback EFI-Loader: forum.manjaro.org root-tip-how-to-primer-on-handling-a-grub-package-update/154003
One thing to mention is the flag –removable of grub-install - explained well in post #28 at archlinux.org pid=2157953#p2157953

better Fix:

sudo pacman -Syu grub
sudo grub-install --removable
sudo grub-mkconfig -o /boot/grub/grub.cfg

[Gkirmathal]

Firefox 138.0 update seems introduced a bug that suddenly prevents user interaction with the toolbar (address/search/plugins/etc) until you restart FF.

138.0.1 has been released to address this, can this update be pushed?

[philm]

@Gkirmathal

138.0.1 has been released to address this, can this update be pushed?

Most likely not due to toolchain updates. Please switch to unstable branch if you really need it or install the flatpak version of firefox.

[beermad]

Perhaps downgrade to the previous version?

[freggel.doe]

I think this is highly inadvisable for a browser as new versions always fix security problems - to which you would make yourself vulnerable by using an older version.

[beermad]

In principle I agree with you. However, when an update renders the browser effectively un-usable (I suffered the same problem myself) there isn’t any alternative.