https://bugs.winehq.org/show_bug.cgi?id=38032
Bug ID: 38032 Summary: "Broken NVIDIA RandR detected" warning needs improvement Product: Wine Version: 1.7.36 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winex11.drv Assignee: wine-bugs@winehq.org Reporter: abolte@systemsaviour.com Distribution: ---
This relates to bug #34348 "Wine xrandr12 failure", which concerns nVidia proprietary drivers not adhering to expected RandR 1.0+ behaviour. Until nVidia addresses the problems preventing Wine from using RandR 1.3 reliably for its intended purpose, Wine warns the user that it is falling back to RandR 1.0 as a workaround. It does this by printing the following warning message very frequently:
"Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead."
(line 488 of dlls/winex11.drv/xrandr.c as of 1.7.36)
The user is reminded of this every time winex11.drv is loaded, which is apparently quite frequently - even for command-line applications. Due to the overuse of the warning, it comes off very strong and may cause unnecessary worry. It may also present annoyances for developers looking through future bug reports that are filled with this message.
I suggest this situation can be improved by the following two proposals:
1. this only be printed the first time winex11.drv is loaded.
2. the message changed to point to a wiki page or man page with a short description of the problem, or even the URL of bug #34348. eg.
"Broken NVIDIA RandR detected, falling back to RandR 1.0. Please refer to http://wiki.winehq.org/RandR"
This would allow users to understand what has happened and decide for themselves what course of action should be taken. Otherwise, I don't think a user will get a sufficient level of understanding from one line of text, and (unlike most Wine output) this one is aimed at the user and not so much at developers debugging something.
https://bugs.winehq.org/show_bug.cgi?id=38032
Adam Bolte abolte@systemsaviour.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte@systemsaviour.com, | |sebastian@fds-team.de
https://bugs.winehq.org/show_bug.cgi?id=38032
Adam Bolte abolte@systemsaviour.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://wiki.winehq.org/FAQ
--- Comment #1 from Adam Bolte abolte@systemsaviour.com --- I added:
10.12.8. I get "Broken NVIDIA RandR detected, falling back to RandR 1.0." printed to the console.
to the Wine wiki: http://wiki.winehq.org/FAQ
So that's an option.
https://bugs.winehq.org/show_bug.cgi?id=38032
--- Comment #2 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to Adam Bolte from comment #1)
I added:
10.12.8. I get "Broken NVIDIA RandR detected, falling back to RandR 1.0." printed to the console.
to the Wine wiki: http://wiki.winehq.org/FAQ
Your FAQ entry just repeats the suggestion to try the nouveau driver, which is not a viable workaround for anyone who wants to play 3D games.
You posted a real workaround in bug 37966; that's what should be in the FAQ.
https://bugs.winehq.org/show_bug.cgi?id=38032
--- Comment #3 from Adam Bolte abolte@systemsaviour.com --- (In reply to Rosanne DiMesio from comment #2)
(In reply to Adam Bolte from comment #1)
I added:
10.12.8. I get "Broken NVIDIA RandR detected, falling back to RandR 1.0." printed to the console.
to the Wine wiki: http://wiki.winehq.org/FAQ
Your FAQ entry just repeats the suggestion to try the nouveau driver, which is not a viable workaround for anyone who wants to play 3D games.
You posted a real workaround in bug 37966; that's what should be in the FAQ.
I figured if somebody has enough knowledge and determination to feel comfortable looking at the bug report (which I linked), they would probably do so.
Happy to add the xorg.conf change suggestion to the FAQ. Obviously that might cause problems with other software, or even prevent Xorg from loading if the user misconfigures xorg.conf. Given the wiki seems to mainly be aimed towards beginners with both Wine and the command line, I wasn't initially sure it was the place for it.
https://bugs.winehq.org/show_bug.cgi?id=38032
--- Comment #4 from Adam Bolte abolte@systemsaviour.com --- (In reply to Rosanne DiMesio from comment #2)
You posted a real workaround in bug 37966; that's what should be in the FAQ.
Done. :)
https://bugs.winehq.org/show_bug.cgi?id=38032
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, source Priority|P2 |P5
--- Comment #5 from Ken Sharp imwellcushtymelike@gmail.com --- (In reply to Adam Bolte from comment #0)
It does this by printing the following warning message very frequently:
"Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead."
(line 488 of dlls/winex11.drv/xrandr.c as of 1.7.36)
The user is reminded of this every time winex11.drv is loaded, which is apparently quite frequently - even for command-line applications.
So this is about changing the console output for this specific warning? A minor patch should fix that.
https://bugs.winehq.org/show_bug.cgi?id=38032
--- Comment #6 from Adam Bolte abolte@systemsaviour.com --- (In reply to Ken Sharp from comment #5)
So this is about changing the console output for this specific warning? A minor patch should fix that.
Looks like there has been some progress made on #34348 with an Nvidia dev offering some possible direction, so maybe (hopefully!) the message will go away completely soon.
https://bugs.winehq.org/show_bug.cgi?id=38032
Robert Walker bob.mt.wya@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bob.mt.wya@gmail.com
--- Comment #7 from Robert Walker bob.mt.wya@gmail.com --- Created attachment 53932 --> https://bugs.winehq.org/attachment.cgi?id=53932 remove the sucky nvidia randr message patch
(In reply to Adam Bolte from comment #6)
(In reply to Ken Sharp from comment #5)
So this is about changing the console output for this specific warning? A minor patch should fix that.
Looks like there has been some progress made on #34348 with an Nvidia dev offering some possible direction, so maybe (hopefully!) the message will go away completely soon.
Thank god... I've been using this patch for a few months now. I don't want my console being spammed constantly!! No, I'm not going to use the nouveau driver with 970M ... :-)
https://bugs.winehq.org/show_bug.cgi?id=38032
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #8 from winetest@luukku.com --- Does this patch help?
https://bugs.wine-staging.com/show_bug.cgi?id=715
The message should be printed only once.
https://bugs.winehq.org/show_bug.cgi?id=38032
--- Comment #9 from Adam Bolte abolte@systemsaviour.com --- Unfortunately I'm not in a position to test currently. My desktop and laptop both use AMD graphics cards these days.
Actually I access to an old laptop with an Nvidia GPU which I could probably test with (if my spouse doesn't have data on it), but it'll need to be reinstalled, etc. No promises.
-
wine-bugs＠winehq.org