Inert Ramblings

28 Comments »

1. Thank you for your post!
   You just solved my mystery log problem!
   *goes deinstalling*

   Comment by Christina | April 29, 2004

2. I was having the same problem with the LiDE but I dont have the disk so how can i deinstall the scanner?

   Comment by Geoffrey | June 3, 2004

3. Bah. I get the error, too…. But i have a laptop, and don’t want to have the scanner connected all the time.

   Oh. And I have a Canon N6470U or something.

   Comment by Jason | June 14, 2004

4. I have a LiDE 20, and while the scanner is connected I get thousands of entries saying
   Looking for devices matching vendor ID=1193 and product ID=8718

   and when its not connected, i get the ones looking for product id 8717 too

   Comment by Zydeco | June 18, 2004

5. I found what programs generate each line:

   N124U_ButtonManager makes:
   Looking for devices matching vendor ID=1193 and product ID=8718

   and N067U_ButtonManager makes:
   Looking for devices matching vendor ID=1193 and product ID=8717

   You can find the ID of your scanner in the System Profiler, and stop these programs from launching automatically in the System Preferences (you should only launch the one that matches the ID of your scanner).
   If you normally don’t have your scanner connected, you may want to deactivate them both, and launch the correct one when you plug in your scanner (i know this is a bother, but what else can be done?)

   Comment by Zydeco | July 25, 2004

6. Thank you so much for your post. I have to use Console to debug a Carbon CFM plugin, and that damn log message was driving me crazy!

   Also, perfect title. Found it in Google first try, first link.

   Comment by Eric Ocean | August 10, 2004

7. Apparently I am not alone. Thank you all for telling me it was the scanner software looking for the scannner hardware. I made these go away (until my next reboot in a few months) by going to terminal, typing “top”, finding the process that matches the scannner, and typing kill and then the process ID. I forgot which they were. Sorry. I shot about four, including some Norton auto this and microsoft self that. I figure while I’m in there shooting gremlins, might as well flip it to full auto, eh? :)

   Comment by Adam Kalins | September 13, 2004

8. I thank you too!

   But not being yet much of a Terminal maven I couldn’t make the kill work. So I went to canonusa.com and downloaded their “Driver Uninstall” program (for the model that I *did* have installed), and that works.

   Comment by Charles Hartman | October 15, 2004

9. I too was getting the annoying “Looking for devices matching vendor” messages in my log. I fixed it using HexEdit.

   Download HexEdit from:
   http://sourceforge.net/project/showfiles.php?group_id=9366

   Edit the following file:
   /Users/Shared/N067U/N067U_Driver.bundle/Contents/MacOS/N067U_Driver

   Do a search for “Looking for devices” within the file and replace the beginning of the string - the L - with a hex zero.

   The whole process is a bit more complicated because the file is open by default, so you have to make a copy, edit that, and replace the original file. Plus the file is inside the bundle so you have to choose “Show Package Contents” to actually get there.

   If I have some time off, I can write a small app or shell script to do this, but that’s not likely anytime in the immediate future.

   Good luck.

   Comment by Eric Shapiro | November 1, 2004

10. thanks a lot for that hint.

    You can do it a little easier: you don’t have to copy and replace the file; instead you just open the process watcher and kill the processes N067U_ButtonManager and N124U_ButtonManager. Than start editing.

    Also check in the system settings, if there are multiple copies of these files and remove the copies from the startup list. I had 6 copies!!!

    :-) Matthias

    Comment by Matthias | November 24, 2004

11. I tried both solutions, but none worked:

    1) I removed both N124U_ButtonManager and N067U_ButtonManager from the login items, restarted, and then manually launched the N124U_ButtonManager (it’s ID matches my Lide20 scanner) and tried to scan with the CXanon Toolbox, but got an error telling me it couldn’t connect to the scanner. So I reinstalled everything.

    2) I edited the driver as described, replacing the “L” from “Looking for devices” in the N067U_Driver with “00″, using HexEdit, but after replacing the original with the edited driver and restarting, when trying to scan, I got an error saying the driver was either missing or damaged…

    Comment by Johan Dada Vis | December 16, 2004

12. THANK YOU! I just discovered this mystery problem and this must be the cause. Will delete the problem driver now.

    Comment by Maria Langer | December 16, 2004

13. canonerror

    Mac¥á¥â °ÊÁ°¤«¤é Looking for devices matching vendor ID=1193 and product ID=8717 ¤Ê¤ó¤ÆÆæ¤Î¥¨¥é¡¼¤¬¥³¥ó¥½¡¼¥ë¥í¥°¤ÇÅǤ«¤ì¤Þ¤¯¤Ã¤Æ¤í¤¯¤Ë¥Ç¥Ð¥Ã¥°¤Ç¤­¤º¤Ëº¤¤Ã¤Æ¤¤¤¿¤¬¡¢ http://www.inertramblings.com/archives/000695.html ¤ò¸«¤Æ¡¢¤Ê¤ó¤ÈCanon¤Î¥¹¥­…

    Trackback by PukiWiki/TrackBack 0.1 | January 31, 2005

14. Thanks, you just solved my problem as well. You’d think Canon could do a little better job with its drivers.

    Comment by Bob | February 10, 2005

15. Another thank you for identifying the problem. On Mac OSX, searching for “ButtonManager” in Finder, using GetInfo for them, and sending the files related to Canoscan cures the repetition problem, and the Photoshop plugin for the scanner still works nicely with them gone.

    Comment by Terence Yorks | June 2, 2005

16. You don’t need to un-install anything. Just go to “system Preferences” and “accounts”. Then click the “login items” tab and remove the “N12 ….” and “N6… button manager”. These are not required to scan (at least from photoshop. But I believe are spposed to monitor the scanner for button presses (which most people don’t use anyway).

    Comment by visskiss | July 3, 2005

17. First, THANK YOU for the post. I have a little more to contribute. visskiss is exactly right about disabling the ButtonManagers in Accounts/Startup Items (’tho the location of the Startup Items may vary depending on your version of the Mac OS). Also, you can open the Activity Monitor (/Applications/Utilities/Activity Monitor in Mac OS 10.3, 10.4), search in the main window for processes with “button” and quit any processes with “…ButtonManager” in their name. This will disable those log-cloggin’ processes completely without a complete restart. It is VERY important to follow visskiss’ instructions, lest those pesky little things pop up again when you do restart.

    Comment by Jonathan Woolson | August 25, 2005

18. I have that message repeatedly, and yet I do not have, nor have I ever had any kind of scanner hooked up to my machine.

    ?

    Comment by Juliet | January 23, 2006

19. Thanks for information. Most helpful.

    Comment by Mike Cripps | February 3, 2006

20. Thanks! Got rid of the N067U stuff altogether as it’s not needed for my LiDE 30. Problem solved!

    Comment by Brent | June 27, 2006

21. Thank you! I love it when a search as cryptic as “Looking for devices matching vendor ID=1193 and product ID=8717″ in google provides me with exactly, and only exactly the results I was looking for. Amazing, amazing.

    Comment by Mitch | September 4, 2006

22. System preferences solution was great! No more console entries…. Anyone out there able to get the Image Capture utility on their imac core2 duo to recognize a lide 30?

    Comment by Roman | September 21, 2006

23. Thanks google for finding this site, and thanks blogger and all the prior comments. I just noticed that console log, and finding the answer here just makes it much faster for me to get rid of it.

    Comment by Tae | September 29, 2006

24. Thank you Thank you!!!
    Console is usable now after following visskiss and Jonathan!

    Comment by andyR | October 24, 2006

25. Thanks to above - finding and fixing this is a GREAT relief!

    Comment by Jim Thomas | October 29, 2006

26. Thanks for this. I killed my process using the Activity Monitor (View > Quit processes)

    Comment by benc | August 23, 2007

27. very helpful… thanks a lot!!

    Comment by br | September 17, 2007

28. FOUR YEARS LATER AND YOU STILL ROCK!!!
    I think this was making something else crash, as it was always present when I was having problms with VLC… at any rate, it was draining away resources I want back!
    …creeps at canon…

    Comment by Penelope | March 23, 2008

Leave a comment

Name (required)

e-Maile-Mail (required - will not be published)

Website

« Previous | Next »

About Inert Ramblings

Site info

Inert Ramblings
Theme: Andreas04 by Andreas Viklund. Blog at WordPress.com.