|Summary:||16bit thousands color output options not working|
|Component:||Server/DDX/XQuartz||Assignee:||Jeremy Huddleston Sequoia <jeremyhu>|
|Status:||RESOLVED MOVED||QA Contact:||Jeremy Huddleston Sequoia <jeremyhu>|
|OS:||Mac OS X (All)|
|i915 platform:||i915 features:|
Description kevin 2016-10-11 22:01:40 UTC
Under Preferences Output there are choices for: from display, 256 color, thousands or millions. Millions 24bit and 256 color work fine but thousands 16bit color still outputs at 24bit color it does not switch to 16bit after restarting. All of the programs we run use 16bit color so they are not functioning.
Comment 1 Jeremy Huddleston Sequoia 2016-10-11 23:14:28 UTC
That preference UI should just be removed.
Comment 2 kevin 2016-10-12 02:47:28 UTC
Created attachment 127230 [details] attachment-7944-0.html But what if you want to run it 16bit mode is there some other way to do it? Kevin Sent from my iPhone > On Oct 11, 2016, at 5:16 PM, email@example.com wrote: > > Jeremy Huddleston Sequoia changed bug 98210 > What Removed Added > Component quartz-wm Server/DDX/XQuartz > Product XQuartz xorg > Version 2.7.9 (xserver-1.17.4) git > You are receiving this mail because: > You reported the bug.
Comment 3 Jeremy Huddleston Sequoia 2016-10-12 07:23:10 UTC
Why would you want to or need to?
Comment 4 kevin 2016-10-12 12:43:59 UTC
Created attachment 127241 [details] attachment-11283-0.html Less colors is a lot faster, especially when working remotely through SSH with a forwarded X window. Since there is less data being sent you can sacrifice some unneeded color and use a larger window which is more beneficial for the work our company does. Kevin Sent from my iPad > On Oct 12, 2016, at 01:23, firstname.lastname@example.org wrote: > > Comment # 3 on bug 98210 from Jeremy Huddleston Sequoia > Why would you want to or need to? > You are receiving this mail because: > You reported the bug.
Comment 5 GitLab Migration User 2018-12-13 18:30:56 UTC
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/189.