https://bugzilla.novell.com/show_bug.cgi?id=857372
https://bugzilla.novell.com/show_bug.cgi?id=857372#c137
--- Comment #137 from Don Hughes 2014-02-27 15:50:06 UTC ---
As a user, printing is just a commodity function, and something that I use
everyday. I do not get any joy out of treaking settings, installing drivers,
and tracking down print filters. I would like to be able to just attach a
printer to the network and have it work, but, unfortunately there are too many
moving parts, and I rely on yast to get things working.
When I print something it is usually because I have some system issue and I
need to print logs, and configuration files, and it is very frustrating to have
to stop working on one problem and figure out why I can not print. And with
every new release a bunch of things break including CUPS and I find that I end
up moving my logs to a Windows machine to print them while I am trying to get
things up and running. How annoying.
Systemd is still a mystery to me where what seem to be minor changes make my
system un-bootable and where I find tracing problems almost impossible. I have
had some systemd issues for over a year that I have spent too much time on
trying to fix on and have just learned to live with them (CUPS being one).
So, if getting remote printing to work again takes creating another bug, then
lets do it.
On the original issue, I now have similar CUPS configuration information in
./sysconfig/cups, ../cups/cupsd.conf, and various /systemd/system/cups.*
files, and when I initially got reports of CUPS listening on a bunch of new
ports, it did not occur to me to look for systemd .socket files. If systemd is
going to bring up various ports, I would expect it to respect the information
in the existing configuration files.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.