Summary: | Layout broken after upgrademakes Plasma Panel unworkable (reconfiguration does not help) | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Bernhard E. Reiter <bernhard> |
Component: | Panel | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | lemmyg, nate, niccolo.venerandi |
Priority: | NOR | ||
Version: | 5.24.90 | ||
Target Milestone: | 1.0 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Screenshot of typical broken layout after upgrade (and login) |
Description
Bernhard E. Reiter
2022-06-11 16:12:55 UTC
this is tricky to reproduce. I have been testing new panels in 5.25.90 and 5.25.0 I didn't notice any layout change. I know that there is a know issue when panel have many icons and it cant resize them properly and suddenly they disappear. I work around for this is to change the height until they have enough space and the problem disappear. https://bugs.kde.org/show_bug.cgi?id=447603 In your case, I would say that could be due new settings problem. Maybe related to the actual distribution. Did you try to recreate the panel? Operating System: Kubuntu 21.10 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-48-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060/PCIe/SSE2 Regards Galder > I have been testing new panels in 5.25.90 and 5.25.0 I didn't notice any layout change. Note that the problem was observed after I've upgraded from 5.24.5 to 5.24.90. (I am not 100% sure, this is guess work from the upgrade log, I want to avoid going back, if possible and I am not sure I could if I wanted to.) > I work around for this is to change the height until they have enough space and the problem disappear. I've tried to change the height. In my case, elements just do not stay where I want to position them, they slide to the left or vanish again. > In your case, I would say that could be due new settings problem. Maybe related to the actual distribution. > Did you try to recreate the panel? Yes, with mixed results. So it was not satisfactory and after restarting I had the same problem. hello, try deleting the following files rm ~/.config/plasma-org.kde.plasma.desktop-appletsrc rm ~/.config/plasmashellrc then remove the panel create new one and restart the session > try deleting the following files
> rm ~/.config/plasma-org.kde.plasma.desktop-appletsrc
> rm ~/.config/plasmashellrc
>
> then remove the panel
> create new one and restart the session
This got me my sane behaviour back, thanks for the instructions.
(a little bit strange was, that the "standard panel" had most stuff backwarts, e.g. the starter to the right, where I would have expected it left. But I could manually move things to places now.)
I suspect the second monitor which is only sometimes connected maybe a factor in reproducing the issue.
The setup here is that if my second monitor is connected, it becomes primary and the secondary screen has a simple panel
only displaying the windows there.
I hope that other people do not run in the problem when doing an upgrade
(as I am running the "beta" versions, the whole idea is to find problems and resolve them before other users do).
It is working for me now, after manual steps.
So how do we contine with the issue?
Glad to hear that is solved for you now.
>>>>>>(as I am running the "beta" versions, the whole idea is to find problems and resolve them before other users do).
Yeah but if we cant reproduce the issue properly is hard to get developers attention.
I know that some issues introduced in 5.24.5 has been solved for 5.25.0.(to be released on 14th of June)
I would just resolve the ticket and if you have same problem in 5.25.0, feel free to reopen it again.
Regards,
Galder
Looping Nate, Maybe he already knows an existing issue with panel layouts. Yes, this unfortunate regression in the beta has already been fixed in the 5.25 final release. *** This bug has been marked as a duplicate of bug 454105 *** thanks Nate Thanks Nate, thanks Galder! (Hmm I wonder why I didn't see the previous report, maybe because it was already fixed and resolved, making a mental note to check the resolved issues explicitly next time.) |