PSI-0.9.2/PSI-0.9.3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
psi (Ubuntu) |
Fix Released
|
Medium
|
Stephan Rügamer |
Bug Description
There is a functional issue with the actual psi package
There is a functional issue with the actual psi package. (hoary and breezy)
If you want to use the gnupg feature of psi and setup your current gpg key, it won't connect to your jabber server correctly.
Finally, it's connecting to the jabber server, but is waiting for the gpg passphrase.
In the normal startup state, psi tries to use the gnupg-agent, which is not even recommended it the packages control file.
So, you can work around if you startup psi with `psi --no-gpg-agent` but this is not set in the corresponding .desktop file for this package.
The other way is to mention gnupg-agent as recommended in the control file, or disable the use of gnupg-agent by default in the source.
If you want, I can provide u a patch for this, or change the .desktop file according to my description.
thx :)
\sh
Changed in psi: | |
assignee: | nobody → hcauwelier |
status: | New → Accepted |
Changed in psi: | |
assignee: | hcauwelier → sh-sourcecode |
status: | Accepted → Fixed |
Hi Again,
ok, I figured out what's happening to this gpg-agent. pgp-agent" . This is not enabled by default, so you have to put it into /etc/X11/ Xsession. options.
Well, first of all, if you install gnupg-agent, it will install a new Xsession.option named "use-session-
After you did this, restart your X session and relogin.
Then you can start psi without the --no-gpg-agent option, and it works.
Finally, you should enable this by default, and install the agent as recommended dependency package in gnupg.
Regards,
\sh