| Summary: | Latte dock 0.9.97 crashes on startup | ||
|---|---|---|---|
| Product: | [Plasma] lattedock | Reporter: | kerossin |
| Component: | application | Assignee: | Michail Vourlakos <mvourlakos> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version: | 0.9.97 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
kerossin
2021-07-05 15:20:47 UTC
Habe you tried default layout? There is chance you are using a crashy applet. I'll do some testing by removing some applets and will try out the default one. I seemed to have fixed the problems for both of my computers. For my PC, when I went in to the layouts I saw that my layout had an extra dock with an error that I wasn't using. The error was: Error #E107: Orphaned Parent Applet Of Subcontainment In your layout there are orphaned pseudo applets that link to unexistent subcontainments. Such case is for example a systemtray that has lost connection with its child applets. Such situation can create crashes, abnormal behavior and data loss when you activate and use this layout. Pseudo Applets: • System Tray [#52] inside Latte Containment [#22] Orphaned Subcontainments: Possible Solutions: 1. Update manually the subcontainment id inside pseudo applet settings when the layout is not active 2. Remove this layout totally Deleting that dock seemed to get rid of the occasional crash. On my laptop, it seems a KDE setting was causing the problem. Startup and Shutdown > Desktop Session 'When logging in:' was set to 'Restore previous saved session' and whenever Latte would crash I'd find these lines together in the journal: 20:54:11 lenovo latte-dock[2605]: "An instance is already running!, use --replace to restart Latte" 20:54:11 lenovo latte-dock[3068]: "An instance is already running!, use --replace to restart Latte Like it was trying to launch 2-3 instances at once on startup. Changing the setting to 'Start with an empty session' seems to have fixed that. That is a good case that Layout Healer/Observer has helped... 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! |