https://bugs.kde.org/show_bug.cgi?id=500729
--- Comment #2 from JMB9 <jmb_...@gmx.net> --- I still hope to reproduce it and aimed at making a video with vokoscreenNG to help in reproducing the problem. At 1st I thought the entire configuration would be lost - but when moving "okular" to "OLD_bad_menue_OLD_okular_OLD" in the directory "~/.local/share/kxmlgui5", the menu works as described but all I configured in Settings and okular_part was still there - but just okular_shell was empty - so I changed that - and the menu stays ok. So this seems to be a valid workaround ... but not a point I could start to search for a trigger event so the problem could finally be reproduced. If I remember correctly the breakage of the menu happens quite fast when starting changing okular_part - i.e. putting several things from left to right to make it visible in the toolbar, changing order and deleting a few by putting them from right to left. And that happened reliably in freshly installed KDE neon ... Is it possible to move away all okular configs so I start as if okular was not yet configured in any way (especially losing the config of "okular_part" - as I suspect something here must be the trigger)? With that point I could configure it and if any "no text" label in the menu appears, I should have found a valid trigger ... and can provide the video ... Just out of curiosity: Why is the label "No text" no point to start for finding the problem? I thought it is a label to debug if a label was left empty which should not happen for a menu point ... or what is the use of "No text"? -- You are receiving this mail because: You are watching all bug changes.
