When attempting to resize the Settings Manager window, you can resize height-wise in both directions. However, when resizing width-wise, you can only make the window grow, it will not shrink. You need to either use xfconf-query to affect the /last/window-width setting (while the manager is not running) or delete the xfce4-settings-manager.xml to reset to default.
Version: 0.12.11
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
When you open the settings manager you get the overview of all the setting items, like appearance, panel and desktop.
If I resize the window horizontally (make it larger) or maximize it, the items in the personal, hardware, system and others group are rearranged in the groups to fit in fewer lines.
Resizing the window back to a smaller state is not possible, I think because the rearrangement in the other direction doesn't work.
It is possible to resize the window when you enter a search term like 'xx', which is no fix but a workaround to get the original size back.
My setup:
xfce4-settings-manager 4.14.2 (Xfce 4.14)
The attached diff combines the fixes for bug 14737 and bug 13402 by making them conditional (only xfce4-settings-manager is assigning a value to item_width).
For those who happen to come across this and haven't gotten a fix, the simple GUI-based workaround which doesn't require editing text files is shown in my duplicate issue xfce4-settings#192 (closed). Here is how.
click on one of the setting manager entries (e.g. display)
I confirm the problem on Ubuntu Studio 20.04/20.10 with xfce4-settings-manager 4.14.3 (Xfce 4.14).
If I maximize or enlarge the window, I cannot reduce its width. Also if I move the window from one display to another (they are arranged one below the other), the window expands to the width of the screen, and the problem appears.
Both quick workaround solutions temporarily fix the problem: