https://bugs.kde.org/show_bug.cgi?id=452442
--- Comment #7 from David Edmundson <k...@davidedmundson.co.uk> --- > It's a matter of getting it done. The challenge is the process order. Pam code forks a process sets an env with a path to a socket. When kwalletd starts it maybe connects to this. This all needs to happen before kwalletd tries to start up from any other activation. -- You are receiving this mail because: You are watching all bug changes.
