[kwin] [Bug 487306] New: Nested kwin_wayland was unresponsive in VMs using the virgl driver with an XWayland crash

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=487306

Bug ID: 487306
   Summary: Nested kwin_wayland was unresponsive in VMs using the
virgl driver with an XWayland crash
Classification: Plasma
   Product: kwin
   Version: 6.0.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: ---

SUMMARY

I booted the Fedora Rawhide/41 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20240518.n.0.iso in a QEMU/KVM VM using GNOME
Boxes with 3D acceleration enabled using the virgl driver from mesa 24.1.0-rc4.
Plasma 6.0.4 on Wayland started. I started Konsole. I tried to run a nested
kwin_wayland session using the instructions at
https://community.kde.org/KWin/Wayland
export $(dbus-launch)
kwin_wayland --xwayland 

The nested kwin_wayland window appeared but was unresponsive. The kwin_wayland
output in Konsole showed a crash in XWayland.

kwin_wayland --xwayland
No backend specified, automatically choosing Wayland because WAYLAND_DISPLAY is
set
unable to lock lockfile /run/user/1000/wayland-0.lock, maybe another compositor
is running
Accepting client connections on sockets: QList("wayland-1")
OpenGL vendor string:   Mesa
OpenGL renderer string: virgl (AMD Radeon R5 Graphics
(radeonsi, carrizo, LLVM 18.1...)
OpenGL version string:  4.3 (Core Profile) Mesa 24.1.0-rc4
OpenGL shading language version string: 4.30
Driver: Unknown
GPU class:  Unknown
OpenGL version: 4.3
GLSL version:   4.30
Mesa version:   24.1
Requires strict binding:no
Virtual Machine:no
Timer query support:yes
linux_dmabuf_feedback.main_device: Failed to fetch DRM device
linux_dmabuf_feedback.tranche_target_device: Failed to fetch DRM device
linux_dmabuf_feedback.tranche_target_device: Failed to fetch DRM device
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/Xwayland (0x557c2ad2d000+0x1660c2) [0x557c2ae930c2]
(EE) 1: /usr/bin/Xwayland (0x557c2ad2d000+0x1661c5) [0x557c2ae931c5]
(EE) 2: /lib64/libc.so.6 (0x7f55eb00c000+0x40750) [0x7f55eb04c750]
(EE) 3: /usr/bin/Xwayland (0x557c2ad2d000+0x41075) [0x557c2ad6e075]
(EE) 4: /usr/bin/Xwayland (0x557c2ad2d000+0x3466f) [0x557c2ad6166f]
(EE) 5: /usr/bin/Xwayland (0x557c2ad2d000+0x1fa76) [0x557c2ad4ca76]
(EE) 6: /lib64/libc.so.6 (0x7f55eb00c000+0x2a1c8) [0x7f55eb0361c8]
(EE) 7: /lib64/libc.so.6 (__libc_start_main+0x8b) [0x7f55eb03628b]
(EE) 8: /usr/bin/Xwayland (0x557c2ad2d000+0x224c5) [0x557c2ad4f4c5]
(EE)
(EE) Segmentation fault at address 0x8
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)

The Xwayland crash was in xwl_glamor_gbm_init_main_dev in frame 10 from
xorg-x11-server-Xwayland-24.1.0-1.fc41. The crashing line in
xwl_glamor_gbm_init_main_dev had a null pointer main_dev so
main_dev->available_nodes looked like a null pointer dereference. 

Core was generated by `/usr/bin/Xwayland :1 -listenfd 61 -listenfd 62
-displayfd 52 -rootless -wm 56'.
Program terminated with signal SIGABRT, Aborted.
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
Downloading source file
/usr/src/debug/glibc-2.39.9000-18.fc41.x86_64/nptl/pthread_kill.c
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
(gdb) bt
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x7f55eb0a41f3 in __pthread_kill_internal (threadid=,
signo=6) at pthread_kill.c:78
#2  0x7f55eb04c69e in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3  0x7f55eb034942 in __GI_abort () at abort.c:79
#4  0x557c2ae9c86a in OsAbort () at ../os/utils.c:1283
#5  0x557c2ae9caee in AbortServer () at ../os/log.c:892
#6  FatalError (f=) at ../os/log.c:1030
#7  0x557c2ae93222 in OsSigHandler (unused=, signo=11,
sip=) at ../os/osinit.c:156
#8  OsSigHandler (signo=11, sip=, unused=) at
../os/osinit.c:110
#9  
#10 xwl_glamor_gbm_init_main_dev (xwl_screen=) at
../hw/xwayland/xwayland-glamor-gbm.c:1517
#11 xwl_glamor_gbm_init_egl (xwl_screen=) at
../hw/xwayland/xwayland-glamor-gbm.c:1552
#12 xwl_glamor_init (xwl_screen=0x557c42ab86d0) at
../hw/xwayland/xwayland-glamor.c:232
#13 0x557c2ad6166f in xwl_screen_init (pScreen=0x557c42ab8040,
argc=, argv=) at
../hw/xwayland/xwayland-screen.c:1109
#14 0x557c2ad4ca76 in AddScreen (pfnInit=, argc=, argv=) at ../dix/dispatch.c:3993
#15 InitOutput (screen_info=, argc=,
argv=) at ../hw/xwayland/xwayland.c:455
#16 dix_main (argc=, argv=, envp=)
at ../dix/main.c:193
#17 main (argc=, argv=, envp=) at

[kwin] [Bug 487217] New: Nested kwin_wayland crashed in KWin::EglSwapchainSlot::buffer in VMs using the llvmpipe driver

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=487217

Bug ID: 487217
   Summary: Nested kwin_wayland crashed in
KWin::EglSwapchainSlot::buffer in VMs using the
llvmpipe driver
Classification: Plasma
   Product: kwin
   Version: 6.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: ---

Created attachment 169605
  --> https://bugs.kde.org/attachment.cgi?id=169605=edit
kwin_wayland crash trace output from drkonqi

SUMMARY

I booted the Fedora Rawhide/41 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20240518.n.0.iso in a QEMU/KVM VM using GNOME
Boxes with 3D acceleration disabled using the llvmpipe driver from mesa
24.1.0-rc4. Plasma 6.0.4 on Wayland started. I started Konsole. I tried to run
a nested kwin_wayland session using the instructions at
https://community.kde.org/KWin/Wayland
export $(dbus-launch)
kwin_wayland --xwayland 

The nested kwin_wayland window didn't appear. A Wayland icon appeared in the
task manager briefly then disappeared. The following output was in Konsole
which showed a Permission denied error and a segmentation fault of
kwin_wayland.

export $(dbus-launch)
kwin_wayland --xwayland
No backend specified, automatically choosing Wayland because WAYLAND_DISPLAY is
set
unable to lock lockfile /run/user/1000/wayland-0.lock, maybe another compositor
is running
Accepting client connections on sockets: QList("wayland-1")
OpenGL vendor string:   Mesa
OpenGL renderer string: llvmpipe (LLVM 18.1.4, 256 bits)
OpenGL version string:  4.5 (Core Profile) Mesa 24.1.0-rc4
OpenGL shading language version string: 4.50
Driver: LLVMpipe
GPU class:  Unknown
OpenGL version: 4.5
GLSL version:   4.50
Mesa version:   24.1
Requires strict binding:no
Virtual Machine:no
Timer query support:yes
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Segmentation fault (core dumped)
liveuser@localhost-live:~$ The Wayland connection broke. Did the Wayland
compositor die?

The nested kwin_wayland crashed in KWin::EglSwapchainSlot::buffer. The crash
might've been due to a null pointer dereference since this=0x0 in
KWin::EglSwapchainSlot::buffer.

Core was generated by `kwin_wayland --xwayland'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  KWin::EglSwapchainSlot::buffer (this=0x0) at
/usr/src/debug/kwin-6.0.4.1-3.fc41.x86_64/src/opengl/eglswapchain.cpp:39
39  return m_buffer;
[Current thread is 1 (Thread 0x7f1ca443ab00 (LWP 2894))]

Thread 1 (Thread 0x7f1ca443ab00 (LWP 2894)):
#0  KWin::EglSwapchainSlot::buffer (this=0x0) at
/usr/src/debug/kwin-6.0.4.1-3.fc41.x86_64/src/opengl/eglswapchain.cpp:39
#1  0x7f1ca526dd18 in KWin::Wayland::WaylandEglPrimaryLayer::present
(this=0x556c1bcd3a50) at /usr/include/c++/14/bits/shared_ptr_base.h:1666
#2  KWin::Wayland::WaylandEglBackend::present (this=,
output=, frame=std::shared_ptr (use count 1,
weak count 0) = {...}) at
/usr/src/debug/kwin-6.0.4.1-3.fc41.x86_64/src/backends/wayland/wayland_egl_backend.cpp:330
#3  0x7f1ca4fa8496 in KWin::Compositor::composite (this=0x556c18467990,
renderLoop=) at
/usr/src/debug/kwin-6.0.4.1-3.fc41.x86_64/src/compositor.cpp:201
#4  0x7f1ca23fa3c4 in QtPrivate::QSlotObjectBase::call
(this=0x556c1bd50870, r=, a=0x7ffcfc84dbf0) at
/usr/src/debug/qt6-qtbase-6.7.0-5.fc41.x86_64/src/corelib/kernel/qobjectdefs_impl.h:469
#5  doActivate (sender=0x556c183c01f0, signal_index=5,
argv=0x7ffcfc84dbf0) at
/usr/src/debug/qt6-qtbase-6.7.0-5.fc41.x86_64/src/corelib/kernel/qobject.cpp:4078
#6  0x7f1ca23f0977 in QMetaObject::activate (sender=,
m=, local_signal_index=local_signal_index@entry=2,
argv=argv@entry=0x7ffcfc84dbf0) at
/usr/src/debug/qt6-qtbase-6.7.0-5.fc41.x86_64/src/corelib/kernel/qobject.cpp:4138
#7  0x7f1ca4fc1c34 in KWin::RenderLoop::frameRequested (this=, _t1=) at
/usr/src/debug/kwin-6.0.4.1-3.fc41.x86_64/redhat-linux-build/src/kwin_autogen/include/moc_renderloop.cpp:208
#8  0x7f1ca4fc83ef in KWin::RenderLoopPrivate::dispatch
(this=0x556c183d37a0) at
/usr/src/debug/kwin-6.0.4.1-3.fc41.x86_64/src/core/renderloop.cpp:128
#9  0x7f1ca23fa3c4 in QtPrivate::QSlotObjectBase::call
(this=0x556c183bdc50, r=, a=0x7ffcfc84dd30) at
/usr/src/debug/qt6-qtbase-6.7.0-5.fc41.x86_64/src/corelib/kernel/qobjectdefs_impl.h:469
#10 doActivate 

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

Matt Fagnani  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #28 from Matt Fagnani  ---
I built qca 2.3.8 with your patch and the one in comment 11 and upgraded to it.
I logged out and in. Using the steps as before, I ran kwalletd6 with the old
config like OPENSSL_CONF=/etc/pki/tls/openssl.cnf.rpmold kwalletd6.
protonvpn-app started normally and kwalletd6 didn't crash. I did likewise with
the empty config, and protonvpn-app and kwalletd6 didn't crash. Thanks. The
patch for https://bugreports.qt.io/browse/QTBUG-118227 looks like it was
included in Qt 6.6.1 there and I'm using 6.6.2.

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #26 from Matt Fagnani  ---
I switched /etc/pki/tls/openssl.cnf back to the old config and rebooted. I
closed the wallet and ran killall kwalletd6 twice. I ran ltrace -fCe
'DH_*+OSSL_*' kwalletd6 I opened the wallet. I ran protonvpn-app which crashed.
kwalletd6 crashed after some of the DH functions as shown in the output.

ltrace -fCe 'DH_*+OSSL_*' kwalletd6
kf.wallet.kwalletd: Lacking a socket, pipe: 0 env: 0
[pid 3618] +++ exited (status 0) +++
[pid 3617] +++ exited (status 0) +++
[pid 3616] +++ exited (status 0) +++
[pid 3615] +++ exited (status 0) +++
[pid 3614] +++ exited (status 0) +++
[pid 3613] +++ exited (status 0) +++
[pid 3654] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3655] --- Called exec() ---
[pid 3655] +++ exited (status 0) +++
[pid 3656] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3657] --- Called exec() ---
[pid 3657] +++ exited (status 0) +++
[pid 3658] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3659] --- Called exec() ---
[pid 3659] +++ exited (status 0) +++
[pid 3660] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3661] --- Called exec() ---
[pid 3661] +++ exited (status 0) +++
[pid 3662] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3663] --- Called exec() ---
[pid 3663] +++ exited (status 0) +++
[pid 3664] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3665] --- Called exec() ---
[pid 3665] +++ exited (status 0) +++
[pid 3677] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3678] --- Called exec() ---
[pid 3678] +++ exited (status 0) +++
[pid 3603] libQt6Core.so.6->OSSL_PROVIDER_load(0, 0x7fb30e297499,
0x55d4cee99010, 1) = 0x7fb2e8001ff0
[pid 3682] +++ exited (status 0) +++
[pid 3603] --- SIGCHLD (Child exited) ---
[pid 3683] --- Called exec() ---
[pid 3683] +++ exited (status 0) +++
[pid 3603] libQt6Core.so.6->OSSL_PROVIDER_unload(0x7fb2e8001ff0,
0x55d4cf2530c0, 0xfffa, 0x7fb30d9f3b20) = 1
[pid 3603] libqca-ossl.so->OSSL_PROVIDER_try_load(0, 0x7fb2f19a10f1, 1,
0x7fb30d9f3ac0 
[pid 3603] legacy.so->OSSL_LIB_CTX_new_child(0x55d4cf2504b0, 0x7fb30c89f300,
24, 0x55d4cf26ac60) = 0x55d4cf25cfb0
[pid 3603] <... OSSL_PROVIDER_try_load resumed> ) =
0x55d4cf2504b0
[pid 3603] libqca-ossl.so->DH_new(0x55d4cf205910, 0x55d4cf2059f0,
0x55d4cf25a630, 0) = 0x7fb2f400bd30
[pid 3603] libqca-ossl.so->DH_set0_pqg(0x7fb2f400bd30, 0x55d4cf24a2b0, 0,
0x55d4cf24a2d0) = 1
[pid 3603] libqca-ossl.so->DH_generate_key(0x7fb2f400bd30, 0x7fb30c8511c0, 16,
0xb10b8f96a080e01d) = 0
[pid 3603] libqca-ossl.so->DH_free(0x7fb2f400bd30, 0x55d4cf205c30,
0x55d19269ff25, 6) = 12
[pid 3603] libqca-ossl.so->DH_new(0x55d4cf205c08, 0, 1, 2)=
0x7fb2f400bd30
[pid 3603] libqca-ossl.so->DH_set0_key(0x7fb2f400bd30, 0x55d4cf206bf0, 0, 1) =
1
[pid 3603] libqca-ossl.so->DH_set0_pqg(0x7fb2f400bd30, 0x55d4cf206160, 0,
0x55d4cf206180) = 1
[pid 3603] --- SIGSEGV (Segmentation fault) ---
[pid 3608] +++ killed by SIGSEGV +++
[pid 3606] +++ killed by SIGSEGV +++
[pid 3611] +++ killed by SIGSEGV +++
[pid 3612] +++ killed by SIGSEGV +++
[pid 3610] +++ killed by SIGSEGV +++
[pid 3609] +++ killed by SIGSEGV +++
[pid 3607] +++ killed by SIGSEGV +++
[pid 3605] +++ killed by SIGSEGV +++
[pid 3604] +++ killed by SIGSEGV +++
[pid 3603] +++ killed by SIGSEGV +++

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

Matt Fagnani  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #25 from Matt Fagnani  ---
Created attachment 167997
  --> https://bugs.kde.org/attachment.cgi?id=167997=edit
ltrace output on kwalletd6 when running Proton VPN GUI twice

I ran ltrace -fCe 'DH_*+OSSL_*' kwalletd6 with the newer default
/etc/pki/tls/openssl.cnf. I ran Proton VPN GUI which didn't appear, but
kwalletd6 didn't crash. I ran Proton VPN GUI again, and it showed up normally.
The ltrace output seemed to show the legacy providers being checked then the DH
functions being run.

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #24 from Matt Fagnani  ---
Created attachment 167996
  --> https://bugs.kde.org/attachment.cgi?id=167996=edit
Older openssl config file which the problem happened with

Thanks. I created an empty file empty.cnf. I closed the wallet in
kwalletmanager. I ran killall kwalletd6 twice in Konsole. I ran
OPENSSL_CONF=empty.cnf kwalletd6 I opened the wallet. I ran Proton VPN GUI
which didn't appear, and kwalletd6 crashed with the same trace as before.

I'm attaching the older openssl config file /etc/pki/tls/openssl.cnf from 2020
which the problem happened with. The older config doesn't mention providers.
Could the lack of the section enabling default providers in the older config
have led to the problem?

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #22 from Matt Fagnani  ---
I think I've found why the problem happened on my system but not yours. The
openssl config file /etc/pki/tls/openssl.cnf was last modified in September
2020 at the time I ran a SCAP Workbench remediation script which modified
/etc/pki/tls/openssl.cnf to add lines about the Fedora crypto policies.
/etc/pki/tls/openssl.cnf wasn't updated since then because rpm doesn't change
config files that don't match those in the update. I moved
/etc/pki/tls/openssl.cnf to /etc/pki/tls/openssl.cnf.rpmold and moved
/etc/pki/tls/openssl.cnf.rpmnew from February 2024 to /etc/pki/tls/openssl.cnf.
I rebooted. kwalletd6 didn't crash when I started Proton VPN GUI or logged in
using it on the next boot using the new openssl config file. The newer openssl
config has a section not in the older one which shows that the legacy providers
are disabled unless certain lines in the following are uncommented. 

# Uncomment the sections that start with ## below to enable the legacy
provider.
# Loading the legacy provider enables support for the following algorithms:
# Hashing Algorithms / Message Digests: MD2, MD4, MDC2, WHIRLPOOL, RIPEMD160
# Symmetric Ciphers: Blowfish, CAST, DES, IDEA, RC2, RC4,RC5, SEED
# Key Derivation Function (KDF): PBKDF1
# In general it is not recommended to use the above mentioned algorithms for
# security critical operations, as they are cryptographically weak or
vulnerable
# to side-channel attacks and as such have been deprecated.

[provider_sect]
default = default_sect
##legacy = legacy_sect
##
[default_sect]
activate = 1

##[legacy_sect]
##activate = 1

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

Matt Fagnani  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #21 from Matt Fagnani  ---
I created an OpenPGP key in KGpg. I exported my Blowfish encrypted wallet, and
then I deleted it in kwalletmanager. I created a new wallet with my OpenPGP key
in kwalletmanager. The Proton VPN GUI and kwalletd6 didn't crash when I started
the Proton VPN GUI, but when I tried to log in to Proton VPN, kwalletd6 crashed
with the same trace and an error popup like "Something went wrong. We're sorry,
a problem occurred" was shown in Proton VPN GUI. I think the problem occurred
when logging in instead of starting because the wallet was empty at that point.
This test and the following were with qca 2.3.8 plus the patch in comment 11.

In another Plasma session, I closed the new wallet encrypted with the OpenPGP
key in kwalletmanager. I ran killall kwalletd6 twice as suggested in comment 9.
I ran OPENSSL_CONF=openssl.cnf kwalletd6 I opened the wallet in kwalletmanager.
I ran Proton VPN GUI and logged in. The login completed without the kwalletd6
crash or the Proton VPN error happening. So this test supports your theory.

I closed the wallet again in kwalletmanager. I ran killall kwalletd6 twice. I
ran ltrace -fCl 'libcrypto*' kwalletd6. Proton VPN crashed when starting, and
kwalletd6 also crashed as shown in the following output.

kf.wallet.kwalletd: Lacking a socket, pipe: 0 env: 0
[pid 67660] +++ exited (status 0) +++
[pid 67659] +++ exited (status 0) +++
[pid 67658] +++ exited (status 0) +++
[pid 67657] +++ exited (status 0) +++
[pid 67656] +++ exited (status 0) +++
[pid 67655] +++ exited (status 0) +++
[pid 67702] +++ exited (status 0) +++
[pid 67703] --- Called exec() ---
[pid 67645] --- SIGCHLD (Child exited) ---
[pid 67703] +++ exited (status 0) +++
[pid 67708] +++ exited (status 0) +++
[pid 67709] --- Called exec() ---
[pid 67645] --- SIGCHLD (Child exited) ---
[pid 67709] +++ exited (status 0) +++
[pid 67710] +++ exited (status 0) +++
[pid 67711] --- Called exec() ---
[pid 67645] --- SIGCHLD (Child exited) ---
[pid 67711] +++ exited (status 0) +++
[pid 67712] +++ exited (status 0) +++
[pid 67713] --- Called exec() ---
[pid 67645] --- SIGCHLD (Child exited) ---
[pid 67713] +++ exited (status 0) +++
[pid 67714] +++ exited (status 0) +++
[pid 67715] --- Called exec() ---
[pid 67645] --- SIGCHLD (Child exited) ---
[pid 67715] +++ exited (status 0) +++
[pid 67716] +++ exited (status 0) +++
[pid 67717] --- Called exec() ---
[pid 67645] --- SIGCHLD (Child exited) ---
[pid 67717] +++ exited (status 0) +++
[pid 67731] +++ exited (status 0) +++
[pid 67732] --- Called exec() ---
[pid 67645] --- SIGCHLD (Child exited) ---
[pid 67732] +++ exited (status 0) +++
[pid 67645] libQt6Core.so.6->OSSL_PROVIDER_load(0, 0x7f8f9fe97499,
0x55d2a3168010, 2) = 0x7f8f78001ff0
[pid 67645] libQt6Core.so.6->EVP_MD_CTX_new(0, 0x7f8f9e313480, 0, 0)  =
0x55d2a347f150
[pid 67645] libQt6Core.so.6->EVP_MD_fetch(0, 0x7f8f9fe993b4, 0x7f8f9fe99415,
0x55d2a347f150) = 0x55d2a3525340
[pid 67645] libQt6Core.so.6->EVP_DigestInit_ex(0x55d2a347f150, 0x55d2a3525340,
0, 0) = 1
[pid 67645] libQt6Core.so.6->EVP_MD_CTX_reset(0x55d2a347f150, 0, 0xffee, 0)
= 1
[pid 67645] libQt6Core.so.6->EVP_DigestInit_ex(0x55d2a347f150, 0x55d2a3525340,
0, 4) = 1
[pid 67645] libQt6Core.so.6->EVP_DigestUpdate(0x55d2a347f150, 0x55d2a34961c0,
9, 0x55d2a34961c0) = 1
[pid 67645] libQt6Core.so.6->EVP_MD_CTX_new(0x55d2a31ea910, 1, 0x55d2a31eaab8,
3) = 0x55d2a3526430
[pid 67645] libQt6Core.so.6->EVP_MD_CTX_copy_ex(0x55d2a3526430, 0x55d2a347f150,
72, 0x55d2a3526430) = 1
[pid 67645] libQt6Core.so.6->EVP_MD_get_size(0x55d2a3525340, -1025,
0x55d2a3168010, 2) = 16
[pid 67645] libQt6Core.so.6->EVP_DigestFinal_ex(0x55d2a3526430, 0x55d2a31eaab8,
0, 2) = 1
[pid 67645] libQt6Core.so.6->EVP_MD_CTX_free(0x55d2a3526430, 0, 0xcbbdf5df,
0x6f4d0cef) = 3
[pid 67645] libQt6Core.so.6->EVP_MD_CTX_reset(0x55d2a347f150, 0, 0xffee, 0)
= 1
[pid 67645] libQt6Core.so.6->EVP_DigestInit_ex(0x55d2a347f150, 0x55d2a3525340,
0, 4) = 1
[pid 67645] libQt6Core.so.6->EVP_DigestUpdate(0x55d2a347f150, 0x55d2a35263f0,
18, 0x55d2a35263f0) = 1
[pid 67645] libQt6Core.so.6->EVP_MD_CTX_new(0x55d2a31ea910, 1, 0x55d2a31eaab8,
2) = 0x55d2a35263e0
[pid 67645] libQt6Core.so.6->EVP_MD_CTX_copy_ex(0x55d2a35263e0, 0x55d2a347f150,
72, 0x55d2a35263e0) = 1
[pid 67645] libQt6Core.so.6->EVP_MD_get_size(0x55d2a3525340, -1025,
0x55d2a3168010, 2) = 16
[pid 67645] libQt6Core.so.6->EVP_DigestFinal_ex(0x55d2a35263e0, 0x55d2a31eaab8,
0, 2) = 1
[pid 67645] libQt6Core.so.6->EVP_MD_CTX_free(0x55d2a35263e0, 0, 0x5d349bcd,
0x77b40417) = 3
[pid 67645] libQt6Core.so.6->EVP_MD_CTX_reset(0x55d2a347f150, 0, 0xf

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #19 from Matt Fagnani  ---
I tried setting the legacy fedora crypto policy which allows DH keys >= 1024
bits with sudo update-crypto-policies --set LEGACY and rebooting but the
problem still happened. I also built kwallet with const auto dlGroup =
QCA::DLGroup(keygen.createDLGroup(QCA::IETF_2048)); at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/src/runtime/kwalletd/kwalletfreedesktopservice.cpp:415,
but the problem happened with that change too.

I created my wallet with "Classic, blowfish encrypted file" in the kwallet
wizard. Blowfish is listed on the OpenSSL legacy providers page at
https://www.openssl.org/docs/man3.0/man7/OSSL_PROVIDER-legacy.html Since the
first bad commit involved OpenSSL legacy providers, could the use of Blowfish
be involved in this problem somehow?

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #17 from Matt Fagnani  ---
In KWalletFreedesktopService::createSessionAlgorithmDhAes at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/src/runtime/kwalletd/kwalletfreedesktopservice.cpp:415
there is const auto dlGroup =
QCA::DLGroup(keygen.createDLGroup(QCA::IETF_1024)); If QCA::IETF_1024 means
that 1024 bit DH keys are used, this might not be allowed by the default crypto
policy in Fedora which I'm using. man crypto-policies shows for the DEFAULT
policy "The Diffie-Hellman parameters are accepted if they are at least 2048
bits long." The private key and public key generated might have had null
pointers because the key size wasn't large enough for the default crypto
policy.

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #16 from Matt Fagnani  ---
Yes, my system is fully updated with the updates-testing repo enabled. I ran
those steps with the qca 2.3.8 build with your patch which gave me the
following output. privateKey.context() appeared to have a non-null pointer.

qmake6 && make && ./test 
Info: creating stash file /programs/qca/test/.qmake.stash
[2]+  Donekate test.pro
g++ -c -pipe -g -Wall -Wextra -D_REENTRANT -DQT_GUI_LIB -DQT_CORE_LIB -I. -I.
-I/usr/include/qt6/QtCrypto -I/usr/include/qt6 -I/usr/include/qt6/QtGui
-I/usr/include/qt6/QtCore -I. -I/usr/lib64/qt6/mkspecs/linux-g++ -o main.o
main.cpp
g++ -Wl,-rpath-link,/usr/lib64 -o test  main.o   -lqca-qt6
/usr/lib64/libQt6Gui.so /usr/lib64/libQt6Core.so -lpthread -lGLX -lOpenGL   
opensslQCAPlugin::MyPKeyContext(0xc34710)

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #14 from Matt Fagnani  ---
I ran the steps like in comment 9 with the qca 2.3.8 build with the patch, but
instead with 
export QT_LOGGING_RULES="*.debug=true" 
kwalletd6 &

The end of the output appeared to show that the first line added by the patch
context() had a null pointer, and then kwalletd6 crashed on the third line with
static_cast(context())->key()
...
qt.core.library: "/usr/lib64/qt6/plugins/crypto/libqca-ossl.so" loaded library
QObject(0x0)
opensslQCAPlugin::MyPKeyContext(0x556d5ce55020)

[1]+  Segmentation fault  (core dumped) kwalletd6

I reported the plasmashell crash I mentioned in my previous comment at
https://bugs.kde.org/show_bug.cgi?id=484565

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 484565] plasmashell crashed in dri2_invalidate_drawable when running the Proton VPN GUI from Konsole

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=484565

--- Comment #1 from Matt Fagnani  ---
Created attachment 167829
  --> https://bugs.kde.org/attachment.cgi?id=167829=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 484565] New: plasmashell crashed in dri2_invalidate_drawable when running the Proton VPN GUI from Konsole

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=484565

Bug ID: 484565
   Summary: plasmashell crashed in dri2_invalidate_drawable when
running the Proton VPN GUI from Konsole
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: 1.0

Application: plasmashell (6.0.2)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.8.1-300.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40 (KDE Plasma Prerelease)"
DrKonqi: 6.0.2 [CoredumpBackend]

-- Information about the crash:
I logged into Plasma 6.0.2 on Wayland in a Fedora 40 KDE Plasma installation. I
was troubleshooting a kwalletd6 crash when starting the Proton VPN GUI which I
reported at https://bugs.kde.org/show_bug.cgi?id=482819 The problem involved
qca 2.3.8. I built qca 2.3.8 with a patch by Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=482819#c11 I upgraded to the qca 2.3.8
build with the patch. I logged out of Plasma and logged in again. I ran the
following steps described by Albert to run kwalletd6 under valgrind then run
the Proton VPN GUI to reproduce the crash
https://bugs.kde.org/show_bug.cgi?id=482819#c9 
"Open a terminal
Start kwalletmanager5 and press the close wallet button (force if needed)
killall kwalletd6 (run it twice to make sure it has not re-spawned itself)
valgrind kwalletd6 

Now in another terminal
kwalletmanager5 and press the open open wallet button
protonvpn-app"

The panel disappeared and reappeared automatically right after I ran
protonvpn-app in Konsole. A plasmashell crash notification was shown.
plasmashell crashed in dri2_invalidate_drawable in the radeonsi driver in mesa
24.0.0. The argument dPriv was null in dri2_invalidate_drawable which might've
led to the crash. The crashing line ../src/gallium/frontends/dri/dri2.c:99 was
drawable->lastStamp++; in the following

static void
dri2_invalidate_drawable(__DRIdrawable *dPriv)
{
   struct dri_drawable *drawable = dri_drawable(dPriv);

   drawable->lastStamp++;

This problem didn't happen before when I ran the Proton VPN GUI.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  dri2_invalidate_drawable (dPriv=0x0) at
../src/gallium/frontends/dri/dri2.c:99
#6  0x7f5e25d54127 in QtWaylandClient::QWaylandEglWindow::updateSurface
(this=0x562892e60320, create=false) at /usr/include/qt6/QtCore/qpoint.h:129
#7  0x7f5e2b63c2a9 in QWindow::resize (this=0x7f5e114230f0, newSize=...) at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/gui/kernel/qwindow.cpp:1995
#8  0x7f5e2de2ee1b in PlasmaQuick::DialogPrivate::syncToMainItemSize() ()
at /lib64/libPlasmaQuick.so.6
#9  0x7f5e2adf2a24 in doActivate (sender=0x7f5e10e7d8c0,
signal_index=25, argv=0x7ffe29b8b1c8) at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qobject.cpp:4051


Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #13 from Matt Fagnani  ---
I built qca 2.3.8 with your patch added. I reproduced the crash first without
using valgrind. The crash happened on the line with static_cast(context())->key() Since context() looked to be run with out a pointer to an
object, I guess the pointer this might've been used which had the null d
pointer.

Core was generated by `/usr/bin/kwalletd6 --pam-login 13 14'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7efd2af813fc in QCA::PrivateKey::deriveKey
(this=this@entry=0x7ffdccf553f0, theirs=...)
at /usr/src/debug/qca-2.3.8-2.fc40.x86_64/src/qca_publickey.cpp:1033
1033qDebug() << static_cast(context())->key();
[Current thread is 1 (Thread 0x7efd2b28f9c0 (LWP 76549))]
(gdb) l
1028SymmetricKey PrivateKey::deriveKey(const PublicKey )
1029{
1030const PKeyContext *theirContext = static_cast(theirs.context());
1031qDebug() << context();
1032qDebug() << theirContext;
1033qDebug() << static_cast(context())->key();
1034qDebug() << theirContext->key();
1035return static_cast(context())->key()->deriveKey(*(theirContext->key()));
1036}
1037
(gdb) bt
#0  0x7efd2af813fc in QCA::PrivateKey::deriveKey
(this=this@entry=0x7ffdccf553f0, theirs=...)
at /usr/src/debug/qca-2.3.8-2.fc40.x86_64/src/qca_publickey.cpp:1033
#1  0x5592e8316992 in
KWalletFreedesktopService::createSessionAlgorithmDhAes (this=0x7efd1000a540,
clientKey=...)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/src/runtime/kwalletd/kwalletfreedesktopservice.cpp:424
#2  KWalletFreedesktopService::OpenSession
(this=0x7efd1000a540, algorithm=, input=,
result=...)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/src/runtime/kwalletd/kwalletfreedesktopservice.cpp:266
#3  0x5592e833bf43 in KWalletFreedesktopServiceAdaptor::OpenSession
(this=0x5592e90d2eb0, algorithm=, input=,
result=)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/redhat-linux-build/src/runtime/kwalletd/kwalletfreedesktopserviceadaptor.cpp:63
#4  KWalletFreedesktopServiceAdaptor::qt_static_metacall
(_o=0x5592e90d2eb0, _c=, _id=,
_a=0x7ffdccf55728)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/redhat-linux-build/src/runtime/kwalletd/moc_kwalletfreedesktopserviceadaptor.cpp:410
#5  0x5592e833c254 in KWalletFreedesktopServiceAdaptor::qt_metacall
(this=0x5592e90d2eb0, _c=QMetaObject::InvokeMetaMethod, _id=6,
_a=0x7ffdccf55728)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/redhat-linux-build/src/runtime/kwalletd/moc_kwalletfreedesktopserviceadaptor.cpp:489
#6  0x7efd2a57bb11 in QDBusConnectionPrivate::deliverCall
(this=this@entry=0x7efd10001690, object=object@entry=0x5592e90d2eb0,
msg=..., metaTypes=..., slotIdx=11)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/dbus/qdbusintegrator.cpp:977
#7  0x7efd2a57f675 in QDBusConnectionPrivate::activateCall
(this=this@entry=0x7efd10001690, object=0x5592e90d2eb0,
flags=flags@entry=273, msg=...)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/dbus/qdbusintegrator.cpp:879
#8  0x7efd2a5802c6 in QDBusConnectionPrivate::activateCall
(this=0x7efd10001690, object=, flags=273, msg=...)
--Type  for more, q to quit, c to continue without paging--c
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/dbus/qdbusintegrator.cpp:825
#9  QDBusConnectionPrivate::activateObject (this=0x7efd10001690, node=...,
msg=..., pathStartPos=)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/dbus/qdbusintegrator.cpp:1460
#10 0x7efd2a58295a in QDBusActivateObjectEvent::placeMetaCall
(this=0x7efd1000afe0)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/dbus/qdbusintegrator.cpp:1580
#11 0x7efd293e25a5 in QObject::event (this=0x7efd1000a540,
e=0x7efd1000afe0)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qobject.cpp:1437
#12 0x7efd2a787f68 in QApplicationPrivate::notify_helper
(this=, receiver=0x7efd1000a540, e=0x7efd1000afe0)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/widgets/kernel/qapplication.cpp:3296
#13 0x7efd2938f218 in QCoreApplication::notifyInternal2
(receiver=0x7efd1000a540, event=0x7efd1000afe0)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1121
#14 0x7efd2938f42d in QCoreApplication::sendEvent (receiver=, event=)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1539
#15 0x7efd29393147 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x5592e8d7e390)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1901
#16 0x7efd2939340d in QCoreApplication::sendPostedEvents
(receiver=, event_type=)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1760
#17 0x7efd29

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #10 from Matt Fagnani  ---
My kwallet is opened automatically when I log in to Plasma with the same
password. You could try installing GNOME 46.0 in your Fedora 40 installation as
I have in case there's something from GNOME that's involved and running
seahorse, evince, and GNOME disks in Plasma as I described. I tried running
kwalletd6 under valgrind a week ago, but I only stopped kwalletd6 once before
running it under valgrind so kwalletd6 kept restarting automatically and I
didn't get it to crash under valgrind then. I followed your instructions. The
valgrind report showed an invalid read and a crash due to a null pointer
dereference in QCA::PrivateKey::deriveKey at the same line as in the gdb trace
I reported originally, which I guess was the null d pointer in the variable
this from privateKey in KWalletFreedesktopService::createSessionAlgorithmDhAes.

==121563== Memcheck, a memory error detector
==121563== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==121563== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==121563== Command: /usr/bin/kwalletd6
==121563== Parent PID: 119206
==121563== 
==121563== Conditional jump or move depends on uninitialised value(s)
==121563==at 0x2BDA8B18: ???
==121563==by 0x2C05E13F: ???
==121563== 
==121563== Conditional jump or move depends on uninitialised value(s)
==121563==at 0x82E63F1:
QtWaylandClient::QWaylandInputDevice::Keyboard::keyboard_key(unsigned int,
unsigned int, unsigned int, unsigned int) (qwaylandinputdevice.cpp:1356)
==121563==by 0xA488055: ffi_call_unix64 (unix64.S:104)
==121563==by 0xA48469F: ffi_call_int.lto_priv.0 (ffi64.c:673)
==121563==by 0xA4874ED: ffi_call (ffi64.c:710)
==121563==by 0x8354F2D: wl_closure_invoke.constprop.0 (connection.c:1025)
==121563==by 0x83557A2: dispatch_event.isra.0 (wayland-client.c:1631)
==121563==by 0x8355A4B: UnknownInlinedFun (wayland-client.c:1777)
==121563==by 0x8355A4B: wl_display_dispatch_queue_pending
(wayland-client.c:2019)
==121563==by 0x82CCCD1: QtWaylandClient::QWaylandDisplay::flushRequests()
(qwaylanddisplay.cpp:229)
==121563==by 0x62E45A4: QObject::event(QEvent*) (qobject.cpp:1437)
==121563==by 0x5001F67: QApplicationPrivate::notify_helper(QObject*,
QEvent*) (qapplication.cpp:3296)
==121563==by 0x6291217: QCoreApplication::notifyInternal2(QObject*,
QEvent*) (qcoreapplication.cpp:1121)
==121563==by 0x6295146: QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (qcoreapplication.cpp:1901)
==121563== 
==121563== Invalid read of size 8
==121563==at 0x4D981DC: QCA::PrivateKey::deriveKey(QCA::PublicKey const&)
(qca_publickey.cpp:1030)
==121563==by 0x141991: UnknownInlinedFun
(kwalletfreedesktopservice.cpp:424)
==121563==by 0x141991: KWalletFreedesktopService::OpenSession(QString
const&, QDBusVariant const&, QDBusObjectPath&)
(kwalletfreedesktopservice.cpp:266)
==121563==by 0x166F42: UnknownInlinedFun
(kwalletfreedesktopserviceadaptor.cpp:63)
==121563==by 0x166F42:
KWalletFreedesktopServiceAdaptor::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (moc_kwalletfreedesktopserviceadaptor.cpp:410)
==121563==by 0x167253:
KWalletFreedesktopServiceAdaptor::qt_metacall(QMetaObject::Call, int, void**)
(moc_kwalletfreedesktopserviceadaptor.cpp:489)
==121563==by 0x5744B10: QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QList const&, int) (qdbusintegrator.cpp:977)
==121563==by 0x5748674: QDBusConnectionPrivate::activateCall(QObject*, int,
QDBusMessage const&) [clone .part.0] (qdbusintegrator.cpp:879)
==121563==by 0x57492C5: activateCall (qdbusintegrator.cpp:825)
==121563==by 0x57492C5:
QDBusConnectionPrivate::activateObject(QDBusConnectionPrivate::ObjectTreeNode&,
QDBusMessage const&, int) (qdbusintegrator.cpp:1460)
==121563==by 0x574B959: QDBusActivateObjectEvent::placeMetaCall(QObject*)
(qdbusintegrator.cpp:1580)
==121563==by 0x62E45A4: QObject::event(QEvent*) (qobject.cpp:1437)
==121563==by 0x5001F67: QApplicationPrivate::notify_helper(QObject*,
QEvent*) (qapplication.cpp:3296)
==121563==by 0x6291217: QCoreApplication::notifyInternal2(QObject*,
QEvent*) (qcoreapplication.cpp:1121)
==121563==by 0x6295146: QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (qcoreapplication.cpp:1901)
==121563==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==121563== 
==121563== 
==121563== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==121563==  Access not within mapped region at address 0x0
==121563==at 0x4D981DC: QCA::PrivateKey::deriveKey(QCA::PublicKey const&)
(qca_publickey.cpp:1030)
==121563==by 0x141991: UnknownInlinedFun
(kwalletfreedesktopservice.cpp:424)
==121563==by 0x141991: KWalletFreedesktopService::OpenSession(QString
cons

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #8 from Matt Fagnani  ---
I bisected this problem with qca from 2.3.7 to 2.3.8. The following first bad
commit involved loading legacy openssl providers.

14eb1ae746c3c75afaef02b487ac65b3de85ad15 is the first bad commit
commit 14eb1ae746c3c75afaef02b487ac65b3de85ad15
Author: Fabian Vogt 
Date:   Fri Dec 22 13:36:00 2023 +0100

plugins/qca-ossl: Actually try loading the legacy provider

OSSL_PROVIDER_available returns true only for loaded providers, not whether
a provider can be loaded. Use OSSL_PROVIDER_try_load instead, which also
allows to keep the default fallback provider.

 plugins/qca-ossl/qca-ossl.cpp | 24 +---
 1 file changed, 5 insertions(+), 19 deletions(-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #7 from Matt Fagnani  ---
In frame 1 in KWalletFreedesktopService::createSessionAlgorithmDhAes,
privateKey and publicKey had null d pointers and clientPublicKey had d = 0x75.
Those keys were generated by qca functions.

(gdb) frame 1
#1  0x55fc1a8bc992 in
KWalletFreedesktopService::createSessionAlgorithmDhAes (this=0x7fcc2400a8a0,
clientKey=...)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/src/runtime/kwalletd/kwalletfreedesktopservice.cpp:424
424 const auto commonSecret = privateKey.deriveKey(clientPublicKey);
(gdb) l
419 }
420
421 auto privateKey = QCA::PrivateKey(keygen.createDH(dlGroup));
422 const auto publicKey = QCA::PublicKey(privateKey);
423 const auto clientPublicKey = QCA::DHPublicKey(dlGroup,
QCA::BigInteger(QCA::SecureArray(clientKey)));
424 const auto commonSecret = privateKey.deriveKey(clientPublicKey);
425 const auto symmetricKey = QCA::HKDF().makeKey(commonSecret, {}, {},
FDO_SECRETS_CIPHER_KEY_SIZE);
426
427 return
std::make_unique(publicKey,
symmetricKey);
428 }
(gdb) p privateKey
$5 = { = { = {_vptr.Algorithm = 0x7fcc3e18e598
, d = {
d = 0x0}}, d = 0x55fc1c7b50e0}, d = 0x70079b90}
(gdb) p publicKey
$6 = { = { = {_vptr.Algorithm = 0x7fcc3e18e5b8
, d = {
d = 0x0}}, d = 0x55fc1c7dca80}, d = 0x70079b90}
(gdb) p clientPublicKey
$7 = { = { = { = {
_vptr.Algorithm = 0x7fcc3e18d880 , d =
{d = 0x55fc1c7dcaa0}}, 
  d = 0x55fc1c819ac0}, d = 0x75}, }
(gdb) p commonSecret
$8 = { = { = {_secure = 96, d = {
d = 0x7fcc3bc3dc88 <_dbus_type_writer_write_basic+152>}}, }, }
(gdb) p symmetricKey
$9 = { = { = {_secure = 38, d = {
d = 0x70079a50}}, }, }

I used evince (Document Viewer) to open an encrypted pdf in Plasma 6.0.2, and
kwalletd6 crashed with the same kind of trace when the password dialog box
appeared. I used GNOME Disks to mount a LUKS encrypted partition in Plasma
6.0.2, and kwalletd6 crashed with the same sort of trace. The problem might be
with GTK programs using the Secret Service interface in Plasma and qca 2.3.8
generating keys with those null or invalid pointers.

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #6 from Matt Fagnani  ---
I used kwalletmanager to export my wallet in encrypted form, then I deleted my
wallet. I created a new wallet when I started Proton VPN GUI and logged in.
kwalletd6 crashed each time when logging in to the Proton VPN server with the
same trace. An error message was shown by the Proton VPN GUI which wasn't shown
before, and the Proton VPN GUI didn't crash. So the problem didn't seem to be
something old about my wallet specifically. 

I ran the GNOME Keyring GUI program seahorse (Passwords and Keys) in Plasma
6.0.2, and kwalletd6 crashed with what looked like the same type of trace. The
problem appeared to be when deriving a private key during a Diffie-Hellman key
exchange.

Core was generated by `/usr/bin/kwalletd6 --pam-login 13 14'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f53b93811dc in QCA::PrivateKey::deriveKey
(this=this@entry=0x7ffecdfbcc90, theirs=...)
at /usr/src/debug/qca-2.3.8-1.fc40.x86_64/src/qca_publickey.cpp:1030
1030return static_cast(context())->key()->deriveKey(*(theirContext->key()));
[Current thread is 1 (Thread 0x7f53b96a79c0 (LWP 1591))]
(gdb) bt
#0  0x7f53b93811dc in QCA::PrivateKey::deriveKey
(this=this@entry=0x7ffecdfbcc90, theirs=...)
at /usr/src/debug/qca-2.3.8-1.fc40.x86_64/src/qca_publickey.cpp:1030
#1  0x55629a2db992 in
KWalletFreedesktopService::createSessionAlgorithmDhAes (this=0x7f53a000a320,
clientKey=...)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/src/runtime/kwalletd/kwalletfreedesktopservice.cpp:424
#2  KWalletFreedesktopService::OpenSession
(this=0x7f53a000a320, algorithm=, input=,
result=...)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/src/runtime/kwalletd/kwalletfreedesktopservice.cpp:266
#3  0x55629a300f43 in KWalletFreedesktopServiceAdaptor::OpenSession
(this=0x55629c5681b0, algorithm=, input=,
result=)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/redhat-linux-build/src/runtime/kwalletd/kwalletfreedesktopserviceadaptor.cpp:63
#4  KWalletFreedesktopServiceAdaptor::qt_static_metacall
(_o=0x55629c5681b0, _c=, _id=,
_a=0x7ffecdfbcfc8)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/redhat-linux-build/src/runtime/kwalletd/moc_kwalletfreedesktopserviceadaptor.cpp:410
#5  0x55629a301254 in KWalletFreedesktopServiceAdaptor::qt_metacall
(this=0x55629c5681b0, _c=QMetaObject::InvokeMetaMethod, _id=6,
_a=0x7ffecdfbcfc8)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/redhat-linux-build/src/runtime/kwalletd/moc_kwalletfreedesktopserviceadaptor.cpp:489
#6  0x7f53b897bb11 in QDBusConnectionPrivate::deliverCall
(this=this@entry=0x7f53a0001690, object=object@entry=0x55629c5681b0,
msg=..., metaTypes=..., slotIdx=11)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/dbus/qdbusintegrator.cpp:977
#7  0x7f53b897f675 in QDBusConnectionPrivate::activateCall
(this=this@entry=0x7f53a0001690, object=0x55629c5681b0,
flags=flags@entry=273, msg=...)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/dbus/qdbusintegrator.cpp:879
#8  0x7f53b89802c6 in QDBusConnectionPrivate::activateCall
(this=0x7f53a0001690, object=, flags=273, msg=...)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/dbus/qdbusintegrator.cpp:825
--Type  for more, q to quit, c to continue without paging--c
#9  QDBusConnectionPrivate::activateObject (this=0x7f53a0001690, node=...,
msg=..., pathStartPos=)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/dbus/qdbusintegrator.cpp:1460
#10 0x7f53b898295a in QDBusActivateObjectEvent::placeMetaCall
(this=0x7f53a00043c0)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/dbus/qdbusintegrator.cpp:1580
#11 0x7f53b77e25a5 in QObject::event (this=0x7f53a000a320,
e=0x7f53a00043c0)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qobject.cpp:1437
#12 0x7f53b8b87f68 in QApplicationPrivate::notify_helper
(this=, receiver=0x7f53a000a320, e=0x7f53a00043c0)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/widgets/kernel/qapplication.cpp:3296
#13 0x7f53b778f218 in QCoreApplication::notifyInternal2
(receiver=0x7f53a000a320, event=0x7f53a00043c0)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1121
#14 0x7f53b778f42d in QCoreApplication::sendEvent (receiver=, event=)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1539
#15 0x7f53b7793147 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55629c210390)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1901
#16 0x7f53b779340d in QCoreApplication::sendPostedEvents
(receiver=, event_type=)
at
/usr/src/debug/qt6-qtbase-6.6.2-6.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1760
#17 0x7f53b7a6751f in postEventSourceDispatch (s=0x55629c212450)
at
/usr/

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #5 from Matt Fagnani  ---
(In reply to Albert Astals Cid from comment #4)
> unfortunately that image you linked seems to have a broken installer
> https://i.imgur.com/yZXIoG4.png

That problem with the installer might be because you appeared to be using
Virtualbox. I've read that Virtualbox support for the new kernel branches used
in Fedora, which is 6.8 in Fedora 40 currently, lag behind by months. I haven't
used Virtualbox though. You could search for the problem you saw at
https://bugzilla.redhat.com/ and report it there if it hasn't been already. 
You could also try to reproduce the problem in the live environment without
installing.

I tried to reproduce the problem with that image in QEMU/KVM VM in GNOME Boxes
and on bare metal, and the problem didn't happen. I installed Fedora Rawhide on
my system in mid 2020 and upgraded to the next version every few months since
then. My kwallet was likely created in 2020, so it's possible that there were
some old keys or other data in it related to this problem. I deleted the Proton
VPN data using kwalletmanager5 a week or so ago, and the problem still happened
after that. The Proton VPN data in my kwallet should be new at least. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

--- Comment #3 from Matt Fagnani  ---
You can download the Fedora 40 KDE Plasma live beta
Fedora-KDE-Live-x86_64-40_Beta-1.10.iso from
https://koji.fedoraproject.org/koji/buildinfo?buildID=2423953 You can boot that
in a QEMU/KVM VM though I haven't tried to reproduce this in a VM or write it
to a USB flash drive with Fedora Media Writer.

I disabled Use KWallet from the Secret Service interface from the KDE Wallet
page in System Settings, and the problem didn't happen with that setting off. I
think because I also have GNOME 46.0 installed the GNOME Keyring was used which
doesn't have this problem.

In QCA::PrivateKey::deriveKey, for the pointer this, one of its three d
pointers was null, and the pointer theirs had d = 0x75 for one of the three
such pointers. If one of those d pointers were dereferenced, the crash might
have resulted.

(gdb) p this
$1 = (QCA::PrivateKey * const) 0x7ffdce589db0
(gdb) p *this
$2 = { = { = {_vptr.Algorithm = 0x7f7a2ffeb598
, d = {
d = 0x0}}, d = 0x55c5ffc37e80}, d = 0x7ffdce589ef0}
(gdb) p theirs
$3 = (const QCA::PublicKey &) @0x7ffdce589df0: { = {
= {
  _vptr.Algorithm = 0x7f7a2ffea880 , d = {d
= 0x55c5ffb593b0}}, 
d = 0x55c5ffc85740}, d = 0x75}

-- 
You are receiving this mail because:
You are watching all bug changes.

[qca] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

Matt Fagnani  changed:

   What|Removed |Added

Product|frameworks-kwallet  |qca
  Component|general |general
 CC||aa...@kde.org,
   ||br...@frogmouth.net,
   ||jus...@karneges.com
   Assignee|va...@kde.org   |unassigned-b...@kde.org
Version|6.0.0   |2.3.8

--- Comment #1 from Matt Fagnani  ---
I downgraded to qca-qt6-2.3.7-3.fc40, and the problem didn't happen after that.
So the problem might be with qca 2.3.8.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 482819] kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

Matt Fagnani  changed:

   What|Removed |Added

   Keywords||qt6

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 482819] New: kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton VPN GUI

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482819

Bug ID: 482819
   Summary: kwalletd6 sometimes crashed in
QCA::PrivateKey::deriveKey when starting Proton VPN
GUI
Classification: Frameworks and Libraries
   Product: frameworks-kwallet
   Version: 6.0.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: va...@kde.org
  Reporter: matt.fagn...@bell.net
CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY

kwalletd6 sometimes crashed in QCA::PrivateKey::deriveKey when starting Proton
VPN GUI. Crashes with the same trace happened three times when starting Proton
VPN each of which was the first time I ran it in a Plasma 6.0.1 session in a
Fedora 40 KDE Plasma installation.

Core was generated by `/usr/bin/kwalletd6 --pam-login 13 14'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f0fa37491dc in QCA::PrivateKey::deriveKey
(this=this@entry=0x7ffe71c73640, theirs=...)
at /usr/src/debug/qca-2.3.8-1.fc40.x86_64/src/qca_publickey.cpp:1030
1030return static_cast(context())->key()->deriveKey(*(theirContext->key()));
[Current thread is 1 (Thread 0x7f0fa37c79c0 (LWP 9448))]

(gdb) bt
#0  0x7f0fa37491dc in QCA::PrivateKey::deriveKey
(this=this@entry=0x7ffe71c73640, theirs=...)
at /usr/src/debug/qca-2.3.8-1.fc40.x86_64/src/qca_publickey.cpp:1030
#1  0x55f537f92992 in
KWalletFreedesktopService::createSessionAlgorithmDhAes (this=0x7f0f8800a320,
clientKey=...)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/src/runtime/kwalletd/kwalletfreedesktopservice.cpp:424
#2  KWalletFreedesktopService::OpenSession
(this=0x7f0f8800a320, algorithm=, input=,
result=...)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/src/runtime/kwalletd/kwalletfreedesktopservice.cpp:266
#3  0x55f537fb7f43 in KWalletFreedesktopServiceAdaptor::OpenSession
(this=0x55f539ee3fe0, algorithm=, input=,
result=)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/redhat-linux-build/src/runtime/kwalletd/kwalletfreedesktopserviceadaptor.cpp:63
#4  KWalletFreedesktopServiceAdaptor::qt_static_metacall
(_o=0x55f539ee3fe0, _c=, _id=,
_a=0x7ffe71c73978)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/redhat-linux-build/src/runtime/kwalletd/moc_kwalletfreedesktopserviceadaptor.cpp:410
#5  0x55f537fb8254 in KWalletFreedesktopServiceAdaptor::qt_metacall
(this=0x55f539ee3fe0, _c=QMetaObject::InvokeMetaMethod, _id=6,
_a=0x7ffe71c73978)
at
/usr/src/debug/kf6-kwallet-6.0.0-1.fc40.x86_64/redhat-linux-build/src/runtime/kwalletd/moc_kwalletfreedesktopserviceadaptor.cpp:489
#6  0x7f0fa2a7bb11 in QDBusConnectionPrivate::deliverCall
(this=this@entry=0x7f0f88001690, object=object@entry=0x55f539ee3fe0,
msg=..., metaTypes=..., slotIdx=11)
at
/usr/src/debug/qt6-qtbase-6.6.2-1.fc40.x86_64/src/dbus/qdbusintegrator.cpp:977
#7  0x7f0fa2a7f675 in QDBusConnectionPrivate::activateCall
(this=this@entry=0x7f0f88001690, object=0x55f539ee3fe0,
flags=flags@entry=273, msg=...)
at
/usr/src/debug/qt6-qtbase-6.6.2-1.fc40.x86_64/src/dbus/qdbusintegrator.cpp:879
#8  0x7f0fa2a802c6 in QDBusConnectionPrivate::activateCall
(this=0x7f0f88001690, object=, flags=273, msg=...)
at
/usr/src/debug/qt6-qtbase-6.6.2-1.fc40.x86_64/src/dbus/qdbusintegrator.cpp:825
--Type  for more, q to quit, c to continue without paging--c
#9  QDBusConnectionPrivate::activateObject (this=0x7f0f88001690, node=...,
msg=..., pathStartPos=)
at
/usr/src/debug/qt6-qtbase-6.6.2-1.fc40.x86_64/src/dbus/qdbusintegrator.cpp:1460
#10 0x7f0fa2a8295a in QDBusActivateObjectEvent::placeMetaCall
(this=0x7f0f8800adc0)
at
/usr/src/debug/qt6-qtbase-6.6.2-1.fc40.x86_64/src/dbus/qdbusintegrator.cpp:1580
#11 0x7f0fa19e25a5 in QObject::event (this=0x7f0f8800a320,
e=0x7f0f8800adc0)
at
/usr/src/debug/qt6-qtbase-6.6.2-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:1437
#12 0x7f0fa2d87f68 in QApplicationPrivate::notify_helper
(this=, receiver=0x7f0f8800a320, e=0x7f0f8800adc0)
at
/usr/src/debug/qt6-qtbase-6.6.2-1.fc40.x86_64/src/widgets/kernel/qapplication.cpp:3296
#13 0x7f0fa198f218 in QCoreApplication::notifyInternal2
(receiver=0x7f0f8800a320, event=0x7f0f8800adc0)
at
/usr/src/debug/qt6-qtbase-6.6.2-1.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1121
#14 0x7f0fa198f42d in QCoreApplication::sendEvent (receiver=, event=)
at
/usr/src/debug/qt6-qtbase-6.6.2-1.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1539
#15 0x7f0fa1993147 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55f539b2d390)
at
/usr/src/debug/qt6-qtbase-6.6.2-1.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1901
#16 0x7f0fa199340d in QCoreApplication::sendPostedEvents
(receiver=, event_type=)
at

[plasmashell] [Bug 482211] Desktop icons sorted by name were occasionally unsorted when starting Plasma

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482211

--- Comment #2 from Matt Fagnani  ---
(In reply to Nate Graham from comment #1)
> Unfortunately the code for desktop icon positioning is quite fragile and
> buggy. There are plans to rewrite to fix this and other similar bugs. Maybe
> for Plasma 6.1 or 6.2.

OK thanks. I should note that I set the splash screen to None because the
splash screen was being shown for about 20 s even though the desktop took
around 5 s to load completely as I reported at
https://bugs.kde.org/show_bug.cgi?id=479824 I don't know if that might be
involved. When the problem happened 2-3 times after I reported this, the first
few icons were still ordered by name and the ones after that were randomly
ordered. This problem might've happened less than 10% of the times I started
Plasma.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 482211] Desktop icons sorted by name were occasionally unsorted when starting Plasma

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482211

Matt Fagnani  changed:

   What|Removed |Added

   Keywords||qt6

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 482211] New: Desktop icons sorted by name were occasionally unsorted when starting Plasma

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=482211

Bug ID: 482211
   Summary: Desktop icons sorted by name were occasionally
unsorted when starting Plasma
Classification: Plasma
   Product: plasmashell
   Version: 5.93.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Folder
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
CC: h...@kde.org
  Target Milestone: 1.0

SUMMARY

I have 18 desktop icons sorted by name arranged into 3 columns in Plasma 6.0.0
on Wayland in a Fedora 40 KDE Plasma installation. The desktop context menu for
Icons shows Sort By - Name, Arrange - Top to bottom, Align - Left, Show
previews is enabled, Locked isn't enabled. Desktop icons sorted by name were
occasionally unsorted when starting Plasma. The desktop icons were seemingly
randomly ordered and Sort By was Unsorted when this problem happened.
This problem happened about 10-20% of the time I started Plasma. I've seen this
problem a few times in the last week or so.

STEPS TO REPRODUCE
1. Boot a Fedora 40 KDE Plasma installation with a user with 18 desktop icons
sorted by name arranged into 3 columns and desktop context menu for Icons set
to Sort By - Name, Arrange - Top to bottom, Align - Left, Show previews is
enabled, Locked isn't enabled. 
2. Log in to Plasma 6.0.0 on Wayland from sddm
3. If the problem didn't happen, log out.
4. Repeat 2-3 until the problem happens.

OBSERVED RESULT
Desktop icons sorted by name were occasionally unsorted when starting Plasma

EXPECTED RESULT
Desktop icons sorted by name would always be sorted when starting Plasma

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 40
(available in About System)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

The version field when entering this report didn't show 6.0.0 as an option so I
selected 5.93.0.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 410211] plasmashell segmentation fault in ScreenPool::ScreenPool() when Plasma on X autologin froze on the splash screen in Fedora Rawhide

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=410211

Matt Fagnani  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #5 from Matt Fagnani  ---
(In reply to Nate Graham from comment #4)
> Fedora is no longer set up this way; Can we ask you to please check if this
> is still an issue with Plasma 6.0? Thanks a lot!

I'm using Fedora 40 now which dropped official support for Plasma on X. I
haven't seen this problem in years.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480474] Plasmashell crashes when dragging files to "combined" windows on icons only task manager

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=480474

Matt Fagnani  changed:

   What|Removed |Added

 CC||matt.fagn...@bell.net

--- Comment #4 from Matt Fagnani  ---
plasmashell crashed five times in a row when dragging text in Thunderbird in
Plasma 5.93.0 on Wayland in a Fedora Rawhide/40 KDE Plasma installation.
Thunderbird had 4-5 emails open in separate windows some of which were replying
to others. The Thunderbird windows appeared to be combined into one task in the
task manager when hovering over it. Text was dragged from one of the emails
which was shown in red moving around with the cursor. plasmashell crashed with
the same traces repeatedly in std::__atomic_base::load. The
traces looked like those in this report. Errors like this= in frames 5-8 might've indicated
a null pointer (plus an offset). QCoreApplication::notifyInternal2 in frame 9
had receiver=0x0. QGuiApplicationPrivate::processDrag in frame 11 had
w=w@entry=0x0, and QWindowSystemInterface::handleDrag in frame 12 had
window=window@entry=0x0.
QtWaylandClient::QWaylandDataDevice::data_device_motion in frame 13 had drag =
0x0 according to the full trace which might be where the null pointer was from.

Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0)
at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7f1ba6e2cb00 (LWP 23013))]

(gdb) bt
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0)
at pthread_kill.c:44
#1  0x7f1ba3ea71f3 in __pthread_kill_internal (signo=11,
threadid=) at pthread_kill.c:78
#2  0x7f1ba3e4f65e in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3  0x7f1ba71ce645 in KCrash::defaultCrashHandler(int) () at
/lib64/libKF6Crash.so.6
#4  0x7f1ba3e4f710 in  () at /lib64/libc.so.6
#5  std::__atomic_base::load
(__m=std::memory_order_acquire, this=)
at /usr/include/c++/14/bits/atomic_base.h:831
#6  std::atomic::load
(__m=std::memory_order_acquire, this=)
at /usr/include/c++/14/atomic:582
#7  QAtomicOps::loadAcquire
(_q_value=)
at
/usr/src/debug/qt6-qtbase-6.6.1-5.fc40.x86_64/src/corelib/thread/qatomic_cxx11.h:213
#8  QBasicAtomicPointer::loadAcquire (this=)
at
/usr/src/debug/qt6-qtbase-6.6.1-5.fc40.x86_64/src/corelib/thread/qbasicatomic.h:179
#9  QCoreApplication::notifyInternal2 (receiver=0x0, event=0x7ffdb5954530)
at
/usr/src/debug/qt6-qtbase-6.6.1-5.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1117
#10 0x7f1ba458f6cd in QCoreApplication::sendEvent (receiver=, event=)
at
/usr/src/debug/qt6-qtbase-6.6.1-5.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1539
#11 0x7f1ba4de47ca in QGuiApplicationPrivate::processDrag
(w=w@entry=0x0, dropData=dropData@entry=0x55df034eb560, p=...,
supportedActions=..., buttons=..., modifiers=...)
at
/usr/src/debug/qt6-qtbase-6.6.1-5.fc40.x86_64/src/gui/kernel/qguiapplication.cpp:3376
#12 0x7f1ba4e435ed in QWindowSystemInterface::handleDrag
(window=window@entry=0x0, dropData=0x55df034eb560, p=,
supportedActions=supportedActions@entry=..., buttons=..., modifiers=...) at
/usr/src/debug/qt6-qtbase-6.6.1-5.fc40.x86_64/src/gui/kernel/qwindowsysteminterface.cpp:845
#13 0x7f1ba6ee5d45 in
QtWaylandClient::QWaylandDataDevice::data_device_motion
--Type  for more, q to quit, c to continue without paging--c
(this=0x55df007ad9d0, time=, x=, y=)
at
/usr/src/debug/qt6-qtwayland-6.6.1-5.fc40.x86_64/src/client/qwaylanddatadevice.cpp:273
#14 0x7f1ba3d08056 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#15 0x7f1ba3d046a0 in ffi_call_int
(cif=cif@entry=0x7ffdb59548c0, fn=, rvalue=,
avalue=, closure=closure@entry=0x0) at ../src/x86/ffi64.c:673
#16 0x7f1ba3d074ee in ffi_call
(cif=cif@entry=0x7ffdb59548c0, fn=, rvalue=rvalue@entry=0x0,
avalue=avalue@entry=0x7ffdb5954990)
at ../src/x86/ffi64.c:710
#17 0x7f1ba726bf2e in wl_closure_invoke
(closure=closure@entry=0x7f1b7c0099d0, target=, 
target@entry=0x55df007b1ab0, opcode=opcode@entry=3, data=,
flags=1) at ../src/connection.c:1025
#18 0x7f1ba726c7a3 in dispatch_event (display=display@entry=0x55df0079fbf0,
queue=0x55df0079fce0)
at ../src/wayland-client.c:1631
#19 0x7f1ba726ca4c in dispatch_queue (queue=0x55df0079fce0,
display=0x55df0079fbf0) at ../src/wayland-client.c:1777
#20 wl_display_dispatch_queue_pending (display=0x55df0079fbf0,
queue=0x55df0079fce0) at ../src/wayland-client.c:2019
#21 0x7f1ba6e9ead2 in QtWaylandClient::QWaylandDisplay::flushRequests
(this=)
at
/usr/src/debug/qt6-qtwayland-6.6.1-5.fc40.x86_64/src/client/qwaylanddisplay.cpp:229
#22 0x7f1ba45f3094 in doActivate

[plasmashell] [Bug 481044] Window previews for Firefox when playing videos with sound or streaming audio were sometimes shifted down and to the right

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=481044

--- Comment #4 from Matt Fagnani  ---
I'm seeing this problem with Konsole and Kate 24.01.95 in Plasma 5.93.0.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 481044] Window previews for Firefox when playing videos with sound or streaming audio were sometimes shifted down and to the right

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=481044

--- Comment #3 from Matt Fagnani  ---
Thanks. This problem usually happened when I stopped moving the cursor over the
Firefox task in the task manager before the window preview popups appeared.
When I kept moving the cursor after the window preview popups appeared, the
problem normally didn't happen or corrected itself. The initial alignment
positions for Firefox previews might be off. I've only seen this problem with
Firefox when video or audio are playing or paused with sound on, so the media
player controls might be involved in the incorrect positioning somehow. The
media player controls like play or pause were either partly cut off at the
bottom of the popups or not shown at all when the problem happened. I haven't
seen this problem when playing video or audio with Falkon or VLC briefly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dragonplayer] [Bug 481046] New: Dragon crashed when playing a video

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=481046

Bug ID: 481046
   Summary: Dragon crashed when playing a video
Classification: Applications
   Product: dragonplayer
   Version: 24.01.95
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: matt.fagn...@bell.net
CC: myr...@kde.org, sit...@kde.org
  Target Milestone: ---

Application: dragon (24.01.95)

Qt Version: 6.6.1
Frameworks Version: 5.249.0
Operating System: Linux 6.8.0-0.rc3.26.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 40 (KDE Plasma Prerelease)
DrKonqi: 5.93.0 [CoredumpBackend]

-- Information about the crash:
I'm using Plasma 5.93.0 on Wayland in a Fedora Rawhide/40 KDE Plasma
installation. I started Dragon. I played a .mp4 h264 video. Dragon didn't show
the video. Dragon crashed after 2-4 seconds. The trace of the crashing thread
appeared to be mostly in gstreamer. I have gstreamer1-1.22.9-1.fc40 installed.
I have ffmpeg-6.1.1-5.fc40 from RPM Fusion installed which has h264 support. I
reproduced the crash once with a different .mp4 video with what looked like the
same trace.

The crash can be reproduced every time.

-- Backtrace:
Application: Dragon Player (dragon), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 92892]
[New LWP 92729]
[New LWP 92733]
[New LWP 92749]
[New LWP 92902]
[New LWP 92752]
[New LWP 92730]
[New LWP 92732]
[New LWP 92900]
[New LWP 92731]
[New LWP 92734]
[New LWP 92751]
[New LWP 92760]
[New LWP 92735]
[New LWP 92736]
[New LWP 92727]
[New LWP 92761]
[New LWP 92728]
[New LWP 92750]
[New LWP 92753]
[New LWP 92894]
[New LWP 92754]
[New LWP 92758]
[New LWP 92759]
[New LWP 92791]
[New LWP 92891]
[New LWP 92893]
[New LWP 92898]
[New LWP 92899]
[New LWP 92901]
[New LWP 92903]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/dragon'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7fb14e6006c0 (LWP 92892))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fb14e6006c0 (LWP 92892))]

Thread 31 (Thread 0x7fb1268006c0 (LWP 92903)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7fb1a93ca540 in g_cond_wait_until (cond=,
mutex=0x557e5a2a1610, end_time=) at ../glib/gthread-posix.c:1677
#2  0x7fb1a93374f3 in g_async_queue_pop_intern_unlocked
(queue=0x557e5a2a1610, wait=1, end_time=40183493337) at
../glib/gasyncqueue.c:378
#3  0x7fb1a939e1ca in g_thread_pool_wait_for_new_task (pool=0x7fb1106b7cb0)
at ../glib/gthreadpool.c:260
#4  g_thread_pool_thread_proxy (data=) at
../glib/gthreadpool.c:325
#5  0x7fb1a939c453 in g_thread_proxy (data=0x7fb114000fa0) at
../glib/gthread.c:835
#6  0x7fb1a98a61f7 in start_thread (arg=) at
pthread_create.c:447
#7  0x7fb1a99283ac in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 30 (Thread 0x7fb1274006c0 (LWP 92901)):
#0  futex_wait (private=0, expected=2, futex_word=0x7fb11016ea60) at
../sysdeps/nptl/futex-internal.h:146
#1  __GI___lll_lock_wait (futex=futex@entry=0x7fb11016ea60, private=0) at
lowlevellock.c:49
#2  0x7fb1a98a9838 in lll_mutex_lock_optimized (mutex=0x7fb11016ea60) at
pthread_mutex_lock.c:48
#3  ___pthread_mutex_lock (mutex=0x7fb11016ea60) at pthread_mutex_lock.c:128
#4  0x7fb1a93bff1d in g_rec_mutex_lock (mutex=mutex@entry=0x7fb11016e488)
at ../glib/gthread-posix.c:397
#5  0x7fb174d76d32 in gst_video_decoder_get_frame
(decoder=decoder@entry=0x7fb11016e370, frame_number=11) at
../gst-libs/gst/video/gstvideodecoder.c:4186
#6  0x7fb164046945 in gst_ffmpegviddec_get_buffer2 (context=0x7fb1104c6200,
picture=0x7fb11058a2c0, flags=1) at ../ext/libav/gstavviddec.c:936
#7  0x7fb14c3ccd03 in ff_get_buffer () at /lib64/libavcodec.so.60
#8  0x7fb14c6b8aea in ff_thread_get_buffer () at /lib64/libavcodec.so.60
#9  0x7fb14c6b901e in ff_thread_get_ext_buffer () at
/lib64/libavcodec.so.60
#10 0x7fb14c4ae101 in h264_frame_start () at /lib64/libavcodec.so.60
#11 0x7fb14c4b5c5e in ff_h264_queue_decode_slice () at
/lib64/libavcodec.so.60
#12 0x7fb14c4c4cd4 in h264_decode_frame.lto_priv () at
/lib64/libavcodec.so.60
#13 0x7fb14c6b9402 in frame_worker_thread.lto_priv () at
/lib64/libavcodec.so.60
#14 

[plasmashell] [Bug 481044] New: Window previews for Firefox when playing videos with sound or streaming audio were sometimes shifted down and to the right

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=481044

Bug ID: 481044
   Summary: Window previews for Firefox when playing videos with
sound or streaming audio were sometimes shifted down
and to the right
Classification: Plasma
   Product: plasmashell
   Version: 5.93.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
CC: qydwhotm...@gmail.com
  Target Milestone: 1.0

SUMMARY

I'm using Plasma 5.93.0 on Wayland in a Fedora Rawhide/40 KDE Plasma
installation. When I've played videos with audio on or streaming audio in
Firefox 124.0a1 and 122.0 on Wayland and hovered over the task manager box for
Firefox, the window text and preview were sometimes shifted down and to the
right. The text of the site title or video file were sometimes cut off at the
right of the popups. The window previews were sometimes cut off by the bottom
and right of the popups. The volume control wasn't shown because it was below
the bottom of the popup when that happened. The window preview popups sometimes
were shown correctly after that when I hovered over the popup or moved the
cursor. This problem seems to have started recently possibly with 5.93.0.

STEPS TO REPRODUCE
1. Boot a Fedora Rawhide/40 KDE Plasma installation updated to 2024-2-8
2. Log in to Plasma 5.93.0 on Wayland. I have the task manager set to Task
manager without icons.
3. Start Firefox
4. Play an mp4 video with sound on or streaming audio in Firefox
5. Hover the cursor on and off of the task manager box for Firefox until the
problem happens

OBSERVED RESULT
Window previews for Firefox when playing videos with sound or streaming audio
were sometimes shifted down and to the right

EXPECTED RESULT
Window previews for Firefox when playing videos with sound or streaming audio
should be shown normally every time

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Rawhide/40
(available in About System)
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.1

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kconfig] [Bug 480758] The desktop icons took about 20 seconds to appear when starting Plasma 5.93.0

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=480758

--- Comment #5 from Matt Fagnani  ---
Created attachment 165606
  --> https://bugs.kde.org/attachment.cgi?id=165606=edit
strace /usr/libexec/kf6/kconf_update output

To make the problem start happening again, I logged out of Plasma, switched to
another VT and reinstalled kwin with sudo dnf reinstall kwin*. When I logged in
to Plasma after that, the problem happened. I ran Konsole before the desktop
icons appeared and ps aux | grep python showed a process /usr/bin/python3
/usr/share/kconf_update/kwin-6.0-overview-activities-shortcuts.py I ran strace
/usr/libexec/kf6/kconf_update in Konsole. The strace output showed that
kconf_update was waiting on
/usr/share/kconf_update/kwin-6.0-overview-activities-shortcuts.py for about 30
s after which it timed out and was killed with the error QProcess: Destroyed
while process ("/usr/bin/python3") is still running.

openat(AT_FDCWD, "/usr/share/kconf_update/kwin.upd", O_RDONLY|O_CLOEXEC) = 4
statx(4, "", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT|AT_EMPTY_PATH, STATX_ALL,
{stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0644,
stx_size=571, ...}) = 0
statx(4, "", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT|AT_EMPTY_PATH, STATX_ALL,
{stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0644,
stx_size=571, ...}) = 0
statx(4, "", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT|AT_EMPTY_PATH, STATX_ALL,
{stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0644,
stx_size=571, ...}) = 0
read(4, "# SPDX-FileCopyrightText: 2023 N"..., 16384) = 571
read(4, "", 15813)  = 0
statx(AT_FDCWD,
"/home/matt/.local/share/kconf_update/kwin-6.0-overview-activities-shortcuts.py",
AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_ALL, 0x7ffe30dcd130) = -1 ENOENT
(No such file or directory)
statx(AT_FDCWD,
"/home/matt/.local/share/flatpak/exports/share/kconf_update/kwin-6.0-overview-activities-shortcuts.py",
AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_ALL, 0x7ffe30dcd130) = -1 ENOENT
(No such file or directory)
statx(AT_FDCWD,
"/var/lib/flatpak/exports/share/kconf_update/kwin-6.0-overview-activities-shortcuts.py",
AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_ALL, 0x7ffe30dcd130) = -1 ENOENT
(No such file or directory)
statx(AT_FDCWD,
"/usr/local/share/kconf_update/kwin-6.0-overview-activities-shortcuts.py",
AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_ALL, 0x7ffe30dcd130) = -1 ENOENT
(No such file or directory)
statx(AT_FDCWD,
"/usr/share/kconf_update/kwin-6.0-overview-activities-shortcuts.py",
AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_ALL,
{stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0755,
stx_size=869, ...}) = 0
getcwd("/home/matt", 4096)  = 11
statx(AT_FDCWD, "/home/matt/.local/bin/python3",
AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_ALL, 0x7ffe30dcd070) = -1 ENOENT
(No such file or directory)
statx(AT_FDCWD, "/home/matt/bin/python3",
AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_ALL, 0x7ffe30dcd070) = -1 ENOENT
(No such file or directory)
statx(AT_FDCWD, "/usr/lib64/ccache/python3",
AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_ALL, 0x7ffe30dcd070) = -1 ENOENT
(No such file or directory)
statx(AT_FDCWD, "/usr/local/bin/python3",
AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_ALL, 0x7ffe30dcd070) = -1 ENOENT
(No such file or directory)
statx(AT_FDCWD, "/usr/bin/python3", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT,
STATX_ALL, {stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0,
stx_mode=S_IFREG|0755, stx_size=15976, ...}) = 0
access("/usr/bin/python3", X_OK)= 0
pipe2([5, 6], O_CLOEXEC)= 0
pipe2([7, 8], O_CLOEXEC)= 0
pipe2([9, 10], O_CLOEXEC)   = 0
pipe2([11, 12], O_CLOEXEC)  = 0
write(3, "\1\0\0\0\0\0\0\0", 8) = 8
waitid(P_PIDFD, 2147483647, NULL, WNOHANG|WEXITED, NULL) = -1 EBADF (Bad file
descriptor)
clone(child_stack=0x7ffe30dcd130,
flags=CLONE_VM|CLONE_PIDFD|CLONE_VFORK|SIGCHLD, parent_tid=[13]) = 69375
close(12)   = 0
close(5)= 0
fcntl(6, F_GETFL)   = 0x1 (flags O_WRONLY)
fcntl(6, F_SETFL, O_WRONLY|O_NONBLOCK)  = 0
close(8)= 0
fcntl(7, F_GETFL)   = 0 (flags O_RDONLY)
fcntl(7, F_SETFL, O_RDONLY|O_NONBLOCK)  = 0
close(10)   = 0
fcntl(9, F_GETFL)   = 0 (flags O_RDONLY)
fcntl(9, F_SETFL, O_RDONLY|O_NONBLOCK)  = 0
ppoll([{fd=11, events=POLLIN}], 1, {tv_sec=60, tv_nsec=0}, NULL, 8) = 1
([{fd=11, revents=POLLHUP}], left {tv_sec=59, tv_nsec=98295})
read(11, "", 16)= 0
write(3, "\1\0\0\0\0\0\0\0", 8) = 8
close(11)   = 0
write(3, "\1\0\

[frameworks-kconfig] [Bug 480758] The desktop icons took about 20 seconds to appear when starting Plasma 5.93.0

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=480758

--- Comment #4 from Matt Fagnani  ---
To clarify, the lines like kded6[1771]: QProcess: Destroyed while process
("/usr/libexec/kf6/kconf_update") is still running. didn't appear in the
journal after I ran /usr/libexec/kf6/kconf_update in Konsole for that user, but
other messages from kconf_update and kded6 appeared about 3-5 s after starting
Plasma when the problem didn't happen.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kconfig] [Bug 480758] The desktop icons took about 20 seconds to appear when starting Plasma 5.93.0

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=480758

Matt Fagnani  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #3 from Matt Fagnani  ---
(In reply to Nate Graham from comment #2)
> Does the exact same issue reproduce on the next boot?

Yes, this problem happened the same way on the next boot until I ran
/usr/libexec/kf6/kconf_update in Konsole. Then the desktop icons appeared after
2-5 s of starting Plasma. I had to run /usr/libexec/kf6/kconf_update in Konsole
separately for each of two users on the system to work around the problem. The
problem started again today right after a dnf offline upgrade which included
kwin-5.93.0-2.fc40 and plasma-integration-5.93.0-3.fc40. I ran
/usr/libexec/kf6/kconf_update in Konsole again for both users and the problem
stopped. /usr/libexec/kf6/kconf_update took about 30-40 s to run in Konsole the
first time I ran it, and its output had a line like QProcess: Destroyed while
process ("/usr/bin/python3") is still running when that happened. The python
program being run might've delayed /usr/libexec/kf6/kconf_update which delayed
kded6 which slowed the desktop icons from appearing.
/usr/libexec/kf6/kconf_update took about 1 s to run in Konsole the second and
third time I ran it in Konsole after today's update as my user, and it didn't
have the python containing line I mentioned. The output of kconf_update kded6
in the journal was about 20 s after starting Plasma when the problem happened
and about 3-5 s after when it didn't. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kconfig] [Bug 480758] The desktop icons took about 20 seconds to appear when starting Plasma 5.93.0

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=480758

Matt Fagnani  changed:

   What|Removed |Added

  Component|generic-performance |general
   Target Milestone|1.0 |---
Product|plasmashell |frameworks-kconfig
 CC||kdelibs-b...@kde.org
Version|5.93.0  |5.249.0
   Assignee|plasma-b...@kde.org |matt...@mjdsystems.ca

--- Comment #1 from Matt Fagnani  ---
The journal had messages which started with Plasma 5.93.0 around 20 s after I
started it like 
kded6[1771]: QProcess: Destroyed while process
("/usr/libexec/kf6/kconf_update") is still running.

I ran /usr/libexec/kf6/kconf_update in Konsole, and it finished after about 30
s. When I logged out and in to Plasma after that, the desktop icons appeared
after about 2 s. /usr/libexec/kf6/kconf_update still being running 20 s into
startup might've delayed the desktop icons from being shown.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480758] New: The desktop icons took about 20 seconds to appear when starting Plasma 5.93.0

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=480758

Bug ID: 480758
   Summary: The desktop icons took about 20 seconds to appear when
starting Plasma 5.93.0
Classification: Plasma
   Product: plasmashell
   Version: 5.93.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: generic-performance
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: 1.0

SUMMARY

I updated a Fedora Rawhide/40 KDE Plasma installation from Plasma 5.92.0 to
5.93.0. I had previously set the splash screen to none in System Settings to
work around the splash screen being shown for about 20 seconds with 5.92.0 even
though the startup took about 5 s to complete
https://bugs.kde.org/show_bug.cgi?id=479824 The desktop icons took about 20
seconds to appear when starting Plasma 5.93.0 on Wayland as opposed to about 5
s with 5.92.0 and earlier. The panel and background appeared after about 5 s
with 5.93.0. This problem happened each of several times I started 5.93.0. I
didn't see any obviously related journal messages that were new.

STEPS TO REPRODUCE
1. Boot a Fedora Rawhide KDE Plasma installation updated to 2024-2-2 with
Plasma 5.93.0 downloaded from
https://bodhi.fedoraproject.org/updates/FEDORA-2024-b19679b66a installed. The
splash screen was previously set to None in System Settings.
2. Log in to Plasma 5.93.0 on Wayland
3. 

OBSERVED RESULT
The desktop icons took about 20 seconds to appear when starting Plasma 5.93.0

EXPECTED RESULT
The desktop icons should have taken about 5 seconds to appear when starting
Plasma 5.93.0

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Rawhide/40
(available in About System)
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.1

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 479824] New: The splash screen was shown for about 20 s when starting Plasma 5.92.0 while Plasma completed startup after 3-5 s with splash screen set to None

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=479824

Bug ID: 479824
   Summary: The splash screen was shown for about 20 s when
starting Plasma 5.92.0 while Plasma completed startup
after 3-5 s with splash screen set to None
Classification: Plasma
   Product: plasmashell
   Version: 5.92.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: generic-performance
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: 1.0

Created attachment 164907
  --> https://bugs.kde.org/attachment.cgi?id=164907=edit
Journal for Plasma 5.92.0 session startup where the splash screen was shown for
20 s

SUMMARY

The splash screen was shown for about 20 s each time I've logged in to Plasma
5.92.0 on Wayland in a Fedora Rawhide/40 KDE Plasma installation. When I moved
the mouse to the top left of the screen while the splash screen was shown after
3-5 s, the desktop was shown to have completed startup in one of the overview
windows. There were amdgpu errors in the journal like
"kwin_wayland_wrapper[1641]: amdgpu: amdgpu_cs_ctx_create2 failed. (-13)" when
kwin_wayland was starting as the Plasma and sddm compositors which continued as
the splash screen was shown and after the desktop appeared.

Jan 14 17:00:22 kwin_wayland[1641]: No backend specified, automatically
choosing drm
Jan 14 17:00:22 wireplumber[1669]:
 Failed to call Lookup:
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Jan 14 17:00:22 kwin_wayland_wrapper[1641]: amdgpu: amdgpu_cs_ctx_create2
failed. (-13)
Jan 14 17:00:22 kwin_wayland_wrapper[1641]: amdgpu: amdgpu_cs_ctx_create2
failed. (-13)
Jan 14 17:00:22 kwin_wayland[1641]: OpenGL vendor string:   AMD
Jan 14 17:00:22 kwin_wayland[1641]: OpenGL renderer string: AMD
Radeon R5 Graphics (radeonsi, carrizo, LLVM 17.0.6, DRM 3.56,
6.7.0-68.fc40.x86_64)
Jan 14 17:00:22 kwin_wayland[1641]: OpenGL version string:  4.6
(Core Profile) Mesa 23.3.3
Jan 14 17:00:22 kwin_wayland[1641]: OpenGL shading language version string:
4.60
Jan 14 17:00:22 kwin_wayland[1641]: Driver:
Unknown
Jan 14 17:00:22 kwin_wayland[1641]: GPU class: 
Unknown
Jan 14 17:00:22 kwin_wayland[1641]: OpenGL version: 4.6
Jan 14 17:00:22 kwin_wayland[1641]: GLSL version:  
4.60
Jan 14 17:00:22 kwin_wayland[1641]: Mesa version:  
23.3.3
Jan 14 17:00:22 kwin_wayland[1641]: Requires strict binding:no
Jan 14 17:00:22 kwin_wayland[1641]: Virtual Machine:no
Jan 14 17:00:22 kwin_wayland[1641]: Timer query support:yes

There were journal errors showing plasmashell aborting shell load because
kactivitymanagerd wasn't running yet.

Jan 14 17:00:25 plasmashell[1857]: kde.plasmashell: Aborting shell load: The
activity manager daemon (kactivitymanagerd) is not running.
Jan 14 17:00:25 plasmashell[1857]: kde.plasmashell: If this Plasma has been
installed into a custom prefix, verify that its D-Bus services dir is known to
the system for the daemon to be activatable.
Jan 14 17:00:25 kactivitymanagerd[1918]: kf.windowsystem: virtual void
KX11Extras::connectNotify(const QMetaMethod&) may only be used on X11
Jan 14 17:00:25 kactivitymanagerd[1918]: kf.windowsystem: virtual void
KX11Extras::connectNotify(const QMetaMethod&) may only be used on X11
Jan 14 17:00:25 systemd[1521]: Started plasma-kactivitymanagerd.service -
KActivityManager Activity manager Service.
Jan 14 17:00:25 plasmashell[1857]: kde.plasmashell: Aborting shell load: The
activity manager daemon (kactivitymanagerd) is not running.
Jan 14 17:00:25 plasmashell[1857]: kde.plasmashell: If this Plasma has been
installed into a custom prefix, verify that its D-Bus services dir is known to
the system for the daemon to be activatable.

plasma-ksplash.service ran for 32 s.

systemctl status --user plasma-ksplash.service
○ plasma-ksplash.service - Splash screen shown during boot
 Loaded: loaded (/usr/lib/systemd/user/plasma-ksplash.service; static)
Drop-In: /usr/lib/systemd/user/service.d
 └─10-timeout-abort.conf
 Active: inactive (dead)

Jan 14 17:00:21 localhost.localdomain systemd[1521]: Starting
plasma-ksplash.service - Splash screen shown during boot...
Jan 14 17:00:53 localhost.localdomain systemd[1521]: Finished
plasma-ksplash.service - Splash screen shown during boot.
Jan 14 17:00:53 localhost.localdomain systemd[1521]: plasma-ksplash.service:
Consumed 3.215s CPU time.

I'll attach the journal for this Plasma session startup.

I set the splash screen to None in System Settings, logged out and logged in.
Plasma completed startup after 3-5 s without a splash screen. The splash screen
was 

[plasmashell] [Bug 471248] plasmashell on Wayland crashed occasionally when playing Instagram story videos in Firefox

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=471248

--- Comment #8 from Matt Fagnani  ---
I set TimeoutSec=1000sec in /usr/lib/systemd/user/plasma-plasmashell.service to
work around the problem I reported at
https://bugs.kde.org/show_bug.cgi?id=478287 Using Plasma 5.27.10 on Wayland
with KF 5.113.0 and Qt 5.15.12, I attached gdb to plasmashell with gdb -p
$(pidof plasmashell) I played Instagram story videos in Firefox 123.0a1 on
Wayland. plasmashell crashed. I ran bt in gdb which then crashed.

Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault.
0x7fe9f08b3a72 in __dynamic_cast () from /lib64/libstdc++.so.6
(gdb) bt
#0  0x7fe9f08b3a72 in __dynamic_cast () at /lib64/libstdc++.so.6
#1  0x7fe9f32b7200 in Plasma::DataContainer::getDataEngine() () at
/lib64/libKF5Plasma.so.5


Fatal signal: Segmentation fault
- Backtrace -
0x559983a27140 gdb_internal_backtrace_1
../../gdb/bt-utils.c:122
0x559983a27140 _Z22gdb_internal_backtracev
../../gdb/bt-utils.c:168
0x559983b64252 handle_fatal_signal
../../gdb/event-top.c:895
0x559983b64429 handle_sigsegv
../../gdb/event-top.c:968
0x7f0426f6e99f ???
   
/usr/src/debug/glibc-2.38-14.fc39.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x5599839f43e8 _ZNK5block5scopeEv
../../gdb/block.c:293
0x559983aab066 _Z26cp_lookup_transparent_typePKc
../../gdb/cp-namespace.c:1029
0x559983ba009c _Z13check_typedefP4type
../../gdb/gdbtypes.c:3052
0x559983d2601c _Z19type_to_type_objectP4type
../../gdb/python/py-type.c:1468
0x559983d274f3 convert_field
../../gdb/python/py-type.c:221
0x559983d27afe make_fielditem
../../gdb/python/py-type.c:275
0x559983d27afe typy_iterator_iternext
../../gdb/python/py-type.c:1440
0x7f04278339fb ???
/usr/src/debug/python3.12-3.12.1-2.fc39.x86_64/Objects/listobject.c:944
0x7f04278470e0 ???
/usr/src/debug/python3.12-3.12.1-2.fc39.x86_64/Objects/listobject.c:982
0x559983d26f0b typy_fields_items
../../gdb/python/py-type.c:311
0x7f042781ab19 ???
   
/usr/src/debug/python3.12-3.12.1-2.fc39.x86_64/Objects/descrobject.c:454
0x7f042780abfb ???
   
/usr/src/debug/python3.12-3.12.1-2.fc39.x86_64/Include/internal/pycore_call.h:92
0x7f042770f759 ???
Python/bytecodes.c:2706
0x7f0427812cda ???
   
/usr/src/debug/python3.12-3.12.1-2.fc39.x86_64/Include/internal/pycore_call.h:92
0x7f042788d08f ???
/usr/src/debug/python3.12-3.12.1-2.fc39.x86_64/Objects/call.c:957
0x559983d19ca7 search_pp_list
../../gdb/python/py-prettyprint.c:83
0x559983d1a182 find_pretty_printer_from_objfiles
../../gdb/python/py-prettyprint.c:113
0x559983d1a182 find_pretty_printer
../../gdb/python/py-prettyprint.c:173
0x559983d1a647
_Z30gdbpy_apply_val_pretty_printerPK23extension_language_defnP5valueP7ui_fileiPK19value_print_optionsPK13language_defn
../../gdb/python/py-prettyprint.c:603
0x559983b6b748
_Z33apply_ext_lang_val_pretty_printerP5valueP7ui_fileiPK19value_print_optionsPK13language_defn
../../gdb/extension.c:489
0x559983f038e6
_Z16common_val_printP5valueP7ui_fileiPK19value_print_optionsPK13language_defn
../../gdb/valprint.c:1072
0x559983d0519e py_print_value
../../gdb/python/py-framefilter.c:251
0x559983d057cb py_print_single_arg
../../gdb/python/py-framefilter.c:397
0x559983d05dee enumerate_args
../../gdb/python/py-framefilter.c:488
0x559983d070dd py_print_args
../../gdb/python/py-framefilter.c:721
0x559983d070dd py_print_frame
../../gdb/python/py-framefilter.c:952
0x559983d087d2
_Z24gdbpy_apply_frame_filterPK23extension_language_defn14frame_info_ptr10enum_flagsI17frame_filter_flagE19ext_lang_frame_argsP6ui_outii
../../gdb/python/py-framefilter.c:1228
0x559983b6bf89
_Z27apply_ext_lang_frame_filter14frame_info_ptr10enum_flagsI17frame_filter_flagE19ext_lang_frame_argsP6ui_outii
../../gdb/extension.c:541
0x559983e0a166 backtrace_command_1
../../gdb/stack.c:2029
0x559983e0a166 backtrace_command
../../gdb/stack.c:2168
0x559983a63794 _Z8cmd_funcP16cmd_list_elementPKci
../../gdb/cli/cli-decode.c:2735
0x559983e73b24 _Z15execute_commandPKci
../../gdb/top.c:575
0x559983b64ab1 _Z15command_handlerPKc
../../gdb/event-top.c:555
0x559983b665a8
_Z20command_line_handlerOSt10unique_ptrIcN3gdb13xfree_deleterIcEEE
../../gdb/event-top.c:791
0x559983b65170 gdb_rl_callback_handler
../../gdb/event-top.c:260
0x7f0427eaf0dc ???
0x559983b652d5 gdb_rl_callback_read_char_wrapper_noexcept
../../gdb/event-top.c:196
0x559983b65487 gdb_rl_callback_read_char_wrapper
../../gdb/event-top.c:235
0x559983eb501f stdin_event_handler
../../gdb/ui.c:155
0x5599840e573d gdb_wait_for_event
../../gdbsupport/event-loop.cc:716
0x5599840e62f1 _Z16gdb_do_one_eventi
../../gdbsupport/event-loop.cc:264
0x559983c51b11 start_event_loop
../../gdb/

[plasmashell] [Bug 471248] plasmashell on Wayland crashed occasionally when playing Instagram story videos in Firefox

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=471248

--- Comment #7 from Matt Fagnani  ---
plasmashell crashed in this way at least twice with 5.27.9 and three times with
5.27.10. On the last such crash with 5.27.10, drkonqi appeared and showed a
segmentation fault in plasmashell on its first page. drkonqi, gdb, kioslave,
plasmashell were aborted by systemd while I was generating the trace after 40 s
because /usr/lib/systemd/user/plasma-plasmashell.service had TimeoutSec=40sec
due to the problem I reported at https://bugs.kde.org/show_bug.cgi?id=478287
Those processes were aborted because Fedora services use the drop-in
configuration file /usr/lib/systemd/user/service.d/10-timeout-abort.conf which
had TimeoutStopFailureMode=abort. The default timeout of 40 s for
plasma-plasmashell.service wasn't long enough for drkonqi and gdb to trace
plasmashell when qt5 debuginfo packages were installed and report the crash.
The crashes' core dumps weren't saved for viewing with coredumpctl so the
crashes' information was lost.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478287] drkonqi, kioslave5, and gdb crashed when creating traces of plasmashell crashes

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478287

Matt Fagnani  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
  Component|general |generic-crash
 Ever confirmed|0   |1
 Resolution|BACKTRACE   |---
Version|5.27.9  |5.27.10
Product|drkonqi |plasmashell
   Target Milestone|--- |1.0

--- Comment #8 from Matt Fagnani  ---
This problem still happens with 5.27.10. I'm reassigning this report to
plasmashell because /usr/lib/systemd/user/plasma-plasmashell.service had
TimeoutSec=40sec. When drkonqi was still creating the trace of plasmashell with
gdb 40 s after plasmashell crashed, systemd aborted
plasma-plasmashell.service's processes plasmashell, drkonqi, kioslave5, and
gdb. Those processes were aborted because Fedora services use the drop-in
configuration file /usr/lib/systemd/user/service.d/10-timeout-abort.conf which
had TimeoutStopFailureMode=abort. The default timeout of 40 s for
plasma-plasmashell.service wasn't long enough for drkonqi and gdb to trace
plasmashell when qt5 debuginfo packages were installed and report the crash.
The tracing didn't take as long when qt5 debuginfo packages weren't installed,
but there still wouldn't be enough time to report crashes in 40 s. The crashes'
core dumps weren't saved for viewing with coredumpctl so the crashes'
information was lost. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478970] plasmawindowed 5.91.0 crashed sometimes when closing

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478970

Matt Fagnani  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=478893

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478893] plasmawindowed crashed in QQuickItem::window when clicking on its maximized window

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478893

Matt Fagnani  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED
   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=478970

--- Comment #2 from Matt Fagnani  ---
Plasma 5.91.0 in Fedora-KDE-Live-x86_64-Rawhide-20231226.n.0.iso doesn't have
this problem. plasmawindowed 5.91.0 often crashed when closing as reported at
https://bugs.kde.org/show_bug.cgi?id=478970

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 478019] Plasma froze after exiting full screen mode in GNOME Boxes QEMU/KVM VMs started in full screen mode

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478019

Matt Fagnani  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Matt Fagnani  ---
Plasma 5.91.0 in Fedora-KDE-Live-x86_64-Rawhide-20231226.n.0.iso doesn't have
this problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 477643] Plasma 5.27.80 got stuck on the splash screen in VMs with kwin_wayland errors

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=477643

Matt Fagnani  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #2 from Matt Fagnani  ---
Plasma 5.91.0 doesn't have this problem in
Fedora-KDE-Live-x86_64-Rawhide-20231226.n.0.iso. The resolution seems to be
changed automatically, as the splash screen icon like ...> moves left and
right. The desktop appeared normally.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478818] Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478818

--- Comment #6 from Matt Fagnani  ---
In System Settings > Search > Plasma Search > Configure KRunner, History was
set to Enable Suggestions by default. I changed History to Disabled on several
GNOME Boxes VM boots before searching, and the problem didn't happen. The
Enable Suggestions setting for History of KRunner doesn't appear in my Plasma
5.27.10 installation, so it might be new. The search suggestions based on
history might be the reason for the problem. I saw the problem in Plasma 5.91.0
on bare metal, so this might not be specific to GNOME Boxes VMs.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478970] plasmawindowed 5.91.0 crashed sometimes when closing

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478970

--- Comment #3 from Matt Fagnani  ---
The null q pointer line wasn't shown in my previous comment.

(gdb) frame 2
#2  0x7fbed3210af3 in Plasma::AppletPrivate::mainConfigGroup
(this=0x5603941b7b40)
at
/usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasma/private/applet_p.cpp:514
Downloading source file
/usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasma/private/applet_p.cpp
514 Containment *c = q->containment();  
(gdb) p q
$4 = (Plasma::Applet *) 0x0

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478970] plasmawindowed 5.91.0 crashed sometimes when closing

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478970

--- Comment #2 from Matt Fagnani  ---
Created attachment 164433
  --> https://bugs.kde.org/attachment.cgi?id=164433=edit
Full trace of all threads of plasmawindowed crash in QObject::parent

plasmawindowed org.kde.plasma.kickoff crashed when closing with a different
trace in QObject::parent. The crash might've been a null pointer dereference
since QObject::parent had this=0x0.

Core was generated by `plasmawindowed org.kde.plasma.kickoff'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  QObject::parent (this=0x0) at /usr/include/qt6/QtCore/qscopedpointer.h:90
Downloading source file /usr/include/qt6/QtCore/qscopedpointer.h
90  T *operator->() const noexcept  
[Current thread is 1 (Thread 0x7fbed19f9b80 (LWP 13870))]
Missing separate debuginfos, use: dnf debuginfo-install
plasma-workspace-5.91.0-2.fc40.x86_64
(gdb) bt
#0  QObject::parent (this=0x0) at /usr/include/qt6/QtCore/qscopedpointer.h:90
#1  Plasma::Applet::containment (this=)
at /usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasma/applet.cpp:733
#2  0x7fbed3210af3 in Plasma::AppletPrivate::mainConfigGroup
(this=0x5603941b7b40)
at
/usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasma/private/applet_p.cpp:514
#3  0x7fbed31eeea5 in Plasma::AppletPrivate::mainConfigGroup
(this=)
at /usr/include/qt6/QtCore/qarraydatapointer.h:413
#4  Plasma::Applet::config (this=0x5603941ac5b0)
at /usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasma/applet.cpp:205
#5  0x7fbed3273f8f in PlasmaQuick::AppletQuickItem::~AppletQuickItem
(this=, this=)
at
/usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasmaquick/appletquickitem.cpp:459
#6  0x7fbed32750e2 in PlasmoidItem::~PlasmoidItem (this=,
this=)
at
/usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasmaquick/plasmoid/plasmoiditem.cpp:46
#7  QQmlPrivate::QQmlElement::~QQmlElement (this=,
this=)
at /usr/include/qt6/QtQml/qqmlprivate.h:99
#8  QQmlPrivate::QQmlElement::~QQmlElement (this=,
this=)
at /usr/include/qt6/QtQml/qqmlprivate.h:99
#9  0x7fbed328e5d0 in PlasmaQuick::SharedQmlEngine::~SharedQmlEngine
(this=, this=)
at
/usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasmaquick/sharedqmlengine.cpp:153
#10 0x7fbed328e685 in PlasmaQuick::SharedQmlEngine::~SharedQmlEngine
(this=, this=)
at
/usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasmaquick/sharedqmlengine.cpp:155
#11 0x7fbed09fa92d in QObjectPrivate::deleteChildren
(this=this@entry=0x5603941ade50)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:2206
#12 0x7fbed09fef68 in QObject::~QObject (this=,
__in_chrg=)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:1159
#13 0x7fbed31ea135 in Plasma::Applet::~Applet (this=,
this=)
at /usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasma/applet.cpp:90
#14 0x7fbed09f3629 in QObject::event (this=0x5603941ac5b0,
e=0x7fbe7cf5e620)
--Type  for more, q to quit, c to continue without paging--c
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:1424
#15 0x7fbed1bc3168 in QApplicationPrivate::notify_helper (this=, receiver=0x5603941ac5b0, 
e=0x7fbe7cf5e620) at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/widgets/kernel/qapplication.cpp:3296
#16 0x7fbed09a0e08 in QCoreApplication::notifyInternal2
(receiver=0x5603941ac5b0, event=0x7fbe7cf5e620)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1121
#17 0x7fbed09a100d in QCoreApplication::sendEvent (receiver=, event=)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1539
#18 0x7fbed09a4d05 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x560393dceb60)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1901
#19 0x7fbed09a507d in QCoreApplication::sendPostedEvents
(receiver=, event_type=)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1760
#20 0x7fbed0c6daef in postEventSourceDispatch (s=0x560393e5c8e0)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:243
#21 0x7fbecf614e5c in g_main_dispatch (context=0x7fbeb8000ef0) at
../glib/gmain.c:3476
#22 g_main_context_dispatch_unlocked (context=0x7fbeb8000ef0) at
../glib/gmain.c:4284
#23 0x7fbecf66ff18 in g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x7fbeb8000ef0, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../glib/gmain.c:4349
#24 0x7fbecf612ad3 in g_main_context_iteration (context=0x7fbeb8000ef0,
may_block=1) at ../glib/gmain.c:4414
#25 0x7fbed0c6d39f in QEventDispatcherGlib::processEvents
(this=0x560393dd5590, flags=...)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/

[plasmashell] [Bug 478818] Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478818

--- Comment #5 from Matt Fagnani  ---
The problem happened for more searches than I thought. Typing ae showed aae and
ag showed aag while there aren't programs started with ae or ag shown in the
menu. Typing aa showed aa so the two first letters might need to be different.
The problem also happened when I ran plasmawindowed org.kde.plasma.kickoff in
Plasma 5.91.0.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478818] Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478818

--- Comment #4 from Matt Fagnani  ---
I found that searching for the first two letters which are prefixes of multiple
programs names showed the doubled first letter problem.
Searching for co showed cco and Contact Theme Editor, Contact Print Theme
Editor, Connection Preferences, Colors are shown in the menu with co
Searching for kd showed kkd and KDE Partition Manager, KDE Connect (SMS), KDE
Wallet are shown in the menu with kd
Searching for fi showed ffi and Filelight, Firewall, Firefox...are shown in the
menu with fi

I prevented plasma-baloorunner.service from running with sudo systemctl mask
--user plasma-baloorunner.service, but the problem still appeared.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478818] Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478818

--- Comment #3 from Matt Fagnani  ---
Searching for ko showed kko the first time in GNOME Boxes, but typing k just
showed k with no results.  There were Konsole, Kontact, KOrganizer, and
Kolourpaint in the results when I corrected it to ko. I haven't seen this
problem with other search strings. There were many spice-vdagent errors in the
journal when using GNOME Boxes which I reported at
https://bugs.kde.org/show_bug.cgi?id=478019 I stopped spice-vdagent before
searching for ko with sudo systemctl stop spice-vdagentd.service
spice-vdagentd.socket, but kko was still shown.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478970] plasmawindowed 5.91.0 crashed sometimes when closing

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478970

Matt Fagnani  changed:

   What|Removed |Added

   Keywords||qt6

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478970] plasmawindowed 5.91.0 crashed sometimes when closing

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478970

--- Comment #1 from Matt Fagnani  ---
Created attachment 164427
  --> https://bugs.kde.org/attachment.cgi?id=164427=edit
Full trace of all threads of plasmawindowed crash when closing

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478970] New: plasmawindowed 5.91.0 crashed sometimes when closing

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478970

Bug ID: 478970
   Summary: plasmawindowed 5.91.0 crashed sometimes when closing
Classification: Plasma
   Product: plasmashell
   Version: 5.91.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: 1.0

Created attachment 164426
  --> https://bugs.kde.org/attachment.cgi?id=164426=edit
Valgrind log with plasmawindowed org.kde.plasma.kickoff

SUMMARY

I ran plasmawindowed org.kde.plasma.kickoff in Konsole in Plasma 5.91.0 on
Wayland in Fedora Rawhide based on https://community.kde.org/Plasma/Debugging
plasmawindowed was blank grey. I maximized plasmawindowed. The main part of the
plasmawindowed window showed a bigger version of the icon like ...> shown on
the Plasma splash screen. I clicked on the main part of the plasmawindowed
window. The Application Launcher menu was shown. The crashes I reported at
https://bugs.kde.org/show_bug.cgi?id=478893 with Plasma 5.90.0 didn't happen. I
closed plasmawindowed. plasmawindowed crashed with an error "corrupted size vs.
prev_size while consolidating" in malloc_printerr in frame 5 of the trace.

Core was generated by `plasmawindowed org.kde.plasma.kickoff'.
Program terminated with signal SIGABRT, Aborted.
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0)
at pthread_kill.c:44
Downloading source file
/usr/src/debug/glibc-2.38.9000-29.fc40.x86_64/nptl/pthread_kill.c
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;  
[Current thread is 1 (Thread 0x7f1b4c3b9b80 (LWP 7248))]
Missing separate debuginfos, use: dnf debuginfo-install
plasma-workspace-5.91.0-2.fc40.x86_64
(gdb) bt
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0)
at pthread_kill.c:44
#1  0x7f1b4a4acc33 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#2  0x7f1b4a45a8fe in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3  0x7f1b4a4428ff in __GI_abort () at abort.c:79
#4  0x7f1b4a4437d0 in __libc_message_impl (fmt=fmt@entry=0x7f1b4a5c1335
"%s\n") at ../sysdeps/posix/libc_fatal.c:132
#5  0x7f1b4a4b6b35 in malloc_printerr (
str=str@entry=0x7f1b4a5c4528 "corrupted size vs. prev_size while
consolidating") at malloc.c:5770
#6  0x7f1b4a4b8c74 in _int_free_merge_chunk (av=av@entry=0x7f1b4a5f5ac0
, p=0x562f336de2e0, size=432)
at malloc.c:4693
#7  0x7f1b4a4b8f4a in _int_free (av=0x7f1b4a5f5ac0 ,
p=p@entry=0x562f336de3f0, 
have_lock=, have_lock@entry=0) at malloc.c:4644
#8  0x7f1b4a4bb7de in __GI___libc_free (mem=0x562f336de400) at
malloc.c:3396
#9  0x7f1b4d5dce98 in PlasmaQuick::AppletQuickItemPrivate::preloadWeight
(this=0x562f338758b0)
at
/usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasmaquick/appletquickitem.cpp:69
#10 0x7f1b4d5def99 in PlasmaQuick::AppletQuickItem::~AppletQuickItem
(this=, this=)
at /usr/include/qt6/QtCore/qflags.h:74
#11 0x7f1b4d5e00e2 in PlasmoidItem::~PlasmoidItem (this=,
this=)
at
/usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasmaquick/plasmoid/plasmoiditem.cpp:46
#12 QQmlPrivate::QQmlElement::~QQmlElement (this=,
this=)
at /usr/include/qt6/QtQml/qqmlprivate.h:99
#13 QQmlPrivate::QQmlElement::~QQmlElement (this=,
this=)
at /usr/include/qt6/QtQml/qqmlprivate.h:99
#14 0x7f1b4d5f95d0 in PlasmaQuick::SharedQmlEngine::~SharedQmlEngine
(this=, this=)
at
/usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasmaquick/sharedqmlengine.cpp:153
#15 0x7f1b4d5f9685 in PlasmaQuick::SharedQmlEngine::~SharedQmlEngine
(this=, this=)
at
/usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasmaquick/sharedqmlengine.cpp:155
#16 0x7f1b4abfa92d in QObjectPrivate::deleteChildren
(this=this@entry=0x562f336d4780)
--Type  for more, q to quit, c to continue without paging--c
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:2206
#17 0x7f1b4abfef68 in QObject::~QObject (this=,
__in_chrg=)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:1159
#18 0x7f1b4d555135 in Plasma::Applet::~Applet (this=,
this=)
at /usr/src/debug/libplasma-5.91.0-1.fc40.x86_64/src/plasma/applet.cpp:90
#19 0x7f1b4abf3629 in QObject::event (this=0x562f336d5350,
e=0x562f34598c30)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:1424
#20 0x7f1b4bdc3168 in QApplicationPrivate::notify_helper (this=, receiver=0x562f336d5350, 
e=0x562f34598c30) at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/widgets/kernel/qapplication.cpp:3296
#21 0x7f1b4aba0e08 in QCoreApplication::notifyInternal2
(receiver=0x562f336d5350, event=0x562f34598c30)

[KPipeWire] [Bug 478086] plasmashell crashed sometimes in QtWaylandClient::QWaylandWindow::createDecoration when hovering over task manager icons

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478086

--- Comment #4 from Matt Fagnani  ---
Created attachment 164390
  --> https://bugs.kde.org/attachment.cgi?id=164390=edit
Valgrind log from trying to reproduce plasmashell crash by hovering over task
manager icons

I saw plasmashell crash with this type of trace in Plasma 5.90.0 when I
disabled WiFi in the Plasma NetworkManager applet then clicked off of the
applet to close it. This crash didn't usually happen when doing so.

I ran plasmashell under valgrind and reproduced the crash as before. The error
The Wayland connection broke. Did the Wayland compositor die? was shown in
Konsole so the crash might've been due to that different reason. The window
previews for konsole and other running programs weren't shown when run under
valgrind, but the popups with just their names were shown. There were many
invalid reads which looked to be buffer overreads. The ones involving
KSvg::SvgPrivate::createRenderer might be more likely to be involved with the
window preview popups. I'm attaching the valgrind log.

==8941== Invalid read of size 16
==8941==at 0x72310E7: UnknownInlinedFun (emmintrin.h:706)
==8941==by 0x72310E7: aeshash128_lt16 (qhash.cpp:630)
==8941==by 0x72310E7: aeshash128(unsigned char const*, unsigned long,
unsigned long, unsigned long) (qhash.cpp:771)
==8941==by 0x65EE59A: UnknownInlinedFun (qhash.h:57)
==8941==by 0x65EE59A: QHashPrivate::Data >::findBucket(QStringView const&) const (qhash.h:683)
==8941==by 0x6621E99: UnknownInlinedFun (qhash.h:718)
==8941==by 0x6621E99: QHash::iterator
QHash::emplace_helper(QStringView&&,
QHashDummyValue&&) [clone .isra.0] (qhash.h:1335)
==8941==by 0x65FE1D3: UnknownInlinedFun (qhash.h:1316)
==8941==by 0x65FE1D3: UnknownInlinedFun (qset.h:158)
==8941==by 0x65FE1D3: UnknownInlinedFun (kconfig.cpp:328)
==8941==by 0x65FE1D3: UnknownInlinedFun (kconfigdata_p.h:252)
==8941==by 0x65FE1D3: UnknownInlinedFun (kconfig.cpp:323)
==8941==by 0x65FE1D3: KConfigGroup::groupList() const
(kconfiggroup.cpp:1168)
==8941==by 0x1B8580: ShellCorona::sanitizeScreenLayout(QString const&)
[clone .isra.0] (shellcorona.cpp:694)
==8941==by 0x175796: ShellCorona::load() (shellcorona.cpp:772)
==8941==by 0x13DE25: UnknownInlinedFun (shellcorona.cpp:328)
==8941==by 0x13DE25: main (main.cpp:227)
==8941==  Address 0x1b5764aa is 42 bytes inside a block of size 46 alloc'd
==8941==at 0x484280F: malloc (vg_replace_malloc.c:442)
==8941==by 0x73DCD10: allocateData (qarraydata.cpp:139)
==8941==by 0x73DCD10: QArrayData::allocate(QArrayData**, long long, long
long, long long, QArrayData::AllocationOption) (qarraydata.cpp:189)
==8941==by 0x73A3E53: allocate (qarraydata.h:105)
==8941==by 0x73A3E53: QString::QString(long long, Qt::Initialization)
(qstring.cpp:2530)
==8941==by 0x73BC0BE: QUtf8::convertToUnicode(QByteArrayView)
(qstringconverter.cpp:608)
==8941==by 0x739D18D: QString::fromUtf8(QByteArrayView) (qstring.cpp:5861)
==8941==by 0x65FD74A: UnknownInlinedFun (qstring.h:588)
==8941==by 0x65FD74A: KConfigIniBackend::parseConfig(QByteArray const&,
KEntryMap&, QFlags, bool) (kconfigini.cpp:157)
==8941==by 0x65E7FB1: UnknownInlinedFun (kconfigini.cpp:64)
==8941==by 0x65E7FB1: KConfigPrivate::parseConfigFiles() (kconfig.cpp:791)
==8941==by 0x66052BE: UnknownInlinedFun (ksharedconfig.cpp:124)
==8941==by 0x66052BE: KSharedConfig::openConfig(QString const&,
QFlags, QStandardPaths::StandardLocation)
(ksharedconfig.cpp:89)
==8941==by 0x1B7F0E: ShellCorona::sanitizeScreenLayout(QString const&)
[clone .isra.0] (shellcorona.cpp:683)
==8941==by 0x175796: ShellCorona::load() (shellcorona.cpp:772)
==8941==by 0x13DE25: UnknownInlinedFun (shellcorona.cpp:328)
==8941==by 0x13DE25: main (main.cpp:227)
==8941== 
==8941== Invalid read of size 16
==8941==at 0x72310E7: UnknownInlinedFun (emmintrin.h:706)
==8941==by 0x72310E7: aeshash128_lt16 (qhash.cpp:630)
==8941==by 0x72310E7: aeshash128(unsigned char const*, unsigned long,
unsigned long, unsigned long) (qhash.cpp:771)
==8941==by 0x65EE59A: UnknownInlinedFun (qhash.h:57)
==8941==by 0x65EE59A: QHashPrivate::Data >::findBucket(QStringView const&) const (qhash.h:683)
==8941==by 0x6621E99: UnknownInlinedFun (qhash.h:718)
==8941==by 0x6621E99: QHash::iterator
QHash::emplace_helper(QStringView&&,
QHashDummyValue&&) [clone .isra.0] (qhash.h:1335)
==8941==by 0x65FE2C0: UnknownInlinedFun (qhash.h:1321)
==8941==by 0x65FE2C0: UnknownInlinedFun (qset.h:158)
==8941==by 0x65FE2C0: UnknownInlinedFun (kconfig.cpp:328)
==8941==by 0x65FE2C0: UnknownInlinedFun (kconfigdata_p.h:252)
==8941==by 0x65FE2C0: UnknownInlinedFun (kconfig.cpp:323)
==8941==by 0x65FE2C0: KConfigGroup::groupList() const
(kconfiggroup.cpp:1168)
==8941==by 0x4D502C6: Plasma::Containment::restoreContents(KConfigGroup&)
(co

[plasmashell] [Bug 478893] plasmawindowed crashed in QQuickItem::window when clicking on its maximized window

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478893

--- Comment #1 from Matt Fagnani  ---
Created attachment 164389
  --> https://bugs.kde.org/attachment.cgi?id=164389=edit
Full trace of all threads of plasmawindowed org.kde.plasma.kicker crash when
typing in its search bar

I ran plasmawindowed org.kde.plasma.kicker in konsole in Plasma 5.90.0 using
the same Fedora Rawhide image. I typed k in the search bar in Kicker in
plasmawindowed. plasmawindowed crashed with the same type of trace as when
clicking on the maximized window of Kickoff. 

Core was generated by `plasmawindowed org.kde.plasma.kicker'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0)
at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;  
[Current thread is 1 (Thread 0x7f478e953b80 (LWP 3153))]
Missing separate debuginfos, use: dnf debuginfo-install
plasma-workspace-5.90.0-2.fc40.x86_64
(gdb) bt
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0)
at pthread_kill.c:44
#1  0x7f478d2a6c23 in __pthread_kill_internal (signo=11,
threadid=) at pthread_kill.c:78
#2  0x7f478d2548ee in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3  0x7f478be366cb in KCrash::defaultCrashHandler (sig=11)
at /usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:612
#4  
#5  QQuickItem::window (this=0x0)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/quick/items/qquickitem.cpp:2870
#6  0x7f4790393805 in PlasmaQuick::PopupPlasmaWindow::setVisualParent
(item=, this=)
at
/usr/src/debug/libplasma-5.90.0-1.fc40.x86_64/src/plasmaquick/popupplasmawindow.cpp:227
#7  PlasmaQuick::PopupPlasmaWindow::setVisualParent (this=0x56499086b830,
item=0x0)
at
/usr/src/debug/libplasma-5.90.0-1.fc40.x86_64/src/plasmaquick/popupplasmawindow.cpp:217
#8  0x7f478f712513 in QQmlPropertyData::writeProperty (this=, target=, 
value=, flags=...)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/redhat-linux-build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:298
#9  0x7f478f70f8d8 in QObjectPointerBinding::write (this=0x56499087c600,
result=..., isUndefined=false, flags=...)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:787
#10 0x7f478f70cac6 in QQmlBinding::doUpdate (this=0x56499087c600,
watcher=..., flags=..., scope=...)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:700
#11 0x7f478f70ec38 in QQmlBinding::update (this=0x56499087c600, flags=...)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:164
#12 0x7f478f7c65cc in QQmlNotifier::emitNotify (endpoint=,
a=0x0)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlnotifier.cpp:70
#13 0x7f478da01e90 in doActivate (sender=0x5649900ec530,
signal_index=46, argv=argv@entry=0x0)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:3913
#14 0x7f478d9f8c9f in QMetaObject::activate (sender=,
signalOffset=, 
--Type  for more, q to quit, c to continue without paging--c
local_signal_index=, argv=argv@entry=0x0)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:4094
#15 0x7f478f873d9f in QQmlVMEMetaObject::activate
(this=this@entry=0x564990872db0, object=, 
index=, args=args@entry=0x0)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlvmemetaobject.cpp:1457
#16 0x7f478f8764c2 in QQmlVMEMetaObject::metaCall (this=0x564990872db0,
o=, c=, 
_id=, a=)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlvmemetaobject.cpp:1007
#17 0x7f478d9b3e95 in QMetaProperty::write (this=0x7ffc30b8e740,
object=0x5649900ec530, v=...)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qmetaobject.cpp:3724
#18 0x7f478d9ffe8b in QObject::doSetProperty (this=0x5649900ec530,
name=, 
name@entry=0x7f47903b5275 "compactRepresentation",
lvalue=lvalue@entry=0x7ffc30b8e810, 
rvalue=rvalue@entry=0x7ffc30b8e810)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:4218
#19 0x7f4790376ab5 in QObject::setProperty (value=..., name=0x7f47903b5275
"compactRepresentation", 
this=) at /usr/include/qt6/QtCore/qobject.h:379
#20 PlasmaQuick::AppletQuickItemPrivate::compactRepresentationCheck
(this=0x56498fc82280)
at
/usr/src/debug/libplasma-5.90.0-1.fc40.x86_64/src/plasmaquick/appletquickitem.cpp:355
#21 0x7f478fc3004f in QQuickItem::setSize (this=0x56498fca7370, size=...)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/quick/items/qquickitem.cpp:7576
#22 0x7f478fbf8fa2 in QQuickAnchorsPrivate::setItemSize (v=...,
this=0x56498fcdc160)
  

[plasmashell] [Bug 478893] plasmawindowed crashed in QQuickItem::window when clicking on its maximized window

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478893

Matt Fagnani  changed:

   What|Removed |Added

   Keywords||qt6

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478893] New: plasmawindowed crashed in QQuickItem::window when clicking on its maximized window

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478893

Bug ID: 478893
   Summary: plasmawindowed crashed in QQuickItem::window when
clicking on its maximized window
Classification: Plasma
   Product: plasmashell
   Version: 5.90.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: 1.0

SUMMARY

I booted the Fedora Rawhide/40 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20231222.n.0.iso in a QEMU/KVM VM using GNOME
Boxes with 3D acceleration enabled using the virgl driver from mesa 23.3.1.
Plasma 5.90.0 on Wayland started. I started Konsole. I ran plasmawindowed
org.kde.plasma.kickoff in Konsole based on
https://community.kde.org/Plasma/Debugging plasmawindowed was blank grey. I
maximized plasmawindowed. The main part of the plasmawindowed window showed a
bigger version of the icon like ...> shown on the Plasma splash screen. I
clicked on the main part of the plasmawindowed window. plasmawindowed crashed
in QQuickItem::window.

Application: plasmawindowed (plasmawindowed), signal: Segmentation fault

[KCrash Handler]
#4  QQuickItem::window (this=0x0) at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/quick/items/qquickitem.cpp:2870
#5  0x7fa8816a7805 in PlasmaQuick::PopupPlasmaWindow::setVisualParent
(item=, this=) at
/usr/src/debug/libplasma-5.90.0-1.fc40.x86_64/src/plasmaquick/popupplasmawindow.cpp:227
#6  PlasmaQuick::PopupPlasmaWindow::setVisualParent (this=0x557074927ad0,
item=0x0) at
/usr/src/debug/libplasma-5.90.0-1.fc40.x86_64/src/plasmaquick/popupplasmawindow.cpp:217
#7  0x7fa880b12513 in QQmlPropertyData::writeProperty (this=, target=, value=, flags=) at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/redhat-linux-build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:298
#8  0x7fa880b0f8d8 in QObjectPointerBinding::write (this=0x557074bbbaf0,
result=..., isUndefined=false, flags=...) at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:787
#9  0x7fa880b0cac6 in QQmlBinding::doUpdate (this=0x557074bbbaf0,
watcher=..., flags=..., scope=...) at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:700
#10 0x7fa880b0ec38 in QQmlBinding::update (this=0x557074bbbaf0, flags=...)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:164
#11 0x7fa880bc65cc in QQmlNotifier::emitNotify (endpoint=,
a=0x0) at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlnotifier.cpp:70
#12 0x7fa87ee01e90 in void doActivate(QObject*, int, void**) () from
/lib64/libQt6Core.so.6
#13 0x7fa880c764c2 in QQmlVMEMetaObject::metaCall (this=0x557074cde660,
o=, c=, _id=, a=)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlvmemetaobject.cpp:1007
#14 0x7fa87edb3e95 in QMetaProperty::write(QObject*, QVariant&&) const ()
from /lib64/libQt6Core.so.6
#15 0x7fa87edffe8b in QObject::doSetProperty(char const*, QVariant const*,
QVariant*) () from /lib64/libQt6Core.so.6
#16 0x7fa88168aab5 in QObject::setProperty (value=..., name=0x7fa8816c9275
"compactRepresentation", this=) at
/usr/include/qt6/QtCore/qobject.h:379
#17 PlasmaQuick::AppletQuickItemPrivate::compactRepresentationCheck
(this=0x5570746d0310) at
/usr/src/debug/libplasma-5.90.0-1.fc40.x86_64/src/plasmaquick/appletquickitem.cpp:355
#18 0x7fa88167f9d1 in PlasmaQuick::AppletQuickItem::setSwitchHeight
(this=0x5570746f0bb0, height=508) at
/usr/src/debug/libplasma-5.90.0-1.fc40.x86_64/src/plasmaquick/appletquickitem.cpp:746
#19 0x7fa880b12513 in QQmlPropertyData::writeProperty (this=, target=, value=, flags=) at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/redhat-linux-build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:298
#20 0x7fa880b10ee7 in GenericBinding<2>::doStore (flags=...,
pd=, value=, this=0x557074700c60) at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:275
#21 GenericBinding<2>::write (this=0x557074700c60, result=...,
isUndefined=, flags=...) at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:243
#22 0x7fa880b0cac6 in QQmlBinding::doUpdate (this=0x557074700c60,
watcher=..., flags=..., scope=...) at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:700
#23 0x7fa880b0ec38 in QQmlBinding::update (this=0x557074700c60, flags=...)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlbinding.cpp:164
#24 0x7fa880bc65cc in QQmlNotifier::emitNotify (endpoint=,
a=0x7ffcd9ebc480) at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/qml/qml/qqmlnotifier.cpp:70
#25 0x7fa87ee01e90 in void 

[kwin] [Bug 478864] Nested kwin_wayland 5.90.0 crashed in QArrayDataPointer >::constEnd in VMs using the llvmpipe driver

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478864

Matt Fagnani  changed:

   What|Removed |Added

   Keywords||qt6

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 478864] New: Nested kwin_wayland 5.90.0 crashed in QArrayDataPointer >::constEnd in VMs using the llvmpipe driver

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478864

Bug ID: 478864
   Summary: Nested kwin_wayland 5.90.0 crashed in
QArrayDataPointer >::constEnd in VMs using the llvmpipe driver
Classification: Plasma
   Product: kwin
   Version: 5.90.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: ---

SUMMARY

I booted the Fedora Rawhide/40 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20231220.n.0.iso in a QEMU/KVM VM using GNOME
Boxes with 3D acceleration disabled using the llvmpipe driver from mesa 23.3.1.
Plasma 5.90.0 on Wayland started. I started Konsole. I tried to run a nested
kwin_wayland session using the instructions at
https://community.kde.org/KWin/Wayland
export $(dbus-launch)
kwin_wayland --xwayland 

The nested kwin_wayland window didn't appear. The following output was in
Konsole which showed a Permission denied error and a segmentation fault of
kwin_wayland.

kwin_wayland --xwayland
No backend specified, automatically choosing Wayland because WAYLAND_DISPLAY is
set
unable to lock lockfile /run/user/1000/wayland-0.lock, maybe another compositor
is running
kwin_core: Parse error in tiles configuration for monitor
"7fb8c463-c102-5440-8fb7-5253b26b5d9c" : "illegal value" Creating default setup
OpenGL vendor string:   Mesa
OpenGL renderer string: llvmpipe (LLVM 17.0.6, 256 bits)
OpenGL version string:  4.5 (Core Profile) Mesa 23.3.1
OpenGL shading language version string: 4.50
Driver: LLVMpipe
GPU class:  Unknown
OpenGL version: 4.5
GLSL version:   4.50
Mesa version:   23.3.1
Requires strict binding:no
Virtual Machine:no
Timer query support:yes
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied
Segmentation fault (core dumped)

The nested kwin_wayland crashed in
QArrayDataPointer >::constEnd. The
crash might've been due to a null pointer dereference since this=0x0 in
KWin::EglSwapchain::acquire in frame 2.

Core was generated by `kwin_wayland --xwayland'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fe3776caece in
QArrayDataPointer >::constEnd
(this=)
at /usr/include/qt6/QtCore/qarraydatapointer.h:121

warning: 121/usr/include/qt6/QtCore/qarraydatapointer.h: No such file or
directory
[Current thread is 1 (Thread 0x7fe3763ff000 (LWP 3019))]
 (gdb) bt
#0  0x7fe3776caece in
QArrayDataPointer >::constEnd
(this=)
at /usr/include/qt6/QtCore/qarraydatapointer.h:121
#1  QList >::end (this=)
at /usr/include/qt6/QtCore/qlist.h:612
#2  KWin::EglSwapchain::acquire (this=0x0) at
/usr/src/debug/kwin-5.90.0-3.fc40.x86_64/src/platformsupport/scenes/opengl/eglswapchain.cpp:103
#3  0x7fe3776a7b13 in KWin::Wayland::WaylandEglCursorLayer::beginFrame
(this=0x5557d102aa60) at /usr/include/c++/13/bits/shared_ptr_base.h:1665
#4  0x7fe37740822a in operator() (__closure=) at
/usr/src/debug/kwin-5.90.0-3.fc40.x86_64/src/compositor_wayland.cpp:301
#5  operator() (__closure=__closure@entry=0x7fff40893770) at
/usr/src/debug/kwin-5.90.0-3.fc40.x86_64/src/compositor_wayland.cpp:321
#6  0x7fe37740895e in KWin::WaylandCompositor::addOutput
(this=this@entry=0x5557d0f77fe0, output=0x5557d0dedd00)
at /usr/src/debug/kwin-5.90.0-3.fc40.x86_64/src/compositor_wayland.cpp:355
#7  0x7fe377408dff in KWin::WaylandCompositor::start (this=0x5557d0f77fe0)
at /usr/src/debug/kwin-5.90.0-3.fc40.x86_64/src/compositor_wayland.cpp:188
#8  0x7fe3747f3827 in QObject::event (this=0x5557d0f77fe0,
e=0x5557d0f78340) at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:1437
#9  0x7fe375bc3168 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt6Widgets.so.6
#10 0x7fe3747a0e08 in QCoreApplication::notifyInternal2
(receiver=0x5557d0f77fe0, event=0x5557d0f78340)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1121
#11 0x7fe3747a100d in QCoreApplication::sendEvent (receiver=, event=)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1539
#12 0x7fe3747a4d05 in QCoreApplicationPrivate::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0,
data=data@entry=0x5557d0d95dc0)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1901
#13 0x7fe37494b786 in QEventDispatcherUNIX::processEvents
(this=0x5557d0da4910, flags=...)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qeventdispatcher_unix.cpp:432
#14 0x7fe375540e42 in

[plasmashell] [Bug 478818] Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478818

Matt Fagnani  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #2 from Matt Fagnani  ---
(In reply to Nate Graham from comment #1)
> Sounds a bit like the system was under some load or hadn't fully finished
> the VT switch, resulted in the first "K" being repeated. Does the same thing
> happen if you type it into KRunner itself? Does it ever happen outside of
> the context of a VT switch?

The problem didn't happen when I pressed alt+f2 and typed konsole into KRunner
on a few VM boots. I don't usually use KRunner that way so I might just have
missed it. I've seen the problem at least 20 times in VMs in the last 2-3 weeks
sometimes a few minutes after the VT switch and when the system was idle
otherwise. The probem might be specific to GNOME Boxes as it didn't happen in
virt-manager QEMU/KVM VMs with the same settings and images. The
plasma-baloorunner.service starting at the same time as the problem with the
errors looked like it might be involved somehow though. The errors like
kf.runner: Error requesting matches; calling "org.kde.runners.baloo"  :
"org.freedesktop.DBus.Error.NotSupported" "" don't happen in Plasma 5.27.10 on
bare metal for me. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478819] New: Logging out of Plasma occasionally led to a black screen instead of sddm appearing

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478819

Bug ID: 478819
   Summary: Logging out of Plasma occasionally led to a black
screen instead of sddm appearing
Classification: Plasma
   Product: plasmashell
   Version: 5.27.9
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Session Management
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: 1.0

SUMMARY

Logging out of Plasma 5.27.9 on Wayland in a Fedora 39 KDE Plasma installation
has occasionally led to a black screen with a text cursor flashing at the top
left instead of sddm on Wayland appearing. I've seen this problem several times
in the last week or so. The black screen happened 10% or less of logouts in
that time. The problem might involve a race condition in which sddm-greeter
sometimes doesn't start. The journal during logouts showed various errors.
dbus-:1.2-org.kde.LogoutPrompt@0.service failed. Many KDE programs lost
connection to the Wayland compositor. plasma-polkit-agent.service and
plasma-powerdevil.service tried to restart many times and failed.

Dec 15 20:59:36 systemd[1449]: Started
dbus-:1.2-org.kde.LogoutPrompt@0.service.
Dec 15 20:59:36 kwin_wayland[1546]: kf.service.services: The desktop entry file
"/usr/share/applications/org.freedesktop.Xwayland.desktop" has Type=
"Application" but has no Exec field.
Dec 15 20:59:36 kwin_wayland[1546]: kf.service.services: The desktop entry file
"/usr/share/applications/qemu.desktop" has Type= "Application" but has no Exec
field.
Dec 15 20:59:36 kernel: Lockdown: systemd-logind: hibernation is restricted;
see man kernel_lockdown.7
Dec 15 20:59:36 kernel: Lockdown: systemd-logind: hibernation is restricted;
see man kernel_lockdown.7
Dec 15 20:59:36 kernel: Lockdown: systemd-logind: hibernation is restricted;
see man kernel_lockdown.7
Dec 15 20:59:36 ksmserver-logout-greeter[5190]: qt.qpa.wayland: Wayland does
not support QWindow::requestActivate()
Dec 15 20:59:36 ksmserver-logout-greeter[5190]: qt.qpa.wayland: Wayland does
not support QWindow::requestActivate()
Dec 15 20:59:39 systemd[1449]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main
process exited, code=exited, status=1/FAILURE
Dec 15 20:59:39 systemd[1449]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed
with result 'exit-code'.
Dec 15 20:59:40 plasmashell[1740]: trying to show an empty dialog
Dec 15 20:59:41 plasmashell[1740]: qt.qpa.wayland: Wayland does not support
QWindow::requestActivate()
Dec 15 20:59:42 systemd[1449]: Started
dbus-:1.2-org.kde.LogoutPrompt@1.service.
Dec 15 20:59:43 kwin_wayland[1546]: kf.service.services: The desktop entry file
"/usr/share/applications/org.freedesktop.Xwayland.desktop" has Type=
"Application" but has no Exec field.
Dec 15 20:59:43 kwin_wayland[1546]: kf.service.services: The desktop entry file
"/usr/share/applications/qemu.desktop" has Type= "Application" but has no Exec
field.
Dec 15 20:59:43 kernel: Lockdown: systemd-logind: hibernation is restricted;
see man kernel_lockdown.7
Dec 15 20:59:43 kernel: Lockdown: systemd-logind: hibernation is restricted;
see man kernel_lockdown.7
Dec 15 20:59:43 kernel: Lockdown: systemd-logind: hibernation is restricted;
see man kernel_lockdown.7
Dec 15 20:59:43 ksmserver-logout-greeter[5234]: qt.qpa.wayland: Wayland does
not support QWindow::requestActivate()
Dec 15 20:59:43 ksmserver-logout-greeter[5234]: qt.qpa.wayland: Wayland does
not support QWindow::requestActivate()
Dec 15 20:59:44 systemd[1449]: Started dbus-:1.2-org.kde.Shutdown@0.service.
Dec 15 20:59:44 systemd[1449]: dbus-:1.2-org.kde.LogoutPrompt@1.service: Main
process exited, code=exited, status=1/FAILURE
Dec 15 20:59:44 systemd[1449]: dbus-:1.2-org.kde.LogoutPrompt@1.service: Failed
with result 'exit-code'.
Dec 15 20:59:44 plasmashell[1740]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/PlasmoidItem.qml:125:
TypeError: Cannot read property 'compactRepresentationItem' of null
Dec 15 20:59:44 kwin_wayland_wrapper[1643]: (EE) failed to read Wayland events:
Connection reset by peer
Dec 15 20:59:44 kded5[1870]: X connection to :0 broken (explicit kill or server
shutdown).
Dec 15 20:59:44 kaccess[2108]: The X11 connection broke (error 1). Did the X11
server die?
Dec 15 20:59:44 systemd[1449]: app-kaccess@autostart.service: Main process
exited, code=exited, status=1/FAILURE
Dec 15 20:59:44 systemd[1449]: app-kaccess@autostart.service: Failed with
result 'exit-code'.
Dec 15 20:59:44 kwin_wayland[1546]: QtDBus: cannot relay signals from parent
QObject(0x55839bc3c020 "") unless they are emitted in the object's thread
QThread(0x55839bb8ad68 "libinput-connection"). Current thread is
QThread(0x55839b93c140 "").
Dec 15 20:59:44 kwalletd5[1490]: The Wayland connection broke. Did the Wayland
compositor die?
Dec 15 20:59:44 kwalletd5[1490]: The Wayland 

[plasmashell] [Bug 478818] New: Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478818

Bug ID: 478818
   Summary: Typing konsole in the Search bar of the Application
Launcher menu showed kkonsole the first time in GNOME
Boxes VMs
Classification: Plasma
   Product: plasmashell
   Version: 5.90.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
CC: mikel5...@gmail.com, noaha...@gmail.com
  Target Milestone: 1.0

SUMMARY

I booted Fedora Rawhide KDE Plasma live images in GNOME Boxes QEMU/KVM VMs in a
Fedora 39 KDE Plasma installation. To work around the VM getting stuck on the
Plasma 5.90.0 on Wayland splash screen as I reported at
https://bugs.kde.org/show_bug.cgi?id=477643 I changed to VT2 using the keyboard
menu in the top bar of GNOME Boxes and selecting Ctrl+Alt+F2. When I changed
back to VT1, Plasma was shown with the Plasma Welcome program open. I opened
the Application Launcher menu. I typed konsole in the Search bar of the
Application Launcher menu. The Search bar showed kkonsole instead of konsole
with no search results the first time I typed it. The journal at the time I
typed konsole showed plasma-baloorunner.service starting and errors like
plasmashell[1844]: kf.runner: Error requesting matches; calling
"org.kde.runners.baloo"  : "org.freedesktop.DBus.Error.NotSupported" ""

Dec 21 00:12:32 plasmashell[1844]: Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Dec 21 00:12:32 plasmashell[1844]: org.kde.plasma.runner.bookmarks: No default
firefox profile found
Dec 21 00:12:32 systemd[1412]: Starting plasma-baloorunner.service - KRunner
provider for baloo file indexer...
Dec 21 00:12:33 baloorunner[3000]: libEGL warning: egl: failed to create dri2
screen
Dec 21 00:12:34 plasmashell[1844]: kf.kunitconversion: currency conversion
table data obtained via network
Dec 21 00:12:34 plasmashell[1844]: QObject::startTimer: Timers cannot be
started from another thread
Dec 21 00:12:34 baloorunner[3000]: MESA: error: ZINK: failed to choose pdev
Dec 21 00:12:34 baloorunner[3000]: libEGL warning: egl: failed to create dri2
screen
Dec 21 00:12:34 systemd[1412]: Started plasma-baloorunner.service - KRunner
provider for baloo file indexer.
Dec 21 00:12:34 plasmashell[1844]: kf.runner: Error requesting matches; calling
"org.kde.runners.baloo"  : "org.freedesktop.DBus.Error.NotSupported" ""
Dec 21 00:12:34 plasmashell[1844]: kf.runner: Error requesting matches; calling
"org.kde.runners.baloo"  : "org.freedesktop.DBus.Error.NotSupported" ""
Dec 21 00:12:34 plasmashell[1844]: kf.runner: Error requesting matches; calling
"org.kde.runners.baloo"  : "org.freedesktop.DBus.Error.NotSupported" ""
Dec 21 00:12:34 chronyd[1257]: Selected source 138.197.152.115
(2.fedora.pool.ntp.org)
Dec 21 00:12:35 plasmashell[1844]: Found icon of unknown type 'unknown' in
'system/package/os/org.kde.latte-dock.desktop/*', skipping it.
Dec 21 00:12:35 plasmashell[1844]: Found icon of unknown type 'unknown' in
'system/package/os/org.kde.discover.snap/*', skipping it.
Dec 21 00:12:35 plasmashell[1844]: Found icon of unknown type 'unknown' in
'system/package/os/io.github.syllo.nvtop/*', skipping it.
Dec 21 00:12:36 plasmashell[1844]: Found icon of unknown type 'unknown' in
'system/package/os/org.kde.kiten.desktop/*', skipping it.

This problem always happened the first time I typed konsole in the Search bar
in a VM's boot. I've seen this happened with 3D acceleration disabled using the
llvmpipe mesa driver and 3D acceleration enabled using the virgl driver. 

STEPS TO REPRODUCE
1. Boot a Fedora 39 KDE Plasma installation updated to 2023-12-20 with
updates-testing enabled
2. Log in to Plasma 5.27.10 on Wayland
3. Start Konsole
4. Install GNOME Boxes if it isn't already with sudo dnf install gnome-boxes
5. Download Fedora-KDE-Live-x86_64-Rawhide-20231220.n.0.iso from
https://koji.fedoraproject.org/koji/buildinfo?buildID=2335875
6. Start GNOME Boxes
7. Boot Fedora-KDE-Live-x86_64-Rawhide-20231220.n.0.iso in a GNOME Boxes
QEMU/KVM VM with 3 GiB RAM, UEFI enabled, and 3D acceleration disabled or
enabled
8. To work around https://bugs.kde.org/show_bug.cgi?id=477643, switch to VT2 in
GNOME boxes via the keyboard menu Ctrl+Alt+F2 and back to VT1 with Ctrl+Alt+F1
after the Plasma 5.90.0 splash screen is shown for several seconds
9. Open the Application Launcher menu
10. Type konsole in the Search bar of the Application Launcher menu

OBSERVED RESULT
Typing konsole in the Search bar of the Application Launcher menu showed
kkonsole the first time in GNOME Boxes VMs

EXPECTED RESULT
Typing konsole in the Search bar of the Application Launcher menu should have
shown konsole

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 

[kwin] [Bug 478421] The panel disappeared after entering full screen mode in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478421

--- Comment #13 from Matt Fagnani  ---
I built kwin 5.90.0 with the patch at
https://invent.kde.org/plasma/kwin/-/merge_requests/4799 added. I updated the
kwin rpms in GNOME Boxes VM using
Fedora-KDE-Live-x86_64-Rawhide-20231216.n.0.iso as in Comment 10. The guest's
panel was still shown in full screen mode after doing that, and Plasma covered
the full screen without the black bands at the top and bottom that I reported.
Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 478421] The panel disappeared after entering full screen mode in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478421

--- Comment #12 from Matt Fagnani  ---
I selected Code > Download Patches at
https://invent.kde.org/plasma/kwin/-/merge_requests/4790 but the patch I
downloaded was the same as the one I downloaded yesterday. Where do I get the
alternative patch?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 478421] The panel disappeared after entering full screen mode in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478421

--- Comment #10 from Matt Fagnani  ---
I built kwin with the patch at
https://invent.kde.org/plasma/kwin/-/merge_requests/4790 added to the current
rawhide kwin repo with fedpkg --release rawhide mockbuild. I copied the kwin
rpms into a GNOME Boxes QEMU/KVM VM using the image
Fedora-KDE-Live-x86_64-Rawhide-20231214.n.0.iso with nautilus. I logged out and
switched to VT2 in the VM. I updated to the kwin rpms I built. I restarted
sddm. The guest's panel still disappeared when I entered full screen mode.
Since the patch fixed the problem at
https://bugs.kde.org/show_bug.cgi?id=477985, the problem I reported might be
different.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 478421] The panel disappeared after entering full screen mode in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478421

--- Comment #9 from Matt Fagnani  ---
The spice-vdagent errors happened at the same time I entered full screen mode
and the guest's panel disappeared. After I stopped spice-vdagentd with sudo
systemctl stop spice-vdagentd.service spice-vdagentd.socket, the guest's panel
was shown in full screen mode and the spice-vdagentd errors weren't shown. I
took this to mean that the panel disappearing is due the same problem with how
GNOME Boxes and spice-vdagent were interacting with Plasma 5.90.0. If you
didn't see the spice-vdagent errors and stopping spice-vdagentd didn't allow
the panel to be shown in full screen mode in VMware for you, then the causes of
the problems we reported might not be the same. The problem I reported didn't
happen using virt-manager, so there might be specific problems with each of
GNOME Boxes and VMware. You can get guest GPU acceleration using the virgl mesa
driver in GNOME Boxes by enabling the 3D acceleration switch in the VM's
properties.

I guess https://invent.kde.org/plasma/kwin/-/merge_requests/4790 is the code
you mentioned. Does that patch apply cleanly to kwin-5.90.0-2.fc40? Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 478421] The panel disappeared after entering full screen mode in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478421

--- Comment #7 from Matt Fagnani  ---
(In reply to Stefan Hoffmeister from comment #5)
> The video shows what I have reported in words in
> https://bugs.kde.org/show_bug.cgi?id=477985, and where progress is being
> made in getting it addressed.
> 
> The only difference is that the underlying kernel graphics driver here (most
> likely) is qxl, while for me it is vmwgfx. Both set the hotplug_mode_update
> DRM property.
> 
> IMHO, this issue here can be resolved as a duplicate of
> https://bugs.kde.org/show_bug.cgi?id=477985

The 6.7-rc5 kernel graphics driver was virtio_gpu in the GNOME Boxes VMs I
used. Did you see the spice-vdagent errors I reported? I don't see them
mentioned in https://bugs.kde.org/show_bug.cgi?id=477985

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 478421] The panel disappeared after entering full screen mode in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478421

--- Comment #4 from Matt Fagnani  ---
(In reply to Vlad Zahorodnii from comment #3)
> Can you check whether plasmashell process crashes?

plasmashell didn't crash when this problem happened. I think that because the
vertical resolution increased but the visible area Plasma was shown in didn't
change, the panel was below the bottom of what was shown in the guest in full
screen mode. This involved the spice-vdagent errors and how GNOME Boxes was
using spice-vdagent. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 478421] The panel disappeared after entering full screen mode in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478421

Matt Fagnani  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #2 from Matt Fagnani  ---
(In reply to Nate Graham from comment #1)
> You''re talking about the Panel in the host OS disappearing when you enter
> Full Screen mode, not the guest OS, right? If so, that's expected. Full
> Screen Mode generally hides the panel. That's the main difference between
> the Full Screen the Maximized modes.

No, the panel in the guest Fedora Rawhide Plasma 5.90.0 disappeared when
entering full screen mode as shown in the recording I attached.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 478421] The panel disappeared after entering full screen mode in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478421

Matt Fagnani  changed:

   What|Removed |Added

   Keywords||qt6

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 478421] New: The panel disappeared after entering full screen mode in GNOME Boxes VMs

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478421

Bug ID: 478421
   Summary: The panel disappeared after entering full screen mode
in GNOME Boxes VMs
Classification: Plasma
   Product: kwin
   Version: 5.90.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: ---

Created attachment 164099
  --> https://bugs.kde.org/attachment.cgi?id=164099=edit
Recording of panel disappearing when entering full screen mode in GNOME Boxes
QEMU/KVM VM with hardware acceleration enabled

SUMMARY

I booted the Fedora Rawhide/40 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20231211.n.0.iso in GNOME Boxes QEMU/KVM VMs in
a Fedora 39 KDE Plasma host using Plasma 5.27.9 on Wayland. To work around the
VM getting stuck on the Plasma 5.27.80 splash screen as I reported at
https://bugs.kde.org/show_bug.cgi?id=477643 I changed to VT2 by using the
keyboard menu in the top bar of GNOME Boxes and selecting Ctrl+Alt+F2. When I
changed back to VT1, Plasma was shown with the Plasma Welcome program open. I
had GNOME Boxes shown as a maximized window. I entered full screen mode in the
VM by selecting the full screen button in the GNOME Boxes top bar. The
resolution appeared to increase vertically, but the visible area Plasma was
shown in remained the same as in the maximized window. There were black bars at
the top and bottom of the screen where Plasma wasn't shown. The panel
disappeared in full screen mode as a result. There were spice-vdagent errors
repeated in the journal in which it appeared to be trying to connect to mutter
by dbus which was odd.

Dec 11 18:42:07 spice-vdagent[2053]: display: failed to call GetCurrentState
from mutter over DBUS
Dec 11 18:42:07 spice-vdagent[2053]:error message: Cannot invoke method;
proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an
owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START
flag
Dec 11 18:42:07 spice-vdagent[2053]: No guest output map, using output index as
display id
Dec 11 18:42:07 kernel: input: spice vdagent tablet as
/devices/virtual/input/input16

This problem happened every time I tried it. I'm attaching a recording of the
problem with these errors shown in Konsole. After I exited full screen mode,
the panel was shown again. 

I stopped spice-vdagent with sudo systemctl stop spice-vdagentd.service
spice-vdagentd.socket The problem didn't happen when entering full screen mode
after I stopped spice-vdagentd and those errors didn't occur. spice-vdagent
crashed when I stopped it. 

STEPS TO REPRODUCE
1. Boot a Fedora 39 KDE Plasma installation updated to 2023-12-11 with
updates-testing enabled
2. Log in to Plasma 5.27.9 on Wayland
3. Start Konsole
4. Install GNOME Boxes if it isn't already with sudo dnf install gnome-boxes
5. Download Fedora-KDE-Live-x86_64-Rawhide-20231211.n.0.iso from
https://koji.fedoraproject.org/koji/buildinfo?buildID=2332213
6. Start GNOME Boxes
7. Boot Fedora-KDE-Live-x86_64-Rawhide-20231211.n.0.iso in a GNOME Boxes
QEMU/KVM VM with 3 GiB RAM, UEFI enabled, and 3D acceleration disabled or
enabled in a maximized window
8. To work around https://bugs.kde.org/show_bug.cgi?id=477643, switch to VT2 in
GNOME boxes via the keyboard menu Ctrl+Alt+F2 and back to VT1 with Ctrl+Alt+F1
9. Enter full screen mode in GNOME Boxes by selecting the full screen button in
its top bar

OBSERVED RESULT
The panel disappeared after entering full screen mode in GNOME Boxes VMs

EXPECTED RESULT
The panel should've remained visible after entering full screen mode

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Rawhide/40
(available in About System)
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1

ADDITIONAL INFORMATION

This problem didn't happen if I selected full screen mode in GNOME Boxes before
Plasma started, but Plasma froze when exiting full screen mode with some of the
same spice-vdagent errors as I reported at
https://bugs.kde.org/show_bug.cgi?id=478019 The problem didn't happen when
using virt-manager QEMU/KVM VMs with the same image and settings. Plasma
5.27.80 had the problem. I don't think this problem happened with Plasma
5.27.9. The problem might've involved how Plasma interacted with spice-vdagent
in GNOME Boxes specifically.

-- 
You are receiving this mail because:
You are watching all bug changes.

[drkonqi] [Bug 478287] drkonqi, kioslave5, and gdb crashed when creating traces of plasmashell crashes

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478287

--- Comment #7 from Matt Fagnani  ---
/usr/lib/systemd/user/plasma-plasmashell.service had TimeoutSec=40sec. So when
drkonqi was still creating the trace of plasmashell 40 s after plasmashell
crashed, systemd aborted plasma-plasmashell.service's processes plasmashell,
drkonqi, kioslave5, gdb. Fedora processes use the drop-in configuration file
/usr/lib/systemd/user/service.d/10-timeout-abort.conf which had
TimeoutStopFailureMode=abort which makes processes abort when timing out to
generated core dumps
https://fedoraproject.org/wiki/Changes/Shorter_Shutdown_Timer I changed the
timeout to TimeoutSec=120sec, logged out and logged in. I reproduced the
plasmashell crash, and the trace completed after about 40 s. drkonqi,
plasmashell, and kioslave5 were aborted after 120 s. The default timeout of 40
s for plasma-plasmashell.service wasn't long enough to trace plasmashell and
report the crash.

-- 
You are receiving this mail because:
You are watching all bug changes.

[drkonqi] [Bug 478287] drkonqi, kioslave5, and gdb crashed when creating traces of plasmashell crashes

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478287

--- Comment #6 from Matt Fagnani  ---
There are systemd service watchdog timeouts which default to 45 s like
DefaultTimeoutStopSec=45s in man systemd-user.conf. The drkonqi and gdb aborts
did usually happen about 45 s after the plasmashell crashes  This timeout might
explain the plasma-plasmashell.service: State 'stop-sigterm' timed out.
Aborting. and the plasmashell, drkonqi, kioslave5, gdb crashes that resulted. I
tried to increase the timeout in /etc/systemd/user.conf to
DefaultTimeoutStopSec=120s and rebooted. I couldn't reproduce the plasmashell
crash when that happened, but I can try it again.

I reproduced the plasmashell crash before that and ran gdb -p $(pidof drkonqi)
from Konsole then tried to create a trace of plasmashell. The trace of drkonqi
when it aborted appeared to have all of its threads waiting.

Thread 1 "drkonqi" received signal SIGABRT, Aborted.
0x7facae321bcd in __GI___poll (fds=0x559976bad470, nfds=4, timeout=53546)
at ../sysdeps/unix/sysv/linux/poll.c:29
29return SYSCALL_CANCEL (poll, fds, nfds, timeout);

(gdb) thread apply all bt

Thread 16 (Thread 0x7fac59e296c0 (LWP 14297) "drkonqi:sh1"):
#0  0x7facae2a5169 in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55997610d764) at
futex-internal.c:57
#1  __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55997610d764,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2  0x7facae2a51ef in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x55997610d764, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3  0x7facae2a7b09 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=, cond=0x55997610d738) at pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x55997610d738, mutex=) at
pthread_cond_wait.c:618
#5  0x7fac8db6abfd in cnd_wait (cond=, mtx=)
at ../src/c11/impl/threads_posix.c:135
#6  0x7fac8db1962b in util_queue_thread_func
(input=input@entry=0x7fac5005e990) at ../src/util/u_queue.c:290
#7  0x7fac8db6ab2c in impl_thrd_routine (p=) at
../src/c11/impl/threads_posix.c:67
#8  0x7facae2a8897 in start_thread (arg=) at
pthread_create.c:444
#9  0x7facae32f6fc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 15 (Thread 0x7fac5aa616c0 (LWP 14296) "QSGRenderThread"):
#0  0x7facae2a5169 in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x559976053424) at
futex-internal.c:57
--Type  for more, q to quit, c to continue without paging--c
#1  __futex_abstimed_wait_common (futex_word=futex_word@entry=0x559976053424,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2  0x7facae2a51ef in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x559976053424, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3  0x7facae2a7b09 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=, cond=0x5599760533f8) at pthread_cond_wait.c:503
#4  ___pthread_cond_wait (cond=0x5599760533f8, mutex=) at
pthread_cond_wait.c:618
#5  0x7facae8fb877 in QWaitConditionPrivate::wait (deadline=...,
this=0x5599760533d0) at thread/qwaitcondition_unix.cpp:146
#6  QWaitCondition::wait (this=this@entry=0x7fac9800df58,
mutex=mutex@entry=0x7fac9800df50, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#7  0x7fac97a4b67a in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x7fac9800df48) at scenegraph/qsgthreadedrenderloop.cpp:257
#8  QSGRenderThread::processEventsAndWaitForMore
(this=this@entry=0x7fac9800deb0) at scenegraph/qsgthreadedrenderloop.cpp:935
#9  0x7fac97a4dbcd in QSGRenderThread::run (this=0x7fac9800deb0) at
scenegraph/qsgthreadedrenderloop.cpp:1052
#10 0x7facae8f5bbd in operator() (__closure=) at
thread/qthread_unix.cpp:350
#11 (anonymous
namespace)::terminate_on_exception >
(t=) at thread/qthread_unix.cpp:287
#12 QThreadPrivate::start (arg=0x7fac9800deb0) at thread/qthread_unix.cpp:310
#13 0x7facae2a8897 in start_thread (arg=) at
pthread_create.c:444
#14 0x7facae32f6fc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 14 (Thread 0x7fac5b2626c0 (LWP 14295) "drkonqi:gl0"):
#0  0x7facae2a5169 in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x5599769992d8) at
futex-internal.c:57
#1  __futex_abstimed_wait_common (futex_word=futex_word@entry=0x5599769992d8,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=c

[drkonqi] [Bug 478287] drkonqi, kioslave5, and gdb crashed when creating traces of plasmashell crashes

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478287

--- Comment #4 from Matt Fagnani  ---
(In reply to Harald Sitter from comment #3)
> You haven't posted a drkonqi backtrace though?

There wasn't a drkonqi trace for the crash when creating the plasmashell trace
because drkonqi crashed the second time when creating the drkonqi trace as I
reported in "Another drkonqi window appeared for the drkonqi trace. I pressed
Developer Information again in drkonqi. drkonqi crashed again." After
reproducing the problem again twice, I think the trace involving File
"/usr/share/drkonqi/gdb/preamble.py", line 518, in qml_trace_frame at the end
of the summary section on my report was from the second drkonqi crash when
creating the trace of the previous drkonqi crash. The following similar trace
only appeared in the journal after I selected Developer Information in drkonqi
to create the trace for the first drkonqi crash, but not when I didn't try to
create the trace of the first drkonqi crash at a different time going through
the reproduction steps.

Dec 09 21:24:47 plasmashell[6584]: Traceback (most recent call last):
Dec 09 21:24:47 plasmashell[6584]:   File "", line 1, in 
Dec 09 21:24:47 plasmashell[6584]:   File "/usr/share/drkonqi/gdb/preamble.py",
line 620, in print_preamble
Dec 09 21:24:47 plasmashell[6584]: print_qml_trace()
Dec 09 21:24:47 plasmashell[6584]:   File "/usr/share/drkonqi/gdb/preamble.py",
line 578, in print_qml_trace
Dec 09 21:24:47 plasmashell[6584]: ret = qml_trace_frame(frame)
Dec 09 21:24:47 plasmashell[6584]:   ^^
Dec 09 21:24:47 plasmashell[6584]:   File "/usr/share/drkonqi/gdb/preamble.py",
line 510, in qml_trace_frame
Dec 09 21:24:47 plasmashell[6584]: value = symbol.value(frame)
Dec 09 21:24:47 plasmashell[6584]: ^^^
Dec 09 21:24:47 plasmashell[6584]: KeyboardInterrupt
Dec 09 21:24:47 plasmashell[6584]: /tmp/drkonqi.qnFYEn:3: Error in sourced
command file:
Dec 09 21:24:47 plasmashell[6584]: Error while executing Python code.
Dec 09 21:24:47 systemd[3541]: plasma-plasmashell.service: Failed with result
'timeout'.
Dec 09 21:24:47 systemd[3541]: plasma-plasmashell.service: Consumed 1min
58.780s CPU time.
Dec 09 21:24:47 systemd[3541]: plasma-plasmashell.service: Scheduled restart
job, restart counter is at 3.
Dec 09 21:24:47 systemd[3541]: Starting plasma-plasmashell.service - KDE Plasma
Workspace...

The creation of the trace for the plasmashell crash took 20-40 seconds and
appeared to get SIGTERM sent to plasma-plasmashell.service which timed out
instead of terminating and resulted in SIGABRT being sent to plasmashell,
drkonqi, kioslave5, and gdb. I don't know what specifically during the
plasmashell trace creation resulted in the SIGTERM being sent to
plasma-plasmashell.service. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[drkonqi] [Bug 478287] drkonqi, kioslave5, and gdb crashed when creating traces of plasmashell crashes

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478287

Matt Fagnani  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #2 from Matt Fagnani  ---
(In reply to Harald Sitter from comment #1)
> I am not quite following. If gdb crashes drkonqi cannot possibly present a
> backtrace. Your expected result can just not happen, can it?

I expected that drkonqi wouldn't have crashed when creating a trace for the
plasmashell crash, which I didn't write but was implied, and then that drkonqi
would have shown the trace. plasma-plasmashell.service appeared to time out
when responding to SIGTERM in the journal message I included
"plasma-plasmashell.service: State 'stop-sigterm' timed out. Aborting"; that
message seemed to happen when drkonqi was creating the plasmashell trace which
usually was ongoing for at least 20 seconds when the crashes happened.
plasmashell, drkonqi, kioslave5, and gdb were aborted right after that based on
the plasma-plasmashell.service timeout. I'm unsure if that happened for all
such crashes, but it might explain the crashes I saw at least in part. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[drkonqi] [Bug 478287] New: drkonqi, kioslave5, and gdb crashed when creating traces of plasmashell crashes

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478287

Bug ID: 478287
   Summary: drkonqi, kioslave5, and gdb crashed when creating
traces of plasmashell crashes
Classification: Applications
   Product: drkonqi
   Version: 5.27.9
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: ---

Created attachment 164029
  --> https://bugs.kde.org/attachment.cgi?id=164029=edit
Journal for the drkonqi, kioslave, gdb crashes when creating a plasmashell
crash trace

SUMMARY

I was using Firefox 122.0a1 (2023-11-30) on Wayland in Plasma 5.27.9 in a
Fedora 39 KDE Plasma installation. I logged into my Instagram account in
Firefox. I played various Instagram stories. As one Instagram story video ended
and another began, plasmashell crashed. drkonqi appeared for reporting the
plasmashell crash. I pressed Developer Information in drkonqi. drkonqi crashed
while gdb from gdb-headless-13.2-11.fc39 was creating a trace. Another drkonqi
window appeared for the drkonqi trace. I pressed Developer Information again in
drkonqi. drkonqi crashed again. An abrt notification was shown. A gdb crash was
shown in abrt and coredumpctl. gdb aborted in iter_match_first_hashed in frame
5 at ../../gdb/dictionary.c:586. There were errors in reading the name variable
at that line like m_demangled_name = 

Core was generated by `/usr/bin/gdb -nw -n -batch -x /tmp/drkonqi.QVBqyR -x
/tmp/drkonqi.JalXhn -p 224'.
Program terminated with signal SIGABRT, Aborted.
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, 
no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7f2f20913080 (LWP 31417))]

(gdb) bt
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, 
no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x7f2f1faa78a3 in __pthread_kill_internal (signo=6, threadid=)
at pthread_kill.c:78
#2  0x7f2f1fa558ee in __GI_raise (sig=6) at ../sysdeps/posix/raise.c:26
#3  0x55dc80b80aca in handle_fatal_signal (sig=6) at
../../gdb/event-top.c:985
#4  
#5  0x55dc80ae97e7 in iter_match_first_hashed (dict=0x55dca15bb2a0,
name=..., 
iterator=0x7ffe3d29d858) at ../../gdb/dictionary.c:586
#6  0x55dc80ae9edf in dict_iter_match_first (iterator=0x7ffe3d29d858,
name=..., 
dict=) at ../../gdb/dictionary.c:490
#7  mdict_iter_match_first (mdict=0x55dca15bb280, name=...,
miterator=miterator@entry=0x7ffe3d29d850)
at ../../gdb/dictionary.c:1229
#8  0x55dc80a13c31 in block_iter_match_step (first=,
name=..., 
iterator=) at ../../gdb/block.c:615
#9  block_iter_match_step (iterator=0x7ffe3d29d840, name=..., first=)
at ../../gdb/block.c:594
#10 0x55dc80a14e28 in block_iter_match_first (iterator=0x7ffe3d29d840,
name=..., 
block=0x55dcb2eeefb0) at ../../gdb/block.c:645
#11 block_find_symbol (block=0x55dcb2eeefb0, name=name@entry=0x55dca24eda70
"QObject", 
domain=domain@entry=STRUCT_DOMAIN, 
matcher=matcher@entry=0x55dc80a15050 , 
data=data@entry=0x0) at ../../gdb/block.c:842
--Type  for more, q to quit, c to continue without paging--c
#12 0x55dc80e363d8 in basic_lookup_transparent_type_1 (objfile=, 
block_index=block_index@entry=STATIC_BLOCK, name=name@entry=0x55dca24eda70
"QObject")
at ../../gdb/symtab.c:2720
#13 0x55dc80e3a53b in basic_lookup_transparent_type (name=0x55dca24eda70
"QObject")
at ../../gdb/symtab.c:2771
#14 basic_lookup_transparent_type (name=0x55dca24eda70 "QObject") at
../../gdb/symtab.c:2739
#15 0x55dc80bbad9d in check_typedef (type=) at
../../gdb/gdbtypes.c:3096
#16 0x55dc80d3581d in type_to_type_object (type=0x55dca253c9b0)
at ../../gdb/python/py-type.c:1389
#17 0x7f2f20110bef in _PyEval_EvalFrameDefault.cold () from
/lib64/libpython3.12.so.1.0
#18 0x7f2f20287876 in PyEval_EvalCode () from /lib64/libpython3.12.so.1.0
#19 0x7f2f202aad9a in run_eval_code_obj () from /lib64/libpython3.12.so.1.0
#20 0x7f2f202a5ebe in run_mod () from /lib64/libpython3.12.so.1.0
#21 0x7f2f202980f6 in PyRun_StringFlags () from /lib64/libpython3.12.so.1.0
#22 0x7f2f20297bb4 in PyRun_SimpleStringFlags () from
/lib64/libpython3.12.so.1.0
#23 0x55dc80d4406a in python_command (arg=,
from_tty=)
at ../../gdb/python/python.c:451
#24 0x55dc80a7f185 in cmd_func (cmd=, args=, 
from_tty=) at ../../gdb/cli/cli-decode.c:2543
#25 0x55dc80e81fd5 in execute_command (p=, 
p@entry=0x55dc9a55ed60 "py print_preamble()", from_tty=) at
../../gdb/top.c:690
#26 0x55dc80b8131f in command_handler (command=0x55dc9a55ed60 "py
print_preamble()")
at ../../gdb/event-top.c:619
#27 0x55dc80e80b9d in read_command_file
(stream=stream@entry=0x55dc9a838ee0)
at 

[plasmashell] [Bug 478086] plasmashell crashed sometimes in QtWaylandClient::QWaylandWindow::createDecoration when hovering over task manager icons

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478086

Matt Fagnani  changed:

   What|Removed |Added

Summary|plasmashell crashed |plasmashell crashed
   |sometimes in|sometimes in
   |QWaitCondition::wait when   |QtWaylandClient::QWaylandWi
   |hovering over task manager  |ndow::createDecoration when
   |icons   |hovering over task manager
   ||icons
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #3 from Matt Fagnani  ---
(In reply to Nate Graham from comment #2)
> Does the issue reproduce if you uncheck "Show small preview windows when
> hovering over Tasks" in the Task Manager widget's settings window and then
> do the same thing to cause the crash to happen?

I unchecked "Show small preview windows when hovering over Tasks" in the Task
Manager widget's settings window. I tried to reproduce the crash as in comment
1 for several minutes, but plasmashell didn't crash. The 5 crashes like this in
Plasma 5.90.0 took from 1 second to 2 minutes to happen, so the problem might
not happen with the preview windows disabled. I checked "Show small preview
windows when hovering over Tasks" in the Task Manager widget's settings window.
I reproduced the crash after about 1 minute of moving the cursor as before. I
think that the problem is actually in thread 73 instead of thread 1 as in the
trace I put in comment. drkonqi focused on thread 1, but it was just
waiting/polling. Both thread 73 and thread 1 had [KCrash Handler] at the top in
drkonqi. Using coredumpctl gdb, the trace of thread 73 was the following.

(gdb) thread 73
[Switching to thread 73 (Thread 0x7f369df6f6c0 (LWP 3082))]
#0  0x7f375d51841d in __GI___poll (fds=fds@entry=0x7f369df6d768,
nfds=nfds@entry=1, timeout=timeout@entry=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
Downloading source file
/usr/src/debug/glibc-2.38.9000-26.fc40.x86_64/io/../sysdeps/unix/sysv/linux/poll.c
29return SYSCALL_CANCEL (poll, fds, nfds, timeout);
(gdb) bt
#0  0x7f375d51841d in __GI___poll (fds=fds@entry=0x7f369df6d768,
nfds=nfds@entry=1, timeout=timeout@entry=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f37607feb98 in poll (__timeout=1000, __nfds=1, __fds=0x7f369df6d768)
at /usr/include/bits/poll2.h:39
#2  pollDrKonqiSocket (sockfd=3, pid=) at
/usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:844
#3  KCrash::startProcess (argv=argv@entry=0x7f369df6d8a8,
waitAndExit=waitAndExit@entry=true, argc=)
at /usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:706
#4  0x7f37607ff659 in KCrash::defaultCrashHandler (sig=11) at
/usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:602
#5  
#6  0x7f375dec0a40 in typeinfo name for QObjectCleanupHandler () from
/lib64/libQt6Core.so.6
#7  0x7f37604f3f5a in QtWaylandClient::QWaylandWindow::createDecoration
(this=0x564f65c87540)
at
/usr/src/debug/qt6-qtwayland-6.6.1-1.fc40.x86_64/src/client/qwaylandwindow.cpp:1034
#8  0x7f37588e199c in QtWaylandClient::QWaylandGLContext::makeCurrent
(this=this@entry=0x7f3710002490, surface=)
at
/usr/src/debug/qt6-qtwayland-6.6.1-1.fc40.x86_64/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:315
#9  0x7f375e79c188 in QOpenGLContext::makeCurrent (this=0x7f37100021e0,
surface=surface@entry=0x564f65d371f0)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/gui/kernel/qopenglcontext.cpp:661
#10 0x7f375e7b48e9 in QRhiGles2::ensureContext (this=0x7f3710001b70,
surface=0x564f65d371f0)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/gui/rhi/qrhigles2.cpp:619
#11 0x7f375e7c071e in QRhiGles2::beginFrame (this=0x7f3710001b70,
swapChain=0x7f37101c8ea0)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/gui/rhi/qrhigles2.cpp:2028
#12 0x7f375e644bea in QRhi::beginFrame (this=0x7f3710001b50,
swapChain=0x7f37101c8ea0, flags=..., flags@entry=...)
at /usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/gui/rhi/qrhi.cpp:10146
#13 0x7f375f8c29f4 in QSGRenderThread::syncAndRender
(this=this@entry=0x564f66f2b500) at /usr/include/qt6/QtCore/qflags.h:73
#14 0x7f375f8c5e93 in QSGRenderThread::run (this=0x564f66f2b500)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:946
#15 0x7f375dd50ace in operator() (__closure=) at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:324
#16 (anonymous
namespace)::terminate_on_exception >
(t=...)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:260
#17 QThreadPrivate::start (arg=0x564f66f2b500) at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/s

[plasmashell] [Bug 478067] The window previews for task manager icons were inverted when using the llvmpipe driver

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478067

--- Comment #4 from Matt Fagnani  ---
(In reply to Nate Graham from comment #3)
> So it's a recurrence of Bug 466299? Or something else?

This is a different problem from Bug 466299 which had window previews that were
right side up but with the wrong colours. In the current problem, the window
previews are upside down with the correct colours. The problem might be in
kpipewire or kwin. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[drkonqi] [Bug 466919] DrKonqi crashed while submitting

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=466919

--- Comment #2 from Matt Fagnani  ---
Created attachment 163891
  --> https://bugs.kde.org/attachment.cgi?id=163891=edit
Trace of all threads of drkonqi crash

-- 
You are receiving this mail because:
You are watching all bug changes.

[drkonqi] [Bug 466919] DrKonqi crashed while submitting

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=466919

Matt Fagnani  changed:

   What|Removed |Added

 CC||matt.fagn...@bell.net

--- Comment #1 from Matt Fagnani  ---
I booted the Fedora Rawhide/40 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20231204.n.0.iso on bare metal. I started
Konsole in Plasma 5.90.0 on Wayland. I ran WAYLAND_DEBUG=1 plasmashell
--replace. To troubleshoot the plasmashell crashes at
https://bugs.kde.org/show_bug.cgi?id=478086 I started Dolphin I quickly moved
the cursor over the Konsole icon in the task manager to the icons to its left
(Firefox, Dolphin, Discover, System Settings). plasmashell crashed when I did
that and the panel disappeared and reappeared automatically a few seconds
later. drkonqi appeared. I selected Developer information, and created a trace.
I tried to report through bugs.kde.org through drkonqi, but drkonqi crashed at
the point that a list of possible duplicate reports was shown and I clicked on
one of the reports.

The crashing thread 7 had a segmentation fault with a trace like that in this
report.

Thread 7 (Thread 0x7f95e51d86c0 (LWP 5730)):
#0  0x7f969b11b41d in __GI___poll (fds=fds@entry=0x7f95e51d6568,
nfds=nfds@entry=1, timeout=timeout@entry=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f969dea1b98 in poll (__timeout=1000, __nfds=1, __fds=0x7f95e51d6568)
at /usr/include/bits/poll2.h:39
#2  pollDrKonqiSocket (sockfd=3, pid=) at
/usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:844
#3  KCrash::startProcess (argv=argv@entry=0x7f95e51d66a8,
waitAndExit=waitAndExit@entry=true, argc=) at
/usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:706
#4  0x7f969dea2659 in KCrash::defaultCrashHandler (sig=11) at
/usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:602
#5  
#6  pcre2_match_data_create_from_pattern_16 (code=0x0, gcontext=0x0) at
src/pcre2_match_data.c:87
#7  0x7f969b9836aa in QRegularExpressionPrivate::doMatch
(this=0x7f95e80011e0, priv=priv@entry=0x7f9620002a50, offset=,
checkSubjectStringOption=checkSubjectStringOption@entry=QRegularExpressionPrivate::CheckSubjectString,
previous=previous@entry=0x0) at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/text/qregularexpression.cpp:1146
#8  0x7f969b983e0e in QRegularExpression::match
(this=this@entry=0x55fdaea8e1d0 ,
subject=..., offset=offset@entry=0,
matchType=matchType@entry=QRegularExpression::NormalMatch, matchOptions=...,
matchOptions@entry=...) at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/text/qregularexpression.cpp:1597
#9  0x55fdaea29b4b in BacktraceLineGdb::parse
(this=this@entry=0x7f95e51d7410) at
/usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/parser/backtraceparsergdb.cpp:119
#10 0x55fdaea2af00 in BacktraceLineGdb::BacktraceLineGdb (this=, lineStr=..., this=, lineStr=...) at
/usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/parser/backtraceparsergdb.cpp:22
#11 0x55fdaea2b180 in BacktraceParserGdb::parseLine (lineStr=...,
this=) at
/usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/parser/backtraceparsergdb.cpp:200
#12 BacktraceParserGdb::newLine (this=, lineStr=...) at
/usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/parser/backtraceparsergdb.cpp:191
#13 0x7f969b8027a8 in doActivate (sender=0x7f95e51d7660,
signal_index=4, argv=0x7f95e51d76b0) at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:4033
#14 0x7f969b7f8807 in QMetaObject::activate
(sender=sender@entry=0x7f95e51d7660, m=m@entry=0x55fdaea86900
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7f95e51d76b0)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:4081
#15 0x55fdaea19d9e in ParseBugBacktraces::newLine (_t1=...,
this=0x7f95e51d7660) at
/usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/redhat-linux-build/src/DrKonqiInternal_autogen/include/moc_parsebugbacktraces.cpp:188
#16 ParseBugBacktraces::parse (comment=..., this=0x7f95e51d7660) at
/usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/bugzillaintegration/parsebugbacktraces.cpp:126
#17 ParseBugBacktraces::parse (this=0x7f95e51d7660) at
/usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/bugzillaintegration/parsebugbacktraces.cpp:113
#18 operator() (__closure=0x7f95e51d7630) at
/usr/src/debug/plasma-drkonqi-5.90.0-1.fc40.x86_64/src/bugzillaintegration/duplicatefinderjob.cpp:108
#19 std::__invoke_impl
>&, QObject*)::&> (__f=...) at /usr/include/c++/13/bits/invoke.h:61
#20 std::__invoke >&, QObject*)::&> (__fn=...) at
/usr/include/c++/13/bits/invoke.h:96
#21 std::invoke >&, QObject*)::&> (__fn=...) at
/usr/include/c++/13/functional:113
#22 operator() (function=..., __closure=) at
/usr/include/qt6/QtConcurrent/qtconcurrentstoredfunctioncall.h:116
#23 std::__invoke_impl >

[plasmashell] [Bug 478067] The window previews for task manager icons were inverted when using the llvmpipe driver

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478067

Matt Fagnani  changed:

   What|Removed |Added

Summary|The window previews for |The window previews for
   |task manager icons were |task manager icons were
   |inverted in VMs using the   |inverted when using the
   |llvmpipe driver |llvmpipe driver

--- Comment #2 from Matt Fagnani  ---
When I booted that image in basic graphics mode which used nomodeset on the
kernel command line and the llvmpipe driver on bare metal, the problem
appeared. When booting the image normally on bare metal using the radeonsi mesa
driver and amdgpu kernel driver, the problem didn't appear.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478086] plasmashell crashed sometimes in QWaitCondition::wait when hovering over task manager icons

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478086

--- Comment #1 from Matt Fagnani  ---
I reproduced the crash by moving the cursor quickly between the Dolphin and
Konsole icons which were both running. Here is the trace from coredumpctl gdb.

Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
Downloading source file
/usr/src/debug/glibc-2.38.9000-26.fc40.x86_64/nptl/pthread_kill.c
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;  
[Current thread is 1 (Thread 0x7f4b7c44e680 (LWP 1979))]
(gdb) bt
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x7f4b794abc23 in __pthread_kill_internal (signo=11,
threadid=) at pthread_kill.c:78
#2  0x7f4b794598ee in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3  0x7f4b7c80b6cb in KCrash::defaultCrashHandler (sig=11) at
/usr/src/debug/kf6-kcrash-5.246.0-1.fc40.x86_64/src/kcrash.cpp:612
#4  
#5  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x7f4b794abc23 in __pthread_kill_internal (signo=11,
threadid=) at pthread_kill.c:78
#7  0x7f4b794598ee in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#8  
#9  0x7f4b794a6407 in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x558c53c52fb0) at
futex-internal.c:57
#10 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x558c53c52fb0,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, 
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#11 0x7f4b794a648f in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x558c53c52fb0, expected=expected@entry=0,
clockid=clockid@entry=0, 
abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139
#12 0x7f4b794a8da9 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=, cond=0x558c53c52f88) at pthread_cond_wait.c:503
#13 ___pthread_cond_wait (cond=0x558c53c52f88, mutex=) at
pthread_cond_wait.c:618
#14 0x7f4b79d596eb in QWaitConditionPrivate::wait (deadline=...,
this=0x558c53c52f60)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/thread/qwaitcondition_unix.cpp:103
#15 QWaitCondition::wait (this=, mutex=0x558c54e0e408,
deadline=...)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/thread/qwaitcondition_unix.cpp:181
#16 0x7f4b7b8c3a87 in QSGThreadedRenderLoop::handleObscurity
(this=this@entry=0x558c53a21d40, w=0x558c555cd020)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1334
#17 0x7f4b7b8c47bd in QSGThreadedRenderLoop::handleObscurity (w=, this=0x558c53a21d40)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1323
#18 QSGThreadedRenderLoop::hide (this=0x558c53a21d40, window=0x558c55a70b70)
at
/usr/src/debug/qt6-qtdeclarative-6.6.1-1.fc40.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1124
#19 0x7f4b7a4661d8 in QWindow::event (this=0x558c55a70b70,
ev=0x7ffd4cb10390) at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/gui/kernel/qwindow.cpp:2576
#20 0x7f4b7bdc3168 in QApplicationPrivate::notify_helper (this=, receiver=0x558c55a70b70, e=0x7ffd4cb10390)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/widgets/kernel/qapplication.cpp:3296
#21 0x7f4b79ba0e08 in QCoreApplication::notifyInternal2
(receiver=0x558c55a70b70, event=0x7ffd4cb10390)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1121
#22 0x7f4b79ba100d in QCoreApplication::sendEvent (receiver=, event=)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:1539
--Type  for more, q to quit, c to continue without paging--c
#23 0x7f4b7a4638b1 in QWindowPrivate::setVisible (visible=false,
this=)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/gui/kernel/qwindow.cpp:415
#24 QWindow::setVisible (this=, visible=false) at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/gui/kernel/qwindow.cpp:681
#25 0x7f4b79c02221 in QtPrivate::QSlotObjectBase::call (a=0x7ffd4cb104d0,
r=0x558c55a70b70, this=0x558c55b14360)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobjectdefs_impl.h:433
#26 doActivate (sender=0x558c55b14380, signal_index=3,
argv=0x7ffd4cb104d0)
at
/usr/src/debug/qt6-qtbase-6.6.1-1.fc40.x86_64/src/corelib/kernel/qobject.cpp:4021
#27 0x7f4b79bf8807 in QMetaObject::activate (sender=,
m=m@entry=0x7f4b7a06df20, local_signal_index=local_signal_index@entry=0, 
argv=argv@entry=0x7ffd4cb104d0) at
/usr/src/debug/qt6

[plasmashell] [Bug 478086] plasmashell crashed sometimes in QWaitCondition::wait when hovering over task manager icons

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478086

Matt Fagnani  changed:

   What|Removed |Added

   Keywords||qt6

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478086] New: plasmashell crashed sometimes in QWaitCondition::wait when hovering over task manager icons

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478086

Bug ID: 478086
   Summary: plasmashell crashed sometimes in QWaitCondition::wait
when hovering over task manager icons
Classification: Plasma
   Product: plasmashell
   Version: 5.90.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: 1.0

SUMMARY

I booted the Fedora Rawhide/40 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20231204.n.0.iso on bare metal. I started
Konsole in Plasma 5.90.0 on Wayland. I ran some Fedora kernel tests in Konsole.
I quickly moved the cursor over the Konsole icon in the task manager to the
icons to its left (Firefox, Dolphin, Discover, System Settings). plasmashell
crashed when I did that and the panel disappeared and reappeared automatically
a few seconds later. drkonqi appeared. I selected Developer information,
installed debuginfo rpms for qt6-qtbase(-gui) glibc glib2, and created a trace.
I tried to report through bugs.kde.org through drkonqi, but drkonqi crashed at
the point that a list of possible duplicate reports was shown. The trace from
coredumpctl info is as follows. The core dump was removed probably due to space
limitations from the drkonqi crash.
The crash was a segmentation fault involving QWaitCondition::wait in qt6-qtbase
6.6.1.

Stack trace of thread 2028:
#0  0x7f2f35ea8bb4 __pthread_kill_implementation (libc.so.6
+ 0x90bb4)
#1  0x7f2f35e568ee raise (libc.so.6 + 0x3e8ee)
#2  0x7f2f391a06cb _ZN6KCrash19defaultCrashHandlerEi
(libKF6Crash.so.6 + 0x86cb)
#3  0x7f2f35e569a0 __restore_rt (libc.so.6 + 0x3e9a0)
#4  0x7f2f35ea8bb4 __pthread_kill_implementation (libc.so.6
+ 0x90bb4)
#5  0x7f2f35e568ee raise (libc.so.6 + 0x3e8ee)
#6  0x7f2f35e569a0 __restore_rt (libc.so.6 + 0x3e9a0)
#7  0x7f2f35ea3407 __futex_abstimed_wait_common (libc.so.6
+ 0x8b407)
#8  0x7f2f35ea5da9 pthread_cond_wait@@GLIBC_2.3.2
(libc.so.6 + 0x8dda9)
#9  0x7f2f367596eb
_ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x3596eb)
#10 0x7f2f382c3a87
_ZN21QSGThreadedRenderLoop15handleObscurityEPNS_6WindowE.part.0
(libQt6Quick.so.6 + 0x4c3a87)
#11 0x7f2f382c47bd
_ZN21QSGThreadedRenderLoop4hideEP12QQuickWindow (libQt6Quick.so.6 + 0x4c47bd)
#12 0x7f2f36e661d8 _ZN7QWindow5eventEP6QEvent
(libQt6Gui.so.6 + 0x2661d8)
#13 0x7f2f387c3168
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 +
0x1c3168)
#14 0x7f2f365a0e08
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 +
0x1a0e08)
#15 0x7f2f36e638b1 _ZN7QWindow10setVisibleEb
(libQt6Gui.so.6 + 0x2638b1)
#16 0x7f2f36602221 _Z10doActivateILb0EEvP7QObjectiPPv
(libQt6Core.so.6 + 0x202221)
#17 0x7f2f366113dd _ZN6QTimer7timeoutENS_14QPrivateSignalE
(libQt6Core.so.6 + 0x2113dd)
#18 0x7f2f365f379f _ZN7QObject5eventEP6QEvent
(libQt6Core.so.6 + 0x1f379f)
#19 0x7f2f387c3168
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 +
0x1c3168)
#20 0x7f2f365a0e08
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 +
0x1a0e08)
#21 0x7f2f3674ef8b _ZN14QTimerInfoList14activateTimersEv
(libQt6Core.so.6 + 0x34ef8b)
#22 0x7f2f3686d099
_ZL19timerSourceDispatchP8_GSourcePFiPvES1_ (libQt6Core.so.6 + 0x46d099)
#23 0x7f2f351cbe5c
g_main_context_dispatch_unlocked.lto_priv.0 (libglib-2.0.so.0 + 0x5be5c)
#24 0x7f2f35226dd8 g_main_context_iterate_unlocked.isra.0
(libglib-2.0.so.0 + 0xb6dd8)
#25 0x7f2f351c9ad3 g_main_context_iteration
(libglib-2.0.so.0 + 0x59ad3)
#26 0x7f2f3686d39f
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt6Core.so.6 + 0x46d39f)
#27 0x7f2f365adbcb
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 +
0x1adbcb)
#28 0x7f2f365a99cd _ZN16QCoreApplication4execEv
(libQt6Core.so.6 + 0x1a99cd)
#29 0x55ab82732e52 main (plasmashell + 0x35e52)
#30 0x7f2f35e4014a __libc_start_call_main (libc.so.6 +
0x2814a)
#31 0x7f2f35e4020b __libc_start_main@@GLIBC_2.34 (libc.so.6
+ 0x2820b)
#32 0x55ab827335a5 _start (plasmashell + 0x365a5)

Stack trace of thread 2046:
#0  0x7f2f35ea3409 

[plasmashell] [Bug 478067] The window previews for task manager icons were inverted in VMs using the llvmpipe driver

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478067

--- Comment #1 from Matt Fagnani  ---
Created attachment 163862
  --> https://bugs.kde.org/attachment.cgi?id=163862=edit
Recording of inverted window previews for Firefox and Dolphin in GNOME Boxes
QEMU/KVM VM with 3D acceleration disabled using llvmpipe

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478067] New: The window previews for task manager icons were inverted in VMs using the llvmpipe driver

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478067

Bug ID: 478067
   Summary: The window previews for task manager icons were
inverted in VMs using the llvmpipe driver
Classification: Plasma
   Product: plasmashell
   Version: 5.90.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
CC: qydwhotm...@gmail.com
  Target Milestone: 1.0

Created attachment 163859
  --> https://bugs.kde.org/attachment.cgi?id=163859=edit
Journal for a boot in which the inverted window previews were shown

SUMMARY

I booted the Fedora Rawhide/40 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20231204.n.0.iso in GNOME Boxes QEMU/KVM VMs
with 3D acceleration disabled using the llvmpipe mesa 23.3.0 driver in a Fedora
39 KDE Plasma host. To work around the VM getting stuck on the Plasma 5.90.0 on
Wayland splash screen as I reported at
https://bugs.kde.org/show_bug.cgi?id=477643 I changed to VT2 using the keyboard
menu in the top bar of GNOME Boxes and selecting Ctrl+Alt+F2. When I changed
back to VT1, Plasma was shown with the Plasma Welcome program open. I started
Firefox, Dolphin, and System Settings among others from the Task Manager. I
hovered over the icons of those programs in the task manager. The window
previews for those programs were inverted. The following kpipewire errors were
shown in the journal when I hovered over the icons.

Dec 04 12:59:43 plasmashell[1858]: kpipewire_logging: Failed to query DMA-BUF
formats.
Dec 04 12:59:49 plasmashell[1858]: kpipewire_logging: Failed to query DMA-BUF
formats.
Dec 04 12:59:53 plasmashell[1858]: kpipewire_logging: Failed to query DMA-BUF
formats.
Dec 04 12:59:53 plasmashell[1858]: kpipewire_logging: PipeWire remote error: 
-2 target not found
Dec 04 12:59:53 plasmashell[1858]: kpipewire_logging: PipeWire remote error: 
-2 unknown resource 3 op:4
Dec 04 12:59:53 plasmashell[1858]: kpipewire_logging: PipeWire remote error: 
-2 unknown resource 3 op:7
Dec 04 12:59:58 plasmashell[1858]: kf.windowsystem: static bool
KX11Extras::hasWId(WId) may only be used on X11
Dec 04 12:59:59 pipewire[1701]: mod.client-node: 0x55a7c3645470: unknown peer
0x55a7c3639010 fd:41
Dec 04 12:59:59 plasmashell[1858]: kpipewire_logging: Failed to query DMA-BUF
formats.
Dec 04 13:00:01 plasmashell[1858]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:
TypeError: Type error
Dec 04 13:00:03 plasmashell[1858]: kf.windowsystem: static bool
KX11Extras::hasWId(WId) may only be used on X11
Dec 04 13:00:04 plasmashell[1858]: kpipewire_logging: Failed to query DMA-BUF
formats.
Dec 04 13:00:14 plasmashell[1858]: kpipewire_logging: PipeWire remote error: 
-2 target not found
Dec 04 13:00:14 plasmashell[1858]: kpipewire_logging: PipeWire remote error: 
-2 unknown resource 4 op:4
Dec 04 13:00:14 plasmashell[1858]: kpipewire_logging: PipeWire remote error: 
-2 unknown resource 4 op:7
Dec 04 13:00:14 plasmashell[1858]: kpipewire_logging: Failed to query DMA-BUF
formats.
Dec 04 13:00:17 plasmashell[1858]: kpipewire_logging: Failed to query DMA-BUF
formats.
Dec 04 13:00:45 kwin_wayland[1689]: This plugin does not support raise()
Dec 04 13:00:56 plasmashell[1858]: kpipewire_logging: Failed to query DMA-BUF
formats.
Dec 04 13:00:56 plasmashell[1858]: kpipewire_logging: Failed to query DMA-BUF
formats.
Dec 04 13:01:01 plasmashell[1858]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:
TypeError: Type error
Dec 04 13:01:03 plasmashell[1858]: kpipewire_logging: Failed to query DMA-BUF
formats.

All programs I tried had window previews which were upside down. The problem
also happened in virt-manager QEMU/KVM VMs with the same image and 3D
acceleration disabled using the llvmpipe driver. Plasma 5.27.80 was also
affected by this problem. I don't think this happened with Plasma 5.27.9. This
problem didn't happen when I booted the same image in GNOME Boxes with 3D
acceleration enabled using the virgl mesa driver. The problem might be specific
to when the llvmpipe driver is used. I'll attach the journal and a recording of
the problem.

STEPS TO REPRODUCE
1. Boot a Fedora 39 KDE Plasma installation updated to 2023-12-3 with
updates-testing enabled
2. Log in to Plasma 5.27.9 on Wayland
3. Start Konsole
4. Install GNOME Boxes if it isn't already with sudo dnf install gnome-boxes
5. Download Fedora-KDE-Live-x86_64-Rawhide-20231204.n.0.iso from
https://koji.fedoraproject.org/koji/buildinfo?buildID=2327615
6. Start GNOME Boxes
7. Boot Fedora-KDE-Live-x86_64-Rawhide-20231204.n.0.iso in a GNOME Boxes
QEMU/KVM VM with 3 GiB RAM, UEFI enabled, and 3D acceleration disabled 
8. To work around https://bugs.kde.org/show_bug.cgi?id=477643, switch to 

[kwin] [Bug 478019] New: Plasma froze after exiting full screen mode in GNOME Boxes QEMU/KVM VMs started in full screen mode

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=478019

Bug ID: 478019
   Summary: Plasma froze after exiting full screen mode in GNOME
Boxes QEMU/KVM VMs started in full screen mode
Classification: Plasma
   Product: kwin
   Version: 5.27.80
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: qt6
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: ---

Created attachment 163834
  --> https://bugs.kde.org/attachment.cgi?id=163834=edit
Journal from a GNOME Boxes VM in which Plasma 5.27.80 froze after exiting full
screen mode

SUMMARY

I booted the Fedora Rawhide/40 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20231202.n.0.iso in GNOME Boxes QEMU/KVM VMs in
a Fedora 39 KDE Plasma host. To work around the VM getting stuck on the Plasma
5.27.80 splash screen as I reported at
https://bugs.kde.org/show_bug.cgi?id=477643 I changed to VT2 using the keyboard
menu in the top bar of GNOME Boxes and selecting Ctrl+Alt+F2. When I changed
back to VT1, Plasma was shown with the Plasma Welcome program open.
I exited full screen mode by selecting the full screen button in the GNOME
Boxes top bar. Plasma froze after exiting full screen mode. I clicked to open
Dolphin and Firefox from the panel and open the Application Launcher menu, but
nothing opened. I clicked to enter full screen mode again and Plasma started
responding again. The programs and menu I clicked on when not in full screen
mode opened.

The journal showed spice-vdagentd errors in which it appeared to be trying to
connect to mutter by dbus which was odd. There were kwin_wayland errors
repeated hundreds of times while Plasma was frozen like  kwin_wayland_drm: Page
flip failed: No space left on device and kwin_wayland_drm: Presentation failed!
No space left on device

Dec 03 20:23:29 spice-vdagent[2047]: vdagent started
Dec 03 20:23:29 systemd[1377]: app-org.kde.kgpg@autostart.service: Skipped due
to 'exec-condition'.
Dec 03 20:23:29 systemd[1377]: Condition check resulted in
app-org.kde.kgpg@autostart.service - KGpg being skipped.
Dec 03 20:23:29 systemd[1377]: Started
app-xdg\x2duser\x2ddirs@autostart.service - User folders update.
Dec 03 20:23:29 systemd[1377]: Started
app-xdg\x2duser\x2ddirs\x2dkde@autostart.service - User folders update.
Dec 03 20:23:29 kconf_update[1878]: kf.config.kconf_update:
/usr/share/kconf_update/style_widgetstyle_default_breeze.upd defined Version=5
but Version=6 was expected
Dec 03 20:23:29 kconf_update[1878]: kf.config.kconf_update:
/usr/share/kconf_update/webengineurlinterceptoradblock.upd defined Version=5
but Version=6 was expected
Dec 03 20:23:29 systemd[1377]: Started xdg-desktop-portal-gtk.service - Portal
service (GTK/GNOME implementation).
Dec 03 20:23:29 systemd[1377]: Started xdg-desktop-portal.service - Portal
service.
Dec 03 20:23:29 spice-vdagent[2047]: display: failed to call GetCurrentState
from mutter over DBUS
Dec 03 20:23:29 spice-vdagent[2047]:error message: Cannot invoke method;
proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an
owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START
flag
Dec 03 20:23:29 systemd[1377]: Reached target xdg-desktop-autostart.target -
Startup of XDG autostart applications.
Dec 03 20:23:29 spice-vdagent[2047]: No guest output map, using output index as
display id
Dec 03 20:23:29 kernel: input: spice vdagent tablet as
/devices/virtual/input/input7
Dec 03 20:23:29 spice-vdagentd[1694]: opening vdagent virtio channel
Dec 03 20:23:29 spice-vdagent[2047]: Received Graphics Device Info:
Dec 03 20:23:29 systemd[1377]: Started
dbus-:1.2-org.freedesktop.Notifications@0.service.
Dec 03 20:23:29 spice-vdagent[2047]: card0 not found while listing DRM devices.
Dec 03 20:23:29 spice-vdagent[2047]: Unable to open file (null)
Dec 03 20:23:29 systemd[1377]: Started
dbus-:1.46-org.a11y.atspi.Registry@0.service.
Dec 03 20:23:29 spice-vdagent[2047]: card0 not found while listing DRM devices.
Dec 03 20:23:29 spice-vdagent[2047]: Unable to open file (null)
Dec 03 20:23:29 spice-vdagent[2047]: channel_id: 0 monitor_id: 0
device_address: pci//01.0, device_display_id: 0 xrandr output ID NOT FOUND
Dec 03 20:23:29 spice-vdagent[2047]: display: failed to call GetCurrentState
from mutter over DBUS
Dec 03 20:23:29 spice-vdagent[2047]:error message: Cannot invoke method;
proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an
owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START
flag
Dec 03 20:23:29 spice-vdagentd[1694]: Set max clipboard: 104857600
Dec 03 20:23:29 spice-vdagent[2047]: No guest output map, using output index as
display id
Dec 03 20:23:29 spice-vdagent[2047]: Received Graphics Device Info:
Dec 03 20:23:29 spice-vdagent[2047]: card0 not found while 

[kwin] [Bug 477643] Plasma 5.27.80 got stuck on the splash screen in VMs with kwin_wayland errors

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=477643

--- Comment #1 from Matt Fagnani  ---
When I selected full-screen mode from the top menu in GNOME Boxes QEMU/KVM VMs
using Plasma 5.27.80 on Wayland with
Fedora-KDE-Live-x86_64-Rawhide-20231127.n.0.iso and
Fedora-KDE-Live-x86_64-Rawhide-20231129.n.0.iso, and then I exited full-screen
mode, Plasma froze. The journal when Plasma froze in this way repeatedly showed
the same errors "kwin_wayland_drm: Page flip failed: No space left on device"
and "kwin_wayland_drm: Presentation failed! No space left on device". When I
selected full-screen mode again, Plasma wasn't frozen any longer and programs I
had clicked on while it was frozen changed or appeared. df showed what appears
to be enough free space on the VM's partitions.

This problem didn't happen when I booted those images in virt-manager QEMU/KVM
VMs with the same settings. In GNOME Boxes QEMU/KVM VMs using Plasma 5.27.9 on
Wayland with Fedora-KDE-Live-x86_64-Rawhide-20231125.n.0.iso and earlier, the
resolution of Plasma appeared to change automatically to fit the window when
Plasma appeared right after the splash screen disappeared. There might be some
problem with the way Plasma 5.27.80's resolution changed in the GNOME Boxes VMs
which didn't happen in virt-manager.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 477643] Plasma 5.27.80 got stuck on the splash screen in VMs with kwin_wayland errors

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=477643

Matt Fagnani  changed:

   What|Removed |Added

   Keywords||qt6

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 477643] New: Plasma 5.27.80 got stuck on the splash screen in VMs with kwin_wayland errors

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=477643

Bug ID: 477643
   Summary: Plasma 5.27.80 got stuck on the splash screen in VMs
with kwin_wayland errors
Classification: Plasma
   Product: kwin
   Version: 5.27.80
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: ---

Created attachment 163555
  --> https://bugs.kde.org/attachment.cgi?id=163555=edit
Journal for a boot when Plasma 5.27.80 got stuck on the splash screen in a VM
using the llvmpipe driver

SUMMARY

I booted the Fedora Rawhide/40 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20231127.n.0.iso in GNOME Boxes QEMU/KVM VMs in
a Fedora 39 KDE Plasma host. Fedora-KDE-Live-x86_64-Rawhide-20231127.n.0.iso is
the first Fedora Rawhide image using Plasma 5.27.80. Plasma 5.27.80 got stuck
on the splash screen which was shown for at least 2 minutes. The cursor was
still movable on the splash screen, and it changed to a hand shape when it was
over the centre of the screen in some places where Plasma Welcome was later
shown. When the VM had 3D acceleration disabled using the llvmpipe mesa
23.3.0-rc2 driver, the spinner on the splash screen spun for a few seconds then
froze. When the VM had 3D acceleration enabled using the virgl mesa driver, the
spinner on the splash screen spun for 2 seconds then disappeared.

I changed to VT2 using the keyboard menu in the top bar of GNOME Boxes and
selecting Ctrl+Alt+F2. When I changed back to VT1, Plasma was shown with the
Plasma Welcome program open. There were some kwin_wayland errors in the journal
when it was starting.

Nov 27 16:54:38 kwin_wayland[1683]: kwin_wayland_drm: Atomic Mode Setting
disabled on GPU /dev/dri/card1 because of cursor offset issues in virtual
machines
Nov 27 16:54:39 kwin_wayland[1683]: kwin_core: Parse error in tiles
configuration for monitor "92e842d7-5928-5c43-884a-4912e7cc82ed" : "illegal
value" Creating default setup
Nov 27 16:54:41 kwin_wayland[1683]: OpenGL vendor string:  
Mesa
Nov 27 16:54:41 kwin_wayland[1683]: OpenGL renderer string:
llvmpipe (LLVM 17.0.4, 256 bits)
Nov 27 16:54:41 kwin_wayland[1683]: OpenGL version string:  4.5
(Core Profile) Mesa 23.3.0-rc2
Nov 27 16:54:41 kwin_wayland[1683]: OpenGL shading language version string:
4.50
Nov 27 16:54:41 kwin_wayland[1683]: Driver:
LLVMpipe
Nov 27 16:54:41 kwin_wayland[1683]: GPU class: 
Unknown
Nov 27 16:54:41 kwin_wayland[1683]: OpenGL version: 4.5
Nov 27 16:54:41 kwin_wayland[1683]: GLSL version:  
4.50
Nov 27 16:54:41 kwin_wayland[1683]: Mesa version:  
23.3
Nov 27 16:54:41 kwin_wayland[1683]: Requires strict binding:no
Nov 27 16:54:41 kwin_wayland[1683]: Virtual Machine:no
Nov 27 16:54:41 kwin_wayland[1683]: Timer query support:yes
Nov 27 16:54:41 kwin_wayland[1683]: kwin_core: Parse error in tiles
configuration for monitor "4d031bd2-ddeb-57b0-97bb-ac4d7cdf2819" : "illegal
value" Creating default setup
Nov 27 16:54:42 kwin_wayland[1683]: kwin_wayland_drm: Setting gamma failed!
Function not implemented
Nov 27 16:54:43 ksplashqml[1691]: libEGL warning: egl: failed to create dri2
screen
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: (WW) Option "-listen" for file
descriptors is deprecated
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: Please use "-listenfd" instead.
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: (WW) Option "-listen" for file
descriptors is deprecated
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: Please use "-listenfd" instead.
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: libEGL warning: egl: failed to
create dri2 screen
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: libEGL warning: egl: failed to
create dri2 screen
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: libEGL warning: NEEDS EXTENSION:
falling back to kms_swrast
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: Refusing to try glamor on llvmpipe
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: EGL setup failed, disabling glamor
Nov 27 16:54:43 kwin_wayland_wrapper[1775]: Failed to initialize glamor,
falling back to sw
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: The XKEYBOARD keymap compiler
(xkbcomp) reports:
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:  Could not
resolve keysym XF86CameraAccessEnable
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:  Could not
resolve keysym XF86CameraAccessDisable
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:  Could not
resolve keysym XF86CameraAccessToggle
Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning:  Could not
resolve keysym XF86NextElement
Nov 27 16:54:43 

[plasmashell] [Bug 477168] New: plasmashell crashed in QObject::parent when playing a video in Firefox

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=477168

Bug ID: 477168
   Summary: plasmashell crashed in QObject::parent when playing a
video in Firefox
Classification: Plasma
   Product: plasmashell
   Version: 5.27.9
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: 1.0

Created attachment 163254
  --> https://bugs.kde.org/attachment.cgi?id=163254=edit
Full trace of all threads of plasmashell crash

SUMMARY

I was using Plasma 5.27.9 on Wayland in a Fedora 39 KDE Plasma installation. I
started Firefox 121.0a1 (2023-11-17) on Wayland. I logged into my Instagram
account. I played various videos in posts and stories. plasmashell crashed
while playing a video in a post. I clicked on the mute button on the video
around the time of the crash though that might've been right after the crash.
The panel disappeared from the bottom of the screen and reappeared
automatically a few seconds later. drkonqi didn't appear. abrt and selinux
notifications appeared. plasmashell crashed in QObject::parent according to
coredumpctl gdb.

Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7ff1f4b63209 in QObject::parent (this=,
this=)
at /usr/include/qt5/QtCore/qscopedpointer.h:116
116 T *operator->() const noexcept
[Current thread is 1 (Thread 0x7ff1f47b9a00 (LWP 29651))]

(gdb) bt
#0  0x7ff1f4b63209 in QObject::parent() const (this=0x55f8b5f92910,
this=)
at /usr/include/qt5/QtCore/qscopedpointer.h:116
#1  Plasma::DataContainer::getDataEngine() (this=this@entry=0x55f8b5f92910)
at
/usr/src/debug/kf5-plasma-5.111.0-1.fc39.x86_64/src/plasma/datacontainer.cpp:202
#2  0x7ff18f1f1fed in
MultiplexedService::activePlayerChanged(PlayerContainer*)
(this=this@entry=0x55f8b785cf80, container=0x55f8b5f92910)
at
/usr/src/debug/plasma-workspace-5.27.9.1-2.fc39.x86_64/dataengines/mpris2/multiplexedservice.cpp:58
#3  0x7ff18f1f91d8 in MultiplexedService::MultiplexedService(Multiplexer*,
QObject*)
(parent=, multiplexer=0x55f8b757d270, this=0x55f8b785cf80)
at
/usr/src/debug/plasma-workspace-5.27.9.1-2.fc39.x86_64/dataengines/mpris2/multiplexedservice.cpp:25
#4  Mpris2Engine::serviceForSource(QString const&) (this=,
source=)
at
/usr/src/debug/plasma-workspace-5.27.9.1-2.fc39.x86_64/dataengines/mpris2/mpris2engine.cpp:40
#5  0x7ff1cfefe130 in Plasma::DataSource::serviceForSource(QString const&)
(source=..., this=0x55f8b51b36a0)
at
/usr/src/debug/kf5-plasma-5.111.0-1.fc39.x86_64/src/declarativeimports/core/datasource.cpp:208
#6  Plasma::DataSource::qt_static_metacall(QObject*, QMetaObject::Call, int,
void**)
(_o=0x55f8b51b36a0, _c=QMetaObject::InvokeMetaMethod, _id=,
_a=)
at
/usr/src/debug/kf5-plasma-5.111.0-1.fc39.x86_64/redhat-linux-build/src/declarativeimports/core/corebindingsplugin_autogen/include/moc_datasource.cpp:201
#7  0x7ff1cfeff922 in Plasma::DataSource::qt_metacall(QMetaObject::Call,
int, void**)
(this=0x55f8b51b36a0, _c=QMetaObject::InvokeMetaMethod, _id=16,
_a=0x7ffcd7984990)
--Type  for more, q to quit, c to continue without paging--c
at
/usr/src/debug/kf5-plasma-5.111.0-1.fc39.x86_64/redhat-linux-build/src/declarativeimports/core/corebindingsplugin_autogen/include/moc_datasource.cpp:370
#8  0x7ff1f3ef532a in QQmlObjectOrGadget::metacall(QMetaObject::Call, int,
void**) const
(this=this@entry=0x7ffcd7984c30,
type=type@entry=QMetaObject::InvokeMetaMethod, index=,
index@entry=21, argv=) at qml/qqmlobjectorgadget.cpp:51
#9  0x7ff1f3dc7e13 in CallMethod
(callType=, callArgs=0x7ffcd7984990, engine=,
argTypes=, argCount=, returnType=,
index=, object=...)
at /usr/include/qt5/QtCore/qvarlengtharray.h:189
#10 CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&,
QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call)
(object=..., data=, engine=engine@entry=0x55f8b48decf0,
callArgs=callArgs@entry=0x7ff1adfbd588,
callType=callType@entry=QMetaObject::InvokeMetaMethod)
at jsruntime/qv4qobjectwrapper.cpp:1553
#11 0x7ff1f3dc9c12 in CallOverloaded
(callType=, propertyCache=,
callArgs=, engine=, data=,
object=) at jsruntime/qv4qobjectwrapper.cpp:1629
#12 QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int)
const
(this=, thisObject=, argv=,
argc=)
at jsruntime/qv4qobjectwrapper.cpp:2117
#13 0x7ff1f3dfa6c1 in QV4::FunctionObject::call(QV4::Value const*,
QV4::Value const*, int) const
(argc=1, argv=0x7ff1adfbd550, thisObject=0x7ff1adfbd538,
this=0x7ffcd7984d58)
at jsruntime/qv4functionobject_p.h:202
#14 QV4::Runtime::CallPropertyLookup::call(QV4::ExecutionEngine*, QV4::Value
const&, unsigned int, QV4::Value*, int) 

[plasmashell] [Bug 464258] plasmashell crashed with the error The Wayland connection experienced a fatal error: Bad file descriptor

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=464258

--- Comment #11 from Matt Fagnani  ---
This type of plasmashell crash happened the two last times I've used Plasma in
a VM in the same sort of way. The last time was with Plasma 5.27.9 on Wayland
in a Fedora Rawhide/40 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20231031.n.0.iso in a QEMU/KVM VM in GNOME Boxes
in a Fedora 39 KDE Plasma installation. I started Konsole from the menu. I
hovered the cursor over the Konsole and Firefox icons in the task manager.
plasmashell crashed when hovering over Firefox task manager icons  The task
manager disappeared and then reappeared automatically a few seconds later. The
journal at the time of the crash showed plasmashell crashed with the error The
Wayland connection experienced a fatal error: Bad file descriptor and lines
like plasmashell[]: kpipewire_logging: Failed to query DMA-BUF formats. A race
condition might be involved in which a file descriptor from kpipewire of the
window preview was sometimes freed then used.

-- 
You are receiving this mail because:
You are watching all bug changes.

[rkward] [Bug 475810] New: rkward.rbackend crashed in QString::isEmpty when closing

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=475810

Bug ID: 475810
   Summary: rkward.rbackend crashed in QString::isEmpty when
closing
Classification: Applications
   Product: rkward
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: rkward-de...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: ---

Created attachment 162412
  --> https://bugs.kde.org/attachment.cgi?id=162412=edit
full trace with all threads of rkward crash

SUMMARY

I ran rkward 0.7.5 using R-4.3.1-3.fc39.x86_64 in Plasma 5.27.8 on Wayland in a
Fedora 39 KDE Plasma installation.  I closed RKWard by clicking the x button at
the top right and selecting Discard all in the box showing the following
"Save modified - RKWard 
The following items have been modified. Do you want to save them before
closing? 
RWorkspace (Data and Functions) Not saved"

rkward.rbackend segmentation faulted in QString::isEmpty when closing 4/4
times. 

Core was generated by `/usr/libexec/rkward.rbackend --debug-level=3
--server-name=%2Ftmp%2FrkwardDflqE'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fa0bee0310d in QString::isEmpty (this=)
at ../../include/QtCore/../../src/corelib/text/qstring.h:1078
1078../../include/QtCore/../../src/corelib/text/qstring.h: No such file or
directory.
[Current thread is 1 (Thread 0x7fa089dff6c0 (LWP 9507))]

(gdb) bt
#0  0x7fa0bee0310d in QString::isEmpty() const (this=)
at ../../include/QtCore/../../src/corelib/text/qstring.h:1078
#1  QIODevice::errorString() const (this=0x0) at io/qiodevice.cpp:2104
#2  0x55edfce94c76 in RKAbstractTransmitter::disconnected()
(this=0x7ffc9ce45660)
at
/usr/src/debug/rkward-0.7.5-1.fc39.x86_64/rkward/rbackend/rktransmitter.cpp:272
#3  0x7fa0beee8821 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fa089dfdca0, r=, this=0x7fa0840024a0)
at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#4  doActivate(QObject*, int, void**)
(sender=0x7fa0840012d0, signal_index=10, argv=0x7fa089dfdca0) at
kernel/qobject.cpp:3925
#5  0x7fa0beee89a8 in doActivate(QObject*, int, void**)
(sender=0x7fa0840013b0, signal_index=11, argv=0x7fa089dfdd70) at
kernel/qobject.cpp:3937
#6  0x7fa0beee3747 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**)
(sender=sender@entry=0x7fa0840013b0, m=m@entry=0x7fa0bf3f57a0
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x0) at
kernel/qobject.cpp:3985
#7  0x7fa0bf346fe7 in QAbstractSocket::disconnected()
(this=this@entry=0x7fa0840013b0)
at .moc/moc_qabstractsocket.cpp:404
#8  0x7fa0bf34794b in QAbstractSocket::disconnectFromHost()
(this=0x7fa0840013b0)
at socket/qabstractsocket.cpp:2841
#9  0x55edfce8dbff in RKRBackendTransmitter::doExit() (this=0x7ffc9ce45660)
at
/usr/src/debug/rkward-0.7.5-1.fc39.x86_64/rkward/rbackend/rkbackendtransmitter.cpp:81
#10 0x7fa0beedf0cb in QObject::event(QEvent*) (this=0x7ffc9ce45660,
e=0x55edfe63a100)
at kernel/qobject.cpp:1347
--Type  for more, q to quit, c to continue without paging--c
#11 0x7fa0beeb452b in doNotify (event=0x55edfe63a100,
receiver=0x7ffc9ce45660)
at kernel/qcoreapplication.cpp:1154
#12 QCoreApplication::notify(QObject*, QEvent*)
(event=, receiver=, this=)
at kernel/qcoreapplication.cpp:1140
#13 QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x7ffc9ce45660, event=0x55edfe63a100) at
kernel/qcoreapplication.cpp:1064
#14 0x7fa0beeb4762 in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=, event=) at
kernel/qcoreapplication.cpp:1462
#15 0x7fa0beeb79f5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*)
(receiver=0x0, event_type=0, data=0x55edfd540ac0) at
kernel/qcoreapplication.cpp:1821
#16 0x7fa0beeb7cad in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=, event_type=) at
kernel/qcoreapplication.cpp:1680
#17 0x7fa0bef06f9f in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x7fa084000ee0)
at kernel/qeventdispatcher_glib.cpp:277
#18 0x7fa0bd30fe1c in g_main_dispatch (context=0x7fa084000c30) at
../glib/gmain.c:3476
#19 g_main_context_dispatch_unlocked (context=0x7fa084000c30) at
../glib/gmain.c:4284
#20 0x7fa0bd36ad78 in g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x7fa084000c30, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4349
#21 0x7fa0bd30da93 in g_main_context_iteration (context=0x7fa084000c30,
may_block=1)
at ../glib/gmain.c:4414
#22 0x7fa0bef06a89 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fa084000b70, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#23 0x7fa0beeb2f0b in
QEventLoop::exec(QFlags)

[marble] [Bug 475672] marble crashed when starting in GNOME

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=475672

Matt Fagnani  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #1 from Matt Fagnani  ---
This problem didn't happen after I updated to qadwaitadecorations-0.1.2-5.fc39
https://bodhi.fedoraproject.org/updates/FEDORA-2023-69e9a0f475
which was marked as fixing a kdenlive crash with a similar trace
https://bugzilla.redhat.com/show_bug.cgi?id=2244239

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-systemmonitor] [Bug 475636] System Monitor crashed sometimes when starting in GNOME with the error "stack smashing detected"

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=475636

Matt Fagnani  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|REPORTED|RESOLVED

--- Comment #1 from Matt Fagnani  ---
This problem didn't happen after I updated to qadwaitadecorations-0.1.2-5.fc39
https://bodhi.fedoraproject.org/updates/FEDORA-2023-69e9a0f475

-- 
You are receiving this mail because:
You are watching all bug changes.

[marble] [Bug 475672] New: marble crashed when starting in GNOME

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=475672

Bug ID: 475672
   Summary: marble crashed when starting in GNOME
Classification: Applications
   Product: marble
   Version: 23.08.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: matt.fagn...@bell.net
  Target Milestone: ---

Created attachment 162330
  --> https://bugs.kde.org/attachment.cgi?id=162330=edit
Full trace of all threads of marble crash

SUMMARY

marble 23.08.1 crashed 4/4 times when starting in GNOME 45.0 on Wayland in a
Fedora 39 KDE Plasma installation. coredumpctl gdb showed the memory access
error _q_value= in frame 6 in QAtomicOps::loadRelaxed which
looked like an invalid pointer. The trace had functions like
QAdwaitaDecorations::updateColors from qadwaitadecorations-0.1.2-1.fc39.x86_64
which I think is used for Qt programs in GNOME in Fedora.

Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `marble'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=11, 
no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7f530edf4f80 (LWP 43363))]
(gdb) bt
#0  __pthread_kill_implementation
(threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at
pthread_kill.c:44
#1  0x7f530d2ae8a3 in __pthread_kill_internal (signo=11,
threadid=)
at pthread_kill.c:78
#2  0x7f530d25c8ee in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3  0x7f530fc44945 in KCrash::defaultCrashHandler(int) () at
/lib64/libKF5Crash.so.5
#4  0x7f530d25c9a0 in  () at /lib64/libc.so.6
#5  std::__atomic_base::load(std::memory_order) const
(__m=std::memory_order_relaxed, this=0x0001)
at /usr/include/c++/13/bits/atomic_base.h:503
#6  QAtomicOps::loadRelaxed(std::atomic const&)
(_q_value=)
at /usr/include/qt5/QtCore/qatomic_cxx11.h:239
#7  QBasicAtomicInteger::loadRelaxed() const (this=0x0001)
at /usr/include/qt5/QtCore/qbasicatomic.h:107
#8  QtPrivate::RefCount::deref() (this=0x0001) at
/usr/include/qt5/QtCore/qrefcount.h:66
#9  QMap::~QMap()
(this=, this=) at
/usr/include/qt5/QtCore/qmap.h:338
#10 QMap::operator=(QMap&&) (other=...,
this=0x55d4453fb630) at /usr/include/qt5/QtCore/qmap.h:349
#11 QAdwaitaDecorations::updateColors(bool) (this=0x55d4453fb5f0,
useDarkColors=)
at
/usr/src/debug/qadwaitadecorations-0.1.2-1.fc39.x86_64/src/qadwaitadecorations.cpp:156
#12 0x7f52978209cb in operator() (watcher=0x55d444eea140,
__closure=0x55d4453e3c40)
--Type  for more, q to quit, c to continue without paging--c
at
/usr/src/debug/qadwaitadecorations-0.1.2-1.fc39.x86_64/src/qadwaitadecorations.cpp:124
#13 QtPrivate::FunctorCall,
QtPrivate::List, void,
QAdwaitaDecorations::initConfiguration()::
>::call
(arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#14
QtPrivate::Functor,
1>::call, void> (arg=,
f=...)
at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#15
QtPrivate::QFunctorSlotObject,
1, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=, this_=0x55d4453e3c30, r=,
a=, ret=) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#16 0x7f530dae84f1 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffea3cd3c60, r=, this=0x55d4453e3c30)
at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#17 doActivate(QObject*, int, void**)
(sender=0x55d444eea140, signal_index=3, argv=0x7ffea3cd3c60) at
kernel/qobject.cpp:3925
#18 0x7f530dae3417 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**)
(sender=, m=m@entry=0x7f530ef315e0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffea3cd3c60)
at kernel/qobject.cpp:3985
#19 0x7f530ef16cc1 in
QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*)
(this=, _t1=) at
.moc/moc_qdbuspendingcall.cpp:158
#20 0x7f530daded9b in QObject::event(QEvent*) (this=0x55d444eea140,
e=0x55d444e4b1c0)
at kernel/qobject.cpp:1347
#21 0x7f530e7aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55d444eea140, e=0x55d444e4b1c0) at
kernel/qapplication.cpp:3640
#22 0x7f530dab4218 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55d444eea140, event=0x55d444e4b1c0) at
kernel/qcoreapplication.cpp:1064
#23 0x7f530dab4432 in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=, event=) at
kernel/qcoreapplication.cpp:1462
#24 0x7f530dab76c5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*)
(receiver=0x0, event_type=0, data=0x55d444817e80) at
kernel/qcoreapplication.cpp:1821
#25 

[plasma-systemmonitor] [Bug 475636] New: System Monitor crashed sometimes when starting in GNOME with the error "stack smashing detected"

[Matt Fagnani]

https://bugs.kde.org/show_bug.cgi?id=475636

Bug ID: 475636
   Summary: System Monitor crashed sometimes when starting in
GNOME with the error "stack smashing detected"
Classification: Applications
   Product: plasma-systemmonitor
   Version: 5.27.8
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: matt.fagn...@bell.net
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 162313
  --> https://bugs.kde.org/attachment.cgi?id=162313=edit
Full trace of all threads of the third System Monitor crash

SUMMARY

I was using GNOME 45.0 on Wayland in a Fedora 39 KDE Plasma installation. I
clicked on the button at top left of the screen. I entered monitor in the
search bar and clicked on Plasma System Monitor. System Monitor crashed
sometimes when starting in GNOME with the error "stack smashing detected" in
the journal and the trace. This problem happened three times each of which were
on the first time I ran System Monitor in different GNOME sessions. System
Monitor briefly appeared and then crashed. System Monitor ran normally on
subsequent times I ran it in the same GNOME session. drkonqi didn't appear the
first two crashes. I removed plasma-drkonqi and reproduced the crash a third
time so that the core dump would be saved. coredumpctl gdb showed that System
Monitor aborted with the "stack smashing detected" error shown in
__GI___fortify_fail in frame 5.

Core was generated by `/usr/bin/plasma-systemmonitor'.
Program terminated with signal SIGABRT, Aborted.

#0  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, 
no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7f27ed48ba00 (LWP 49125))]
(gdb) bt
#0  __pthread_kill_implementation
(threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at
pthread_kill.c:44
#1  0x7f27eb8aa8a3 in __pthread_kill_internal (signo=6, threadid=)
at pthread_kill.c:78
#2  0x7f27eb8588ee in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3  0x7f27eb8408ff in __GI_abort () at abort.c:79
#4  0x7f27eb8417d0 in __libc_message (fmt=fmt@entry=0x7f27eb9be309 "*** %s
***: terminated\n")
at ../sysdeps/posix/libc_fatal.c:150
#5  0x7f27eb93dcd9 in __GI___fortify_fail
(msg=msg@entry=0x7f27eb9be321 "stack smashing detected") at
fortify_fail.c:24
#6  0x7f27eb93ef64 in __stack_chk_fail () at stack_chk_fail.c:24
#7  0x7f27ed7c463b in loadProperty(QV4::ExecutionEngine*, QObject*,
QQmlPropertyData const&)
(v4=0x55c03f8eba30, object=, property=)
at jsruntime/qv4qobjectwrapper.cpp:207
#8  0x7f27ed7c5525 in
QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*,
QV4::ExecutionEngine*, QV4::Lookup*) (object=0x7f27d02d35c0,
engine=0x55c03f8eba30, lookup=0x55c0409f0d10)
at jsruntime/qv4qobjectwrapper.cpp:880
#9  0x7f27ed7e5b0a in QV4::Moth::VME::interpret(QV4::CppStackFrame*,
QV4::ExecutionEngine*, char const*) (frame=0xbfe5, frame@entry=0x7ffd40e123d0,
engine=0x55c03f8eba30, code=0x7f277e9e2e2e "")
at jsruntime/qv4vme_moth.cpp:641
#10 0x7f27ed7ea59f in QV4::Moth::VME::exec(QV4::CppStackFrame*,
QV4::ExecutionEngine*)
(frame=frame@entry=0x7ffd40e123d0, engine=engine@entry=0x55c03f8eba30)
at jsruntime/qv4vme_moth.cpp:466
--Type  for more, q to quit, c to continue without paging--c
#11 0x7f27ed77a512 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*)
(this=this@entry=0x55c0408e3df0, thisObject=,
argv=argv@entry=0x7f27d02d35b0, argc=, context=)
at jsruntime/qv4function.cpp:69
#12 0x7f27ed910760 in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*)
(this=this@entry=0x55c0409f1ff0, callData=0x7f27d02d3580,
isUndefined=isUndefined@entry=0x7ffd40e125bf) at
qml/qqmljavascriptexpression.cpp:212
#13 0x7f27ed916ee7 in QQmlBinding::evaluate(bool*)
(this=this@entry=0x55c0409f1ff0,
isUndefined=isUndefined@entry=0x7ffd40e125bf)
at
../../include/QtQml/5.15.10/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95
#14 0x7f27ed91b49b in
QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&,
QFlags, QV4::Scope&)
(this=0x55c0409f1ff0, watcher=..., flags=..., scope=...) at
qml/qqmlbinding.cpp:254
#15 0x7f27ed918d35 in
QQmlBinding::update(QFlags)
(this=0x55c0409f1ff0, flags=...) at qml/qqmlbinding.cpp:194
#16 0x7f27ed8f4527 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**)
(endpoint=, a=0x0) at qml/qqmlnotifier.cpp:104
#17 0x7f27ec0e81c0 in doActivate(QObject*, int, void**)
(sender=0x55c0409f1910, signal_index=15, argv=0x0) at
kernel/qobject.cpp:3817
#18