https://bugs.kde.org/show_bug.cgi?id=373399
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=373399
--- Comment #6 from Bug Janitor Service ---
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 b
https://bugs.kde.org/show_bug.cgi?id=373399
--- Comment #5 from Krzysztof ---
Currently, I do not use this software therefore I cannot confirm whether it
happens with new version of software.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373399
Justin Zobel changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=373399
--- Comment #3 from Krzysztof ---
This type of crash isn't reproducible in a sense that it's not known what it
causes. It happens very rarely. However, after it crashes already it usually
would crash several times afterwards. As I remind, some time it a
https://bugs.kde.org/show_bug.cgi?id=373399
--- Comment #2 from Kevin Funk ---
@Krzysztof: Looks like a duplicate of bug 338289.
Is the crash reproducible?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373399
--- Comment #1 from Kevin Funk ---
Pasting backtrace of crashed thread inline:
Thread 12 (Thread 0x7f63fbbe2700 (LWP 9696)):
[KCrash Handler]
#6 0x in ?? ()
#7 0x7f640854e212 in Lexer::tokenize (this=this@entry=0x7f63fbbe1910,
_se
