Created attachment 698099 [details] troubleshoot.txt via GUI (for cups) Description of problem: This bug is related to Bug 821237 - "[CUPS usb] Canon PIXMA MP280 doesn't work" and to Bug 847923 Got MP280 to work (F15-F17) but when upgraded to F18 have problems, once again. The scanner works via "scangearmp" but the printer NOT. I try to print something & get message that it has been printed, when it hasn't been processed. Interestingly, the printer DOES work with a downloaded (specially formatted) img "raw.print" - which I downloaded from https://bugzilla.redhat.com/attachment.cgi?id=604971 --> via "Bug 847923" (comment 12: Jiri Popelka) Version-Release number of selected component (if applicable): cups-libs-1.5.4-20.fc18.i686 cups-devel-1.5.4-20.fc18.i686 cups-1.5.4-20.fc18.i686 How reproducible: Steps to Reproduce: 1. try to print 2. 3. Actual results: error - no print Expected results: printed doc Additional info: ... 'error_log': ['E [16/Feb/2013:08:50:43 +0100] Returning IPP client-error-not-possible for Cancel-Job (ipp://localhost/jobs/275) from localhost', (see troubleshoot.txt - attached) ******************************************************************* there was a problem I noted on boot screen with systemd udev rules: SYSFS being deprecated to ATTRS : changed SYSFS to ATTRS in /etc/udev/rules.d/80-canon_mfp.rules and removed the "#" in front of "MP280 series" ****************************** # 80-canon_mfp.rules ACTION!="add", GOTO="canon_mfp_end" SUBSYSTEM=="usb_device", GOTO="canon_mfp_start" SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", GOTO="canon_mfp_start" GOTO="canon_mfp_end" LABEL="canon_mfp_start" ... MP280 series ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="1746", MODE="666" #MP495 series ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="1747", MODE="666" #MG5100 series ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="1748", MODE="666"
(In reply to comment #0) > Created attachment 698099 [details] > troubleshoot.txt via GUI (for cups) 'printer-make-and-model': u'Canon MP280 series Ver.3.40', This looks like you're using the Canon printer driver, which is not part of Fedora, therefore we can't help with it. > Description of problem: > Got MP280 to work (F15-F17) but when upgraded to F18 have problems, once > again. It's a strange beast this MP280 anyway ;-) > Interestingly, the printer DOES work with a downloaded (specially formatted) > img > "raw.print" - which I downloaded from > https://bugzilla.redhat.com/attachment.cgi?id=604971 --> via "Bug 847923" > (comment 12: Jiri Popelka) That was created using the gutenprint driver so there's a solid chance that the printer will work when you switch (for example in system-config-printer, double click on the printer and press 'Change...' Make and Model) to gutenprint. > /etc/udev/rules.d/80-canon_mfp.rules This file probably came from the Canon proprietary driver.
Also please post output of su -c "lpinfo -l -v" | grep 280
(In reply to comment #1) > ... the printer will work when you switch to gutenprint If that doesn't help try instructions from bug #873123, comment #0
(In reply to comment #2) > Also please post output of > su -c "lpinfo -l -v" | grep 280 [jack@localhost ~]$ su -c "lpinfo -l -v" | grep 280 Password: make-and-model = Canon MP280 series Device: uri = usb://Canon/MP280%20series?serial=A28F16&interface=1 info = Canon MP280 series make-and-model = Canon MP280 series device-id = MFG:Canon;CMD:BJL,BJRaster3,BSCCe,IVEC,IVECPLI;SOJ:TXT01;MDL:MP280 series;CLS:PRINTER;DES:Canon MP280 series;VER:1.040;STA:10;FSI:00;HRI:EU;MSI:DAT,E3,HASF;PDR:4;PSE:LFPE25423;
>> /etc/udev/rules.d/80-canon_mfp.rules >This file probably came from the Canon proprietary driver. Didn't have this problem till updated to F18... ****************************************************** I'll try changing to gutenprint, now... there is no "gutenprint" listed in db... switched to Canon PIXMA MP280 - CUPS+Gutenprint v5.2.9 Simplified Works... thanks!
I want to mark this "BUG" as solved (i.e. I'm sure it will help someone who uses Linux & MP280). How do you do that -- without marking the "status" as "CLOSED" ???
I'm not aware of any such option, however you can change the name of the bug as I'm doing right now.