[Bug 34348] Wine xrandr12 failure

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=34348

--- Comment #28 from Adam Bolte <abolte at systemsaviour.com> ---
> Well, no. The proprietary NVIDIA driver generally has better performance
> than Mesa, but for many things Nouveau is perfectly adequate, and it would
> be a pretty sad world in which performance would be the only consideration
> for which software to use. I also think there's a significant difference
> between asking someone to consider an option and telling them not to do
> something.

I do agree with those points too. I would imagine that driver software being
"free software" should be an important consideration, for example. On that
point, it seems to me that including D3D9 would have probably helped a lot of
people move away from proprietary drivers and onto the free drivers. However, I
didn't really want to get into a discussion of the pros and cons of the chosen
approach here. :)

And you are correct that the output does say "consider". But it feels far more
forceful than that when it's constantly filling up your screen with those
warnings. ie:

abolte at ettin:~$ wine cmd.exe
wine: created the configuration directory '/home/abolte/.wine'
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to
RandR 1.0. Please consider using the Nouveau driver instead.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to
RandR 1.0. Please consider using the Nouveau driver instead.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to
RandR 1.0. Please consider using the Nouveau driver instead.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to
RandR 1.0. Please consider using the Nouveau driver instead.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to
RandR 1.0. Please consider using the Nouveau driver instead.
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to
RandR 1.0. Please consider using the Nouveau driver instead.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to
RandR 1.0. Please consider using the Nouveau driver instead.
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:iphlpapi:NotifyAddrChange (Handle 0x195e1a8, overlapped 0x195e1c0): stub
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to
RandR 1.0. Please consider using the Nouveau driver instead.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to
RandR 1.0. Please consider using the Nouveau driver instead.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to
RandR 1.0. Please consider using the Nouveau driver instead.
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:iphlpapi:NotifyAddrChange (Handle 0x166e820, overlapped 0x166e82c): stub
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to
RandR 1.0. Please consider using the Nouveau driver instead.
wine: configuration in '/home/abolte/.wine' has been updated.
Microsoft Windows 5.2.3790 (1.7.35)

Z:\home\abolte>

So that's only a built-in command line application. Instead, maybe we could
just complain about it the one time when Wine first needs to use RandR? The
current vibe I get when I see that is "Something is broken and you need to take
action to fix this or otherwise there will be uncertain consequences and don't
say you weren't warned!".

Is there anything Wine needs to do that RandR 1.0 cannot? Searching for RandR
on the Wine wiki returns 0 results.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.