Control: severity -1 minor
Control: tag -1 + upstream

On 12/09/15 19:00, Rahul Amaram wrote:
> Severity: grave

> After installing the libpam-kwallet5 package, when I login via SDDM, a process
> such as below is started.

> Konsole outpu rahul    12635 12634  0 22:08 ?        00:00:00
> /usr/bin/kwalletd5 --pam-login 17 27

The way that libpam-kwallet5 works is that is listens in a socket and waits
for someone to connect to it. Currently the part that connects to it is in the
startkde script that is part of plasma-workspace from the version 5.4.0, sadly
plasma-workspace hasn't migrated to testing and so it shows the current 
behavior.

That said, it means that libpam-kwallet5 is only useful in a session that has
the code snippet from startkde:
if test -n "$PAM_KWALLET5_LOGIN" ; then
        env | socat STDIN UNIX-CONNECT:$PAM_KWALLET5_LOGIN
fi
And the kwalletd5 processes will be `hanged' in a session without it.
(You can add the previous snippet to your startkde script to fix this issue
while we wait for plasma-workspace to enter into testing)

This problem was reported upstream as part of the code review done before
packaging it and acknowledged upstream:

http://lists.alioth.debian.org/pipermail/pkg-kde-talk/2014-October/001971.html
and:
http://lists.alioth.debian.org/pipermail/pkg-kde-talk/2015-January/002002.html

Àlex, please consider this a friendly ping about this issue.

Some ideas:
 - Avoid starting a new kwalled5 if there is one already for the same user.
 - Set the environment, if needed, on the first kwalletmanager instantiation.
 - Have a timeout for the environment read (1 minute should be enough).

Happy hacking,
-- 
"It is practically impossible to teach good programming to students that have
had a prior exposure to BASIC: as potential programmers they are mentally
mutilated beyond hope of regeneration."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to