Bug#870612: libreoffice-writer: Border line style control not a11y accessible

2023-08-22 Thread Michael Weghorn

Hi,

On Thu, 3 Aug 2017 13:33:01 +0200 Alex ARNAUD  wrote:

Forwarded: https://bugs.documentfoundation.org/show_bug.cgi?id=101886

DESCRIPTION FROM UPSTREAM:
> The border line style control (svtlo-LineListBox) found in the border tab in 
most dialogs isnt accessible with a screen reader and labels need to be added to 
each entry similar to line properties styles control (svxlo-LineLB).


this is fixed upstream now, see the LibreOffice bug report for more details.

Best regards,
Michael


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1019740: libreoffice: Please package the qt6 VCL plugin

2022-09-14 Thread Michael Weghorn
Package: libreoffice
Version: 1:7.4.1~rc1-3+b1
Severity: wishlist
X-Debbugs-Cc: m.wegh...@posteo.de

Dear Maintainer,

a Qt 6 based UI variant (VCL plugin) was added to LibreOffice in this commit:
https://git.libreoffice.org/core/commit/88d57cf241209ffec9eaed3e523942ab51af6db6

It is the Qt 6 variant of the "qt5" VCL plugin (autogen option '--enable-qt5')
and shares almost all code with it.

The qt6 VCL plugin can be enabled by the '--enable-qt6' autogen option.

It would be nice if the qt6 VCL plugin were packaged in Debian as well.

Best regards,
Michael

PS: The trigger for this request is a question in LO Bugzilla:
https://bugs.documentfoundation.org/show_bug.cgi?id=145734#c2

The qt6 VCL plugin was never mentioned in the official LO release notes, since
it was initially mostly meant to be used for own experimenting before making it
official, but at least from my (developer's) experience, I haven't run into any
issues that are specific to the qt6 VCL plugin (as compared to the qt5/kf5 one)
for a while when used together with recent versions of Qt 6.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
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 libreoffice depends on:
ii  libreoffice-base1:7.4.1~rc1-3+b1
ii  libreoffice-calc1:7.4.1~rc1-3+b1
ii  libreoffice-core1:7.4.1~rc1-3+b1
ii  libreoffice-draw1:7.4.1~rc1-3+b1
ii  libreoffice-impress 1:7.4.1~rc1-3+b1
ii  libreoffice-math1:7.4.1~rc1-3+b1
ii  libreoffice-report-builder-bin  1:7.4.1~rc1-3+b1
ii  libreoffice-writer  1:7.4.1~rc1-3+b1
ii  python3-uno 1:7.4.1~rc1-3+b1

Versions of packages libreoffice recommends:
ii  fonts-crosextra-caladea 20130214-2.1
ii  fonts-crosextra-carlito 20130920-1.1
ii  fonts-dejavu2.37-2
ii  fonts-liberation1:1.07.4-11
ii  fonts-liberation2   2.1.5-1
ii  fonts-linuxlibertine5.3.0-6
ii  fonts-noto-core 20201225-1
ii  fonts-noto-extra20201225-1
ii  fonts-noto-mono 20201225-1
ii  fonts-noto-ui-core  20201225-1
ii  fonts-sil-gentium-basic 1.102-1.1
ii  libreoffice-java-common 1:7.4.1~rc1-3
ii  libreoffice-nlpsolver   0.9+LibO7.4.1~rc1-3
ii  libreoffice-report-builder  1:7.4.1~rc1-3
ii  libreoffice-script-provider-bsh 1:7.4.1~rc1-3
ii  libreoffice-script-provider-js  1:7.4.1~rc1-3
ii  libreoffice-script-provider-python  1:7.4.1~rc1-3
ii  libreoffice-sdbc-mysql  1:7.4.1~rc1-3+b1
ii  libreoffice-sdbc-postgresql 1:7.4.1~rc1-3+b1
ii  libreoffice-wiki-publisher  1.2.0+LibO7.4.1~rc1-3

Versions of packages libreoffice suggests:
ii  cups-bsd 2.4.2-1+b1
ii  default-jre [java8-runtime]  2:1.11-72
ii  firefox-esr  102.2.0esr-1
ii  ghostscript  9.56.1~dfsg-1
ii  gnupg2.2.39-1
pn  gpa  
ii  gstreamer1.0-libav   1.20.3-1+b1
ii  gstreamer1.0-plugins-bad 1.20.3-2
ii  gstreamer1.0-plugins-base1.20.3-2
ii  gstreamer1.0-plugins-good1.20.3-1
ii  gstreamer1.0-plugins-ugly1.20.3-1
ii  hunspell-de-de-frami [hunspell-dictionary]   1:7.4.0~rc2-4
ii  hunspell-en-gb [hunspell-dictionary] 1:7.4.0~rc2-4
ii  hunspell-en-us [hunspell-dictionary] 1:2020.12.07-2
ii  hunspell-es [hunspell-dictionary]1:7.4.0~rc2-4
ii  hunspell-fr-classical [hunspell-dictionary]  1:7.0-1
ii  hunspell-it [hunspell-dictionary]1:7.4.0~rc2-4
ii  hunspell-pt-br [hunspell-dictionary] 1:7.4.0~rc2-4
ii  hunspell-pt-pt [hunspell-dictionary] 1:7.4.0~rc2-4
ii  hyphen-de [hyphen-hyphenation-patterns]  1:7.4.0~rc2-4
ii  hyphen-en-gb [hyphen-hyphenation-patterns]   1:7.4.0~rc2-4
ii  hyphen-en-us [hyphen-hyphenation-patterns]   2.8.8-7
ii  hyphen-es [hyphen-hyphenation-patterns]  1:7.4.0~rc2-4
ii  hyphen-fr [hyphen-hyphenation-patterns]  1:7.4.0~rc2-4
ii  hyphen-it [hyphen-hyphenation-patterns]  1:7.4.0~rc2-4
ii  imagemagick  8:6.9.11.60+dfsg-1.3+b3
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.3+b3
ii  libgl1   1.5.0-1
pn  libofficebean-java   
pn  libreoffice-grammarcheck 
ii  libreoffice-help-de 

Bug#993574: python3-virtualsmartcard: Cannot import virtualsmartcard module

2022-08-08 Thread Michael Weghorn
(...) With this in place, I still ran into another problem, 
described in upstream issue 
https://github.com/frankmorgner/vsmartcard/issues/218

("ModuleNotFoundError: No module named 'sha'").
With a logical backport of the suggested upstream PR 
https://github.com/frankmorgner/vsmartcard/pull/228 , running `vicc` 
then works without errors for me. Backport in the patch-queue branch of 
my local package looks like this:

(...)


FWIW, that upstream pull request has been merged now.



Bug#993574: python3-virtualsmartcard: Cannot import virtualsmartcard module

2022-07-23 Thread Michael Weghorn

Hi,

is there any chance to get a fixed package released sometime soon?

The following change fixed this for me in a local rebuild of the 
package, but there might be a better way to handle it:


diff --git a/debian/python3-virtualsmartcard.install 
b/debian/python3-virtualsmartcard.install

index 47ee4d3..ded283b 100644
--- a/debian/python3-virtualsmartcard.install
+++ b/debian/python3-virtualsmartcard.install
@@ -1 +1 @@
-usr/lib/python3.*/site-packages/virtualsmartcard 
/usr/lib/python3/site-packages/virtualsmartcard
+usr/lib/python3.*/site-packages/virtualsmartcard 
usr/lib/python3/dist-packages/



Side note: With this in place, I still ran into another problem, 
described in upstream issue 
https://github.com/frankmorgner/vsmartcard/issues/218

("ModuleNotFoundError: No module named 'sha'").
With a logical backport of the suggested upstream PR 
https://github.com/frankmorgner/vsmartcard/pull/228 , running `vicc` 
then works without errors for me. Backport in the patch-queue branch of 
my local package looks like this:


diff --git a/virtualsmartcard/src/vpicc/virtualsmartcard/CryptoUtils.py 
b/virtualsmartcard/src/vpicc/virtualsmartcard/CryptoUtils.py

index 56e0ed4..552cff1 100644
--- a/virtualsmartcard/src/vpicc/virtualsmartcard/CryptoUtils.py
+++ b/virtualsmartcard/src/vpicc/virtualsmartcard/CryptoUtils.py
@@ -27,12 +27,11 @@ from virtualsmartcard.utils import inttostring
 try:
 # Use PyCrypto (if available)
 from Crypto.Cipher import DES3, DES, AES, ARC4  # @UnusedImport
-from Crypto.Hash import HMAC, SHA as SHA1
+from Crypto.Hash import HMAC

 except ImportError:
 # PyCrypto not available.  Use the Python standard library.
 import hmac as HMAC
-import sha as SHA1

 CYBERFLEX_IV = b'\x00' * 8


Best regards,
Michael



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1002857: Bug #995810: libgoogle-glog-dev: Dependency on libunwind-dev

2022-01-05 Thread Michael Weghorn

Hi,

On Thu, 30 Dec 2021 11:11:43 +0100 Marc Glisse 
 wrote:

Package: libgoogle-glog-dev
Version: 0.5.0+really0.4.0-2
Severity: normal

Dear Maintainer,

with the switch to llvm-13 in testing, installing libgoogle-glog-dev has
become problematic, it depends on libunwind-dev, but that conflicts with
libunwind-13-dev.
I couldn't find an official doc on what the LLVM
maintainers expect, but it looks like depending on libunwind-x.y-dev may
work. I didn't test it though, some libunwind files seem to have moved,
and I may have completely misunderstood the relation between the various
libunwind packages.


I have run into a similar problem with the libgstreamer1.0-dev package, 
which can no longer be installed in parallel with libc++-dev because


* libc++-dev depends on libc++-13-dev, which depends on 
libunwind-13-dev, which breaks libunwind-dev

* libgstreamer1.0-dev depends on libunwind-dev

As far as I can see, two relevant commits in the LLVM packaging git repo 
on the way to the current situation are:


* Commit c72a6c0e50e318c83e6bff901dd0e2e591f65145 [1], "Generate 
libunwind-12 & libunwind-12-dev packages", which added the 
libunwind--dev package with a "Breaks" on libunwind-dev
* Commit 103cb1357c55b508e283d329083119d2429029ca [2], "libc++-13-dev 
should depends on libunwind-13-dev (Closes: #995810)", which added the 
corresponding dependency


Can the LLVM packaging team possibly give a hint what is the intended 
way to deal with the situation?
(I would then open a bug report for libgstreamer1.0-dev with the 
relevant information as well if something has to be done there)?


Best regards,
Michael


[1] 
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/c72a6c0e50e318c83e6bff901dd0e2e591f65145
[2] 
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/103cb1357c55b508e283d329083119d2429029ca




Bug#994057: #994057,libegl-mesa0: 21.2.1-2 with intel graphic card produces artifact on firefox-esr

2021-11-18 Thread Michael Weghorn



Hello,

On 09/11/2021 03.45, Patrick Häcker wrote:

I tested the Mesa upstream version from https://gitlab.freedesktop.org/mesa/
mesa/-/tree/main and can confirm the broken version there, too.

However: I didn't get any artifacts with mesa-21.3.0-rc4. I didn't bisect that
as mesa-21.2.5 has the artifacts and it does not matter which rc fixes it.

So we probably need our pinning in /etc/apt/preferences

Package: libegl-mesa0 libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0
Pin: version 21.2.*
Pin-Priority: -1

for some more days until 21.3.0 is released and if that gets packaged quickly,
the problem should probably be gone soon.


thanks. I can confirm my issues are gone after upgrading to 21.3.0~rc5-1 
from experimental.


Kind regards,
Michael



Bug#994057: #994057,libegl-mesa0: 21.2.1-2 with intel graphic card produces artifact on firefox-esr

2021-11-03 Thread Michael Weghorn



Hello,

On Fri, 17 Sep 2021 14:15:50 +0200 Sylvain Tgz  > 
This bug couldn't be related between libraries and hardware ?


I found newer application with artifact : VLC, simplescreenrecorder


I'm having this issue on Debian testing as well, after an upgrade of 
Mesa packages from 20.3.5-1 to 21.2.4-1.
The problem disappears after downgrading to version 20.3.5-1 of the 
packages and rebooting (packages in my case: libegl-mesa0 
libegl1-mesa-dev libgl1-mesa-dev libgl1-mesa-dri libglapi-mesa 
libglx-mesa0 mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers 
libgbm1 libgbm-de).


Testing with versions in between from snapshot.debian.org reveals that 
it's still OK with 21.1.6-1 and the issue starts with 21.2.0-1.


Other related reports that look like they might be about the same 
problem, all related to Mesa 21.2 (I'm seeing artifacts in Firefox and 
in Konsole as described, as well as in other applications):


https://forum.manjaro.org/t/konsole-tmux-rendering-problems-horizontal-stripes/86975
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1944951

Graphics card info from 'hwinfo' output:

49: PCI 02.0: 0300 VGA compatible controller (VGA)
  [Created at pci.386]
  Unique ID: _Znp.A3c8F1k8IIB
  SysFS ID: /devices/pci:00/:00:02.0
  SysFS BusID: :00:02.0
  Hardware Class: graphics card
  Device Name: "Onboard IGD"
  Model: "Intel UHD Graphics 630 (Mobile)"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x3e9b "UHD Graphics 630 (Mobile)"
  SubVendor: pci 0x103c "Hewlett-Packard Company"
  SubDevice: pci 0x8610
  Revision: 0x02
  Driver: "i915"
  Driver Modules: "i915"
  Memory Range: 0xe400-0xe4ff (rw,non-prefetchable)
  Memory Range: 0xa000-0xafff (ro,non-prefetchable)
  I/O Ports: 0x4000-0x403f (rw)
  Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled)
  IRQ: 166 (44948 events)
  Module Alias: "pci:v8086d3E9Bsv103Csd8610bc03sc00i00"
  Driver Info #0:
Driver Status: i915 is active
Driver Activation Cmd: "modprobe i915"
  Config Status: cfg=new, avail=yes, need=no, active=unknown


Michael



Bug#979577: qtcreator: Clang Code Model no longer finds 'stddef.h' since version 4.14.0-2

2021-01-08 Thread Michael Weghorn



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

2021-01-08 Thread Michael Weghorn
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

2020-07-20 Thread Michael Weghorn
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

2020-04-01 Thread Michael Weghorn
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/debian/control
@@ -7,7 +7,6 @@ U

Bug#917522: pcmanfm: Some keyboard navigation shortcuts in PCManFM no longer working

2020-02-23 Thread Michael Weghorn
tags 917522 + fixed-upstream
thanks

On 23/02/2020 10.24, Kurt Meyer wrote:
> When will this get fixed or is it even fixable? It's been over a year.

The bug has already been fixed upstream. s. previous comments, but the
Debian package does not yet contain the fix.



signature.asc
Description: OpenPGP digital signature


Bug#951325: rr: Changed path for librrpreload{,_32}.so causes problems

2020-02-14 Thread Michael Weghorn
ags:"rw-p", file_offset:0x27000, device:64769, 
inode:5636228, data_file:"/lib/x86_64-linux-gnu/ld-2.29.so", 
data_offset:0x27000, file_size:0x29700 }
  { map_file:"", addr:0x7ff683478000, length:0x1000, prot_flags:"rw-p", 
file_offset:0x0, device:0, inode:0, data_file:"", data_offset:0x0, 
file_size:0x0 }
  { map_file:"[vdso]", addr:0x7ffe01dfe000, length:0x1000, 
prot_flags:"r-xp", file_offset:0x0, device:0, inode:0, data_file:"", 
data_offset:0x0, file_size:0x0 }
  { map_file:"", addr:0x6800, length:0x20, prot_flags:"rwxp", 
file_offset:0x0, device:0, inode:0, data_file:"", data_offset:0x0, 
file_size:0x0 }
  { tid:671731, addr:0x7ffe01dd7000, length:0x22000 }
  { tid:671731, addr:0x555d1550b000, length:0x2000 }
  { tid:671731, addr:0x7ff683478000, length:0x1000 }
  { tid:671731, addr:0x7ffe01dfe000, length:0x1000 }
  { tid:671731, addr:0x555d154ef000, length:0x1000 }
  { tid:671731, addr:0x555d15501000, length:0x1000 }
  { tid:671731, addr:0x555d15507000, length:0x1000 }
  { tid:671731, addr:0x555d1550a000, length:0x1000 }
  { tid:671731, addr:0x7ff68344e000, length:0x1000 }
  { tid:671731, addr:0x7ff68346d000, length:0x1000 }
  { tid:671731, addr:0x7ff683475000, length:0x1000 }
  { tid:671731, addr:0x7ff683477000, length:0x1000 }
  { tid:671731, addr:0x7ffe01dfe8f0, length:0xb }
  { tid:671731, addr:0x7ffe01dfe850, length:0xb }
  { tid:671731, addr:0x7ffe01dfe8e0, length:0xb }
  { tid:671731, addr:0x7ffe01dfe9b0, length:0xb }
  { tid:671731, addr:0x7ffe01dfe568, length:0x11c }
  { tid:671731, addr:0x7ffe01dfe520, length:0x44 }
  { tid:671731, addr:0x7ffe01dfe4c0, length:0x60 }
}
{
  real_time:28495.888457 global_time:83128, event:`INSTRUCTION_TRAP' 
tid:671731, ticks:849
rax:0xd6f75186 rbx:0x0 rcx:0x rdx:0x4334 rsi:0x0 
rdi:0x7ffe01df5e00 rbp:0x7ffe01df5df0 rsp:0x7ffe01df5d90 r8:0x0 r9:0x0 r10:0x0 
r11:0x246 r12:0x0 r13:0x0 r14:0x0 r15:0x7ffe01df5e00 rip:0x7ff68344fe96 
eflags:0x10206 cs:0x33 ss:0x2b ds:0x0 es:0x0 fs:0x0 gs:0x0 
orig_rax:0x fs_base:0x0 gs_base:0x0
}
=== Start rr backtrace:
rr(_ZN2rr13dump_rr_stackEv+0x41)[0x558b01430631]
rr(_ZN2rr9GdbServer15emergency_debugEPNS_4TaskE+0x625)[0x558b0134abf5]
rr(+0xb1581)[0x558b0135b581]
rr(_ZN2rr21EmergencyDebugOstreamD2Ev+0x75)[0x558b0135b745]

rr(_ZN2rr4Task17read_bytes_helperENS_10remote_ptrIvEElPvPb+0xb0)[0x558b014137c0]
rr(+0x13479c)[0x558b013de79c]
rr(+0x139e52)[0x558b013e3e52]

rr(_ZN2rr19rep_process_syscallEPNS_10ReplayTaskEPNS_15ReplayTraceStepE+0xf5)[0x558b013e4905]

rr(_ZN2rr13ReplaySession28setup_replay_one_trace_frameEPNS_10ReplayTaskE+0x705)[0x558b013d5125]

rr(_ZN2rr13ReplaySession11replay_stepERKNS0_15StepConstraintsE+0xba)[0x558b013d524a]

rr(_ZN2rr14ReplayTimeline19replay_step_forwardENS_10RunCommandEl+0xcb)[0x558b013ee65b]
rr(_ZN2rr9GdbServer14debug_one_stepERNS_10GdbRequestE+0xfde)[0x558b0134d58e]

rr(_ZN2rr9GdbServer12serve_replayERKNS0_15ConnectionFlagsE+0x6eb)[0x558b0134e54b]
rr(+0x121129)[0x558b013cb129]

rr(_ZN2rr13ReplayCommand3runERSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE+0x4ca)[0x558b013cc98a]
rr(main+0x27a)[0x558b013003ea]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7fe6dac0]
rr(_start+0x2a)[0x558b0130051a]
=== End rr backtrace
Launch gdb with
  gdb '-l' '1' '-ex' 'set sysroot /' '-ex' 'target extended-remote 
127.0.0.1:16536' /usr/lib/libreoffice/program/soffice.bin


-- 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-3-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 rr depends on:
ii  libc6   2.29-10
ii  libc6-i386  2.29-10
ii  libcapnp-0.7.0  0.7.0-5
ii  libgcc1 1:9.2.1-25
ii  libstdc++6  9.2.1-25
ii  python3 3.7.5-3

rr recommends no packages.

rr suggests no packages.

-- no debconf information
>From 750c9896e9b24b1c6eab8be547716ccc5dee8f39 Mon Sep 17 00:00:00 2001
From: Michael Weghorn 
Date: Fri, 14 Feb 2020 13:30:45 +0100
Subject: [PATCH] d/rules: Move librrpreload* to /usr/lib/rr

rr expects the two libraries 'librrpreload.so' and
'librrpreload_32.so' there, so make sure that they are
there.

This also requires to run 'dh_python3' with the
'--no-ext-rename' arg, since it would otherwise rename
those like this (in an amd64 build):

I: dh_python3 fs:343: renaming librrpreload.so to 
librrpreload.cpython-37m-x86_64-linux-gnu.so
I: dh_python3 fs:343: renaming librrpreload_32.so to 
li

Bug#941686: backintime-qt: Version 1.2.1-1 has wrong dependency on qt4 python3-dbus.mainloop

2019-10-03 Thread Michael Weghorn
Package: backintime-qt
Version: 1.2.1-1
Severity: normal
Tags: patch

Dear Maintainer,

backintime 1.2.1-1, which is currently in the NEW queue, switched from
Qt 4 to Qt 5.

However, the package still declares a (wrong) dependency on the qt4-based 
package
'python3-dbus.mainloop.qt', which should be replaced by the qt5 version,
'python3-dbus.mainloop.pyqt5' that is now being used.

Best regards,
Michael

PS: Thanks for packaging the new version!


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-2-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages backintime-qt depends on:
ii  backintime-common1.2.1-1
ii  libnotify-bin0.7.8-1
ii  policykit-1  0.105-26
ii  python3  3.7.3-1
ii  python3-dbus.mainloop.pyqt5  5.12.3+dfsg-2
ii  python3-pyqt55.12.3+dfsg-2
ii  x11-utils7.7+4

Versions of packages backintime-qt recommends:
ii  python3-secretstorage  2.3.1-2

Versions of packages backintime-qt suggests:
ii  meld  3.20.0-2

-- no debconf information
>From 4d9751c7d215ebdd56f14239d6edfd0e1db78b19 Mon Sep 17 00:00:00 2001
From: Michael Weghorn 
Date: Thu, 3 Oct 2019 21:26:56 +0200
Subject: [PATCH] d/control: Update python3-dbus.mainloop dep for qt5

Package 'python3-dbus.mainloop.qt' is the qt4 version,
while backintime now uses qt5.

To demonstrate the issue:

$ python3 /usr/share/backintime/qt/serviceHelper.py
Traceback (most recent call last):
  File "/usr/share/backintime/qt/serviceHelper.py", line 74, in 
import dbus.mainloop.pyqt5
ModuleNotFoundError: No module named 'dbus.mainloop.pyqt5'
---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 9a19da2..6ea3eee 100644
--- a/debian/control
+++ b/debian/control
@@ -35,7 +35,7 @@ Architecture: all
 Breaks: backintime-kde (<< 1.1.6-1~), backintime-gnome (<< 1.1.6-1~), 
backintime-qt4 (<< 1.2.1-0.1~)
 Replaces: backintime-kde (<< 1.1.6-1~), backintime-gnome (<< 1.1.6-1~), 
backintime-kde4, backintime-qt4 (<< 1.2.1-0.1~)
 Conflicts: backintime-kde4
-Depends: x11-utils, libnotify-bin, python3-pyqt5, python3-dbus.mainloop.qt, 
policykit-1,
+Depends: x11-utils, libnotify-bin, python3-pyqt5, python3-dbus.mainloop.pyqt5, 
policykit-1,
  backintime-common (= ${source:Version}), ${python3:Depends}, ${misc:Depends}
 Recommends: python3-secretstorage
 Suggests: meld | kompare
-- 
2.23.0



Bug#911844: okular: Prints to the wrong printer

2019-06-15 Thread Michael Weghorn
> 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


Bug#911844: okular: Prints to the wrong printer

2019-06-15 Thread Michael Weghorn
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#920859: libreoffice-kde5: Crash when minimizing file save dialog

2019-01-30 Thread Michael Weghorn
Hi,

On 30/01/2019 22.34, Rene Engelhard wrote:
> Upstream says:
> 
> 14:44 < _rene_> bubli: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920859. known? (gtk3_kde5)
> 14:45 <@bubli> _rene_: Neven seen before
> 14:49 -!- NaveenNaidu_ [~NaveenNai@223.186.44.102] has quit [Ping timeout: 
> 268 seconds]
> 14:51 < mst___> caolan, so a) the clipboard locking in VclGtkClipboard looks 
> broken b) since LO 5.3, commit ed7e74ae1c7ecfc29df152a8397fb9f6e1763a60 works 
> around the breakage 
> because my extension here will always hold the SolarMutex now 
> so the main thread doesn't get a chance to run anyway
> 14:52 < IZBot> core - try to avoid the deadlock around the clipboard,  - 
> http://cgit.freedesktop.org/libreoffice/core/commit/?id=ed7e74ae1c7ecfc29df152a8397fb9f6e1763a60
> 14:52 -!- NaveenNaidu_ [~NaveenNai@223.186.44.102] has joined #libreoffice-dev
> 14:55 < michaelweghorn> _rene_: I can reproduce here and can take a look, but 
> probably not before next week

I have created an upstream bug and am currently working on a fix:
https://bugs.documentfoundation.org/show_bug.cgi?id=123077

Regards,
Michael



signature.asc
Description: OpenPGP digital signature


Bug#917522: pcmanfm: Some keyboard navigation shortcuts in PCManFM no longer working

2018-12-28 Thread Michael Weghorn
On 28/12/2018 07.25, Asho Yeh wrote:
> Package: pcmanfm
> Version: 1.3.1-1
> Severity: normal
> 
> a few keyboard shortcuts for navigating directories in PCManFM (Alt+Home 
> to
> return to ~/, Alt+Up to go to parent folder) no longer work.
> [...]

There's also an upstream bug for this that has a patch attached that's
waiting for review: https://sourceforge.net/p/pcmanfm/bugs/1085/

Best regards,
 Michael


PS: It seems that two bug reports were accidently created; #917523 has
the same content.



signature.asc
Description: OpenPGP digital signature


Bug#874973: [kprinter4] Future Qt4 removal from Buster

2018-07-29 Thread Michael Weghorn
Hi,

On 2018-07-29 10:55, Boyuan Yang wrote:
> [...]
> It seems that kprinter4 has stopped development since 2014 and there's no 
> sign 
> of porting to Qt5. I'm wondering if you will pick up this software and port 
> it 
> to Qt5 or if there's already a Qt5 counterpart around. If none of those will 
> happen, kprinter4 will have to be removed from Debian eventually together 
> with 
> Qt4.
> [...]
just a quick note: I did a port to Qt 5 and created the following
upstream diff a while ago (but there hasn't been too much activity...):
https://phabricator.kde.org/D9341

Regards,
Michael



signature.asc
Description: OpenPGP digital signature


Bug#873226: Okular doesnt load cups default options for printers

2018-05-02 Thread Michael Weghorn
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#874949: [kdiff3] Future Qt4 removal from Buster

2018-04-11 Thread Michael Weghorn
On 2018-04-11 19:47, Eike wrote:
> For KDiff3 QT, it would not be hard. For the KDE version, there's no upstream
> KDE 5 version and the upstream author doesn't have time to implement it. 
> There are people trying to create a KDE5 version, though. I'd prefer to 
> package that when/if it works. The alternative would be to deprecate the
> KDE version and just have kdiff3-qt.
> 

According to [1] (s.a. the links given there), kdiff3 is now a project
under the KDE umbrella. I haven't tested the version there yet, though,
and can't say anything about how well it works.


1:
https://www.phoronix.com/scan.php?page=news_item=KDiff3-Restored-And-Joins-KDE



Bug#815589: libokularcore6: okular sets fit-to-page option when printing

2018-03-09 Thread Michael Weghorn
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

2018-02-08 Thread Michael Weghorn
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

2018-02-07 Thread Michael Weghorn
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" <m.wegh...@posteo.de
> <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=135888
> <http://forums.debian.net/viewtopic.php?f=6=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

2018-02-07 Thread Michael Weghorn
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=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#888954: [Pkg-libvirt-maintainers] Bug#888954: libvirt-daemon: System freezes when restarting libvirtd while VM is running

2018-02-01 Thread Michael Weghorn
tags 888954 + fixed-upstream
thanks

On 2018-01-31 19:31, Michael Weghorn wrote:
> [...]
> In addition, there is a stack trace posted at
> https://lkml.org/lkml/2017/12/17/212 that looks very similar, so the fix
> referred to at https://lkml.org/lkml/2017/12/20/426 might fix the issue.

I rebuilt the kernel package with the mentioned fix added as an
additional patch and can confirm that this fixes the problem for me.
The corresponding upstream commit is this one:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=74d0833c659a8a54735e5efdd44f4b225af68586


Regards,
  Michael



Bug#888954: [Pkg-libvirt-maintainers] Bug#888954: libvirt-daemon: System freezes when restarting libvirtd while VM is running

2018-01-31 Thread Michael Weghorn
I did some further testing with older kernel versions from
snapshot.debian.org to identify from when on the problem occurs and
discovered 2 things:

1) The problem does not necessarily occur every single time. For some of
the affected kernel versions, I needed two or three attempts (with
reboots in between) to reproduce the issue.

2) The first affected kernel version is 4.14~rc3-1~exp1, while 4.13.13-1
still works without problems.

In addition, there is a stack trace posted at
https://lkml.org/lkml/2017/12/17/212 that looks very similar, so the fix
referred to at https://lkml.org/lkml/2017/12/20/426 might fix the issue.


Regards,
  Michael



Bug#888954: [Pkg-libvirt-maintainers] Bug#888954: libvirt-daemon: System freezes when restarting libvirtd while VM is running

2018-01-31 Thread Michael Weghorn
reassign 888954 linux-image-4.14.0-3-amd64 4.14.13-1
thanks

Hi,

On 2018-01-31 16:12, Guido Günther wrote:
> [...]
> This looks like a kernel bug. Please reassign to the appropriate
> package. I can restart libvirtd without issues with
> linux-image-4.14.0-3-amd64 (although 4.14.12-2).
> Cheers,
>  -- Guido
> 

Thanks for the super-quick reply.

As suggested, I am reassigning this to the respective kernel package.

Regards,
  Michael



Bug#888954: libvirt-daemon: System freezes when restarting libvirtd while VM is running

2018-01-31 Thread Michael Weghorn
Package: libvirt-daemon
Version: 4.0.0-1
Severity: important

Dear Maintainer,

when libvirtd is restarted while a VM is running, the system "freezes".

The following steps can be taken in order to reproduce the problem:

* Set up and start a virtual machine using `virt-install`, e.g. as follows:

$ wget 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.3.0-amd64-netinst.iso
$ virt-install --connect=qemu:///system --name demo --memory 500 --disk 
none --network none --livecd --cdrom debian-9.3.0-amd64-netinst.iso

* While the virtual machine is running, restart the libvirt daemon:

$ sudo systemctl restart libvirtd.service

This (almost always) leads to the system become "frozen", since a kernel
panic is caused. The output captured on another computer with the "netconsole"
module is given below.


The kernel package in use is linux-image-4.14.0-3-amd64, version 4.14.13-1.
systemd has version 237-1.


Please let me know in case I can provide any additional information that
can be of help.

Since libvirtd and the running VM are causing the kernel panic, I am
reporthing this for the "libvirt-daemon" package. Please let me know or
reassign to another package if this is incorrect.


Best regards,
  Michael


PS: I originally was faced with the problem when system freezes started
appearing from time to time when I was doing package updates, since
a systemd trigger causes `systemctl reload-daemon` to be called when
anything underneath `/etc/init.d` is changed...


--- START of output via netconsole on other computer 
$ nc -l -p 32769 -u
[...]

[  411.419936] BUG: unable to handle kernel NULL pointer dereference at 
00b0
[  411.419949] IP: pids_free+0x11/0x40
[  411.419952] PGD 0 P4D 0 
[  411.419956] Oops:  [#1] SMP PTI
[  411.419959] Modules linked in: netconsole uas usb_storage configfs 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter devlink 
intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi 
snd_hda_codec_realtek coretemp snd_hda_codec_generic kvm_intel kvm irqbypass 
snd_hda_intel snd_hda_codec crct10dif_pclmul crc32_pclmul iTCO_wdt 
iTCO_vendor_support snd_hda_core snd_hwdep evdev ghash_clmulni_intel 
intel_cstate snd_pcm snd_timer snd soundcore lpc_ich ppdev intel_uncore 
mfd_core intel_rapl_perf serio_raw wmi_bmof i915 sg pcspkr video drm_kms_helper 
mei_me mei parport_pc parport drm i2c_algo_bit button wmi ip_tables x_tables 
autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb sr_mod sd_mod cdrom 
crc32c_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper psmouse 
i2c_i801
[  411.420011]  ahci libahci libata ehci_pci ehci_hcd scsi_mod e1000e usbcore 
ptp pps_core usb_common [last unloaded: netconsole]
[  411.420017] CPU: 0 PID: 1 Comm: systemd Tainted: GW   
4.14.0-3-amd64 #1 Debian 4.14.13-1
[  411.420019] Hardware name: LENOVO 4524BL8/, BIOS 9HKT53AUS 07/18/2012
[  411.420022] task: 989ab93b1040 task.stack: b57640648000
[  411.420025] RIP: 0010:pids_free+0x11/0x40
[  411.420027] RSP: 0018:b5764064bdf0 EFLAGS: 00010246
[  411.420031] RAX: 9899b66688f8 RBX:  RCX: 000a
[  411.420033] RDX: 000a RSI: 000b RDI: 9899b65bda10
[  411.420036] RBP: 9899b65bda10 R08: 1000 R09: 0007
[  411.420038] R10: 55593d8fa010 R11: 9899b67ac006 R12: bd25e0e0
[  411.420044] R13: 9899b66688f8 R14: 9899b65bda10 R15: 989ab40c3880
[  411.420047] FS:  7faa1a71be00() GS:989abe20() 
knlGS:
[  411.420050] CS:  0010 DS:  ES:  CR0: 80050033
[  411.420052] CR2: 00b0 CR3: 000138674005 CR4: 000626f0
[  411.420055] Call Trace:
[  411.420059]  cgroup_free+0x5c/0xd0
[  411.420065]  __put_task_struct+0x3d/0x150
[  411.420067]  css_task_iter_next+0x6f/0x80

 
[  411.420070]  kernfs_seq_next+0x23/0x50   

 
[  411.420074]  ? cgroup_procs_show+0x26/0x30   

 
[  411.420077]  seq_read+0x313/0x440

 
[  411.420080]  vfs_read+0x89/0x130 

 

Bug#887746: okular: Please package new upstream version 17.12.1

2018-01-19 Thread Michael Weghorn
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

2018-01-18 Thread Michael Weghorn
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

2018-01-16 Thread Michael Weghorn
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

2018-01-16 Thread Michael Weghorn
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

2018-01-16 Thread Michael Weghorn
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

2018-01-16 Thread Michael Weghorn
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

2018-01-16 Thread Michael Weghorn
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

2018-01-13 Thread Michael Weghorn
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

2018-01-10 Thread Michael Weghorn
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#886798: libpoppler46: displays empty pages after security update

2018-01-10 Thread Michael Weghorn
Just a note: #886733 seems to describe the same problem for Debian stable.

Regards,
  Michael

On 2018-01-09 23:37, Andreas Gösele wrote:
> Package: libpoppler46
> Version: 0.26.5-2+deb8u2
> Severity: important
> 
> Dear Maintainer,
> 
> after the security update from 0.26.5-2+deb8u1 to 0.26.5-2+deb8u2
> programs like okular, xpdf and zathura don't display correctly many
> pdf files, showing either blank pages, mostly blank pages or not
> displaying certain characters. This concerns files I created myself
> and files I downloaded from the internet like:
> 
> https://www.uni-heidelberg.de/md/awi/forschung/dp391.pdf
> 
> Okular gives many error messages of the type:
> 
> okular(18722) PDFGeneratorPopplerDebugFunction: [Poppler] "Error (180512): 
> Missing or bad Type3 CharProc entry"
> 
> Going back and forth between 0.26.5-2+deb8u1 and 0.26.5-2+deb8u2
> clearly show that the error is related to the new version of libpoppler46.
> 
> -- System Information:
> Debian Release: 8.10
>   APT prefers oldstable-updates
>   APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages libpoppler46 depends on:
> ii  libc6  2.19-18+deb8u10
> ii  libfontconfig1 2.11.0-6.3+deb8u1
> ii  libfreetype6   2.5.2-3+deb8u2
> ii  libjpeg62-turbo1:1.3.1-12
> ii  liblcms2-2 2.6-3+deb8u1
> ii  libopenjpeg5   1:1.5.2-3
> ii  libpng12-0 1.2.50-2+deb8u3
> ii  libstdc++6 4.9.2-10
> ii  libtiff5   4.0.3-12.3+deb8u4
> ii  multiarch-support  2.19-18+deb8u10
> 
> Versions of packages libpoppler46 recommends:
> ii  poppler-data  0.4.7-1
> 
> libpoppler46 suggests no packages.
> 
> -- no debconf information
> 



Bug#886798: libpoppler46: displays empty pages after security update

2018-01-10 Thread Michael Weghorn
Just a note: #886733 seems to describe the same problem for Debian stable.

Regards,
  Michael

On 2018-01-09 23:37, Andreas Gösele wrote:
> Package: libpoppler46
> Version: 0.26.5-2+deb8u2
> Severity: important
> 
> Dear Maintainer,
> 
> after the security update from 0.26.5-2+deb8u1 to 0.26.5-2+deb8u2
> programs like okular, xpdf and zathura don't display correctly many
> pdf files, showing either blank pages, mostly blank pages or not
> displaying certain characters. This concerns files I created myself
> and files I downloaded from the internet like:
> 
> https://www.uni-heidelberg.de/md/awi/forschung/dp391.pdf
> 
> Okular gives many error messages of the type:
> 
> okular(18722) PDFGeneratorPopplerDebugFunction: [Poppler] "Error (180512): 
> Missing or bad Type3 CharProc entry"
> 
> Going back and forth between 0.26.5-2+deb8u1 and 0.26.5-2+deb8u2
> clearly show that the error is related to the new version of libpoppler46.
> 
> -- System Information:
> Debian Release: 8.10
>   APT prefers oldstable-updates
>   APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages libpoppler46 depends on:
> ii  libc6  2.19-18+deb8u10
> ii  libfontconfig1 2.11.0-6.3+deb8u1
> ii  libfreetype6   2.5.2-3+deb8u2
> ii  libjpeg62-turbo1:1.3.1-12
> ii  liblcms2-2 2.6-3+deb8u1
> ii  libopenjpeg5   1:1.5.2-3
> ii  libpng12-0 1.2.50-2+deb8u3
> ii  libstdc++6 4.9.2-10
> ii  libtiff5   4.0.3-12.3+deb8u4
> ii  multiarch-support  2.19-18+deb8u10
> 
> Versions of packages libpoppler46 recommends:
> ii  poppler-data  0.4.7-1
> 
> libpoppler46 suggests no packages.
> 
> -- no debconf information
> 



Bug#783607: libpoppler: Some contents in some pdf documents seem to be ignored

2018-01-10 Thread Michael Weghorn
Hi,

the bug is still reproducible in current Debian stable (libpoppler64
0.48.0-2+deb9u1).

However, I can no longer reproduce it in current Debian unstable
(libpoppler72 0.61.1-2), so it seems to have been fixed in the meanwhile.

Regards,
  Michael

On 2018-01-09 21:53, Andreas Goesele wrote:
> This bug is still present in libpoppler46:amd64 0.26.5-2+deb8u1 and
> libpoppler46:amd64 0.26.5-2+deb8u2
> 



Bug#886557: okular: Poor rendering

2018-01-07 Thread Michael Weghorn
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#879472: ITP: libqtdbustest -- Library for testing DBus interactions using Qt

2017-10-22 Thread Michael Weghorn
Hi,

this looks very similar to #878895.
How are the two related?


Regards,
Michael

On 2017-10-22 01:16, Mike Gabriel wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Mike Gabriel 
> 
> * Package name: libqtdbustest
>   Version : 0.2+bzr42
>   Upstream Author : Pete Woods 
> * URL : https://code.launchpad.net/libqtdbustest
> * License : LGPL-3
>   Programming Lang: C++
>   Description : Library for testing DBus interactions using Qt
> 
>  Simple library for testing Qt based DBus services and clients.
>  .
>  The library also comes with a simple executable for running test
>  scripts under a private DBus environment.
>  .
>  This package will be maintained under the umbrella of the Ayatana
>  Packagers Team.
> 



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

2017-10-09 Thread Michael Weghorn
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

2017-10-05 Thread Michael Weghorn
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 <m.wegh...@posteo.de>
>> Komu: Leoš Pohl <lp...@centrum.cz>, 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

2017-10-04 Thread Michael Weghorn
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

2017-09-29 Thread Michael Weghorn

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#876184: pdfsam: Disable donation window, news, and ads for premiun features

2017-09-19 Thread Michael Weghorn
Hi Markus,

thank you you for your quick reply and the clarification.

As I said before, this is OK with me. (We'll then probably deploy an
adapted version of the package within our organisation to comply with
our security policies.)

Regards,
  Michael



signature.asc
Description: OpenPGP digital signature


Bug#876184: pdfsam: Disable donation window, news, and ads for premiun features

2017-09-19 Thread Michael Weghorn
Package: pdfsam
Version: 3.3.2-2
Severity: wishlist

Dear Maintainer,

PDFsam provides the possibility to enable or disable
certain "features" in its options.

At the moment, the following functionality is enabled
by default:

* "Show donation window"
* "Check for news at startup"
* "Show premium features"

In my opinion, it would be better to have those options
disabled by default.
(Currently, there is already a patch that disables
the check for updates at startup.)

Of course, this is a "matter of taste", so please feel free
to close this bug as invalid in case you see that differently.

Regards,
  Michael


-- System Information:
Debian Release: buster/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-2-amd64 (SMP w/2 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 pdfsam depends on:
ii  default-jre [java8-runtime]2:1.8-59
ii  libatinject-jsr330-api-java1.0+ds1-3
ii  libbcmail-java 1.57-1
ii  libbcprov-java 1.57-1
ii  libcommons-io-java 2.5-1
ii  libcommons-lang3-java  3.5-1
ii  libfontawesomefx-java  8.9-1
ii  libgettext-commons-java0.9.6-6
ii  libhibernate-validator-java4.3.3-2
ii  libjackson2-jr-java2.8.9-2
ii  liblogback-java1:1.1.9-4
ii  libsambox-java 1.1.16-1
ii  libsejda-eventstudio-java  1.0.6-1
ii  libsejda-injector-java 1.0.2-1
ii  libsejda-java  3.2.2-2
ii  libslf4j-java  1.7.25-1
ii  openjdk-8-jre [java8-runtime]  8u144-b01-1
ii  openjfx8u131-b11-2

pdfsam recommends no packages.

pdfsam suggests no packages.

-- no debconf information



Bug#874372: pdfsam: Missing dependencies to liblogback-java and libsambox-java

2017-09-06 Thread Michael Weghorn
Hi,

Thank you for your quick reply.

On 2017-09-05 19:17, Markus Koschany wrote:
> [...] Unfortunately there is another
> error. If you try to manipulate a PDF file (e.g. using the extract
> feature), nothing will happen but an error message is logged. It is
> related to libhibernate-java. Downgrading to 4.2.1 makes it go away. If
> you found the solution for this problem, that would be awesome.

I tried to analyse the problem.

The problem seems to be that the jar package inside the Debian package
"libhibernate-validator-java" is missing something needed by pdfsam (or
one of its other dependencies).

Stack trace/error message I got whe trying to extract a page (probably
the one you also get):

~~~
$ pdfsam
INFO  21:39:38.386 o.p.PdfsamApp[JavaFX-Launcher] Starting PDFsam
INFO  21:39:39.344 o.s.c.c.GlobalConfiguration[JavaFX Application
Thread] Configuring Sejda 2.10.4
INFO  21:39:39.971 o.p.PdfsamApp[JavaFX Application Thread] Started in 1
second
INFO  21:40:23.036 o.p.p.SAMBoxPdfLoadService[pool-2-thread-1] pages.pdf
loaded
ERROR 21:41:05.567 org.pdfsam.UncaughtExceptionLogger[pool-3-thread-1]
Unexpected error
java.lang.ExceptionInInitializerError: null
at
org.hibernate.validator.internal.engine.ConfigurationImpl.(ConfigurationImpl.java:63)
at
org.hibernate.validator.HibernateValidator.createGenericConfiguration(HibernateValidator.java:41)
at
javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:173)
at
org.sejda.core.validation.DefaultValidationContext.(DefaultValidationContext.java:41)
at
org.sejda.core.validation.DefaultValidationContext.(DefaultValidationContext.java:36)
at
org.sejda.core.validation.DefaultValidationContext$DefaultValidationContextHolder.(DefaultValidationContext.java:70)
at
org.sejda.core.validation.DefaultValidationContext.getContext(DefaultValidationContext.java:50)
at
org.sejda.core.service.DefaultTaskExecutionService.validate(DefaultTaskExecutionService.java:97)
at
org.sejda.core.service.DefaultTaskExecutionService.execute(DefaultTaskExecutionService.java:66)
at
org.sejda.core.service.DefaultTaskExecutionService.execute(DefaultTaskExecutionService.java:58)
at
org.pdfsam.task.TaskExecutionController.lambda$request$0(TaskExecutionController.java:87)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: Invalid logger interface
org.hibernate.validator.internal.util.logging.Log (implementation not
found in sun.misc.Launcher$AppClassLoader@a09ee92)
at org.jboss.logging.Logger$1.run(Logger.java:2556)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.logging.Logger.getMessageLogger(Logger.java:2529)
at org.jboss.logging.Logger.getMessageLogger(Logger.java:2516)
at
org.hibernate.validator.internal.util.logging.LoggerFactory.make(LoggerFactory.java:28)
at 
org.hibernate.validator.internal.util.Version.(Version.java:27)
... 14 common frames omitted
~~~

It does work as expected when building the jar file "manually" from the
same source that is used for the Debian package, e.g by running the
following commands:

~~~
$ apt source libhibernate-validator-jav
$ cd libhibernate-validator-java-4.3.3/
$ mvn clean install -DdisableDocumentationBuild=true
-Dmaven.test.skip=true -s settings-example.xml
~~~

and modifying the respective symlink in order to use that jar file
instead of the one provided by the Debian package (executed from
directory where build was made):

~~~
$ sudo ln -s -f
"${PWD}/engine/target/hibernate-validator-4.3.3.Final.jar"
/usr/share/pdfsam/lib/hibernate-validator.jar
~~~

After doing so, extracting pages works in pdfsam.


The relevant difference between the jar file generated in the Debian
package build process and the one from the "manual build" can be seen in
the directory  "org/hibernate/validator/internal/util/logging/ after
extracting the two jar files (from Debian build and from manual build):

~~~
mkdir -p /tmp/extracted/manual /tmp/extracted/debian
unzip "${PWD}/engine/target/hibernate-validator-4.3.3.Final.jar" -d
/tmp/extracted/manual
unzip /usr/share/java/hibernate-validator.jar -d /tmp/extracted/debian/
~~~

The version from the Debian build is missing files as compared to the
other one.
>From Debian package:

~~~
$ ls -l /tmp/extracted/debian/org/hibernate/validator/internal/util/logging/
total 32
-rw-r--r-- 1 user user 21057 May 13  2016 Log.class
-rw-r--r-- 1 user user   944 May 13  2016 LoggerFactory.class
-rw-r--r-- 1 user user  1894 May 13  2016 Messages.class
~~~

>From jar file built manually:

~~~
$ ls -l /tmp/extracted/manual/org/hibernate/validator/internal/util/logging/
total 144
-rw-r--r-- 1 user user 21057 Sep  6 19:11 Log.class
-rw-r--r-- 

Bug#874372: pdfsam: Missing dependencies to liblogback-java and libsambox-java

2017-09-05 Thread Michael Weghorn
Package: pdfsam
Version: 3.2.5-1
Severity: normal


Dear Maintainer,

when trying to start pdfsam in Debian experimental, that failed
with the following error message:

~~~
$ pdfsam
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
Exception in Application start method
Exception in Application stop method
Exception in thread "main" java.lang.RuntimeException: Exception in Application 
start method
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:917)
at 
com.sun.javafx.application.LauncherImpl.lambda$launchApplication$1(LauncherImpl.java:182)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NoClassDefFoundError: 
ch/qos/logback/classic/encoder/PatternLayoutEncoder
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.getDeclaredMethods(Class.java:1975)
at org.sejda.injector.Injector.providers(Injector.java:343)
at org.sejda.injector.Injector.(Injector.java:120)
at org.sejda.injector.Injector.start(Injector.java:102)
at org.pdfsam.PdfsamApp.initInjector(PdfsamApp.java:169)
at org.pdfsam.PdfsamApp.start(PdfsamApp.java:139)
at 
com.sun.javafx.application.LauncherImpl.lambda$launchApplication1$8(LauncherImpl.java:863)
at 
com.sun.javafx.application.PlatformImpl.lambda$runAndWait$7(PlatformImpl.java:326)
at 
com.sun.javafx.application.PlatformImpl.lambda$null$5(PlatformImpl.java:295)
at java.security.AccessController.doPrivileged(Native Method)
at 
com.sun.javafx.application.PlatformImpl.lambda$runLater$6(PlatformImpl.java:294)
at 
com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:95)
at com.sun.glass.ui.gtk.GtkApplication._runLoop(Native Method)
at 
com.sun.glass.ui.gtk.GtkApplication.lambda$null$5(GtkApplication.java:139)
... 1 more
Caused by: java.lang.ClassNotFoundException: 
ch.qos.logback.classic.encoder.PatternLayoutEncoder
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 17 more
~~~

After manually installing the package "liblogback-java", starting pdfsam still 
failed, now with the following error message:

~~~
$ pdfsam
INFO  15:53:56.083 o.p.PdfsamApp[JavaFX-Launcher] Starting PDFsam
INFO  15:53:57.408 o.s.c.c.GlobalConfiguration[JavaFX Application Thread] 
Configuring Sejda 2.10.4
Exception in Application start method
INFO  15:53:57.449 o.p.PdfsamApp[JavaFX Application Thread] Closing PDFsam...
Exception in Application stop method
Exception in thread "main" java.lang.RuntimeException: Exception in Application 
start method
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:917)
at 
com.sun.javafx.application.LauncherImpl.lambda$launchApplication$1(LauncherImpl.java:182)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.sejda.injector.InjectionException: Can't instantiate 
org.pdfsam.task.TaskExecutionController
at org.sejda.injector.Injector.lambda$provider$4(Injector.java:188)
at 
org.sejda.injector.Injector.lambda$singletonProvider$6(Injector.java:230)
at org.sejda.injector.Injector.lambda$new$3(Injector.java:134)
at java.lang.Iterable.forEach(Iterable.java:75)
at org.sejda.injector.Injector.(Injector.java:134)
at org.sejda.injector.Injector.start(Injector.java:102)
at org.pdfsam.PdfsamApp.initInjector(PdfsamApp.java:169)
at org.pdfsam.PdfsamApp.start(PdfsamApp.java:139)
at 
com.sun.javafx.application.LauncherImpl.lambda$launchApplication1$8(LauncherImpl.java:863)
at 
com.sun.javafx.application.PlatformImpl.lambda$runAndWait$7(PlatformImpl.java:326)
at 
com.sun.javafx.application.PlatformImpl.lambda$null$5(PlatformImpl.java:295)
at java.security.AccessController.doPrivileged(Native Method)
at 
com.sun.javafx.application.PlatformImpl.lambda$runLater$6(PlatformImpl.java:294)
at 
com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:95)
at com.sun.glass.ui.gtk.GtkApplication._runLoop(Native Method)
at 
com.sun.glass.ui.gtk.GtkApplication.lambda$null$5(GtkApplication.java:139)
... 1 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 

Bug#839605: network-manager: wireless stuck on "link is not ready"

2017-08-30 Thread Michael Weghorn
Hi,

related upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=777523

Ubuntu has included the mentioned workaround in their package; bug
report:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513

Regards,
Michael



Bug#790322: /usr/share/gdebi/gdebi-gtk: prompt for root password returns incorrect password

2017-08-10 Thread Michael Weghorn
Hi,

I just experienced the described problem as well.

As far as I understand it, the problem is not specific to gdebi, but is
a more general problem with the 'gksu' command. This problem is also
described in the Debian bug reports #481689 [1], #570700 [2], and
#700162 [3].

The workaround of explicitly setting the gconf key
'/apps/gksu/sudo-mode' to 'true', e.g. by using the command

gconftool-2 --set /apps/gksu/sudo-mode --type boolean true

as described in #570700 works for me.

#867236 [4] mentions that 'gksu' is deprecated and is planned to be
removed for the next Debian release (buster) and the right way for an
application to request elevated privileges is to use PolicyKit instead.

Are there currently any plans to drop the use of 'gksu' in gdebi?


Michael

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481689
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570700
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700162
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867236

On Sat, 27 Jun 2015 21:05:06 -0400 Seryn Rosenblum 
wrote:
> Package: gdebi
> Version: 0.9.5.5+nmu1
> Severity: important
> File: /usr/share/gdebi/gdebi-gtk
> 
> Dear Maintainer,
> When selecting a .deb file to open with gdebi from within thunar the user is
> prompted to enter an admin password. After selecting 'ok' the prompt returns
> 'incorrect password'. Open a terminal open gdebi with sudo (same password)
> and the user can select the same file and install it.
> 
> 
> -- System Information:
> Debian Release: 8.1
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages gdebi depends on:
> ii  gdebi-core0.9.5.5+nmu1
> ii  gir1.2-gtk-3.03.14.5-1
> ii  gir1.2-vte-2.90   1:0.36.3-1
> ii  gksu  2.0.2-9
> ii  gnome-icon-theme  3.12.0-1
> ii  python3-gi3.14.0-1
> pn  python3:any   
> 
> Versions of packages gdebi recommends:
> ii  libgtk2-perl  2:1.2492-4
> ii  lintian   2.5.30+deb8u4
> ii  shared-mime-info  1.3-1
> 
> gdebi suggests no packages.
> 
> -- no debconf information
> 
> 



Bug#869663: [okular] Review tools should not be automatically switched off right after used

2017-07-25 Thread Michael Weghorn
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

2017-07-25 Thread Michael Weghorn

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

2017-07-20 Thread Michael Weghorn
https://bugs.kde.org/show_bug.cgi?id=358289 seems to be a corresponding 
upstream bug.




Bug#868763: okular: Please package new upstream version

2017-07-18 Thread Michael Weghorn
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

2017-07-18 Thread Michael Weghorn

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



Bug#839605: network-manager: wireless stuck on "link is not ready"

2017-04-19 Thread Michael Weghorn
On Fri, 4 Nov 2016 18:10:52 +0100 aaa bbb  wrote:
> All I needed to get wireless WLAN working, was to add this to
> /etc/NetworkManager/NetworkManager.conf
> [device-mac-randomization]
> wifi.scan-rand-mac-address=no


Adding the above directive works for me as well. (I am using
network-manager 1.6.2-3 on current Debian sid).

I had previously discovered another workaround: Using the "old naming
scheme" (rather than systemd/udev's new predictable naming scheme) for
the Wifi device worked as well for me:

After disabling the respective systemd unit "network/99-default.link",
the Wifi device gets the name "wlan0" instead of "wlxb0487a89c6ac"
(based on the MAC address) and the connection is successfully
established when using NetworkManager.

This can be achieved by creating an empty file
/etc/systemd/network/99-default.link which then overrides sytemd's
default options in /lib/systemd/network/99-default.link



Bug#792467: pdfsam: gui perspective is working console perspective isnt...

2017-03-20 Thread Michael Weghorn
On Wed, 15 Jul 2015 05:57:59 +0200 treaki  wrote:
> Package: pdfsam
> Version: 1.1.4-2
> Severity: important
> 
> Dear Maintainer,
> 
> i have followed the instructions given by pdfsam-console but it isnt working 
> as aspected...
> 
> treaki@hostname:~/[...]/p01$ pdfsam-console -compressed -f page01.pdf -f 
> page02.pdf -o pr01.pdf concat
> [...]

When running exactly the same command, I get the same result. The reason
is that pdfsam has a certain expectation of the specification for the
output file (parameter '-o'). Using '-o ./pr01.pdf' (with a leading './'
to indicate that the file is to be created in the current directory) works:


$ pdfsam-console -compressed -f page01.pdf -f page02.pdf -o
./pr01.pdf concat
[warning] /usr/bin/pdfsam-console: No java runtime was found

=

 pdfsam console

 available properties:
 pdfsam.log.console.level
 pdfsam.log.file.level
 pdfsam.log.file.filename

  JAVA: java

  JAVA_OPTS: -Dlog4j.configuration=console-log4j.xml

  CLASSPATH:
:/usr/share/pdfsam/lib/dom4j.jar:/usr/share/pdfsam/lib/emp4j-1.0.1.jar:/usr/share/pdfsam/lib/itext.jar:/usr/share/pdfsam/lib/jaxen.jar:/usr/share/pdfsam/lib/log4j-1.2.jar:/usr/share/pdfsam/lib/looks.jar:/usr/share/pdfsam/lib/pdfsam-console-2.0.6e.jar:/usr/share/pdfsam/lib/pdfsam-jcmdline-1.0.3.jar:/usr/share/pdfsam/lib/pdfsam-langpack.jar


=

19:32:41,322 DEBUG  Console log level set to DEBUG
19:32:41,342 DEBUG  Starting arguments parsing.
19:32:41,348 DEBUG  Command 'concat' parsed in 5ms
19:32:41,348 DEBUG  Starting arguments validation.
19:32:41,350 DEBUG  Command 'concat' validated in 2ms
19:32:41,353 DEBUG  Creating temporary file..
19:32:41,401 INFO   /home/michi/page01.pdf: 1 pages to be added.
19:32:41,457 DEBUG  PdfSimpleConcatenator created.
19:32:41,482 INFO   1 pages processed correctly.
19:32:41,489 INFO   /home/michi/page02.pdf: 1 pages to be added.
19:32:41,493 INFO   1 pages processed correctly.
19:32:41,494 INFO   Total processed pages: 2.
19:32:41,509 DEBUG  File /home/michi/pr01.pdf created.
19:32:41,510 INFO   Command 'concat' executed in 159ms



Bug#846540: Fwd: Re: hplip-gui: hp-toolbox and hp-setup cannot load

2016-12-10 Thread Michael Weghorn
Hi Alejandro,

last week, I had written a reply to your Debian bug report on hplip-gui
[1] with a few thoughts on what might play a role (s. forwarded email
below). Unfortunately, I wrote the reply only to the bug tracker's email
address and not to your personal email address, so you might not have
got the reply in case you are not subscribed to the bug report (I am not
sure whether the bug reporter is automatically subscribed.)

Sorry for forgetting to add your email address at first.

Regards,
Michael

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846540

 Forwarded Message 
Subject: Re: hplip-gui: hp-toolbox and hp-setup cannot load
Date: Sat, 3 Dec 2016 22:24:43 +0100
From: Michael Weghorn <m.wegh...@posteo.de>
To: 846...@bugs.debian.org

Hi Alejandro,

I just installed "hplip-gui" on unstable/sid in a VM and running
hp-setup or hp-check did work for me. (I did not check the
functionality, just that the problem you described did not occur.)

Do you have the package "libhpmud0" installed?
It contains the respective shared library file "libhpipp.so.0" that is
mentioned in the error message you get:

~~~
$ dpkg -S /usr/lib/x86_64-linux-gnu/libhpipp.so.0
libhpmud0:amd64: /usr/lib/x86_64-linux-gnu/libhpipp.so.0
~~~

As far as I understand, the package should automatically be installed as
it is declared as a dependency of package "hplip" (which is itself a
dependency of "hplip-gui").

If I explicitly ignore that dependency and force the removal of the
package "libhpmud0", I can reproduce the error messages you wrote about:

~~~
$ sudo dpkg --purge libhpmud0
dpkg: dependency problems prevent removal of libhpmud0:amd64:
 libsane-hpaio:amd64 depends on libhpmud0.
 printer-driver-hpcups depends on libhpmud0.
 hplip depends on libhpmud0 (= 3.16.10+repack0-1).

dpkg: error processing package libhpmud0:amd64 (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 libhpmud0:amd64
$ sudo dpkg --purge --force-all libhpmud0
dpkg: libhpmud0:amd64: dependency problems, but removing anyway as you
requested:
 libsane-hpaio:amd64 depends on libhpmud0.
 printer-driver-hpcups depends on libhpmud0.
 hplip depends on libhpmud0 (= 3.16.10+repack0-1).

(Reading database ... 75747 files and directories currently installed.)
Removing libhpmud0:amd64 (3.16.10+repack0-1) ...
Processing triggers for libc-bin (2.24-7) ...
$ hp-setup
Traceback (most recent call last):
  File "/usr/bin/hp-setup", line 48, in 
from base import device, utils, tui, models, module, services, os_utils
  File "/usr/share/hplip/base/device.py", line 41, in 
from . import status
  File "/usr/share/hplip/base/status.py", line 32, in 
import cupsext
ImportError: libhpipp.so.0: cannot open shared object file: No such file
or directory
~~~

As far as I understand it so far, "libhpmud0" should always be present
in normal cases because of the declared dependencies.

Michael



Bug#846540: hplip-gui: hp-toolbox and hp-setup cannot load

2016-12-03 Thread Michael Weghorn
Hi Alejandro,

I just installed "hplip-gui" on unstable/sid in a VM and running
hp-setup or hp-check did work for me. (I did not check the
functionality, just that the problem you described did not occur.)

Do you have the package "libhpmud0" installed?
It contains the respective shared library file "libhpipp.so.0" that is
mentioned in the error message you get:

~~~
$ dpkg -S /usr/lib/x86_64-linux-gnu/libhpipp.so.0
libhpmud0:amd64: /usr/lib/x86_64-linux-gnu/libhpipp.so.0
~~~

As far as I understand, the package should automatically be installed as
it is declared as a dependency of package "hplip" (which is itself a
dependency of "hplip-gui").

If I explicitly ignore that dependency and force the removal of the
package "libhpmud0", I can reproduce the error messages you wrote about:

~~~
$ sudo dpkg --purge libhpmud0
dpkg: dependency problems prevent removal of libhpmud0:amd64:
 libsane-hpaio:amd64 depends on libhpmud0.
 printer-driver-hpcups depends on libhpmud0.
 hplip depends on libhpmud0 (= 3.16.10+repack0-1).

dpkg: error processing package libhpmud0:amd64 (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 libhpmud0:amd64
$ sudo dpkg --purge --force-all libhpmud0
dpkg: libhpmud0:amd64: dependency problems, but removing anyway as you
requested:
 libsane-hpaio:amd64 depends on libhpmud0.
 printer-driver-hpcups depends on libhpmud0.
 hplip depends on libhpmud0 (= 3.16.10+repack0-1).

(Reading database ... 75747 files and directories currently installed.)
Removing libhpmud0:amd64 (3.16.10+repack0-1) ...
Processing triggers for libc-bin (2.24-7) ...
$ hp-setup
Traceback (most recent call last):
  File "/usr/bin/hp-setup", line 48, in 
from base import device, utils, tui, models, module, services, os_utils
  File "/usr/share/hplip/base/device.py", line 41, in 
from . import status
  File "/usr/share/hplip/base/status.py", line 32, in 
import cupsext
ImportError: libhpipp.so.0: cannot open shared object file: No such file
or directory
~~~

As far as I understand it so far, "libhpmud0" should always be present
in normal cases because of the declared dependencies.

Michael



Bug#843725: accerciser: Missing dependency to gir1.2-rsvg-2.0

2016-11-08 Thread Michael Weghorn
Package: accerciser
Version: 3.22.0-1
Severity: normal

Dear Maintainer,

when gir1.2-rsvg-2.0 is not installed and I try to start accerciser,
it crashes on start.

Console output:

~~~
$ accerciser 
/usr/bin/accerciser:48: PyGIWarning: Gtk was imported without specifying a 
version first. Use gi.require_version('Gtk', '3.0') before import to ensure 
that the right version gets loaded.
  from gi.repository import Gtk as gtk
Traceback (most recent call last):
  File "", line 890, in _find_spec
AttributeError: 'DynamicImporter' object has no attribute 'find_spec'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/accerciser", line 74, in 
accerciser.main()
  File "/usr/lib/python3/dist-packages/accerciser/__init__.py", line 34, in main
from .accerciser import Main
  File "/usr/lib/python3/dist-packages/accerciser/accerciser.py", line 27, in 

from .accessible_treeview import *
  File "/usr/lib/python3/dist-packages/accerciser/accessible_treeview.py", line 
26, in 
from .node import Node
  File "/usr/lib/python3/dist-packages/accerciser/node.py", line 21, in 
from gi.repository import Rsvg as rsvg
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 127, in find_module
'introspection typelib not found' % namespace)
ImportError: cannot import name Rsvg, introspection typelib not found
~~~

It works after manually installing the package "gir1.2-rsvg-2.0", so I
think this should be declared as a dependency in the control file.


Regards,
Michael


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

Kernel: Linux 4.8.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages accerciser depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  gir1.2-atk-1.0   2.22.0-1
ii  gir1.2-gdkpixbuf-2.0 2.36.0-1
ii  gir1.2-gtk-3.0   3.22.3-1
ii  gir1.2-pango-1.0 1.40.3-3
ii  gir1.2-wnck-3.0  3.20.1-2
ii  ipython3 5.1.0-2
ii  python3-cairo1.10.0+dfsg-5+b1
ii  python3-pyatspi  2.20.2+dfsg-2
pn  python3:any  

accerciser recommends no packages.

accerciser suggests no packages.

-- no debconf information



Bug#832362: crashed: jaw_impl_get_instance: assertion failed

2016-11-08 Thread Michael Weghorn
Hello,

On 09/11/16 00:02, Samuel Thibault wrote:
> It should produce a warning instead of a crash, yes.
> 
> You can already fetch it from 
> 
> deb http://incoming.debian.org/debian-buildd buildd-unstable main contrib 
> non-free 

I can confirm the issue is fixed in the new version. The following
warning appears now (multiple times):

** (java:1006): WARNING **: jaw_impl_get_instance called from
jaw_thread. If you are running a screen reader, this is expected
If you are not running a screen reader, please report this warning to
the java-atk-wrapper package, explaining how to reproduce this warning

Thanks again for fixing this.

Michael



Bug#832362: crashed: jaw_impl_get_instance: assertion failed

2016-11-08 Thread Michael Weghorn
Hi Samuel,

thank you for your quick fix.

On 08/11/16 23:19, Samuel Thibault wrote
> 
> Alex, are you perhaps using a screen reader?  I would be very surprised
> if you are getting this while no screen reader is currently running,
> and I'm interested in a reproducer.  It's definitely an issue in
> java-atk-wrapper at least, thus reassigning.

Not being Alex, I had the same issue - originally with "jitsi" from
their repository, but I can reproduce it with "mediathekview" as well.

It originally happened to me when running "accerciser" (a tool that
queries the accessibility APIs as well), but I can also reproduce it
when I run orca (screen reader) instead. For me, the crash did not occur
when not running accerciser or orca.

Dropping the patch "check-thread" helped for me as a workaround as I
mentioned in #838778.

In case that helps, I can retest once version version 0.33.3-10 is
available in unstable.

Regards,
Michael



Bug#838778: libatk-wrapper-java: crashes JVM when launching a java application

2016-11-08 Thread Michael Weghorn
The respective assertion is added by Debian patch "check-thread".

For testing purposes, I rebuilt the package without that patch. In that
case, the crash does not occur. (But that probably leads to other
problems...).

Regards,
Michael



Bug#825107: unattended-upgrades: Cannot enable/disable automatic upgrades using debconf with noninteractive frontend

2016-05-26 Thread Michael Weghorn
On 2016-05-24 04:20, James Valleroy wrote:
> Is there a way to accommodate this, while also preserving local
> changes during an upgrade?

Thank you for your quick reply. Reading that post helped me better
understand the problem and how everything is related with each other.

On further research, I found that the man page of debconf-devel (7)
(section "Config file handling") describes how config files should be
handled by debconf.
The way unattended-upgrades does it is totally according to that.

This showed me that my understanding of debconf so far was not
sufficient and my first approach of changing the value was not
appropriate.
I checked how FAI [1] does it and the appropriate way seems to be to
use the "DEBCONF_DB_OVERRIDE" environment variable as described in the
man page of debconf (7).

Example:

root@debian:~# cat /tmp/override.dat
Name: unattended-upgrades/enable_auto_updates
Template: unattended-upgrades/enable_auto_updates
Value: false
Owners: unattended-upgrades

root@debian:~# DEBCONF_DB_OVERRIDE="File{/tmp/override.dat
readonly:true}" DEBIAN_FRONTEND=noninteractive dpkg-reconfigure
unattended-upgrades
Replacing config file /etc/apt/apt.conf.d/20auto-upgrades with new
version
update-rc.d: warning: start and stop actions are no longer
supported; falling back to defaults
debconf: DbDriver "_ENV_stack": unable to save changes to:
unattended-upgrades/enable_auto_updates

Then, to also update the debconf cache:

root@debian:~# debconf-copydb override_db config
--config=Name:override_db --config=Driver:File
--config=Filename:"/tmp/override.dat"


Therefore, this bug should possibly closed as "invalid".

Regards,
Michael

[1] http://fai-project.org/



Bug#825107: unattended-upgrades: Cannot enable/disable automatic upgrades using debconf with noninteractive frontend

2016-05-23 Thread Michael Weghorn
Package: unattended-upgrades
Version: 0.92
Severity: normal

Dear Maintainer,

as far as I can see, changing the setting whether upgrades should
automatically be downloaded and applied does not work with debconf in
noninteractive mode.

The corresponding debconf parameter is
"unattended-upgrades/enable_auto_updates"

By default, it is set to 'true':

root@debian:~# debconf-show unattended-upgrades
  unattended-upgrades/enable_auto_updates: true
  unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";

The following command changes the value to 'false':

root@debian:~# echo "unattended-upgrades 
unattended-upgrades/enable_auto_updates boolean false" | debconf-set-selections 
root@debian:~# debconf-show unattended-upgrades
* unattended-upgrades/enable_auto_updates: false
  unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";

However, that new value is not taken into account when running
"dpkg-reconfigure" with the noninteractive frontend:

root@debian:~# dpkg-reconfigure -fnoninteractive unattended-upgrades
update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults
root@debian:~# debconf-show unattended-upgrades
* unattended-upgrades/enable_auto_updates: true
  unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";

I would have expected the value to still be "false" and the automatic
downloading and installing of newer packages disabled in the configuration
file. This is not the case.

This might - among others - break the possibility to configure
unattended-upgrades using systems for automatic deployment that rely on
the noninteractive debconf interface.

The reason seems to be the following section in the config script (which
seems to be related to the following GitHub issue:
https://github.com/mvo5/unattended-upgrades/issues/18):

# Load configuration from disk, if it exists.
if [ -e "$AUTO_UPGRADE" ]; then
if grep -q 'APT::Periodic::Unattended-Upgrade "1";' $AUTO_UPGRADE ; then
db_set unattended-upgrades/enable_auto_updates true
elif grep -q 'APT::Periodic::Unattended-Upgrade "0";' $AUTO_UPGRADE ; 
then
db_set unattended-upgrades/enable_auto_updates false
fi
fi

Best regards,
Michael

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

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

Versions of packages unattended-upgrades depends on:
ii  apt1.2.12
ii  apt-utils  1.2.12
ii  debconf [debconf-2.0]  1.5.59
ii  init-system-helpers1.33
ii  lsb-base   9.20160110
ii  lsb-release9.20160110
ii  python33.5.1-3
ii  python3-apt1.1.0~beta2
ii  ucf3.0036
ii  xz-utils   5.1.1alpha+20120614-2.1

Versions of packages unattended-upgrades recommends:
ii  cron [cron-daemon]  3.0pl1-128

Versions of packages unattended-upgrades suggests:
pn  bsd-mailx  
ii  exim4-daemon-light [mail-transport-agent]  4.87-3

-- debconf information:
* unattended-upgrades/origins_pattern: 
"origin=Debian,codename=${distro_codename},label=Debian-Security";
* unattended-upgrades/enable_auto_updates: false



Bug#822334: reprepro: Consider environment vars for bash completion

2016-05-14 Thread Michael Weghorn
On 2016-05-08 15:10, Bernhard R. Link wrote:
> 
> Could you try attached file? It should fix your issue and also add
> support for the "+b/" notation reprepro allows.

Thank you very much!

"REPREPRO_BASE_DIR" works perfectly for me.

However, I think that "REPREPRO_CONFIG_DIR" would have to be used
instead of "REPREPRO_CONF_DIR". (Sorry, I also wrote it wrong once in my
report.)

Best regards,
Michael



Bug#822334: reprepro: Consider environment vars for bash completion

2016-04-23 Thread Michael Weghorn
Package: reprepro
Version: 4.17.0-1
Severity: wishlist
Tags: patch

Dear Maintainer,

reprepro has the nice feature of providing bash completion for codenames, e.g. 
with the "list" subcommand.

Example repository:

$ cat /tmp/reprepro-test/conf/distributions 
Origin: Test
Label: Test
Suite: mytestsuite
Codename: mytestsuite
Version: 3.1
Architectures: i386 amd64
Components: main
Description: Test suite

Origin: Test
Label: Test
Suite: unstable
Codename: sid
Version: 3.2
Architectures: i386 amd64
Components: main
Description: Test unstable

Tab completion works e.g. in the the following example:

$ reprepro -b /tmp/reprepro-test/ list   
mytestsuite  sid

Here, the existing suites are suggested for tab completion.

Currently, tab completion does not work, when the base-dir is
not explicitly specified, but set via the environment variable
"REPREPRO_BASE_DIR".

Example:

$ export REPREPRO_BASE_DIR=/tmp/reprepro-test
$ reprepro list  
etch  experimental  sarge sid   
whatever-you-defined  woody 

Instead of the existing suites, the dummy suites are suggested.
It would be nice if the environment variables "REPREPRO_BASE_DIR"
and "REPREPRO_CONF_DIR" could also be taken into account for bash completion.

As far as I can see, the attachted patch would add this support.


Please feel free to close this as WONTFIX in case the patch does
not work as it should or you do not see any good reason to add this support.


Best regards,
Michael

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

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

Versions of packages reprepro depends on:
ii  libarchive13 3.1.2-11+b1
ii  libbz2-1.0   1.0.6-8
ii  libc62.22-7
ii  libdb5.3 5.3.28-11
ii  libgpg-error01.21-3
ii  libgpgme11   1.6.0-3
ii  liblzma5 5.1.1alpha+20120614-2.1
ii  pinentry-curses  0.9.7-5
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages reprepro recommends:
ii  apt  1.2.10

Versions of packages reprepro suggests:
ii  gnupg-agent  2.1.11-7
pn  inoticoming  
pn  lzip 

-- no debconf information
>From 5559a564009c07611d7959283d6ea5d3e1afa7e4 Mon Sep 17 00:00:00 2001
From: Michael Weghorn <m.wegh...@posteo.de>
Date: Sat, 23 Apr 2016 15:39:45 +0200
Subject: [PATCH] bash completion: Support REPREPRO_{BASE,CONFIG}_DIR

Use the value of those environment variables as
basis for the bash completion in case no params are given
which explicity specify other values.
---
 docs/reprepro.bash_completion | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/reprepro.bash_completion b/docs/reprepro.bash_completion
index b548cef..3d28c06 100644
--- a/docs/reprepro.bash_completion
+++ b/docs/reprepro.bash_completion
@@ -2,8 +2,8 @@ _reprepro()
 {
 	local cur prev commands options noargoptions i state cmd ignores hiddencommands commands codenames confdir outdir basedir architectures components importrules snapshots
 
-	confdir=""
-	basedir=""
+	confdir="$REPREPRO_CONFIG_DIR"
+	basedir="$REPREPRO_BASE_DIR"
 	outdir=""
 
 	function parse_config() {
-- 
2.8.1



Bug#805357: cups-pdf: Print job with multiple input files doesn't work

2015-11-17 Thread Michael Weghorn
Package: cups-pdf
Version: 2.6.1-20
Severity: normal

Dear Maintainer,

sending a print job with multiple print files to the cups-pdf printer
does not work as expected.

When trying to print three or more files in one print job, the print job
seems to "hang" and does not disappear any more. Subsequent print jobs
sent to cups-pdf are not processed (possibly wait for the previous
print job to complete).

The following commands can be used to reproduce the described
behaviour:

echo "Hello world" > /tmp/input.txt
lp -d PDF /tmp/input.txt /tmp/input.txt /tmp/input.txt

The print job does not finish and can be shown e.g. using the command
"lpstat".

This also happens when different input files are used.
Printing a single file works OK.

When printing the same file only twice, the print job finishes, but the
created PDF file contains only the first page.


Expected behaviour:
The print job finishes and a PDF file with three pages, each containing
the text "Hello world", is created in the directory "~/PDF/".


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

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

Versions of packages cups-pdf depends on:
ii  dpkg 1.18.3
ii  printer-driver-cups-pdf  2.6.1-20

cups-pdf recommends no packages.

cups-pdf suggests no packages.

-- no debconf information



Bug#805357: cups-pdf: Print job with multiple input files doesn't work

2015-11-17 Thread Michael Weghorn

Sorry, I forgot to attach the patch to my previous email.
Here it is.

Best regards,
Michael

On 2015-11-17 10:58, Michael Weghorn wrote:

[...]
The following patch disables that behaviour. After applying the patch,
printing multiple files works.
The patch is only meant to demonstrate this behaviour and should be
extended/improved in case it is meant to be included.
[...]Index: cups-pdf-2.6.1/src/cups-pdf.c
===
--- cups-pdf-2.6.1.orig/src/cups-pdf.c
+++ cups-pdf-2.6.1/src/cups-pdf.c
@@ -505,7 +505,7 @@ static int preparespoolfile(FILE *fpsrc,
 else if (!strncmp(buffer, "%%EOF", 5)) {
   if (!rec_depth) {
 log_event(CPDEBUG, "found end of postscript code", buffer);
-break;
+//break;
   }
   else {
 log_event(CPDEBUG, "found end of embedded (e)ps code", buffer);


Bug#805357: cups-pdf: Print job with multiple input files doesn't work

2015-11-17 Thread Michael Weghorn
When sending multiple files in a single print job, the file passed to 
the cups-pdf backend seems to contain all of the single files (converted 
to PostScript) concatenated.
cups-pdf stops reading the input file after "the first PostScript file" 
has been read.


The following patch disables that behaviour. After applying the patch, 
printing multiple files works.
The patch is only meant to demonstrate this behaviour and should be 
extended/improved in case it is meant to be included.


However, I do not know whether there are possibly other reasons to 
explicitly stop processing the input file after "the first file" has 
been processed.
It should also be mentioned that Ghostscript (which is used by cups-pdf) 
is basically not meant for merging files, s.a. 
http://bugs.ghostscript.com/show_bug.cgi?id=696064.


Best regards,
Michael



Bug#801745: vlc: Segfault when watching WebM video with increased speed

2015-10-24 Thread Michael Weghorn
Hi Andreas,

thank you very much already for taking the time to look at this and for
the detailed analysis.

Best regards,
Michael



Bug#801745: vlc: Segfault when watching WebM video with increased speed

2015-10-24 Thread Michael Weghorn
Hi Andreas,

On 2015-10-24 21:44, Andreas Cadhalpun wrote:
> I've discussed this with ffmpeg upstream developers and it turns out
> that fixing the assembler code was feasible, after all.
> It is now fixed upstream in commit 52f84d8 [1].
> Actually, it had been reported before in above trac ticket, but
> couldn't be reproduced. Thanks again for providing the reproducer!
> 
> So this will be fixed with the ffmpeg 2.8.2 upload, but that might
> take a while.

That is great news. Thank you once again for taking action so quickly,
for the great analysis and for talking to the upstream developers!

Best regards,
Michael



Bug#801745: vlc: Segfault when watching WebM video with increased speed

2015-10-13 Thread Michael Weghorn
The attached file contains the VLC output and the GDB backtrace.

Please let me know whether I can provide any additional information that
is useful.
$ while true; do gdb -ex run -ex quit --args vlc -vvv --play-and-exit --rate 2.5 http://download.media.tagesschau.de/video/2015/1012/TV-20151012-2022-5601.webm.webm; done
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from vlc...Reading symbols from /usr/lib/debug/.build-id/39/1fbfcc27d12d994a7d3208f55cf56694091211.debug...done.
done.
Starting program: /usr/bin/vlc -vvv --play-and-exit --rate 2.5 http://download.media.tagesschau.de/video/2015/1012/TV-20151012-2022-5601.webm.webm
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
VLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 2.2.1-0-ga425c42)
[00605148] core libvlc debug: VLC media player - 2.2.1 Terry Pratchett (Weatherwax)
[00605148] core libvlc debug: Copyright © 1996-2015 the VideoLAN team
[00605148] core libvlc debug: revision 2.2.1-0-ga425c42
[00605148] core libvlc debug: configured with ./configure  '--includedir=${prefix}/include' '--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' '--localstatedir=/var' '--libdir=${prefix}/lib/x86_64-linux-gnu' '--libexecdir=${prefix}/lib/x86_64-linux-gnu' '--disable-dependency-tracking' '--build=x86_64-linux-gnu' 'CPPFLAGS=-D_FORTIFY_SOURCE=2' 'LDFLAGS=-Wl,-z,relro -Wl,--as-needed' '--config-cache' '--disable-maintainer-mode' '--disable-silent-rules' '--disable-update-check' '--enable-fast-install' '--prefix=/usr' '--docdir=/usr/share/doc/vlc-nox' '--libdir=/usr/lib' '--sysconfdir=/etc' '--with-binary-version=4' '--enable-a52' '--enable-aa' '--enable-bluray' '--enable-bonjour' '--enable-caca' '--enable-chromaprint' '--enable-dbus' '--enable-dca' '--enable-directfb' '--enable-dvbpsi' '--enable-dvdnav' '--enable-faad' '--enable-flac' '--enable-fluidsynth' '--enable-freerdp' '--enable-freetype' '--enable-fribidi' '--enable-gles1' '--enable-gles2' '--enable-gnutls' '--enable-jack' '--enable-kate' '--enable-libass' '--enable-libmpeg2' '--enable-libxml2' '--enable-lirc' '--enable-live555' '--enable-mad' '--enable-mkv' '--enable-mod' '--enable-mpc' '--enable-mtp' '--enable-mux_ogg' '--enable-ncurses' '--enable-notify' '--enable-ogg' '--enable-opus' '--enable-pulse' '--enable-qt' '--enable-realrtsp' '--enable-samplerate' '--enable-schroedinger' '--enable-sdl' '--enable-sdl-image' '--enable-sftp' '--enable-shine' '--enable-shout' '--enable-skins2' '--enable-speex' '--enable-svg' '--enable-svgdec' '--enable-taglib' '--enable-theora' '--enable-twolame' '--enable-upnp' '--enable-vcdx' '--enable-vdpau' '--enable-vnc' '--enable-vorbis' '--enable-x264' '--enable-x265' '--enable-zvbi' '--with-kde-solid=/usr/share/kde4/apps/solid/actions/' '--disable-decklink' '--disable-dxva2' '--disable-fdkaac' '--disable-gnomevfs' '--disable-goom' '--disable-libtar' '--disable-mfx' '--disable-opencv' '--disable-projectm' '--disable-sndio' '--disable-telx' '--disable-vpx' '--disable-vsxu' '--disable-wasapi' '--enable-alsa' '--enable-atmo' '--enable-dc1394' '--enable-dv1394' '--enable-linsys' '--enable-omxil' '--enable-udev' '--enable-v4l2' '--enable-libva' '--enable-vcd' '--enable-smbclient' '--disable-oss' '--enable-crystalhd' '--enable-mmx' '--enable-sse' '--disable-neon' '--disable-altivec' 'CFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security' 'CXXFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security' 'build_alias=x86_64-linux-gnu' 'OBJCFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security'
[00605148] core libvlc debug: searching plug-in modules
[00605148] core libvlc debug: loading plugins cache file /usr/lib/vlc/plugins/plugins.dat
[00605148] core libvlc debug: recursively browsing `/usr/lib/vlc/plugins'
[00605148] core libvlc debug: saving plugins cache /usr/lib/vlc/plugins/plugins.dat
[00605148] core libvlc debug: plug-ins loaded: 460 modules
[00605148] core libvlc debug: opening config file (/home/michi/.config/vlc/vlcrc)
[00605148] core libvlc debug: translation test: code is "en_GB"
[00605148] core libvlc debug: CPU has capabilities MMX MMXEXT SSE SSE2 SSE3 SSSE3 

Bug#801745: vlc: Segfault when watching WebM video with increased speed

2015-10-13 Thread Michael Weghorn
Package: vlc
Version: 2.2.1-4
Severity: important

Dear Maintainer,

when watching particular WebM videos with increased speed, VLC often crashes
due to a segmentation fault. 

When watching the same video multiple times, the segmentation fault does not
always occur and if so, it may occur at different points in time.

The following command can be used to reproduce the problem and examine it in 
GDB.
It plays a video in VLC repeatedly, until the segmentation fault occurs (which 
is often in the
first run already for me):

while true; do gdb -ex run -ex quit --args vlc -vvv --play-and-exit --rate 2.5 
http://download.media.tagesschau.de/video/2015/1012/TV-20151012-2022-5601.webm.webm;
 done

I am attaching the VLC output and the GDB backtrace of the segmentation fault.
The packages "vlc-dbg" and "ffmpeg-dbg" are installed on my system.

As far as I understand, the segmentation fault itself occurs in the ffmpeg 
library "libavcodec-ffmpeg56".
The crash happens with a similar backtrace on Debian jessie, where libav is 
used instead of ffmpeg.


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

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

Versions of packages vlc depends on:
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-44
ii  libavcodec-ffmpeg56 7:2.8-1
ii  libavutil-ffmpeg54  7:2.8-1
ii  libc6   2.19-22
ii  libcaca00.99.beta19-2
ii  libcairo2   1.14.2-2
ii  libegl1-mesa [libegl1-x11]  10.6.8-1
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-5
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-5
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-5
ii  libfreetype62.6-2
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:5.2.1-22
ii  libgl1-mesa-glx [libgl1]10.6.8-1
ii  libgles1-mesa [libgles1]10.6.8-1
ii  libgles2-mesa [libgles2]10.6.8-1
ii  libglib2.0-02.46.0-2
ii  libpulse0   7.0-1
ii  libqt5core5a5.4.2+dfsg-9
ii  libqt5gui5  5.4.2+dfsg-9
ii  libqt5widgets5  5.4.2+dfsg-9
ii  libqt5x11extras55.4.2-2+b1
ii  librsvg2-2  2.40.11-1
ii  libsdl-image1.2 1.2.12-5+b5
ii  libsdl1.2debian 1.2.15-11
ii  libstdc++6  5.2.1-22
ii  libva-drm1  1.6.1-1
ii  libva-x11-1 1.6.1-1
ii  libva1  1.6.1-1
ii  libvlccore8 2.2.1-4
ii  libvncclient1   0.9.10+dfsg-3
ii  libx11-62:1.6.3-1
ii  libxcb-composite0   1.10-3+b1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.10-3+b1
ii  libxcb-shm0 1.10-3+b1
ii  libxcb-xv0  1.10-3+b1
ii  libxcb1 1.10-3+b1
ii  libxext62:1.3.3-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.1-4
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  2.2.1-4
ii  vlc-plugin-samba   2.2.1-4
ii  xdg-utils  1.1.1-1

vlc suggests no packages.

Versions of packages vlc-nox depends on:
ii  liba52-0.7.4   0.7.4-18
ii  libasound2 1.0.29-1
ii  libass50.13.0-1
ii  libavahi-client3   0.6.31-5
ii  libavahi-common3   0.6.31-5
ii  libavc1394-0   0.5.4-2
ii  libavcodec-ffmpeg567:2.8-1
ii  libavformat-ffmpeg56   7:2.8-1
ii  libavutil-ffmpeg54 7:2.8-1
ii  libbasicusageenvironment0  2014.01.13-1
ii  libbluray1 1:0.9.0-1
ii  libc6  2.19-22
ii  libcddb2   1.3.2-5
ii  libcdio13  0.83-4.2
ii  libchromaprint01.2-1+b1
ii  libcrystalhd3  1:0.0~git20110715.fdd2f19-11+b1
ii  libdbus-1-31.10.0-3
ii  libdc1394-22   2.2.3-1
ii  libdca00.0.5-7
ii  libdirectfb-1.2-9  1.2.10.0-5.1
ii  libdvbpsi101.3.0-2
ii  libdvdnav4 5.0.3-1
ii  libdvdread45.0.3-1
ii  libebml4v5 1.3.1-5
ii  libfaad2   2.8.0~cvs20150510-1
ii  libflac8   1.3.1-4
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.6-2
ii  libfribidi00.19.7-1
ii  libgcc11:5.2.1-22
ii  libgcrypt201.6.3-2
ii  libgnutls-deb0-28  3.3.18-1
ii  libgpg-error0  1.20-1
ii  libgroupsock1  2014.01.13-1
ii  libjpeg62-turbo1:1.4.1-2
ii  libkate1

Bug#782709: icedove: No special characters in Passwords allowed

2015-08-23 Thread Michael Weghorn
Hi,

I have searched in Mozilla's bug tracker.
There is an upstream Thunderbird bug report which looks to me like it
was dealing with the same issue:

https://bugzilla.mozilla.org/show_bug.cgi?id=312593

Best regards,
Michael



Bug#616361: cups does no longer work with virtual guest (kvm)

2015-08-16 Thread Michael Weghorn
Hi Juergen,

is this still an issue with newer CUPS versions?

I tried this with Debian Jessie on the host and in the KVM virtual
machine (CUPS version is 1.7.5-11+deb8u1) with a virtual NAT network and
it works for me.

I attach my modified version of the file /etc/cups/cupsd.conf of the
host machine.

If it is still a problem: Could you possibly provide some more
information on your KVM setup (particularly network settings)? Is the
cupsd.conf in the bug report the one from the host or from the guest?

Best regards,
Michael
LogLevel debug
MaxLogSize 0
# Allow remote access
Port 631
Listen /var/run/cups/cups.sock
# Share local printers on the local network.
Browsing On
BrowseLocalProtocols dnssd
DefaultAuthType Basic
WebInterface Yes
Location /
  # Allow shared printing...
  Order allow,deny
  Allow @LOCAL
/Location
Location /admin
  Order allow,deny
/Location
Location /admin/conf
  AuthType Default
  Require user @SYSTEM
  Order allow,deny
/Location
Policy default
  JobPrivateAccess default
  JobPrivateValues default
  SubscriptionPrivateAccess default
  SubscriptionPrivateValues default
  Limit Create-Job Print-Job Print-URI Validate-Job
Order deny,allow
  /Limit
  Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs 
Set-Job-Attributes Create-Job-Subscription Renew-Subscription 
Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job 
Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job 
CUPS-Get-Document
Require user @OWNER @SYSTEM
Order deny,allow
  /Limit
  Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class 
CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices
AuthType Default
Require user @SYSTEM
Order deny,allow
  /Limit
  Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer 
Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs 
Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer 
Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs 
CUPS-Reject-Jobs
AuthType Default
Require user @SYSTEM
Order deny,allow
  /Limit
  Limit Cancel-Job CUPS-Authenticate-Job
Require user @OWNER @SYSTEM
Order deny,allow
  /Limit
  Limit All
Order deny,allow
  /Limit
/Policy
Policy authenticated
  JobPrivateAccess default
  JobPrivateValues default
  SubscriptionPrivateAccess default
  SubscriptionPrivateValues default
  Limit Create-Job Print-Job Print-URI Validate-Job
AuthType Default
Order deny,allow
  /Limit
  Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs 
Set-Job-Attributes Create-Job-Subscription Renew-Subscription 
Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job 
Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job 
CUPS-Get-Document
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
  /Limit
  Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class 
CUPS-Delete-Class CUPS-Set-Default
AuthType Default
Require user @SYSTEM
Order deny,allow
  /Limit
  Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer 
Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs 
Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer 
Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs 
CUPS-Reject-Jobs
AuthType Default
Require user @SYSTEM
Order deny,allow
  /Limit
  Limit Cancel-Job CUPS-Authenticate-Job
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
  /Limit
  Limit All
Order deny,allow
  /Limit
/Policy


Bug#793989: cups: printing PDF file with Boomaga PPD not possible

2015-07-30 Thread Michael Weghorn
Hello Brian,

thank you very much for your quick reply.

 Can we think in terms of bug #771259? I've tested with cups 1.7.0-2 and
 ${HOME}/tofile-boomaga is produced. Not so with cups 1.7.1-1.

The cause indeed seems to be the same. I just rebuilt the CUPS packages
currently in Jessie (version 1.7.5-11+deb8u1) with the patch attached to
#771259 and the problem does not occur with this modified version.

Regards,

Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#793989: cups: printing PDF file with Boomaga PPD not possible

2015-07-29 Thread Michael Weghorn
Package: cups
Version: 2.0.3-10
Severity: normal

Dear Maintainer,

when printing a PDF file to a printer set up with the attached PPD file
tofile-boomaga.ppd and the CUPS file backend, no output file is actually
created.

Steps to reproduce:
* allow setting up file devices in CUPS by adding/modifying the
  following line in /etc/cups/cups-files.conf:
  FileDevice Yes
* restart CUPS to make that change active
* set up a printer with the attached PPD file and the CUPS file URI:
  $ sudo lpadmin -p tofile-boomaga -v file:${HOME}/tofile-boomaga -E -P 
tofile-boomaga.ppd  
* print any PDF file to the printer:
  $ lp -d tofile-boomaga test.pdf

Result:
nothing happens, no file ${HOME}/tofile-boomaga is created

Expected result:
The PDF file should be printed to (i.e. saved as) the file
${HOME}/tofile-boomaga.


When I print a text file instead, the file ${HOME}/tofile-boomaga is
created as expected and holds the content of the text file that was sent
to the printer by the command lp -d tofile-boomaga test.txt. (The resulting
file is a PDF file.)

Printing a PDF file as described above still works on wheezy, but not
on jessie or sid.

This does not only affect printing PDF files directly but more use cases,
as many applications produce PDF output when printing a file.
Possibly, this might be a general problem when printing PDF files to
printers that receive PDF input if no additional CUPS filters are involved.

The problem might have to do with the fact that the printed file is already
in PDF format and the PPD file specifies that PDF is expected as input for the
printer and so no real CUPS filters are processed.


The Boomaga project can be found on GitHub here:
https://github.com/Boomaga/boomaga

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

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

Versions of packages cups depends on:
ii  cups-client2.0.3-10
ii  cups-common2.0.3-10
ii  cups-core-drivers  2.0.3-10
ii  cups-daemon2.0.3-10
ii  cups-filters   1.0.71-1
ii  cups-ppdc  2.0.3-10
ii  cups-server-common 2.0.3-10
ii  debconf [debconf-2.0]  1.5.57
ii  ghostscript9.06~dfsg-2
ii  libavahi-client3   0.6.31-5
ii  libavahi-common3   0.6.31-5
ii  libc-bin   2.19-19
ii  libc6  2.19-19
ii  libcups2   2.0.3-10
ii  libcupscgi12.0.3-10
ii  libcupsimage2  2.0.3-10
ii  libcupsmime1   2.0.3-10
ii  libcupsppdc1   2.0.3-10
ii  libgcc11:5.1.1-14
ii  libstdc++6 5.1.1-14
ii  libusb-1.0-0   2:1.0.19-1
ii  lsb-base   4.1+Debian13+nmu1
ii  poppler-utils  0.26.5-2
ii  procps 2:3.3.10-2

Versions of packages cups recommends:
ii  avahi-daemon 0.6.31-5
ii  colord   1.2.1-1+b2
ii  cups-filters [ghostscript-cups]  1.0.71-1
ii  printer-driver-gutenprint5.2.10-3

Versions of packages cups suggests:
ii  cups-bsd   2.0.3-10
pn  cups-pdf   none
ii  foomatic-db-compressed-ppds [foomatic-db]  20150411-1
ii  hplip  3.14.6-1+b2
ii  printer-driver-hpcups  3.14.6-1+b2
pn  smbclient  none
ii  udev   222-2

-- debconf information:
  cupsys/backend: lpd, socket, usb, snmp, dnssd
  cupsys/raw-print: true


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#790307: python-ldap3: wrong Python version in package description

2015-06-27 Thread Michael Weghorn
Package: python-ldap3
Version: 0.9.4.2-1
Severity: minor

Dear Maintainer,

the package description says:
This package contains the Python 3.x version of the library.
However, the package is for Python version 2.x.

The package for Python 3.x is actually called python3-ldap3.

-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages python-ldap3 depends on:
ii  python-pyasn1  0.1.7-1
pn  python:any none

python-ldap3 recommends no packages.

python-ldap3 suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org