cursor is placed much above the window border after dragging a snapped window

Bug #903846 reported by Omer Akram on 2011-12-13
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Compiz Snapping Windows Plugin
Medium
Unassigned
Unity Distro Priority
Undecided
Unassigned
compiz (Ubuntu)
Medium
Unassigned

Bug Description

1. start gnome-terminal
2. snap it to the right edge
3. now drag the window border to un-snap the window.

What happens:
the window is un-snapped and the cursor is quite a bit above the window title (see in the video, or attached screenshot)

What should happen:
on un-snapping the window the cursor should be over the window title bar

please see the attached video.

Related branches

Omer Akram (om26er) wrote :
Daniel van Vugt (vanvugt) wrote :

I can't reproduce this bug but it sounds like bug 886192.

Also I'm a bit concerned about your panel shadow... unless you've been experimenting with code and can explain that? :)

Omer Akram (om26er) wrote :

that panel shadow bug that's a long standing issue. happens only when using a screen recording utility. I believe its specific to nvidia binary (not sure though)

Changed in compiz-core:
importance: Undecided → Low
Omer Akram (om26er) wrote :

also its an issue for me on two machines, nvidia and intel :/

Daniel van Vugt (vanvugt) wrote :

Oh, I see the shadow issue is bug 763579...

Omer Akram (om26er) on 2012-01-20
Changed in compiz (Ubuntu):
importance: Low → Medium
Changed in compiz-core:
importance: Low → Medium
status: New → Confirmed
Changed in compiz (Ubuntu):
status: New → Confirmed
Didier Roche (didrocks) on 2012-01-20
Changed in unity-distro-priority:
status: New → Fix Committed
Omer Akram (om26er) wrote :

the linked branch sounds like it fixed the bug but I am not sure if we have this code in oneiric or not.

affects: compiz-core → compiz-snap-plugin
Changed in compiz-snap-plugin:
status: Confirmed → Fix Committed
Tim Penhey (thumper) on 2012-02-20
tags: added: distro-priority
Daniel van Vugt (vanvugt) wrote :

The fix for this bug is invalid and was removed a while ago because it is dead code. If you look carefully you'll see the new code introduced is not connected to the existing logic in any way. It does nothing. However no one noticed till we upgraded to a compiler that warned us.

Discussion about the problem continues in bug 201681.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments