You are not logged in.
Latte-dock-git is crashing at startup.
coredumps logs :
PID: 676 (latte-dock)
UID: 1000 (chandan)
GID: 1000 (chandan)
Signal: 11 (SEGV)
Timestamp: Mon 2021-03-29 12:56:29 IST (8min ago)
Command Line: /usr/bin/latte-dock
Executable: /usr/bin/latte-dock
Control Group: /user.slice/user-1000.slice/session-2.scope
Unit: session-2.scope
Slice: user-1000.slice
Session: 2
Owner UID: 1000 (chandan)
Boot ID: 406568f4e6184bd99495593ff6c5a77d
Machine ID: c2955e1dca09471aa10c753e2269a126
Hostname: arch
Storage: /var/lib/systemd/coredump/core.latte-dock.1000.406568f4e6184bd99495593ff6c5a77d.676.1617002789000000.zst
Message: Process 676 (latte-dock) of user 1000 dumped core.
Stack trace of thread 676:
#0 0x00007f7df89beef5 raise (libc.so.6 + 0x3cef5)
#1 0x00007f7dfa6e8189 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x4189)
#2 0x00007f7df89bef80 __restore_rt (libc.so.6 + 0x3cf80)
#3 0x00005613597057e0 _ZN7QStringC4ERKS_ (latte-dock + 0x747e0)
#4 0x000056135972fcb5 _ZNK5Latte7Layouts12Synchronizer19currentLayoutsNamesEv (latte-dock + 0x9ecb5)
#5 0x000056135971a7b3 _ZNK5Latte7Layouts7Manager19currentLayoutsNamesEv (latte-dock + 0x897b3)
#6 0x000056135975aa53 _ZN5Latte8Settings10Controller7Layouts11initLayoutsEv (latte-dock + 0xc9a53)
#7 0x000056135975c7e4 _ZN5Latte8Settings10Controller7LayoutsC2EPNS0_7Handler10TabLayoutsE (latte-dock + 0xcb7e4)
#8 0x00005613597767ac _ZN5Latte8Settings7Handler10TabLayoutsC2EPNS0_6Dialog14SettingsDialogE (latte-dock + 0xe57ac)
#9 0x000056135976bfd4 _ZN5Latte8Settings6Dialog14SettingsDialogC2EP7QWidgetPNS_6CoronaE (latte-dock + 0xdafd4)
#10 0x000056135971af15 _ZN5Latte7Layouts7Manager23showLatteSettingsDialogEib (latte-dock + 0x89f15)
#11 0x00005613597ee8e1 _ZN16LatteDockAdaptor18qt_static_metacallEP7QObjectN11QMetaObject4CallEiPPv (latte-dock + 0x15d8e1)
#12 0x00007f7df93e9066 n/a (libQt5DBus.so.5 + 0x21066)
#13 0x00007f7df93ec65b n/a (libQt5DBus.so.5 + 0x2465b)
#14 0x00007f7df93eca8b n/a (libQt5DBus.so.5 + 0x24a8b)
#15 0x00007f7df93ef478 n/a (libQt5DBus.so.5 + 0x27478)
#16 0x00007f7df9155532 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e2532)
#17 0x00007f7df9e6e752 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a752)
#18 0x00007f7df9128a2a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b5a2a)
#19 0x00007f7df912b523 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b8523)
#20 0x00007f7df9182054 n/a (libQt5Core.so.5 + 0x30f054)
#21 0x00007f7df75d2f9c g_main_context_dispatch (libglib-2.0.so.0 + 0x53f9c)
#22 0x00007f7df7626a49 n/a (libglib-2.0.so.0 + 0xa7a49)
#23 0x00007f7df75d06f1 g_main_context_iteration (libglib-2.0.so.0 + 0x516f1)
#24 0x00007f7df9181691 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e691)
#25 0x00007f7df91273ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43ac)
#26 0x00007f7df912f844 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2bc844)
#27 0x00005613596cd73b main (latte-dock + 0x3c73b)
#28 0x00007f7df89a9b25 __libc_start_main (libc.so.6 + 0x27b25)
#29 0x00005613596ce03e _start (latte-dock + 0x3d03e)
Stack trace of thread 745:
#0 0x00007f7df82b79ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
#1 0x00007f7df82b1260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
#2 0x00007f7dee23438c n/a (i965_dri.so + 0x1c138c)
#3 0x00007f7dee233aa8 n/a (i965_dri.so + 0x1c0aa8)
#4 0x00007f7df82ab299 start_thread (libpthread.so.0 + 0x9299)
#5 0x00007f7df8a81053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 747:
#0 0x00007f7df75ce2b8 g_source_ref (libglib-2.0.so.0 + 0x4f2b8)
#1 0x00007f7df75d1419 n/a (libglib-2.0.so.0 + 0x52419)
#2 0x00007f7df75d2a5b g_main_context_prepare (libglib-2.0.so.0 + 0x53a5b)
#3 0x00007f7df76268f6 n/a (libglib-2.0.so.0 + 0xa78f6)
#4 0x00007f7df75d06f1 g_main_context_iteration (libglib-2.0.so.0 + 0x516f1)
#5 0x00007f7df91816ac _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6ac)
#6 0x00007f7df91273ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43ac)
#7 0x00007f7df8f3fd12 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd12)
#8 0x00007f7df93df098 n/a (libQt5DBus.so.5 + 0x17098)
#9 0x00007f7df8f40eff n/a (libQt5Core.so.5 + 0xcdeff)
#10 0x00007f7df82ab299 start_thread (libpthread.so.0 + 0x9299)
#11 0x00007f7df8a81053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 743:
#0 0x00007f7df82b79ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
#1 0x00007f7df82b1260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0
I'm using
latte-dock-git , with edna layout.
plasma sddm
kwin
NOTE: The default latte-dock is working fine but i want to use latte-dock-git for some extra features.
Any help would be appriciated, I'm tired of this issue from 2 weeks.
Offline
It is a package built from git. Since it doesn't follow releases, it is more unstable than latte-dock.
If you want it solved, you either keep updating it to the latest commit until it is fixed or you go upstream and report it.
Offline
It is a package built from git. Since it doesn't follow releases, it is more unstable than latte-dock.
If you want it solved, you either keep updating it to the latest commit until it is fixed or you go upstream and report it.
Yes it's build from git , it's up-to-date as per now .
But the thing that worries me that's , I used the same latte-dock-git version in garuda linux(arch fork) and it's working fine on my same laptop .
Anyhow where can I go and report it.
Offline
Did you try to move the config away?
https://aur.archlinux.org/packages/latte-dock-git/ links https://invent.kde.org/plasma/latte-dock where you can now find https://invent.kde.org/plasma/latte-dock/-/issues/59
If this is you or not, please provide the backtrace w/ debug symbols there.
Online
Moving to AUR issues.
Offline
Did you try to move the config away?
https://aur.archlinux.org/packages/latte-dock-git/ links https://invent.kde.org/plasma/latte-dock where you can now find https://invent.kde.org/plasma/latte-dock/-/issues/59
If this is you or not, please provide the backtrace w/ debug symbols there.
Tried moving configs aways. Still the issue remains .
Yes I posted that issue on latte-dock page.
Ok I'll add the backtrace logs too.
Last edited by cyborge (2021-03-29 13:11:18)
Offline
Is there any reason why you choose the git version? Latte Dock is quite stable in my system.
Offline
Is there any reason why you choose the git version? Latte Dock is quite stable in my system.
Neet it for some extra features , like edge margins
Offline