tag 908095 upstream
thanks
local10 - 07.09.18, 12:15:
> Was able to open the problematic file by reconfiguring Kwrite and
> changing the default encoding to UTF-8 and the fallback encoding to
> UTF-16 (Kwrite keeps changing UTF-16 to ucs2 but whatever).
>
> That's a good news for me, of course, b
Was able to open the problematic file by reconfiguring Kwrite and changing the
default encoding to UTF-8 and the fallback encoding to UTF-16 (Kwrite keeps
changing UTF-16 to ucs2 but whatever).
That's a good news for me, of course, but still I feel Kwrite shouldn't crash
like that even if the d
Sep 6, 2018, 12:38 PM by bernha...@mailbox.org:
> Then you could press the reload button in the crash reporting window
> and it should give a better readable stack.
> (That way more likely to attract some maintainer.)
>
OK, one more time after definitely pressing the Reload button. Please see the
Sep 6, 2018, 12:38 PM by bernha...@mailbox.org:
> just found your report and tried to reproduce the crash.
>
> First I assume you copied this text from the crash reporting window?
>
Yes. Also, kwrite was launched from LXDE.
> Unfortunately my test file does not get me that far to the crash.
> T
Hello,
just found your report and tried to reproduce the crash.
First I assume you copied this text from the crash reporting window?
This information would be way more readable if you would install
the debug symbols for the executable and all the shared objects in
the crashing stack.
Like describe
Package: kwrite
Version: 4:18.04.0-1
Severity: important
Kwrite crashes while opening a file, kwrite was able to open this file in
Wheezy consistently without any issues.
Thanks
Executable: kwrite PID: 9355 Signal: Segmentation fault (11) Time: 9/6/18
01:31:20
Applic
6 matches
Mail list logo
