Bug 669020 - wine-twain does not support a scanner running fine with sane.
Summary: wine-twain does not support a scanner running fine with sane.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: wine
Version: 14
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-12 13:29 UTC by Joachim Backes
Modified: 2012-08-16 17:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 17:05:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Vuescan error msg (scanner not found) (8.90 KB, image/png)
2011-01-12 13:29 UTC, Joachim Backes
no flags Details

Description Joachim Backes 2011-01-12 13:29:18 UTC
Created attachment 473020 [details]
Vuescan error msg (scanner not found)

Description of problem:
Having an Canon Lide 30 USB scanner running fine with sane. Now, I installed the vuescan Windows software (http://www.hamrick.com/, VueScan 9 x32, version 9.0.12)
by "wine vuex3290.exe") and then starting vuescan. But vuescan is not able to find my Canon scanner (see attachment vuescan.png).

Version-Release number of selected component (if applicable):
Version 1.3.10-1.fc14.i686, especially wine-twain-1.3.10-1.fc14.i686

How reproducible:
always

Steps to Reproduce:
1.see description
2.
3.
  
Actual results:
Vuescan does not find my scanner

Expected results:
scanner found

Additional info:

Comment 1 Joachim Backes 2011-01-12 13:34:11 UTC
Output of "wine vuescan.exe"
============================

wine vuex3290.exe
fixme:system:SetProcessDPIAware stub!
fixme:sti:stillimagew_GetDeviceList (0x1313b0, 0, 0x0, 0x16fdfe4, 0x16fdfe8): stub
err:ole:CoGetClassObject class {15757976-7a4b-4b7d-b1ca-7b902927cb97} not registered
err:ole:CoGetClassObject no class object {15757976-7a4b-4b7d-b1ca-7b902927cb97} could be created for context 0x1
err:ole:CoGetClassObject class {15757976-7a4b-4b7d-b1ca-7b902927cb97} not registered
err:ole:CoGetClassObject no class object {15757976-7a4b-4b7d-b1ca-7b902927cb97} could be created for context 0x1
err:ole:create_server class {b6c292bc-7c88-41ee-8b54-8ec92617e599} not registered
err:ole:CoGetClassObject no class object {b6c292bc-7c88-41ee-8b54-8ec92617e599} could be created for context 0x4
fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),1,3,(nil),0,(nil)) - stub!
fixme:wia:wiadevmgr_QueryInterface interface {00000003-0000-0000-c000-000000000046} not implemented
fixme:wia:wiadevmgr_QueryInterface interface {00000003-0000-0000-c000-000000000046} not implemented
fixme:wia:wiadevmgr_EnumDeviceInfo (0x123548, 16, 0xb3e5e8): stub
err:rpc:I_RpcReceive we got fault packet with status 0x3e6
fixme:richedit:ME_HandleMessage ECO_NOHIDESEL not implemented yet!
fixme:richedit:ME_HandleMessage ECO_NOHIDESEL not implemented yet!
fixme:richedit:ME_HandleMessage ECO_NOHIDESEL not implemented yet!
fixme:richedit:ME_HandleMessage ECO_NOHIDESEL not implemented yet!
fixme:richedit:ME_HandleMessage ECO_NOHIDESEL not implemented yet!
fixme:richedit:ME_HandleMessage ECO_NOHIDESEL not implemented yet!


Output of sane-find-scanner:
==============================

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan], chip=LM9832/3) at libusb:002:002
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.

Comment 2 Fedora End Of Life 2012-08-16 17:05:29 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.