Comment 31 for bug 420015

... was found, but after printing a test page I have noticed there is an 'usb' process belonging to user 'lp', and this process eats 100% of one CPU core (almost all is 'system'). Have stopped cups server, killed 'usb' process (doesn't react on sigterm), started CUPS again, queued a job with few pages - again, eating CPU without terminating after those pages were printed (at least they were printed :-)).

Must I file a new bug? Or - is it better to report new bug after official resolution of this one?