To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=99835
                 Issue #|99835
                 Summary|Scanning interface not SANE API compliant
               Component|utilities
                 Version|OOo 3.0
                Platform|All
                     URL|
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|mh
             Reported by|alesh





------- Additional comments from [email protected] Wed Mar  4 02:35:13 +0000 
2009 -------
I am developer on the epkowa sane backend.

While doing some testing with OpenOffice, I noticed (through analyzing some log
files) that the scan interface doesn't appear to be SANE spec compliant.

Specifically, sane_close() and sane_exit() are not called as expected. Not when
you close the scan interface and not even when you shutdown OpenOffice.

Not calling sane_exit() is especially problematic, causing bad things to happen
in the epkowa backend under certain conditions because it doesn't get a chance
to cleanup after itself. Even going so far as to cause OpenOffice to
occasionally crash if you try scanning with it again.

Could someone confirm my observations regarding sane_close() and sane_exit() not
being called on exit?

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to