Bug 484576 - KDE crashed on startup after new installation
Summary: KDE crashed on startup after new installation
Status: RESOLVED DUPLICATE of bug 481760
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 23.08.4
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-03-27 06:37 UTC by Justin Bloom
Modified: 2024-07-31 08:08 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 Justin Bloom 2024-03-27 06:37:36 UTC
Application: kdeconnectd (23.08.4)

Qt Version: 5.15.9
Frameworks Version: 5.113.0
Operating System: Linux 5.14.0-432.el9.x86_64 x86_64
Windowing System: X11
Distribution: CentOS Stream 9
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
I just installed in CentOS 9 Stream using epel-repo and crb, I saw errors about no match for certain packages. When I rebooted, it still went into Gnome and showed an error that KDE couldn't start

The reporter is unsure if this crash is reproducible.

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

[KCrash Handler]
#4  0x00007f93e6fc4036 in KdeConnectConfig::deviceId() () from /lib64/libkdeconnectcore.so.23
#5  0x00007f93e6fc762d in KdeConnectConfig::deviceInfo() () from /lib64/libkdeconnectcore.so.23
#6  0x00007f93e6fb40b5 in LanLinkProvider::broadcastToNetwork() () from /lib64/libkdeconnectcore.so.23
#7  0x00007f93e58dbc69 in QtPrivate::QSlotObjectBase::call (a=0x7ffc1cde0150, r=<optimized out>, this=0x7f93cc01a030) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate<false> (sender=0x55fa149f40d0, signal_index=3, argv=0x7ffc1cde0150) at kernel/qobject.cpp:3923
#9  0x00007f93e58d6947 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7f93e5b6f560 <QTimer::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc1cde0150) at kernel/qobject.cpp:3983
#10 0x00007f93e58deeee in QTimer::timeout (this=<optimized out>, _t1=...) at .moc/moc_qtimer.cpp:205
#11 0x00007f93e58d2c8f in QObject::event (this=0x55fa149f40d0, e=0x7ffc1cde02b0) at kernel/qobject.cpp:1369
#12 0x00007f93e65af533 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55fa149f40d0, e=0x7ffc1cde02b0) at kernel/qapplication.cpp:3640
#13 0x00007f93e58a7958 in QCoreApplication::notifyInternal2 (receiver=0x55fa149f40d0, event=0x7ffc1cde02b0) at kernel/qcoreapplication.cpp:1064
#14 0x00007f93e58f8ad3 in QTimerInfoList::activateTimers (this=0x55fa148fa2d0) at kernel/qtimerinfo_unix.cpp:643
#15 0x00007f93e58f93cc in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:183
#16 0x00007f93e4257f4f in g_main_dispatch (context=0x7f93cc005000) at ../glib/gmain.c:3364
#17 g_main_context_dispatch (context=0x7f93cc005000) at ../glib/gmain.c:4079
#18 0x00007f93e42ad268 in g_main_context_iterate.constprop.0 (context=context@entry=0x7f93cc005000, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4155
#19 0x00007f93e4255713 in g_main_context_iteration (context=0x7f93cc005000, may_block=1) at ../glib/gmain.c:4220
#20 0x00007f93e58f97d8 in QEventDispatcherGlib::processEvents (this=0x55fa148c4800, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#21 0x00007f93e58a6362 in QEventLoop::exec (this=this@entry=0x7ffc1cde0550, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#22 0x00007f93e58ae894 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#23 0x000055fa12e5b011 in main ()
[Inferior 1 (process 7711) detached]

The reporter indicates this bug may be a duplicate of or related to bug 481760.

Reported using DrKonqi
Comment 1 cwo 2024-07-31 08:08:04 UTC
*** This bug has been marked as a duplicate of bug 481760 ***