2011-04-06 01:06:06 |
Benjamin Humphrey |
bug |
|
|
added bug |
2011-04-06 01:06:06 |
Benjamin Humphrey |
attachment added |
|
[1] Workspace switcher showing the dead zone https://bugs.launchpad.net/bugs/752098/+attachment/1985795/+files/dead-zone1.png |
|
2011-04-06 01:06:38 |
Benjamin Humphrey |
attachment added |
|
[2] A terminal window in the dead zone https://bugs.launchpad.net/unity/+bug/752098/+attachment/1985796/+files/terminal-in-dead-zone.png |
|
2011-04-06 01:08:02 |
Benjamin Humphrey |
description |
I have a 15.4" laptop that I connect to a 24" Dell monitor when I'm at work. The laptop has a screen resolution of 1280 x 800, the 24" monitor is 1920 x 1080.
Because the laptop sits lower than the monitor, and because of both the resolution and physical size differences, a virtual "dead zone" appears above my laptop.
The mouse can be moved into this dead zone, and when I initiate "workspace switcher" it looks like attached image [1]. You can clearly see there is a black "dead zone" below the large monitor to the right, and a huge dead zone above the laptop screen on the left.
This is a problem in itself, because the mouse can be "lost" in the dead zone and not easily found unless the user knows where to look.
But the main issue is that Compiz sees this "dead zone" as a fairly enticing place to place windows (obviously because it reckons there is nothing there) - so whenever I start a new application (in this case a Terminal window), it spawns in the dead zone, and I can't see it. Unless I open up workspace switcher and "pull" it down into the visible area. Attached image [2].
Attached image [3] shows the setup I have, with the virtual dead zone highlighted.
This brainstorm idea from 12 months ago highlights the issue some more: http://brainstorm.ubuntu.com/idea/24412/ |
I have a 15.4" laptop that I connect to a 24" Dell monitor when I'm at work. The laptop has a screen resolution of 1280 x 800, the 24" monitor is 1920 x 1080.
Because the laptop sits lower than the monitor, and because of both the resolution and physical size differences, a virtual "dead zone" appears above my laptop.
The mouse can be moved into this dead zone, and when I initiate "workspace switcher" it looks like attached image [1]. You can clearly see there is a black "dead zone" below the large monitor to the right, and a huge dead zone above the laptop screen on the left.
This is a problem in itself, because the mouse can be "lost" in the dead zone and not easily found unless the user knows where to look.
But the main issue is that Compiz sees this "dead zone" as a fairly enticing place to place windows (obviously because it reckons there is nothing there) - so whenever I start a new application (in this case a Terminal window), it spawns in the dead zone, and I can't see it. Unless I open up workspace switcher and "pull" it down into the visible area. Attached image [2].
Attached image [3] shows the setup I have, with the virtual dead zone highlighted.
Other operating systems (like Windows) do this "dead zone" thing too, except that they a) don't allow the mouse to move into the dead zone and b) don't spawn applications in the dead zone.
A quick fix would be to change the Compiz "Place Window" plugin settings to have applications spawn under the cursor, but this still doesn't fix the fundamental issue and wouldn't prevent the mouse from moving into the area.
This brainstorm idea from 12 months ago highlights the issue some more: http://brainstorm.ubuntu.com/idea/24412/ |
|
2011-04-06 01:10:33 |
Benjamin Humphrey |
description |
I have a 15.4" laptop that I connect to a 24" Dell monitor when I'm at work. The laptop has a screen resolution of 1280 x 800, the 24" monitor is 1920 x 1080.
Because the laptop sits lower than the monitor, and because of both the resolution and physical size differences, a virtual "dead zone" appears above my laptop.
The mouse can be moved into this dead zone, and when I initiate "workspace switcher" it looks like attached image [1]. You can clearly see there is a black "dead zone" below the large monitor to the right, and a huge dead zone above the laptop screen on the left.
This is a problem in itself, because the mouse can be "lost" in the dead zone and not easily found unless the user knows where to look.
But the main issue is that Compiz sees this "dead zone" as a fairly enticing place to place windows (obviously because it reckons there is nothing there) - so whenever I start a new application (in this case a Terminal window), it spawns in the dead zone, and I can't see it. Unless I open up workspace switcher and "pull" it down into the visible area. Attached image [2].
Attached image [3] shows the setup I have, with the virtual dead zone highlighted.
Other operating systems (like Windows) do this "dead zone" thing too, except that they a) don't allow the mouse to move into the dead zone and b) don't spawn applications in the dead zone.
A quick fix would be to change the Compiz "Place Window" plugin settings to have applications spawn under the cursor, but this still doesn't fix the fundamental issue and wouldn't prevent the mouse from moving into the area.
This brainstorm idea from 12 months ago highlights the issue some more: http://brainstorm.ubuntu.com/idea/24412/ |
I have a 15.4" laptop that I connect to a 24" Dell monitor when I'm at work. The laptop has a screen resolution of 1280 x 800, the 24" monitor is 1920 x 1080.
Because the laptop sits lower than the monitor, and because of both the resolution and physical size differences, a virtual "dead zone" appears above my laptop.
The mouse can be moved into this dead zone, and when I initiate "workspace switcher" it looks like attached image [1]. You can clearly see there is a black "dead zone" below the large monitor to the right, and a huge dead zone above the laptop screen on the left.
This is a problem in itself, because the mouse can be "lost" in the dead zone and not easily found unless the user knows where to look.
But the main issue is that Compiz sees this "dead zone" as a fairly enticing place to place windows (obviously because it reckons there is nothing there) - so whenever I start a new application (in this case a Terminal window), it spawns in the dead zone, and I can't see it. Unless I open up workspace switcher and "pull" it down into the visible area. Attached image [2].
Attached image [3] shows the setup I have, with the virtual dead zone highlighted with orange post it notes.
Other operating systems (like Windows) do this "dead zone" thing too, except that they a) don't allow the mouse to move into the dead zone and b) don't spawn applications in the dead zone.
A quick fix would be to change the Compiz "Place Window" plugin settings to have applications spawn under the cursor, but this still doesn't fix the fundamental issue and wouldn't prevent the mouse from moving into the area.
This brainstorm idea from 12 months ago highlights the issue some more: http://brainstorm.ubuntu.com/idea/24412/ |
|
2011-04-06 01:15:04 |
Benjamin Humphrey |
attachment added |
|
[3] Photo showing my setup with orange post it notes highlighting dead zones https://bugs.launchpad.net/unity/+bug/752098/+attachment/1985830/+files/IMG_20110406_130758.jpg |
|
2011-04-06 01:17:43 |
Benjamin Humphrey |
description |
I have a 15.4" laptop that I connect to a 24" Dell monitor when I'm at work. The laptop has a screen resolution of 1280 x 800, the 24" monitor is 1920 x 1080.
Because the laptop sits lower than the monitor, and because of both the resolution and physical size differences, a virtual "dead zone" appears above my laptop.
The mouse can be moved into this dead zone, and when I initiate "workspace switcher" it looks like attached image [1]. You can clearly see there is a black "dead zone" below the large monitor to the right, and a huge dead zone above the laptop screen on the left.
This is a problem in itself, because the mouse can be "lost" in the dead zone and not easily found unless the user knows where to look.
But the main issue is that Compiz sees this "dead zone" as a fairly enticing place to place windows (obviously because it reckons there is nothing there) - so whenever I start a new application (in this case a Terminal window), it spawns in the dead zone, and I can't see it. Unless I open up workspace switcher and "pull" it down into the visible area. Attached image [2].
Attached image [3] shows the setup I have, with the virtual dead zone highlighted with orange post it notes.
Other operating systems (like Windows) do this "dead zone" thing too, except that they a) don't allow the mouse to move into the dead zone and b) don't spawn applications in the dead zone.
A quick fix would be to change the Compiz "Place Window" plugin settings to have applications spawn under the cursor, but this still doesn't fix the fundamental issue and wouldn't prevent the mouse from moving into the area.
This brainstorm idea from 12 months ago highlights the issue some more: http://brainstorm.ubuntu.com/idea/24412/ |
I have a 15.4" laptop that I connect to a 24" Dell monitor when I'm at work. The laptop has a screen resolution of 1280 x 800, the 24" monitor is 1920 x 1080.
Because the laptop sits lower than the monitor, and because of both the resolution and physical size differences, a virtual "dead zone" appears above my laptop.
The mouse can be moved into this dead zone, and when I initiate "workspace switcher" it looks like attached image [1]. You can clearly see there is a black "dead zone" below the large monitor to the right, and a huge dead zone above the laptop screen on the left.
This is a problem in itself, because the mouse can be "lost" in the dead zone and not easily found unless the user knows where to look.
But the main issue is that Compiz sees this "dead zone" as a fairly enticing place to place windows (obviously because it reckons there is nothing there) - so whenever I start a new application (in this case a Terminal window), it spawns in the dead zone, and I can't see it. Unless I open up workspace switcher and "pull" it down into the visible area. Attached image [2].
Attached image [3] shows the setup I have, with the virtual dead zone highlighted with orange post it notes.
As a side effect of this bug, activating the Unity launcher by using the corner hot-spot becomes almost impossible due to the corner technically not existing anymore - it exists vertically, but the horizontal "roof" of the BFB is no longer physically there, so I'm constantly overshooting the hot corner. It's particularly frustrating because the launcher "peeks" out at you when you get close, but I can't actually get it to stay out because I am over shooting all the time. It's almost as if Unity is teasing me.
Other operating systems (like Windows) do this "dead zone" thing too, except that they a) don't allow the mouse to move into the dead zone and b) don't spawn applications in the dead zone.
A quick fix would be to change the Compiz "Place Window" plugin settings to have applications spawn under the cursor, but this still doesn't fix the fundamental issue and wouldn't prevent the mouse from moving into the area.
This brainstorm idea from 12 months ago highlights the issue some more: http://brainstorm.ubuntu.com/idea/24412/ |
|
2011-04-06 01:19:29 |
Benjamin Humphrey |
description |
I have a 15.4" laptop that I connect to a 24" Dell monitor when I'm at work. The laptop has a screen resolution of 1280 x 800, the 24" monitor is 1920 x 1080.
Because the laptop sits lower than the monitor, and because of both the resolution and physical size differences, a virtual "dead zone" appears above my laptop.
The mouse can be moved into this dead zone, and when I initiate "workspace switcher" it looks like attached image [1]. You can clearly see there is a black "dead zone" below the large monitor to the right, and a huge dead zone above the laptop screen on the left.
This is a problem in itself, because the mouse can be "lost" in the dead zone and not easily found unless the user knows where to look.
But the main issue is that Compiz sees this "dead zone" as a fairly enticing place to place windows (obviously because it reckons there is nothing there) - so whenever I start a new application (in this case a Terminal window), it spawns in the dead zone, and I can't see it. Unless I open up workspace switcher and "pull" it down into the visible area. Attached image [2].
Attached image [3] shows the setup I have, with the virtual dead zone highlighted with orange post it notes.
As a side effect of this bug, activating the Unity launcher by using the corner hot-spot becomes almost impossible due to the corner technically not existing anymore - it exists vertically, but the horizontal "roof" of the BFB is no longer physically there, so I'm constantly overshooting the hot corner. It's particularly frustrating because the launcher "peeks" out at you when you get close, but I can't actually get it to stay out because I am over shooting all the time. It's almost as if Unity is teasing me.
Other operating systems (like Windows) do this "dead zone" thing too, except that they a) don't allow the mouse to move into the dead zone and b) don't spawn applications in the dead zone.
A quick fix would be to change the Compiz "Place Window" plugin settings to have applications spawn under the cursor, but this still doesn't fix the fundamental issue and wouldn't prevent the mouse from moving into the area.
This brainstorm idea from 12 months ago highlights the issue some more: http://brainstorm.ubuntu.com/idea/24412/ |
I have a 15.4" laptop that I connect to a 24" Dell monitor when I'm at work. The laptop has a screen resolution of 1280 x 800, the 24" monitor is 1920 x 1080.
Because the laptop sits lower than the monitor, and because of both the resolution and physical size differences, a virtual "dead zone" appears above my laptop.
The mouse can be moved into this dead zone, and when I initiate "workspace switcher" it looks like attached image [1]. You can clearly see there is a black "dead zone" below the large monitor to the right, and a huge dead zone above the laptop screen on the left.
This is a problem in itself, because the mouse can be "lost" in the dead zone and not easily found unless the user knows where to look.
But the main issue is that Compiz sees this "dead zone" as a fairly enticing place to stick windows (obviously because it reckons there is nothing there) - so whenever I start a new application (in this case a Terminal window), it spawns in the dead zone, and I can't see it. Unless I open up workspace switcher and "pull" it down into the visible area. Attached image [2].
Attached image [3] shows the setup I have, with the virtual dead zone highlighted with orange post it notes.
As a side effect of this bug, activating the Unity launcher by using the corner hot-spot becomes almost impossible due to the corner technically not existing anymore - it exists vertically, but the horizontal "roof" of the BFB is no longer physically there, so I'm constantly overshooting the hot corner. It's particularly frustrating because the launcher "peeks" out at you when you get close, but I can't actually get it to stay out because I am over shooting all the time. It's almost as if Unity is teasing me.
Other operating systems (like Windows) do this "dead zone" thing too, except that they a) don't allow the mouse to move into the dead zone and b) don't spawn applications in the dead zone.
A quick fix would be to change the Compiz "Place Window" plugin settings to have applications spawn under the cursor, but this still doesn't fix the fundamental issue and wouldn't prevent the mouse from moving into the area.
This brainstorm idea from 12 months ago highlights the issue some more: http://brainstorm.ubuntu.com/idea/24412/ |
|
2011-04-06 01:38:17 |
jorgejhms |
bug |
|
|
added subscriber jorgejhms |
2011-04-06 04:04:05 |
wei00007 |
bug task added |
|
ubuntu |
|
2011-04-06 05:21:17 |
Sebastian Schlatow |
bug |
|
|
added subscriber Sebastian Schlatow |
2011-04-06 09:41:31 |
Bilal Akhtar |
affects |
ubuntu |
unity (Ubuntu) |
|
2011-04-06 09:41:31 |
Bilal Akhtar |
unity (Ubuntu): importance |
Undecided |
Medium |
|
2011-04-06 09:41:31 |
Bilal Akhtar |
unity (Ubuntu): status |
New |
Confirmed |
|
2011-04-06 09:41:40 |
Bilal Akhtar |
unity (Ubuntu): importance |
Medium |
High |
|
2011-04-06 09:41:49 |
Bilal Akhtar |
unity: status |
New |
Confirmed |
|
2011-04-06 09:41:59 |
Bilal Akhtar |
bug task added |
|
compiz (Ubuntu) |
|
2011-04-06 09:42:09 |
Bilal Akhtar |
compiz (Ubuntu): status |
New |
Confirmed |
|
2011-04-06 09:42:11 |
Bilal Akhtar |
compiz (Ubuntu): importance |
Undecided |
High |
|
2011-04-15 09:37:25 |
Neil J. Patel |
unity: assignee |
|
Sam "SmSpillaz" Spilsbury (smspillaz) |
|
2011-04-15 09:37:34 |
Neil J. Patel |
unity: importance |
Undecided |
High |
|
2011-04-15 09:37:37 |
Neil J. Patel |
unity: milestone |
|
3.8.10 |
|
2011-04-19 15:36:02 |
Sam Spilsbury |
compiz (Ubuntu): status |
Confirmed |
In Progress |
|
2011-04-19 15:36:04 |
Sam Spilsbury |
unity: status |
Confirmed |
In Progress |
|
2011-04-19 15:36:06 |
Sam Spilsbury |
compiz (Ubuntu): assignee |
|
Sam "SmSpillaz" Spilsbury (smspillaz) |
|
2011-04-19 17:06:06 |
Didier Roche-Tolomelli |
unity: milestone |
3.8.10 |
3.8.12 |
|
2011-04-21 12:06:55 |
Didier Roche-Tolomelli |
unity (Ubuntu): status |
Confirmed |
In Progress |
|
2011-04-22 12:09:52 |
David Barth |
unity: milestone |
3.8.12 |
3.8.14 |
|
2011-04-22 12:10:53 |
David Barth |
unity: importance |
High |
Low |
|
2011-04-22 12:10:55 |
David Barth |
compiz (Ubuntu): importance |
High |
Low |
|
2011-04-22 12:10:58 |
David Barth |
unity (Ubuntu): importance |
High |
Low |
|
2011-05-03 01:14:03 |
Tv |
bug |
|
|
added subscriber Tv |
2011-05-06 22:57:33 |
Jaime Rave |
bug |
|
|
added subscriber Jaime Rave |
2011-05-14 07:16:50 |
Aminda Suomalainen |
bug |
|
|
added subscriber Mika Suomalainen |
2011-05-16 13:58:14 |
Jelmer Vernooij |
bug |
|
|
added subscriber Jelmer Vernooij |
2011-05-16 13:58:54 |
John A Meinel |
bug |
|
|
added subscriber John A Meinel |
2011-05-17 13:53:42 |
Jason Smith |
compiz (Ubuntu): assignee |
Sam "SmSpillaz" Spilsbury (smspillaz) |
Jason Smith (jassmith) |
|
2011-05-17 13:53:44 |
Jason Smith |
unity: assignee |
Sam "SmSpillaz" Spilsbury (smspillaz) |
Jason Smith (jassmith) |
|
2011-05-17 13:54:05 |
Jason Smith |
compiz (Ubuntu): status |
In Progress |
Invalid |
|
2011-05-21 17:53:44 |
James G Scherer |
attachment added |
|
png of small zone on dual monitor unity https://bugs.launchpad.net/ubuntu/+source/unity/+bug/752098/+attachment/2137744/+files/UnityBug752098.png |
|
2011-05-26 15:13:27 |
Jason Smith |
unity: status |
In Progress |
Fix Committed |
|
2011-05-26 15:13:59 |
Jason Smith |
branch linked |
|
lp:~jassmith/unity/unity.sru-fixes |
|
2011-05-26 15:16:21 |
Jason Smith |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2011-05-26 15:28:25 |
Jason Smith |
description |
I have a 15.4" laptop that I connect to a 24" Dell monitor when I'm at work. The laptop has a screen resolution of 1280 x 800, the 24" monitor is 1920 x 1080.
Because the laptop sits lower than the monitor, and because of both the resolution and physical size differences, a virtual "dead zone" appears above my laptop.
The mouse can be moved into this dead zone, and when I initiate "workspace switcher" it looks like attached image [1]. You can clearly see there is a black "dead zone" below the large monitor to the right, and a huge dead zone above the laptop screen on the left.
This is a problem in itself, because the mouse can be "lost" in the dead zone and not easily found unless the user knows where to look.
But the main issue is that Compiz sees this "dead zone" as a fairly enticing place to stick windows (obviously because it reckons there is nothing there) - so whenever I start a new application (in this case a Terminal window), it spawns in the dead zone, and I can't see it. Unless I open up workspace switcher and "pull" it down into the visible area. Attached image [2].
Attached image [3] shows the setup I have, with the virtual dead zone highlighted with orange post it notes.
As a side effect of this bug, activating the Unity launcher by using the corner hot-spot becomes almost impossible due to the corner technically not existing anymore - it exists vertically, but the horizontal "roof" of the BFB is no longer physically there, so I'm constantly overshooting the hot corner. It's particularly frustrating because the launcher "peeks" out at you when you get close, but I can't actually get it to stay out because I am over shooting all the time. It's almost as if Unity is teasing me.
Other operating systems (like Windows) do this "dead zone" thing too, except that they a) don't allow the mouse to move into the dead zone and b) don't spawn applications in the dead zone.
A quick fix would be to change the Compiz "Place Window" plugin settings to have applications spawn under the cursor, but this still doesn't fix the fundamental issue and wouldn't prevent the mouse from moving into the area.
This brainstorm idea from 12 months ago highlights the issue some more: http://brainstorm.ubuntu.com/idea/24412/ |
Test Case:
0) Install unity 3.8.14 and restart your session
1) Have a dual monitor setup
2) Ensure right monitor is primary (ugly)
3) open firefox and place on left edge of left monitor
4) restart firefox
Result: firefox should not end up squished into the left side of the screen.
I have a 15.4" laptop that I connect to a 24" Dell monitor when I'm at work. The laptop has a screen resolution of 1280 x 800, the 24" monitor is 1920 x 1080.
Because the laptop sits lower than the monitor, and because of both the resolution and physical size differences, a virtual "dead zone" appears above my laptop.
The mouse can be moved into this dead zone, and when I initiate "workspace switcher" it looks like attached image [1]. You can clearly see there is a black "dead zone" below the large monitor to the right, and a huge dead zone above the laptop screen on the left.
This is a problem in itself, because the mouse can be "lost" in the dead zone and not easily found unless the user knows where to look.
But the main issue is that Compiz sees this "dead zone" as a fairly enticing place to stick windows (obviously because it reckons there is nothing there) - so whenever I start a new application (in this case a Terminal window), it spawns in the dead zone, and I can't see it. Unless I open up workspace switcher and "pull" it down into the visible area. Attached image [2].
Attached image [3] shows the setup I have, with the virtual dead zone highlighted with orange post it notes.
As a side effect of this bug, activating the Unity launcher by using the corner hot-spot becomes almost impossible due to the corner technically not existing anymore - it exists vertically, but the horizontal "roof" of the BFB is no longer physically there, so I'm constantly overshooting the hot corner. It's particularly frustrating because the launcher "peeks" out at you when you get close, but I can't actually get it to stay out because I am over shooting all the time. It's almost as if Unity is teasing me.
Other operating systems (like Windows) do this "dead zone" thing too, except that they a) don't allow the mouse to move into the dead zone and b) don't spawn applications in the dead zone.
A quick fix would be to change the Compiz "Place Window" plugin settings to have applications spawn under the cursor, but this still doesn't fix the fundamental issue and wouldn't prevent the mouse from moving into the area.
This brainstorm idea from 12 months ago highlights the issue some more: http://brainstorm.ubuntu.com/idea/24412/ |
|
2011-05-26 15:38:06 |
Didier Roche-Tolomelli |
unity: status |
Fix Committed |
Fix Released |
|
2011-05-26 15:39:28 |
Launchpad Janitor |
branch linked |
|
lp:unity/3.0 |
|
2011-05-26 15:42:13 |
Didier Roche-Tolomelli |
nominated for series |
|
Ubuntu Natty |
|
2011-05-26 15:42:13 |
Didier Roche-Tolomelli |
bug task added |
|
compiz (Ubuntu Natty) |
|
2011-05-26 15:42:13 |
Didier Roche-Tolomelli |
bug task added |
|
unity (Ubuntu Natty) |
|
2011-05-26 15:42:22 |
Didier Roche-Tolomelli |
compiz (Ubuntu Natty): status |
New |
Invalid |
|
2011-05-26 16:16:26 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-desktop/unity/ubuntu |
|
2011-05-26 16:20:12 |
Launchpad Janitor |
unity (Ubuntu): status |
In Progress |
Fix Released |
|
2011-05-26 17:13:22 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/unity |
|
2011-05-30 05:57:58 |
Martin Pitt |
unity (Ubuntu Natty): status |
New |
Fix Committed |
|
2011-05-30 05:58:00 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
2011-05-30 05:58:02 |
Martin Pitt |
tags |
|
verification-needed |
|
2011-05-30 06:20:48 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/natty-proposed/unity |
|
2011-06-09 05:54:23 |
Launchpad Janitor |
unity (Ubuntu Natty): status |
Fix Committed |
Fix Released |
|