[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#798786: marked as done ([libpam-kwallet5] kwalletd5 started by libpam-kwallet5 is not used by kwalletmanager5)

Your message dated Wed, 15 Mar 2017 12:22:48 +0100
with message-id <20170315112240.3unmhux2rb3yui4o@gnuservers.com.ar>
and subject line Re: Bug#798786: [libpam-kwallet5] kwalletd5 started by libpam-kwallet5 is not used by kwalletmanager5
has caused the Debian Bug report #798786,
regarding [libpam-kwallet5] kwalletd5 started by libpam-kwallet5 is not used by kwalletmanager5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
798786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798786
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Title: Konsole outpu
Package: libpam-kwallet5
Version: 5.4.0-1
Severity: grave

--- Please enter the report below this line. ---

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

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

Now when I start kwalletmanager, a new kwalletd5 process is created.

Konsole output rahul    12806     1  0 22:08 ?        00:00:04 /usr/bin/kwalletd5

instead of it connecting to the already started kwalletd5 process.

Also, when I logout, the initial kwalletd5 process launched by pam is not terminated and becomes a zombie process. So, eventual logins ends up with multiple such processes.

Konsole output rahul     4346     1  0 21:17 ?        00:00:00 /usr/bin/kwalletd5 --pam-login 17 25
rahul     9801     1  0 21:52 ?        00:00:00 /usr/bin/kwalletd5 --pam-login 17 21
rahul    11679     1  0 22:03 ?        00:00:00 /usr/bin/kwalletd5 --pam-login 17 25
rahul    12180     1  0 22:05 ?        00:00:00 /usr/bin/kwalletd5 --pam-login 17 26


--- System information. ---
Architecture: amd64
Kernel: Linux 4.1.0-2-amd64

Debian Release: stretch/sid
500 trusty ppa.launchpad.net
500 stable dl.google.com
500 stable deb.opera.com
500 oldstable packages.x2go.org
500 all liveusb.info
1000 testing security.debian.org
1000 testing httpredir.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.





--- End Message ---
--- Begin Message --- 
Version: 5.6.3-1

¡Hola Rahul!

El 2015-09-13 a las 15:59 +0530, Rahul Amaram escribió:
I pointed my repo to unstable and upgraded plasma-workspace. The problem is now solved. I don't see any more zombie kwalletd5 process.
NOTE 1: ksshaskpass was broken earlier. Now, ksshaskpass is able to retrieve the credentials at login time for adding my private keys to the ssh agent. I am initializing this by adding "ssh-add" in the startup programs (which indirectly calls ksshaskpass).
NOTE 2: It is possible that your kde wallet might get closed after being unlocked upon login. To avoid this, ensure via kde wallet manager "Configure wallet ..." settings that "Close when last application stops using it" is not checked. 

This package finally solves a long-time problem in Debian :)!
Thanks for reporting. I'm closing the issue with the version of kwallet_pam that adds the desktop independant version of the mentioned snippet of startkde. 

Happy hacking,
--
"If it ain't broke, don't fix it" -- Bert Lance

"If we can't fix it, it ain't broke" -- Lieutenant Colonel Walt Weir
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: