http://bugs.winehq.org/show_bug.cgi?id=3794
------- Additional Comments From saulius.krasuckas(a)elst.vtu.lt 2005-10-11 11:44 -------
It seems the log shows shutdown phase already. I guess next I'd try "+loaddll"
and "+process,+tid,+loaddll,+module,+snoop,warn+all" flags, but I hardly can
tell how much lines we'll need. :-/
Maybe other people will suggest something more solid.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=3573
------- Additional Comments From Speeddymon(a)gmail.com 2005-10-11 11:29 -------
Agreed about the REAL support thing. Although, if Eugene reads this bug again,
we also have determined it to be a bad patch in Xorg (read poorly thought out).
So we are attempting to see if someone else can take a look at it and try to
fix it in the next round of patches for Xorg.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=2885
------- Additional Comments From saulius.krasuckas(a)elst.vtu.lt 2005-10-11 11:08 -------
* Andreas wrote:
|
| > is this on a completely fresh install?
|
| No. And why would it be?
Sometimes it's easier to find a bug if you test app without having additional
stuff in the system.
| > (so after rm -rf ~/.wine) If not , please try on a fresh install.
|
| Not a chance in hell!
| If you seriously think I'll reinstall all apps that need registry entries,
| among those rather fickly ones like the SoF series, you've got another
| thing coming. If you can give me a list of potentially dangerous registry
| entries, I'll check for those, but I absolutely, positively draw the line
| at a fresh install.
Hey, don't treat "rm -rf" in an absolute scale. :-)
Fresh install can be tested without losing the old one. Put the old one in a
safe place and you are done. In UNIX all stuff is files, so you just operate on
them in a way you like. :-P
| What I did try was renaming all *.reg files (and config) in my ~/.wine
| directory so none of the files should have been seen by Wine, and the
| program failed in the same way. That could also have been caused by
| then missing registry entries, though, but that's as close to a fresh
| install as I'm going to go.
Yes, but just try:
$ mkdir ~/BACKUPS
$ mv ~/.wine ~/BACKUPS
$ wineprefixcreate
That should put your existing wine setup into a safe place and should create a
new fresh "~/.wine" directory, AFAIK.
| > It seems at first it is loaded by x11drv, then unloaded, and then loaded
| > again by e2_d3d8_driver_mfc.dll. My Max Payne is demo v1.05.
|
| That rings a bell: Bug 2725, which I also get when a 3D rendering context
| (OpenGL in 2725) is destroyed and then immediately reopened (when it fails).
| This may even be driver-specific.
If fresh "~/.wine" doesn't help, then add +opengl flag to the previous
combination mentioned here and attach the output, please.
And one wild guess: does switching a Desktop Double Buffering checkbox (winecfg
-> Graphics) make any difference?
--
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.
http://bugs.winehq.org/show_bug.cgi?id=3805
Summary: Font antialiasing does not work since 20050930
Product: Wine
Version: 0.9.1.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-gdi-(printing)
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: t.artem(a)mailcity.com
On my computer (Fedora Core 4 partly upgraded to FC5/Rawhide) font antialiasing
doesn't work in Wine versions 20050930, 0.9 and 0.9.1 (which was released today).
All previous wine versions work fine.
This is the extract of ./configure script:
checking for FT_Init_FreeType in -lfreetype... yes
checking for freetype-config... freetype-config
checking for ft2build.h... yes
checking for freetype/freetype.h... yes
checking for freetype/ftglyph.h... yes
checking for freetype/tttables.h... yes
checking for freetype/ftnames.h... no
checking for freetype/ftsnames.h... yes
checking for freetype/ttnameid.h... yes
checking for freetype/ftoutln.h... yes
checking for freetype/ftwinfnt.h... yes
checking for freetype/internal/sfnt.h... yes
Note that I have freetype-2.1.10 installed.
Both older wine versions and newer wine versions have `libfreetype.so.6` string
compiled into gdi32.dll.so library.
Strace of regedit run tells me that wine indeed tries opening libfreetype
library and MS core fonts installed on my Linux box:
strace -fF regedit
...
[pid 15899] open("/usr/lib/libfreetype.so.6", O_RDONLY) = 12
[pid 15899] open("/usr/X11R6/lib/X11/fonts/TTF/arial.ttf", O_RDONLY) = 12
[pid 15899] open("/usr/X11R6/lib/X11/fonts/TTF/verdana.ttf", O_RDONLY) = 12
[pid 15899] open("/usr/X11R6/lib/X11/fonts/TTF/times.ttf", O_RDONLY) = 12
...
--
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.
http://bugs.winehq.org/show_bug.cgi?id=3804
------- Additional Comments From guillermo.e.reyes(a)gmail.com 2005-10-11 10:47 -------
Created an attachment (id=1327)
--> (http://bugs.winehq.org/attachment.cgi?id=1327&action=view)
Test App with both failing and good.
The file includes 2 .EXE files and the .DLLs needed to be run.
File: Pruebas-normal.exe (this is the executable that if failing to display the
characters at the edit field).
File: Pruebas-rich-text.exe (this is the executable that displays the
characters at the edit field).
The difference between both files is that in the "Pruebas-normal.exe" the edit
field is a normal edit field and in the "Pruebas-rich-text.exe" the edit field
is formatted as Rich Text Format field.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=3804
Summary: Problem with character display
Product: Wine
Version: 0.9
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-gui
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: guillermo.e.reyes(a)gmail.com
Hello,
I have an application I made with WinDev8 (http://www.windev.com).
The application is a simple window which requires the user to fill some
info in a field and then displays some information regarding the code
the user entered.
The problem I'm having is that when I run the application with WINE, I
can correctly see the labels that describe each of the fields, but when
I start typing in the field, I only see the cursor moving, but there's
no display of the characters.
I have installed the .TTF files and have used the same font on the
label and on the edit field. I can see the correct font being
displayed in the windows at the label, but in the edit field I do not.
The characters are being fed to the application, the problem is I can't
see them; neither the one's I enter, but also the one's the application
fills.
The only way I could saw the characters is by changing the edit field
to RTF format, but this gives me some problem when trying to identify
the data the user entered.
Hope you can help me!
Regards,
Guillermo
--
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.