Discussion:
Bug#848178: gimagereader fails to start
(too old to reply)
joe belisle
2016-12-14 21:50:02 UTC
Permalink
Raw Message
Package: gimagereader
Version: 3.2.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

gimagereader fails to start. If started from the bash prompt it gives the
following error: gimagereader-gtk: symbol lookup error: gimagereader-gtk:
undefined symbol: _ZN9tesseract11TessBaseAPI13AnalyseLayoutEv

I reported a very similar bug a year or so ago and it was simply a failure to
have updated changed symbols.



-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gimagereader depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2
ii libatkmm-1.6-1v5 2.24.2-2
ii libc6 2.24-7
ii libcairomm-1.0-1v5 1.12.0-1+b1
ii libfontconfig1 2.11.0-6.7
ii libgcc1 1:6.2.1-5
ii libglib2.0-0 2.50.2-2
ii libglibmm-2.4-1v5 2.50.0-1
ii libgomp1 6.2.1-5
ii libgtk-3-0 3.22.4-1
ii libgtkmm-3.0-1v5 3.22.0-1
ii libgtksourceviewmm-3.0-0v5 3.18.0-1
ii libgtkspellmm-3.0-0v5 3.0.5+dfsg-1
ii libjpeg62-turbo 1:1.5.1-2
ii libjson-glib-1.0-0 1.2.2-1
ii libpangomm-1.4-1v5 2.40.1-3
ii libpodofo0.9.4 0.9.4-3
ii libpoppler-glib8 0.44.0-3
ii libsane 1.0.25-2+b1
ii libsigc++-2.0-0v5 2.10.0-1
ii libstdc++6 6.2.1-5
ii libtesseract3 3.04.00-5
ii libxml++2.6-2v5 2.40.1-1

gimagereader recommends no packages.

gimagereader suggests no packages.

-- no debconf information
Debian Bug Tracking System
2016-12-15 11:30:01 UTC
Permalink
Raw Message
Your message dated Thu, 15 Dec 2016 12:22:04 +0100
with message-id <e942896d-63fb-ab5c-bce7-***@inventati.org>
and subject line Re: Bug#848178: Close bug
has caused the Debian Bug report #848178,
regarding gimagereader fails to start
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)
--
848178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848178
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Debian Bug Tracking System
2016-12-15 20:10:02 UTC
Permalink
Raw Message
reopen -1
Bug #848178 {Done: Philip Rinn <***@inventati.org>} [gimagereader] gimagereader fails to start
Bug reopened
Ignoring request to alter fixed versions of bug #848178 to the same values previously set
reassign -1 libtesseract3 3.04.01-4.2
Bug #848178 [gimagereader] gimagereader fails to start
Bug reassigned from package 'gimagereader' to 'libtesseract3'.
No longer marked as found in versions gimagereader/3.2.0-1.
Ignoring request to alter fixed versions of bug #848178 to the same values previously set
Bug #848178 [libtesseract3] gimagereader fails to start
Marked as found in versions tesseract/3.04.01-4.2.
retitle -1 libtesseract3: generated shlibs dependencies are not strict enough
Bug #848178 [libtesseract3] gimagereader fails to start
Changed Bug title to 'libtesseract3: generated shlibs dependencies are not strict enough' from 'gimagereader fails to start'.
--
848178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848178
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Philip Rinn
2016-12-16 11:30:01 UTC
Permalink
Raw Message
Hi Adrian,
Please do not close bugs that are actual bug - the generated
dependencies must ensure that problems like the issue in this
bug won't happen.
Reopened and moved to the package where the root cause of this bug is.
well, so true.

The root cause of this bug was a silent ABI break in tesseract 3.04.00 -> 3.04.01
which is reverted upstream (https://github.com/tesseract-ocr/tesseract/issues/254).

See the corresponding Debian bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794489
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816857

And see also for the whole picture:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815056
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815860
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815970

From my point of view it should have been save to use libtesseract3 (3.04.00-5)
with a binary that was build against libtesseract3 (>>3.04.01-4). This does not
seem to be the case.

As the Debian maintainers of tesseract didn't provide much help in the past (see
the first two mentioned bugs) and as it will not affect any Debian release I just
closed the bug. But as you said it's actually still a bug in tesseract.

Best,
Philip
Debian Bug Tracking System
2017-01-05 20:30:01 UTC
Permalink
Raw Message
severity -1 normal
Bug #848178 [libtesseract3] libtesseract3: generated shlibs dependencies are not strict enough
Severity set to 'normal' from 'grave'
--
848178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848178
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Loading...