Thanks for the crash report. As the message at the top of the summary says, if something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ?

Thanks.

(In reply to TraceyC from comment #1)
> Thanks for the crash report. As the message at the top of the summary says,
> if something crashed, we need a backtrace of it so we can figure out what's
> going on. Can you please attach a backtrace of the crash using the
> coredumpctl command-line program, as detailed in
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ?
> 
> Thanks.

Hi, I have already upload the trace, but the bug is gone after update openSUSE Tumbleweed.
Here is the latest update with no bug, I will close this for now.
Operating System: openSUSE Tumbleweed 20251113
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 4600H with Radeon Graphics
Memory: 8 GiB of RAM (7.6 GiB usable)
Graphics Processor 1: NVIDIA GeForce GTX 1650 Ti
Graphics Processor 2: llvmpipe
Manufacturer: LENOVO
Product Name: 82B5
System Version: Lenovo Legion 5 15ARH05

I celebrate too early, I would like to reopen as the bug persist.

Created attachment 186873 [details]
Crash log debug on konsole

I was able to replicate the issue on konsole, not terminal inside dolphin.

I saw a konsole crash a few days back, while building software. Unfortunately the crashdump has been cleaned up since. I had been building software for several hours and continued for several hours afterward, and only had the one crash.

When I saw this bug report mentioned elsewhere, I had the intention to attempt the replication and collect a crashdump. But obviously, the original procedure is not exactly reliable, and I don't have a reliable method to reproduce the fault, either... 

Is there a new procedure we could follow, to replicate the fault, which actually works (crashes) every time?

That didn't take too long :D This was in Konsole, not Dolphin.

By the way... the instructions at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl

Specifically say to paste this in. I always feel like it's long and I should be making an attachment instead? Anyway:

(gdb) bt
#0  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x00007fa393a9de33 in __pthread_kill_internal (threadid=<optimized out>, signo=11) at pthread_kill.c:89
#2  0x00007fa393a427b6 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3  0x00007fa396095390 in KCrash::defaultCrashHandler(int) () at /lib64/libKF6Crash.so.6
#4  0x00007fa393a42910 in <signal handler called> () at /lib64/libc.so.6
#5  QImage::isNull (this=0x18) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/gui/image/qimage.cpp:1342
#6  0x00007fa394db157d in QPainter::drawImage (this=0x7ffe7ce5d548, targetRect=..., image=..., sourceRect=..., flags=...) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/gui/painting/qpainter.cpp:5197
#7  0x00007fa39126bc68 in QtWaylandClient::QWaylandShmBackingStore::scroll(QRegion const&, int, int) () at /lib64/libQt6WaylandClient.so.6
#8  0x00007fa394cb7131 in QBackingStore::scroll (this=this@entry=0x55cc37c64ad0, area=..., dx=dx@entry=0, dy=dy@entry=-18) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/gui/painting/qbackingstore.cpp:265
#9  0x00007fa395652d03 in QWidgetRepaintManager::bltRect (this=this@entry=0x55cc38191770, rect=..., dx=dx@entry=0, dy=dy@entry=-18, widget=widget@entry=0x55cc37e195a0)
    at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/widgets/kernel/qwidgetrepaintmanager.cpp:532
#10 0x00007fa3956581e2 in QWidgetPrivate::scrollRect (this=0x55cc38181730, rect=..., dx=0, dy=-18) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/widgets/kernel/qwidgetrepaintmanager.cpp:490
#11 0x00007fa395f7c70f in Konsole::TerminalScrollBar::scrollImage(int, QRect const&, Konsole::Character*, int) () at /lib64/libkonsoleprivate.so.25.08.3
#12 0x00007fa395f67510 in Konsole::TerminalDisplay::updateImage() () at /lib64/libkonsoleprivate.so.25.08.3
#13 0x00007fa394435c20 in QtPrivate::QSlotObjectBase::call (this=0x55cc382ac010, r=<optimized out>, a=0x7ffe7ce5da88) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qobjectdefs_impl.h:461
#14 doActivate<false> (sender=0x55cc382d0e30, signal_index=3, argv=0x7ffe7ce5da88) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qobject.cpp:4255
#15 0x00007fa394435c20 in QtPrivate::QSlotObjectBase::call (this=0x55cc37ec86e0, r=<optimized out>, a=0x7ffe7ce5db58) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qobjectdefs_impl.h:461
#16 doActivate<false> (sender=0x55cc38787f10, signal_index=11, argv=0x7ffe7ce5db58) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qobject.cpp:4255
#17 0x00007fa395eb8109 in Konsole::Emulation::showBulk() () at /lib64/libkonsoleprivate.so.25.08.3
#18 0x00007fa394435c20 in QtPrivate::QSlotObjectBase::call (this=0x55cc37eb4ba0, r=<optimized out>, a=0x7ffe7ce5dcb0) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qobjectdefs_impl.h:461
#19 doActivate<false> (sender=0x55cc38787fd0, signal_index=3, argv=0x7ffe7ce5dcb0) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qobject.cpp:4255
#20 0x00007fa39443c0c3 in QMetaObject::activate<void, QTimer::QPrivateSignal> (sender=<optimized out>, mo=<optimized out>, local_signal_index=0, ret=0x0) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qobjectdefs.h:319
#21 QTimer::timeout (this=<optimized out>, _t1=...) at /usr/src/debug/qtbase-everywhere-src-6.10.0/build/src/corelib/Core_autogen/include/moc_qtimer.cpp:182
#22 0x00007fa394423626 in QObject::event (this=<optimized out>, e=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qobject.cpp:1386
#23 0x00007fa3955e7918 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55cc38787fd0, e=0x7ffe7ce5de30) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/widgets/kernel/qapplication.cpp:3307
#24 0x00007fa3943cdc98 in QCoreApplication::notifyInternal2 (receiver=0x55cc38787fd0, event=0x7ffe7ce5de30) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qcoreapplication.cpp:1109
#25 0x00007fa3945729bc in QTimerInfoList::activateTimers (this=0x55cc378e6020) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qtimerinfo_unix.cpp:426
#26 0x00007fa394695f64 in timerSourceDispatch (source=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qeventdispatcher_glib.cpp:152
#27 idleTimerSourceDispatch (source=source@entry=0x55cc378f52b0) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qeventdispatcher_glib.cpp:199
#28 0x00007fa391d6cb36 in g_main_dispatch (context=0x7fa388000f60) at ../glib/gmain.c:3565
#29 g_main_context_dispatch_unlocked (context=context@entry=0x7fa388000f60) at ../glib/gmain.c:4425
#30 0x00007fa391d6fa28 in g_main_context_iterate_unlocked (context=context@entry=0x7fa388000f60, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4490
#31 0x00007fa391d7026c in g_main_context_iteration (context=0x7fa388000f60, may_block=1) at ../glib/gmain.c:4556
#32 0x00007fa394694038 in QEventDispatcherGlib::processEvents (this=0x55cc378a3700, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qeventdispatcher_glib.cpp:399
#33 0x00007fa3943dc12b in QEventLoop::exec (this=0x7ffe7ce5e0a0, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/global/qflags.h:77
#34 0x00007fa3943d2bd3 in QCoreApplication::exec () at /usr/src/debug/qtbase-everywhere-src-6.10.0/src/corelib/kernel/qcoreapplication.cpp:1452
#35 0x000055cbfbcb3f41 in ??? ()
#36 0x00007fa393a2b2fb in __libc_start_call_main (main=main@entry=0x55cbfbcb15c0, argc=argc@entry=1, argv=argv@entry=0x7ffe7ce5e758) at ../sysdeps/nptl/libc_start_call_main.h:58
#37 0x00007fa393a2b3cb in __libc_start_main_impl (main=0x55cbfbcb15c0, argc=1, argv=0x7ffe7ce5e758, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe7ce5e748) at ../csu/libc-start.c:360
#38 0x000055cbfbcb4985 in ??? ()
(gdb)

Sorry, worth mentioning: I had recently cleared the scrollback buffer. Aside from that, everything I was doing was basically identical to what I'd been doing the last couple hours (build, fail, repeat). It's quite possible I'd just done that when it crashed on me last time.

(In reply to pallaswept from comment #8)
> Sorry, worth mentioning: I had recently cleared the scrollback buffer. Aside
> from that, everything I was doing was basically identical to what I'd been
> doing the last couple hours (build, fail, repeat). It's quite possible I'd
> just done that when it crashed on me last time.

Hi,
What is your distro? Is it also openSUSE TW? Your back trace log are similar to mine in that there is something to do with "scroll".

Yes also TW.

> kinfo
Operating System: openSUSE Tumbleweed 20251114
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3090

Under Wayland in openSUSE Tumbleweed I'm also seeing this crash with a similar stack trace when using konsole. The crash also occurs with qterminal. It's reproducable simply by running "vmstat 1" and waiting a little while.

I noticed QtWaylandClient in the stack trace, so as an experiment I started konsole by running "konsole --platform xcb", and so far after several days no crashes; I have over a dozen konsole instances in separate processes, most with multiple tabs, all running fine. Without those args the crash occurs predictably as before.

Bug 512059 appears to be the same issue.

(In reply to pallaswept from comment #7)
> By the way... the instructions at
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
> 
> Specifically say to paste this in. I always feel like it's long and I should
> be making an attachment instead? 

The advantage to pasting the output in the report is that it's searchable. That makes it easier to find reports that are related or duplicate.

Changing the project to Konsole since that's what's crashing.

I'm not able to reproduce this on git-master running 
vmstat 1

*** Bug 512059 has been marked as a duplicate of this bug. ***

(In reply to TraceyC from comment #14)
> I'm not able to reproduce this on git-master running 
> vmstat 1

I started vmstat 1 when you sent this reply, and it just crashed now, so it took about 50 minutes.

My scrollback buffer is unlimited, not sure if relevant (it doesn't normally cause any problem) but it seems possible so I thought I should mention it.

When I posted that last reply, I started another instance of konsole and ran vmstat 1.... It's still going, and I need to kill it off now. I don't think that's a reliable reproduction method either.

*** Bug 512388 has been marked as a duplicate of this bug. ***

*** Bug 512531 has been marked as a duplicate of this bug. ***

Another potential reproducer from the duplicate report:

> -- Information about the crash:
> I had invoked `flatpak run com.stremio.Service`:

(In reply to TraceyC from comment #20)

> Another potential reproducer from the duplicate report:
> 
> > -- Information about the crash:
> > I had invoked `flatpak run com.stremio.Service`:

I'm going to proactively remove the "when compiling software" from the title, because I've since also reproduced this when running `flatpak update -y && sudo dnf upgrade -y --refresh --offline && sudo dnf5 offline reboot -y`, at the `sudo dnf5 offline reboot` stage. Therefore, I seriously doubt that this is specific to software compilation. Apologies if inaccurate.

Oof. This just happened to me while running a system update. Qt6 was halfway through updating at that exact moment, and konsole wouldnt even restart so I could fix the machine. Restored from a snapshot (thanks suse) and did the update again... In a TTY this time.

A warning for others. Do your critical stuff in a TTY until this is fixed.

> A warning for others. Do your critical stuff in a TTY until this is fixed.

Good point! running update in tmux :)

> I'm going to proactively remove the "when compiling software" from the title,

In my experience it crashes when there is output. Compiling usually counts (especially when you run old-style Make which was quite verbose), but I had different crashes when I just ran program which logs. Same for running system update.

Updating Qt from 6.10.0 to 6.10.1 did not resolve the issue.

Operating System: openSUSE Tumbleweed 20251127
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.17.9-11.gcce8896-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600XT 6-Core Processor
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: AMD Radeon RX 9070

I usually see a crash within a few minutes if I start 10 konsole (or qterminal) instances each running "vmstat 1":
> for i in {1..10}; do konsole -e 'vmstat 1' & done

A reliable workaround for me has been to pass the "--platform xcb" arguments to konsole. I've yet to experience a crash with that option:
> konsole --platform xcb

*** Bug 512624 has been marked as a duplicate of this bug. ***

*** Bug 512911 has been marked as a duplicate of this bug. ***

*** Bug 512917 has been marked as a duplicate of this bug. ***

I am also reproducing this since updating Tumbleweed (technically slowroll, which is not great if the package has passed that safety net) a few days ago. It shows up for me as I run my browser from the shell so it's around for a long time.

I can potentially upload a core dump if required, let me know and I will just check if there's anything sensitive in there. Alternatively I might be able to analyse on my machine locally.
```
                                                                  Stack trace of thread 21660:
                                                                  #0  0x00007fa95ae9dd3c __pthread_kill_implementation (libc.so.6 + 0x9dd3c)
                                                                  #1  0x00007fa95ae427b6 raise (libc.so.6 + 0x427b6)
                                                                  #2  0x00007fa95d494360 KCrash::defaultCrashHandler(int) (libKF6Crash.so.6 + 0x8360)
                                                                  #3  0x00007fa95ae42910 __restore_rt (libc.so.6 + 0x42910)
                                                                  #4  0x00007fa95bfbe404 QImage::isNull() const (libQt6Gui.so.6 + 0x1be404)
                                                                  #5  0x00007fa95c1b0ced QPainter::drawImage(QRectF const&, QImage const&, QRectF const&, QFlags<Qt::ImageConversionFlag>) (libQt6Gui.so.6 + 0x3b0ced)
                                                                  #6  0x00007fa957fe1be8 QtWaylandClient::QWaylandShmBackingStore::scroll(QRegion const&, int, int) (libQt6WaylandClient.so.6 + 0xccbe8)
                                                                  #7  0x00007fa95c0b69f1 QBackingStore::scroll(QRegion const&, int, int) (libQt6Gui.so.6 + 0x2b69f1)
                                                                  #8  0x00007fa95ca52383 QWidgetRepaintManager::bltRect(QRect const&, int, int, QWidget*) (libQt6Widgets.so.6 + 0x252383)
                                                                  #9  0x00007fa95ca57862 QWidgetPrivate::scrollRect(QRect const&, int, int) (libQt6Widgets.so.6 + 0x257862)
                                                                  #10 0x00007fa95d37c70f Konsole::TerminalScrollBar::scrollImage(int, QRect const&, Konsole::Character*, int) (libkonsoleprivate.so.25.08.3 + 0x17c70f)
                                                                  #11 0x00007fa95d367510 Konsole::TerminalDisplay::updateImage() (libkonsoleprivate.so.25.08.3 + 0x167510)
                                                                  #12 0x00007fa95b835b20 QtPrivate::QSlotObjectBase::call(QObject*, void**) (libQt6Core.so.6 + 0x235b20)
                                                                  #13 0x00007fa95b835b20 QtPrivate::QSlotObjectBase::call(QObject*, void**) (libQt6Core.so.6 + 0x235b20)
                                                                  #14 0x00007fa95d2b8109 Konsole::Emulation::showBulk() (libkonsoleprivate.so.25.08.3 + 0xb8109)
                                                                  #15 0x00007fa95b835b20 QtPrivate::QSlotObjectBase::call(QObject*, void**) (libQt6Core.so.6 + 0x235b20)
                                                                  #16 0x00007fa95b83bfc3 void QMetaObject::activate<void, QTimer::QPrivateSignal>(QObject*, QMetaObject const*, int, void*, QTimer::QPrivateSignal const&) (libQt6Core.so.6 + 0x23bfc3)
                                                                  #17 0x00007fa95b823966 QObject::event(QEvent*) (libQt6Core.so.6 + 0x223966)
                                                                  #18 0x00007fa95c9e7a78 QApplicationPrivate::notify_helper(QObject*, QEvent*) (libQt6Widgets.so.6 + 0x1e7a78)
                                                                  #19 0x00007fa95b7ce298 QCoreApplication::notifyInternal2(QObject*, QEvent*) (libQt6Core.so.6 + 0x1ce298)
                                                                  #20 0x00007fa95b97157c QTimerInfoList::activateTimers() (libQt6Core.so.6 + 0x37157c)
                                                                  #21 0x00007fa95ba8ede4 timerSourceDispatch (libQt6Core.so.6 + 0x48ede4)
                                                                  #22 0x00007fa958ab5b36 n/a (libglib-2.0.so.0 + 0x5fb36)
                                                                  #23 0x00007fa958ab8a28 n/a (libglib-2.0.so.0 + 0x62a28)
                                                                  #24 0x00007fa958ab926c g_main_context_iteration (libglib-2.0.so.0 + 0x6326c)
                                                                  #25 0x00007fa95ba8ca28 QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (libQt6Core.so.6 + 0x48ca28)
                                                                  #26 0x00007fa95b7dc1ab QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (libQt6Core.so.6 + 0x1dc1ab)
                                                                  #27 0x00007fa95b7d3183 QCoreApplication::exec() (libQt6Core.so.6 + 0x1d3183)

```

Setting to confirmed, given the number of duplicates and people who are experiencing this

*** Bug 513007 has been marked as a duplicate of this bug. ***

Bugreport in openSUSE: https://bugzilla.opensuse.org/show_bug.cgi?id=1254543

(In reply to Oleg from comment #33)
> Bugreport in openSUSE: https://bugzilla.opensuse.org/show_bug.cgi?id=1254543

Quoting this here because I think you've found something interesting:

1. open Konsole or QTerminal and start output-heavy process, like compilation
2. switch to another desktop or minimize window
3. wait a bit

Step 2. We haven't had a reliable method to repro, I think this part might be critical.

I have run EXTREMELY long buffers (like, tailing a logfile spamming errors 100's per second, and falling asleep for a few hours) and had no crash, and then had relatively small buffers cause the crash. Whatever it is, it's not just 'lots of output' that is needed.

I have another laptop with identical software setup (latest Tumbleweed, Wayland), but different hardware - Intel graphics instead of AMD. This issue is not reproducable on it. So graphic drivers might be involved here.

Another observation. Roughly at the same time when this issue in Konsole began, KDE Connect started to crash randomly. More rare, and at absolutely random times, like sitting doing nothing - boom KDE Crash Handler pops up. Again. only on laptop with AMD CPU and graphics.  I haven't investigated these crashes b/c they are much less impactful, but given the timing and symptoms the root cause might be the same.

Given that the crash reports are coming from openSUSE users, the issue migth be related to this patch applied to qt6-base in the openSUSE builds:

https://build.opensuse.org/projects/openSUSE:Factory/packages/qt6-base/files/0001-fix-slow-scrolling-on-wayland.patch

(In reply to ct from comment #36)

> Given that the crash reports are coming from openSUSE users

Per https://bugs.kde.org/show_bug.cgi?id=512531, not solely OSTW. F43, too.

(In reply to Roke Julian Lockhart Beedell from comment #37)
> (In reply to ct from comment #36)
> 
> > Given that the crash reports are coming from openSUSE users
> 
> Per https://bugs.kde.org/show_bug.cgi?id=512531, not solely OSTW. F43, too.

Looks like Fedora also has that patch:

https://src.fedoraproject.org/rpms/qt6-qtbase/c/2ff34253dc5789679d4b7889902c51341ad6b374

*** Bug 513143 has been marked as a duplicate of this bug. ***

I am experiencing exactly the same problem since the last update a few days ago.

Operating System: KDE neon User Edition
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.8.0-88-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics
Memory: 64 GiB of RAM (62.2 GiB usable)
Graphics Processor: AMD Radeon Graphics
Manufacturer: Dell Inc.
Product Name: Inspiron 14 7425 2-in-1
System Version: 1.23.0

(In reply to ct from comment #36)
> Given that the crash reports are coming from openSUSE users, the issue migth
> be related to this patch applied to qt6-base in the openSUSE builds:
> 
> https://build.opensuse.org/projects/openSUSE:Factory/packages/qt6-base/files/
> 0001-fix-slow-scrolling-on-wayland.patch

I have changed the platform to Neon because I experience this bug in KDE neon User Edition since updating a few days ago. The crash happens consistently when the application running in Konsole logs moderately frequently - 1-5 lines per second - for 1 minute or longer.

Operating System: KDE neon User Edition
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.8.0-88-generic (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics
Memory: 64 GiB of RAM (62.2 GiB usable)
Graphics Processor: AMD Radeon Graphics
Manufacturer: Dell Inc.
Product Name: Inspiron 14 7425 2-in-1
System Version: 1.23.0

The stack trace of the thread crashing Konsole:

#0  0x0000726394a9eb2c __pthread_kill_implementation (libc.so.6 + 0x9eb2c)
#1  0x0000726394a4527e __GI_raise (libc.so.6 + 0x4527e)
#2  0x000072639708d5f6 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x95f6)
#3  0x0000726394a45330 __restore_rt (libc.so.6 + 0x45330)
#4  0x0000726395c653b4 _ZNK6QImage6isNullEv (libQt6Gui.so.6 + 0x2653b4)
#5  0x0000726395e295af _ZN8QPainter9drawImageERK6QRectFRK6QImageS2_6QFlagsIN2Qt19ImageConversionFlagEE (libQt6Gui.so.6 + 0x4295af)
#6  0x000072639173240b _ZN15QtWaylandClient23QWaylandShmBackingStore6scrollERK7QRegionii (libQt6WaylandClient.so.6 + 0xab40b)
#7  0x0000726395d49ed1 _ZN13QBackingStore6scrollERK7QRegionii (libQt6Gui.so.6 + 0x349ed1)
#8  0x0000726396a8c2ba _ZN21QWidgetRepaintManager7bltRectERK5QRectiiP7QWidget (libQt6Widgets.so.6 + 0x68c2ba)
#9  0x0000726396a91810 _ZN14QWidgetPrivate10scrollRectERK5QRectii (libQt6Widgets.so.6 + 0x691810)
#10 0x0000726396f655bd _ZN7Konsole17TerminalScrollBar11scrollImageEiRK5QRectPNS_9CharacterEi (libkonsoleprivate.so.25.08.3 + 0x1655bd)
#11 0x0000726396f587eb _ZN7Konsole15TerminalDisplay11updateImageEv (libkonsoleprivate.so.25.08.3 + 0x1587eb)
#12 0x000072639569fc89 n/a (libQt6Core.so.6 + 0x49fc89)
#13 0x000072639569fc89 n/a (libQt6Core.so.6 + 0x49fc89)
#14 0x0000726396eac0e7 _ZN7Konsole9Emulation8showBulkEv (libkonsoleprivate.so.25.08.3 + 0xac0e7)
#15 0x000072639569fc89 n/a (libQt6Core.so.6 + 0x49fc89)
#16 0x000072639564a0ad _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt6Core.so.6 + 0x44a0ad)
#17 0x0000726395632d8e _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x432d8e)
#18 0x0000726396a3d68d _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x63d68d)
#19 0x00007263956d6ec0 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x4d6ec0)
#20 0x00007263955a65e7 _ZN14QTimerInfoList14activateTimersEv (libQt6Core.so.6 + 0x3a65e7)
#21 0x0000726395488271 n/a (libQt6Core.so.6 + 0x288271)
#22 0x00007263921585c5 n/a (libglib-2.0.so.0 + 0x5d5c5)
#23 0x00007263921b7737 n/a (libglib-2.0.so.0 + 0xbc737)
#24 0x0000726392157a63 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca63)
#25 0x0000726395486fef _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x286fef)
#26 0x00007263956e14e3 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4e14e3)
#27 0x00007263956db62f _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x4db62f)
#28 0x00005d46b8928671 n/a (konsole + 0x7671)
#29 0x0000726394a2a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)
#30 0x0000726394a2a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)
#31 0x00005d46b89290e5 n/a (konsole + 0x80e5)

Copied the stack trace from the journal, which doesn't demangle C++ identifiers, for some inexplicable reason. After c++filt:


#0  0x0000726394a9eb2c __pthread_kill_implementation (libc.so.6 + 0x9eb2c)
#1  0x0000726394a4527e __GI_raise (libc.so.6 + 0x4527e)
#2  0x000072639708d5f6 KCrash::defaultCrashHandler(int) (libKF6Crash.so.6 + 0x95f6)
#3  0x0000726394a45330 __restore_rt (libc.so.6 + 0x45330)
#4  0x0000726395c653b4 QImage::isNull() const (libQt6Gui.so.6 + 0x2653b4)
#5  0x0000726395e295af QPainter::drawImage(QRectF const&, QImage const&, QRectF const&, QFlags<Qt::ImageConversionFlag>) (libQt6Gui.so.6 + 0x4295af)
#6  0x000072639173240b QtWaylandClient::QWaylandShmBackingStore::scroll(QRegion const&, int, int) (libQt6WaylandClient.so.6 + 0xab40b)
#7  0x0000726395d49ed1 QBackingStore::scroll(QRegion const&, int, int) (libQt6Gui.so.6 + 0x349ed1)
#8  0x0000726396a8c2ba QWidgetRepaintManager::bltRect(QRect const&, int, int, QWidget*) (libQt6Widgets.so.6 + 0x68c2ba)
#9  0x0000726396a91810 QWidgetPrivate::scrollRect(QRect const&, int, int) (libQt6Widgets.so.6 + 0x691810)
#10 0x0000726396f655bd Konsole::TerminalScrollBar::scrollImage(int, QRect const&, Konsole::Character*, int) (libkonsoleprivate.so.25.08.3 + 0x1655bd)
#11 0x0000726396f587eb Konsole::TerminalDisplay::updateImage() (libkonsoleprivate.so.25.08.3 + 0x1587eb)
#12 0x000072639569fc89 n/a (libQt6Core.so.6 + 0x49fc89)
#13 0x000072639569fc89 n/a (libQt6Core.so.6 + 0x49fc89)
#14 0x0000726396eac0e7 Konsole::Emulation::showBulk() (libkonsoleprivate.so.25.08.3 + 0xac0e7)
#15 0x000072639569fc89 n/a (libQt6Core.so.6 + 0x49fc89)
#16 0x000072639564a0ad QTimer::timeout(QTimer::QPrivateSignal) (libQt6Core.so.6 + 0x44a0ad)
#17 0x0000726395632d8e QObject::event(QEvent*) (libQt6Core.so.6 + 0x432d8e)
#18 0x0000726396a3d68d QApplicationPrivate::notify_helper(QObject*, QEvent*) (libQt6Widgets.so.6 + 0x63d68d)
#19 0x00007263956d6ec0 QCoreApplication::notifyInternal2(QObject*, QEvent*) (libQt6Core.so.6 + 0x4d6ec0)
#20 0x00007263955a65e7 QTimerInfoList::activateTimers() (libQt6Core.so.6 + 0x3a65e7)
#21 0x0000726395488271 n/a (libQt6Core.so.6 + 0x288271)
#22 0x00007263921585c5 n/a (libglib-2.0.so.0 + 0x5d5c5)
#23 0x00007263921b7737 n/a (libglib-2.0.so.0 + 0xbc737)
#24 0x0000726392157a63 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca63)
#25 0x0000726395486fef QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (libQt6Core.so.6 + 0x286fef)
#26 0x00007263956e14e3 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (libQt6Core.so.6 + 0x4e14e3)
#27 0x00007263956db62f QCoreApplication::exec() (libQt6Core.so.6 + 0x4db62f)
#28 0x00005d46b8928671 n/a (konsole + 0x7671)
#29 0x0000726394a2a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)
#30 0x0000726394a2a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)
#31 0x00005d46b89290e5 n/a (konsole + 0x80e5)

kde neon
plasma 6.5.4
qt 6.10.1
konsole 25.12.0

                Module linux-vdso.so.1 from deb linux-6.18.0-061800.202511302339.amd64
                Module libgomp.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
                Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2build1.1.amd64
                Module libsystemd.so.0 from deb systemd-255.4-1ubuntu8.11.amd64
                Module libudev.so.1 from deb systemd-255.4-1ubuntu8.11.amd64
                Module libgcc_s.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
                Module libstdc++.so.6 from deb gcc-14-14.2.0-4ubuntu2~24.04.amd64
                Stack trace of thread 12922:
                #0  0x000074322229eb2c __pthread_kill_implementation (libc.so.6 + 0x9eb2c)
                #1  0x000074322224527e __GI_raise (libc.so.6 + 0x4527e)
                #2  0x00007432244b95f6 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x95f6)
                #3  0x0000743222245330 __restore_rt (libc.so.6 + 0x45330)
                #4  0x00007432234653b4 _ZNK6QImage6isNullEv (libQt6Gui.so.6 + 0x2653b4)
                #5  0x00007432236295af _ZN8QPainter9drawImageERK6QRectFRK6QImageS2_6QFlagsIN2Qt19ImageConversionFlagEE (libQt6Gui.so.6 + 0x4295af)
                #6  0x000074321ef9c40b _ZN15QtWaylandClient23QWaylandShmBackingStore6scrollERK7QRegionii (libQt6WaylandClient.so.6 + 0xab40b)
                #7  0x0000743223549ed1 _ZN13QBackingStore6scrollERK7QRegionii (libQt6Gui.so.6 + 0x349ed1)
                #8  0x000074322428c2ba _ZN21QWidgetRepaintManager7bltRectERK5QRectiiP7QWidget (libQt6Widgets.so.6 + 0x68c2ba)
                #9  0x0000743224291810 _ZN14QWidgetPrivate10scrollRectERK5QRectii (libQt6Widgets.so.6 + 0x691810)
                #10 0x000074322497304e _ZN7Konsole17TerminalScrollBar11scrollImageEiRK5QRectPNS_9CharacterEi (libkonsoleprivate.so.25.12.0 + 0x17304e)
                #11 0x00007432249567d0 _ZN7Konsole15TerminalDisplay11updateImageEv (libkonsoleprivate.so.25.12.0 + 0x1567d0)
                #12 0x0000743222e9fc89 n/a (libQt6Core.so.6 + 0x49fc89)
                #13 0x0000743222e9fc89 n/a (libQt6Core.so.6 + 0x49fc89)
                #14 0x00007432248acfc7 _ZN7Konsole9Emulation8showBulkEv (libkonsoleprivate.so.25.12.0 + 0xacfc7)
                #15 0x0000743222e9fc89 n/a (libQt6Core.so.6 + 0x49fc89)
                #16 0x0000743222e4a0ad _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt6Core.so.6 + 0x44a0ad)
                #17 0x0000743222e32d8e _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x432d8e)
                #18 0x000074322423d68d _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x63d68d)
                #19 0x0000743222ed6ec0 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x4d6ec0)
                #20 0x0000743222da65e7 _ZN14QTimerInfoList14activateTimersEv (libQt6Core.so.6 + 0x3a65e7)
                #21 0x0000743222c88271 n/a (libQt6Core.so.6 + 0x288271)
                #22 0x000074321f9145c5 n/a (libglib-2.0.so.0 + 0x5d5c5)
                #23 0x000074321f973737 n/a (libglib-2.0.so.0 + 0xbc737)
                #24 0x000074321f913a63 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca63)
                #25 0x0000743222c86fef _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x286fef)
                #26 0x0000743222ee14e3 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x4e14e3)
                #27 0x0000743222edb62f _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x4db62f)
                #28 0x0000622bcaed3e68 n/a (konsole + 0x6e68)
                #29 0x000074322222a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)
                #30 0x000074322222a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)
                #31 0x0000622bcaed4c75 n/a (konsole + 0x7c75)

For what it's worth, it also happens on Fedora 43 (crashed some 3 times in the last 24h) mostly during compiles, but also other longer-running tasks with continuous but not overly excessive output.

Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.17.11-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland

Konsole: 25.12.0

*** Bug 513445 has been marked as a duplicate of this bug. ***

*** Bug 513537 has been marked as a duplicate of this bug. ***

*** Bug 513534 has been marked as a duplicate of this bug. ***

Potential fix from openSUSE ?

https://build.opensuse.org/projects/openSUSE:Factory/packages/qt6-base/files/0001-wayland-Fix-crash-in-QWaylandShmBackingStore-scroll.patch

*** Bug 513484 has been marked as a duplicate of this bug. ***

I was consistently hitting this issue under Fedora 43 and managed to get a consistent reproduction, confirmed with a couple of people in the Fedora forums (https://discussion.fedoraproject.org/t/crashing-konsole-since-upgrade-to-f43/177471/15):

* Open Konsole and run the bash snippet `while true; do sleep 0.02; echo 'a line of text that covers a about half a row, give or take'; done`
* Move the Konsole to another desktop or change virtual desktop away from it
* Wait a few seconds for the crash notification

Variants without the sleep, values of 0.01 or 0.1 and higher don't seem to exhibit the crash, 0.05 takes a bit longer to crash. I originally consistently noticed this problem running scripts over SSH and after local attempts to replicate, tried an interleaved sleep to replicate the slightly slower stuttery output. 

I have a T480 laptop and what is happening is obviously timing sensitive, so different machines may not be as consistent. A couple of people in the FC forums gave it a go and did report that it was happening for them, every time. 

(In reply to dm from comment #48)
> Potential fix from openSUSE ?

I pulled down the current Fedora SRPM (qt6-qtbase-6.10.1-2.fc43.src.rpm ) and applied this patch from the SuSE ticket, after a rebuild, can confirm no more crashing.

Additionally, for a quick, no-rebuild workaround, `konsole --platform xcb` to avoid using the Wayland backend with the problem stops crashing for me.

I don't understand why the task isn't progressing. The problem is critical; hundreds of people on KDE can't compile anything using the built-in terminal. Fix is ready, so what's the problem with applying it and release new packages?

*** Bug 513702 has been marked as a duplicate of this bug. ***

(In reply to Vladimir Bely from comment #51)
> I don't understand why the task isn't progressing. The problem is critical;
> hundreds of people on KDE can't compile anything using the built-in
> terminal. Fix is ready, so what's the problem with applying it and release
> new packages?

It is a rather severe bug indeed.

As a workaround, I changed win+o keyboard shortcut to open Alacritty terminal instead of Konsole. No terminal crashes since then.

(In reply to Vladimir Bely from comment #51)
> I don't understand why the task isn't progressing. The problem is critical;
> hundreds of people on KDE can't compile anything using the built-in
> terminal. Fix is ready, so what's the problem with applying it and release
> new packages?

The problem is caused by distributions downstream-patching Qt, so it's them that need to apply the fix. OpenSUSE has done it already, Fedora should do it soon.

(In reply to Nicolas Fella from comment #54)
> The problem is caused by distributions downstream-patching Qt, so it's them
> that need to apply the fix. OpenSUSE has done it already, Fedora should do
> it soon.

When will the bug be fixed on KDE Neon?

(In reply to Nicolas Fella from comment #54)
> (In reply to Vladimir Bely from comment #51)
> > I don't understand why the task isn't progressing. The problem is critical;
> > hundreds of people on KDE can't compile anything using the built-in
> > terminal. Fix is ready, so what's the problem with applying it and release
> > new packages?
> 
> The problem is caused by distributions downstream-patching Qt, so it's them
> that need to apply the fix. OpenSUSE has done it already, Fedora should do
> it soon.

How could this possibly be the case in the light of the identical crash stacktrace on latest KDE Neon reported above, please?

(In reply to Maxim Egorushkin from comment #56)
> (In reply to Nicolas Fella from comment #54)
> > (In reply to Vladimir Bely from comment #51)
> > > I don't understand why the task isn't progressing. The problem is critical;
> > > hundreds of people on KDE can't compile anything using the built-in
> > > terminal. Fix is ready, so what's the problem with applying it and release
> > > new packages?
> > 
> > The problem is caused by distributions downstream-patching Qt, so it's them
> > that need to apply the fix. OpenSUSE has done it already, Fedora should do
> > it soon.
> 
> How could this possibly be the case in the light of the identical crash
> stacktrace on latest KDE Neon reported above, please?

Neon also applied the relevant patch, so it will also need to apply the fix

(In reply to Nicolas Fella from comment #57)
> (In reply to Maxim Egorushkin from comment #56)
> > (In reply to Nicolas Fella from comment #54)
> > > (In reply to Vladimir Bely from comment #51)
> > > > I don't understand why the task isn't progressing. The problem is critical;
> > > > hundreds of people on KDE can't compile anything using the built-in
> > > > terminal. Fix is ready, so what's the problem with applying it and release
> > > > new packages?
> > > 
> > > The problem is caused by distributions downstream-patching Qt, so it's them
> > > that need to apply the fix. OpenSUSE has done it already, Fedora should do
> > > it soon.
> > 
> > How could this possibly be the case in the light of the identical crash
> > stacktrace on latest KDE Neon reported above, please?
> 
> Neon also applied the relevant patch, so it will also need to apply the fix

So, has Neon applied it, or does it need to apply it? Could you please provide a link where I can track the application of the patch in Neon?

(In reply to Vladimir Bely from comment #58)

> > Neon also applied the relevant patch, so it will also need to apply the fix
> 
> So, has Neon applied it, or does it need to apply it? Could you please
> provide a link where I can track the application of the patch in Neon?

It's applied the previous patch, and needs to apply a new one (or revert the previous one).

(In reply to Roke Julian Lockhart Beedell from comment #59)
> (In reply to Vladimir Bely from comment #58)
> 
> > > Neon also applied the relevant patch, so it will also need to apply the fix
> > 
> > So, has Neon applied it, or does it need to apply it? Could you please
> > provide a link where I can track the application of the patch in Neon?
> 
> It's applied the previous patch, and needs to apply a new one (or revert the
> previous one).

What are the urls for patches you refer to, mr Roke Julian Lockhart Beedell, please?

Apologies; I don't know. I'm interested, too. Thanks for asking Mr. Fella.

(In reply to Nicolas Fella from comment #57)
> Neon also applied the relevant patch, so it will also need to apply the fix

What are the urls to the patch and fix you refer to, Nicolas?

(In reply to Maxim Egorushkin from comment #66)
At this point, the conversation is turning into back and forth bickering. With respect to bug reports being focused on the bug itself, and in respect to the people subscribed to this report, I'm asking for this to stop.

I would like to remind you of the KDE Community Code of Conduct:
https://kde.org/code-of-conduct/

Thanks for your understanding.

(In reply to Maxim Egorushkin from comment #68)
> I am genuinely under impression that bots hijacked and control these
> accounts, because their communication is borderline absurd. 
> 

Their communication is normal for their communication style, based on triaging numerous bug reports. Calling their communication "absurd" is a personal attack, which is completely unwarranted. 

I'm closing this report as the conversation is no longer on topic or useful.