Technically it isn’t, as it’s the better way to do it (and in my opinion, ideally, using pacman instead). But I do agree fully that this doesn’t help GUI users.
Still, the commands are all readily found on here, so hopefully that will suffice for now until this issue is fixed. Also, if Wayland works with your setup, any difference there?
I don’t suppose you’ve tried octopi as an alternative? You can add the notifier icon to your tray and it has a green Pacman “ghost” (see note below) and red blinking one when updates are available.
Just my 2p worth.
Depending on your visibility preferences via right-clicking an empty space next to the notification icons, selecting Configure System Tray and alter the entries.
It is strange - very strange - and apparently - a very random issue.
Last time around was the Gnome desktop - if I recall correct - now it appears you are using Plasma.
Such random issues which cannot be provoked on other systems is impossible to troubleshoot.
I can provoke a similar issue by clicking the main window of pamac - thus hiding the authentication dialog - but it never disappears - it is still present as an active window.
There is two versions of Pamac - a gtk4 version and a gtk3 version.
There is two versions of Plasma - Plasma 6.1.5 on stable and Plasma 6.2.2 in testing and unstable.
I run Plasma 6.2 on Wayland and the gtk3 version of Pamac (no Nvidia - though I can’t really see the GPU connection).
I open Pamac with the icon that indicates available updates.
I want to apply the updates and the Authentication window appears.
I start to type my password and after 1-3 characters the Authentication window disappears. (Sometimes it disappears that fast, that I am not able to type anything.)
Pamac stays open and stays at the step of checking for internal conflicts.
Because closing of Pamac with the cross in the upper right corner does not work, I kill the Pamac process.
A further try shows the same problem.
So it seems to occur deterministic on my system. How can I activate some debug log to provide useful information about this issue?
Runing pamac update in a terminal works fine.
Operating System: Manjaro Linux
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.10.13-3-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 12 Ă— AMD Ryzen 5 2600X Six-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 560 Series
As far as I’m aware this issue and a notification issue have been rearing their ugly heads quite randomly, and for several months, without any definitive solution.
At least until one is found, the Pamac CLI is a viable option. Though, my opinion is that pacman is better. I find that using a combination of commands works well.
> I installed/Updated the Pamac from gtk3 to gtk4 version
later on I removed onedriveGUI, because a popup Windows always came up that I have to re authenticate, which didn’t came up in older Versionen, was annoying, so I uninstalled it.
But I needed to reinstall onedrive-abraunegg
An other day the Security Update for xorg.
And Later on for Testing I Installed TVbrowser
And This Morning These two Updates came up,
the Pamac GUI - Authentication window did not disapear.
You replaced pamac-gtk3 with pamac-gtk (gtk4) and now the authentication dialog works as expected?
That is a quite strange - if I recall correct - the first time you posted about Pamac authentication, your system was using Gnome - and with the Gnome edition comes with pamac-gtk (gtk4) version.
I am quite about this - I have been trying to replicate the issue with pamac-gtk3 on Plasma 6.2 - I have tried with and without enabling thirdparty (AUR) update check and - launching the update from the tray notification - and I cannot recreate a missing authentication dialog.
As noted earlier I can provoke the behaviour of an unresponsive pamac window - at will - by clicking outside the authentication dialog which then moves it to the back. The dialog is still accessible using though using the icon in the taskbar
Maybe because kodi-addon-pvr-waipu is an AUR package!?
Maybe because pamac-cli does not update AUR packages without --aur option
and does not have an authentication window
and works independent of pamac-gtk and pamac-gtk3
I guess it doesn’t matter any more for OP since they found a pamac-gtk workaround
No possibility of getting debug data for pamac-gtk3 to resolve original alleged issue
But pamac-gtk3 is still included in Manjaro ISOs at the moment, so maybe the next user will post some actionable data about problems updating AUR packages
It did, for a while, which I found particularly annoying. GUI Polkit window showing up with a CLI program? No thanks! Got round that at the time by using TTY (or SSH) until it was fixed.
I installed pamac-debug now. Where can I check the debug log after the next time the problem occurred?
My second update today also triggered the problem, but only at the first try. It only updates packages from the extra repository (Thunderbird and Signal) and no AUR. But to be mention I have AUR support activated in pamac including automatic updates. At the next updates I will check if pamac update --aur works and if deactivating AUR support in pamac let the problem disapear or not.
By the way, I also have pamac-gtk3 installed and not pamac-gtk. I will not upgrade now, because maybe I can find further informations about the problem.
pamac-cli has not used an authentication window since at least Jun 2023
Package was also changed to not follow pamac GUI settings for updating AUR packages
and an additional setting to turn off AUR updates was added to pamac GUI packages