Summary: | Kio6 segfaults if trying to access an Samsung Galaxy S 8 via MTP in TWRP Recovery Manager | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kio-extras | Reporter: | devzero |
Component: | MTP | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | REPORTED --- | ||
Severity: | crash | CC: | cousinmarc, elvis.angelaccio, kfm-devel, sitter |
Priority: | NOR | ||
Version: | 24.05.0 | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | kio6 backtrace from coredump |
Description
devzero
2024-05-27 16:48:10 UTC
Please provide a backtrace as per https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports i attached gdb first to dolphin, however that does not give anything, so I attached it to kiod6 continued it then it crashed wit the following backtrace: (gdb) continue Continuing. Thread 1 "kiod6" received signal SIGSEGV, Segmentation fault. 0x00007d721697e1dd in ?? () from /usr/lib/libc.so.6 (gdb) backtrace #0 0x00007d721697e1dd in ??? () at /usr/lib/libc.so.6 #1 0x00007d7203f3a326 in ??? () at /usr/lib/libmtp.so.9 #2 0x00007d7203f27ec4 in LIBMTP_Get_Filemetadata () at /usr/lib/libmtp.so.9 #3 0x00007d720abf15cc in ??? () at /usr/lib/qt6/plugins/kf6/kiod/kmtpd.so #4 0x00007d720abf6916 in ??? () at /usr/lib/qt6/plugins/kf6/kiod/kmtpd.so #5 0x00007d7217d8463d in ??? () at /usr/lib/libQt6DBus.so.6 #6 0x00007d7217d8538a in ??? () at /usr/lib/libQt6DBus.so.6 #7 0x00007d7217d8eecf in ??? () at /usr/lib/libQt6DBus.so.6 #8 0x00007d7217d8ef1a in ??? () at /usr/lib/libQt6DBus.so.6 #9 0x00007d7216f8c0cf in QObject::event(QEvent*) () at /usr/lib/libQt6Core.so.6 #10 0x00007d7217efc55c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6 #11 0x00007d7216f44e08 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6 #12 0x00007d7216f451cb in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt6Core.so.6 #13 0x00007d72171a45ec in ??? () at /usr/lib/libQt6Core.so.6 #14 0x00007d72165e4a89 in ??? () at /usr/lib/libglib-2.0.so.0 #15 0x00007d72166469b7 in ??? () at /usr/lib/libglib-2.0.so.0 #16 0x00007d72165e3f95 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #17 0x00007d72171a28bd in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6 #18 0x00007d7216f4f0de in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6 #19 0x00007d7216f4942d in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6 #20 0x000057f5270393d9 in ??? () #21 0x00007d7216839c88 in ??? () at /usr/lib/libc.so.6 #22 0x00007d7216839d4c in __libc_start_main () at /usr/lib/libc.so.6 #23 0x000057f5270396b5 in ??? () (gdb) Created attachment 169912 [details]
kio6 backtrace from coredump
the attached backtrace from a coredump
Out of a coredump, gdb could gather more data then the 23 lines, HTH. Looks a bit like a possible bug in libmtp. Probably worth inspecting our code for possible problems though. Relevant snippet: #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76 #1 0x00007cd3080cb326 in ptp_unpack_PTPTIME (str=0x6654c7a9 <error: Cannot access memory at address 0x6654c7a9>) at /usr/src/debug/libmtp/libmtp-1.1.21/src/ptp-pack.c:720 ptpdate = {<optimized out> <repeats 40 times>} tmp = {<optimized out>, <optimized out>, <optimized out>, <optimized out>, <optimized out>} ptpdatelen = <optimized out> tm = {tm_sec = <optimized out>, tm_min = <optimized out>, tm_hour = <optimized out>, tm_mday = <optimized out>, tm_mon = <optimized out>, tm_year = <optimized out>, tm_wday = <optimized out>, tm_yday = <optimized out>, tm_isdst = <optimized out>, tm_gmtoff = <optimized out>, tm_zone = <optimized out>} ptpdate = {<optimized out> <repeats 40 times>} tmp = {<optimized out>, <optimized out>, <optimized out>, <optimized out>, <optimized out>} ptpdatelen = <optimized out> tm = {tm_sec = <optimized out>, tm_min = <optimized out>, tm_hour = <optimized out>, tm_mday = <optimized out>, tm_mon = <optimized out>, tm_year = <optimized out>, tm_wday = <optimized out>, tm_yday = <optimized out>, tm_isdst = <optimized out>, tm_gmtoff = <optimized out>, tm_zone = <optimized out>} #2 ptp_object_want (params=0x5b54d8a63e90, handle=1, want=5, retob=<optimized out>) at /usr/src/debug/libmtp/libmtp-1.1.21/src/ptp.c:9095 i = 5 prop = 0x5b54d8a02ef8 nrofprops = <optimized out> props = 0x5b54d8a02e80 --Type <RET> for more, q to quit, c to continue without paging-- ret = 8193 ob = <optimized out> read64bit = <optimized out> #3 0x00007cd3080b8ec4 in LIBMTP_Get_Filemetadata (device=0x5b54d89c90e0, fileid=<optimized out>) at /usr/src/debug/libmtp/libmtp-1.1.21/src/libmtp.c:4469 params = 0x5b54d8a63e90 ret = <optimized out> ob = 0x5b54d8a69af0 #4 0x00007cd3081b65cc in MTPLister::run (this=0x7cd30400eaa0) at /usr/src/debug/kio-extras/kio-extras-24.05.0/mtp/kiod_module/mtplister.cpp:29 file = std::unique_ptr<LIBMTP_file_struct> = {get() = <optimized out>} #5 0x00007cd3081bb916 in ListerAdaptor::run (this=0x5b54d8a0b460) at /usr/src/debug/kio-extras/build/mtp/kiod_module/listeradaptor.cpp:45 I also have kiod6 segfaulting, on trying to create a file on MTP storage (a BMW connectedride navigator, it seems it's an android device). My backtrace is different, should I also post it here ? |