Siduction Forum > Hardware - Support

[EN] "Filter failed"

<< < (2/3) > >>

lanig:
Thanks for the answers.
The Canon installation script does an "apt update" and installs what is necessary. I suppose that all the cups packages are installed. Same answer for the firmware.

I have tried to change the driver to LPB 112 but same result.
If I try to clean the printer I got the message

--- Code: ---Unsupported document-format "application/vnd.cups-command".
--- End code ---

--- Code: --- journalctl -b | grep cups
[...]
mars 21 13:26:18 logodenn snapd[1032]: services.go:1103: RemoveSnapServices - disabling snap.cups.cupsd.service
mars 21 13:26:18 logodenn snapd[1032]: services.go:1103: RemoveSnapServices - disabling snap.cups.cups-browsed.service
mars 21 13:26:18 logodenn systemd[1]: run-snapd-ns-cups.mnt.mount: Deactivated successfully.
mars 21 13:26:18 logodenn systemd[1]: snap-cups-1024.mount: Deactivated successfully.
mars 21 13:27:35 logodenn systemd[1]: Stopping cups-browsed.service - Make remote CUPS printers available locally...
mars 21 13:27:35 logodenn systemd[1]: cups-browsed.service: Deactivated successfully.
mars 21 13:27:35 logodenn systemd[1]: Stopped cups-browsed.service - Make remote CUPS printers available locally.
mars 21 13:27:35 logodenn systemd[1]: Stopping cups.service - CUPS Scheduler...
mars 21 13:27:35 logodenn systemd[1]: cups.service: Deactivated successfully.
mars 21 13:27:35 logodenn systemd[1]: Stopped cups.service - CUPS Scheduler.
mars 21 13:27:35 logodenn systemd[1]: cups.service: Consumed 42.870s CPU time, 275.0M memory peak, 288.0K memory swap peak.
mars 21 13:27:35 logodenn systemd[1]: cups.path: Deactivated successfully.
mars 21 13:27:35 logodenn systemd[1]: Stopped cups.path - CUPS Scheduler.
mars 21 13:27:35 logodenn systemd[1]: Stopping cups.path - CUPS Scheduler...
mars 21 13:27:35 logodenn systemd[1]: Started cups.path - CUPS Scheduler.
mars 21 13:27:35 logodenn systemd[1]: cups.socket: Deactivated successfully.
mars 21 13:27:35 logodenn systemd[1]: Closed cups.socket - CUPS Scheduler.
mars 21 13:27:35 logodenn systemd[1]: Stopping cups.socket - CUPS Scheduler...
mars 21 13:27:35 logodenn systemd[1]: Listening on cups.socket - CUPS Scheduler.
mars 21 13:27:35 logodenn systemd[1]: Starting cups.service - CUPS Scheduler...
mars 21 13:27:35 logodenn systemd[1]: Started cups.service - CUPS Scheduler.
mars 21 13:27:35 logodenn systemd[1]: Started cups-browsed.service - Make remote CUPS printers available locally.
mars 21 13:27:55 logodenn kernel: audit: type=1400 audit(1711024075.964:464): apparmor="DENIED" operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=130098 comm="usb" capability=12  capname="net_admin"
mars 21 13:27:55 logodenn kernel: audit: type=1400 audit(1711024075.988:465): apparmor="DENIED" operation="open" class="file" profile="/usr/lib/cups/backend/cups-pdf" name="/etc/cups/" pid=130117 comm="cups-pdf" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
mars 21 13:28:22 logodenn kernel: audit: type=1400 audit(1711024102.154:466): apparmor="DENIED" operation="open" class="file" profile="/usr/lib/cups/backend/cups-pdf" name="/etc/cups/" pid=130174 comm="cups-pdf" requested_mask="r" denied_mask="r" fsuid=0 ouid=0


--- End code ---

Could it be an app armor problem ?

eriefisher:
Do you have libcups-filters installed? Should be a t64 version now.

lanig:
I think so :

--- Code: ---dpkg -l  |grep cups |grep filter
ii  cups-filters                                             1.28.17-3.1+b1                            amd64        OpenPrinting CUPS Filters - Main Package
ii  cups-filters-core-drivers                                1.28.17-3.1+b1                            amd64        OpenPrinting CUPS Filters - Driverless printing
ii  libcupsfilters1t64:amd64                                 1.28.17-3.1+b1                            amd64        OpenPrinting CUPS Filters - Shared library

--- End code ---

eriefisher:
I'm not sure what to add at this point. Possibly a firewall issue but you say the printer is detected automatically so this may not be the case.

hendrikL:
If it works as a driverless printer, then there is no need to install extra printing software.
What you can try is to download our latest, in this case kde, testimage, and try to print a testfile. If it's working, then something is broken or miss configured on your system.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version
Powered by Advanced Topic Prefix Pro
Powered by SMFPacks WYSIWYG Editor