Bug 262592 - Panel visibility settings work wrong
Summary: Panel visibility settings work wrong
Status: RESOLVED DUPLICATE of bug 258012
Alias: None
Product: plasma4
Classification: Unmaintained
Component: containment-panel (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-08 22:03 UTC by Nikolay Rysev
Modified: 2011-04-05 09:30 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolay Rysev 2011-01-08 22:03:28 UTC 
Version:           unspecified (using KDE 4.5.95) 
OS:                Linux

Both "Auto-hide" and "Windows can cover" options work as "Windows go below".

I get "Windows can cover" option to work once, but it breaked after some windows manipulations.

AFAIK, betas of 4.6 not affected.

Reproducible: Always

Steps to Reproduce:
- Unlock widgets
- Go to "More settings" of default panel
- Choose "Auto-hide" or "Windows can cover"

Actual Results:  
There are no difference with "Windows go below"


I tested with default settings and clean profile, results are same.
Comment 1 Marco Martin 2011-01-10 18:44:02 UTC 
can't seem to be reproduceable in trunk. can somebody else confim it?
Comment 2 Nikolay Rysev 2011-01-10 19:24:25 UTC 
Is auto-hide works for you?

Also, panel looks as garbage if I set left/right screen edge (with o w/o compositing). With top/bottom it looks fine.
Comment 3 Nikolay Rysev 2011-01-30 10:51:54 UTC 
4.6 release, bug still present.
Comment 4 Nikolay Rysev 2011-02-05 10:37:23 UTC 
Anybody here? :)

I tried on opensuse 11.4m6 — same results.
Comment 5 Nikolay Rysev 2011-03-05 09:54:34 UTC 
4.6.1 — nothing changed.
Comment 6 Nikolay Rysev 2011-03-25 14:24:22 UTC 
Trunk doesn't affected, only stable 4.6.x branch.
Comment 7 Nikolay Rysev 2011-04-05 09:30:55 UTC 

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