[Bug 31655] Upgrading Wine destroys registry entries

[wine-bugs at winehq.org]

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

Ken Sharp <imwellcushtymelike at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #41616|0                           |1
        is obsolete|                            |
  Attachment #41617|0                           |1
        is obsolete|                            |
  Attachment #41637|0                           |1
        is obsolete|                            |
  Attachment #41896|0                           |1
        is obsolete|                            |

--- Comment #9 from Ken Sharp <imwellcushtymelike at gmail.com> ---
Created attachment 59993
  --> https://bugs.winehq.org/attachment.cgi?id=59993
system.reg diff

Right... this is actually really easy to recreate. Remember "fgrep VMR
~/.wine/system.reg" as it indicates that a (substantial) change to the registry
has taken place.

1. "winetricks quartz"
2. "wineboot"
3. "fgrep VMR ~/.wine/system.reg" = nothing
4. "wineboot -u" (or upgrade Wine)
5. fgrep VMR ~/.wine/system.reg" =

@="VMR Mixer"
@="VMR Allocator Presenter 9"
@="VMR Allocator Presenter DDXcl Mode"
@="VMR ImageSync"
@="VMR Allocator Presenter"
@="VMR Mixer 9"
@="VMR ImageSync 9"

So it is the presence of a native quartz.dll which is causing the registry to
change to the point in which Slingplayer (for example) will no longer function
correctly.

I am assuming that this shouldn't occur, but updating Wine occurs more
frequently than updating Windows versions.

All in one go:

$ winetricks -q quartz; wineserver -w; fgrep VMR ~/.wine/system.reg; wineboot
-u; wineserver -w; fgrep VMR ~/.wine/system.reg

"wineboot" ("wineboot --init") runs the same update_wineprefix() function as
"wineboot -u", but the -u forces the update.

case 'u': update = TRUE; break;

if (init || update) update_wineprefix( update );

https://source.winehq.org/source/programs/wineboot/wineboot.c#0989

Anyway...

During this "update" process a whole bunch of registry entries are added (or
modified). I cannot find a source for these entries so I can only assume it to
have something to do with quartz.dll interacting with... ? I tried "wine
regsvr32 quartz.dll" which succeeds but this doesn't seem to have the same
effect on the registry.

I couldn't find any useful traces but I assume a +relay would tell me. I'm
hoping that somebody knows how this all works, though.

Attached is a registry diff with a lot of repetitive stuff clipped out. You can
see a lot of quartz related stuff has been added.

Slingplayer can't be the only application affected by this, it just can't...

-- 
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.