Bug 409873 - Space before \documentclass{beamer} = crash
Summary: Space before \documentclass{beamer} = crash
Status: RESOLVED WORKSFORME
Alias: None
Product: kile
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.1.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-16 20:57 UTC by olavocontact
Modified: 2019-09-19 04:33 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description olavocontact 2019-07-16 20:57:55 UTC
SUMMARY

Dear Kile Developers,

I noticed that every time I try to open a .tex file with one or more spaces at the first line before  \documentclass{beamer}, kile will immediately crash. 
I could fix the problem removing the space  at the first line. 
Could you please try to reproduce this error?

Thanks in advance.

Olavo


STEPS TO REPRODUCE
1. Open Kile with an empty document and type the following:

 \documentclass{beamer}

\begin{document}
 
\end{document}

2. Notice that  \documentclass{beamer} should be at the 1st line and there is a space before it.
 
3. Save the file

4. Close the file

5. Open the file
 

OBSERVED RESULT
Kile will crash with a segmentation fault error.
E.g: 
Executable: kile PID: 7366 Signal: Segmentation fault (11) Time: 07/16/19 05:56:11 PM


SOFTWARE/OS VERSIONS
Application: kile (2.1.3)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-154-generic x86_64
Distribution: Ubuntu 16.04.6 LTS

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

Report to https://bugs.kde.org/


ADDITIONAL INFORMATION
Comment 1 Kai Uwe Broulik 2019-07-17 07:23:51 UTC
Can you please install debug symbols for kile and kf5texteditor and try generating a backtrace?
Comment 2 Bug Janitor Service 2019-08-01 04:33:09 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
mark the bug 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 3 olavocontact 2019-08-08 20:41:11 UTC
(In reply to Kai Uwe Broulik from comment #1)
> Can you please install debug symbols for kile and kf5texteditor and try
> generating a backtrace?

Could you please point me some reference about how to install debug symbols for kile and kf5texteditor? I tried $ sudo apt-get install kile-dbgsym kf5texteditor, but it didn't work. 
PS: I'm sorry for my ignorance. It's my first time reporting a bug on this forum.
Comment 4 Christoph Feck 2019-08-20 18:47:19 UTC
Some information is available at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please ask in a forum of your distribution for exact package names.
Comment 5 Bug Janitor Service 2019-09-04 04:33:08 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
mark the bug 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 6 Bug Janitor Service 2019-09-19 04:33:10 UTC
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!