snapping terminal window with ctrl+alt+num2 or num8 leads to offset between visible window position and cursor-selection area, other dual screen problems too

Bug #1285691 reported by Brian Richardson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-terminal (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hello,

I have posted this same question elsewhere (http://askubuntu.com/questions/423686/12-04-ctrl-alt-8-2-window-snap-problems-only-with-terminal-window and https://answers.launchpad.net/ubuntu/+question/244665) with no solutions yet, and will copy/paste what I posted there as the description is somewhat extensive.

I'm running a fresh install of Ubuntu 12.04.4, I have dual screens running on an nvidia gtx 760 running 331.49 drivers. Not sure whether this is relevant or not, but I have only the launcher bar enabled on the left most screen, and sticky edges disabled.

The two problems I am experiencing involve ctrl-alt-num window snap feature, but only with ctrl-alt-8 and ctrl-alt-2, and only with a gnome-terminal window. These issues do not seem to affect other application windows as far as I can tell.

Problem 1: On the left screen, when snapping the gnome-terminal window to the top or bottom half (ctrl-alt-8 or -2, respectively), immediately after snapping if I use the cursor to select text the actual selection area appears offset to the right of the cursor by a distance equivalent to the width of the launcher bar.

If I use Compiz ccsm Unity plugin to adjust the size of the launcher bar, the size of the offset between the cursor and consequent selection area changes proportionately.

This horizontal cursor/selection area offset problem is temporarily resolved by simply clicking the title bar of the terminal window once (no movement of the window required), and subsequent text selection in the terminal window is properly aligned with the cursor. Hotkey snapping the terminal window again revives the offset.

Problem 2: When using the right screen, and snapping a window to the top or bottom half (ctrl-alt-8 or -2) the window visually appears to be properly snapped on the top/bottom half of the right screen, but the window manager seems to think the terminal window is in fact snapped to the top/bottom of the left screen.

To clarify what I mean by this is, after snapping a terminal window on the right screen using either of these hotkey combinations, if I click on the terminal window (either terminal area, or title bar) where I see it on the right screen, it is as if I am clicking on the desktop (or other application behind the terminal window, if there is one), and the terminal window goes out of focus. However, after snapping the terminal window on the right screen to the top/bottom, if I click on the left screen in the top/bottom area it is as if I am clicking on the terminal window.

To temporarily resolve this issue immediately after snapping the window, if, in the left screen, I click on the invisible area which matches up with the terminal window's title bar the terminal window gains focus, and I can then click on the visible terminal window where I see it on the right screen.

Attempted, but failed fixes: I have tried the following

dconf reset -f /org/compiz/
gconftool-2 --recursive-unset /apps/compiz-1
unity --reset
and apt-get purge/reinstall of unity and compiz packages.
Also tried creating new user accounts, both administrator and standard, and can replicate the problem in those accounts too immediately after account creation with no other changes.

Brian

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-terminal 3.4.1.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-17.31~precise1-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Thu Feb 27 09:19:24 2014
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Brian Richardson (brian-richardson83) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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