Bug 394626 - Application Launcher doesn't draw Favourites properly when opened for the first time since start.
Summary: Application Launcher doesn't draw Favourites properly when opened for the fir...
Status: RESOLVED DUPLICATE of bug 395390
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Launcher (Kickoff) (show other bugs)
Version: 5.12.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-23 17:27 UTC by Maciej Mrozowski
Modified: 2018-07-26 01:43 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot illustrating the problem (18.43 KB, image/png)
2018-05-23 17:30 UTC, Maciej Mrozowski
Details
When the bar is on the left, the Favorites menu is upper-offset (103.95 KB, image/png)
2018-07-19 12:34 UTC, JLSalvador
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Mrozowski 2018-05-23 17:27:50 UTC
Steps to reproduce:

1. $ kquiapp5 plasmashell
2. $ plasmashell
3. Open Application Launcher menu (see attached screenshot)
Favourites are not loaded or they are loaded but are not rendered properly. They are only visibly inserted (or moved by some layout manager) once some other menu is selected (Applications, Computer, etc).

This has this annoying effect, that whoever uses muscle memory to navigate Application Launcher, it will always fail first for the time AL is used since it's started.
Comment 1 Maciej Mrozowski 2018-05-23 17:30:10 UTC
Created attachment 112838 [details]
screenshot illustrating the problem

Regression must have been introduced very recently, 5.12.4 or 5.12.3 didn't have it.
Comment 2 JLSalvador 2018-07-19 12:34:11 UTC
Created attachment 114012 [details]
When the bar is on the left, the Favorites menu is upper-offset

I can confirm this behaviour on 5.13.3 (Archlinux).

When the bar is on the left, the Favorites menu is upper-offset.
Comment 3 Patrick Silva 2018-07-26 01:43:50 UTC

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