Seems to happen surely (and maybe only in this case) if Apper tries to
check for updates for the first.
I have tried from scratch with another debianized machine:
I have installed Apper (for the first time) with
apt-get install apper
and it's installed with other new packages (also packagekit)
then I have do a
/usr/lib/packagekit/packagekitd --verbose > file
and I have checked for new updates from the apper gui and the problem is
appeared. After a few minutes I have killed the process.
It happens every time. But does not happen anymore, after, if I do a
pkcon get-updates
So, for me an initial pkcon get-updates solves the problem but I don't
understand why...
I hope to be helpful
In the packagekitd log attacched:
I have opened apper around at 23:19
and I have start a check for updates around at 23:20
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
