[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#764253: system-config-printer: Creates millions of ppd symlinks



Hi Till,

On 22.10.2014 18:14, Till Kamppeter wrote:
I have forwarded this report to Tim Waugh from Red Hat, original author
of system-config-printer and he has answered me the following:
[...]

Thanks for forwarding this upstream.

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

Yes, this fixes the cups side of the problem.

  * 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

I can confirm that this prevents the infinite loop.
The temporary files are still left behind in /tmp upon failure, but as long as that are not millions, it doesn't matter.

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.

There is a DBus call explicitly starting this service:
method call sender=:1.37 -> dest=org.freedesktop.DBus serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=StartServiceByName
   string "org.fedoraproject.Config.Printing"

This is caused by the scp applet:
/usr/share/system-config-printer/applet.py

If this applet is not running, scp-dbus-service is not started upon printing.

Best regards,
Andreas


Reply to: