September 2006 - Wine-Bugs - list.winehq.org

[Bug 6236] strange characters in progress bar
by Wine Bugs Sept. 21, 2006

Sept. 21, 2006

http://bugs.winehq.org/show_bug.cgi?id=6236 ------- Additional Comments From the3dfxdude(a)gmail.com 2006-20-09 22:22 ------- It seemed in both your comments #2 and #7 you were blaming a bad or misconfigured fontforge. That is why I asked you if you looked. What I'm thinking now is the SuSE Wine RPM was built correctly, and his compiled copy is missing the wine fonts. I do not agree that his SuSE RPM is at fault because my build work the same, and so does two other people. Regardless of what he is doing, the preference of Marlett is fairly unfriendly to the user in this situation. That is why I mentioned the order. It might need to be looked at because there are fonts on his system that do work. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6236] strange characters in progress bar
by Wine Bugs Sept. 21, 2006

Sept. 21, 2006

http://bugs.winehq.org/show_bug.cgi?id=6236 ------- Additional Comments From truiken(a)gmail.com 2006-20-09 21:31 ------- Jesse, did you even look at the screen shots? The first screen shot, with the bad font problem, was taken with Wine from the Suse rpm. The second screenshot, with a readable font (albeit small), was taken with Wine from compiled Git. I didn't say it was a problem with the distro. It's a problem with the Suse Wine rpm. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6236] strange characters in progress bar
by Wine Bugs Sept. 21, 2006

Sept. 21, 2006

http://bugs.winehq.org/show_bug.cgi?id=6236 ------- Additional Comments From the3dfxdude(a)gmail.com 2006-20-09 20:59 ------- James did you even look at the screen shots? He correctly compiled wine with working fonts. The weird symbols he is talking about in the first screenshot is the from the Marlett font that Wine built. The second screen shot is a font from the Bitstream Vera font, which is on practically every distro. I was able to overrride Marlett with Vera two ways, by copying it into the \windows\fonts folder or by removing all wine built fonts. To get a more readable font instead of Vera, don't copy Vera in to the \windows\fonts folder, and just remove Marlett from /usr/share/wine/fonts, keeping the rest intact. I think it chooses the System font then... What the problem is here is Wine's preference of Marlett, which cannot display the correct characters. The order goes something like this: 1. Choose a font based on registry keys (there are none by default) 2. Choose a font from \windows\fonts (there are none installed here by default) 3. Choose a font from /usr/share/wine/fonts (prefers marlett) 4. Choose a font from based X font paths (varies according to settings) This is not simply a distro problem. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6236] strange characters in progress bar
by Wine Bugs Sept. 21, 2006

Sept. 21, 2006

http://bugs.winehq.org/show_bug.cgi?id=6236 ------- Additional Comments From truiken(a)gmail.com 2006-20-09 20:03 ------- Thomas, you mistake my dry tone for anger. I have no hard feelings toward your bug report; that would be silly. If the Suse package produces bad fonts, please contact the Suse project, or even the person who makes the Suse wine package, meissner(a)suse.de. > there is no way that a dummy user can understand this cryptic fixme-message The fixme isn't meant to be understood by a user. It's a reminder to the developer that something needs to be fixed. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6236] strange characters in progress bar
by Wine Bugs Sept. 21, 2006

Sept. 21, 2006

http://bugs.winehq.org/show_bug.cgi?id=6236 ------- Additional Comments From thomas(a)haeber.de 2006-20-09 19:55 ------- Sorry for my incompetence, but please calm down. I've not reopened this report and I do nor want any wonders from you. I have no other fonts, the prepackaged wine.rpm of SuSE 10.1 has only this strange font (not readable), the self compiled with additional fonts still has hard to read fonts. IMO this is not only a problem of the users config, there is no way that a dummy user can understand this cryptic fixme-message. How can a user relize which font the programm needs? There should be a more informative message for users without wine or compile knowledge, this would improve the usability. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6243] New: AC_CHECK_LIB not recognizing FreeType on Kubuntu AMD64
by Wine Bugs Sept. 21, 2006

Sept. 21, 2006

http://bugs.winehq.org/show_bug.cgi?id=6243 Summary: AC_CHECK_LIB not recognizing FreeType on Kubuntu AMD64 Product: Wine Version: CVS Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-binary AssignedTo: wine-bugs(a)winehq.org ReportedBy: wine(a)eternaldusk.com Compiling Wine on my Kubuntu AMD64 system produces the following Warning/Error: -------------------- configure: WARNING: Your system appears to have the FreeType 2 runtime libraries configure: WARNING: installed, but 'freetype-config' is not in your PATH. Install configure: WARNING: the freetype-devel package (or its equivalent on your distribution) configure: WARNING: to enable Wine to use TrueType fonts. configure: WARNING: FreeType is missing. configure: WARNING: Fonts will not be built. Dialog text may be invisible or unaligned. Configure finished. Do 'make depend && make' to compile Wine. -------------------- I do not get the error if I compile it in a 32-bit chroot. When ignoring the warning and compiling 64-bit, everything other than fonts in some apps seems to run fine. I did some digging into configure.ac and found the cause of the warning: --------------------- checking for freetype-config... freetype-config checking for FT_Init_FreeType in -lfreetype... no ******************* JJL - ft_lib = no, FREETYPELIBS=-L/usr/local/lib -Wl,--rpath -Wl,/usr/local/lib -lfreetype -lz, FREETYPEINCL=-I/usr/local/include/freetype2 -I/usr/local/include checking for parport header/ppdev.h... yes ... evil(a)pluto:~/install/wine$ ll /usr/local/lib/libfreetype* -rw-r--r-- 1 root root 3571116 2006-09-20 14:30 /usr/local/lib/libfreetype.a -rwxr-xr-x 1 root root 842 2006-09-20 14:30 /usr/local/lib/libfreetype.la lrwxrwxrwx 1 root root 21 2006-09-20 14:30 /usr/local/lib/libfreetype.so -> libfreetype.so.6.3.10 lrwxrwxrwx 1 root root 21 2006-09-20 14:30 /usr/local/lib/libfreetype.so.6 -> libfreetype.so.6.3.10 -rwxr-xr-x 1 root root 2075854 2006-09-20 14:30 /usr/local/lib/libfreetype.so.6.3.10 --------------------- Apparently the AC_CHECK_LIB call for FT_Init_FreeType is failing As you can see: Not only do I have FreeType2 (which seems to work fine compiling every other app that needs it), I even upgraded from the latest CVS to see if it corrected the problem. It didn't. I know almost nothing of autotools/autoconf. Is this a bug in the 64-bit AC_CHECK_LIB, or could there something wrong with the parameters being passed to it that would still work on 32-bit? Here's how the output of freetype-config --cflags and --lib varies between my 32-bit chroot and my 64-bit environments: 32-bit: ------------ evil(a)pluto:~$ freetype-config --cflags -I/usr/include/freetype2 evil(a)pluto:~$ freetype-config --libs -lfreetype -lz 64-bit: ----------- evil(a)pluto:~$ freetype-config --cflags -I/usr/local/include/freetype2 -I/usr/local/include evil(a)pluto:~$ freetype-config --libs -L/usr/local/lib -Wl,--rpath -Wl,/usr/local/lib -lfreetype -lz I'm wondering if all that extra stuff in the libs variable is messing with AC_CHECK_LIB's results. I tried to override the libraries myself, but I have another problem in that whenever I make changes to configure.ac and run "autoconf configure.ac > configure", I get a lot of SED errors like this: ... config.status: creating dlls/ws2_32/tests/Makefile sed: file ./confstattYvqXN/subs-4.sed line 14: unterminated `s' command config.status: creating dlls/wsock32/Makefile sed: file ./confstattYvqXN/subs-4.sed line 14: unterminated `s' command ... I'm guessing there's a parameter that I'm unaware of that I need to be using on the autoconf command. -J -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 4894] Custom BOINC doesn't work
by Wine Bugs Sept. 21, 2006

Sept. 21, 2006

http://bugs.winehq.org/show_bug.cgi?id=4894 ------- Additional Comments From karl.glatz(a)gmail.com 2006-20-09 19:18 ------- ArtRage 2 has the same problem! Download: http://www2.ambientdesign.com/files/ar2winfree.exe --- wine ArtRage.exe fixme:actctx:FindActCtxSectionStringW 00000000 (null) 2 L"msvcr80.dll" 0x347b0c err:module:LdrInitializeThunk "MSVCR80.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\\Programme\\Ambient Design\\ArtRage 2\\ArtRage.exe" failed, status c0000142 --- -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6236] strange characters in progress bar
by Wine Bugs Sept. 21, 2006

Sept. 21, 2006

http://bugs.winehq.org/show_bug.cgi?id=6236 truiken(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED ------- Additional Comments From truiken(a)gmail.com 2006-20-09 19:11 ------- Closing again. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6236] strange characters in progress bar
by Wine Bugs Sept. 21, 2006

Sept. 21, 2006

http://bugs.winehq.org/show_bug.cgi?id=6236 truiken(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID ------- Additional Comments From truiken(a)gmail.com 2006-20-09 19:11 ------- This is another invaild report where the proper libs and packages aren't installed before compiling wine, so the fonts are messed up. > The fixme still appears, maybe there could be a better notification for users with bad configured font settings or a message which font is missing ./configure --verbose will tell you what packages you're missing. Wine can only work with the fonts you have installed on your system, so if you want a better font, install more fonts. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 6242] Regression in 0.9.21 causes Full Tilt Poker to crash after login
by Wine Bugs Sept. 20, 2006

Sept. 20, 2006

http://bugs.winehq.org/show_bug.cgi?id=6242 scott(a)open-vote.org changed: What |Removed |Added ---------------------------------------------------------------------------- Component|wine-user |wine-ole ------- Additional Comments From scott(a)open-vote.org 2006-20-09 18:03 ------- I've attached a log of the crash. The line starting with: fixme:ole:OleCreate {8856f961-340a-11d0-a96b-00c04fd705a2} {00000112-0000-0000-c000-000000000046} semi-stub! is what happens after hitting enter at the login screen, which leads me to believe this might be a regression in OLE. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0