You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I open the Lubuntu Update app from the menu it takes me straight in to the app. When I click on Check For Updates it uses LXQt Sudo to ask for the password to do a checkupdate. Then after that finishes, I click on Install Updates and once again LXQt Sudo asks me for the password, this time for a doupdate. From a user experience point of view this is less satisfactory than Software Sources, where LXQt sudo comes up a single time to allow me to run software-properties-qt, before the interface appears, but that at least then has all the power it needs to run.
I understand that there may be something to do with the Systray icon and notification from the /usr/lib/apt/apt.systemd.daily tasks that made you choose this interface flow, but please bear in mind it is a sub-par flow when called manually from the start menu, and you might like to rethink how privileges are elevated in that case.
Thanks
The text was updated successfully, but these errors were encountered:
When I open the Lubuntu Update app from the menu it takes me straight in to the app. When I click on Check For Updates it uses LXQt Sudo to ask for the password to do a
checkupdate
. Then after that finishes, I click on Install Updates and once again LXQt Sudo asks me for the password, this time for adoupdate
. From a user experience point of view this is less satisfactory than Software Sources, where LXQt sudo comes up a single time to allow me to run software-properties-qt, before the interface appears, but that at least then has all the power it needs to run.I understand that there may be something to do with the Systray icon and notification from the
/usr/lib/apt/apt.systemd.daily
tasks that made you choose this interface flow, but please bear in mind it is a sub-par flow when called manually from the start menu, and you might like to rethink how privileges are elevated in that case.Thanks
The text was updated successfully, but these errors were encountered: