Bug 462478 - latte-dock crashes at startup randomly
Summary: latte-dock crashes at startup randomly
Status: REPORTED
Alias: None
Product: lattedock
Classification: Plasma
Component: application (show other bugs)
Version: 0.10.8
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Michail Vourlakos
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-12-01 07:07 UTC by tnemeth
Modified: 2022-12-01 07:34 UTC (History)
0 users

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 tnemeth 2022-12-01 07:07:09 UTC
Application: latte-dock (0.10.8)

Qt Version: 5.15.6
Frameworks Version: 5.100.0
Operating System: Linux 6.0.0-4-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux bookworm/sid
DrKonqi: 5.26.3 [KCrashBackend]

-- Information about the crash:
There is not enough information in the logs to find out why it crashes. This happens at startup but not all the time which is confusing. Theres' too much shit in ~/.xsession-errors (nobody seems to clean what's output from their apps and a lot of "debug" stuiff can be found here) but a simple grep displays :

```
kdeinit5: Got EXEC_NEW '/usr/bin/latte-dock' from launcher.
kdeinit5: preparing to launch '/usr/bin/latte-dock'
org.kde.plasma.session: Starting autostart service  "/home/thomas/.config/autostart/org.kde.latte-dock.desktop" ("/usr/bin/latte-dock")
"An instance is already running!, use --replace to restart Latte"
grep: .xsession-errors : binary file matches
```

There are still some latte process found in `ps` :
```
thomas    327529  2.2  0.6 2063056 228444 ?      Tsl  07:49   0:14 /usr/bin/latte-dock
thomas    328346  0.0  0.0      0     0 ?        Z    07:49   0:00 [latte-dock] <defunct>
```

So it seems a previous instance was running when Latte is started through SystemSettings configuration which was the documented way to start it.
Killing remnants manually and starting it again (still manually) makes it work again.

(I hope Markdown is supported in the comments).

The crash can be reproduced sometimes.

-- Backtrace:
Application: Latte Dock (latte-dock), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f605c2beb0e in ?? () from /lib/x86_64-linux-gnu/libKF5ActivitiesStats.so.1
#5  0x00007f6094ed44a3 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x00007f6094ca7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x00007f6094d2866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6

Thread 10 (Thread 0x7f6047e546c0 (LWP 328189) "latte-dock"):
#1  0x00007f6092e0ba62 in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6
#2  0x00007f6092e0ce60 in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6
#3  0x00007f6094ca7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x00007f6094d2866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6

Thread 9 (Thread 0x7f605d5ff6c0 (LWP 327701) "QQmlThread"):
#1  0x00007f6093b899ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f6093b89acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f60955094ce in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f60954b019b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f60952cab17 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f6096f283e5 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x00007f60952cbcd1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f6094ca7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#9  0x00007f6094d2866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6

Thread 8 (Thread 0x7f607ddfc6c0 (LWP 327680) "QQmlThread"):
#1  0x00007f6093b899ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f6093b89acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f60955094ce in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f60954b019b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f60952cab17 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f6096f283e5 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x00007f60952cbcd1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f6094ca7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#9  0x00007f6094d2866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6

Thread 7 (Thread 0x7f607e5fd6c0 (LWP 327617) "QDBusConnection"):
#1  0x00007f6093b899ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f6093b89acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f60955094ce in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f60954b019b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f60952cab17 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f6095f1a487 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007f60952cbcd1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f6094ca7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#9  0x00007f6094d2866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6

Thread 6 (Thread 0x7f607edfe6c0 (LWP 327604) "latte-dock:sh2"):
#1  0x00007f6094ca73f8 in pthread_cond_wait () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f608d507699 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3  0x00007f608d4bc74b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4  0x00007f608d5075d7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5  0x00007f6094ca7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#6  0x00007f6094d2866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6

Thread 5 (Thread 0x7f607f5ff6c0 (LWP 327603) "latte-dock:sh1"):
#1  0x00007f6094ca73f8 in pthread_cond_wait () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f608d507699 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3  0x00007f608d4bc74b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4  0x00007f608d5075d7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5  0x00007f6094ca7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#6  0x00007f6094d2866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7f608c9116c0 (LWP 327602) "latte-dock:sh0"):
#1  0x00007f6094ca73f8 in pthread_cond_wait () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f608d507699 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3  0x00007f608d4bc74b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4  0x00007f608d5075d7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5  0x00007f6094ca7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#6  0x00007f6094d2866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f608d1126c0 (LWP 327601) "latte-d:disk$0"):
#1  0x00007f6094ca73f8 in pthread_cond_wait () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f608d507699 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3  0x00007f608d4bc74b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4  0x00007f608d5075d7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5  0x00007f6094ca7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#6  0x00007f6094d2866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7f608ffff6c0 (LWP 327563) "QXcbEventQueue"):
#1  0x00007f60979a0d12 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f60979a307a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f60902facb0 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f60952cbcd1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f6094ca7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#6  0x00007f6094d2866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f6090c90f00 (LWP 327529) "latte-dock"):
#1  0x00007f6094ca73f8 in pthread_cond_wait () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f60952d199b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007f609740b968 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x00007f609740cc23 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x00007f60959495b5 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#6  0x00007f6096162f5e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x00007f60954b1718 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f609593e73d in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#9  0x00007f6095911e1c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#10 0x00007f60902fbc7a in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#11 0x00007f6093b897a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f6093b89a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007f6093b89acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007f60955094b6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f60954b019b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f60954b8306 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x0000559f6e7474f5 in ?? ()
#18 0x00007f6094c4618a in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#19 0x00007f6094c46245 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#20 0x0000559f6e74e3aa in _start ()
[Inferior 1 (process 327529) detached]

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

Reported using DrKonqi
Comment 1 tnemeth 2022-12-01 07:34:36 UTC
The contents of ~/.xsession-errors should not be taken into account. After check, the file was 2GB large... As there is no timestamp, it's impossible to find out when those lines were output.