Bug 374805 - Panel not autohiding when located between two monitors
Summary: Panel not autohiding when located between two monitors
Status: RESOLVED DUPLICATE of bug 351175
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.8.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
Depends on:
Reported: 2017-01-09 11:46 UTC by Rafael Linux User
Modified: 2017-01-11 00:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

My multimonitor configuration (57.10 KB, image/png)
2017-01-09 11:46 UTC, Rafael Linux User
Full desktop showing the not hided panel (deleted)
2017-01-09 12:18 UTC, Rafael Linux User

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael Linux User 2017-01-09 11:46:58 UTC
Created attachment 103304 [details]
My multimonitor configuration

Since I have Plasma 5, I have a big problem with my main desktop panel.
I have 2 monitors. I have my main panel on my bigger monitor, between my physically adjacent monitors. I always have my main panel attached to the left side of my main monitor with "autohide" enabled.

However, with Plasma 5, my main panel is not autohiding. Is always opened, despite "auto hide" is enabled. Each time my mouse pointer cross over this panel, momentarily (for a second) panel seems to hide and appears again.

This happens if this panel is located in the edge between monitors. It works fine when I place panel on any other side.

This was working fine with KDE 4.

Please, any fix for this?

Thank you
Comment 1 Rafael Linux User 2017-01-09 12:18:37 UTC
Created attachment 103305 [details]
Full desktop showing the not hided panel

Is this capture, we can see that when my panel is on the middel (left side of right monitor or right side of left monitor) the auto hide function is not working.
Comment 2 Ben Cooksley 2017-01-09 20:42:44 UTC
The content of attachment 103305 [details] has been deleted for the following reason:

Privacy removal request
Comment 3 Christoph Feck 2017-01-11 00:00:03 UTC

*** This bug has been marked as a duplicate of bug 351175 ***