[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#860366: marked as done (okular: Okular crashes when opening some documents)



Your message dated Tue, 16 Jan 2018 22:31:27 +0100
with message-id <[🔎] 76f292e9-ebda-8029-73e3-d6bb0a11cfd0@posteo.de>
and subject line Re: okular: Okular crashes when opening some documents
has caused the Debian Bug report #860366,
regarding okular: Okular crashes when opening some documents
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
860366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860366
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: okular
Version: 4:16.08.2-1+b1
Severity: normal

Dear Maintainer,

when I try to open 

http://scw.bokomoko.de/~rd/fdbaut/2013-08-28-Uebersichtsplan.pdf

with okular, it crashes.

Evince opens on the same system the document without any problems.

Thanks
Rainer


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (300, 'unstable'), (250, 'experimental')
Architecture: i386 (i686)
Foreign Architectures: amd64

Kernel: Linux 4.9.0-2-686-pae (SMP w/2 CPU cores)
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 okular depends on:
ii  kde-runtime         4:16.08.3-2
ii  libc6               2.24-9
ii  libfreetype6        2.6.3-3.1
ii  libgcc1             1:6.3.0-12
ii  libjpeg62-turbo     1:1.5.1-2
ii  libkdecore5         4:4.14.26-1
ii  libkdeui5           4:4.14.26-1
ii  libkexiv2-11        4: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  libkpty4            4:4.14.26-1
ii  libokularcore7      4:16.08.2-1+b1
ii  libphonon4          4:4.9.0-4
ii  libpoppler-qt4-4    0.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-12
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  ghostscript            9.20~dfsg-3
pn  jovie                  <none>
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
ii  unrar                  1:5.3.2-1

-- no debconf information

--- End Message ---
--- Begin Message ---
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
> 
> 

--- End Message ---

Reply to: