Re: Bug#764253: system-config-printer: Creates millions of ppd symlinks
I have forwarded this report to Tim Waugh from Red Hat, original author
of system-config-printer and he has answered me the following:
----------
> can you check this ppdcache.py problem mentioned here?
I've committed a change which should stop the looping by failing the
call on IOError.
https://git.fedorahosted.org/cgit/system-config-printer.git/commit/?h=1.4.x&id=9a81dd1de3afaf30eec92045429029103823b577
> And why is scp-dbus-service doing something when a job is printed?
You're in a better position to find that out. It doesn't do that for me.
Run "scp-dbus-service --debug" before printing, and see which D-Bus call
it receives. Or watch dbus-monitor --session.
By the way, you know about CUPS STR #4500, right..?
https://cups.org/str.php?L4500
----------
For the two bugs you mentioned there are fixes now:
> Thus I think there are two bugs here:
> * cups should not create files with wrong permissions in /etc/cups/ppd
CUPS STR #4500: https://cups.org/str.php?L4500
> * scp-dbus-service should not start an infinite loop creating millions
> of symlinks in /tmp just because the permissions in /etc/cups/ppd
> are wrong
https://git.fedorahosted.org/cgit/system-config-printer.git/commit/?h=1.4.x&id=9a81dd1de3afaf30eec92045429029103823b577
The only strange thing is that scp-dbus-service gets triggered by simply
printing. So can you please try what Tim suggests:
----------
Run "scp-dbus-service --debug" before printing, and see which D-Bus call
it receives. Or watch dbus-monitor --session.
----------
and post your results here? Thanks.
Till
Reply to: