http://bugs.winehq.org/show_bug.cgi?id=1163
Steven Edwards <winehacker(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |winehacker(a)gmail.com
--- Comment #8 from Steven Edwards <winehacker(a)gmail.com> 2007-12-19 06:12:20 ---
Can we get a test app that shows this and a retest?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7150
Steven Edwards <winehacker(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |winehacker(a)gmail.com
--- Comment #4 from Steven Edwards <winehacker(a)gmail.com> 2007-12-19 06:11:14 ---
So do we need to implement our own shaping algorithm now that we are not using
libICU?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=1236
Steven Edwards <winehacker(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |winehacker(a)gmail.com
--- Comment #6 from Steven Edwards <winehacker(a)gmail.com> 2007-12-19 06:09:15 ---
This needs a retest
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=609
Steven Edwards <winehacker(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |winehacker(a)gmail.com
--- Comment #7 from Steven Edwards <winehacker(a)gmail.com> 2007-12-19 06:08:45 ---
This should be resolved now. Maarten Lankhorst implemented Bidi in gdi32 so we
no longer depend on libICU. If there are still issues they should be opened as
new bugs and this meta bug closed.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8540
Sven <catnip(a)web.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |catnip(a)web.de
--- Comment #8 from Sven <catnip(a)web.de> 2007-12-19 04:13:09 ---
Same problem with Radeon HD2600 and newest ATI drivers.
Have to set UseGLSL=disabled for now.
What's the meaning of "0:1:"? My DISPLAY is ":0.0"
fglrx 8.43.2
wine 0.9.51
fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #1:
"Fragment shader was successfully compiled to run on hardware.\nWARNING: 0:1:
extension 'GL_ARB_draw_buffers' is not supported"
fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #2:
"Vertex shader was successfully compiled to run on hardware.\n"
fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #3:
"Fragment shader(s) linked, vertex shader(s) linked."
...
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7711
--- Comment #26 from Hans Leidekker <hans(a)it.vu.nl> 2007-12-19 03:09:58 ---
Please repeat the steps from comment #18 with step 1 replaced with
this one:
1. WINEDEBUG=+explorer wine winefile > explorer.log 2>&1
and attach the log file here.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7711
--- Comment #25 from Alexander K. Seewald <alex(a)seewald.at> 2007-12-19 01:48:48 ---
I have the following hal libraries (debian etch packages) installed. AFAIK the
hal works perfectly under normal linux (otherwise the drive would not attach),
so what's the problem with wine here?
ii hal 0.5.8.1-9
Hardware Abstraction Layer
ii libhal-dev 0.5.8.1-9
Hardware Abstraction Layer - development fil
ii libhal-storage-dev 0.5.8.1-9
Hardware Abstraction Layer - development fil
ii libhal-storage1 0.5.8.1-9
Hardware Abstraction Layer - shared library
ii libhal1 0.5.8.1-9
Hardware Abstraction Layer - shared library
AFAIK wine has everything it needs - configure --verbose gives:
checking dbus/dbus.h usability... yes
checking dbus/dbus.h presence... yes
checking for dbus/dbus.h... yes
checking hal/libhal.h usability... yes
checking hal/libhal.h presence... yes
checking for hal/libhal.h... yes
checking for dbus_connection_close in -ldbus-1... yes
checking for -lhal... libhal.so.1
I've noted that in wine/dlls/hal, in hal.spec there are almost only stubs,
except for...
@ stdcall -norelay KfAcquireSpinLock(ptr)
@ stdcall -norelay KfLowerIrql(long)
@ stdcall -norelay KfRaiseIrql()
@ stdcall -norelay KfReleaseSpinLock(ptr long)
Is there a known hal-related problem with linux kernel 2.6.23-rc3? What should
I do next to ensure a working hal up to at least device broadcast on plugging
in? And how exactly do I debug this? (i.e. is there a proper +debug parameter
to get the device notifications from hal-layer?)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=4130
--- Comment #4 from Lei Zhang <thestig(a)google.com> 2007-12-18 18:16:29 ---
I don't think it's a problem anymore. Xinerama support is much better now. Dan,
care to comment on this?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7711
--- Comment #24 from Hans Leidekker <hans(a)it.vu.nl> 2007-12-18 14:24:00 ---
The way you have set things up means there's no notification of any kind
that a new drive has arrived and I doubt that this app will poll for new
drives. With properly configured dbus/hal Wine sends a broadcast message
when a new drive arrives, which may not be sufficient either, but it's
certainly worth trying.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8868
--- Comment #8 from Mike Halcrow <winehq.org(a)halcrow.us> 2007-12-18 14:20:41 ---
For the record, I still run with 0.9.38+pbuffer because fbo gives a noticeable
performance hit.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.