Bug 389025

Summary: menu items become invisible when using a custom shortcuts scheme
Product: [Applications] krita Reporter: jdreske
Component: UsabilityAssignee: Halla Rempt <halla>
Status: RESOLVED FIXED    
Severity: normal CC: halla, scottpetrovic, storm.anthro
Priority: NOR Keywords: regression, release_blocker
Version First Reported In: 4.0.0-beta.1   
Target Milestone: ---   
Platform: macOS (DMG)   
OS: macOS   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: screenshot osx menu

Description jdreske 2018-01-15 20:11:21 UTC
Created attachment 109892 [details]
screenshot osx menu

In Krita 4.0.0 beta.1 (and pre-alpha) a lot of menu entries are invisible.
The text and vector tools look promising but i'm not able to investigate further because a lot of menu entries are missing.
Comment 1 Scott Petrovic 2018-01-15 22:09:03 UTC
have you tried clearing your kritarc file. This is a settings file that is shared between multiple Krita versions. There is something in the 3.x version that is messing up 4.0

https://docs.krita.org/KritaFAQ#Resetting_Krita_configuration
Comment 2 jdreske 2018-01-16 10:10:02 UTC
Deleting these files worked. great!
Comment 3 jdreske 2018-01-16 10:44:01 UTC
Sorry - on reopening Krita4 the menues were partly invisible again.
I found out that the problem occurs when I change the shortcut scheme to my custom scheme. When I set it to default before closing the menues load properly.
best regards
Comment 4 Halla Rempt 2018-01-17 11:06:24 UTC
Yes, I can confirm the issue and that it is bound up to using a custom shortcuts scheme.
Comment 5 Halla Rempt 2018-01-18 09:55:32 UTC
Git commit 08e641f68ebae56b3e537f8ba156d55ae7748303 by Boudewijn Rempt.
Committed on 18/01/2018 at 09:54.
Pushed by rempt into branch 'master'.

Load the action info objects even if there's a custom shortcut scheme

M  +3    -2    libs/widgetutils/kis_action_registry.cpp

https://commits.kde.org/krita/08e641f68ebae56b3e537f8ba156d55ae7748303
Comment 6 Alvin Wong 2018-01-18 13:09:34 UTC
*** Bug 384774 has been marked as a duplicate of this bug. ***