<AWT Dev> <AWT dev>[9] Review request for 8022810: Cannot list all the available display modes on Ubuntu linux in case of two screen devices

Semyon Sadetsky semyon.sadetsky at oracle.com
Mon Jun 20 10:29:30 UTC 2016

On 6/7/2016 7:06 PM, Sergey Bylokhov wrote:

> On 01.06.16 9:57, Semyon Sadetsky wrote:
>> I don't have access to such hardware as well. I'm using linux VMs with
>> several virtual screens. Adding a new screen to a VM configuration can
>> be done in 10 seconds in most VMMs.
>> The result of the getDisplayModes() for 2-screen Ubuntu VM before the
>> fix looked like:
>> for device[0]: <current screen 0 mode>, <<the rest modes of
>> screen-0>>,<<all modes of screen-1>>
>> for device[1]: <current screen 1 mode>
> So can you confirm that after the fix the next code will work w/o 
> exceptions?
> http://cr.openjdk.java.net/~serb/tmp/Test.java
Yes, for the single screen configuration.
This test has no use for multimonitor config because display mode change 
is not supported in case of Xinerama.
And I'm planing to fix that, including get/setDisplayMode().

> I am worried since we updated the enumDisplayModes(), but did not 
> update the getCurrentDisplayMode() which still uses the old code.
>>>>>>>>> the list of supported modes changed and my question was: what
>>>>>>>>> happens
>>>>>>>>> when these modes will be passed to setDisplayMode() (of course
>>>>>>>>> modes
>>>>>>>>> and setDisplayMode should be from one GraphicsDevice object).
>>>>>>>> the same as before the fix.
> Actually it seems that setDisplayMode() should not work since 
> JDK-8131752. probably someday we should change the code in 
> X11GraphicsDevice.isDisplayChangeSupported(), which skip the xinerama 
> case.

More information about the awt-dev mailing list