HP Neverstop Laser 1000W recognized but won't print anything

Support Printers
1

I’ll get straight to the point. I own an HP printer (Neverstop Laser 1000W) and been using it for a while now. I have several different machines at home, and all of them can communicate with this printer wirelessly with no issues.
One PC runs Windows 10
Another runs Ubuntu 24.04.1 LTS
And I have this PC of mine, which used to also run the same version of Ubuntu, but recently I switched to Manjaro.

I went with KDE, and the printer was recognized in the GUI, but it couldn’t find any drivers for it. So for the next few hours I tried a few different ones, and every single time when I tried to print a test page, I could hear the printer start up, wait for a few seconds then power down without printing anything.

Since all the other machines could print fine, I went to my other Ubuntu machine and retrieved the PPD file from it, and transferred that over to this PC.
Using that file, the printer also simply started up, did nothing for a few seconds then powered off again.

When I sent a printing job, I checked the logs, here’s what I saw:

In /var/log/cups/page_log

HP_Neverstop_Laser_100x tib 23 [30/Nov/2024:13:09:31 +0100] total 1 - localhost Untitled 1 - -

In /var/log/cups/access_log

localhost - - [30/Nov/2024:13:09:31 +0100] "POST /printers/HP_Neverstop_Laser_100x HTTP/1.1" 200 224 Create-Job successful-ok
localhost - - [30/Nov/2024:13:09:31 +0100] "POST /printers/HP_Neverstop_Laser_100x HTTP/1.1" 200 10876 Send-Document successful-ok

In /var/log/cups/error_log was different, as I never actually got an error message DURING printing, but the file contained the following last few lines:

W [30/Nov/2024:12:21:34 +0100] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103
W [30/Nov/2024:12:21:34 +0100] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name is not activatable
W [30/Nov/2024:12:21:34 +0100] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name is not activatable
W [30/Nov/2024:12:21:34 +0100] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name is not activatable
E [30/Nov/2024:13:04:18 +0100] [CGI] ippfind (PID 7806) stopped with status 2!

Also keep in mind that the printer works perfectly fine, I can print anything from any other PC in the house, even from my phone. It’s not a hardware fault.

And that’s where I am currently. If anyone is able to point me in the right direction I’d be very happy! Thank you!

2

Hi @TibAverus,

According to:

The printer uses the AirPrintTM standard:

https://i.imgur.com/oISYoMq.png

And on All Supported Printer Models | hp's Developer Portal it seems to be supported by the normal hplip driver/library from version 3.19.6 onwards.

So, I don’t really know what to say, except to make sure it’s using the AirPrintTM standard.

3

I’ve attempted to install hplip before, and similar to last time, the install script fails because I cannot satisfy some dependencies, namely:

warning: Missing REQUIRED dependency: python3-pyqt4 (PyQt 4- Qt interface for Python (for Qt version 4.x))
warning: This installer cannot install 'python3-pyqt4' for your distro/OS and/or version.
error: Installation cannot continue without this dependency. Please manually install this dependency and re-run this installer.

Furthermore, the current driver I’m using appears to be showing that it should be using AirPrint, but I’m not entirely sure.
Since I cannot paste in a screenshot, my driver file contains, among many other lines, the following:

*NickName: "HP Printer, driverless, 2.0.0"
*APSupplies: "https://NPI157870.local/hp/device/info_config_AirPrint.html?tab=Networking&menu=AirPrintStatus"
4

I think if you’re trying to print over wifi…hmm, no wait, maybe this isn’t that hard. Make sure the avahi daemon is enabled and started before trying to print.

systemctl status avahi-daemon.{service,socket}
5

Checking the service status at first gave me the following output

○ avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; disabled; preset: disabled)
     Active: inactive (dead)
TriggeredBy: ○ avahi-daemon.socket

○ avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.socket; disabled; preset: disabled)
     Active: inactive (dead)
   Triggers: ● avahi-daemon.service
     Listen: /run/avahi-daemon/socket (Stream)

After enabling it and checking it’s status a few moments later, I got the following:

○ avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; preset: disabled)
     Active: inactive (dead)
TriggeredBy: ○ avahi-daemon.socket

○ avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.socket; enabled; preset: disabled)
     Active: inactive (dead)
   Triggers: ● avahi-daemon.service
     Listen: /run/avahi-daemon/socket (Stream)

Printing unfortunately still doesn’t work right, and will only start up the printer, but won’t actually print out anything.

6

How did you enabled it?

Did you try this?
sudo systemctl enable --now avahi-daemon.service

7

And make sure cups is started and enabled:

sudo systemctl enable --now cups.service
8

Looks like I tried to enable it incorrectly, this seems to have done it!

● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; preset: disabled)
     Active: active (running) since Sat 2024-11-30 14:38:56 CET; 1min 38s ago
 Invocation: 8bee7107980c44399ad606fa7f34d8f6
TriggeredBy: ● avahi-daemon.socket
   Main PID: 19748 (avahi-daemon)
     Status: "avahi-daemon 0.8 starting up."
      Tasks: 2 (limit: 76724)
     Memory: 1.2M (peak: 1.6M)
        CPU: 6ms
     CGroup: /system.slice/avahi-daemon.service
             ├─19748 "avahi-daemon: running [tib-manjaro.local]"
             └─19749 "avahi-daemon: chroot helper"

nov 30 14:38:56 tib-manjaro avahi-daemon[19748]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
nov 30 14:38:56 tib-manjaro avahi-daemon[19748]: New relevant interface lo.IPv6 for mDNS.
nov 30 14:38:56 tib-manjaro avahi-daemon[19748]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
nov 30 14:38:56 tib-manjaro avahi-daemon[19748]: New relevant interface lo.IPv4 for mDNS.
nov 30 14:38:56 tib-manjaro avahi-daemon[19748]: Network interface enumeration completed.
nov 30 14:38:56 tib-manjaro avahi-daemon[19748]: Registering new address record for fe80::b0d7:bf9e:2721:1628 on enp5s0.*.
nov 30 14:38:56 tib-manjaro avahi-daemon[19748]: Registering new address record for 192.168.50.230 on enp5s0.IPv4.
nov 30 14:38:56 tib-manjaro avahi-daemon[19748]: Registering new address record for ::1 on lo.*.
nov 30 14:38:56 tib-manjaro avahi-daemon[19748]: Registering new address record for 127.0.0.1 on lo.IPv4.
nov 30 14:38:57 tib-manjaro avahi-daemon[19748]: Server startup complete. Host name is tib-manjaro.local. Local service cookie is 3493677415.

● avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.socket; enabled; preset: disabled)

Furthermore, I also made sure cups.service is enabled

● cups.service - CUPS Scheduler
     Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; preset: disabled)
     Active: active (running) since Sat 2024-11-30 12:21:34 CET; 2h 21min ago
 Invocation: 0e059f78946d47eda1a24305caa8b50d
TriggeredBy: ● cups.path
             ● cups.socket
       Docs: man:cupsd(8)
   Main PID: 691 (cupsd)
     Status: "Scheduler is running..."
      Tasks: 2 (limit: 76724)
     Memory: 149M (peak: 309.4M)
        CPU: 1.706s
     CGroup: /system.slice/system-cups.slice/cups.service
             ├─ 691 /usr/bin/cupsd -l
             └─7127 /usr/lib/cups/notifier/dbus dbus://

nov 30 12:21:34 tib-manjaro systemd[1]: Starting CUPS Scheduler...
nov 30 12:21:34 tib-manjaro systemd[1]: Started CUPS Scheduler.

However, even with these services enabled, printing still fails. The printer seemingly gets some kind of request, starts up, does nothing, then goes back to stand-by mode.

I have also did a full reboot of the machine, making sure these services were enabled even after that, but it didn’t help.

1 Like
9

I do not have a lot of experience with CUPS. I got my printer working, but it’s driverless specifically researched and bought 'cuz of that, so it was actually very easy. So sorry, we’ve reached the end of my knowledge.

10

Thank you for the tips so far! I’ll keep trying and if I do find a solution, I’ll post it here in case anyone else runs into the same thing.

1 Like
11

Have a look here:

https://wiki.archlinux.org/title/CUPS#Printer_drivers

and here, as well:

1 Like
12

After some back and forth and looking around online resources, the link provided by @Mirdarthos had the answer to my issue!

From here, running the following command:

pamac build hplip-plugin

Then doing a full reboot of the machine added the correct driver to the list of available drivers, which wasn’t present before. The driver that worked in my case was the following:
HP Neverstop Laser 100x, driverless, cups-filters 2.0.1

Hope this helps anyone in the future, and thank you for pointing me in the right direction!

2 Likes