http://bugs.winehq.org/show_bug.cgi?id=8147
------- Additional Comments From ajrich(a)earthlink.net 2007-28-04 19:12 -------
I'm afraid I don't know how to find my system's ssh hostname.
--
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=1631
------- Additional Comments From hughes28105(a)gawab.com 2007-28-04 19:11 -------
this attachment may help the last line is this.
fixme:d3d:IWineD3DDeviceImpl_ValidateDevice (0x1bd700) : stub
fixme:d3d:IWineD3DDeviceImpl_ValidateDevice (0x1bd700) : stub
err:dsound:DSOUND_MixOne underrun on sound buffer 0x4d8e628
wine client error:9: write: Bad file descriptor
can this be of any help.
--
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=8199
Summary: hardcoded /usr/lib/libsicu*.a breaks biarch builds
Product: Wine
Version: CVS
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-patches
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rmh(a)aybabtu.com
The configure check for libsicu{uc,data}.a assumes these libraries can only be
found on /usr/lib or in a directory provided by the user. This breaks build on
multiarch systems, where /usr/lib/libsicu*.a are 64-bit, and 32-bit libraries
are available elsewhere. Depending on the system's binutils, this can result in
build failure or in libicu functionality being disabled (see
http://sourceware.org/ml/binutils/2007-04/msg00370.html).
Fortunately, wine doesn't need to know how to find the 32-bit lib directory,
because the toolchain is already capable of finding it. Having a fallback value
of "-lsicu*" is enough to grant the library will be static, since libicu uses
this "s" prefix to differenciate static libs.
--
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=8176
------- Additional Comments From floppie(a)quadra-tec.net 2007-28-04 18:19 -------
My intention was for this bug to be more broad than just EQ1. I wanted any
games that required texture wrapping to be linked to it, rather than just this one.
--
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=1631
------- Additional Comments From hughes28105(a)gawab.com 2007-28-04 18:10 -------
I have had problems with system shock 2 on 0.9.36. it look like the buffer is
having a problem is buffer is underrun. i have attach the debug log.
--
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=7682
vitaliy(a)kievinfo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #5990 is|0 |1
obsolete| |
------- Additional Comments From vitaliy(a)kievinfo.com 2007-28-04 17:50 -------
Created an attachment (id=5991)
--> (http://bugs.winehq.org/attachment.cgi?id=5991&action=view)
a better test
This time using existing env. variable.
This test does show that we do have a problem with the way our symlinks
configured to point into $HOME.
Should we disable this feature of NtQueryDirectoryFile? Or should we get rid of
the symlinks pointing to $HOME? However that won't fix it for existing
configurations (which we don't really care too much). Except this won't prevent
users from setting something like this and braking Wine.
I remember there was a huge discussion about this and it was decided that
symlinks would be the best solution. Apparently they are not. Quite opposite -
they do not 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.
http://bugs.winehq.org/show_bug.cgi?id=7698
------- Additional Comments From jrliggett(a)cox.net 2007-28-04 17:13 -------
Something else I just noticed: the crash always seems to occur when shooting
from a distance. If you keep your shots at close range, it might avoid the
crash. I just played for a good 30 minutes on de_dust2 and the map changed
before it crashed. Then we moved on to de_paranesi, where there's lots of
long-range shooting, and every time I get into a long-distance firefight, and I
hit something that kicks up some dust or debris, it crahses. So maybe this isn't
related to the HL2DM font bug?
--
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=8153
vitaliy(a)kievinfo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|jnewman(a)codeweavers.com |wine-bugs(a)winehq.org
--
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=8198
paloseco(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|Other |PC
--
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=7640
------- Additional Comments From vitaliy(a)kievinfo.com 2007-28-04 15:56 -------
Because no one found the real cause of this 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.
http://bugs.winehq.org/show_bug.cgi?id=7892
------- Additional Comments From blin(a)gmx.net 2007-28-04 15:51 -------
And you're sure that you're using native crypt32.dll? Not the builtin one wine
ships with?
--
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=8196
------- Additional Comments From volker.groeschel(a)sap.com 2007-28-04 15:25 -------
The device should be in the registry like it is in XP.
It does not need any dedicated driver, it works with the standard SCSI ASPI.
Since Ubuntu finds the device it should be possible to fill the registry
automatically.
How is that intended to work? How can I check what's going wrong?
When it is not possible to fix the configuration tool, can I fill the registry
manually? Which values would I need to make sure that it matches the
configuration of LINUX, e.g. when I start with the XP branch what do I need to
change?
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2]
"Interrupt"=dword:00000010
"IOAddress"=dword:0000b000
"Driver"="aic78xx"
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2\Scsi Bus 0]
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2\Scsi Bus 0\Initiator Id 7]
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2\Scsi Bus 0\Target Id 6]
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2\Scsi Bus 0\Target Id
6\Logical Unit Id 0]
"Identifier"="DVB2000 Nokia rulez 2.21"
"Type"="CommunicationsPeripheral"
"InquiryData"=hex:09,00,02,02,20,00,00,00,44,56,42,32,30,30,30,20,4e,6f,6b,69,\
61,20,72,75,6c,65,7a,20,20,20,20,20,32,2e,32,31
--
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=8193
------- Additional Comments From truiken(a)gmail.com 2007-28-04 15:17 -------
By msi.log, do you mean the last part of WINEDEBUG=+msi,+msidb wine setup.exe >&
msi.log? That's not wine writing to the file, that's bash redirecting standard
output to a file, which can be anywhere on the file system.
WINEDEBUG=+msi,+msidb,+file wine setup.exe >& ~/msi.log
That will put the log in your home directory. Next time you run the installer,
run it from the disk and make sure the drive is set up in winecfg.
(I still need the COD2.msi file attached here)
--
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=8193
------- Additional Comments From stfan4cjk(a)gmail.com 2007-28-04 15:12 -------
I am but I needed to copy the disk to the desktop because wine was trying to
right the msi.log to the disk
--
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.