https://bugs.kde.org/show_bug.cgi?id=463475
Nicolas Fella changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #29 from Bernhard Übelacker ---
Added some details about the possible source of this problematic huge
dimensions to https://bugs.kde.org/show_bug.cgi?id=473602.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #28 from Bernhard Übelacker ---
Some short additions:
- I am getting this with X server.
The resize event way up in the stack looks like
the new width should change from 1920 to 65528 and the height from 996 to
65504.
With 4 bytes per pixel
https://bugs.kde.org/show_bug.cgi?id=463475
Bernhard Übelacker changed:
What|Removed |Added
CC||bernha...@mailbox.org
--- Comment #27 from
https://bugs.kde.org/show_bug.cgi?id=463475
Dick Tracey changed:
What|Removed |Added
CC||traceyd...@yandex.com
--- Comment #26 from Dick T
https://bugs.kde.org/show_bug.cgi?id=463475
aux...@gmail.com changed:
What|Removed |Added
CC||aux...@gmail.com
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=463475
Matan Ziv-Av changed:
What|Removed |Added
CC||a...@haxalot.com
--- Comment #25 from Matan Ziv-
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #24 from Lukas Bergdoll ---
Sorry for the late reply. I'm now using a custom release build version from
your branch. And so far I've not seen crashes.
Also I want to add, that it was a pleasant surprise how easy it was to build
konsole, cle
https://bugs.kde.org/show_bug.cgi?id=463475
Celeste Wouters changed:
What|Removed |Added
CC||pe...@elementw.net
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #23 from Matan Ziv-Av ---
> linewidth = 4093
This was my suspicion. It seems as if the fake screen created by Qt is very
wide (or has a weird DPI that causes the font to be very narrow in pixels).
My patch should prevent bidi code from cra
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #22 from Lukas Bergdoll ---
Created attachment 155703
--> https://bugs.kde.org/attachment.cgi?id=155703&action=edit
27_01_2023_crash_with_current_logline
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #21 from Lukas Bergdoll ---
(In reply to Matan Ziv-Av from comment #20)
> Anyone that can reproduce this crash reliably is invited to test with this
> branch:
> https://invent.kde.org/matan/konsole/-/commits/sleep-crash
> Which tries to hand
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #20 from Matan Ziv-Av ---
Anyone that can reproduce this crash reliably is invited to test with this
branch:
https://invent.kde.org/matan/konsole/-/commits/sleep-crash
Which tries to handle two issues that might cause this crash.
--
You ar
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #19 from Lukas Bergdoll ---
I'll do more experiments tomorrow. What I found is, that adding a new tab and
doing some work in the tabs, ls etc. helps with making it crash. Just opening
konsole, without doing anything has yet to yield a crash
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #18 from Matan Ziv-Av ---
I had one crash which might be similar, out of 32 attempts of turning the
monitor off and on. Unfortunately, without a core dump.
This is the error output:
qt.qpa.xcb: xcb_shm_create_segment() can't be called for
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #17 from Matan Ziv-Av ---
(In reply to Lukas Bergdoll from comment #15)
> New crash after turning off display shorty after crash
>
> The old crash happened after longer use, and that backtrace looked like a
> smashed stack. I have screensho
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #16 from Lukas Bergdoll ---
> New crash after turning off display shorty after crash
I meant to write:
New crash after turning off display. Then after turning it back on, I get this
crash:
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #15 from Lukas Bergdoll ---
New crash after turning off display shorty after crash
Thread 1 "konsole" received signal SIGSEGV, Segmentation fault.
__memcpy_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:27
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #14 from Lukas Bergdoll ---
Yes, and only if the monitor goes to sleep.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #13 from Matan Ziv-Av ---
(In reply to Lukas Bergdoll from comment #10)
> I have the same issue, it keeps crashing it always crashes in
> TerminalDisplay.cpp:3165 `log2line[i] = pos;`. Disabling bidi did not help,
> nor did rolling back to k
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #12 from Lukas Bergdoll ---
qt5-base 5.15.8+kde+r174-1 Arch Linux package. And I use X11.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #11 from Shmerl ---
(In reply to Lukas Bergdoll from comment #10)
> I have the same issue, it keeps crashing it always crashes in
> TerminalDisplay.cpp:3165 `log2line[i] = pos;`. Disabling bidi did not help,
> nor did rolling back to konsole
https://bugs.kde.org/show_bug.cgi?id=463475
Lukas Bergdoll changed:
What|Removed |Added
CC||lukas.bergd...@gmail.com
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #9 from Shmerl ---
Looks like after Qt 5.15.8 this bug is gone. I'll keep watching if it happens
and after a while not, I can close this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #8 from Shmerl ---
Looks like when konsole is run in xcb mode (XWayland), there is still a freeze
issue (not crash) that still happens even with bidirectional option disabled.
But it might be another problem. I can open a separate bug.
--
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #7 from Shmerl ---
If that makes a difference, my current Konsole profile is using DejaVu Sans
Mono font.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #6 from Shmerl ---
Looks like it didn't crash so far in such scenario with bi-directional text
rendering option disabled! I'll test it a bit more to confirm further, but it
looks like it indeed narrows it down.
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #5 from Matan Ziv-Av ---
(In reply to Shmerl from comment #4)
> How can I disable it?
Settings -> Edit current profile... -> Appearance -> Complex Text Layout ->
Bi-Directional text rendering
--
You are receiving this mail because:
You ar
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #4 from Shmerl ---
How can I disable it?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463475
Matan Ziv-Av changed:
What|Removed |Added
CC||ma...@svgalib.org
--- Comment #3 from Matan Ziv-
https://bugs.kde.org/show_bug.cgi?id=463475
Shmerl changed:
What|Removed |Added
Version|22.12.0 |22.12.1
--
You are receiving this mail because:
You a
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #2 from Shmerl ---
Crash still happens with konsole 22.12.1.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463475
--- Comment #1 from Shmerl ---
Just to add, I'm running it in KDE Wayland session, Wayland mode.
--
You are receiving this mail because:
You are watching all bug changes.
33 matches
Mail list logo
