Just an update on my VRAM issue. Noticed Firefox taking up a lot and there seems to be a n VRAM leak bug in Firefox 141: https://bugzilla.mozilla.org/show_bug.cgi?id=1979488
I have the same error. pacman -Qo tells me that no package owns that file, so Iām also gonna override it.
But iām curious: can that happen if one does npm update -g?
1 Like
My custom colors are running fine, since years under KDE and no changes after this update for KDE Kate or Firefox either.
In Kate under Settings>Window Color Scheme and Edit Color Theme are both selected as usualā¦ maybe you just need to re-select them?
If you ran npm with sudo or as root, then yes.
My KDE Kate color themes are fine. Intact.
But the ColorChooserās Custom colors (red area) is always blank, no matter what I save there. That is the issue on my side.
Weirdly enough, KSnipās color chooser custom colors are intact.
Found this, btw:
https://bugs.kde.org/show_bug.cgi?id=502957
1 Like
Itās a bug. 
1 Like
Yeah, just found it
https://bugs.kde.org/show_bug.cgi?id=502957
1 Like
This went poorly for me.
I installed using my normal pacman -Syu method on my daily driver system thatās been operational and regularly updated since 2021. As usual, I checked and read this page before updating and followed the instructions and warnings. As I mentioned higher up the page, after updating I looked at the output in the terminal and saw that dracut had shown some errors but that the update appeared to have completed properly despite this. Afterwards I ran install-grub as suggested. Furthermore, I took the advice of @7tvd and added the entries that he mentioned into the folder that he suggested.
I had asked for advice from @Yochanan regarding this new dracut implementation. He kindly responded but I wasnāt clear on their statement so asked for a clarification but didnāt receive any. Perhaps itās my own lack of understanding with things, perhaps not. Iāve been a daily Linux user for 20 years at this point some Iām not exactly new at this.
Eventually I had to reboot and was greeted with a grub rescue screen. I booted into a usb live session and followed the manjaro grub rescue wiki to rebuild the boot loader with no luck. It does seem like perhaps dracut wasnāt my problem though. In hindsight, I think that my system may have had the boot loader installed on the MBR and using install-grub put it in an efi partition that I wasnāt using causing things to get messy. Furthermore, I had secure boot turned on in my bios and I think that may have initially been preventing the system from booting after the install-grub changed the grub location. When I turned off secure boot I was greeted with a blue screen showing all of my hardware data with an error about the efi location on my nvme drive being invalid.
Iāve now reinstalled my system. Fortunately, I keep a seperate home partition so I didnāt have to start from scratch. Nonetheless a frustrating experience.
Okay this update is a big problem for me, as it looks my nvidia card is unstable now after the release update. The only thing i was doing, was watching a movie and after i was done, i closed it and went away from PC.
After i came back i saw a full system freeze, only Steam was running minimizedā¦ nothing else was open. TTY wasnāt working, all what i could do was REISUB.
Iāve been having a love/hate relationship with kernel 6.12 as it has had, resolved, and recently reintroduced āpage flip errorsā that have been creating panel freezes in KDE (either laptop screen or external secondary monitor just stops refreshing the display) on my amdgpu.
The fix/workaround for me has been to revert back to kernel 6.6 (I like to stick with LTS), but I donāt have to manage a āproprietaryā driver with my kernel changesā¦ so I have no idea how easy or hard that would be to do.
Food for thought.
1 Like
Smooth update here, a part of a little problem that the pacman -Syu seemed stuck at the end (but I just waited and it finished). It seems that my system has a strange, 0-size timeshift snapshot that hangs (until it timeouts) when the update tries to delete it:
Iāll try to learn how to remove it, but if somebody has any hints for debugging/solving the thing, Iām all ears ;-).
Update: it got deleted on the second try. Puzzling, but ok ā another nice update from the team, thank you!
1 Like
Flameshot was updated to v13 in this stable update:
flameshot 12.1.0-6 13.0.1-1
v13 has a bug with dual monitor setups (affected me at least) where the screen gets offset when trying to take a screenshot.
Downgrading back to the previous version (v12), as recommended by this comment on the linked github issue, is the workaround I went with for now.
sudo pacman -U /var/cache/pacman/pkg/flameshot-12.1.0-6-x86_64.pkg.tar.zst
1 Like
HI! So the new update causes audio problems on ASUSTeK intel raptor lake (alc294 + cs35l41)
Model: 2023 ROG Asus Strix G18
Audio:
Device-1: Intel Raptor Lake High Definition Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel
alternate: snd_soc_avs,snd_sof_pci_intel_tgl
bus-ID: 0000:00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog]
Audio is distorted, full of crackles and popping.
Downgrading linux-firmware seems to āfixā[1] the issue.
See:
Where can I officially submit a bug report for this?
Some less noticeable audio distortion is still present (and also was before the update) I suspect
linux-firmwarealso has to do with that. ā©ļø