Bug#979577: qtcreator: Clang Code Model no longer finds 'stddef.h' since version 4.14.0-2
Thanks for the quick reply! On 08/01/2021 17.28, Pino Toscano wrote: qtcreator 4.14.0-2 has been available in unstable (which you use) for more than two weeks, so reading this problem now seems slightly awkward. Have you used qtcreator 4.14.0-2 (and it code model) successfully so far in the past two weeks? I'm usually using testing (and use unstable for double-checking before reporting bugs) and haven't really used qtcreator since Christmas as far as I can remember. (The package migrated to testing on 2020-12-28.) My suspect is the upload of llvm-toolchain-11 done yesterday, and your package list: ii libclang1-11 1:11.0.1-2 show you updated to it. Can you please try to backport your LLVM/Clang 11 packages to the same version used to build qtcreator? You can get the list of installed packages using: $ dpkg -l '*llvm*11*' | grep ^ii $ dpkg -l '*clang*11*' | grep ^ii and then use the `debsnap` tool, part of the devscripts package, to download them, e.g.: $ debsnap -d . -a amd64 libclang-11 1:11.0.1~+rc2-1 (you will need to repeat that for all the packages you have installed, removing the :amd64 suffix in the packages that have multi-arch annotations). The issue is still reproducible after downgrading the LLVM/Clang packages this way. It disappears when downgrading qtcreator and qtcreator-data to 4.14.0-1, though. Michael
Bug#979577: qtcreator: Clang Code Model no longer finds 'stddef.h' since version 4.14.0-2
Package: qtcreator
Version: 4.14.0-2
Severity: normal
X-Debbugs-Cc: m.wegh...@posteo.de
Dear Maintainer,
since version 4.14.0-2, Qt Creator's Clang Code Model is unable to find the
'stddef.h' header. It still works OK with version 4.14.0-1.
Sample steps to reproduce:
* create a simple C++ project with a source file that
(directly or indirectly) includes 'stddef.h',
e.g. via "File" -> "New File or Project" -> "Plain C++ Application"
(or use files from sample project at the end)
* open the source file 'main.cpp'
* if not present yet, add an '#include ' or '#include stddef.h'
Result:
A warning shows up:
> Warning: The code model could not parse an included file, which might lead to
incorrect code completion and highlighting, for example.
>
> wchar.h:35:10: error: 'stddef.h' file not found
> [...]
and the Code Model does not work properly.
It works again as expected when downgrading to qtcreator 4.14.0-1.
Files for sample project to reproduce the issue:
main.cpp:
#include
using namespace std;
int main()
{
cout << "Hello World!" << endl;
return 0;
}
CMakeLists.txt:
cmake_minimum_required(VERSION 3.5)
project(testp-project LANGUAGES CXX)
set(CMAKE_CXX_STANDARD 11)
set(CMAKE_CXX_STANDARD_REQUIRED ON)
add_executable(testp-project main.cpp)
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-1-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages qtcreator depends on:
ii clang-11 1:11.0.1-2
ii libc6 2.31-9
ii libclang1-11 1:11.0.1-2
ii libdw1 0.182-3
ii libelf10.182-3
ii libgcc-s1 10.2.1-3
ii libkf5syntaxhighlighting5 5.77.0-2
ii libqt5concurrent5 5.15.2+dfsg-2
ii libqt5core5a [qtbase-abi-5-15-2] 5.15.2+dfsg-2
ii libqt5designer55.15.2-3
ii libqt5designercomponents5 5.15.2-3
ii libqt5gui5 5.15.2+dfsg-2
ii libqt5help55.15.2-3
ii libqt5network5 5.15.2+dfsg-2
ii libqt5printsupport55.15.2+dfsg-2
ii libqt5qml5 [qtdeclarative-abi-5-15-2] 5.15.2+dfsg-2
ii libqt5quick5 5.15.2+dfsg-2
ii libqt5quickwidgets55.15.2+dfsg-2
ii libqt5serialport5 5.15.2-2
ii libqt5sql5 5.15.2+dfsg-2
ii libqt5sql5-sqlite 5.15.2+dfsg-2
ii libqt5svg5 5.15.2-2
ii libqt5widgets5 5.15.2+dfsg-2
ii libqt5xml5 5.15.2+dfsg-2
ii libstdc++6 10.2.1-3
ii libyaml-cpp0.6 0.6.3-9
ii libzstd1 1.4.8+dfsg-1
ii qml-module-qtqml-models2 5.15.2+dfsg-2
ii qml-module-qtquick-controls5.15.2-2
ii qml-module-qtquick25.15.2+dfsg-2
ii qtchooser 66-2
ii qtcreator-data 4.14.0-2
Versions of packages qtcreator recommends:
ii clang-tidy1:11.0-51+nmu1
ii gdb-minimal [gdb] 10.1-1.7
ii gnome-terminal [x-terminal-emulator] 3.38.1-2
ii konsole [x-terminal-emulator] 4:20.12.1-1
ii make 4.3-4
ii qmlscene 5.15.2+dfsg-2
ii qt5-doc 5.15.2-2
ii qt5-qmltooling-plugins5.15.2+dfsg-2
ii qtbase5-dev-tools 5.15.2+dfsg-2
ii qtcreator-doc 4.14.0-2
ii qtdeclarative5-dev-tools 5.15.2+dfsg-2
ii qttools5-dev-tools5.15.2-3
ii qttranslations5-l10n 5.15.1-2
ii qtxmlpatterns5-dev-tools 5.15.2-2
Versions of packages qtcreator suggests:
pn clazy
ii cmake 3.18.4-1+b1
ii g++ 4:10.2.0-1
ii git 1:2.30.0-1
ii meson 0.56.1-1
pn subversion
pn valgrind
-- no debconf information
Bug#965386: plasma-browser-integration: Please package Firefox extension
Package: plasma-browser-integration Version: 5.17.5-1 Severity: wishlist X-Debbugs-Cc: m.wegh...@posteo.de Dear Maintainer, currently, the WebExtension for plasma-browser-integration is not packaged in Debian. For the Firefox case, it is therefore necessary to install the extension manually from AMO: https://addons.mozilla.org/en-US/firefox/addon/plasma- integration/ It would be great if it could be provided via Debian package (possibly a separate binary package than the one that already exists). Note: The file 'dev_README.txt' in the sources describes how to build the extension, but this probably cannot be followed as is, since it involves installing packages via "npm" in the first step (which is not in line with Debian's packaging practices). Best regards, Michael -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-browser-integration depends on: ii kio 5.70.1-1 ii libc6 2.31-1 ii libkf5activities5 5.70.0-1 ii libkf5configcore5 5.70.0-1 ii libkf5coreaddons5 5.70.0-1 ii libkf5crash5 5.70.0-1 ii libkf5dbusaddons5 5.70.0-1 ii libkf5filemetadata3 5.70.0-1 ii libkf5i18n5 5.70.0-1 ii libkf5kiocore55.70.1-1 ii libkf5kiowidgets5 5.70.1-1 ii libkf5notifications5 5.70.0-1 ii libkf5purpose-bin 5.70.0-1 ii libkf5purpose55.70.0-1 ii libkf5runner5 5.70.0-1 ii libkf5service-bin 5.70.0-1 ii libkf5service55.70.0-1 ii libqt5core5a 5.14.2+dfsg-4 ii libqt5dbus5 5.14.2+dfsg-4 ii libqt5gui55.14.2+dfsg-4 ii libqt5widgets55.14.2+dfsg-4 ii libstdc++610.1.0-6 plasma-browser-integration recommends no packages. plasma-browser-integration suggests no packages. -- no debconf information
Bug#955465: qtcreator: Unnecessary botan build dep
Package: qtcreator
Version: 4.11.0-2
Severity: normal
Tags: patch
Dear Maintainer,
qtcreator has a now unnecessary build dependency on package
'libbotan-2-dev'.
Botan is no longer used since upstream commit
d7178b88c4b2572fb83b28f8178940766216deed
("SSH: Use OpenSSH tools").
Therefore, I suggest do drop that build dependency, in particular
since qtcreator is currently marked for autoremoval due to bug
#952951 ("botan: Replace PKCS11 headers provided by OASIS").
A patch to do so will be attached.
Kind regards,
Michael
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages qtcreator depends on:
ii libc6 2.30-2
ii libclang1-81:8.0.1-9
ii libgcc-s1 [libgcc1]10-20200324-1
ii libgcc11:10-20200324-1
ii libkf5syntaxhighlighting5 5.62.0-3
ii libllvm8 1:8.0.1-9
ii libqbscore1.13 1.13.1-2
ii libqt5concurrent5 5.12.5+dfsg-9
ii libqt5core5a [qtbase-abi-5-12-5] 5.12.5+dfsg-9
ii libqt5designer55.12.5-2+b2
ii libqt5designercomponents5 5.12.5-2+b2
ii libqt5gui5 5.12.5+dfsg-9
ii libqt5help55.12.5-2+b2
ii libqt5network5 5.12.5+dfsg-9
ii libqt5printsupport55.12.5+dfsg-9
ii libqt5qml5 [qtdeclarative-abi-5-12-5] 5.12.5-5
ii libqt5quick5 5.12.5-5
ii libqt5quickwidgets55.12.5-5
ii libqt5script5 5.12.5+dfsg-2
ii libqt5serialport5 5.12.5-1
ii libqt5sql5 5.12.5+dfsg-9
ii libqt5sql5-sqlite 5.12.5+dfsg-9
ii libqt5widgets5 5.12.5+dfsg-9
ii libqt5xml5 5.12.5+dfsg-9
ii libstdc++6 10-20200324-1
ii qml-module-qtqml-models2 5.12.5-5
ii qml-module-qtquick-controls5.12.5-1+b1
ii qml-module-qtquick25.12.5-5
ii qtchooser 66-2
ii qtcreator-data 4.11.0-2
Versions of packages qtcreator recommends:
ii clang 1:9.0-49.1
ii clang-tidy 1:9.0-49.1
ii gdb9.1-2
ii konsole [x-terminal-emulator] 4:19.08.1-2+b1
ii make 4.2.1-1.2
ii qmlscene 5.12.5-5
ii qt5-doc5.12.5-1
ii qt5-qmltooling-plugins 5.12.5-5
ii qtbase5-dev-tools 5.12.5+dfsg-9
ii qtcreator-doc 4.11.0-2
ii qtdeclarative5-dev-tools 5.12.5-5
ii qttools5-dev-tools 5.12.5-2+b2
ii qttranslations5-l10n 5.12.5-1
ii qtxmlpatterns5-dev-tools 5.12.5-1
ii xterm [x-terminal-emulator]353-1
Versions of packages qtcreator suggests:
ii clazy 1.6-2+b1
ii cmake 3.16.3-1
ii g++ 4:9.2.1-3.1
ii git 1:2.25.1-1
pn kate-data
ii subversion 1.13.0-2+b1
ii valgrind1:3.15.0-1
-- no debconf information
From 2c75d9fd06b44e8e381a39af2e81fc38f4e01c37 Mon Sep 17 00:00:00 2001
From: Michael Weghorn
Date: Tue, 31 Mar 2020 17:06:28 +0200
Subject: [PATCH] Drop unused botan build dependency
Botan has been removed upstream with
commit d7178b88c4b2572fb83b28f8178940766216deed
Author: Christian Kandeler
Date: Fri Nov 23 11:07:57 2018 +0100
SSH: Use OpenSSH tools
... instead of our own SSH library.
Advantages:
- Full compatibility with OpenSSH behavior guaranteed.
- Minimal maintenance effort.
- Less code to build.
- Big chunk of 3rd party sources can be removed from our repository.
One the downside, Windows users now need to install OpenSSH for
RemoteLinux support. Hoewever, people doing embedded development
probably have it installed anyway.
[ChangeLog] Switched SSH backend to OpenSSH
Fixes: QTCREATORBUG-15744
Fixes: QTCREATORBUG-15807
Fixes: QTCREATORBUG-19306
Fixes: QTCREATORBUG-20210
Change-Id: Ifcfefdd39401e45ba1f4aca35d2c5bf7046c7aab
Reviewed-by: Eike Ziller
Reviewed-by: Ulf Hermann
---
debian/control | 1 -
debian/rules | 3 +--
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/debian/control b/debian/control
index 0b279a0..9529edb 100644
--- a/debian/control
+++ b/de
Re: Bug#911844: okular: Prints to the wrong printer
> Michael, thank you are lot for your research which made that bug report > actionable. > > Of course there may be another bug in there: When one printer cannot be > used for some reason, it should not automatically switch to another one. > But nonetheless the commit you pointed out looks like it can really help > here. Yes, after taking a quick glance at the commit again, I think that this other bug you mention should also be fixed by that commit. Previously, the currently selected printer (variable 'm_name' etc.) would just not be reassigned a new value (the newly selected printer) if a non-PPD printer was selected. Thus, the last printer having a PPD that was previously selected in the dialog would be the target of the print job. The commit changes this. Regards, Michael signature.asc Description: OpenPGP digital signature
Re: Bug#911844: okular: Prints to the wrong printer
Hi, On 11/06/2019 23.37, Martin Steigerwald wrote: > Hmmm, so it works okay with okular 19.04.1. > > That means somewhere between 17.12 and 19.04.1 is a bug fix for the issue > you reported. Maybe upstream has an idea which one it might be. At this > point I believe all that could be done would be to find and then backport > that fix, as Debian is in deep freeze and packaging 19.04 thus out of > scope. I've investigated a bit and it's not an Okular issue, but one in the Qt print dialog with printers that don't have PPD files. It can be reproduced e.g. with kate just the same and Brian even mentioned in the initial report that qpdfview is affected as well. The issue has been fixed upstream (qtbase) with the following commit (so that's what would have to be backported): commit 84cc8d0badb4abc3c9a96d59c61dddce916a216c Author: Albert Astals Cid Date: Mon Feb 5 09:20:20 2018 +0100 cups: Support raw printers They don't have a ppd but we don't *really* need a ppd to just print Change-Id: Idf6b6dafc19420a511b057194488e2170cae4d70 This probably also fixes #911702, but I didn't test that explicitly. Regards, Michael signature.asc Description: OpenPGP digital signature
Bug#873226: Okular doesnt load cups default options for printers
On Fri, 25 Aug 2017 17:38:10 +0200 Raschi Diego wrote: > Package: okular > Version: 4:16.08.2-1+b1 > Severity: important > > Hi, > > Okular has the same issue when retrieving printer information like > previous release (Jessie). Basically, selecting the printer does not > load the default options of cups, for example the default options of my > printers are set to double-sided side long (so the paper should get > printed on each side). By printing from okular this setting is not > loaded so the pdf doesn't get printed on the long side (it get printed > only on one side of the paper) Another example is color mode, if > grayscale is set in cups, okular doesnt load this setting and use color > (the default of okular) Sorry for my bad english > Cheers, Diego > Hi, this is/was actually an issue in the Qt print dialog, but options are now properly initialized in the current upstream development version. Most of the improvements will be contained in Qt version 5.11 (more details on that e.g. in [1] ). Proper initialization of the duplex value in the print dialog will be part of Qt 5.12. [2] Best regards, Michael [1] https://www.kdab.com/better-support-for-cups-features-in-qt-5-11/ [2] https://codereview.qt-project.org/#/c/226881/
Bug#815589: libokularcore6: okular sets fit-to-page option when printing
forwarded 815589 https://bugs.kde.org/show_bug.cgi?id=336617 thanks Hi, there is the following upstream bug report that deals with the issue of the printout in Okular always being scaled down to the printable area: https://bugs.kde.org/show_bug.cgi?id=336617 Regards, Michael On Mon, 22 Feb 2016 19:39:11 +0100 M G Berberich wrote: > Package: libokularcore6 > Version: 4:15.08.3-1 > Severity: important > > Dear Maintainer, > > when printing pdfs okular sets the “fit-to-page”-option which results > in scaling down the printout. There is no option to prevent okular > from doing this, so printing of anything that has to have a specific > size is impossible. > > [...]
Bug#807044: Okular scales down A4 to A5 on printing
On 2018-02-08 18:25, Marc Haber wrote: > On Thu, Jan 18, 2018 at 03:26:35PM +0100, Michael Weghorn wrote: >> Thanks, Marc, for retesting and the quick reply. > > You're welcome. I apologize for adding more confusion to this, but I > cannot reproduce this any more in current sid. > > I guess it's fine to close the issue for okular 4:17.08.3-3 then. > Thanks for the update. and nice to hear you're no longer having the problem. I'm closing this then as you suggested. Regards, Michael PS: Interestingly, a very similar issue hast just recently been reported upstream: https://bugs.kde.org/show_bug.cgi?id=389953
Bug#887793: okular: Does not display text (the text is there and you can copy it) when it contains accents
reassign 887793 libpoppler64
found 887793 poppler/0.48.0-2+deb9u1
fixed 887793 poppler/0.48.0-2+deb9u2
thanks
Thank you for your quick replies.
I'm closing the bug report then.
Regards,
Michael
On 2018-02-07 16:52, Yago Fernandez wrote:
> It's alright now
>
> El 7 feb. 2018 15:43, "Michael Weghorn" <mailto:m.wegh...@posteo.de>> escribió:
>
> Hi,
>
> On 2018-01-20 00:40, Iago wrote:
> >
> > After one of the latest security updates in debian stretch some
> pdf files started to display "transparent" text. I think that this
> is related to pdf with accents.
> > Another user (http://forums.debian.net/viewtopic.php?f=6&t=135888
> <http://forums.debian.net/viewtopic.php?f=6&t=135888>) says that thi
> happens when generating a pdf from latex and using
> \usepackage[T1]{fontenc}, needed for accentuated text.
>
> this sounds very much like bug #886733.
> A new version of Poppler which fixes this regression has been released
> in the meanwhile.
>
> Does the problem still occur for you with the latest Poppler update
> (version 0.48.0-2+deb9u2)?
>
> Regards,
> Michael
>
Bug#887793: okular: Does not display text (the text is there and you can copy it) when it contains accents
Hi,
On 2018-01-20 00:40, Iago wrote:
>
> After one of the latest security updates in debian stretch some pdf files
> started to display "transparent" text. I think that this is related to pdf
> with accents.
> Another user (http://forums.debian.net/viewtopic.php?f=6&t=135888) says that
> thi happens when generating a pdf from latex and using
> \usepackage[T1]{fontenc}, needed for accentuated text.
this sounds very much like bug #886733.
A new version of Poppler which fixes this regression has been released
in the meanwhile.
Does the problem still occur for you with the latest Poppler update
(version 0.48.0-2+deb9u2)?
Regards,
Michael
Bug#887746: okular: Please package new upstream version 17.12.1
Package: okular Version: 4:17.08.3-2 Severity: wishlist Dear Maintainer, thanks for maintaining Okular for Debian and providing a Qt 5 based version with version 17.08.3. In the meanwhile, upstream has released version 17.12.1 and it would be great if that one could be packaged for Debian. KDE Neon has already packaged it, so having a look at their packaging might possibly help; the git repository is at https://anongit.neon.kde.org/applications/okular.git Kind regards, Michael -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages okular depends on: ii kio 5.37.0-2 ii libc62.26-4 ii libfreetype6 2.8.1-1 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libkf5activities55.37.0-2 ii libkf5archive5 5.37.0-2 ii libkf5bookmarks5 5.37.0-2 ii libkf5codecs55.37.0-2 ii libkf5completion55.37.0-2 ii libkf5configcore55.37.0-2 ii libkf5configgui5 5.37.0-2 ii libkf5configwidgets5 5.37.0-2 ii libkf5coreaddons55.37.0-3 ii libkf5i18n5 5.37.0-2 ii libkf5iconthemes55.37.0-2 ii libkf5itemviews5 5.37.0-2 ii libkf5jobwidgets55.37.0-2 ii libkf5kexiv2-15.0.0 17.08.3-1 ii libkf5kiocore5 5.37.0-2 ii libkf5kiowidgets55.37.0-2 ii libkf5parts5 5.37.0-2 ii libkf5pty5 5.37.0-2 ii libkf5service-bin5.37.0-2 ii libkf5service5 5.37.0-2 ii libkf5textwidgets5 5.37.0-2 ii libkf5wallet-bin 5.37.0-2 ii libkf5wallet55.37.0-2 ii libkf5widgetsaddons5 5.37.0-2 ii libkf5windowsystem5 5.37.0-2 ii libkf5xmlgui55.37.0-2 ii libokular5core7 4:17.08.3-2 ii libphonon4qt5-4 4:4.9.1-3 ii libpoppler-qt5-1 0.61.1-2 ii libqca-qt5-2 2.1.3-1 ii libqmobipocket2 4:17.08.3-2 ii libqt5core5a 5.9.2+dfsg-6 ii libqt5dbus5 5.9.2+dfsg-6 ii libqt5gui5 5.9.2+dfsg-6 ii libqt5printsupport5 5.9.2+dfsg-6 ii libqt5qml5 5.9.2-3 ii libqt5quick5 5.9.2-3 ii libqt5svg5 5.9.2-3 ii libqt5widgets5 5.9.2+dfsg-6 ii libqt5xml5 5.9.2+dfsg-6 ii libspectre1 0.2.8-1 ii libstdc++6 7.2.0-19 ii phonon4qt5 4:4.9.1-3 ii qml-module-org-kde-kirigami 1.1.0-2 ii qml-module-org-kde-kquickcontrolsaddons 5.37.0-2+b1 ii qml-module-qt-labs-folderlistmodel 5.9.2-3 ii qml-module-qtgraphicaleffects5.9.2-2 ii qml-module-qtquick-controls 5.9.2-2 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages okular recommends: ii cups-bsd 2.2.6-4 Versions of packages okular suggests: ii ghostscript9.22~dfsg-1 pn jovie pn okular-extra-backends ii poppler-data 0.4.8-2 pn texlive-binaries pn unrar -- no debconf information
Bug#807044: Okular scales down A4 to A5 on printing
Thanks, Marc, for retesting and the quick reply. On 2018-01-17 23:22, Marc Haber wrote: > https://www.eisenbahn-unfalluntersuchung.de/SharedDocs/Downloads/EUB/Untersuchungsberichte/2015/104_Duisburg-Wedau_-_Lintorf.pdf > - click on "herunterladen" and use the resulting PDF. I can't reproduce the problem with this document in my setup. Some more questions that might help to narrow down the problem: In the initial report, you wrote: > I am printing to a PostScript printer via local CUPS (Debian unstable) > to a remote CUPS server (Debian stable). Do you know whether the problem also occurs when printing to a printer directly connected to your computer or a network printer without using a remote CUPS server (if you have the possibility to test this)? Does the problem also occur when using the CUPS-PDF printer? (from package "printer-driver-cups-pdf", which saves the output into a file underneath $HOME/PDF? Could you switch CUPS log level to "debug" in /etc/cups/cupsd.conf and attach the error_log (/var/log/cups/error_log) that results from a print job in Okular that shows the problem? Regards, Michael
Bug#860366: okular: Okular crashes when opening some documents
Hi Rainer, thanks for the quick reply. Let's close the bug report then as you suggested. Regards, Michael On 2018-01-16 22:23, Rainer Dorsch wrote: > Hi Michael, > > thanks for testing. > > It works here now as well on stable. I switched though from i386 to amd64 in > the meantime. Since it uses an enormous amount of memory > 2GB you might hit > it only on i386 > > I suggest to close the issue, when somebody repros it, it can be reopened > > Thanks > Rainer > > Am Dienstag, 16. Januar 2018, 18:26:12 CET schrieben Sie: >> tags 860366 moreinfo >> thanks >> >> Hi Rainer, >> >> I just tried to reproduce the crash with the mentioned file. With the >> Okular version in current Debian testing/unstable (4:17.08.3-2), I >> cannot reproduce the problem, the file opens fine for me. >> >> Does the problem still occur there for you? >> >> Regards, >> Michael > >
Bug#816354: okular: No file association for pdf files and no menu entry
Hi Sten, does the described problem still occur for you? I just tried to reproduce but did not encounter this problem. Regards, Michael On Mon, 29 Feb 2016 23:10:56 -0500 Sten Heinze wrote: > [...] > Trying to open a pdf file from dolphin only leads to an 'open with..' dialog > where I can select the application to do so. But no entry for okular can be > found is the list of known application nor in the applications list in the > Plasma launcher. However, okular can be run from the command line and can > open the pdf file, so just the file associations and menu entry is missing. > [...]
Bug#860366: okular: Okular crashes when opening some documents
tags 860366 moreinfo thanks Hi Rainer, I just tried to reproduce the crash with the mentioned file. With the Okular version in current Debian testing/unstable (4:17.08.3-2), I cannot reproduce the problem, the file opens fine for me. Does the problem still occur there for you? Regards, Michael
Bug#814602: okular: freezes on trying to load *.chm file
Hi, On Sat, 13 Feb 2016 13:14:56 +0100 Maria wrote: > Okular freezes when trying to load a *.chm file. > Mouse turns into please wait status, menus doesn't react. > Only possibillity is killing the window. > [...] does this problem still occur with the Okular version in current Debian testing/unstable? If so, could you possibly attach a file with which the problem occurs? Regards, Michael
Bug#807044: Okular scales down A4 to A5 on printing
Hi Marc and Adi, On Thu, 27 Apr 2017 19:53:45 +0200 Adi Kriegisch wrote: > There seem to be several upstream issues dealing with this, eg. > https://bugs.kde.org/show_bug.cgi?id=348171 > > Okular in its current version in Stretch (16.08.2-1+b1) cannot be used for > printing. The mentioned upstream bug has been closed in the meanwhile. Does the problem still occur with the Okular version in current Debian unstable/testing? If so, could you please provide more detailed steps how to reproduce and possibly attach a PDF document that is affected? (If I understand correctly, the use case which breaks for you is printing an A4 document to A4 paper, which has been working fine for me so far.) Regards, Michael
Bug#886733: okular fails to render some text
reassign 886733 libpoppler64 found 886733 poppler/0.48.0-2+deb9u1 notfound 886733 okular/4:16.08.2-1 thanks Hi, getting over the Debian patches added with the latest security update, I realized that patch "CVE-2017-14519.patch" causes the problem of the text disappearing (with the PDF document I tested with). When I build the package without that patch, the text is there again. On 2018-01-12 20:11, Carsten Knoll wrote: > Questions: is there a reasonable way to change the library okular uses? > I.e. compiling poppler by myself or undo the update? As a workaround for now, you could for example * reinstall the old version (0.48.0-2) of the Poppler packages (you can explicitly specify the version number to use using `apt install PACKAGENAME1=0.48.0-2 PACKAGENAME2=0.48.0-2 [...]`). Note that you will probably have to specify all currently installed Poppler packages since they have dependencies on each other. (You will however probably get the version from stretch-security again after a while if you have unattended-upgrades enabled, which your video suggests). * rebuild the package from stretch-security with the patch mentioned above removed. (Please let me know in case you need further details on this.) > Why is evince not affected? AFAK it also uses poppler? I am not sure. AFAIK, poppler also has parts that are specific to Qt (which Okular uses) and GLib (which evince uses) for example. It might be something there or Evince uses other functions in some places or ... > Currently this bug is associated with package okular. > Shouldn't it be associated with some poppler-package? If so, with which one? Yes, I think it should be reassigned. This email should cause the bug to be reassigned to package "libpoppler64" for now. (I am not totally sure whether it is actually the correct binary package, so if anybody knows better, please feel free to correct this if it is relevant.) Regards, Michael
Bug#886733: okular fails to render some text
Just a note: #886798 seems to describe the same problem for oldstable.
Regards,
Michael
On 2018-01-09 12:22, Semyon Glazyrin wrote:
> Package: okular
> Version: 4:16.08.2-1+b1
> Severity: normal
>
> Dear Maintainer,
>
> After latest upgrade of popper:
>
> [UPGRADE] libpoppler-glib8:amd64 0.48.0-2 -> 0.48.0-2+deb9u1
> [UPGRADE] libpoppler-qt4-4:amd64 0.48.0-2 -> 0.48.0-2+deb9u1
> [UPGRADE] libpoppler-qt5-1:amd64 0.48.0-2 -> 0.48.0-2+deb9u1
> [UPGRADE] libpoppler64:amd64 0.48.0-2 -> 0.48.0-2+deb9u1
>
> okular fails to render some text in documents.
>
> Way to reproduce: generate pdf-file with pdflatex
>
> \documentclass{article}
> \usepackage[utf8]{inputenc}
> \usepackage[russian]{babel}
>
> \begin{document}
> test
> \end{document}
>
> The text in the file compiled with pdflatex is not visible in okular, though
> evince, gv open it well.
>
> Thanks,
> Semyon Glazyrin
>
> -- System Information:
> Debian Release: 9.3
> APT prefers stable
> APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-4-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/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages okular depends on:
> ii kde-runtime 4:16.08.3-2
> ii libc6 2.24-11+deb9u1
> ii libfreetype62.6.3-3.2
> ii libjpeg62-turbo 1:1.5.1-2
> ii libkdecore5 4:4.14.26-2
> ii libkdeui5 4:4.14.26-2
> ii libkexiv2-114:15.04.3-1
> ii libkio5 4:4.14.26-2
> ii libkparts4 4:4.14.26-2
> ii libkprintutils4 4:4.14.26-2
> ii libkpty44:4.14.26-2
> ii libokularcore7 4:16.08.2-1+b1
> ii libphonon4 4:4.9.0-4
> ii libpoppler-qt4-40.48.0-2+deb9u1
> ii libqca2 2.1.1-4+b2
> ii libqimageblitz4 1:0.0.6-4+b2
> ii libqmobipocket1 4:16.08.0-1
> ii libqt4-dbus 4:4.8.7+dfsg-11
> ii libqt4-declarative 4:4.8.7+dfsg-11
> ii libqt4-svg 4:4.8.7+dfsg-11
> ii libqt4-xml 4:4.8.7+dfsg-11
> ii libqtcore4 4:4.8.7+dfsg-11
> ii libqtgui4 4:4.8.7+dfsg-11
> ii libsolid4 4:4.14.26-2
> ii libspectre1 0.2.8-1
> ii libstdc++6 6.3.0-18
> ii phonon 4:4.9.0-4
> ii zlib1g 1:1.2.8.dfsg-5
>
> Versions of packages okular recommends:
> ii cups-bsd 2.2.1-8
>
> Versions of packages okular suggests:
> ii ghostscript9.20~dfsg-3.2+deb9u1
> pn jovie
> ii okular-extra-backends 4:16.08.2-1+b1
> ii poppler-data 0.4.7-8
> ii texlive-binaries 2016.20160513.41080.dfsg-2
> pn unrar
>
> -- debconf-show failed
>
Bug#886557: okular: Poor rendering
Hi Laurent, does this happen for every PDF document or just for specific ones? Can you possibly attach one that is affected? I just tried quickly with one PDF document and did not see any real difference between the "old" Okular in testing and the one in unstable. Regards, Michael On Sun, 07 Jan 2018 17:32:58 +0100 laurent B wrote: > Package: okular > Version: 4:17.08.3-2 > Severity: important > Tags: upstream > > Dear Maintainer, > > Since last update of my system (buster/sid) the rendering of Okular is getting > pretty ugly. Letters look "pixelised". > It looks like a resolution problem : If I zoom the pixelation is still there > but represents a lower relative size with respect to the size of the letter. > It is specific to okular since evince or other are not concerned. > > > [...]
Bug#860360: okular: I can confirm the bug with czech accents. Create a folder with accents, place a pdf file inside, cannot open the pdf from Dolphin. If immediately try to open from okular, the p
On 2017-10-09 19:49, lp...@centrum.cz wrote: > I can confirm that this helped resolve the issue. Thank you very much! > Leos You're welcome. Thanks for the confirmation that this solved the issue! @Máximo: Do you still have the issue with Okular not being able to open PDF files if the path contains accents? Do the steps described below possibly also fix the problem for you? > Can you please try the following: > > * open a terminal > * run the following command there: "sudo dpkg-reconfigure locales" > * select "cs_CZ.UTF-8" and confirm so that the respective locale is > generated > > (There may be ways to generate the locales using the graphical user > interface instead, but that depends on the specific desktop environment > in use. Please let me know in case the above steps are not clear enough.) > Instead of selecting "cs_CZ.UTF-8", that might be something else in your case. Can you possibly post the output you get when you type the command "locale" on the command line? Regards, Michael
Bug#860360: okular: I can confirm the bug with czech accents. Create a folder with accents, place a pdf file inside, cannot open the pdf from Dolphin. If immediately try to open from okular, the p
Thanks for the additional information. As far as I understand it so far,
this is not really an Okular problem, but one of your locale settings.
Can you please try the following:
* open a terminal
* run the following command there: "sudo dpkg-reconfigure locales"
* select "cs_CZ.UTF-8" and confirm so that the respective locale is
generated
(There may be ways to generate the locales using the graphical user
interface instead, but that depends on the specific desktop environment
in use. Please let me know in case the above steps are not clear enough.)
Regards,
Michael
On 2017-10-05 18:21, lp...@centrum.cz wrote:
>
> I have more details. In my case, I had in System settings -> Regional
> settings -> Formats:
> Region: United States - American English (en_US)
> Detailed settings enabled and time format set to Czech (cs_CZ). With
> this particular settings I can reproduce the problem plus I get the
> errors with locale. Once I switch this settings to "No change" are
> logout and log back in, Okular opens pdf files in a path with accents
> without a problem. I have confirmed it twice.
>
>
>
> The locale outputs with the time set to "No change":
>
> LANG=en_US.UTF-8
> LANGUAGE=
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=
>
> and this is the output of locale when I change time format to czech
> (with region en_US):
>
> locale: Cannot set LC_ALL to default locale: No such file or directory
> LANG=en_US.UTF-8
> LANGUAGE=
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME=cs_CZ.UTF-8
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=
>
>
>
> Leos
>
>
>
> __
>> Od: Michael Weghorn
>> Komu: Leoš Pohl , 860...@bugs.debian.org
>> Datum: 04.10.2017 21:18
>> Předmět: Re: Bug#860360: okular: I can confirm the bug with czech accents.
>>
> Hi Leoš,
>
> thanks for reporting that you also have this issue.
>
> On 2017-10-04 18:42, Leoš Pohl wrote:
>>
>> -- debconf information:
>> perl: warning: Setting locale failed.
>> perl: warning: Please check that your locale settings:
>> LANGUAGE = "",
>> LC_ALL = (unset),
>> LC_TIME = "cs_CZ.UTF-8",
>> LANG = "en_US.UTF-8"
>> are supported and installed on your system.
>> perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
>> locale: Cannot set LC_ALL to default locale: No such file or directory
>>
>
> The above output indicates that something seems to be wrong with your
> locale settings.
>
> Can you please post the output of the command "locale"?
>
> Does the problem go away if the respective locales are generated?
> You can have them generated by running the command "dpkg-reconfigure"
> (with root privileges) and selecting the corresponding locales. (The
> above output suggests that those are "cs_CZ.UTF-8" and "en_US.UTF-8" in
> your case.)
>
>
> Regards,
> Michael
>
Bug#860360: okular: I can confirm the bug with czech accents. Create a folder with accents, place a pdf file inside, cannot open the pdf from Dolphin. If immediately try to open from okular, the path
Hi Leoš,
thanks for reporting that you also have this issue.
On 2017-10-04 18:42, Leoš Pohl wrote:
>
> -- debconf information:
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = "",
> LC_ALL = (unset),
> LC_TIME = "cs_CZ.UTF-8",
> LANG = "en_US.UTF-8"
> are supported and installed on your system.
> perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
> locale: Cannot set LC_ALL to default locale: No such file or directory
>
The above output indicates that something seems to be wrong with your
locale settings.
Can you please post the output of the command "locale"?
Does the problem go away if the respective locales are generated?
You can have them generated by running the command "dpkg-reconfigure"
(with root privileges) and selecting the corresponding locales. (The
above output suggests that those are "cs_CZ.UTF-8" and "en_US.UTF-8" in
your case.)
Regards,
Michael
Bug#876494: okular: FTBFS: dh_install reports missing files
Hi, I had a look at this. The relevant parts from the build log are probably the following: ~~~ [...] Setting up libqmobipocket-dev (4:16.08.0-1) ... [...] CMake Warning at generators/CMakeLists.txt:85 (find_package): Could not find a configuration file for package "QMobipocket" that is compatible with requested version "2". The following configuration files were considered but not accepted: /usr/lib/cmake/QMobipocket/QMobipocketConfig.cmake, version: unknown [...] -- The following OPTIONAL packages have not been found: * Qt5TextToSpeech * QMobipocket (required version >= 2) [...] ~~~ As can be seen from above, the old version 4:16.08.0-1 of the build dependency "libqmobipocket-dev" was used during the build. The new version 4:17.08.1-1 had been uploaded to experimental only a few seconds before uploading the new okular package (s. https://tracker.debian.org/news/873145) and was therefore probably not available during the build. I can reproduce the problem when using that old version of "libqmobipocket-dev". The problem goes away when the new version 4:17.08.1-1 of libqmobipocket-dev from experimental is installed. Therefore, a rebuild should basically fix the problem. I think a versioned build-dependency should be added. Regards, Michael
Bug#869663: [okular] Review tools should not be automatically switched off right after used
Hi Antonio, On 2017-07-25 22:45, Antonio Marcos López Alonso wrote: > 2) is exactly the behavior I was looking for and I regret I couldn't find it > out before. My bad. > > Thanks a lot for pointing this out for me and also I apologize for the > unnecessary noise (so you might want to close this issue). > Thank you for your quick reply! I am glad to read this is what you were looking for. I am therefore closing the bug report as you suggested. Regards, Michael
Bug#869663: [okular] Review tools should not be automatically switched off right after used
Hi Antonio, when you use the mouse instead of the keyboard shortcut to select the highlighter, you have (at least) two options: 1) When you enable the highlighter using a single mouse click, the behaviour is as you described. 2) When you enable the highlighter using a double mouse click, the highlighter remains active and is not automatically unselected after you highlight a single passage of text. Is 2) basically the behaviour you wish to have? If so, is it sufficient as it is implemented now? Otherwise: Can you possibly give some more details on your suggestion to add a manual toggling option? Can you make a proposal on where exactly it might be added and how the the user would interact with (enable/disable) it? Regards, Michael Am 2017-07-25 14:37 schrieb Antonio Marcos López Alonso: Package: okular Version: 4:16.08.2-1+b1 Severity: wishlist --- Please enter the report below this line. --- Everytime I select and use one of the review (F6) tools it turns automatically unselected right after being used. For instance: 1) Select the highlighter (F4). 2) Highlight some PDF text. 3) Try to highlight some other text in the same file (either in the same page or other). I'm forced to press F4 again as highlighter toggled unselected right after step 2 which is quite awkward. So I'm requesting to add a manual toggling setup option to Review tools. Regards, Antonoo --- System information. --- Architecture: Kernel: Linux 4.11.0-1-amd64 Debian Release: buster/sid 500 testing ftp.es.debian.org 500 stable dl.google.com --- Package information. --- Depends (Version) | Installed ===-+-= libokularcore7 (= 4:16.08.2-1+b1) | 4:16.08.2-1+b1 kde-runtime (>> 4:4.10) | 4:16.08.3-2 libc6 (>= 2.14) | libfreetype6 (>= 2.2.1) | libjpeg62-turbo (>= 1.3.1) | libkdecore5 (>= 4:4.14) | libkdeui5 (>= 4:4.14) | libkexiv2-11 (>= 4:4.5.90) | libkio5 (>= 4:4.14) | libkparts4 (>= 4:4.14) | libkprintutils4 (>= 4:4.14) | libkpty4(>= 4:4.14) | libphonon4 (>= 4:4.6.0really4.3.80) | libpoppler-qt4-4(>= 0.38.0) | libqca2 (>= 2.0.2) | libqimageblitz4(>= 1:0.0.4) | libqmobipocket1 (>= 4:4.11.80) | libqt4-dbus(>= 4:4.6.1) | libqt4-declarative (>= 4:4.7.0~rc1) | libqt4-svg (>= 4:4.5.3) | libqt4-xml (>= 4:4.5.3) | libqtcore4 (>= 4:4.8.0) | libqtgui4 (>= 4:4.8.0) | libsolid4 (>= 4:4.14) | libspectre1 (>= 0.2.3) | libstdc++6 (>= 5) | phonon | zlib1g (>= 1:1.1.4) | Recommends (Version) | Installed =-+-=== cups-bsd | 2.2.4-2 Suggests (Version) | Installed -+-=== ghostscript | 9.21~dfsg-1 jovie| 4:16.08.0-1+b1 okular-extra-backends (= 4:16.08.2-1+b1) | 4:16.08.2-1+b1 poppler-data | 0.4.7-8 texlive-binaries | 2017.20170613.44572-3 unrar| 1:5.5.5-1
Bug#860360: [Okular] could not open pdf from context menu whether pdf file or path has accents
https://bugs.kde.org/show_bug.cgi?id=358289 seems to be a corresponding upstream bug.
Bug#868763: okular: Please package new upstream version
Package: okular Version: 4:16.08.2-1+b1 Severity: wishlist Dear Maintainer, Debian currently contains Okular version 16.08.2, which is still KDE 4/Qt 4 based. The current upstream version is 17.04.3. Among other changes, this version has been ported to Frameworks 5. It would be great if Debian could include the current upstream version. Note: KDE Neon provides up-to-date versions built from their CI system; maybe having a look at their packaging might help. The git repository is available at git://anongit.neon.kde.org/applications/okular Regards, Michael -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages okular depends on: ii kde-runtime 4:16.08.3-2 ii libc6 2.24-12 ii libfreetype62.8-0.2 ii libjpeg62-turbo 1:1.5.1-2 ii libkdecore5 4:4.14.26-2 ii libkdeui5 4:4.14.26-2 ii libkexiv2-114:15.04.3-1 ii libkio5 4:4.14.26-2 ii libkparts4 4:4.14.26-2 ii libkprintutils4 4:4.14.26-2 ii libkpty44:4.14.26-2 ii libokularcore7 4:16.08.2-1+b1 ii libphonon4 4:4.9.0-4 ii libpoppler-qt4-40.48.0-2 ii libqca2 2.1.3-1 ii libqimageblitz4 1:0.0.6-5 ii libqmobipocket1 4:16.08.0-1 ii libqt4-dbus 4:4.8.7+dfsg-11 ii libqt4-declarative 4:4.8.7+dfsg-11 ii libqt4-svg 4:4.8.7+dfsg-11 ii libqt4-xml 4:4.8.7+dfsg-11 ii libqtcore4 4:4.8.7+dfsg-11 ii libqtgui4 4:4.8.7+dfsg-11 ii libsolid4 4:4.14.26-2 ii libspectre1 0.2.8-1 ii libstdc++6 7.1.0-9 ii phonon 4:4.9.0-4 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages okular recommends: ii cups-bsd 2.2.4-2 Versions of packages okular suggests: ii ghostscript9.21~dfsg-1 pn jovie pn okular-extra-backends ii poppler-data 0.4.7-8 ii texlive-binaries 2017.20170613.44572-3 pn unrar -- no debconf information
Bug#860360: [Okular] could not open pdf from context menu whether pdf file or path has accents
Hi Máximo, I tried to reproduce the described issue with current Debian sid/unstable, but was unable to do so. What I did: 1) create some PDF file (using LibreOffice) under the path you mentioned $ ls -l /home/user00/Documents/Books/FÃsica/Estadisticas/Fundamentals_of_Statistical_And_Thermal_Physics-F_Reif.pdf -rw-r--r-- 1 user00 user00 7083 Jul 18 11:33 /home/user00/Documents/Books/FÃsica/Estadisticas/Fundamentals_of_Statistical_And_Thermal_Physics-F_Reif.pdf 2) Open the directory in Dolphin (KDE's file manager) 3) Open the file using right click in the file manager -> "Open with" -> "Okular" For me, the file opened file and was displayed in Okular as expected. I am not sure whether the steps I took are exactly the same ones that you took. Can you possibly give some more information about that? Are you also using Dolphin (KDE's file manager) or possibly another file manager? Regards, Michael
