| Summary: | Trying to add a new widget to the desktop leads to an empty desktop with default settings. | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Christian Krippendorf <CerebrosuS> |
| Component: | Containment | Assignee: | Sebastian Kügler <sebas> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kde, rouphen |
| Priority: | NOR | ||
| Version First Reported In: | 5.6.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Christian Krippendorf
2016-05-05 11:52:20 UTC
This bug is biting me since the first versions of Plasma 5. As Christian Krippendorf stated, it's perfectly reproducible following the indicated steps. I have a dual-monitor setup, mirrored (my desktop is shown in both screens, duplicated), and this bug only happens once per session. After rebooting or relogin, the old desktop setting is back. Sometimes, however, it triggers in the background while changing the wallpaper/messing with certain widgets, or while I'm web browsing. Can't find any explanation on the Internet. Looks like you have two overlying desktop windows and the other one suddenly pops in front? Well, that is what I'm suspecting. Possibly, a part of the widget management triggers the switch by its own. A couple of days ago, for example, I was trying different wallpapers just for the sake of customization, minimizing the windows in order to look the desktop without obstacles and then restoring them back quickly... and it started to shift between my current settings and the Plasma defaults like crazy, especially while I was clicking the taskbar, navigating trough the wallpaper picker or just selecting a random icon placed in the desktop. Obviously, it's not a game breaker bug, but it's a little bit annoying; I think it twice before adding any widget now. I am not able to reproduce this bug with plasma 5.9.2 anymore. Because I still have the same system configuration and just the version changed I think the bug has been fixed with new releases. If no one is against marking this bug as closed, I will do so. Greetings |