I should have anticipated the response.
Have a nice life!
…
Same. I don’t use GUI stuff for upgrading, etc. - just for the panel notifier and sometimes to check what’s available.
For the OP: why not ssh into the media server from another machine and do the upgrades, installations and maintenance that way? No GUI dialogue pop-ups to bug you (unless you use ssh -X maybe).
1 Like
Still a workaround for a BUG.
Then report the BUG.
2 Likes
…and here’s another alternative to recover from it safely: reisub.
I would suggest you use the terminal for your updates until this condition is properly diagnosed and rectified. It is unlikely that pacman or pamac (non-gui) will be affected by such a short time-out to screen blanking; unless you’re configured to immediately hibernate instead of using a sane sleep state.
Using the terminal will make it necessary to change your workflow for a time. That shouldn’t be an issue for any experienced Linux user.
In the meantime, if you are so convinced it’s a bug with Pamac, please report it as such after first making certain it hasn’t already been reported.
Something else you could try in the meantime, however, is changing the Pamac-Manager version:
sudo pacman -Syu pamac-gtk
# or
sudo pacman -Syu pamac-gtk3
… depending which is installed.
During install you will be asked which to keep.
Lastly, failure to maintain your system (as required and expected when using a rolling release distribution) is also a recipe for unexpected conditions to arise.
- Related: System Maintenance
Check that you are fully updated, and that any issues noted in the Stable Update announcements have also been addressed; unless, of course, in the event that you’re using another branch such as ‘Unstable’.
That is all. Good luck.
2 Likes
Happens on both…
Then, you’d best report it, and use pacman in the meantime.
When/if you make that report, you might also consider linking to the post from @Nachlese who I believe was able to reproduce the condition earlier.
Cheers.
It is unlikely to be an issue with pamac-gtk.
Other applications prompting for the password are affected in the same way.
He mentioned gparted.
The screen blanking/locking is interfering with (polkit) authentication.
When the screen gets locked while the password dialog is active
and is then unlocked to continue,
neither the password dialog nor any other part of the GUI is responding.
(except for an already open terminal window - it is half covered by the unresponsive password dialog
and cannot be moved or resized,
but it is still working and commands can be run from it)
Thus my suggestion to restart the display manager, to avoid a hard reset/reboot.
Restarting the display manager will, of course, kill everything else that was running in the session.
I wonder whether that is a Gnome specific behavior.
Or a GDM issue.
I know it does not happen with lightdm and a Xfce4 session.
If it is a bug then it is not one with pamac-gtk.
Yep either Gnome or polkit or their interaction…point a finger of blame & I’ll file the bug report where it needs to go.
Not a solution while streaming media.
I know. But it avoids a hard reset.
Foks, this topic is going nowhere. How can anyone solve the issue with nothing to go on?
Whether the issue is with Pamac, Polkit or whatever: Logs or it didn’t happen.
Please see:
1 Like
It’s confirmed recreatable as described.
If that’s your final answer, this thread will be hidden from the public and closed.
Note that I do not want to do that.
EDIT: To be more clear, neither the developer of Pamac nor the developers of Polkit will have enough information to find out what’s causing the issue without logs.
The helpful volunteers here have already given their suggestions and there’s no more to say.
Which logs would be needed…
They’re specified in the tutorial I linked above. Feel free to ask any questions you have along the way.
1 Like
I installed manjaro-log-helper…you want them all…
but… either it doesn’t recognize my manjaro partition &/or there is no “OK” to click after choosing the logs to save.
I launched pamac from the terminal & no errors were displayed…I got this …
[manjaro@manjaro-pc ~]$ cat gdm.err.log
Apr 15 09:49:23 manjaro-pc gdm-autologin][726]: gkr-pam: couldn't unlock the login keyring.
Apr 15 10:05:46 manjaro-pc gdm-autologin][724]: gkr-pam: couldn't unlock the login keyring.
Apr 15 15:11:05 manjaro-pc gdm-autologin][729]: gkr-pam: couldn't unlock the login keyring.
Apr 15 15:18:12 manjaro-pc gdm-autologin][835]: gkr-pam: couldn't unlock the login keyring.
Apr 15 15:31:15 manjaro-pc gdm-autologin][727]: gkr-pam: couldn't unlock the login keyring.
Apr 15 15:34:31 manjaro-pc gdm-autologin][728]: gkr-pam: couldn't unlock the login keyring.
Apr 15 15:42:51 manjaro-pc gdm-autologin][759]: gkr-pam: couldn't unlock the login keyring.
Apr 15 15:45:28 manjaro-pc gdm-autologin][824]: gkr-pam: couldn't unlock the login keyring.
Apr 15 15:49:21 manjaro-pc gdm-autologin][740]: gkr-pam: couldn't unlock the login keyring.
Apr 15 15:55:08 manjaro-pc gdm-autologin][730]: gkr-pam: couldn't unlock the login keyring.
Apr 15 16:09:10 manjaro-pc gdm-autologin][737]: gkr-pam: couldn't unlock the login keyring.
Apr 15 16:13:05 manjaro-pc gdm-autologin][860]: gkr-pam: couldn't unlock the login keyring.
Apr 15 20:25:40 manjaro-pc gdm-autologin][848]: gkr-pam: couldn't unlock the login keyring.
Apr 17 13:15:38 manjaro-pc gdm-autologin][825]: gkr-pam: couldn't unlock the login keyring.
Apr 17 13:44:54 manjaro-pc gdm-autologin][869]: gkr-pam: couldn't unlock the login keyring.
Apr 17 14:20:48 manjaro-pc gdm-autologin][763]: gkr-pam: couldn't unlock the login keyring.
Apr 17 14:43:20 manjaro-pc gdm-autologin][739]: gkr-pam: couldn't unlock the login keyring.
Apr 18 05:53:15 manjaro-pc gdm-autologin][704]: gkr-pam: couldn't unlock the login keyring.
Apr 19 13:34:06 manjaro-pc gdm-autologin][735]: gkr-pam: couldn't unlock the login keyring.
Apr 23 16:25:35 manjaro-pc gdm-autologin][752]: gkr-pam: couldn't unlock the login keyring.
Apr 23 17:40:09 manjaro-pc gdm-autologin][808]: gkr-pam: couldn't unlock the login keyring.
Apr 23 17:55:57 manjaro-pc gdm-autologin][687]: gkr-pam: couldn't unlock the login keyring.
Apr 27 15:24:41 manjaro-pc gdm-autologin][760]: gkr-pam: couldn't unlock the login keyring.
Apr 27 16:06:40 manjaro-pc gdm-autologin][770]: gkr-pam: couldn't unlock the login keyring.
Apr 27 18:14:36 manjaro-pc gdm-autologin][746]: gkr-pam: couldn't unlock the login keyring.
Apr 27 18:16:45 manjaro-pc gdm-password][2335]: gkr-pam: unable to locate daemon control file
Apr 27 18:49:23 manjaro-pc gdm-autologin][733]: gkr-pam: couldn't unlock the login keyring.
Apr 29 12:54:14 manjaro-pc gdm-autologin][769]: gkr-pam: couldn't unlock the login keyring.
Apr 29 13:37:16 manjaro-pc gdm-autologin][761]: gkr-pam: couldn't unlock the login keyring.
Apr 29 13:46:11 manjaro-pc gdm-autologin][757]: gkr-pam: couldn't unlock the login keyring.
Apr 29 13:56:23 manjaro-pc gdm-autologin][759]: gkr-pam: couldn't unlock the login keyring.
Apr 29 18:53:03 manjaro-pc gdm-autologin][763]: gkr-pam: couldn't unlock the login keyring.
Apr 30 14:51:56 manjaro-pc gdm-autologin][772]: gkr-pam: couldn't unlock the login keyring.
Apr 30 16:22:41 manjaro-pc gdm[639]: GLib: Source ID 85 was not found when attempting to remove it
Apr 30 16:23:07 manjaro-pc gdm[639]: GLib: Source ID 102 was not found when attempting to remove it
Apr 30 16:24:26 manjaro-pc gdm[639]: GLib: Source ID 106 was not found when attempting to remove it
Apr 30 16:30:30 manjaro-pc gdm[639]: GLib: Source ID 110 was not found when attempting to remove it
Apr 30 16:39:04 manjaro-pc gdm[639]: GLib: Source ID 124 was not found when attempting to remove it
Apr 30 16:39:28 manjaro-pc gdm[639]: GLib: Source ID 134 was not found when attempting to remove it
Apr 30 16:39:47 manjaro-pc gdm[639]: GLib: Source ID 138 was not found when attempting to remove it
Apr 30 16:41:11 manjaro-pc gdm-autologin][771]: gkr-pam: couldn't unlock the login keyring.
Apr 30 16:56:09 manjaro-pc gdm[631]: GLib: Source ID 59 was not found when attempting to remove it
May 01 19:13:05 manjaro-pc gdm[631]: GLib: Source ID 62 was not found when attempting to remove it
May 01 19:14:35 manjaro-pc gdm-autologin][774]: gkr-pam: couldn't unlock the login keyring.
May 01 19:32:16 manjaro-pc gdm-password][2738]: gkr-pam: unable to locate daemon control file
May 01 19:43:43 manjaro-pc gdm-autologin][761]: gkr-pam: couldn't unlock the login keyring.
May 01 19:46:48 manjaro-pc gdm-password][2512]: gkr-pam: unable to locate daemon control file
May 02 13:29:15 manjaro-pc gdm-autologin][22955]: gkr-pam: couldn't unlock the login keyring.
May 01 19:42:27 manjaro-pc polkit-agent-helper-1[3864]: pam_unix(polkit-1:auth): conversation failed
May 01 19:42:27 manjaro-pc polkit-agent-helper-1[3864]: pam_unix(polkit-1:auth): auth could not identify password for [manjaro]
[manjaro@manjaro-pc ~]$