Bug 1014838 - Downsize the maximized window (second screen), the frame around the window isn't visible
Downsize the maximized window (second screen), the frame around the window is...
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: gnome-shell (Show other bugs)
20
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Owen Taylor
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-02 17:47 EDT by robin.test
Modified: 2013-10-25 11:19 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-25 11:19:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description robin.test 2013-10-02 17:47:19 EDT
Description of problem:
If you downsize the maximized windows on the second screen, the frame around the window and the menu bar wont't be visible. If you starts the application again and it starts maximized (e.g. system-monitor), the frame and the menu bar will still not be visible

Version-Release number of selected component (if applicable):
3.10.0-1.fc20

How reproducible:
Everytime

Steps to Reproduce:
1. Open a gnome application (like nautilus or system-monitor)
2. Maximize on second screen
3. Try to downsize the window by dragging down the frame.

Actual results:
the frame around the window and the menu bar aren't visible
the window is still maximized

Expected results:
the window is dowsized

Additional info:
Happend with gnome shell
Comment 1 robin.test 2013-10-02 18:08:17 EDT
mutter: 3.10.0.1-1.fc20
gnome-shell: 3.10.0.1-1.fc20
gnome-system-monitor: 3.10.0-1.fc20
nautilus: 3.10.0-1.fc20
Comment 2 Florian Müllner 2013-10-25 11:19:38 EDT
The examples mentioned (nautilus and system-monitor) have both been ported to client-side decorations in 3.10, so this is most likely https://bugzilla.gnome.org/show_bug.cgi?id=708718. It has been fixed in 3.10.1.

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