Bug 1331891
| Summary: | Console window could be hidden after login via consoles on multiple hosts | ||
|---|---|---|---|
| Product: | Red Hat Directory Server | Reporter: | Noriko Hosoi <nhosoi> |
| Component: | Directory Console | Assignee: | Rich Megginson <rmeggins> |
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> |
| Severity: | medium | Docs Contact: | Petr Bokoc <pbokoc> |
| Priority: | high | ||
| Version: | 10.0 | CC: | gparente, nhosoi, nkinder, pbokoc, rmeggins, vashirov |
| Target Milestone: | DS10.1 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | idm-console-framework-1.1.16-2.el7dsrv | Doc Type: | Bug Fix |
| Doc Text: |
Directory Server Console can no longer be located off-screen at startup
Red Hat Directory Server Console window coordinates are stored in user preferences in the `o=netscaperoot` suffix. Previously, if the Directory Console was used by the same user on two different systems with different monitor setups, it was possible for the coordinates to be off screen on one of them, and consequently the Directory Console window could be hidden after logging in. This update adds a check which compares saved window coordinates with the current screen size, and resets the window location if currently outside the screen, which ensures the window is always visible.
|
Story Points: | --- |
| Clone Of: | 1261524 | Environment: | |
| Last Closed: | 2016-11-07 15:39:55 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1261524 | ||
| Bug Blocks: | |||
|
Comment 2
Viktor Ashirov
2016-09-13 14:36:15 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2665.html |