Bug#764472: cups creates millions of temporary files when printing
Il 09/10/2014 13:20, Brian Potkin ha scritto:
> Antonio,
>
> Please don't forget to Cc the bug report. I'v bounced your previous two
> mails there so there is no need to do anything about those.
Sorry.
>
>
>
> On Thu 09 Oct 2014 at 11:05:44 +0200, Antonio Sartori wrote:
>
>> Hello Brian,
>>
>> Some additional information:
>>
>> The links are created when printing with evince, but not when printing
>> with lp. (Actually, printing with evince produces blank pages, but I
>> don't know whether this is related - maybe it's a problem of my pdf file.)
>>
>> The links continue to be created after the print command from evince has
>> been given (about 500000 links per minute). During this, a process uses
>> most of the cpu, and it is
>>
>> /usr/bin/python /usr/share/system-config-printer/scp-dbus-service.py
>>
>> Killing this process, the creation of symlinks stops. So I guess this is
>> what creates this lot of symlinks.
>>
>> I am not quite sure now whether this is a bug of evince, or of
>> system-config-printer or something else.
> Nice progress. I'm thinking that your report should be reassigned to
> system-config-printer and merged with #764253:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764253
Yes, I think it is the same problem.
> But before doing so let us see if we can give the maintainers there some
> help.
>
> Acroread is non-running but I'd be happier if it were not around. Please
> would you purge it from the system and try a print or two. From evince
> is one obvious application. Iceweasel uses the same GTK print dialog so
> it too would be suitable.
I uninstalled acroread, and the problem disappeared. I installed it
again, and still I wasn't able to reproduce the bug. So I'm not sure
whether it depends on acroread. I tried to print various things on
different printers from various applications, but I haven't been able to
reproduce the problem. I'll keep an eye on it and see if this happens again.
Regards,
Antonio
> Another couple of links to rather old bug reports:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=582202
> https://bugzilla.redhat.com/show_bug.cgi?id=498743
>
> Regards,
>
> Brian.
Reply to: