Bug 392463 - Okular segfaults all the time when used with emacs/latex
Summary: Okular segfaults all the time when used with emacs/latex
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (show other bugs)
Version: 1.1.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-03-28 18:41 UTC by Sergio
Modified: 2018-10-29 02:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergio 2018-03-28 18:41:54 UTC
When used from emacs on LaTeX documents, okular crashes rather often with a segmentation fault.

Specifically:

- When producing the PDF through lualatex that takes a fairly longer time than pdflatex or xelatex to produce the PDF, okular crashes very frequently while the new PDF is being produced.

- When producing the PDF through lualatex with the -synctex option, okular systematically crashes on opening some files with the --unique file.pdf#src:1/path/./file.tex idiom
Comment 1 Albert Astals Cid 2018-03-31 22:09:21 UTC
Can you provide a backtrace?

Read https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports if you do not understand what backtrace means or how to get one
Comment 2 Christoph Feck 2018-05-01 01:48:57 UTC
If you can provide the information requested in comment #1, please add it.
Comment 3 Christoph Feck 2018-05-30 22:46:39 UTC
To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment.
Comment 4 Sergio 2018-05-31 09:20:22 UTC
To Albert, Christoph,

I need to apologize, but I am overworked and I will be so for at least some more 15 days, with little possibility of testing. I opened the bug with the hope to create a place so that others who could be experiencing my issue could comment and provide further details.

I'll try to get the backtrace and a test case when deadlines relax a bit.
Comment 5 Christoph Feck 2018-06-15 01:06:46 UTC
Sergio, please don't let work burn you out.

KDE developers are still interested in investigating this issue.
Comment 6 Andrew Crouthamel 2018-09-28 03:17:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Andrew Crouthamel 2018-10-29 02:07:57 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!