Created attachment 178871 [details] Screenshot showing broken menu structure with 'no text' and my choice for toolbar - which may caused this *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY When I installed KDE neon Noble (several times due to new PC with booting problems - related to ASUS&Ubuntu 24.04 LTS plus NVMe which at least made the problem more severe) and configured it (while adding things to the toolbar I 1st spotted a 'no text' menu point - so I think that is directly related to the problem), all config changes directly result in a broken menu structure: there were menu points missing (one must rely on shortcuts etc.; like 'print' or 'configure toolbars') and some menue points are just showing "now text". I thought the next update may correct that - but it stays bugged for me. So there is something really strange going on - while I can work (with shortcuts - knowing okular quite well) - but it is an extreme annoyance. Why is this problem not visible for developers and can stay for so long? Would prefer communication in case this is not reproducable ... so that this is solved for all soon. STEPS TO REPRODUCE 1. Install okular 2. configure it (especially toolbars - see screenshot) 3. using okular and seeing that menu is a mess OBSERVED RESULT The menu structure is broken: 1) some labeled are missing but show 'no text' (I think this must be a fallback so this error should be easy to find). 2) menu points are no longer there: print - workaround: Ctrl|Strg-P, configure toolbars - workaround: right mouse click in toolbar etc.) I always had these full toolbar and that never caused any problem ... so there is something weird happening - and not catched even when okular was updated ... My 1st screenshot with that problem was on 14. Dec. 2024 - and I thought, such a big problem will just be solved with next release - but was not! EXPECTED RESULT Correct menu structure as with KDE 5 SOFTWARE/OS VERSIONS GNU/Linux: KDE neon 6.3 (freshly updated) (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: 6.3.1 KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 KDE Gears 24.12.2 Qt Version: 6.8.2 # Mesa from Ubuntu Noble HWE2 - Mesa: 24.2.8 # Linux from Ubuntu Mainline-PPA - Linux: 6.12.16 ADDITIONAL INFORMATION I just spotted the problem when installing KDE neon Noble-based on the new PC and configured ocular there - while the clones Jammy partition having already Plasma 6 had no problem - but it was configured on KDE Plasma 5 - so maybe the okular configuration is broken by new KDE 6 in a way it disrupts the menu structure ??? As KDE 6 created a huge pile of problems for my workflow, I am still thinking about some subtile changes causing this. But I am not sure that the problem is KDE related ... may just be intuition - especially as this problem got not solved, maybe most will not see it ?
This happens to people, but no one has been able to give us a way to reproduce it, so it remains unfixable for now. You can fix it locally by removing the files in ~/.local/share/kxmlgui5/okular (you will lose your customizations when you remove those files). If you find the exact customization steps that you that cause this breakage please tell us.
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"?
The part configuration is stored in ~/.local/share/kxmlgui5/okular/part.rc Are you sure removing that file doesn't reset the part configuration? > Just out of curiosity: Why is the label "No text" no point to start for finding the problem? We know it's broken, we don't know how it breaks, having a way to reproduce it is the key.
I was waiting for Ocular 25.4.0 to make a video to get a reproducible bug about the trashed menu. Unfortunately I was shocked when seeing a new bug in Ocular, that instead of cursor up/down just going to a previous/next entire page only getting some lines up/down, while the former behavour is now in cursor left/right. And to make it worse - also Page Up/Down does the stupid thing which does cursor up/down now. This is an extreme regression - ones again - and I am using faith in LDE developer fixing the mess KDE 6 was (incl. Framework, Gears etc.).
Updating status as this is pending steps to reproduce from the reporter.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME.