Wireless Printing

[Germ]

Fully updated Cauldron x86-64

I have a Canon MG3600 series printer that works perfectly on MGA8. Wireless printing.

I go through the setup in Cauldron and get this error at the end:

Code: Select all

CUPS server error
There was an error during the CUPS operation:'server-error-internal-error'

I've enabled zero-conf and printer discovery in the firewall. Any idea what I'm missing?

[doktor5000]

Might help if you could post the output as root of of

Code: Select all

systemctl status "cups*" -al -n25

[Germ]

Code: Select all

[germ@localhost ~]$ systemctl status "cups*" -al -n25
● cups.socket - CUPS Scheduler
     Loaded: loaded (/usr/lib/systemd/system/cups.socket; enabled; preset: enabled)
     Active: active (running) since Sun 2023-06-25 12:38:58 CDT; 4h 56min left
   Triggers: ● cups.service
     Listen: /run/cups/cups.sock (Stream)
     CGroup: /system.slice/cups.socket

Warning: some journal files were not opened due to insufficient permissions.

● cups.path - CUPS Scheduler
     Loaded: loaded (/usr/lib/systemd/system/cups.path; enabled; preset: enabled)
     Active: active (running) since Sun 2023-06-25 12:38:58 CDT; 4h 56min left
   Triggers: ● cups.service

Warning: some journal files were not opened due to insufficient permissions.

● cups.service - CUPS Scheduler
     Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; preset: disabled)
     Active: active (running) since Sun 2023-06-25 12:39:16 CDT; 4h 56min left
TriggeredBy: ● cups.path
             ● cups.socket
       Docs: man:cupsd(8)
   Main PID: 4208 (cupsd)
     Status: "Scheduler is running..."

[doktor5000]

You're missing the essential parts, the log excerpts:

the output as root

[Germ]

Sorry, missed that...

Code: Select all

[root@localhost ~]# systemctl status "cups*" -al -n25
● cups.socket - CUPS Scheduler
     Loaded: loaded (/usr/lib/systemd/system/cups.socket; enabled; preset: enabled)
     Active: active (running) since Sun 2023-06-25 12:38:58 CDT; 4h 41min left
   Triggers: ● cups.service
     Listen: /run/cups/cups.sock (Stream)
     CGroup: /system.slice/cups.socket

Jun 25 12:38:58 localhost.localdomain systemd[1]: Listening on cups.socket.

● cups.path - CUPS Scheduler
     Loaded: loaded (/usr/lib/systemd/system/cups.path; enabled; preset: enabled)
     Active: active (running) since Sun 2023-06-25 12:38:58 CDT; 4h 41min left
   Triggers: ● cups.service

Jun 25 12:38:58 localhost.localdomain systemd[1]: Started cups.path.

● cups.service - CUPS Scheduler
     Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; preset: disabled)
     Active: active (running) since Sun 2023-06-25 12:39:16 CDT; 4h 41min left
TriggeredBy: ● cups.path
             ● cups.socket
       Docs: man:cupsd(8)
   Main PID: 4208 (cupsd)
     Status: "Scheduler is running..."

Doesn't look much different...

[doktor5000]

That is after you already tried to configure the printer via drakconf ?

[Germ]

Yes. I tried drakconf first and then localhost:631 when drakconf didn't configure it.

[doktor5000]

When you tried the CUPS web frontend localhost:631 - what selections do you get for your network printer, what did you choose and what was the error message there ?

[Germ]

When I tried the CUPS front end I got no errors. The printer shows up on the system, I get the print dialog, it just refuses to print.

[benmc]

were you offered more than one option for the driver?

or, did the system only offer a driverless setup?

[Germ]

I had three options. Tried all three but none worked. Driverless, gutenprint, and gutenprint-simplified. Same printer works on USB. I need to boot the mga8 and see what driver it uses, but like I said in my original post it works just fine in mageia 8. Also works fine in cauldron on USB.

[doktor5000]

Well for network printers some other packages could interfere, e.g. ipp-usb could be one such issue, see e.g. https://bugs.mageia.org/show_bug.cgi?id=31623

What you could also do is manually create a printer queue, see e.g. https://forums.linuxmint.com/viewtopic.php?t=374986 (the later parts with lpadmin). Maybe that yields some more details what goes wrong.
Or on the cups admin site enable debug logging, maybe that provides some more details.

It might also help to check the journal logs (journalctl -ab) around the time you tried to add a printer and post it here or check yourself if maybe there's something that could be related to the internal server error from cups.

[Germ]

OK, I'll give that a try. Thanks.