SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. start Lokalize 2. 3. OBSERVED RESULT Lokalize opens The project overview tab opens The translation memory tab opens The tab in which a to-be-translated-file can be opened, but the content is not shown/drawn EXPECTED RESULT The to-be-translated-file should be visible SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
I can see it as well on Debian testing, both using the packaged lokalize (21.12.3) and the last version from git (23.03.70) using the packaged Frameworks (5.98.0) and Qt (5.15.6).
Created attachment 153686 [details] Broken Dockwidget screenshot
I'm a bit embarassed by this issue, it seems the dockwidget is not well supported in wayland. I'll try to find a solution, but if a complete re-write is required I don't have the capacity to do it.
But this is not about wayland, I see the issue on X11.
(In reply to Luigi Toscano from comment #4) > But this is not about wayland, I see the issue on X11. You are correct... Does your layout also gets broken when you just open/close project/translation-memory tabs without opening an actual file? The nightly build works fine on Windows with kde FW 5.99/qt 5.15.5 so that looks system specific. @LC Which distro are you using?
(In reply to Simon Depiets from comment #5) > (In reply to Luigi Toscano from comment #4) > > But this is not about wayland, I see the issue on X11. > > You are correct... > Does your layout also gets broken when you just open/close > project/translation-memory tabs without opening an actual file? > > The nightly build works fine on Windows with kde FW 5.99/qt 5.15.5 so that > looks system specific. > @LC Which distro are you using? Debian. I have seen this bug since many months (summer 2022). I am on experimental/sid/testing
*** Bug 463159 has been marked as a duplicate of this bug. ***