Bug 2227406 - [abrt] kdeconnectd: qt_message_fatal(): kdeconnectd killed by SIGABRT
Summary: [abrt] kdeconnectd: qt_message_fatal(): kdeconnectd killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-connect
Version: 38
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: marcdeop
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:fc582e745e4e5e3a6200ce58a42...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-29 09:09 UTC by Christian Stadelmann
Modified: 2024-05-28 13:37 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-28 13:37:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: proc_pid_status (1.44 KB, text/plain)
2023-07-29 09:09 UTC, Christian Stadelmann
no flags Details
File: limits (1.29 KB, text/plain)
2023-07-29 09:09 UTC, Christian Stadelmann
no flags Details
File: os_info (734 bytes, text/plain)
2023-07-29 09:09 UTC, Christian Stadelmann
no flags Details
File: cpuinfo (2.57 KB, text/plain)
2023-07-29 09:09 UTC, Christian Stadelmann
no flags Details
File: core_backtrace (43.20 KB, text/plain)
2023-07-29 09:09 UTC, Christian Stadelmann
no flags Details
File: dso_list (585 bytes, text/plain)
2023-07-29 09:09 UTC, Christian Stadelmann
no flags Details
File: backtrace (107.00 KB, text/plain)
2023-07-29 09:09 UTC, Christian Stadelmann
no flags Details
Backtrace of second crash when aborting the stuck file transfer dialog (87.54 KB, text/plain)
2023-07-29 09:24 UTC, Christian Stadelmann
no flags Details


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 461040 0 NOR REOPENED Сrashes when receiving files from phone 2023-07-29 09:24:09 UTC

Description Christian Stadelmann 2023-07-29 09:09:23 UTC
Description of problem:
I tried sharing multiple files from my smartphone to my PC. It repeatedly did not finish but got stuck in the progress bar.

Steps I followed:
1. On my smartphone, open the file manager
2. Select multiple files (5…50 files, 1…500MB) and click the "Share" button
3. Select KDE connect and share with my PC
4. When KDE connect progress bar is stuck, click "Abbrechen" ("Abort"?)

What happens:
The first few files were transferred just fine. At some point, the progress bar in KDE connect's window on my PC got stuck. KDE connect on the Smartphone seemed to continue sending files (progress bar continued as if everything were fine), finishing in regular expected time, but the files were not stored on my PC.
After I pressed "Abbrechen", it seems like KDE connect crashed (tray icon vanished). I'm not sure however whether this crash report was happening at the time the transfer got stuck or whether it was happening at the time KDE connect's tray icon vanished.

What should happen:
File transfer should not get stuck. KDE connect should not crash when aborting stuck file transfer.

How reproducible:
It seems like this issue happens more likely the more files (or larger files?) I transfer. With 10 files of at least 100MB, I could reproduce it 100%.

Software and versions:
My smartphone is running Android 12 and KDE connect 1.27.0. I shared the files with "Simple File Manager" (see https://github.com/SimpleMobileTools/Simple-File-Manager ).

Additional comments:
At the same time, something weird happened with my Wifi router (Fritz!Box 7520, Fritz!OS 7.50): It seemed to crash somehow, disconnecting from the internet but still reacting to ping.

Version-Release number of selected component:
kdeconnectd-23.04.3-2.fc38

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         kdeconnectd killed by SIGABRT
journald_cursor: s=c13f6a5aaaaa4f56b87e84b483d36f17;i=8f9c6;b=468166f4b8d5405ab1d1115d38514443;m=7623696a;t=6019ad9ad0e14;x=e51177e9bc4cf0ec
executable:     /usr/libexec/kdeconnectd
cmdline:        /usr/libexec/kdeconnectd
rootdir:        /
kernel:         6.4.6-200.fc38.x86_64
package:        kdeconnectd-23.04.3-2.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: qt_message_fatal

Truncated backtrace:
Thread no. 1 (11 frames)
 #4 qt_message_fatal at global/qlogging.cpp:1914
 #6 KIO::SlaveBase::waitForAnswer(int, int, QByteArray&, int*) at /usr/src/debug/kf5-kio-5.108.0-1.fc38.x86_64/src/core/slavebase.cpp:1149
 #7 KIO::SlaveBase::canResume(unsigned long long) at /usr/src/debug/kf5-kio-5.108.0-1.fc38.x86_64/src/core/slavebase.cpp:1116
 #8 FileProtocol::put(QUrl const&, int, QFlags<KIO::JobFlag>) at /usr/src/debug/kf5-kio-5.108.0-1.fc38.x86_64/src/ioslaves/file/file.cpp:550
 #9 KIO::SlaveBase::dispatch(int, QByteArray const&) at /usr/src/debug/kf5-kio-5.108.0-1.fc38.x86_64/src/core/slavebase.cpp:1289
 #10 KIO::SlaveBase::dispatchLoop() at /usr/src/debug/kf5-kio-5.108.0-1.fc38.x86_64/src/core/slavebase.cpp:342
 #11 KIO::WorkerThread::run() at /usr/src/debug/kf5-kio-5.108.0-1.fc38.x86_64/src/core/workerthread.cpp:62
 #12 operator() at thread/qthread_unix.cpp:350
 #13 (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > at thread/qthread_unix.cpp:287
 #14 QThreadPrivate::start(void*) at thread/qthread_unix.cpp:310
 #16 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Comment 1 Christian Stadelmann 2023-07-29 09:09:26 UTC
Created attachment 1980557 [details]
File: proc_pid_status

Comment 2 Christian Stadelmann 2023-07-29 09:09:28 UTC
Created attachment 1980558 [details]
File: limits

Comment 3 Christian Stadelmann 2023-07-29 09:09:29 UTC
Created attachment 1980559 [details]
File: os_info

Comment 4 Christian Stadelmann 2023-07-29 09:09:31 UTC
Created attachment 1980560 [details]
File: cpuinfo

Comment 5 Christian Stadelmann 2023-07-29 09:09:33 UTC
Created attachment 1980561 [details]
File: core_backtrace

Comment 6 Christian Stadelmann 2023-07-29 09:09:34 UTC
Created attachment 1980562 [details]
File: dso_list

Comment 7 Christian Stadelmann 2023-07-29 09:09:36 UTC
Created attachment 1980563 [details]
File: backtrace

Comment 8 Christian Stadelmann 2023-07-29 09:24:09 UTC
As mentioned in the upstream bug report by others, there are two different but related crashes happening here:
1. The crash with the backtrace above, probably happens when file transfer between smartphone and PC is stuck
2. The second crash when aborting the stuck file transfer dialog. I'll attack that crash's backtrace in the next comment.

Comment 9 Christian Stadelmann 2023-07-29 09:24:54 UTC
Created attachment 1980564 [details]
Backtrace of second crash when aborting the stuck file transfer dialog

Comment 10 Aoife Moloney 2024-05-28 13:37:13 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.