Summary: | Okular crashed while screen was locked by user. | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Thomas Michalka <Thomas.Michalka> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aacid |
Priority: | NOR | ||
Version: | 0.17.5 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Thomas Michalka
2014-09-10 10:14:48 UTC
The crash happend while the desktop/screen was locked. After I logged in again the crash handler window showed me the crash of okular. Unfortunatey I don't know which file okular has been showing before the crash. Where you modifying the file? (latex regeneration or similar? Hi,
Am 11.09.2014 10:29, schrieb Albert Astals Cid:
> https://bugs.kde.org/show_bug.cgi?id=338971
>
> Albert Astals Cid <aacid@kde.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Resolution|--- |WAITINGFORINFO
> Status|UNCONFIRMED |NEEDSINFO
> CC| |aacid@kde.org
>
> --- Comment #2 from Albert Astals Cid <aacid@kde.org> ---
> Where you modifying the file? (latex regeneration or similar?
Neither did I nor a process. That's for sure so far.
I think the PDF-file was opened by clicking on a link in FF or on an
attachment entry in TB. Unfortunately I don't know this more exactly
because opening happened some days before the crash of okular.
HTH, Tom
Looking at the backtrace of the crash i'm pretty sure we've fixed this in newer versions (you're using a relatively old okular version) so i'm going to mark this as fixed. Thanks for caring about Okular and reporting this bug. |