[kde] [Bug 441349] New: latte-dock crash on system starts
Yakun Li
bugzilla_noreply at kde.org
Sun Aug 22 09:31:43 BST 2021
https://bugs.kde.org/show_bug.cgi?id=441349
Bug ID: 441349
Summary: latte-dock crash on system starts
Product: kde
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: liyakun127 at gmail.com
Target Milestone: ---
Application: latte-dock (0.10.0)
Qt Version: 5.15.2
Frameworks Version: 5.85.0
Operating System: Linux 5.13.8-1-default x86_64
Windowing System: X11
Drkonqi Version: 5.22.4
Distribution: "openSUSE Tumbleweed"
-- Information about the crash:
- What I was doing when the application crashed:
The system just starts and latte-dock was set to auto start, but the latte-dock
crash after system start without any additional operations.
The crash can be reproduced every time.
-- Backtrace:
Application: Latte Dock (latte-dock), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fab89916200
(LWP 3421))]
[KCrash Handler]
#6 0x000055c859e615fe in QString::QString (other=..., this=0x7ffd84121580) at
/usr/include/qt5/QtCore/qstring.h:1093
#7 Latte::Layout::AbstractLayout::name (this=<optimized out>) at
/usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/layout/abstractlayout.cpp:204
#8 Latte::Layouts::Synchronizer::currentLayoutsNames (this=<optimized out>) at
/usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/layouts/synchronizer.cpp:202
#9 0x000055c859e9521e in Latte::Layouts::Manager::currentLayoutsNames
(this=<optimized out>) at
/usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/layouts/manager.cpp:155
#10 Latte::Settings::Controller::Layouts::initLayouts (this=0x55c85c84d7a0) at
/usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/settings/settingsdialog/layoutscontroller.cpp:582
#11 0x000055c859e5bce6 in Latte::Settings::Controller::Layouts::Layouts
(parent=0x55c85c497290, this=0x55c85c84d7a0) at
/usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/settings/settingsdialog/layoutscontroller.cpp:75
#12 Latte::Settings::Handler::TabLayouts::TabLayouts (parent=0x55c85c035f10,
this=0x55c85c497290) at
/usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/settings/settingsdialog/tablayoutshandler.cpp:54
#13 Latte::Settings::Dialog::SettingsDialog::SettingsDialog (parent=0x0,
corona=<optimized out>, this=0x55c85c035f10) at
/usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/settings/settingsdialog/settingsdialog.cpp:69
#14 Latte::Layouts::Manager::showLatteSettingsDialog (this=0x55c85bf89f00,
firstPage=0, toggleCurrentPage=<optimized out>) at
/usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/layouts/manager.cpp:398
#15 0x000055c859f1fd91 in LatteDockAdaptor::qt_static_metacall
(_a=0x7ffd84121880, _id=10, _c=QMetaObject::InvokeMetaMethod,
_o=0x55c85c0505c0) at
/usr/src/debug/latte-dock-0.10.0-1.1.x86_64/build/app/lattedockadaptor.moc:184
#16 LatteDockAdaptor::qt_metacall (this=0x55c85c0505c0,
_c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7ffd84121880) at
/usr/src/debug/latte-dock-0.10.0-1.1.x86_64/build/app/lattedockadaptor.moc:241
#17 0x00007fab8c47f6bb in QDBusConnectionPrivate::deliverCall (this=<optimized
out>, object=<optimized out>, msg=..., metaTypes=..., slotIdx=<optimized out>)
at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190
#18 0x00007fab8c4830ac in QDBusConnectionPrivate::activateCall
(this=this at entry=0x7fab7800b910, object=0x55c85c0505c0, flags=flags at entry=273,
msg=...) at qdbusintegrator.cpp:904
#19 0x00007fab8c4835b9 in QDBusConnectionPrivate::activateCall (msg=...,
flags=273, object=<optimized out>, this=0x7fab7800b910) at
qdbusintegrator.cpp:853
#20 QDBusConnectionPrivate::activateObject (this=0x7fab7800b910, node=...,
msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1489
#21 0x00007fab8c485e58 in QDBusActivateObjectEvent::placeMetaCall
(this=0x55c85bdb6f60) at qdbusintegrator.cpp:1617
#22 0x00007fab8c1a7f5e in QObject::event (this=0x7ffd84122240,
e=0x55c85bdb6f60) at kernel/qobject.cpp:1314
#23 0x00007fab8cfa9a7f in QApplicationPrivate::notify_helper (this=<optimized
out>, receiver=0x7ffd84122240, e=0x55c85bdb6f60) at
kernel/qapplication.cpp:3632
#24 0x00007fab8c17b96a in QCoreApplication::notifyInternal2
(receiver=0x7ffd84122240, event=0x55c85bdb6f60) at
kernel/qcoreapplication.cpp:1064
#25 0x00007fab8c17e9b7 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55c85bc854b0) at
kernel/qcoreapplication.cpp:1821
#26 0x00007fab8c1d37d3 in postEventSourceDispatch (s=s at entry=0x55c85bdaa6a0) at
kernel/qeventdispatcher_glib.cpp:277
#27 0x00007fab8a54380f in g_main_dispatch (context=0x7fab80005000) at
../glib/gmain.c:3337
#28 g_main_context_dispatch (context=0x7fab80005000) at ../glib/gmain.c:4055
#29 0x00007fab8a543b98 in g_main_context_iterate
(context=context at entry=0x7fab80005000, block=block at entry=1,
dispatch=dispatch at entry=1, self=<optimized out>) at ../glib/gmain.c:4131
#30 0x00007fab8a543c4f in g_main_context_iteration (context=0x7fab80005000,
may_block=1) at ../glib/gmain.c:4196
#31 0x00007fab8c1d2e54 in QEventDispatcherGlib::processEvents
(this=0x55c85bdaca60, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#32 0x00007fab8c17a36b in QEventLoop::exec (this=this at entry=0x7ffd84121e60,
flags=..., flags at entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#33 0x00007fab8c182650 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#34 0x00007fab8c7081dc in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#35 0x00007fab8cfa99f5 in QApplication::exec () at kernel/qapplication.cpp:2824
#36 0x000055c859e0f3b8 in main (argc=<optimized out>, argv=<optimized out>) at
/usr/src/debug/latte-dock-0.10.0-1.1.x86_64/app/main.cpp:313
[Inferior 1 (process 3421) detached]
Possible duplicates by query: bug 82199, bug 429973, bug 424760, bug 410345,
bug 409383.
Reported using DrKonqi
This report was filed against 'kde' because the product 'latte-dock' could not
be located in Bugzilla. Add it to drkonqi's mappings file!
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list