-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty output pane + crash #134
Comments
Hi |
Hey, I have no experience with gdb, but figured I might as well have a look... that's mighty interesting, found I had a problem with my languages but that has not fixed the problem. It didn't crash running in gdb anyways. I see the openCL errors but have no idea what to do with them ;) thx
|
So did the program not crash at all repeating the same steps you performed before when it crashed? The fact that you get no output from tesseract is most certaily because of the ton of OpenCL errors. What shouldn't happen is that gImageReader crashes as a result of tesseract failing, it should rather present an error message. So could you try and reproduce the error with gdb active in order to produce a backtrace? As far as the OpenCL errors are concerned, I assume it has something to do with the proprietary fglrx driver, but I'm not experienced with OpenCL so you'll need to pursue this further with the respective upstreams. |
Nope, no crash... before it would crash when I clicked the recognize button the second time. Now I can click it as much as I like nothing happens, output pane empty.... So, you suggest following up on the fglrx driver? Funny thing is I switched from a ATI GPU to Nvidia GPU about 5 months ago. Seems there is still something leftover that didn't get cleared by the uninstall... hmmm, this could get tricky. Whats with all the gtk-warnings, can I ignore those? Ty for the heads up |
Well that is certainly a source of trouble, OpenCL is picking up the fglrx driver, and all the
etc messages indeed point to the fact that no compatible device exists. So yes, it looks like you have a lot of leftovers installed on your system which you'll need to clean up. Taking it to the fglrx maintainers won't help much in this case since it really looks like a configuration issue with your system. The gtk warnings are related to the gtk version no supporting certain properties, but they should be pretty harmless (it's actually hard to write code which runs without any of the gtk versions out there complaining about some detail :) ). Don't think there is much I can do gImageReader side here, hence closing. |
Have you seen this? |
No - but it still wont fix trying to talk to a nvidia device with a fglrx driver ;) |
Hi,
I'm having problems with the recent version. Starts up ok, but when I try to recognize the output pane stays empty. If I click recognize again it crashes... tried german and english on same jpeg.
Start from terminal gives this:
The text was updated successfully, but these errors were encountered: