Page 1 of 3 123 LastLast
Results 1 to 10 of 27

Thread: Leap. Cups not working after upgrade from 13.1

  1. #1
    Join Date
    Jan 2009
    Location
    Taft, Republic of California. UTC -8
    Posts
    1,474

    Default Leap. Cups not working after upgrade from 13.1

    Pretty fresh upgrade to Leap 42.1 from 13.1 all is working well except printing over network.
    HP printers on Network. They don't show up in desktop settings and will not print from applications unless CUPS is restarted/started.
    I go into yast printers and the printers show up there and the configuration system restarts cups and all is well.
    HP manager is sitting happily in system tray.
    I can also just do
    service cups restart
    after a reboot and the printers are accessible.
    It seems CUPS is not starting or is starting before the network is up possibly.

    Steps I've taken so far. Uninstalled printers and all HP services in yast. Then added everything back via yast printer setup after a reboot.
    Googled for this problem in Leap.
    Seems I need to tell CUPS to start or Start at the right time.
    How do I accomplish this?

    This is Wife's machine and I don't want her to have to jump through any hoops just to print understandably and I can't be here all the time to start/restart CUPS manually.
    Tumbleweed

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,714
    Blog Entries
    1

    Default Re: Leap. Cups not working after upgrade from 13.1

    I wonder if you have cups.service enabled?

    Code:
    systemctl status cups
    If necessary, do
    Code:
    systemctl enable cups
    Code:
    systemctl start cups

  3. #3
    Join Date
    Jan 2009
    Location
    Taft, Republic of California. UTC -8
    Posts
    1,474

    Default Re: Leap. Cups not working after upgrade from 13.1

    From a fresh boot I did
    Code:
    linux-jf72:/home/ann # systemctl status cups
    cups.service - CUPS Printing Service
       Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
       Active: inactive (dead)
    
    
    No idea how to proceed from here.
    How to I make it boot in a live active mode?
    Tumbleweed

  4. #4
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,714
    Blog Entries
    1

    Default Re: Leap. Cups not working after upgrade from 13.1

    I'm a little suspicious of your upgrade. Can you explain how you did this?

    Can you post the following?
    Code:
    cat /usr/lib/systemd/system/cups.service

  5. #5
    Join Date
    Jan 2009
    Location
    Taft, Republic of California. UTC -8
    Posts
    1,474

    Default Re: Leap. Cups not working after upgrade from 13.1

    linux-jf72:/home/ann # cat /usr/lib/systemd/system/cups.service
    [Unit]
    Description=CUPS Printing Service
    After=network.target

    [Service]
    ExecStart=/usr/sbin/cupsd -f

    [Install]
    WantedBy=multi-user.target
    Tumbleweed

  6. #6
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,714
    Blog Entries
    1

    Default Re: Leap. Cups not working after upgrade from 13.1

    Okay, that looks as it should be.
    Code:
    systemctl restart cups
    Code:
    systemctl status cups
    Report back with output from last command

  7. #7
    Join Date
    Jan 2009
    Location
    Taft, Republic of California. UTC -8
    Posts
    1,474

    Default Re: Leap. Cups not working after upgrade from 13.1

    Code:
    linux-jf72:/home/ann # systemctl status cups
    cups.service - CUPS Printing Service
       Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
       Active: active (running) since Wed 2015-12-16 15:49:49 PST; 21s ago
     Main PID: 2680 (cupsd)
       CGroup: /system.slice/cups.service
               └─2680 /usr/sbin/cupsd -f
    
    Tumbleweed

  8. #8
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,714
    Blog Entries
    1

    Default Re: Leap. Cups not working after upgrade from 13.1

    That is as expected as well. It's not clear to me why it doesn't start at boot. Once the network.target has been reached, all should be good

    That can be verified with
    Code:
    systemctl list-units -t target
    Code:
    systemctl status network.target
    When you next reboot, check
    Code:
    systemctl is-failed cups.service

  9. #9
    Join Date
    Jan 2009
    Location
    Taft, Republic of California. UTC -8
    Posts
    1,474

    Default Re: Leap. Cups not working after upgrade from 13.1

    Sorry.I'm just getting back to this. Got sick and had other stuff get in way.

    Code:
    linux-jf72:/home/ann # systemctl list-units -t target
    UNIT                 LOAD   ACTIVE SUB    DESCRIPTION
    basic.target         loaded active active Basic System
    cryptsetup.target    loaded active active Encrypted Volumes
    getty.target         loaded active active Login Prompts
    graphical.target     loaded active active Graphical Interface
    local-fs-pre.target  loaded active active Local File Systems (Pre)
    local-fs.target      loaded active active Local File Systems
    multi-user.target    loaded active active Multi-User System
    network.target       loaded active active Network
    nss-lookup.target    loaded active active Host and Network Name Lookups
    paths.target         loaded active active Paths
    remote-fs-pre.target loaded active active Remote File Systems (Pre)
    remote-fs.target     loaded active active Remote File Systems
    slices.target        loaded active active Slices
    sockets.target       loaded active active Sockets
    sound.target         loaded active active Sound Card
    swap.target          loaded active active Swap
    sysinit.target       loaded active active System Initialization
    time-sync.target     loaded active active System Time Synchronized
    timers.target        loaded active active Timers
    
    LOAD   = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB    = The low-level unit activation state, values depend on unit type.
    
    

    Code:
    linux-jf72:/home/ann # systemctl status network.target
    network.target - Network
       Loaded: loaded (/usr/lib/systemd/system/network.target; static)
       Active: active since Tue 2015-12-22 08:55:45 PST; 5min ago
         Docs: man:systemd.special(7)
               http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget
    
    
    Code:
    linux-jf72:/home/ann # systemctl is-failed cups.service
    unknown 
    
    Tumbleweed

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,714
    Blog Entries
    1

    Default Re: Leap. Cups not working after upgrade from 13.1

    Quote Originally Posted by FlameBait View Post
    Sorry.I'm just getting back to this. Got sick and had other stuff get in way.
    No worries....stuff happens....

    Code:
    linux-jf72:/home/ann # systemctl is-failed cups.service
    unknown 
    
    This is unusual - it means that CUPS was stopped legitimately by some other process for some reason. I can't think what though...

    It might be useful to examine the journal log for cups-relate messages perhaps. Reboot, then observe the following
    Code:
    journalctl -u cups
    Last edited by deano_ferrari; 22-Dec-2015 at 14:53.

Page 1 of 3 123 LastLast

Posting Permissions

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