Bug 467755 - KDE Daemon crashed after windows starting and starting services.
Summary: KDE Daemon crashed after windows starting and starting services.
Status: RESOLVED DUPLICATE of bug 453875
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 22.12.1
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-03-24 15:01 UTC by yogesh kumar
Modified: 2024-07-31 08:03 UTC (History)
2 users (show)

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


Attachments
KDE Daemon crashed after windows starting and starting services. (6.95 KB, text/vnd.kde.kcrash-report)
2023-03-24 15:14 UTC, yogesh kumar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description yogesh kumar 2023-03-24 15:01:35 UTC
Application: kdeconnectd (22.12.1)
 (Compiled from sources)
Qt Version: 5.15.3
Frameworks Version: 5.102.0
Operating System: Linux 5.14.0-289.el9.x86_64 x86_64
Windowing System: X11
Distribution: CentOS Stream 9
DrKonqi: 5.26.5 [KCrashBackend]

-- Information about the crash:
KDE Daemon crashed after windows starting and starting services.

The crash can be reproduced every time.

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

[KCrash Handler]
#4  0x00007ff5fa2847e6 in KdeConnectConfig::deviceId() () from /lib64/libkdeconnectcore.so.22
#5  0x00007ff5fa2892c7 in NetworkPacket::createIdentityPacket(NetworkPacket*) () from /lib64/libkdeconnectcore.so.22
#6  0x00007ff5fa2754d0 in LanLinkProvider::broadcastToNetwork() () from /lib64/libkdeconnectcore.so.22
#7  0x00007ff5f8adaf49 in QtPrivate::QSlotObjectBase::call (a=0x7ffd3e07fb40, r=<optimized out>, this=0x55589fe6d5e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate<false> (sender=0x55589fd5c468, signal_index=3, argv=0x7ffd3e07fb40) at kernel/qobject.cpp:3886
#9  0x00007ff5f8ad5ec7 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7ff5f8d7e580 <QTimer::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd3e07fb40) at kernel/qobject.cpp:3946
#10 0x00007ff5f8ade1ee in QTimer::timeout (this=<optimized out>, _t1=...) at .moc/moc_qtimer.cpp:205
#11 0x00007ff5f8ad1a2f in QObject::event (this=0x55589fd5c468, e=0x7ffd3e07fca0) at kernel/qobject.cpp:1336
#12 0x00007ff5f97ae423 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55589fd5c468, e=0x7ffd3e07fca0) at kernel/qapplication.cpp:3637
#13 0x00007ff5f8aa7358 in QCoreApplication::notifyInternal2 (receiver=0x55589fd5c468, event=0x7ffd3e07fca0) at kernel/qcoreapplication.cpp:1064
#14 0x00007ff5f8af7d43 in QTimerInfoList::activateTimers (this=0x55589fd3b150) at kernel/qtimerinfo_unix.cpp:643
#15 0x00007ff5f8af863c in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:183
#16 0x00007ff5f712fe2f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#17 0x00007ff5f7184508 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0
#18 0x00007ff5f712d5f3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#19 0x00007ff5f8af8a48 in QEventDispatcherGlib::processEvents (this=0x55589fd3d000, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#20 0x00007ff5f8aa5d62 in QEventLoop::exec (this=this@entry=0x7ffd3e07ff40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#21 0x00007ff5f8aae294 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#22 0x000055589e04b0ae in main ()
[Inferior 1 (process 3522) detached]

Reported using DrKonqi
Comment 1 yogesh kumar 2023-03-24 15:14:16 UTC
Created attachment 157548 [details]
KDE Daemon crashed after windows starting and starting services.

kde connect application is used on cent os and installing from terminal .after installation this app is giving some error like "KDE Daemon crashed after windows starting and starting its services".

Note:
I am using this bag tracking system first time. but this bug tracking system is very hectic/irritating,just because of bug reporting is not in easy way .it's just like programming.and I thought everybody couldn't submitting bug this way or following set of instructions.
It should be like that need mail account - application installed os version - saved bug report - simpal event discription .
Comment 2 cwo 2024-07-31 08:03:14 UTC

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