Bug in cups web interface?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug in cups web interface?

Tom Horsley
I used localhost:631 last night to turn on the global setting
to make my printers visible on the network. It said it was
restarting the server, but apparently all it did was stop
the server until I manually did a "systemctl start cups"
in a root window.

Anyone else noticed this? If I wanted to report it
would just "cups" be the right component to use in
bugzilla?
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Bug in cups web interface?

Ed Greshko
On 04/12/18 20:13, Tom Horsley wrote:
> I used localhost:631 last night to turn on the global setting
> to make my printers visible on the network. It said it was
> restarting the server, but apparently all it did was stop
> the server until I manually did a "systemctl start cups"
> in a root window.
>
> Anyone else noticed this? If I wanted to report it
> would just "cups" be the right component to use in
> bugzilla?

It won't fail for me consistently.  Sometimes cupsd fails to restart and sometimes
it  succeeds.

Suggest you check "systemctl status cups" when it fails as well as the journal and
then file the BZ against cups. 


--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.


_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]

signature.asc (235 bytes) Download Attachment