https://bugs.kde.org/show_bug.cgi?id=485407
continue2...@outlook.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |continue2...@outlook.com
--- Comment #3 from continue2...@outlook.com ---
I can confirm this bug in my computers running Hyprland(Arch Linux) and KDE
Plasma(Arch Linux), and my friend's computer running KDE Plasma(Arch Linux).
When using Hyprland, '/usr/lib/polkit-kde-authentication-agent-1' is start
manually, and it failed with SIGSEGV after the first authentication, no matter
the authentication itself is successful or not.
On Plasma it does fail, but silently, because in Plasma,
polkit-kde-authentication-agent-1 is started by user service
'plasma-polkit-agent.service', and the service itself configured as
'Restart=on-failure', so the problem can be ignored.
I downloaded debug symbols and debugged with gdb, here is what I found.
Thread 1 "polkit-kde-auth" received signal SIGSEGV, Segmentation fault.
QObject::deleteLater (this=0x0)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.cpp:2456
2456 Q_D(QObject);
(gdb) c
Continuing.
Thread 1 "polkit-kde-auth" received signal SIGSEGV, Segmentation fault.
0x0000722e4fcab32c in ?? () from /usr/lib/libc.so.6
(gdb) c
It seems that the problem is caused by qt 6.7.0 but not polkit-kde-agent, since
the process failed in the function 'QObject::deleteLater()' when accessing a
nullptr, and this code belongs to qt6-base but not the polkit component.
Further more, I found in qt 6.7.0, the commit
https://github.com/qt/qtbase/commit/d50746e changed the way the
'QObject::deleteLater()' function works, so it might be a bug upstream caused
by qt 6.7.0.
--
You are receiving this mail because:
You are watching all bug changes.
