After update and restart i got full brightness with my monitor which give me eye cancer.
After short research i found this new setting in /etc/tlp.conf - TLP user configuration (version 1.7.0) and changed it to AMDGPU_ABM_LEVEL_ON_AC=4 to solve my problem.
2 Likes
Why is this update so huge?
I literally have no space on my root partition to install it
Is there a way to see the entire dependency tree of the installed packages so that I know what I can remove? It would be nice if we donāt have to ask about every specific package like v86d to find out that itās not needed anymore
1 Like
KDE Plasma, Xorg
Update went fine with some notes. Update with Pamac CLI gave this conflict;
conflicting dependencies:
- x!ļæ½9t and a
ļæ½ļæ½Ch0Fļæ½Nq are in conflict
Running update with pacman shows that tlp is the conflict.
Pacman also asked for some replacements;
:: Replace lib32-libva-mesa-driver with multilib/lib32-mesa? [Y/n]
:: Replace lib32-mesa-vdpau with multilib/lib32-mesa? [Y/n]
:: Replace libva-mesa-driver with extra/mesa? [Y/n]
:: Replace mesa-vdpau with extra/mesa? [Y/n]
:: Replace qcoro-qt6 with extra/qcoro? [Y/n]
After uninstalling tlp I ran pamac upgrade again which did not ask to replace, which its not doing when the recommendation is to replace, and update went through without further hiccups.
A quick check and all seems fine after reboot.
1 Like
itās better to uninstall power-profiles-daemon imo instead of tlp, that thing is next to useless compared to tlp
2 Likes
After update, SDDM canāt load Breath or any themes (I also tried with breeze) ā can"t loggin with Plasma neither X11 ā thanks TimeShift !
1 Like
After the update, any event of moving the Nautilus screen crashes (attach to left corner, example), requiring a restart. Seems something related with NVidia.
ov 30 10:51:59 ryzen systemd[1]: Starting Cleanup of Temporary Directories...
nov 30 10:51:59 ryzen systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
nov 30 10:51:59 ryzen systemd[1]: Finished Cleanup of Temporary Directories.
nov 30 10:51:59 ryzen systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
nov 30 10:52:02 ryzen systemd[4321]: Started dbus-:1.2-org.gnome.Nautilus@4.service.
nov 30 10:52:02 ryzen nautilus[12638]: Connecting to org.freedesktop.Tracker3.Miner.Files
nov 30 10:52:03 ryzen gnome-shell[4449]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3400004 (Loadingā¦)
nov 30 10:52:03 ryzen systemd[4321]: Started dbus-:1.2-org.gnome.NautilusPreviewer@4.service.
nov 30 10:52:03 ryzen systemd[1]: Starting Hostname Service...
nov 30 10:52:03 ryzen systemd[1]: Started Hostname Service.
nov 30 10:52:03 ryzen nautilus[12638]: NautilusShortcutManager 0x5a604f14f760 exceeds NautilusWindow width: requested 374 px, 360 px available
nov 30 10:52:03 ryzen nautilus[12638]: NautilusShortcutManager 0x5a604f14f760 exceeds NautilusWindow width: requested 374 px, 360 px available
nov 30 10:52:03 ryzen nautilus[12638]: NautilusShortcutManager 0x5a604f14f760 exceeds NautilusWindow width: requested 374 px, 360 px available
nov 30 10:52:03 ryzen nautilus[12638]: NautilusShortcutManager 0x5a604f14f760 exceeds NautilusWindow width: requested 374 px, 360 px available
nov 30 10:52:03 ryzen nautilus[12638]: NautilusShortcutManager 0x5a604f14f760 exceeds NautilusWindow width: requested 374 px, 360 px available
nov 30 10:52:03 ryzen nautilus[12638]: NautilusShortcutManager 0x5a604f14f760 exceeds NautilusWindow width: requested 374 px, 360 px available
nov 30 10:52:03 ryzen nautilus[12638]: NautilusShortcutManager 0x5a604f14f760 exceeds NautilusWindow width: requested 374 px, 360 px available
nov 30 10:52:03 ryzen nautilus[12638]: NautilusShortcutManager 0x5a604f14f760 exceeds NautilusWindow width: requested 374 px, 360 px available
nov 30 10:52:03 ryzen nautilus[12638]: NautilusShortcutManager 0x5a604f14f760 exceeds NautilusWindow width: requested 374 px, 360 px available
nov 30 10:52:04 ryzen nautilus[12638]: NautilusShortcutManager 0x5a604f14f760 exceeds NautilusWindow width: requested 374 px, 360 px available
nov 30 10:52:05 ryzen nautilus[12638]: vkQueuePresentKHR(): A surface has changed in such a way that it is no longer compatible with the swapchain. (VK_ERROR_OUT_OF_DATE_KHR) (-1000001004)
nov 30 10:52:05 ryzen gnome-shell[4449]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
nov 30 10:52:05 ryzen gnome-shell[4449]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
nov 30 10:52:06 ryzen gnome-shell[4449]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
nov 30 10:52:06 ryzen gnome-shell[4449]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
nov 30 10:52:06 ryzen nautilus[12638]: NautilusShortcutManager 0x5a604f14f760 exceeds NautilusWindow width: requested 374 px, 238 px available
nov 30 10:52:06 ryzen nautilus[12638]: vkQueuePresentKHR(): A surface has changed in such a way that it is no longer compatible with the swapchain. (VK_ERROR_OUT_OF_DATE_KHR) (-1000001004)
nov 30 10:52:06 ryzen nautilus[12638]: NautilusShortcutManager 0x5a604f14f760 exceeds NautilusWindow width: requested 374 px, 360 px available
nov 30 10:52:07 ryzen gnome-shell[4449]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
nov 30 10:52:07 ryzen gnome-shell[4449]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
nov 30 10:52:07 ryzen kernel: NVRM: Xid (PCI:0000:09:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 0: WIDTH CT Violation. Coordinates: (0x378, 0x0)
nov 30 10:52:07 ryzen kernel: NVRM: Xid (PCI:0000:09:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x500420=0x80000010 0x500434=0x378 0x500438=0x1100 0x50043c=0x0
nov 30 10:52:07 ryzen kernel: NVRM: Xid (PCI:0000:09:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 1: WIDTH CT Violation. Coordinates: (0x380, 0x0)
nov 30 10:52:07 ryzen kernel: NVRM: Xid (PCI:0000:09:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x508420=0x80000010 0x508434=0x380 0x508438=0x1100 0x50843c=0x0
nov 30 10:52:07 ryzen kernel: NVRM: Xid (PCI:0000:09:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 2: WIDTH CT Violation. Coordinates: (0x370, 0x0)
nov 30 10:52:07 ryzen kernel: NVRM: Xid (PCI:0000:09:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x510420=0x80000010 0x510434=0x370 0x510438=0x1100 0x51043c=0x0
nov 30 10:52:07 ryzen kernel: NVRM: Xid (PCI:0000:09:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ChID 002e, Class 0000c597, Offset 00000000, Data 00000000
nov 30 10:52:14 ryzen /usr/lib/gdm-x-session[4353]: (WW) NVIDIA: Wait for channel idle timed out.
Itās possible to downgrade the NVidia version (to before update) and how to do that?
Update: I updated to Kernel 6.12.1-4-MANJARO and NVidia 550.135. Now, some cases work, others donāt and everything stops.
I have two issues after the update.
-
On kernel 6.12, the system (Kde 6, X11, Nvidia 4060 on 535 driver) now canāt see the internal laptop screen, only external screen. On 6.11 everything is fine.
-
[MAJOR] Trackpoint scrolling doesnāt work anymore. How do I get it back?
Wayland still unusable with gnome and nvidia, but everything else works fine, thanks for update!
Very sluggish graphics after update on Manjaro Plasma with intel onboard.
Had to roll back because it was unusable.
3 Likes
Had this same problem as @DanFreed and same solution worked.
However, Pamac isnāt working properly. After removing tlp I tried updating through the GUI and the window closed while running the update. Opened a new instance of it and it wouldnāt update until it closed the previous session that I could no longer access. Restarted my computer and tried to update through GUI again. It asked for password but then closed the password window before I hit enter and started the update. I closed it and began update through CLI. Seems to be no issues as of now but install is still going.
Edit: Everything seems to be working as usual.
1 Like
Hi @Moilleadoir , in Control Panel > Theme > Settings, if you have this set to let apps decide, then it is the app that is controlling it. I do prefer and use dark mode, but I tend to be on the computer a lot at night or in dark rooms.
Now, QT apps may not conform to the settings in Control Panel, those you have to use QT6 Settings.
To be honest, I am not a fan of forcing the user to use one or the other. Some apps work better in dark mode and other works better in light mode, I like the trend where apps are giving the user the option regardless of the system setting.
In a TTY pamac checkupdates found no updates at first, so I ran sudo pacman -Sy. Then pamac checkupdates found 424 available updates, and the update with pamac upgrade went well.
The mirror I use was updated 5 hours before I ran the above.
Same here.
After updating my Manjaro system, I noticed that the appearance of the network speed widget in the taskbar has changed. Previously, the download and upload rates were displayed in a stacked layout (up and down). However, after the update, the layout has changed to a side-by-side (left and right) display.
I preferred the old stacked layout as it was more compact and easier to read. Is there a way to revert to the previous appearance or customize the layout of the network speed widget?
1 Like
Which Intel? Wayland?
OK, it is somehow known that Nvidia isnāt supporting kernel 6.12 yet. Which would also mean that we might release Manjaro 24.2 with 6.11 kernel series ā¦ People can voice up in a polite manner so Nvidia might release updated drivers soon: Patch for 565.57.01 + Linux kernel 6.12 - Linux - NVIDIA Developer Forums
2 Likes
No real problems, I donāt like it when my kernel changed from LTS to 6.11.10-2 but that is an easy fix. Iāll try it out tho, and see how it goes before I revert back.
Cursor size in GTK 4 apps is now too large on Wayland. Bug comes from GTK 4.16 and affects a cursor if its nominal size is different then image size. My workaround was to change cursor theme for now.
This blog post explains it really well: Cursor Size Problems In Wayland, Explained - KDE Blogs
1 Like
Gnome Calendar in Cinnamon lost connection to my added Google account and complained about it at every boot in notifications. Solved by running gnome-online-accounts-gtk and reconnecting it again as third party access.
i3-4005U, X11