Bug 462390 - Crashes due KDE Connect if mobile device is locked
Summary: Crashes due KDE Connect if mobile device is locked
Status: REPORTED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 22.04.3
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi
: 433218 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-11-29 11:20 UTC by devanshjangid99
Modified: 2023-12-11 08:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description devanshjangid99 2022-11-29 11:20:15 UTC
Application: dolphin (22.04.3)
 (Compiled from sources)
Qt Version: 5.15.3
Frameworks Version: 5.98.0
Operating System: Linux 5.15.0-53-generic x86_64
Windowing System: Wayland
Distribution: Ubuntu 22.04.1 LTS
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
If the android device that is connect is locked, and the user tries to browse the device whilst it is locked, Dolphin will crash when trying to access the phone's storage via KDE Connect.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140373549512128) at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=140373549512128) at ./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=140373549512128, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#7  0x00007fab486ef476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007fab486d57f3 in __GI_abort () at ./stdlib/abort.c:79
#9  0x00007fab48b8fba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fab467afe45 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#11 0x00007fab467c011a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#12 0x00007fab48df07c8 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007fab48df3cb3 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007fab48df44e3 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007fab498aa713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007fab48db8e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007fab48e12cc5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007fab469d9d1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fab46a2e6f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fab469d73c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fab48e120b8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007fab48db775b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007fab48dbfcf4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x0000560ef4012ccb in ?? ()
#25 0x00007fab486d6d90 in __libc_start_call_main (main=main@entry=0x560ef400d6a0, argc=argc@entry=1, argv=argv@entry=0x7ffe7b15a588) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x00007fab486d6e40 in __libc_start_main_impl (main=0x560ef400d6a0, argc=1, argv=0x7ffe7b15a588, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe7b15a578) at ../csu/libc-start.c:392
#27 0x0000560ef4013455 in ?? ()
[Inferior 1 (process 30247) detached]

Reported using DrKonqi
Comment 1 Akseli Lahtinen 2023-12-11 08:28:10 UTC
*** Bug 433218 has been marked as a duplicate of this bug. ***