Unity

unity launcher wrong behaviour with _NET_WM_STRUT in another app

Bug #884648 reported by Dennis Schwertel on 2011-11-01

6

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Compiz	Confirmed	Low	Unassigned
	Unity	Confirmed	Low	Unassigned
	compiz (Ubuntu)	Confirmed	Low	Unassigned
	unity (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Hi
i wrote a little panel for my touchpad. this a hack but did reveal a bug in unity:
https://gist.github.com/1329168
this script creates a panel at the bottom of the screen and injects onboard (the onscreen keyboard) into it. now the keyboard is always visible even when windows are maximized because windows do not go over or under this panel.

this works fine in unity-2d and all the windows and the launcher stays above this area. But in unity-3d, the launcher does not react to this "resize" event and the launcher still uses the complete space even if it should resize. unity-2d does this correct.

See original description

Dennis Schwertel (tmassassin) on 2011-11-01

description:

updated

Revision history for this message

Omer Akram (om26er) wrote on 2012-03-28:

#1

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in unity:
status:	New → Incomplete
Changed in unity (Ubuntu):
status:	New → Incomplete

Revision history for this message

Dennis Schwertel (tmassassin) wrote on 2012-03-30:

#2

use this script to create a bottom panel with a keyboard injected into it.
https://gist.github.com/1364864
the other steps are in the description.

the important part is the x window property change _NET_WM_STRUT which is kinda broken in the launcher of unity 3d because it does not honor this property

Revision history for this message

Dennis Schwertel (tmassassin) wrote on 2012-03-31:

#3

just tried it in ubuntu precise (up to date patches) and 11.10. This problem still occurs when launching the script.

Changed in unity:
status:	Incomplete → New
Changed in unity (Ubuntu):
status:	Incomplete → New

Andrea Azzarone (azzar1) on 2012-04-21

Changed in unity:
status:	New → Triaged
Changed in unity (Ubuntu):
status:	New → Confirmed
Changed in unity:
status:	Triaged → New
Changed in unity (Ubuntu):
status:	Confirmed → New

Revision history for this message

Bilal Akhtar (bilalakhtar) wrote on 2012-08-16:

#4

If you're going to use onboard anyway, shouldn't onboard work well with Unity when enabled with 12.04 onward?

Revision history for this message

Omer Akram (om26er) wrote on 2012-08-16:

#5

test.py Edit (1.1 KiB, text/x-python)

I have attached your code here for ease. I have been able to create the issue here as well. I believe compiz people would know better.

affects:	unity (Ubuntu) → compiz (Ubuntu)
affects:	compiz-core → compiz
Changed in compiz:
status:	New → Confirmed
Changed in compiz (Ubuntu):
status:	New → Confirmed
Changed in unity:
status:	New → Confirmed
Changed in compiz:
importance:	Undecided → Low
Changed in unity:
importance:	Undecided → Low
Changed in compiz (Ubuntu):
importance:	Undecided → Low

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

test.py Edit

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.