No issues, everything went smoothly but after i updated i got a message about updates to flatpak. No flatpaks installed but they are enabled in pamac so guessing it’s pamac dependencies that needed updating
1 Like
Just updated and everything seems fine, aside the fact that Firefox hang for a minute after launch (and went gray), which very, very rarely happens. Not sure if that is related to anything.
EDIT: I’m just experiencing weird performance and stability issues:
I closed the lid, opened it a minute later to see a black screen and couldn’t make to the working, visible desktop (suspend is not enabled). I had to reboot forcefully, which made the whole boot animations to be dark gray and when the desktop showed up, there was no cursor and I couldn’t do anything. Another boot: everything seems to be fine. However, I have never experienced anything like that before, so that is very, very worrying.
On a surface, update is fine, but something wrong is underneath and the system is not as stable or performant as it should be. If the issues keep happening, I will have to roll back from the backup.
1 Like
Anything in journalctl?
Nvidia issue is now solved.
3 Likes
System was unable to boot following update of linux66-nvidia-470xx 470.256.02-35
Sep 15 16:35:41 gnomic systemd[1]: Failed to start NVIDIA Persistence Daemon.
But no problem booting other installed kernels 6.1.110 and 6.6-49_rt41
Installed kernel 6.10.10 and that also works no problem, So I removed kernel 6.6.51
EDIT: issue resolved by kernel update 6.6.51-1 > 6.6.52-1
Haven’t checked yet, but it looked like race conditions after hard reboot which I was forced to a few times to get into the system. Current reboot looks normal, or LOOKED normal till I launched YT and it turned out that SOMETHING HAPPENED WITH SOUND VOLUME in KDE, meaning, it is so loud I had to lower it to 4%, while normally it was so quiet I had to use 100% most of the time. However, before any 2% volume step made a difference, while now, difference between 100% and 4% us very, very low. Something is wrong.
Edit: here is the journald output, I don’t see anything unusual or related to sound:
michaldybczak Sirius16-Manjaro ~ journalctl -b-1 -p3 --no-pager
wrz 15 20:38:11 Sirius16-Manjaro kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.TPNL], AE_ALREADY_EXISTS (20240322/dswload2-326)
wrz 15 20:38:11 Sirius16-Manjaro kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240322/psobject-220)
wrz 15 20:38:11 Sirius16-Manjaro kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.TPDD], AE_ALREADY_EXISTS (20240322/dswload2-326)
wrz 15 20:38:11 Sirius16-Manjaro kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240322/psobject-220)
wrz 15 20:38:11 Sirius16-Manjaro kernel: atkbd serio0: Failed to deactivate keyboard on isa0060/serio0
wrz 15 20:38:11 Sirius16-Manjaro kernel: atkbd serio0: Failed to enable keyboard on isa0060/serio0
wrz 15 20:38:12 Sirius16-Manjaro kernel: iwlwifi 0000:06:00.0: WRT: Invalid buffer destination
wrz 15 20:38:12 Sirius16-Manjaro kernel: Bluetooth: hci0: No support for _PRR ACPI method
wrz 15 20:38:13 Sirius16-Manjaro kernel: iwlwifi 0000:06:00.0: WRT: Invalid buffer destination
wrz 15 20:38:13 Sirius16-Manjaro kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
wrz 15 20:38:14 Sirius16-Manjaro kernel: iwlwifi 0000:06:00.0: WRT: Invalid buffer destination
wrz 15 20:38:16 Sirius16-Manjaro systemd[1736]: basic.target: Job paths.target/start deleted to break ordering cycle starting with basic.target/start
wrz 15 21:04:41 Sirius16-Manjaro kernel: watchdog: watchdog0: watchdog did not stop!
Remote desktop function added in Plasma 6.1 seems to be missing, and I don’t see any package that would enable it.
You mean Krdp?
1 Like
Having the individual CPU usage applet in the panel (Plasma), and then clicking to expand it seems to make a black box on wayland… if you’re real unlucky this black void spreads to the entire screen & sddm needs to be restarted.
yup, thought that was installed. oops.
Maybe a refresh will clean up the folder for you.
I got again the issue with the laggy, non-functional cursor. I cannot afford this bug happening so regularly, so I restored the system from the backup.
I can officially say, that this is the worst update since years! Usually, there are no issues or are minor ones that go away quickly, but this time, the cursor bug is too much, because it makes the system non-functional.
I’m switching to stable for some time, in hope it will be resolved with time.
I would report this bug, but I have no idea where, I can’t see any errors in journald and have no idea how to trigger it. It just randomly happens. I could live with the sound issue, but having no pointer in the system to interact with it is too big.
@michaldybczak can you check if that issue with the cursor lag is also present in XFCE, LxQt or GNOME? I assume you use Plasma: Weird mouse anomalies after update to KDE Plasma 6.1 - Help - KDE Discuss
1 Like
I have only two laptops. One, the newest one is for work, so I already applied the backup. The cursor issue happened right after THIS UPDATE. Never experienced it earlier. Installing various DEs on the same system would be tricky and time-consuming. The other (old) laptop is sort of a backup and I wouldn’t like to mess with it too much either. I don’t have any other spare hardware to test other DEs. Besides, this suspiciously happen right after the update after the first reboot, which forced me to a series of hard reboots. Then it worked fine, till 1 or 2 hour later to get this issue again.
The cursor issue seems to be triggered in Firefox (since it never happened during for example gaming session), but closing Firefox is not helping at all. Since I lack the functional cursor, it’s hard to do any tests in that state. Sure, I could try something in TTY, but I don’t have that much time to figure it out. It just doesn’t work. I expect that the current backup will work fine as it was before and mind you, it works on Plasma 6.1.4, so I doubt this is related to the problem you mentioned.
Also, the sound got fixed when I restored from backup.
Like I said, I am not new to this and am using testing and occasional unstable branch from years and rarely any serious issues arise. My system install works 8 years now, so it may have some legacy problems, but in overall, I have less complaints that many newcomers as it seems. However, this update was really messy and I forgot even that could happen. Like I said earlier, on a surface update went fine and everything was OK, but later issues started piling up.
To explain the cursor issue:
Everything works and then, I open some random site and the cursor disappears. Then it turns out somewhere else but frozen. I can move it, but need to wait for ca. 10 seconds for it to more, and in meantime it stays frozen or disappears again. It is as if the whole system was incredibly lagging but I can see that it responds to shortcuts.
Are you experiencing this issue on X11 and Wayland ?
Maybe this is related to this, even tough, it’s not the same issue:
Or this one:
https://bbs.archlinux.org/viewtopic.php?id=297684&p=2
It seems systemd has been causing some problems for some time now, there are maybe other side effects.
@michaldybczak you could also try to boot one of these to see what happens on that machine without installing anything:
1 Like
Uh, no. Unless this is not a question for me. I don’t have working suspend on this laptop and was not trying to suspend the system. The cursor issue has nothing to do with it.
Here is my system info just FYI:
inxi -b
System:
Host: Sirius16-Manjaro Kernel: 6.10.6-10-MANJARO arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.1.4 Distro: Manjaro Linux
Machine:
Type: Laptop System: TUXEDO product: TUXEDO Sirius 16 Gen1 v: N/A
serial: <superuser required>
Mobo: NB04 model: APX958 serial: <superuser required> UEFI: American
Megatrends LLC. v: 1.00A00_20240108 date: 01/08/2024
Battery:
ID-1: BAT0 charge: 73.7 Wh (92.0%) condition: 80.1/80.1 Wh (100.0%)
CPU:
Info: 8-core AMD Ryzen 7 7840HS w/ Radeon 780M Graphics [MT MCP]
speed (MHz): avg: 984 min/max: 400/5137
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 33 [Radeon RX 7600/7600
XT/7600M XT/7600S/7700S / PRO W7600] driver: amdgpu v: kernel
Device-2: Advanced Micro Devices [AMD/ATI] Phoenix1 driver: amdgpu
v: kernel
Device-3: Microdia Integrated Camera driver: uvcvideo type: USB
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu,amdgpu
resolution: 1969x1108
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.2-arch1.1
renderer: AMD Radeon 780M (radeonsi gfx1103_r1 LLVM 18.1.8 DRM 3.57
6.10.6-10-MANJARO)
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8168
Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
Drives:
Local Storage: total: 2.73 TiB used: 711.31 GiB (25.5%)
Info:
Memory: total: 32 GiB note: est. available: 30.58 GiB used: 8.56 GiB (28.0%)
Processes: 415 Uptime: 1h 28m Shell: Bash inxi: 3.3.36
Will try it after work, so probably in late afternoon or evening. Hard to say if the bug will trigger, because it can take a few hours to do so, and what am I going to do with vanilla live system all that time? Hm…
I think everything points to plasma here: [Plasma 6.1] Did something changed in performance for Intel CPUs? - Help - KDE Discuss. You may want to install Xfce - ArchWiki on your system. It should be fine by just installing a minimal version of it to test if Firefox works normal there. An uninstallation should be easy and clean. Simply do a system snapshot before.
Also don’t customize Plasma and try with X11 too. Check also different browsers than Firefox based ones.
I think that was a hasty suggestion - though I’d ask first if you tried creating a test user to verify it already… and jump around between Wayland and X11 as you play.
If that fails, then the general consensus is that the most stable desktop is XFCE (which you’ll likely hate after using Plasma) and there’s advice on methods to do this without messing things up… keeping handy dandy backups at the ready.
Yes that sounds correct, the mouse input & cursor rendering is done by the compositor. Same with window rendering, issues with things being rendered gray were mentioned. I haven’t used KWin + KDE since testing the Asahi Linux alpha a while back, but I do remember some strange things on upgrade between KDE Plasma versions having to do with cache. IIRC, the new version of Plasma was upgraded, but didn’t clear old files in ~/.cache, which were created by the old version of KDE + Plasma. It caused some graphical glitches and other problems until I realized that I needed to: rm ~/.cache/*plasma* and restart the session. It took a while the first time to rebuild caches, but worked fine after that. Maybe that’s what’s happening?
Otherwise, it sounds like a bug in KWin (as reported by inxi: compositor: kwin_wayland ).
Yeah, that’s a valid point. Maybe it helps to save some time using LiveUSB + Ventoy?
Maybe try out booting an alternate compositor in a Live USB / Ventoy drive to rule out other issues?
If it’s a bug in KDE / KWin, then report it to KDE’s bugtracker here. Search for similar issues first to avoid creating a duplicate issue.
1 Like
You reported multiple issues, with your sound, with Firefox, with your mouse. Can you try a new user and use this user for a while to see if you can reproduce the issues (and do not import your real user config folder as if the issue is in local user, you would reimport the issues most likely)?
1 Like