Created attachment 164885 [details] Screenshot of the window after adding an autostart script manually SUMMARY Looking at autostart, I cannot add/remove in there. When I add a .desktop script in ~/.config/autostart, it appears immediately, but when I click on it there is a message that is not visible (we just see the bottom of it, see attachment). STEPS TO REPRODUCE 1. Open autostart settings 2. Add a desktop file to ~/.config/autostart 3. Click on the new entry that appears OBSERVED RESULT The "Add button" does nothing The bottom of a message displayed when clicking on an entry added manually with a file is shown. EXPECTED RESULT - The Add button should do something or be greyed out and an explanation given on why it isn't activated. - If a message has to be displayed it needs to be entirely visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Latest KDE unstable in up to date archlinux KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.7.0 Wayland
The message being cut off is https://bugs.kde.org/show_bug.cgi?id=478891 The rest is hard to tell without actually seeing the message
I tried to resized and things in the window but could never get to see the text. I have noticed that I cannot add shortcuts either. There is a add button in the shortcuts settings, but it does nothing. I can add shortcuts in each of the individual modules, but this add button does nothing. (not sure if it is related)
(In reply to Jonathan Bisson from comment #2) > I tried to resized and things in the window but could never get to see the > text. > > I have noticed that I cannot add shortcuts either. There is a add button in > the shortcuts settings, but it does nothing. > I can add shortcuts in each of the individual modules, but this add button > does nothing. (not sure if it is related) `I tried to resize and move things`
ah, yes, the "Add" button should actually open a menu, but it doesn't
See https://bugs.kde.org/show_bug.cgi?id=479775
This is a Qt 6.7 bug: https://bugreports.qt.io/browse/QTBUG-121014
*** This bug has been marked as a duplicate of bug 478891 ***