Bug#910024: thunderbird: Thunderbird useless after unkonwn automatic upgrades

2018-10-02 Thread Miguel Hermanns
Dear Carsten,

issue found by running Thunderbird in safe mode. The problem was the theme
(nautilus), which is not compatible with Thunderbird 60.0. What is strange,
however, is that Thunderbird 60.0 was automatically disabling the theme due
to its incompatibility, which is good, but it was nevertheless not
rendering correctly the user interface.

Thanks a lot for your help and best regards,

Miguel

On Mon, Oct 1, 2018 at 7:01 PM Carsten Schoenert 
wrote:

> Hello,
>
> Am 01.10.18 um 16:51 schrieb Miguel Hermanns:
> > Package: thunderbird
> > Version: 1:60.0-3~deb9u1
> > Severity: important
> >
> > Dear Maintainer,
> >
> > When I started Thunderbird this morning, after the weekend, several
> > issues have appeared:
> >
> > - Icons for forwarding/responding/etc are no longer there.
> >
> > - Choosing from the right mouse botton menu to answer an email opens a
> >   new window to answer the email, but no text from the original email is
> >   copied for referencing.
> >
> > - Also the list of emails from the email to respond are not shown, nor
> >   the subject with the usual Re: in front.
> >
> > - Attached files are not shown at the bottom of the messages in the
> >   inbox, or anywhere in the window opened for the writing of a new
> >   email.
> >
> > I have updated the packages and restarted the computer to exclude any
> > version issues, but the problems persist. Since the visual aspect of
> > Thunderbird has changed, I assume it has been upgraded automatically
> > during the last week. Or a component/library on which it depends on
> > has been upgraded. At the moment, due to the abovementioned issues,
> > Thunderbird cannot be used on my computer.
> the update of Thunderbird 1:60.0-3~deb9u1 was introduced on 16 Sep 2018,
> this is almost 14 days from now.
>
> https://www.debian.org/security/2018/dsa-4295
>
> If your issue was introduced by Thunderbird itself and you do automatic
> updated this would mean you haven't done automatic update for over 14
> days. This is unlikely.
>
> You can check the time of the thunderbird update by have look into the
> logs of apt
>
>   /var/log/apt/history*
>
> I expect Thunderbird was updated earlier than in the last days.
>
> There are reports from a lot of users with a similar behavior which have
> installed a needed thunbird-l10n and lightning package but not the
> respective lightning-l10n package. Did you have checked the other reports?
>
> Did you have checked the other possibilities as described in the Debian
> wiki?
>
> https://wiki.debian.org/Thunderbird#Bug_Reporting_.2F_Issues
>
> --
> Mit freundlichen Grüßen
> Carsten Schönert
>


Bug#910024: thunderbird: Thunderbird useless after unkonwn automatic upgrades

2018-10-01 Thread Miguel Hermanns
Dear Carsten,

thanks for the fast response. Although you are right that the update could
have taken place earlier than this weekend, I usually keep my programs open
for long times, so that if an update happens, I do not necessarily
see/notice it. I have checked the history files you point out and the
update took place on September 17th, and indeed Thunderbird was not closed
since then until last Friday.

I also see that on that same day also the package lightning was updated,
but no mention of lightning-l10n. In fact, as you mention, the package
lightning-l10n is not installed in my PC. I will check that tomorrow and
let you know if it changes things.

I will also try the other things you mention. As said, tomorrow I report
any new findings.

Thanks again for your help and best regards,

Miguel



On Mon, Oct 1, 2018 at 7:01 PM Carsten Schoenert 
wrote:

> Hello,
>
> Am 01.10.18 um 16:51 schrieb Miguel Hermanns:
> > Package: thunderbird
> > Version: 1:60.0-3~deb9u1
> > Severity: important
> >
> > Dear Maintainer,
> >
> > When I started Thunderbird this morning, after the weekend, several
> > issues have appeared:
> >
> > - Icons for forwarding/responding/etc are no longer there.
> >
> > - Choosing from the right mouse botton menu to answer an email opens a
> >   new window to answer the email, but no text from the original email is
> >   copied for referencing.
> >
> > - Also the list of emails from the email to respond are not shown, nor
> >   the subject with the usual Re: in front.
> >
> > - Attached files are not shown at the bottom of the messages in the
> >   inbox, or anywhere in the window opened for the writing of a new
> >   email.
> >
> > I have updated the packages and restarted the computer to exclude any
> > version issues, but the problems persist. Since the visual aspect of
> > Thunderbird has changed, I assume it has been upgraded automatically
> > during the last week. Or a component/library on which it depends on
> > has been upgraded. At the moment, due to the abovementioned issues,
> > Thunderbird cannot be used on my computer.
> the update of Thunderbird 1:60.0-3~deb9u1 was introduced on 16 Sep 2018,
> this is almost 14 days from now.
>
> https://www.debian.org/security/2018/dsa-4295
>
> If your issue was introduced by Thunderbird itself and you do automatic
> updated this would mean you haven't done automatic update for over 14
> days. This is unlikely.
>
> You can check the time of the thunderbird update by have look into the
> logs of apt
>
>   /var/log/apt/history*
>
> I expect Thunderbird was updated earlier than in the last days.
>
> There are reports from a lot of users with a similar behavior which have
> installed a needed thunbird-l10n and lightning package but not the
> respective lightning-l10n package. Did you have checked the other reports?
>
> Did you have checked the other possibilities as described in the Debian
> wiki?
>
> https://wiki.debian.org/Thunderbird#Bug_Reporting_.2F_Issues
>
> --
> Mit freundlichen Grüßen
> Carsten Schönert
>


Bug#910024: thunderbird: Thunderbird useless after unkonwn automatic upgrades

2018-10-01 Thread Miguel Hermanns
Package: thunderbird
Version: 1:60.0-3~deb9u1
Severity: important

Dear Maintainer,

When I started Thunderbird this morning, after the weekend, several
issues have appeared:

- Icons for forwarding/responding/etc are no longer there.

- Choosing from the right mouse botton menu to answer an email opens a
  new window to answer the email, but no text from the original email is
  copied for referencing.

- Also the list of emails from the email to respond are not shown, nor
  the subject with the usual Re: in front.

- Attached files are not shown at the bottom of the messages in the
  inbox, or anywhere in the window opened for the writing of a new
  email.

I have updated the packages and restarted the computer to exclude any version 
issues, but the problems persist. Since the visual aspect of Thunderbird has 
changed, I assume it has been upgraded automatically during the last week. Or a 
component/library on which it depends on has been upgraded. At the moment, due 
to the abovementioned issues, Thunderbird cannot be used on my computer.

Thanks in advance and best regards,

Miguel



-- System Information:
Debian Release: 9.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages thunderbird depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u3
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.26-0+deb9u1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libgtk2.0-0   2.24.31-2
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.5-1
ii  libpangocairo-1.0-0   1.40.5-1
ii  libpangoft2-1.0-0 1.40.5-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxext6  2:1.3.3-1+b2
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc22.21-2.1+b2
ii  x11-utils 7.7+3+b1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages thunderbird recommends:
ii  hunspell-en-us [hunspell-dictionary]  20070829-7
ii  lightning 1:60.0-3~deb9u1

Versions of packages thunderbird suggests:
pn  apparmor  
ii  fonts-lyx 2.2.2-1
ii  libgssapi-krb5-2  1.15-1+deb9u1

-- no debconf information



Bug#858620: okular freezes regularly the whole desktop for 10 seconds or so. Happens quite often.

2017-03-27 Thread Miguel Hermanns
I have some further information that may (or not) help. If during the
freezing I try to change programs, of course nothing happens. However, when
the desktop gets responsive again, the mouse icon changes and wants to
paste a text document to the next program I click. If it is a text editor
(Kile) or a browser (iceweasel), then indeed a text file is pasted or
opened with extension .desktop.


Bug#858620: okular freezes regularly the whole desktop for 10 seconds or so. Happens quite often.

2017-03-24 Thread Miguel Hermanns
Package: okular
Version: 4:16.08.2-1+b1
Severity: important

Dear Maintainer,

when okular is open and running, the whole desktop freezes regularly for
ten seconds or so. After that the desktop becomes responsive again. This
happens quite often, every few minutes or so, which renders the bug
quite annoying if you tend to have okular always open. 

I cannot tell what triggers a freeze, but I have already
confirmed that the problem goes away once okular is closed and not running.


*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages okular depends on:
ii  kde-runtime 4:16.08.3-1
ii  libc6   2.24-9
ii  libfreetype62.6.3-3+b2
ii  libjpeg62-turbo 1:1.5.1-2
ii  libkdecore5 4:4.14.26-1
ii  libkdeui5   4:4.14.26-1
ii  libkexiv2-114:15.04.3-1
ii  libkio5 4:4.14.26-1
ii  libkparts4  4:4.14.26-1
ii  libkprintutils4 4:4.14.26-1
ii  libkpty44:4.14.26-1
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.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-1
ii  libspectre1 0.2.8-1
ii  libstdc++6  6.3.0-10
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-2
ii  jovie  4:16.08.0-1+b1
pn  okular-extra-backends  
ii  poppler-data   0.4.7-8
ii  texlive-binaries   2016.20160513.41080.dfsg-1
ii  unrar  1:5.3.2-1

-- no debconf information



Bug#858325: k3b: qk3b fails to start from terminal due to symbol lookup error, works otherwise

2017-03-21 Thread Miguel Hermanns
Package: k3b
Version: 2.0.3a-2+b2
Severity: important

Dear Maintainer,

starting k3b from the terminal fails with the following error message:

k3b: symbol lookup error: /usr/lib/x86_64-linux-gnu/libQt3Support.so.4:
undefined symbol: _ZTI9QMenuItem

However, starting k3b from the KDE menu works without problems.


-- Package-specific info:
Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/cdrw
Using /dev/cdrom of unknown capabilities
Device type: Removable CD-ROM
Version: 5
Response Format: 2
Capabilities   : 
Vendor_info: 'HL-DT-ST'
Identification : 'DVDRAM GH24NSD1 '
Revision   : 'LB00'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE 
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages k3b depends on:
ii  cdparanoia 3.10.2+debian-11
ii  cdrdao 1:1.2.3-3
ii  genisoimage9:1.1.11-3+b2
ii  k3b-data   2.0.3a-2
ii  kde-runtime4:16.08.3-1
ii  libc6  2.24-9
ii  libk3b62.0.3a-2+b2
ii  libkcddb4  4:16.08.3-1
ii  libkcmutils4   4:4.14.26-1
ii  libkde3support44:4.14.26-1
ii  libkdecore54:4.14.26-1
ii  libkdeui5  4:4.14.26-1
ii  libkfile4  4:4.14.26-1
ii  libkio54:4.14.26-1
ii  libknotifyconfig4  4:4.14.26-1
ii  libqt4-qt3support  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  libqtwebkit4   2.3.4.dfsg-9.1
ii  libsolid4  4:4.14.26-1
ii  libstdc++6 6.3.0-6
ii  udisks22.1.8-1
ii  wodim  9:1.1.11-3+b2

Versions of packages k3b recommends:
ii  dvd+rw-tools 7.1-11.1
ii  growisofs7.1-11.1
ii  libk3b6-extracodecs  2.0.3a-2+b2
ii  vcdimager0.7.24+dfsg-0.2

Versions of packages k3b suggests:
pn  k3b-extrathemes  
ii  k3b-i18n 2.0.3a-2
pn  kde-config-cddb  
pn  movixmaker-2 
pn  normalize-audio  
ii  sox  14.4.1-5+b2

-- no debconf information



Bug#857946: okular fails to start from terminal reporting incompatible Qt libraries, but works otherwise

2017-03-21 Thread Miguel Hermanns
It seems the problem is not okular related since it affects other programs
too. I wanted to start Libreoffice from the terminal and got exactly the
same error message.

On Thu, Mar 16, 2017 at 4:21 PM, Miguel Hermanns 
wrote:

> Package: okular
> Version: 4:16.08.2-1+b1
> Severity: important
>
> Dear Maintainer,
>
> after installing debian stretch RC2 and rebooting the system a few
> times, okular fails to start from the terminal with the following message:
>
> Cannot mix incompatible Qt library /version 0x40807) with this library
> (version 0x40806)
> Aborted
>
> However, starting okular from inside KDE, for instance from the menu or
> when clicking on an attached pdf file, works perfectly.
>
>
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages okular depends on:
> ii  kde-runtime 4:16.08.3-1
> ii  libc6   2.24-9
> ii  libfreetype62.6.3-3+b2
> ii  libjpeg62-turbo 1:1.5.1-2
> ii  libkdecore5 4:4.14.26-1
> ii  libkdeui5   4:4.14.26-1
> ii  libkexiv2-114:15.04.3-1
> ii  libkio5 4:4.14.26-1
> ii  libkparts4  4:4.14.26-1
> ii  libkprintutils4 4:4.14.26-1
> ii  libkpty44:4.14.26-1
> 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.1-4
> 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-1
> ii  libspectre1 0.2.8-1
> ii  libstdc++6  6.3.0-6
> 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-2
> ii  jovie  4:16.08.0-1+b1
> pn  okular-extra-backends  
> ii  poppler-data   0.4.7-8
> ii  texlive-binaries   2016.20160513.41080.dfsg-1
> ii  unrar  1:5.3.2-1
>
> -- no debconf information
>


Bug#858029: partman-efi: Manual partinioning in EFI system without EFI boot partition does not trigger an error message

2017-03-17 Thread Miguel Hermanns
I don't have them, sorry :-(

Sadly, I cannot reproduce the error for you, since the computer is already
in use now.

On Fri, Mar 17, 2017 at 5:54 PM, Steve McIntyre  wrote:

> On Fri, Mar 17, 2017 at 05:37:07PM +0100, Miguel Hermanns wrote:
> >No other OS installed and I did not get that message.
> >
> >I'm using an NVMe Samsung 960 EVO drive for / and swap, and a traditional
> >WD Red for /home. I don't know if that may have an influence.
>
> OK, this is weird. :-/
>
> I don't suppose you kept the installation logs from the first
> installation attempt? I can't explain the differences in what we're
> seeing, and they would help.
>
> --
> Steve McIntyre, Cambridge, UK.
> st...@einval.com
> "You can't barbecue lettuce!" -- Ellie Crane
>
>


Bug#858029: partman-efi: Manual partinioning in EFI system without EFI boot partition does not trigger an error message

2017-03-17 Thread Miguel Hermanns
No other OS installed and I did not get that message.

I'm using an NVMe Samsung 960 EVO drive for / and swap, and a traditional
WD Red for /home. I don't know if that may have an influence.

Best regards,

Miguel


On Fri, Mar 17, 2017 at 5:20 PM, Steve McIntyre  wrote:

> On Fri, Mar 17, 2017 at 05:03:17PM +0100, Miguel Hermanns wrote:
> >Dear Steve,
> >
> >It was the first time I installed something in EFI mode, as in the past I
> >always switched back to legacy mode. So I'm quite sure I booted in EFI
> >mode.
> >
> >After the installation and seeing that the computer was not booting, I
> >started to research in the internet and found the Debian installation
> guide
> >I mention in the bug report. After that I started to understand what was
> >going wrong and I installed again Debian from scratch and without changing
> >anything in the BIOS. But this time I allowed partman to do a guided
> >partitioning, which I afterwards tuned to my needs. Partman of course
> >included the EFI boot partition, and this time everything went fine.
>
> OK, I'm struggling to reproduce this here. I've just started 2 test
> EFI installations in a VM. Create just a single filesystem on a blank
> disk with no ESP and I get
>
>   No EFI partition was found.
>
>   Go back to the menu and resume partitioning?
>
> when I say "Finish partitioning". Was there any other OS installed
> already on the system?
>
> --
> Steve McIntyre, Cambridge, UK.
> st...@einval.com
> Google-bait:   http://www.debian.org/CD/free-linux-cd
>   Debian does NOT ship free CDs. Please do NOT contact the mailing
>   lists asking us to send them to you.
>
>


Bug#858029: partman-efi: Manual partinioning in EFI system without EFI boot partition does not trigger an error message

2017-03-17 Thread Miguel Hermanns
Dear Steve,

It was the first time I installed something in EFI mode, as in the past I
always switched back to legacy mode. So I'm quite sure I booted in EFI
mode.

After the installation and seeing that the computer was not booting, I
started to research in the internet and found the Debian installation guide
I mention in the bug report. After that I started to understand what was
going wrong and I installed again Debian from scratch and without changing
anything in the BIOS. But this time I allowed partman to do a guided
partitioning, which I afterwards tuned to my needs. Partman of course
included the EFI boot partition, and this time everything went fine.

Best regards,

Miguel

On Fri, Mar 17, 2017 at 3:57 PM, Steve McIntyre  wrote:

> On Fri, Mar 17, 2017 at 03:20:33PM +0100, Miguel Hermanns wrote:
> >Package: partman-efi
> >Version: 75
> >Severity: important
> >
> >Dear Maintainer,
> >
> >When installing debian stretch RC2, manual partitioning was done without
> >specifying an EFI boot partition. This did not trigger an error message
> >by partman, although according to section 6.3.3.3 of the installation
> >guide it should have done so.
>
> Hi Miguel,
>
> That's how the code has worked for me in the past, and it's not
> changed in quite a while. Are you sure you booted in EFI mode?
>
> --
> Steve McIntyre, Cambridge, UK.
> st...@einval.com
> "When C++ is your hammer, everything looks like a thumb." -- Steven M.
> Haflich
>
>


Bug#858029: partman-efi: Manual partinioning in EFI system without EFI boot partition does not trigger an error message

2017-03-17 Thread Miguel Hermanns
Package: partman-efi
Version: 75
Severity: important

Dear Maintainer,

When installing debian stretch RC2, manual partitioning was done without
specifying an EFI boot partition. This did not trigger an error message
by partman, although according to section 6.3.3.3 of the installation
guide it should have done so. 

The result was that the computer was unable to boot after the
first stage of the installation.




-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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



Bug#857946: okular fails to start from terminal reporting incompatible Qt libraries, but works otherwise

2017-03-16 Thread Miguel Hermanns
Package: okular
Version: 4:16.08.2-1+b1
Severity: important

Dear Maintainer,

after installing debian stretch RC2 and rebooting the system a few
times, okular fails to start from the terminal with the following message:

Cannot mix incompatible Qt library /version 0x40807) with this library
(version 0x40806)
Aborted

However, starting okular from inside KDE, for instance from the menu or
when clicking on an attached pdf file, works perfectly.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages okular depends on:
ii  kde-runtime 4:16.08.3-1
ii  libc6   2.24-9
ii  libfreetype62.6.3-3+b2
ii  libjpeg62-turbo 1:1.5.1-2
ii  libkdecore5 4:4.14.26-1
ii  libkdeui5   4:4.14.26-1
ii  libkexiv2-114:15.04.3-1
ii  libkio5 4:4.14.26-1
ii  libkparts4  4:4.14.26-1
ii  libkprintutils4 4:4.14.26-1
ii  libkpty44:4.14.26-1
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.1-4
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-1
ii  libspectre1 0.2.8-1
ii  libstdc++6  6.3.0-6
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-2
ii  jovie  4:16.08.0-1+b1
pn  okular-extra-backends  
ii  poppler-data   0.4.7-8
ii  texlive-binaries   2016.20160513.41080.dfsg-1
ii  unrar  1:5.3.2-1

-- no debconf information