Your message dated Fri, 4 May 2018 19:40:44 +0200
with message-id <e899b01c-3b74-946e-58c8-a819579d2...@inventati.org>
and subject line 
has caused the Debian Bug report #896656,
regarding texmaker does notr start "symbol lookup error" and "undefined symbol: 
synctex_next_result"
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 ow...@bugs.debian.org
immediately.)


-- 
896656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texmaker
Version: 5.0.2-1+b1
Severity: important

Dear Maintainer,

When I try to start texmaker, it does not start. Instead I get the
following:

$ texmaker
texmaker: symbol lookup error: texmaker: undefined symbol:
synctex_next_result

The result is fully reproducible.

With best regards,
Wojtek

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

Kernel: Linux 4.15.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages texmaker depends on:
ii  libc6                             2.27-3
ii  libgcc1                           1:8-20180414-1
ii  libgl1                            1.0.0-2
ii  libqt5concurrent5                 5.10.1+dfsg-5
ii  libqt5core5a [qtbase-abi-5-10-0]  5.10.1+dfsg-5
ii  libqt5gui5                        5.10.1+dfsg-5
ii  libqt5network5                    5.10.1+dfsg-5
ii  libqt5printsupport5               5.10.1+dfsg-5
ii  libqt5script5                     5.10.1+dfsg-2
ii  libqt5widgets5                    5.10.1+dfsg-5
ii  libqt5xml5                        5.10.1+dfsg-5
ii  libstdc++6                        8-20180414-1
ii  libsynctex1                       2018.20180416.47457-1
ii  texmaker-data                     5.0.2-1

Versions of packages texmaker recommends:
ii  aspell                                0.60.7~20110707-4
ii  asymptote                             2.44-1
ii  ghostscript                           9.22~dfsg-2.1
ii  hunspell-en-us [hunspell-dictionary]  1:2017.08.24
pn  latex-beamer                          <none>
ii  myspell-pl [myspell-dictionary]       20170707-1
ii  netpbm                                2:10.0-15.3+b2
ii  psutils                               1.17.dfsg-4
ii  texlive-lang-english                  2018.20180416-1
ii  texlive-latex-extra                   2018.20180416-1

Versions of packages texmaker suggests:
pn  texlive-lang-all  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Package: texmaker
Version: 5.0.2-2


Hi,

this bug is fixed in texmaker 5.0.2-2. It was just uploaded to unstable but I
failed to close the bugs correctly in the changelog.

Best,

Philip



Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to