I am not @r0ckhopper nor @swh 
but I got that too. It is not related to Plasma 6.7 itself but to spectacle version 6.7. It looks like they added this dependency for this version.
I did get that tesseract update as well. Wondering what it was.
they’re language packages. make sure you select the eng one.
Unless of course English isn’t your native tongue ;0
I have a new install of the KDE desktop 6.7 and I noticed I have had some freezing while trying to add widgets (Application Launcher) to a panel. This is part of the stack dump:
Jun 18 17:02:55 mani systemd-coredump[32991]: [🡕] Process 19930 (plasmashell) of user 1000 dumped core.
Stack trace of thread 19930:
#0 0x0000000000000060 n/a (n/a + 0x0)
#1 0x00007fd5c224d874 n/a (libQt6WaylandClient.so.6 + 0x6e874)
#2 0x00007fd5c22b49b5 _ZN15QtWaylandClient18QWaylandDataSource16data_source_sendERK7QStringi (libQt6WaylandClient.so.6 + 0xd59b5)
#3 0x00007fd5c229e1f1 _ZN9QtWayland14wl_data_source11handle_sendEPvP14wl_data_sourcePKci (libQt6WaylandClient.so.6 + 0xbf1f1)
#4 0x00007fd5c217dac6 n/a (libffi.so.8 + 0x7ac6)
#5 0x00007fd5c217a76b n/a (libffi.so.8 + 0x476b)
#6 0x00007fd5c217d06e ffi_call (libffi.so.8 + 0x706e)
#7 0x00007fd5c3e3277d n/a (libwayland-client.so.0 + 0x477d)
#8 0x00007fd5c3e33609 n/a (libwayland-client.so.0 + 0x5609)
#9 0x00007fd5c3e33a13 wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x5a13)
#10 0x00007fd5c224f37e n/a (libQt6WaylandClient.so.6 + 0x7037e)
#11 0x00007fd5c11f0a59 n/a (libQt6Core.so.6 + 0x1f0a59)
#12 0x00007fd5c149d0f5 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x49d0f5)
#13 0x00007fd5c1191983 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x191983)
#14 0x00007fd5c1e66cfb _ZN10QBasicDrag4dragEP5QDrag (libQt6Gui.so.6 + 0x666cfb)
#15 0x00007fd5c1e6781c _ZN12QDragManager4dragEP5QDrag (libQt6Gui.so.6 + 0x66781c)
#16 0x00007fd5c1e67a6c _ZN5QDrag4execE6QFlagsIN2Qt10DropActionEE (libQt6Gui.so.6 + 0x667a6c)
#17 0x00007fd5c2ee7814 n/a (libQt6Quick.so.6 + 0x4e7814)
#18 0x00007fd5c2ee88c2 _ZN18QQuickDragAttached11qt_metacallEN11QMetaObject4CallEiPPv (libQt6Quick.so.6 + 0x4e88c2)
#19 0x00007fd5c268a723 n/a (libQt6Qml.so.6 + 0x28a723)
#20 0x00007fd5c2774398 _ZN19QQmlPropertyPrivate5writeEP7QObjectRK16QQmlPropertyDataRK8QVariantRK14QQmlRefPointerI15QQmlContextDataE6QFlagsINS2_9WriteFlagEE (libQt6Qml>
#21 0x00007fd5c25fa3e7 _ZN3QV414QObjectWrapper11setPropertyEPNS_15ExecutionEngineEP7QObjectPK16QQmlPropertyDataRKNS_5ValueE (libQt6Qml.so.6 + 0x1fa3e7)
#22 0x00007fd5c25ef669 _ZN3QV414QObjectWrapper14setQmlPropertyEPNS_15ExecutionEngineERK14QQmlRefPointerI15QQmlContextDataEP7QObjectPNS_6StringE6QFlagsINS0_4FlagEERKNS>
#23 0x00007fd5c28072ec _ZN3QV415QQmlTypeWrapper10virtualPutEPNS_7ManagedENS_11PropertyKeyERKNS_5ValueEPS4_ (libQt6Qml.so.6 + 0x4072ec)
#24 0x00007fd5c25cd110 _ZN3QV46Lookup14setterFallbackEPS0_PNS_15ExecutionEngineERNS_5ValueERKS4_ (libQt6Qml.so.6 + 0x1cd110)
#25 0x00007fd533f48edd n/a (n/a + 0x0)
#26 0x00007fd5c266a70d n/a (libQt6Qml.so.6 + 0x26a70d)
#27 0x00007fd5c25b8777 n/a (libQt6Qml.so.6 + 0x1b8777)
#28 0x00007fd5c254dacc _ZNK8QJSValue4callERK5QListIS_E (libQt6Qml.so.6 + 0x14dacc)
#29 0x00007fd5c2bb81d5 _ZN20QQuickItemGrabResult5eventEP6QEvent (libQt6Quick.so.6 + 0x1b81d5)
#30 0x00007fd5c350411f _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x10411f)
#31 0x00007fd5c1183658 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x183658)
#32 0x00007fd5c1183a61 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x183a61)
#33 0x00007fd5c149fc98 n/a (libQt6Core.so.6 + 0x49fc98)
#34 0x00007fd5bf9ebbfd n/a (libglib-2.0.so.0 + 0x61bfd)
#35 0x00007fd5bf9ede57 n/a (libglib-2.0.so.0 + 0x63e57)
#36 0x00007fd5bf9edfe5 g_main_context_iteration (libglib-2.0.so.0 + 0x63fe5)
#37 0x00007fd5c149d0b2 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x49d0b2)
#38 0x00007fd5c1191983 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x191983)
#39 0x00007fd5c1186eaa _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x186eaa)
#40 0x000055769210f5cf n/a (plasmashell + 0x275cf)
#41 0x00007fd5c0827741 n/a (libc.so.6 + 0x27741)
#42 0x00007fd5c0827879 __libc_start_main (libc.so.6 + 0x27879)
#43 0x000055769210fdd5 n/a (plasmashell + 0x27dd5)
Gemini Feedback:
That stack trace points directly to a known kind of friction on Linux: Wayland clipboard/drag-and-drop interactions between different toolkit ecosystems (or mismatched desktop components). Specifically, plasmashell crashed during a Drag and Drop operation (QBasicDrag::drag, QDragManager::drag) while trying to send data over a Wayland data source (QWaylandDataSource::data_source_send). It ultimately hit a null pointer or invalid memory address (#0 0x0000000000000060 n/a), triggering the core dump.
Here is why this is happening and how to address it.
The Root Cause
Because you are running both GNOME 50 and KDE Plasma 6.7 on the same Arch machine, you have a mix of GTK-based and Qt-based environment configurations coexisting.
When you modified the desktop, plasmashell attempted to initiate a drag-and-drop mechanism to grab or move an element (evident in #29 QQuickItemGrabResult5event). Under Wayland, the Qt6 Wayland client layer tried to negotiate a data transfer protocol (wl_data_source) via libffi and libwayland-client. A mismatch or unexpected state in the Wayland compositor data-offer sequence caused plasmashell to read from an invalid memory offset (0x60), crashing the entire shell.
Reminds me of the sort of issues I have with Elisa the music player which creates a new pipewire stream for every track because of regression/behavior change in Qt6 multimedia when in Qt5 it created one audio sink. Generally why I avoid updates to plasma until a patch. I think arch does the same with the kernel. Kind of wish they would hold it back but I’ll just wait until it gets ironed out.
Here it is
thanks @marteng69 
I don’t have that issue.
Me either.
Can’t reproduce any flickering here. Might be a specific driver/hardware issue.
No problems here, maybe try logging in as a new user?
well plasmashell is crashing for me this morning. I can’t get to the desktop. I had to rollback to yesterday morning timeshift I had. I’m ok for now but i’ll have to investigate why 6.7 crashes for me…
Edit : it’s kwin that’s crashing. I’ll investigate after work.
It isn’t a new theme, but to a different theming engine, which makes future changes easier. At the moment they want Union to look the same and people to report cases if it doesn’t.
Ya, it is expected to look the same as Breeze. Different theming engine.
kwin was updated again just a few hours ago. Perhaps this has solved your problem.
Paquete (15) Versión antigua Versión nueva Diferencia neta Tamaño de la descarga
extra/alsa-card-profiles 1:1.6.6-1 1:1.6.7-1 0,00 MiB 0,03 MiB
extra/gst-plugin-pipewire 1:1.6.6-1 1:1.6.7-1 0,00 MiB 0,07 MiB
extra/kwin 6.7.0-1 6.7.0-3 0,00 MiB 10,57 MiB
multilib/lib32-libpipewire 1:1.6.6-1 1:1.6.7-1 0,00 MiB 0,31 MiB
multilib/lib32-mesa 1:26.1.2-2 1:26.1.3-2 0,02 MiB 13,12 MiB
multilib/lib32-pipewire 1:1.6.6-1 1:1.6.7-1 0,00 MiB 1,44 MiB
extra/libpipewire 1:1.6.6-1 1:1.6.7-1 0,00 MiB 0,50 MiB
extra/libwireplumber 0.5.14-1 0.5.15-1 0,07 MiB 0,29 MiB
extra/mesa 1:26.1.2-2 1:26.1.3-2 0,03 MiB 13,21 MiB
extra/pipewire 1:1.6.6-1 1:1.6.7-1 0,00 MiB 0,69 MiB
extra/pipewire-alsa 1:1.6.6-1 1:1.6.7-1 0,00 MiB 0,01 MiB
extra/pipewire-audio 1:1.6.6-1 1:1.6.7-1 0,00 MiB 1,72 MiB
extra/pipewire-jack 1:1.6.6-1 1:1.6.7-1 0,00 MiB 0,17 MiB
extra/pipewire-pulse 1:1.6.6-1 1:1.6.7-1 0,00 MiB 0,21 MiB
extra/wireplumber 0.5.14-1 0.5.15-1 0,06 MiB 0,28 MiB
Tamaño total de la descarga: 42,62 MiB
Tamaño total de la instalación: 160,38 MiB
Tamaño neto tras actualizar: 0,18 MiB
:: ¿Continuar con la instalación? [S/n] s
I finally hurried too 
kinfo
Operating System: EndeavourOS
KDE Plasma Version: 6.7.0
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.0.12-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-3230M CPU @ 2.60GHz
Memory: 8 GiB of RAM (7.7 GiB usable)
Graphics Processor: Intel® HD Graphics 4000
Thanks for the info. I was planning on reapplying the updates in about 45 minutes after work. I’ll keep you posted on it see if this fixes the issue. Otherwise I’ll see what the logs tell me. This is a perfect example of making daily timeshift backup to come back quickly from those kind of issues. It took me more time to remember how to restore timeshift than the actuall restore itself.