Application: latte-dock (0.10.0) Qt Version: 5.15.3 Frameworks Version: 5.84.0 Operating System: Linux 5.11.0-25-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: When I log into my account Latte sometimes chrashes on startup. It started doing it since the latest update. The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [New LWP 2154] [New LWP 2179] [New LWP 2214] [New LWP 2215] [New LWP 2216] [New LWP 2217] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x00007fd07b473aff in __GI___poll (fds=0x7ffe4fac7ff8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fd0778e59c0 (LWP 2125))] Thread 7 (Thread 0x7fd06d458700 (LWP 2217)): #0 futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x55dc3b607de8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55dc3b607d98, cond=0x55dc3b607dc0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55dc3b607dc0, mutex=0x55dc3b607d98) at pthread_cond_wait.c:647 #3 0x00007fd06e61d84b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x00007fd06e61d44b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x00007fd07ab68609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #6 0x00007fd07b480293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fd06dc59700 (LWP 2216)): #0 futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x55dc3b607de8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55dc3b607d98, cond=0x55dc3b607dc0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55dc3b607dc0, mutex=0x55dc3b607d98) at pthread_cond_wait.c:647 #3 0x00007fd06e61d84b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x00007fd06e61d44b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x00007fd07ab68609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #6 0x00007fd07b480293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fd06e45a700 (LWP 2215)): #0 futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x55dc3b607de8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55dc3b607d98, cond=0x55dc3b607dc0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55dc3b607dc0, mutex=0x55dc3b607d98) at pthread_cond_wait.c:647 #3 0x00007fd06e61d84b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x00007fd06e61d44b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x00007fd07ab68609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #6 0x00007fd07b480293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fd074fdf700 (LWP 2214)): #0 futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x55dc3b607de8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55dc3b607d98, cond=0x55dc3b607dc0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55dc3b607dc0, mutex=0x55dc3b607d98) at pthread_cond_wait.c:647 #3 0x00007fd06e61d84b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x00007fd06e61d44b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x00007fd07ab68609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #6 0x00007fd07b480293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fd075d8f700 (LWP 2179)): #0 0x00007fd07b473aff in __GI___poll (fds=0x7fd068004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007fd079d7936e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fd079d794a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fd07bb91fcb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007fd07bb3625b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007fd07b94fc22 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007fd07bdf3f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x00007fd07b950dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007fd07ab68609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #9 0x00007fd07b480293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fd076ac0700 (LWP 2154)): #0 0x00007fd07b473aff in __GI___poll (fds=0x7fd076abfae8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007fd07dfaec1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x00007fd07dfb090a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x00007fd0771dbe58 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x00007fd07b950dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007fd07ab68609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #6 0x00007fd07b480293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fd0778e59c0 (LWP 2125)): [KCrash Handler] #4 QString::QString (other=..., this=0x7ffe4fac8d50) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1093 #5 Latte::Layout::AbstractLayout::name (this=0x0) at ./app/layout/abstractlayout.cpp:204 #6 0x000055dc3a2f60ef in Latte::Layouts::Synchronizer::currentLayoutsNames (this=<optimized out>) at ./app/layouts/synchronizer.cpp:202 #7 0x000055dc3a2e1a56 in Latte::Layouts::Manager::currentLayoutsNames (this=<optimized out>) at ./app/layouts/manager.cpp:155 #8 0x000055dc3a342842 in Latte::Settings::Controller::Layouts::initLayouts (this=this@entry=0x55dc3bb82ac0) at ./app/settings/settingsdialog/layoutscontroller.cpp:582 #9 0x000055dc3a343d2d in Latte::Settings::Controller::Layouts::Layouts (this=0x55dc3bb82ac0, parent=<optimized out>) at ./app/settings/settingsdialog/layoutscontroller.cpp:75 #10 0x000055dc3a362c44 in Latte::Settings::Handler::TabLayouts::TabLayouts (this=0x55dc3b90d9d0, parent=<optimized out>) at ./app/settings/settingsdialog/tablayoutshandler.cpp:880 #11 0x000055dc3a35470a in Latte::Settings::Dialog::SettingsDialog::SettingsDialog (this=0x55dc3b722530, parent=<optimized out>, corona=<optimized out>) at ./app/settings/settingsdialog/settingsdialog.cpp:69 #12 0x000055dc3a2e1c83 in Latte::Layouts::Manager::showLatteSettingsDialog (this=0x55dc3b6f50d0, firstPage=0, toggleCurrentPage=<optimized out>) at ./app/layouts/manager.cpp:398 #13 0x000055dc3a2a472d in Latte::Corona::showSettingsWindow (this=<optimized out>, page=<optimized out>) at ./app/lattecorona.cpp:1126 #14 0x000055dc3a40c713 in LatteDockAdaptor::showSettingsWindow (page=<optimized out>, this=0x55dc3b746000) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:425 #15 LatteDockAdaptor::qt_static_metacall (_o=_o@entry=0x55dc3b746000, _id=_id@entry=10, _a=_a@entry=0x7ffe4fac90f0, _c=QMetaObject::InvokeMetaMethod) at ./obj-x86_64-linux-gnu/app/lattedockadaptor.moc:199 #16 0x000055dc3a40c981 in LatteDockAdaptor::qt_static_metacall (_a=0x7ffe4fac90f0, _id=10, _c=QMetaObject::InvokeMetaMethod, _o=0x55dc3b746000) at ./obj-x86_64-linux-gnu/app/lattedockadaptor.moc:241 #17 LatteDockAdaptor::qt_metacall (this=0x55dc3b746000, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7ffe4fac90f0) at ./obj-x86_64-linux-gnu/app/lattedockadaptor.moc:241 #18 0x00007fd07be0055b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #19 0x00007fd07be059e7 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #20 0x00007fd07be05de0 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #21 0x00007fd07be0901c in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #22 0x00007fd07bb652f9 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x00007fd07c90ddc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x00007fd07c916bb8 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x00007fd07bb3775a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x00007fd07bb3a061 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x00007fd07bb92957 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x00007fd079d7917d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x00007fd079d79400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x00007fd079d794a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x00007fd07bb91fb2 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x00007fd07bb3625b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x00007fd07bb3e414 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x000055dc3a27f216 in main (argc=<optimized out>, argv=<optimized out>) at ./app/main.cpp:313 [Inferior 1 (process 2125) 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!
I can confirm that latte-dock v0.10.0 is broken. It's not functioning properly when started via KDE/Plasma Autostart. On login, the bottom half of the screen is blacked out and blocks any desktop functionality from mid-screen down. If you open a terminal and kill the latte-dock process, all desktop functionality returns. You can then start latte-dock from the system menu, and it starts and functions as expected. I have tried clearing the qmlcache, rebuilding the package in my build environment, building the master version from github, autostarting from xdg and attempted to start it from session restore. None of these approaches fix the problem. I have not found any evidence that the latte-dock process has crashed, it's simply interfering with the normal desktop startup. I have checked the logs for any sign of crashes - I haven't found any. I did note that my build of the master code did produce a drkonqi process which I have never been able to access.
In the crash topic this is fixed
(In reply to Jeff Hodd from comment #1) > I can confirm that latte-dock v0.10.0 is broken. It's not functioning > properly when started via KDE/Plasma Autostart. On login, the bottom half of > the screen is blacked out and blocks any desktop functionality from > mid-screen down. If you open a terminal and kill the latte-dock process, all > desktop functionality returns. You can then start latte-dock from the system > menu, and it starts and functions as expected. I have tried clearing the > qmlcache, rebuilding the package in my build environment, building the > master version from github, autostarting from xdg and attempted to start it > from session restore. None of these approaches fix the problem. I have not > found any evidence that the latte-dock process has crashed, it's simply > interfering with the normal desktop startup. I have checked the logs for any > sign of crashes - I haven't found any. I did note that my build of the > master code did produce a drkonqi process which I have never been able to > access. for the autostart issues: 1. You must make sure that the auto start desktop file used is updated properly 2. Remove all latte desktop files from: ~/.config/autostart/ 3. Add in ~/.config/autostart/ the new desktop file provided from Latte The crash comes when the system tries to autostart Latte more than two times.
[root@bslxenvy64 latte]# cd /home/jghodd/.config/autostart [root@bslxenvy64 autostart]# ll total 8 -rw------- 1 jghodd jghodd 590 Jun 16 2020 kdock-thunderbird.desktop -rw-r--r-- 1 jghodd jghodd 301 Sep 17 2020 megasync.desktop lrwxrwxrwx 1 jghodd jghodd 50 Aug 9 16:52 org.kde.latte-dock.desktop -> /usr/share/applications/org.kde.latte-dock.desktop Don't need to reset my autostart. I use a symlink, so it's always pointing to whatever was most recently installed. The only time I found a double-start was if I logged out and logged back in without killing the latte-dock process before doing so.
Created attachment 140663 [details] Screenshot after login First of 3 screenshots.
Created attachment 140664 [details] 2 of 3 - locate and kill single instance of latte-dock. Desktop restored Shows the terminal where I locate the latte-dock process and kill it, showing how it clears the desktop.
Created attachment 140665 [details] 3 of 3 - same session - restart of latte-dock from sys menu Restart latte-dock from the system menu. It seems as if instead of a double-start, it may be starting too early. I only ever find one running instance.
BTW, this is not resolved or fixed. I see the same issue with your master code base, so whatever the issue is, it's still there. I had a similar issue a few months ago with plasma, and it turned out the plasma developer who helped out found that components were being started before the corona startup was complete. Same issue here perhaps?
(In reply to Jeff Hodd from comment #8) > BTW, this is not resolved or fixed. I see the same issue with your master > code base, so whatever the issue is, it's still there. > > I had a similar issue a few months ago with plasma, and it turned out the > plasma developer who helped out found that components were being started > before the corona startup was complete. Same issue here perhaps? Open a new topic, with details etc. The topic about the crash is fixed. Your topic is different.