Bug 711304 - fallback mode workspace does not use right area of ~50 pixels
Summary: fallback mode workspace does not use right area of ~50 pixels
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 15
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-07 06:48 UTC by Hin-Tak Leung
Modified: 2011-07-12 08:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-12 08:31:21 UTC
Type: ---


Attachments (Terms of Use)
first screenshot, showing the effect of gnome not using the right hand side of screen. (197.58 KB, image/png)
2011-06-07 06:48 UTC, Hin-Tak Leung
no flags Details
Another screenshot showing the problem for maximized windows (102.26 KB, image/png)
2011-06-07 06:52 UTC, Hin-Tak Leung
no flags Details
desktop screenshot with a different gnome theme (105.56 KB, image/png)
2011-06-07 19:01 UTC, Hin-Tak Leung
no flags Details

Description Hin-Tak Leung 2011-06-07 06:48:59 UTC
Created attachment 503386 [details]
first screenshot, showing the effect of gnome not using the right hand side of screen.

Description of problem:

See screen shot - gnome 3 fallback mode does not use right-area of ~50 pixels.
(note top/bottom panels extend to end of screen but the middle area does not).

Version-Release number of selected component (if applicable):
Up to date F15, 
$ rpm -q gnome-session
gnome-session-3.0.1-2.fc15.x86_64



How reproducible:
Always

Steps to Reproduce:
1. Just go into fallback mode.
2. run screenshot program.
3.
  
Actual results:
The right area of ~50 pixels is not used.


Expected results:
Use the whole dislay.

Additional info:
Note that the top/bottom panels extends to edge, just the middle area is not.
Also maximized window (or newly launched window) only extend to the used area and not the whole display. (see 2nd screenshot, where I maximize this window as I type it).

Comment 1 Hin-Tak Leung 2011-06-07 06:52:15 UTC
Created attachment 503388 [details]
Another screenshot showing the problem for maximized windows

This is a screenshot on an maximized window. (the bug filing firefox). This seems to suggest that the window manager is not telling clients the correct useable area?

Comment 2 Hin-Tak Leung 2011-06-07 06:56:46 UTC
I am running metacity as windows manager. Compiz seems to be quite buggy - quite a few common non-gnome applications (konqueror, Terminal (from Terminal-0.4.7-1.fc15.x86_64)) seem to be able to crash the gnome session.

Please feel free to fill this under a different component - I am filing under gnome-session because I cannot think of a better place. This does not seem to be a hardware problem - as the top/bottom panels can extend to the end of the physical screen, just the middle workspace isn't.

Comment 3 Hin-Tak Leung 2011-06-07 19:01:17 UTC
Created attachment 503557 [details]
desktop screenshot with a different gnome theme

Tweaking gnome theme with tweak-gnome-tool resulting in the not-used area painted the theme color, suggesting that this is a software bug (of mis-calculating the useable workspace?) rather than hardware/driver problem.

Comment 4 Hin-Tak Leung 2011-07-12 08:31:21 UTC
After suffering the problem for almost 5 weeks (and logged out/in, rebooted many times) and reading many things about gnome-shell, on a hunch, I thought the unused area looks like an extra notification/panel area which is entirely empty and unpopulated. So I tried ALT-right-click on it. Lord and behold, various things happened everywhere the entire desktop - some of the maximized windows enlarged, etc

So the problem disappeared after I ALT-right-click on that area. I don't know if it is possible to have a side-way-panel/notification area in gnome-shell, but seeing as this looks like a gnome-shell confusion bug, I am re-assigning to gnome-shell, and closing it.


Note You need to log in before you can comment on or make changes to this bug.