@Till: I haven't been able to reproduce the problem post-sprint. But I don't have any other systems on my network advertising CUPS queues. I was only seeing it at the sprint
I'm not sure why you switched this to incomplete though: you've got multiple confirmations of the bug and stack traces indicating where in the code it is busy-looping.
Given that some of the advertised print queues were from your laptop, have you been able to reproduce this on your home network?
@Till: I haven't been able to reproduce the problem post-sprint. But I don't have any other systems on my network advertising CUPS queues. I was only seeing it at the sprint
I'm not sure why you switched this to incomplete though: you've got multiple confirmations of the bug and stack traces indicating where in the code it is busy-looping.
Given that some of the advertised print queues were from your laptop, have you been able to reproduce this on your home network?