On 05.05.2022 04:41, Yuri Kanivetsky wrote: > Hi, > > This might be not a systemd issue. But the behavior is weird, and I'm not sure. > > I'm trying to run GNOME in a docker container. And gnome-keyring fails to start: > > https://gist.github.com/x-yuri/c3c715ea6355633de4546ae957a66410 > > I added debug statements, and in the log I see: > > May 02 05:09:02 ab6aaba04124 systemd[109]: Starting Start > gnome-keyring for the Secrets Service, and PKCS #11... > May 02 05:09:02 ab6aaba04124 gnome-keyring-d[309]: -- main: 1046 > May 02 05:09:02 ab6aaba04124 gnome-keyring-daemon[309]: > gnome-keyring-daemon: no process capabilities, insecure memory might > get used > May 02 05:09:02 ab6aaba04124 gnome-keyring-daemon[309]: -- > fork_and_print_environment: fork(), parent, 653 > May 02 05:09:02 ab6aaba04124 gnome-keyring-daemon[321]: -- > fork_and_print_environment: fork(), child, 684 > May 02 05:09:02 ab6aaba04124 gnome-keyring-daemon[321]: couldn't > access control socket: /run/user/1000/keyring/control: No such file or > directory > May 02 05:09:02 ab6aaba04124 gnome-keyring-daemon[309]: -- > fork_and_print_environment: exit(0), 680 > May 02 05:09:02 ab6aaba04124 gnome-keyring-daemon[321]: -- main: > return 0, 1210 > May 02 05:10:32 ab6aaba04124 systemd[109]: gnome-keyring.service: > State 'stop-sigterm' timed out. Killing. > May 02 05:10:32 ab6aaba04124 systemd[109]: gnome-keyring.service: > Failed with result 'timeout'. > May 02 05:10:32 ab6aaba04124 systemd[109]: Failed to start Start > gnome-keyring for the Secrets Service, and PKCS #11. > ... > > I can only reproduce it on Debian 8. Which kind of makes it > unimportant. But the behavior is so weird (either gnome-keyring is > blocked in/after exit(), or systemd tries to kill a process that > exited), that I can't help but think about what is really going on > there. > So run systemd user instance with debug level logging to see which process are still left.