<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Rolf,<br>
<br>
regarding the scanner buttons: the MG6300 matches the MG6200. This
would make the patch as simple as this:<code></code><code></code><br>
<br>
diff --git a/backend/pixma_mp150.c b/backend/pixma_mp150.c<br>
index 494c23e..febd06c 100644<br>
--- a/backend/pixma_mp150.c<br>
+++ b/backend/pixma_mp150.c<br>
@@ -918,7 +918,7 @@ handle_interrupt (pixma_t * s, int timeout)<br>
* oo: original<br>
* tt: target<br>
* poll event with 'scanimage -A' */<br>
- if (s->cfg->pid == MG6200_PID)<br>
+ if (s->cfg->pid == MG6200_PID || s->cfg->pid ==
MG6300_PID)<br>
/* button no. in buf[7]<br>
* size in buf[10] 01=A4; 02=Letter; 08=10x15; 09=13x18;
0b=auto<br>
* format in buf[11] 01=JPEG; 02=TIFF; 03=PDF; 04=Kompakt-PDF<br>
<br>
<br>
Regarding the USB connectivity error: it occurred again today and
I sort of believe it was caused by a xsane. I did noticed the USB
connection name changed when the issue occurred. When it works,
the name is 'pixma:04A91765_20A814', when there are issues the
name changes to 'pixma:04A91765':<br>
<br>
With the connection issue:<br>
$ scanimage -L<br>
device `v4l:/dev/video0' is a Noname UVC Camera (046d:0825)
virtual device<br>
device `pixma:MG6300_canon-printer' is a CANON Canon PIXMA
MG6300 multi-function peripheral<br>
device `pixma:04A91765' is a CANON Canon PIXMA MG6300
multi-function peripheral<br>
<br>
Without the connection issue:<br>
$ scanimage -L<br>
device `v4l:/dev/video0' is a Noname UVC Camera (046d:0825)
virtual device<br>
device `pixma:MG6300_canon-printer' is a CANON Canon PIXMA
MG6300 multi-function peripheral<br>
device `pixma:04A91765_20A814' is a CANON Canon PIXMA MG6300
multi-function peripheral<br>
</div>
<br>
Can you tell where this name is created?<br>
<br>
Thanks again, Theo<br>
</body>
</html>