New strange errors when creating a new prefix

Questions about Wine on Linux
Locked
F_style
Level 4
Level 4
Posts: 155
Joined: Sat Sep 25, 2010 8:55 pm

New strange errors when creating a new prefix

Post by F_style »

Look, I know this is Wine forum, but I think a bit of background is needed to expose the issue. If you simply don't care, skip to the 5th paragraph.

Just installed openSUSE 12.3 64 bit with GNOME 3.6.2. This release of openSUSE came in fact with an ugly defect regarding Nvidia drivers, as I was told in the openSUSE community: when installing them (version 310.32, from their repository, of course) they no longer add the user to the video group, one must add it manually or else graphic environment will be totally destroyed after reboot (and I confirmed it...).

I did have one more strange thing: after first reboot with the driver and trying to reboot system asked me for my root password, but since then it hasn't asked me again.

Finally, updated the driver to version 310.44 via Yast and the repository, as always. Seemingly it went well, though before there was a message when selecting the G03 package to update: that there was a problem with the package and suggested action was replace (delete) old G03 and install new version. There was nothing new with the process, but the message showing up was new.

So finally installed latest Wine 1.5.27 from the Wine repository. Ran winecfg and now I got this:

Code: Select all

(user)@linux-loyv:~> winecfg
wine: created the configuration directory '/home/jc_lara/.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:storage:create_storagefile Storage share mode not implemented.
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:storage:create_storagefile Storage share mode not implemented.
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:iphlpapi:NotifyAddrChange (Handle 0xf4e308, overlapped 0xf4e320): 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.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
fixme:storage:create_storagefile Storage share mode not implemented.
p11-kit: couldn't load module: /usr/lib/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/pkcs11/gnome-keyring-pkcs11.so: no se puede abrir el fichero del objeto compartido: No existe el fichero o el directorio
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:iphlpapi:NotifyAddrChange (Handle 0xffe8d0, overlapped 0xffe8dc): 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/jc_lara/.wine' has been updated.
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.
After this, when running winecfg again:

Code: Select all

(user)@linux-loyv:~> winecfg
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.
err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
Later tried my game of always, Limbo, expecting indeed a big error and getting ready to take note of the ugly console output log. But surprisingly it ran normally well. I don't have more games for now, that's why I always test with this one. As a note, I always use emulated desktop in Wine settings.

What do you think can be happening? Should I worry about these nvidia-related winecfg errors?
User avatar
dimesio
Moderator
Moderator
Posts: 13368
Joined: Tue Mar 25, 2008 10:30 pm

Re: New strange errors when creating a new prefix

Post by dimesio »

If everything is working don't worry about messages in the console.
F_style
Level 4
Level 4
Posts: 155
Joined: Sat Sep 25, 2010 8:55 pm

Re: New strange errors when creating a new prefix

Post by F_style »

@Dimesio:
Do you still use openSUSE by chance? Have you tried latest release?
I ask this because, as an openSUSE user I thought you could know far more about the situation. And if I ask in openSUSE forums they'll say "ask on Wine forums", or if very *very* lucky, the same as you said.
Thanks.
User avatar
dimesio
Moderator
Moderator
Posts: 13368
Joined: Tue Mar 25, 2008 10:30 pm

Re: New strange errors when creating a new prefix

Post by dimesio »

I still use openSUSE, but haven't tried 12.3, and I am using an older Nvidia driver. The message is not unique to openSUSE; I've seen it in a couple of posts from users of other distros who were having problems. One did try nouveau as the message suggested and reported back that things were much worse with it--the game in question wouldn't start at all. If you do run into problems you could try nouveau (and please report back whether or not it works), but as long as you're not having problems, don't worry about it.
Locked