[SOLVED] Canon Pixma MG7750 - usb - will scan but not print

[gittiest personITW]

LM19.1 / Cinnamon / Tessa / Newbie (thats me, not the printer)

Hi,
I have a Canon Pixma connected by USB - That can't print but can scan from the computer.
It was working without a problem up till a few days ago, but it doesn't get used everyday so I don't know what stopped it.
When I try to print something, the computer says "printing" but nothing happens with the printer.
If I type
cancel -a
The computer says "cancelling print" - looks normal.

There seems to be the following entries in journalctl, some of which are definitely related to when I try and print and some which may have something to do with it, or may not:

Code: Select all

[Jun 22 00:08:26 Beast5 kernel: xhci_hcd 0000:1d:00.3: Timeout while waiting for setup device command
Jun 22 00:08:31 Beast5 kernel: xhci_hcd 0000:1d:00.3: Timeout while waiting for setup device command
Jun 22 00:08:31 Beast5 kernel: usb 5-1: device not accepting address 5, error -62
Jun 22 00:08:32 Beast5 kernel: usb 5-1: new high-speed USB device number 6 using xhci_hcd
Jun 22 00:08:37 Beast5 kernel: xhci_hcd 0000:1d:00.3: Timeout while waiting for setup device command
Jun 22 00:08:42 Beast5 kernel: xhci_hcd 0000:1d:00.3: Timeout while waiting for setup device command
Jun 22 00:08:42 Beast5 kernel: usb 5-1: device not accepting address 6, error -62
Jun 22 00:08:42 Beast5 kernel: usb usb5-port1: unable to enumerate USB device
Jun 22 00:08:50 Beast5 anacron[5230]: Job `cron.daily' terminated
Jun 22 00:08:50 Beast5 anacron[5230]: Normal exit (1 job run)
Jun 22 00:09:08 Beast5 systemd[1]: dev-disk-by\x2did-usb\x2dCanon_MG7700_series_30086F\x2d0:0.device: Job dev-disk-by\x2did-usb\x2dCanon_MG7700_series_30086F\x2d0:0.device/start timed out.
Jun 22 00:09:08 Beast5 systemd[1]: Timed out waiting for device MG7700_series.
Jun 22 00:09:08 Beast5 systemd[1]: Dependency failed for /mnt/usb-Canon_MG7700_series_30086F-0:0.
Jun 22 00:09:08 Beast5 systemd[1]: mnt-usb\x2dCanon_MG7700_series_30086F\x2d0:0.mount: Job mnt-usb\x2dCanon_MG7700_series_30086F\x2d0:0.mount/start failed with result 'dependency'.
Jun 22 00:09:08 Beast5 systemd[1]: dev-disk-by\x2did-usb\x2dCanon_MG7700_series_30086F\x2d0:0.device: Job dev-disk-by\x2did-usb\x2dCanon_MG7700_series_30086F\x2d0:0.device/start failed with result 'timeout'.
Jun 22 00:10:38 Beast5 kernel: usb 3-2.4: reset high-speed USB device number 3 using xhci_hcd
Jun 22 00:11:04 Beast5 kernel: usb 3-2.4: reset high-speed USB device number 3 using xhci_hcd
Jun 22 00:12:23 Beast5 kernel: usb 3-2.4: reset high-speed USB device number 3 using xhci_hcd
Jun 22 00:13:26 Beast5 kernel: usb 3-2.4: reset high-speed USB device number 3 using xhci_hcd
Jun 22 00:15:01 Beast5 CRON[6091]: pam_unix(cron:session): session opened for user root by (uid=0)
Jun 22 00:15:01 Beast5 CRON[6092]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jun 22 00:15:01 Beast5 CRON[6091]: pam_unix(cron:session): session closed for user root
Jun 22 00:15:13 Beast5 kernel: usb 3-2.4: reset high-speed USB device number 3 using xhci_hcd
Jun 22 00:15:16 Beast5 kernel: usb 3-2.4: reset high-speed USB device number 3 using xhci_hcd
Jun 22 00:15:30 Beast5 kernel: usb 3-2.4: reset high-speed USB device number 3 using xhci_hcd
Jun 22 00:15:39 Beast5 kernel: usb 3-2.4: reset high-speed USB device number 3 using xhci_hcd
Jun 22 00:16:52 Beast5 kernel: usb 3-2.4: reset high-speed USB device number 3 using xhci_hcd
Jun 22 00:17:01 Beast5 CRON[6148]: pam_unix(cron:session): session opened for user root by (uid=0)
Jun 22 00:17:01 Beast5 CRON[6149]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 22 00:17:01 Beast5 CRON[6148]: pam_unix(cron:session): session closed for user root
Jun 22 00:17:19 Beast5 kernel: usb 3-2.4: reset high-speed USB device number 3 using xhci_hcd
Jun 22 00:18:44 Beast5 kernel: usb 3-2.4: reset high-speed USB device number 3 using xhci_hcd
Jun 22 00:20:03 Beast5 dbus-daemon[1104]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.8" (uid=115 pid=1124 comm="avahi-daemon: starting up " label="unconfined") interfac
Jun 22 00:20:03 Beast5 dbus-daemon[1104]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.8" (uid=115 pid=1124 comm="avahi-daemon: starting up " label="unconfined") interfac
Jun 22 00:20:18 Beast5 dbus-daemon[1104]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.8" (uid=115 pid=1124 comm="avahi-daemon: starting up " label="unconfined") interfac
Jun 22 00:20:18 Beast5 dbus-daemon[1104]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.8" (uid=115 pid=1124 comm="avahi-daemon: starting up " label="unconfined") interfac
Jun 22 00:20:32 Beast5 dbus-daemon[1104]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.8" (uid=115 pid=1124 comm="avahi-daemon: starting up " label="unconfined") interfac
Jun 22 00:20:32 Beast5 dbus-daemon[1104]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.8" (uid=115 pid=1124 comm="avahi-daemon: starting up " label="unconfined") interfac
Jun 22 00:21:01 Beast5 dbus-daemon[1104]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.8" (uid=115 pid=1124 comm="avahi-daemon: starting up " label="unconfined") interfac
Jun 22 00:21:01 Beast5 dbus-daemon[1104]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.8" (uid=115 pid=1124 comm="avahi-daemon: starting up " label="unconfined") interfac
Jun 22 00:21:14 Beast5 dbus-daemon[1104]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.8" (uid=115 pid=1124 comm="avahi-daemon: starting up " label="unconfined") interfac
Jun 22 00:21:14 Beast5 dbus-daemon[1104]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.8" (uid=115 pid=1124 comm="avahi-daemon: starting up " label="unconfined") interfac

Also, the entry has dissappeared from "Disks" program but the directory it points to is still there, and the entry is still in fstab unchanged.
I tried mounting it manually with:

Code: Select all

~$ sudo mount /dev/disk/by-id/usb-Canon_MG7700_series_30086F-0:0 /mnt/usb-Canon_MG7700_series_30086F-0:0
mount: /mnt/usb-Canon_MG7700_series_30086F-0:0: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program.

Any ideas are greatly appreciated

[gittiest personITW]

I uninstalled the cnijfilter and reinstalled.
The entry is back in the Disks program, the fstab is completely unchanged, and as far as the computer seems to be concerned, the printer is processing the print command.
I've changed USB cables to known working ones. Still exactly the same result - can scan from printer to computer, but no printing. (start with simple things first).
The Printing Queue comes up as "Processing".
The Printer Properties comes up as "Processing - Rendering completed"
So, the computer is doing its job up till sending the actual command. Is that CUPS or does CUPS only refer to Wifi/network printing?

[carum carvi]

It cant be the usb cable, because it does perform a scan perfectly.

It is compatible with LinuxMint because the printing function did work untill a few days ago.

How long ago did it still work? More than a week or more than 2 weeks? Could an update cause a printer to stop working while it did work perfectly before?

Can you print a test page with a button on the printer, without having to use the computer? Just to check everything is in working order.

[gittiest personITW]

Hi,
It was about a week ago. The Test button / Clean printheads etc all give the same result that the computer is processing or Processing - Rendering completed.
Yes,it could have been an update but don't know.
Another printer went down completely also - of course, you only find this out when you really need it. That one was a network printer (wifi) but reinstalled it with the latest driver. phew!

[carum carvi]

Sorry, but what is unclear to me if you were able to print a testpage with a button located on the printer itself, while disconnected to any computer? Does your printer print colors or black and white text on a test page? Or if you press such a test button on the printer itself doesnt it do anything?

I have googled your error messages. I found out that a kernel update can cause problems, by not recognizing your usb connection anymore. A more experienced forummember should help you out by analyzing those error messages in more detail.

Other possible cause of error; Have you installed other usb devices recently? Have you got other usb devices attached? And how old is your computer? A hardware malfunction of that particular usb connection cant be ruled out either. But your scan function DOES work, which makes that possibility of a hardware malfunction less likely I would think.

[gittiest personITW]

Hi,
Sorry - my bad explanation.

If I press the test button or try to get it to check printheads or attempt to print from an application - nothing happens on the printer itself.
The computer processes the job but nothing happens on the printer.
The only time the computer seems to communicate with the printer is when I type
cancel -a (the printer screen flashes and resets)
or scan from the printer to the computer.

The hardware - motherboard/ram/cpu are all brand new X470 chipset. New M2 drive (system drive).
It could be a kernel update that caused the problem.
If I rollback - would there be issues with security?

[pdc_2]

Canon do a driver for this MG7700 series device

what about installing that driver and evaluating it?

If you go here https://asia.canon/en/support/0100690202/1

and click to download and save what will be cnijfilter2-5.20-1-deb.tar.gz (so it is a generic driver Canon have taken to issuing in recent years)

it should end up in your Downloads directory so if you open a terminal; copy each command and paste it into the terminal one by one

Code: Select all

cd Downloads

Code: Select all

tar -zxvf cnijfilter2-5.20-1-deb.tar.gz 

Code: Select all

cd cnijfilter2-5.20-1-deb

Code: Select all

sudo ./install.sh

and that should install the driver and create an entry in your PRINTERS folder; (seems sensible to delete any existing entry there for the 7700 as you say it is not working ........ before doing the above ...... then you should have only one icon when you run the above commands .......

[gittiest personITW]

Hi pdc,
Thanks for that.
That was the driver I originally used.

I 'uninstalled' the driver and reinstalled it.
That was when it showed back up in Disks program.
Apart from that there is no difference in the function - but yes - definitely worth a go.

[brian_p]

The MG7750 is an AirPrint device. Why bother with drivers when you can have it printing within minutes.

https://wiki.debian.org/QuickPrintQueuesCUPS

[gittiest personITW]

I think you are a print god of some sort brian.
I bow down in your presence and will sacrifice the last remaining unicorn in your name.

Many thanks.
Got it to print and it even shows the ink levels which it never did before.



For other mere mortals - this is how it was done.....

Enabled the wifi on the printer.
Pointed it to the SSID of the router.
Typed in WPA key
Enabled the Bonjour Service on the printer
Went into the Printer utility on LM and Right clicked the printer and chose Properties.
Went to Device URI tab and clicked Change
Under Network Printer, click the correct printer
Select Driverless Printing.
OK