Public bug reported:
Description: Ubuntu 9.04
Release: 9.04
landscape-client:
Installed: 1.0.29.1-0ubuntu0.9.04.0
Candidate: 1.0.29.1-0ubuntu0.9.04.0
Version table:
*** 1.0.29.1-0ubuntu0.9.04.0 0
500 http://ftp-stud.hs-esslingen.de jaunty/main Packages
100 /var/lib/dpkg/status
This is happening on a random basis, so I am not yet 100% sure about how
to reproduce it.
Here are the lines of ps that show what is being done:
root 24635 0.0 0.0 5052 1348 pts/2 T 21:02 0:00 /bin/sh
/usr/bin/apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 4E5E17B5
root 24638 0.0 0.0 5696 936 pts/2 D 21:03 0:00 gpg
--ignore-time-conflict --no-options --no-default-keyring --secret-keyring
/etc/apt/secr
118 24647 0.4 1.4 59444 44432 ? S 21:04 0:02
/usr/bin/python /usr/bin/landscape-package-reporter --quiet
118 24649 0.0 0.0 3380 1488 ? S 21:04 0:00 sh -c { gpg
--batch --no-secmem-warning --status-fd 1 --no-default-keyring --keyring /etc/a
118 24650 0.0 0.0 3356 760 ? D 21:04 0:00 gpg --batch
--no-secmem-warning --status-fd 1 --no-default-keyring --keyring /etc/apt/trust
Here are the gpg cmdlines:
root 24638 0.0 0.0 5696 936 pts/2 D 21:03 0:00 gpg
--ignore-time-conflict --no-options --no-default-keyring --secret-keyring
/etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring
/etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv-keys 4E5E17B5
118 24650 0.0 0.0 3356 760 ? D 21:04 0:00 gpg --batch
--no-secmem-warning --status-fd 1 --no-default-keyring --keyring
/etc/apt/trusted.gpg --verify
/var/lib/smart/channels/aptsync-51346df49398301a30df1133ebade96f%%http:__snapshots.ekiga.net_snapshots_debian_._Release.gpg
/var/lib/smart/channels/aptsync-51346df49398301a30df1133ebade96f%%http:__snapshots.ekiga.net_snapshots_debian_._Release
As you can see, there are 2 gpg processes, first started as root, second
as landscape (uid 118).
There are now 2 landscape-package-reporter processes and the second one
started one more gpg instance which immediately went into D state.
I think that in order to reproduce this issue some gpg-related action
should be done on trusted.gpg/trustdb.gpg at the same time as lanscape-
package-reporter.
** Affects: landscape-client (Ubuntu)
Importance: Undecided
Status: New
--
landscape-package-reporter introduces a deadlock for gpg when started during
package install/key import
https://bugs.launchpad.net/bugs/410018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
