[Bug 42726] New: Windows areempty and very small: null_driver instead of X11
https://bugs.winehq.org/show_bug.cgi?id=42726 Bug ID: 42726 Summary: Windows areempty and very small: null_driver instead of X11 Product: Wine Version: 2.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: pkrizek(a)tes.cz Distribution: --- Created attachment 57707 --> https://bugs.winehq.org/attachment.cgi?id=57707 screenshot: totalCmd. winecfg behaves the same way Building Wine from source. target: National Instruments RT Linux, 64bit 4.1.15-rt17-4.0.0f0 config: --disable-tests --with-x --without-xrender --without-freetype --enable-win64 Result: X-windows apps show empty and/or very small windows. They react to keyboard but there isn't anything rendered inside the windows. Text applications (e.g. wine64 cmd.exe) run OK. I tried to add debug prints into the code. Found out that gdi32/driver.c detects the X11 and looks up the X11 gdi_dc_funcs* but gdi32/bitblt.c/StretchBlt calls nulldrv_StretchBlt ignoring that there is X11 already detected. Same behavior when emulating a virtual desktop (copied ~/.wine/*.reg from a working install because even winecfg doesn't render). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42726 --- Comment #1 from Alexandre Julliard <julliard(a)winehq.org> --- The null driver thing is normal, but if you build with --without-freetype you won't get any text rendering, and the metrics will be all wrong. Don't do that. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42726 --- Comment #2 from Petr Křížek <pkrizek(a)tes.cz> --- The problem is that when I do ../wine-2.4/configure \ --disable-tests --with-x --without-xrender --enable-win64 /*i.e. I omitted the --without-freetype*/ then I'm getting configure: error: FreeType 64-bit development files not found. Fonts will not be built. Use the --without-freetype option if you really want this. and then make: *** No targets specified and no makefile found. Stop. ------------ But the following packages seem to be installed OK. # opkg list-installed | grep freetype libfreetype-dev - 2.5.4-r0.153 libfreetype6 - 2.5.4-r0.153 -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42726 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Alexandre Julliard <julliard(a)winehq.org> --- You can check config.log to see the exact error, then you should probably ask on the forum about the right packages to install for your distro. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42726 --- Comment #4 from Petr Křížek <pkrizek(a)tes.cz> --- I took a look into config.log. The ./configure script asks for $(freetype-config --cflags) but the /usr/bin/freetype-config from my distro reads just: #!/bin/sh echo '--should-not-have-used-/usr/bin/freetype-config' exit 1 Of course, this won't work. Let's look whether we borrow libfreetype* from another distro binaries or whether we build it from source. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=42726 Frédéric Delanoy <frederic.delanoy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Frédéric Delanoy <frederic.delanoy(a)gmail.com> --- Closing INVALID bugs -- 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.
participants (1)
-
wine-bugs@winehq.org