Bug 476732 - complete lockup forcing a REPEATED restart (would not post the first time)
Summary: complete lockup forcing a REPEATED restart (would not post the first time)
Status: RESOLVED DUPLICATE of bug 452304
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 22.04.3
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-11-09 01:17 UTC by goo
Modified: 2024-08-02 15:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description goo 2023-11-09 01:17:10 UTC
Application: kdeconnectd (22.04.3)

Qt Version: 5.15.3
Frameworks Version: 5.104.0
Operating System: Linux 6.2.0-36-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04.3 LTS
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
was using the browser enerting text into a message when the music stopped and everythign froze.. only option was a hard reset with the power button, but the machine would not post until after the 2nd hard reset.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fcac0149e04 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fcac02315ff in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fcac0237003 in QSettings::beginGroup(QString const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fcac1b3743a in KdeConnectConfig::getDeviceProperty(QString const&, QString const&, QString const&) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.22
#8  0x00007fcac1b26542 in LanLinkProvider::configureSslSocket(QSslSocket*, QString const&, bool) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.22
#9  0x00007fcac1b2f8e0 in CompositeUploadJob::newConnection() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.22
#10 0x00007fcac02f1793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007fcabff432d0 in QTcpServerPrivate::readNotification() () from /lib/x86_64-linux-gnu/libQt5Network.so.5
#12 0x00007fcabff4f589 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5
#13 0x00007fcac0f6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007fcac02b9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007fcac0313cc5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007fcabea51d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007fcabeaa7258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fcabea4f3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fcac03130b8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007fcac02b875b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007fcac02c0cf4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x0000562cc10effad in ?? ()
#23 0x00007fcabf829d90 in __libc_start_call_main (main=main@entry=0x562cc10efb70, argc=argc@entry=1, argv=argv@entry=0x7ffeab9da2d8) at ../sysdeps/nptl/libc_start_call_main.h:58
#24 0x00007fcabf829e40 in __libc_start_main_impl (main=0x562cc10efb70, argc=1, argv=0x7ffeab9da2d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffeab9da2c8) at ../csu/libc-start.c:392
#25 0x0000562cc10f0235 in _start ()
[Inferior 1 (process 2000) detached]

Reported using DrKonqi
Comment 1 goo 2023-11-09 01:53:07 UTC
also worth mentioning that the crash handler is hung on "submitting bug report..." 

but since the report is listed here, i'm just going to kill the window.
Comment 2 cwo 2024-08-02 15:06:40 UTC
Thank you for the bug report! This issue has already been filed; please follow the linked bug report for updates on a fix.

*** This bug has been marked as a duplicate of bug 452304 ***