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!
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
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!
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
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.
libpamac 11.6.3-1 extra
Library for Pamac package manager based on libalpm
pamac-gtk 11.7.1-1 extra
A Package Manager based on libalpm with AUR and Appstream support (GTK4)
pamac-cli 11.6.0-3 extra
A CLI Package Manager based on libalpm with AUR support
pamac search pamac
Summary
pamac search pamac
libpamac-snap-plugin 11.6.3-1 extra
Snap plugin for Pamac
libpamac-nosnap 1:11.6.4-1 AUR
Pamac package manager library based on libalpm. Without Snap support
libpamac-git 11.6.4.r0.g9108cba-1 AUR
Library for Pamac package manager based on libalpm - git version
libpamac-full-git 1:11.4.1.r0.g29d7180-1 AUR
Library for Pamac package manager based on libalpm - flatpak and snap support enabled
libpamac-full 1:11.6.4-1 AUR
Library for Pamac package manager based on libalpm - flatpak and snap support enabled
libpamac-flatpak-plugin 11.6.3-1 extra
Flatpak plugin for Pamac
libpamac-debug 11.6.3-1 extra
Detached debugging symbols for libpamac
libpamac-aur 11.6.4-1 AUR
Pamac package manager library based on libalpm
libpamac 11.6.3-1 [Installed] extra
Library for Pamac package manager based on libalpm
pamac-tray-icon-plasma 0.1.3-3 AUR
Pamac tray icon for plasma users
pamac-tray-icon-plasma 0.1.3-2 extra
Pamac tray icon for Plasma users
pamac-nosnap 11.7.1-2 AUR
A Gtk3 frontend, Package Manager based on libalpm with AUR and Appstream support
pamac-gtk3-debug 10.6.0-3 extra
Detached debugging symbols for pamac-gtk3
pamac-gtk3 10.6.0-3 extra
A Package Manager based on libalpm with AUR and Appstream support (GTK3)
pamac-gnome-integration 11.7.1-1 extra
Pamac GNOME integration (GTK3)
pamac-debug 11.7.1-1 extra
Detached debugging symbols for pamac
pamac-cli-debug 11.6.0-3 extra
Detached debugging symbols for pamac-cli
pamac-classic 7.3.0-2 AUR
A Gtk3 frontend for libalpm - classic version
pamac-aur-git 11.7.1.r0.g73cef1d-1 AUR
A Gtk3 frontend for libalpm - git version
pamac-aur 11.7.1-3 AUR
A Gtk3 frontend, Package Manager based on libalpm with AUR and Appstream support
pamac-appstream-hook 1-1 AUR
Pacman hook for cleaning up Appstream data from tags that Pamac can’t handle.
pamac-all-git 1:10.4.3.r0.gd314d70-1 AUR
A Gtk3 frontend for libalpm (everything in one package - snap, flatpak, appindicator)
pamac-all 11.7.1-1 AUR
A GUI frontend for libalpm (everything in one package - snap, flatpak, appindicator, aur, appstream)
pamac-gtk 11.7.1-1 [Installed] extra
A Package Manager based on libalpm with AUR and Appstream support (GTK4)
pamac-cli 11.6.0-3 [Installed] extra
A CLI Package Manager based on libalpm with AUR support
The installed packages are in “Extra” … i.e. in the repos. Some of the other packages are in AUR.
If the ones shown in the first “Summary” are not present, sudo pacman -S pamac
Obviously, pamac is from the Manjaro repositories. Apparently, it crashes when using a third-party repo. Removing the unsupported third-party repo is a good workaround for the issue.
Another obviously, it probably is a bug in pamac which should be fixed.
