Bug 424722 - Latte docks/panels unresponsive after updating
Summary: Latte docks/panels unresponsive after updating
Status: RESOLVED DUPLICATE of bug 406580
Alias: None
Product: lattedock
Classification: Plasma
Component: application (show other bugs)
Version: git (master)
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Michail Vourlakos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-27 20:20 UTC by rayholmium
Modified: 2020-08-21 00:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rayholmium 2020-07-27 20:20:05 UTC
SUMMARY

Latte docks/panels unresponsive after updating

STEPS TO REPRODUCE
1. build latte from master
2. run application
3. attempt to interact with icons/widgets

OBSERVED RESULT

docks and panels do not respond to left clicks or right clicks. settings can still be accessed via meta + a, but it only applies to the primary panel and there is no way to edit secondary dock.

the behaviour seems similar to a plasma-framework mismatch as described in the latte dock FAQ, but if I understand correctly this should not be an issue when building from master?

EXPECTED RESULT

Docks/panels fully clickable and editable. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.7.10-arch1-1
(available in About System)
KDE Plasma Version: 5.19.3
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
Comment 1 rayholmium 2020-08-14 03:53:33 UTC
Update: Panels are now working, but docks are still frozen.

Since my last post, I have:

- tested version 0.9.11 (working perfectly)
- reinstalled latte master to most recent
- cleared all latte caches and configs
- updated other packages, though I don't believe that included any kde frameworks

I've managed to rebuild my setup with just panels and am content with that, though am curious what might be causing the frozen dock issue.
Comment 2 rayholmium 2020-08-21 00:31:49 UTC
I'm a dummy and had set PLASMA_USE_QT_SCALING=1 which has already been addressed here:

https://bugs.kde.org/show_bug.cgi?id=406580
Comment 3 rayholmium 2020-08-21 00:32:27 UTC

*** This bug has been marked as a duplicate of bug 406580 ***