SSH service should be hidden from Startup Applications too
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-keyring (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
| Trusty |
Invalid
|
Low
|
Unassigned | ||
| Xenial |
Invalid
|
Low
|
Unassigned | ||
| Yakkety |
Invalid
|
Low
|
Unassigned | ||
Bug Description
SRU Team
========
Wait to accept this. Showing the SSH service was apparently intentional and not just an oversight.
https:/
Impact
======
Ubuntu has for several years set NoDisplay=true for various services that use /etc/xdg/autostart so that users don't open Startup Applications and turn off a service that isn't really meant to be disabled that way
gnome-keyring has a patch to do this, but one service "SSH Key Agent" needs to be added to the patch.
Test Case
=========
Install the updated gnome-keyring package.
Open Startup Applications in Ubuntu (Unity) or Ubuntu GNOME
"SSH Key Agent" should not show up in the list.
Regression Potential
=======
Low. If someone *did* uncheck the box next to SSH in Startup Applications, it will now be a bit more tricky to re-enable that service.
rm ~/.local/
| Changed in gnome-keyring (Ubuntu Xenial): | |
| importance: | Undecided → Low |
| status: | New → In Progress |
| Changed in gnome-keyring (Ubuntu Yakkety): | |
| importance: | Undecided → Low |
| status: | New → In Progress |
| Changed in gnome-keyring (Ubuntu Trusty): | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| description: | updated |
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in gnome-keyring (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Robie Basak (racb) wrote | #2 |
| Changed in gnome-keyring (Ubuntu Xenial): | |
| status: | In Progress → Incomplete |
| Changed in gnome-keyring (Ubuntu Yakkety): | |
| status: | In Progress → Incomplete |
| Changed in gnome-keyring (Ubuntu Trusty): | |
| status: | Triaged → Incomplete |
| Changed in gnome-keyring (Ubuntu Yakkety): | |
| status: | Incomplete → Invalid |
| Changed in gnome-keyring (Ubuntu Xenial): | |
| status: | Incomplete → Invalid |
| Changed in gnome-keyring (Ubuntu Trusty): | |
| status: | Incomplete → Invalid |
| Jeremy Bícha (jbicha) wrote | #3 |
| Khurshid Alam (khurshid-alam) wrote | #4 |
This bug was fixed in the package gnome-keyring - 3.20.0-3ubuntu1
---------------
gnome-keyring (3.20.0-3ubuntu1) zesty; urgency=medium
* Merge with Debian. Remaining changes:
- debian/control.in:
+ Add Vcs-Bzr for Ubuntu.
- debian/control, debian/*.install, debian/rules:
+ Install pkcs11 in its own binary.
- debian/
+ Apply capabilities at the end of the ubiquity process to make sure new
installs have gnome-keyring-
- debian/
+ Provide upstart user session jobs.
- debian/user/*, debian/*.override, debian/rules:
+ Install units to start gnome-keyring with systemd if the session
is using it.
+ Disable XDG autostart when we're using upstart.
- 04_nodisplay_
+ Mark autostart files as NoDisplay=true.
- 0001-Look-
+ Fix finding dlopen and dlsym in the build, fixing FTBFS.
- 0002-pam-
+ Fix null pointer dereference when no password is supplied, e.g. in
lightdm --test-mode.
- 0001-Die-
+ Cherry-pick upstream patch to track our login session and exit if
that ends. This means that gnome-keyring gets cleaned up properly
on logout under dbus-user-session.
* Update 04_nodisplay_
(LP: #1657909)
gnome-keyring (3.20.0-3) unstable; urgency=medium
[ Jeremy Bicha ]
* Enable parallel building and all hardening flags
* Add debian/
- Skip a few failing tests that have already been reported upstream.
Before the switch from cdbs to dh, these tests still failed but did
not fail the build and therefore were mostly unnoticed.
* Explicitly Build-Depend on python for tests (Closes: #832852)
[ Dmitry Shachnev ]
* Depend on default-
dbus-x11 (closes: #835885).
-- Jeremy Bicha <email address hidden> Thu, 19 Jan 2017 20:04:08 -0500