[Stable Update] 2024-11-30 - Kernels, Plasma, GNOME, COSMIC, LXQT, SYSTEMD

Announcements Stable Updates
165

Depends on when you performed your update. @philm issued a few additional changes on 12/01/24, see this post.

1 Like
166

Up until the update, OpenSnitch and OneDriveGUI used to open just fine into the system tray in KDE. Now they fail to do so. Must be a change in KDE and applications still need to catch up. Just leaving this here so it is known.

EDIT:
systemd[939]: app-pamac\x2dtray\x2dplasma@autostart.service: Failed with result 'core-dump'.

Process 1077 (ibus-ui-gtk3) of user 1000 dumped core.
Process 944 (kwalletd6) of user 1000 dumped core.
Process 1382 (xdg-desktop-por) of user 1000 dumped core.
Process 1725 (pamac-tray-plas) of user 1000 dumped core.
Process 1721 (DiscoverNotifie) of user 1000 dumped core.
Process 1377 (kactivitymanage) of user 1000 dumped core.

LOL. Ok, Iā€™ll have to take a closer look on whatā€™s going on. This is a dump mess right now.

All of them are crashing on a call to Qt: QtWaylandClient::QWaylandTabletPadV2()

EDIT 178293789123:
Solved. Tablet driver XPPenLinux3.4.9-240607 was causing the crashes. Uninstalling solved it.

167

A post was split to a new topic: Internal Laptop screen is blank after Plasma 6.4.4 update

168

@purplemunchies You have already the latest 550 Nvidia driver packages available. Define it doesnā€™t work with 6.12? which exact GPU you have? Others posted it works for them as seen here: Help testing Nvidia drivers with Kernel 6.12

@Minsker: There is no reason to not uninstall a running kernel when it is EOL. Same will happen if the kernel is provided by the linux package at Arch. You can see their history when they switch out kernels. You can discuss your issue in our gitlab: Find a proper solution to automate EOL kernel removal via ALPM (#13) Ā· Issues Ā· Release plan / Packaging Ā· GitLab. Your issue is more with the amdgpu driver and that it is known that 6.11+ there might be some issues. However, I donā€™t see any issues with 780M iGPU on my end. All 6.10 kernel releases you can find here: Releases Ā· manjaro-kernels/linux610 Ā· GitHub. Simply add linux-meta to your ignore list if you want to keep outdated kernels on your system.

169

4 posts were split to a new topic: Plasma 6.2: massive tearing in all games and more on Wayland

170

Updated three of my machines with no problems. Kalarm has been updated to 24.08.3 and the sound error that had been introduced in version 24.08.1 has been fixed. I undid the workaround changes I had made to the System Beep (bell) and tested the alarm sound. Working fine now.

1 Like
171

A post was split to a new topic: Somethingā€™s off with pamac

173

2 posts were split to a new topic: Plasma widgets, panels and wallpapers disappear after logging in

174

A post was merged into an existing topic: Plasma widgets, panels and wallpapers disappear after logging in

175

Well the one reason I provided - it breaks some setups where people had a reasonable expectancy to be able to roll back (though you could argue my setup is incomplete, it is not an all too uncommon setup for encryption).
Iā€™ll post there (*) about handling this separately from packages. E.g. donā€™t set linux meta to conflict with 6.10, but have the kernel application issue softwarnings that the kernel is EOL (or even notify that a new kernel is available, which Iā€™d like to know about, too).

The reason this doesnā€™t affect all 780M setups, I suspect, has to do with the screen. The Framework 16 internal screen (2560x1600@165Hz) is affected (with a thread on their forums), even worse if set to 60Hz, but my 1080p60Hz external screen is not, while another persons external screen is affected worse than their internal. I think that might be the source of the variety.

Thanks anyway! (Esp. for the tip about ignoring linux-meta, bit risky since without notifications I will probably forget and never update my kernels, so Iā€™d prefer a better solution)

(*) gitlab signup seems broken: An error occurred while validating username

176

Hi Philm,

It is the same behavior as the first time I tried it. In GRUB I select the 6.12.x kernel and it boots to a black screen.

GPU is, NVIDIA GeForce GTX 970.

My Manjaro XFCE system is fully updated. There was one update this morning for Manjaro base files that I applied. Then restarted my PC and tried kernel 6.12.x again just to be sure nothing else changed, with the same result.

177

Somehow seems quite similar to the issue that caused Wayland + Plasma to boot to a black screen on NVIDIA, which was related to how NVIDIA drivers handle KMS on newer kernel versions (or how newer kernels handle KMS).

Maybe try the same instructions, i.e.

  1. Add nvidia_drm.modeset=1 and nvidia_drm.fbdev=1 to GRUB_CMDLINE_LINUX in /etc/default/grub (or use GRUBā€™s edit entry feature to add this manually for testing)
  2. Set MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm) in /etc/mkinitcpio.conf
  3. Rebuild initial ramdisks by running sudo mkinitcpio -P, followed by sudo update-grub to commit those changes

There shouldnā€™t be any harm in trying this, could well be that this applies to XFCE as well for newer kernels.

1 Like
179

Hi fonic,

nvidia_drm.modeset=1 was manually added in the GRUB config sometime last year as a work around for one of the Manjaro updates.

nvidia_drm.fbdev=1 was not part of that and I donā€™t see it in the GRUB config file.

Iā€™m not exactly willing to experiment right now with things that might break my operating system. Kernel 6.11.x works just fine until the Manjaro developers figure how to make 6.12.x work with the Nvidia proprietary graphics drivers.

180

After the update, hardware acceleration in MPV stopped working completely.

2 Likes
181

Thatā€™s understandable, but then it might be difficult for the devs to reproduce the issue, since they cannot test for each and every hardware configuration thatā€™s out there.

182

System crashed twice today with this. Rolled kernel back to 6.11 for now.

kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:79:crtc-0] flip_done timed out
kwin_wayland[1011]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug

Same issue is being reported here

1 Like
183 
lib32-nvidia-utils 550.135-1
linux611-nvidia 550.135-3
linux612-nvidia 550.135-3
mhwd-nvidia 550.135-1
mhwd-nvidia-390xx 390.157-17
mhwd-nvidia-470xx 470.256.02-8
nvidia-settings 550.135-1
nvidia-utils 550.135-1

sddm still crashes when starting the x11 session. Iā€™m on a GeForce GTX 1070. nvidia_drm.modeset=1 kernel option is still in place since previous issues.

184

OTB bitmap fonts do not display anymore with KDE. Apparently this is regression introduced by Qt 6.8.0.

I canā€™t post more details because links are forbidden.

1 Like
185

When I boot into my laptop after upgrading, I am booting into a black screen on Plasma. I have an old Nvidia 965M in this laptop. I already have the kernel parameters set.

When I run plasmashell --replace, I am seeing the following.

KPackageStructure of KPluginMetaData(pluginId:"org.kde.plasma.simplemenu", fileName: "/usr/share/plasma/plasmoids/org.kde.plasma.simplemenu/metadata.json") does not match requested format "Plasma/Applet"
kf.plasma.quick: Applet preload policy set to 1
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth":
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9
Toolbox not loading, toolbox package is either invalid or disabled.
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
qt.dbus.integration: Could not connect "org.cups.cupsd.Notifier" to PrinterFinishingsChanged(QString, QString, QString, uint, QString, bool) : 
applications:com.discordapp.Discord.desktop: Progress value -100 is out of bounds!
LaunchProcess: failed to execvp:
/usr/lib/qt6/QtWebEngineProcess
LaunchProcess: failed to execvp:
/usr/lib/qt6/QtWebEngineProcess
[2787:2787:1203/161719.326285:FATAL:zygote_host_impl_linux.cc(201)] Check failed: . : No such file or directory (2)
Trace/breakpoint trap (core dumped)

I was running kernel 6.6 and I tried going to 6.12, but no change in behavior. Error occurs in both.

Is this maybe just a cache issue? Should I try reinstalling anything?

186

Thanks for the work! I wouldnā€™t have thought that this update didnā€™t result in a broken laptop. This update managed to remove linux610 and install linux611 via the meta pkg, all while running linux610.