Created attachment 191315 [details] Screenshot showing the problem Steps to reproduce: 1) In Impress, create a blank document 2) Insert a table (any size) 3) Enter text in the first cell 4) Select text and right-click to open context menu 5) Go to the "Size" entry and notice that the submenu opens with wrong entries (there are empty lines and some commands should not be visible) This problem only occurs in master using kf5 or gen. Problem present in: Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 07036eea5089feae511145412d7105cb76c1955a CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL threaded Not present in: Version: 7.6.3.2 (X86_64) / LibreOffice Community Build ID: 60(Build:2) CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 4:7.6.3-0ubuntu0.23.10.1~lo1 Calc: threaded
Asking myself: Is this related to LibreOffice Dark Appearence? (Tools -> Options > View > Appearance). Font being black on black or is it truly an empty line
Another possibility bug 158101
Created attachment 191628 [details] test_7641_version_linux I would say it is ok with 7.6.4.1 as well: Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 16; OS: Linux 6.6; UI render: default; VCL: kf5 (cairo+xcb) Locale: es-ES (es_ES.UTF-8); UI: es-ES Calc: threaded openSUSE Tumbleweed.
(In reply to Raúl Osuna from comment #3) > I would say it is ok with 7.6.4.1 as well: It is OK in 7.6 indeed... the problem was introduced in 24.2. Also present in current master: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 8c822b764b35a0116a0865e991a87c8315e005ab CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL threaded
Actually disabled items are being shown in all menus when using non-GTK backends. Hence, this is a duplicate of bug 158101. *** This bug has been marked as a duplicate of bug 158101 ***