Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: CUPS no longer starts at boot after update

  1. #1
    Join Date
    Jun 2008
    Location
    Hessia
    Posts
    303

    Question CUPS no longer starts at boot after update

    How can I ensure that CUPS is started during the boot sequence?

    YaST2 -> Services Manager shows the two entries cups and cupsd as active. However, after booting is completed, the list of available printers in applications is empty, and the URL localhost:631 just returns "not found".

    However, entering:
    Code:
    > sudo systemctl start cups
    >
    at a console and then waiting 5 seconds fixes the problem.


    The problem appeared first after a usual update (YaST2 -> Software -> Update All Packages (if newer)) which was done around mid or late January on my laptop. The laptop is not connected to any printers by itself, but is used in various networks where printers are available.

    About a week ago, I updated my wife's laptop, and the same problem occurred. Again systemctl start cups fixes the issue, but this is too tedious for her to accept, so I started to investigate now. My wife's laptop just uses the default repositories + packman.

    An update on Friday fixed the issue for me (worked on several attempts), but updating both machines on Monday (10. Feb 2014) caused both machines to fail again (several attempts).

    I found this thread here:which seems quite related, but it talks about a CUPS server, and I do not understand enough whether it applies to a normal CUPS client running on a laptop in order to print wirelessly, and what I should do as a consequence now.

  2. #2
    Join Date
    Sep 2012
    Posts
    7,090

    Default Re: CUPS no longer starts at boot after update

    Let's start with output of "systemctl status cups cupsd" immediately after boot.

  3. #3
    Join Date
    Jun 2008
    Location
    Hessia
    Posts
    303

    Default Re: CUPS no longer starts at boot after update

    Directly after booting is finished, with no connection to localhost:631 possible:
    Code:
    # systemctl status cups cupsdcups.service - CUPS Printing Service
       Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
       Active: inactive (dead)
    
    
    
    
    cupsd.service
       Loaded: not-found (Reason: No such file or directory)
       Active: inactive (dead)
    
    
    #
    Then I enter:
    Code:
    # systemctl start cups
    # systemctl status cups cupsd
    cups.service - CUPS Printing Service
       Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
       Active: active (running) since Tue 2014-02-11 18:10:40 CET; 2s ago
     Main PID: 1901 (cupsd)
       CGroup: /system.slice/cups.service
               └─1901 /usr/sbin/cupsd -f
    
    
    Feb 11 18:10:40 machine.url.net systemd[1]: Started CUPS ...
    Feb 11 18:10:40 machine.url.net cupsd[1901]: No limit for...
    Feb 11 18:10:40 machine.url.net cupsd[1901]: No limit for...
    Feb 11 18:10:40 machine.url.net cupsd[1901]: No limit for...
    Feb 11 18:10:40 machine.url.net cupsd[1901]: No limit for...
    Feb 11 18:10:40 machine.url.net cupsd[1901]: No limit for...
    Feb 11 18:10:40 machine.url.net cupsd[1901]: No JobPrivat...
    Feb 11 18:10:40 machine.url.net cupsd[1901]: No JobPrivat...
    Feb 11 18:10:40 machine.url.net cupsd[1901]: No Subscript...
    Feb 11 18:10:40 machine.url.net cupsd[1901]: No Subscript...
    
    
    cupsd.service
       Loaded: not-found (Reason: No such file or directory)
       Active: inactive (dead)
    
    
    Hint: Some lines were ellipsized, use -l to show in full.
    #
    ...and printing over the network works fine again (no local printer connected).
    (I edited the URL above from our real one to "machine.url.net")

  4. #4
    Join Date
    Nov 2010
    Location
    Texas, USA
    Posts
    106

    Default Re: CUPS no longer starts at boot after update

    I also have this issue (OS 13.1 x64, KDE).

    I've just gotten used to manually restarting "cupsd" any time I restart the machine
    so my printers will work again.

    Code:
    systemctl restart cupsd.service

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,695
    Blog Entries
    1

    Default Re: CUPS no longer starts at boot after update

    Hi STurtle

    It's a known problem (and especially affects those relying on printing over networks due to socket-activation issues) See this long thread:

    https://forums.opensuse.org/showthre...r-after-update

    and bug report

    https://bugzilla.novell.com/show_bug.cgi?id=857372#c75

    You have two choices currently: Modify cups.socket as suggested in thread, or update CUPS from OBS printing repo (which modifies cups.service not to use cups.socket any longer). I'm currently using last option (with client and CUPS server).

  6. #6
    Join Date
    Nov 2010
    Location
    Texas, USA
    Posts
    106

    Default Re: CUPS no longer starts at boot after update

    Disabling cups.socket (and rebooting) did not help.

    All of the printers worked under 13.1 until a recent update. I don't
    print often so I'm not sure exactly which update caused the problem.
    I just noticed it yesterday.

    I don't have much time to trouble shoot, so simply restarting cupsd.service
    whenever I (very seldom) restart the machines is a acceptable workaround.

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,695
    Blog Entries
    1

    Default Re: CUPS no longer starts at boot after update

    Quote Originally Posted by xlis View Post
    Disabling cups.socket (and rebooting) did not help.
    No, you don't just disable cups.socket as cups.service currently relies on it. The update from the OBS repo modifies cups.service and socket-activation is no longer used.

    All of the printers worked under 13.1 until a recent update. I don't
    print often so I'm not sure exactly which update caused the problem.
    I just noticed it yesterday.
    It's all covered in the thread I linked to and the corresponding bug rpeort.

    I don't have much time to trouble shoot, so simply restarting cupsd.service
    whenever I (very seldom) restart the machines is a acceptable workaround.
    That workaround may be okay for you, but not for those relying on printing in network environments, including CUPS servers.

  8. #8
    Join Date
    Nov 2010
    Location
    Texas, USA
    Posts
    106

    Default Re: CUPS no longer starts at boot after update

    I'm not discouraging others from using the OBS version.

    For me, the manual workaround is no problem. I reboot maybe once a month.

    Once an official fix is in the standard Update repos I'll pick it up.

    If I install from OBS then I have to keep monitoring when an official fix
    is released so I can remove the OBS version and get the official version.
    It's a personal thing, but I don't usually use any OBS repos unless it is
    to resolve a system crash issue.

    Thanks for the info.

  9. #9
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,695
    Blog Entries
    1

    Default Re: CUPS no longer starts at boot after update

    Whatever works for you.

  10. #10
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    4,029

    Default Re: CUPS no longer starts at boot after update

    Quote Originally Posted by xlis View Post
    For me, the manual workaround is no problem. I reboot maybe once a month.
    You could also create a small script containing the command and have it automatically run at login.

    First, write the script and place it where you have execute permissions (/usr/bin, for example).

    To have it run at login:

    Configure Desktop => Startup and Shutdown

    Add Script

    Now when you login, it is done for you.
    "Take a Walk on a Sunny Day, Greet everyone along the way, and Make Somebody Smile, Today"
    Gerry Jack Macks"Walk On A Sunny Day" GerryJackMacks.net

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •