http://bugs.winehq.org/show_bug.cgi?id=4227
------- Additional Comments From dank(a)kegel.com 2007-20-03 22:25 -------
Amazingly, yes. Can't get the app to start, though.
WINEDEBUG=+ole ~/wine-git/wine QTPro.exe
shows approximately
...
trace:ole:RPC_GetLocalClassObject waiting for
L"\\\\.\\pipe\\{0EABB8C3-EB3F-4240-86D2-E574D40EA94A}"
trace:ole:create_local_service Attempting to start Local service for
{0eabb8c3-eb3f-4240-86d2-e574d40ea94a}
trace:ole:WINE_StringFromCLSID 0x4ab7e8->{0EABB8C3-EB3F-4240-86D2-E574D40EA94A}
err:ole:create_server class {0eabb8c3-eb3f-4240-86d2-e574d40ea94a} not registered
...
--
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.
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=7810
------- Additional Comments From giuseppe.bilotta(a)gmail.com 2007-20-03 20:34 -------
To elaborate further, the two possible approaches are:
1. removing the check on L124 and adding a line to ignore_error for
request_code == X_CreatePixmap and error_code == BadValue
or
2. use XListPixmapFormats to retrieve the supported pixmap formats, and check
against those instead of checking against the pre-fixed values. Retrieving the
supported pixmap formats can probably be done at driver initialization.
--
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=7810
Summary: "err:x11drv:X11DRV_CreateBitmap Trying to make bitmap
with planes=1, bpp=32" with a 24bit visual
Product: Wine
Version: 0.9.31.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-x11driver
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: giuseppe.bilotta(a)gmail.com
When running The Bat version 3.x I get a long string of errors
err:x11drv:X11DRV_CreateBitmap Trying to make bitmap with planes=1, bpp=32
I'm running the stock Debian X.org 7.1.0-15 with the open source nVidia driver
(nv) and the screen depth is 24 bit.
It is my understanding that the error line comes from line 124 of bitmap.c
http://source.winehq.org/source/dlls/winex11.drv/bitmap.c?v=wine-0.9.31#L124
and that the reason for the early warning is to prevent the call to
XCreatePixmap (on line 143 of the same file) from failing due to depth mismatch.
However, screen_depth and allowed pixmap depths are not always the same, as
shown by a call to xdpyinfo on my system:
number of supported pixmap formats: 7
supported pixmap formats:
depth 1, bits_per_pixel 1, scanline_pad 32
depth 4, bits_per_pixel 8, scanline_pad 32
depth 8, bits_per_pixel 8, scanline_pad 32
depth 15, bits_per_pixel 16, scanline_pad 32
depth 16, bits_per_pixel 16, scanline_pad 32
depth 24, bits_per_pixel 32, scanline_pad 32
depth 32, bits_per_pixel 32, scanline_pad 32
Given that the relevant code hasn't changed in 0.9.33, I think the code is
still valid.
The solution is probably to skip the explicit test for the bitmap depth on line
124 and rather check if XCreatePixmap generates some error after line 143. As
an alternative, the bitmap depth should be checked against all the pixmap depth
supported by the visual rather than just the monochrome and visual depth. But I
think the 'check after XCreatePixmap' solution is better.
I'm sorry I've never done any Xlib programming ever, or I'd try and provide a
patch myself.
--
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=7807
------- Additional Comments From russofris(a)hotmail.com 2007-20-03 18:28 -------
Louis, can you post your Arch type so they can eliminate this being AMD64 related?
--
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=6911
------- Additional Comments From gravillon(a)gmail.com 2007-20-03 18:00 -------
Hi, i got exactly the same problem and i solved it by configuring my video card
to work in 3D mode (GLX) under X11 - installed the driver module (nvidia...) and
configured properly my /etc/X11/xorg.conf -. Now it works perfectly.
For information, here is some extracts of my xorg.conf:
#Check the "glx is in ur Module section:
Section "Module"
Load "glx"
[...]
EndSection
#And be sure to use the properly 3d driver, 'nvidia' for me, not the 'nv' one
Section "Device"
Identifier "Card0"
Driver "nvidia"
Option "AddARGBGLXVisuals" "true"
Option "RenderAccel" "true"
Option "AllowGLXWithComposite" "True"
VendorName "nVidia Corporation"
BoardName "NV34 [GeForce FX 5500]"
BusID "PCI:1:0:0"
EndSection
Section "Extensions"
Option "Composite" "enable"
EndSection
And voila, enjoy ,)
--
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=7653
------- Additional Comments From zarquon(a)t-online.de 2007-20-03 17:14 -------
The important question is: what do you intend to do about it? Nothing and kill
Wine once and for all on older platforms due to what's possibly a rather common
bug (if it also applies to XF86), or try to avoid the problem there and only
affect (newer) software that absolutely requires multithreaded GDI? To me this
looks like a classic case of a configure option.
Generally speaking, Wine developers should leave their new rigs with the latest
of everything and try to get it to run on more dated systems now and then; an
extremely frustrating experience, I can assure you.
--
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=7554
mikolaj.zalewski(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Component|wine-richedit |wine-shell32
Ever Confirmed| |1
------- Additional Comments From mikolaj.zalewski(a)gmail.com 2007-20-03 16:47 -------
With a long string I've been able to reproduce it. It looks like a bug in our
autocomplete in shell32.
--
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=5347
------- Additional Comments From mikolaj.zalewski(a)gmail.com 2007-20-03 16:37 -------
Created an attachment (id=5469)
--> (http://bugs.winehq.org/attachment.cgi?id=5469&action=view)
patch to see the stack trace
Could you run Photoshop with this patch applied and attach the console output.
This patch will cause a crash but from the stack trace we will know why this
function is called like that. Of coures after the test remove this patch as it
may result in crashes in other programs.
--
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.