can not use lptools when ssh'ed into a system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
launchpadlib |
Triaged
|
Low
|
Unassigned |
Bug Description
I'd like to be able to use lptools on another system to which I am connected via ssh. This fails for me:
14:12:29 - flash:[/tmp] lp-grab-attachments 991792
Gkr-Message: couldn't connect to dbus session bus: Failed to connect to socket /tmp/dbus-
Traceback (most recent call last):
File "/usr/bin/
main()
File "/usr/bin/
launchpad = config.
File "/usr/lib/
return Launchpad.
File "/usr/lib/
credential_
File "/usr/lib/
authorizati
File "/usr/lib/
return self.do_
File "/usr/lib/
'launchpadlib', unique_key)
File "/usr/lib/
return _keyring_
File "/usr/lib/
items = gnomekeyring.
gnomekeyring.
affects: | lptools → launchpadlib |
Changed in launchpadlib: | |
importance: | Undecided → Low |
status: | New → Triaged |
When I use launchpadlib for sync bug descriptions on different projects I can see the same error on my VM (with user via ssh).
and realy, I can't find workaround for this issue (only run my scripts like services from the desktop user session)
Looks like we can implement other login methods (or create specific users for auto-scripts), which will allow to work with launchpad API without oAuth.