mutter doesn't position SSH_AUTH_SOCK to gnome-keyring value
Bug #599506 reported by
Didier Roche-Tolomelli
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mutter (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: mutter
when starting mutter as a windowmanager required_component:
- Ctrl + Alt + T (mutter starting a gnome-terminal) : env | grep SSH_AUTH: SSH_AUTH_
- gnome-terminal started by the panel: SSH_AUTH_
-> Only the panel and other components have gnome-keyring variables into their environment
-> mutter doesn't have when started as required_component
| Changed in mutter (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in mutter (Ubuntu): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
This bug was fixed in the package mutter - 2.31.2-2ubuntu6
---------------
mutter (2.31.2-2ubuntu6) maverick; urgency=low
* remove debian/
finally was an evil idea to delay mutter from WindowManager to
Initialization phase. This create a lot of weird effects like
gnome-keyring race condition not putting most of the time
SSH_AUTH_SOCK to the right value (LP: #599506)
-- Didier Roche <email address hidden> Mon, 28 Jun 2010 21:07:55 +0200