https://bugs.kde.org/show_bug.cgi?id=499076
nyanpasu64 <nyanpas...@tuta.io> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nyanpas...@tuta.io
--- Comment #2 from nyanpasu64 <nyanpas...@tuta.io> ---
Got a crash on FileTransferJob::doStart when waking a computer from sleep. If I
expand the KDE Connect icon in the Plasma system tray, I get another daemon
crash there.
Running /usr/bin/kdeconnectd manually crashes too.
In https://invent.kde.org/network/kdeconnect-kde, the only call to
FileTransferJob::doStart() I can find comes from FileTransferJob::start().
Poking around in Ghidra, my vague impression is that the crash happens because
in FileTransferJob, `QSharedPointer<QIODevice> m_origin` is nullptr and
`m_origin->bytesAvailable()` crashes. My question is, why are you running a
file transfer job from a remote device that isn't even online right now?
I tried breakpointing FileTransferJob::start(), but now the bug no longer
happens. But I see two Pixel 4a devices in the device list, one is paired and
the other isn't, but when I click the one that isn't, the right side says
Paired. And when I unpair, System Settings crashes. Anyway now there's no
longer two of them, so problem "solved" for now?
Operating System: Fedora Linux 42
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.9-300.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Intel® HD Graphics 4000
Manufacturer: M&A Technology
Product Name: DB75EN__
--
You are receiving this mail because:
You are watching all bug changes.
