I installed master version (2 days ago) of latte-dock by making my own openSUSE repo. https://build.opensuse.org/package/show/home:andythe_great:branches:KDE:Extra/latte-dock-git However, sometime it just crash with no warning. I ran latte-dock with this command. env QV4_FORCE_INTERPRETER=1 latte-dock -d Which when it crash, it show this. ... [Debug : 2:06:23.762762] - "syncGeometry() calculations for edge: Plasma::Types::BottomEdge" [Debug : 2:06:23.762762] - "syncGeometry() ended..." [Warning : 2:06:24.216216] - "KAStatsFavoritesModel::setFavorites is ignored" [Warning : 2:06:24.258258] - "trying to show an empty dialog" [Debug : 2:06:24.265265] - "DOCK VIEW FROM LAYOUT ::: \"Plasma\" - activities: (\"{0}\")" [Debug : 2:06:24.274274] - "immediateSyncGeometry() called..." [Debug : 2:06:24.274274] - "syncGeometry() calculations for screen: \"VGA-1\" _ QRect(0,0 1920x1080)" [Debug : 2:06:24.274274] - "syncGeometry() calculations for edge: Plasma::Types::TopEdge" [Debug : 2:06:24.274274] - "syncGeometry() ended..." [Debug : 2:06:24.384384] - " PLASMA STRUTS MANAGER :: is available..." [Warning : 2:06:24.458458] - "No object for name \"alsa_output.pci-0000_00_1b.0.analog-stereo.monitor\"" [Debug : 2:06:25.351351] - " PLASMA SCREEN GEOMETRIES, LAST AVAILABLE SCREEN RECTS :: QHash()" [Debug : 2:06:25.351351] - " PLASMA SCREEN GEOMETRIES, SCREEN :: 10 - \"VGA-1\"" [Debug : 2:06:25.354354] - " PLASMA SCREEN GEOMETRIES, AVAILABLE RECT :: \"VGA-1\" : QRect(0,37 1920x1043)" [Debug : 2:06:25.355355] - " PLASMA SCREEN GEOMETRIES, AVAILABLE REGION :: \"VGA-1\" : QRegion(0,37 1920x1043)" [Debug : 2:06:26.654654] - "Loading visibility mode: Latte::Types::DodgeActive on startup..." [Debug : 2:06:27.654654] - " PLASMA SCREEN GEOMETRIES, LAST AVAILABLE SCREEN RECTS :: QHash((\"VGA-1\", QRect(0,37 1920x1043)))" [Debug : 2:06:27.654654] - " PLASMA SCREEN GEOMETRIES, SCREEN :: 10 - \"VGA-1\"" [Debug : 2:06:27.657657] - " PLASMA SCREEN GEOMETRIES, AVAILABLE RECT :: \"VGA-1\" : QRect(0,37 1920x1018)" [Debug : 2:06:27.658658] - " PLASMA SCREEN GEOMETRIES, AVAILABLE REGION :: \"VGA-1\" : QRegion(size=2, bounds=(0,37 1920x1043) - [(0,37 1920x1017), (0,1079 1920x1)])" Segmentation fault (core dumped) Which does not show any useful error. I could not use ddd since it has been removed from openSUSE Tumbleweed. Any suggestion to get more backtrace? Thank you. Operating System: openSUSE Tumbleweed 20200917 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.1 Kernel Version: 5.8.7-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000
I got the similar problem in kubuntu groovy beta. Latte is okay in kubuntu focal running kernel 5.8.14 When start up in konsole, it crashed and gave the following message KCrash: Attempting to start /usr/bin/latte-dock KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = latte-dock path = /usr/bin pid = 49048 KCrash: Arguments: /usr/bin/latte-dock KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi Using ddd and backtrace give the following text. Thread 1 "latte-dock" received signal SIGSEGV, Segmentation fault. 0x00005555555e1fde in ?? () #6 0x0000555555588a9e in _start () #5 0x00007ffff55a0cb2 in __libc_start_main (main=0x5555555870c0, argc=1, argv=0x7fffffffdcd8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdcc8) at ../csu/libc-start.c:314 #4 0x0000555555588363 in ?? () #3 0x00005555555a18b3 in ?? () #2 0x00005555555e5c15 in ?? () #1 0x00005555555e5752 in ?? () #0 0x00005555555e1fde in ?? () I am not a technical guy and have no idea on this bug
https://userbase.kde.org/LatteDock/HowToReportCrashes
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
(In reply to Samson from comment #1) > I got the similar problem in kubuntu groovy beta. Latte is okay in kubuntu > focal running kernel 5.8.14 > When start up in konsole, it crashed and gave the following message > > KCrash: Attempting to start /usr/bin/latte-dock > KCrash: crashing... crashRecursionCounter = 2 > KCrash: Application Name = latte-dock path = /usr/bin pid = 49048 > KCrash: Arguments: /usr/bin/latte-dock > KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi > > Using ddd and backtrace give the following text. > > Thread 1 "latte-dock" received signal SIGSEGV, Segmentation fault. > 0x00005555555e1fde in ?? () > > > #6 0x0000555555588a9e in _start () > #5 0x00007ffff55a0cb2 in __libc_start_main (main=0x5555555870c0, argc=1, > argv=0x7fffffffdcd8, init=<optimized out>, fini=<optimized out>, > rtld_fini=<optimized out>, stack_end=0x7fffffffdcc8) at > ../csu/libc-start.c:314 > #4 0x0000555555588363 in ?? () > #3 0x00005555555a18b3 in ?? () > #2 0x00005555555e5c15 in ?? () > #1 0x00005555555e5752 in ?? () > #0 0x00005555555e1fde in ?? () > > I am not a technical guy and have no idea on this bug From my latest test, it was likely due to "Event Calendar" widgets, try remove it if you have one.
waiting proper crash report