View Single Post
Old 05-25-2013, 04:07 AM   #5
toddos
Guru
toddos ought to be getting tired of karma fortunes by now.toddos ought to be getting tired of karma fortunes by now.toddos ought to be getting tired of karma fortunes by now.toddos ought to be getting tired of karma fortunes by now.toddos ought to be getting tired of karma fortunes by now.toddos ought to be getting tired of karma fortunes by now.toddos ought to be getting tired of karma fortunes by now.toddos ought to be getting tired of karma fortunes by now.toddos ought to be getting tired of karma fortunes by now.toddos ought to be getting tired of karma fortunes by now.toddos ought to be getting tired of karma fortunes by now.
 
toddos's Avatar
 
Posts: 695
Karma: 822675
Join Date: May 2010
Device: Kobo Aura, Nokia Lumia 920 (Freda)
On-screen keyboard is the closest thing to "accessibility" that would be running on my system. However, that did give me a path to go down. I attached a debugger and ended up seeing this:

Code:
(119c.f2c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Program Files\Calibre2\DLLs\QtGui4.dll - 
QtGui4!QWidgetPrivate::winSetupGestures+0x26f:
00000000`61662e4f 4c8b11          mov     r10,qword ptr [rcx] ds:00000000`00000068=????????????????
winSetupGestures in QWidgetPrivate seems to be related to supporting multitouch functionality in Qt. I assume that because I have a touch screen, that's why it's being called. Since calibre isn't targeting touch in any way, this must be something internal to Qt that it does automatically, and that's broken in the 64-bit version. It may be somewhat related to this Qt bug.

Since I can't (or won't) disable my touchscreen, I guess I'm stuck with 32-bit calibre until Qt fixes this issue.
toddos is offline   Reply With Quote