You should not use sudo with pamac.
3 Likes
If you have NTFS partitions/drives donāt use kernel 6.8, it will fail to mount them at boot, and can even corrupt your saved data.
Remember LO scaling issue on Plasma 6? Itās back, because the next update of LO uses vcl:kf6 or something like that.
You are right. Without sudo there is no segfault, but it still freezes like on GUI version:
pamac update -a
Preparing...
Database synchronization...
Refreshing core.db...
Refreshing extra.db...
Refreshing multilib.db...
Refreshing DEB_Arch_Extra.db...
And it stays there forever. When forcefully quit, database lock needs to be removed manually.
Did you try without AUR? And using the deb_extra third party repo is unsupported.
AUR packages install actually works. The additional repo is just for one package. It has nothing to do with the issue, because there are many users reporting the same kind of behavior, and none of them have this specific repo. Just check the comments above. It is already reported, so now we just need to wait for the fix:
1 Like
Your wireplumber LUA configuration files may no longer work, after update to 0.5.0-1:
EDIT 1: The third Trackmania 2020 sub-item
EDIT 2: LibreOffice scaling issue
I tested Plasma 6 with KaOS as soon as it jumped to RC (Jan 31st I think) and last week I re-installed it as Manjaro KDE and started using unstable. Itās a few-years-old Lenovo E495 with a Ryzen CPU+iGPU, no issues there as expected.
A few days ago I (made a full backup and) kicked my workstation (AMD CPU+GPU) into unstable too, and everything went better than expected! I have a few remarks, some of which were already known:
- application launcher icon was reset
- I had to change it two times after two reboots, but the second change sticked
- default audio device changed from Sound Blaster Z to AMD Radeon HDMI
- this happened during package installation
- accelerated YouTube playback with Firefox works as usual
- Trackmania 2020 (using Steam native) in windowed mode no longer has a window title bar
- this can be anything from Proton to KWin
- can be moved with Super+drag still
- mouse clicks donāt go through at all in windowed mode - this is a non-harmless issue
- LibreOffice double-scales its UI
- Fixed upstream - link in earlier this thread
Okay, my deskputer isnāt configured with anything fancy, aside a few mouse and GUI options, so I kinda expected the config nuke not needing to take place. Anyway, itās awesome to see the upgrade process go so smoothly. Great work!
2 Likes
hello. Iām having issues trying to update kooha. it say its unable to meet dependenciesā¦ glib2>=2.80 and libadwaita>=1:1.5.0. how can I fix this? thank you
From the Arch packagerās comments, it rather sounds like you are being intentionally blocked.
- upgpkg: 2.3.0-2: Block installation for folks without glib2 from testing
- upgpkg: 2.3.0-3: Block installation for folks without libadwaita from testing
- upgpkg: 2.3.0-4: Include epoch version in version requirement to catch libadwaita
As of 2024-03-23, only Arch Testing has glib2>=2.80 and libadwaita>=1:1.5.0.
Which filesystem?
Its an old veracrypt container from the time before i used linux (about 8 years ago) and, yes its filesystem is NTFS.
I have read Philms latest statement:
but i myself did not define any mount options in veracrypt.
So either veracrypt has to change its default mount behavior (by the way, its not only veracrypt, also cryptsetup is not able to mount the container with kernel 6.8) or i have to convert my container to another filesystem, i think.
Addentum:
I have copied contents from NTFS-veracryptfile to a newone formatted with exFAT and that has solved the problem for me!
1 Like
Fine, if i want to use pamac i cannot use mesa-nonfree repo anymore 
I wonder if this is a bug or a feature like āyou should not use third-party-reposā 
Another curiosity:
Not all third-party-repos seem to give this problem, i have included chaotic-aur-repo which is probably not a showstopper but mesa-nonfree definitely is.
Thanks for the feedback, since im using Exfat Filesystem in Veracrypt i was worried that i would sooner or later maybe run into this issue, but now that you confirmed that you could solve the problem with Exfat, im less worried 
1 Like
@ara we updated pacman, which might fix the issues you may have with 3rd party repositories.
2 Likes
Yes, pamac working again with pacman 3rd party repos enabled!
1 Like
You can use any repo you wish - your system under your control
But update announcements are for reporting issues with Manjaro repository packages
1 Like
Please read my statement and the context. It deals with an issue from pamac where using some third party repos (but not all, as i stated) has temporary blocked the update-process.
This issue is fixed now, as you can also read.
Also please understand that i already know that its my system and my control.
1 Like
I read the context and resolution on Manjaro Gitlab before your comment
pamac-daemon coredumps on database sync with
upgrade
It is a problem from libalpm because when adding the DEB_Arch_Extra repo, I have a segfault with pacman 6.1.0-3 but not when I build pacman from git master branch. The required fix is Fetch signature and database from the same URL (eb5bf691) Ā· Commits Ā· Pacman / Pacman Ā· GitLab
1 Like
And, pamac is not a Manjaro repository package?