1. apt-get install dbus-user-session
2. reboot
3. confirm flatpak not installed:
emc@emc-office:~$ which flatpak
4. Check reverse dependancies and ensure there is nothing dependant on it
emc@emc-office:~$ apt-rdepends --reverse dbus-user-session
Reading package lists... Done
Building dependency tree
Reading state information... Done
dbus-user-session
Reverse Depends: razer-daemon (1.1.15-0ubuntu1)
razer-daemon
Reverse Depends: polychromatic (>= 0.3.10-xenial)
polychromatic
emc@emc-office:~$ sudo apt-get remove --purge razer-daemon polychromatic
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'polychromatic' is not installed, so not removed
Package 'razer-daemon' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
5. Check Passwords and Keys
Login section is missing
6. start chrome
emc@emc-office:~$ /opt/google/chrome/chrome
[4151:4181:0823/233754.144116:ERROR:nss_util.cc(802)] After loading Root Certs, loaded==false: NSS error code: -8018
Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[4151:4151:0823/233844.494199:ERROR:background_mode_manager_aura.cc(13)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool)
Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[4151:4176:0823/233909.532194:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-103397427961759974994
7. Remove dbus-user-session, reboot and confirm problem resolved
Yep.
So I think this is clear that adding/deleting dbus-user-session induces seahorse to not unlock, cause undetermined, which then sets off failures for anyone using keys.
1. apt-get install dbus-user-session
2. reboot
3. confirm flatpak not installed:
emc@emc-office:~$ which flatpak
4. Check reverse dependancies and ensure there is nothing dependant on it
emc@emc-office:~$ apt-rdepends --reverse dbus-user-session
Reading package lists... Done
Building dependency tree
Reading state information... Done
dbus-user-session
Reverse Depends: razer-daemon (1.1.15-0ubuntu1)
razer-daemon
Reverse Depends: polychromatic (>= 0.3.10-xenial)
polychromatic
emc@emc-office:~$ sudo apt-get remove --purge razer-daemon polychromatic
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'polychromatic' is not installed, so not removed
Package 'razer-daemon' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
5. Check Passwords and Keys
Login section is missing
6. start chrome
emc@emc-office:~$ /opt/google/ chrome/ chrome 0823/233754. 144116: ERROR:nss_ util.cc( 802)] After loading Root Certs, loaded==false: NSS error code: -8018 0823/233844. 494199: ERROR:backgroun d_mode_ manager_ aura.cc( 13)] Not implemented reached in virtual void BackgroundModeM anager: :EnableLaunchOn Startup( bool) 0823/233909. 532194: ERROR:token_ service_ table.cc( 130)] Failed to decrypt token for service AccountId- 103397427961759 974994
[4151:4181:
Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[4151:4151:
Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[4151:4176:
7. Remove dbus-user-session, reboot and confirm problem resolved
Yep.
So I think this is clear that adding/deleting dbus-user-session induces seahorse to not unlock, cause undetermined, which then sets off failures for anyone using keys.