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

--- Comment #8 from Jakob Petsovits <jpe...@petsovits.com> ---
Ah, I see what's going on. The (updated, binary-incompatible) NetworkProvider
destructor is executed for code in our build directories, e.g.:

> #12 NetworkPacket::~NetworkPacket (this=0x7ffd3362d940, __in_chrg=<optimized 
> out>) at 
> /home/akseli/Repositories/kde/src/kdeconnect-kde/core/networkpacket.h:23
#13 ClipboardPlugin::sendConnectPacket (this=0x56438c436310) at
/home/akseli/Repositories/kde/src/kdeconnect-kde/plugins/clipboard/clipboardplugin.cpp:85

However, the code further up the stack comes from Arch packages, as can be
induced from the /usr/src/ build directory:

#14 0x00007f016c8d9039 in Device::reloadPlugins (this=0x56438cbe3e30) at
/usr/src/debug/kde-connect-24.12.2-1.fc41.x86_64/core/device.cpp:182
#15 0x00007f016c8d1e5b in Daemon::onNewDeviceLink (this=0x7ffd3362f990,
link=0x56438ccc6af0) at
/usr/src/debug/kde-connect-24.12.2-1.fc41.x86_64/core/daemon.cpp:186

Because m_id got removed from NetworkPacket and is used from a bunch of places,
it's likely that there is a mismatch between constructor and destructor
depending on which code exactly is creating or destroying the NetworkPacket at
hand.

Running kdeconnectd manually from my build directory
(/home/kpetso/build/prefix/bin/kdeconnectd) as opposed to the binary from the
Arch package (/usr/bin/kdeconnectd) makes it not crash anymore. Although there
are still lots of warnings in the debug output like

> kdeconnect.core: missing property 0x555555aa8fc0 "id"

from qjsonobject2qobject() at networkpacket.cpp:71.

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

Reply via email to