http://bugs.winehq.org/show_bug.cgi?id=10029
Summary: Tahoma entry in registry, but tahoma related errors re- occur followed by registry entry vanishing Product: Wine Version: 0.9.47. Platform: PC-x86-64 URL: http://www.invelos.com/Downloads.aspx OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: wine-misc AssignedTo: wine-bugs@winehq.org ReportedBy: Stuart@houseofanime.org
The recent wine release (0.9.47) mentioned a change relating to the Tahoma font - a font which causes issues for one of my applications, DVD Profiler. To se if this resolved the issue, I tried upgrading from wine 0.9.46 to 0.9.47 with a fresh .wine directory to see what happened.
In 0.9.46, the following would be observed behaviour with a typical install: 1) Run winecfg as normal 2) Install gecko using winetricks 3) Run setup.exe for DVD Profiler 4) Go through installation without issues 5) Run DVD Profiler and be inundated with 'invalid floating point' errors. 6) Kill application. 7) Add tahoma.ttf to fonts directory 8) Add tahoma entry to registry under "HKEY_LOCAL_MACHINE/Software/Miscrosoft/WindowsNT/CurrentVersion/Font" 9) Run DVD Profiler, get one 'invalid floating point' error (bug 8460), and then the application runs (mostly) as expected.
In 0.9.47, I confirmed that a) the font directory was empty, and b) the tahoma registry entry as described under step 8 above existed after running winecfg, without me having to enter it. I then ran a similar process to that described above: 1) - 4) as before 5) Unexpectedly got same response
!!! Checking, the registry entry that was confirmed before installing DVD Profiler was gone!
6+) as before.
In summary, the tahoma registry entry appeared at winecfg and then vanished when it was required. Otherwise, performance was as 0.9.46.
http://bugs.winehq.org/show_bug.cgi?id=10029
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
--- Comment #1 from Austin English austinenglish@gmail.com 2008-04-15 01:41:14 --- Is this still an issue in current (0.9.59 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=10029
--- Comment #2 from Stuart Middleton Stuart@houseofanime.org 2008-04-16 10:39:10 --- Yes, but I do have more to add (only just discovered this).
There is a difference in behaviour depending on whether I run winecfg or not. Note that the user manual in the Wiki currently suggests that winecfg should be run as part of the setup process, but a query on the user forum / mailing list indicated that winecfg is not required / should not be run.
Anyway,
If you run winecfg as described in step 1), you get the bahaviour as described (i.e. the tahoma entry in the registry vanishes when you run the app and you have to re-enter it manually using winetricks and regedit). However, if you omit running winecfg, the application runs fine without the tahoma-based errors and there is no funny business with a disappearing tahoma registry value.
Basically, it looks as though there's something funny going on when you use winecfg to trigger the .wine directory creation. It seems to somehow create a tahoma registry entry that does not persist as it should.
Hope that helps.
http://bugs.winehq.org/show_bug.cgi?id=10029
Stuart Middleton Stuart@houseofanime.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #3 from Stuart Middleton Stuart@houseofanime.org 2008-12-02 08:51:11 --- Can no longer reproduce error in latest version (1.1.9).
http://bugs.winehq.org/show_bug.cgi?id=10029
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from Alexandre Julliard julliard@winehq.org 2008-12-05 11:12:56 --- Closing bugs fixed in 1.1.10.