Bug #903269 shows that this issue is still happening in precise. Sebastian, was this thought to be fixed already in aptdaemon? Can you help with this bug?
Bug #903269 shows that this issue is still happening in precise. Sebastian, was this thought to be fixed already in aptdaemon? Can you help with this bug?