http://bugs.winehq.org/show_bug.cgi?id=18095
Summary: VisualFEA's Toolbar is broken (does no line wrapping)
Product: Wine
Version: 1.1.19
Platform: PC-x86-64
URL: http://www.visualfea.com/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cs071007(a)fhstp.ac.at
Created an attachment (id=20529)
--> (http://bugs.winehq.org/attachment.cgi?id=20529)
VisualFEA Win vs. Wine
The Item toolbar (right side of screen) in visualfea does not apply line
wrapping as it does in windows, making the app unusable for work. Rest of the
app seems to work quite nicely (applying boundaries and so on, solver,
visualization, ...)
Wine does not give any warnings in the console, though (is there some verbose
option?)
Ah, I'll just attach a screen of win & wine so you know what I'm talking about.
It's the same install in both cases. Jnstaller ran in wine, windows only has
access to wine's program dir through a network share ;)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=18018
Summary: Gun Metal is unresponsive to joystick
Product: Wine
Version: 1.1.10
Platform: PC-x86-64
URL: http://www.gamershell.com/download_866.shtml
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: shacklein(a)gmail.com
I noticed this bug in 1.1.19 and tested it in my earliest pre-compiled package
too (1.1.10) and it was present there.
The problem is that Gun Metal does not seem to respond to my joystick at all
(Playstation Dualshock-style controller). However, the joystick works fine with
other applications in Wine, including GTA:San Andreas.
URL is to the Gun Metal demo version 1.14 which exhibits the problem. I've
tested with both evdev and js devices. I'm unsure what additional information
to supply, such as debug logs. :)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=26365
Summary: Geneforge 1 - text gets cut away
Product: Wine
Version: 1.3.14
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xaron77(a)fastmail.fm
Text gets cut-away on the right side of dialogue screen (letters often get cut
in half) and character statistics screen. No errors are displayed.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=24147
Summary: Worms Reloaded: Screen position issues at non-native
resolution
Product: Wine
Version: 1.3.1
Platform: x86
URL: http://steampowered.com
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: adys.wh(a)gmail.com
Created an attachment (id=30389)
--> (http://bugs.winehq.org/attachment.cgi?id=30389)
Screenshot of behaviour
See attached screenshot.
At resolutions other than native, the game screen "slides" towards the
bottomleft and hides part of the screen outside the display.
err:ole:RevokeDragDrop invalid hwnd (nil)
err:ole:RevokeDragDrop invalid hwnd 0x50130
err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful --
perhaps display has changed?
err:ole:CoGetClassObject class {074b110f-7f58-4743-aea5-12f15b5074ed} not
registered
err:ole:CoGetClassObject no class object {074b110f-7f58-4743-aea5-12f15b5074ed}
could be created for context 0x1
err:ole:CoInitializeEx Attempt to change threading model of this apartment from
multi-threaded to apartment threaded
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x2953530,0x2953490): stub
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=32265
Bug #: 32265
Summary: Polycom People+Content IP crashes when attempting to
stream desktop to remote display
Product: Wine
Version: unspecified
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: aboyd(a)fusionio.com
Classification: Unclassified
Created attachment 42578
--> http://bugs.winehq.org/attachment.cgi?id=42578
Backtrace of PPCIP crash
When I try to stream my desktop to a remote display (a Polycom HDX 7000 HD)
using People+Content IP, I can connect to the display fine, but when I press
the play button, PPCIP freezes for about 20 seconds, then crashes.
I've attached the backtrace.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=27798
Summary: GTA3 & GTAVC rendering is messed up
Product: Wine
Version: 1.3.23
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: b7.10110111(a)gmail.com
See http://i.imgur.com/EigrV.png
Works correctly in 1.3.22, appears in 1.3.23, remains in 1.3.24.
Reproducible on my intel (EEE PC 901) video:
Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
, but NOT on nvidia gtx460.
Will try to do regression testing, but... well, intel Atom...
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=30837
Bug #: 30837
Summary: Star Trek Online doesn't detect joystick/gamepad
Product: Wine
Version: 1.5.5
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: vitor.dominor(a)gmail.com
Classification: Unclassified
Recently I decided to try playing Star Trek Online with one of my old but still
working xbox 1 gamepads. For that purpose, I installed the xboxdrv (the
userspace driver for xbox 360 and 1 gamepads) and after running xboxdrv with
the command xboxdrv --silent --trigger-as-button, I started the game. The game
has support for joysticks (I made sure I enabled joystick support in the
in-game options). However, the game does not detect it, since it does not
respond to any button presses or axis movements from the gamepad.
When running the game from the terminal, the output I get with the gamepad
attached to the PC is attached to this bug report.
I have tried running the game natively on Windows 7 and XP SP3 with the gamepad
attached and it is detected and runs as expected. Furthermore, by running STO
with apimonitor from http://www.rohitab.com/apimonitor in Windows, I was able
to determine that the game uses direct input 8, specifically the
IDirectInputDevice8 and IDirectInput8 interfaces, to detect and control the
system mouse and any attached joystick. It uses in particular the
IDirectInput8::EnumDevices to find any available joysticks.
In order to determine if this is an issue specific to this game running on
Wine, I tried using the gamepad with another game well supported by wine and
which also supports joysticks: Trackmania Nations Forever. This one detects the
gamepad as a joystick automatically and by adding +dinput to WINEDEBUG, I
noticed the following line on the output:
Code:
trace:dinput:IDirectInputWImpl_EnumDevices (this=0x12f718,0x0004
'DIDEVTYPE_JOYSTICK',0x8fc5a0,0x12238a0,0001).
After that, wine outputs successfull detection of the joystick:
Code:
trace:dinput:find_joydevs Found a joystick on /dev/input/event16: Xbox Gamepad
(userspace driver) ({9e573eda-7734-11d2-8d4a-23903fb6bdf7})
Next, while running STO on wine with WINEDEBUG="+dinput":
and while the game detects and initializes the system mouse through dinput, it
seems to initialize the IDirectInput8 Interface, but it does not enumerate any
joystick unlike Trackmania.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=26160
Summary: Broken control path in mcicda
Product: Wine
Version: 1.3.13
Platform: x86
OS/Version: Mac OS X 10.5
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winmm&mci
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hoehle(a)users.sourceforge.net
I'm thankful to C. Robinson for making mcicda work on my Linux machines since
wine-1.1.5. Since then the code supports 2 modes of operation, either via
- IOCTL_CDROM_*_AUDIO (PLAY/STOP/PAUSE/RESUME/SEEK)
- or via a separate thread using DirectSound with
IOCTL_CDROM_RAW_READ. READ_TOC is needed in both modes.
However,
commit 8afa626faa3c5aa2d32d17dca77edaf9efb3a5da
uses as selector
if (wmcda->hThread != 0) {
which causes inconsistent results as the thread may be long dead. I believe
that is not the correct way to select whether to invoke either
thread/DS+RAW_READ commands or IOCTL_CDROM_*_AUDIO ones.
Consider this sequence of MCI commands:
cmd hThread comment
play -- start hThread
stop # !0 => SetEvent stopEvent, hThread becomes 0
stop # =0 => DeviceIoControl
resume # =0 => DeviceioControl
play
resume # !0 => DSB+Play, unlike previously
status mode !0 GetStatus yields PLAY, later STOP
it will never detect that a disk was long ejected!
stop
status mode =0 GetStatus performs IoControl instead
and hence reports current and correct state.
It's fine that the code supports 2 modes of operation, the bug is that the
current code confuses itself as to which branch should be taken and produces
results depending on the history of commands rather than the current state (and
HW capabilities), wrongly mixing both code paths, leading to incorrect results.
IMHO a binary decision via hThread is wrong, there are more states to consider:
- DSB + RAW_READ is useable / being used;
- IOCTL_CDROM_PLAY_AUDIO is useable / being used
- don't know yet.
This issue becomes more important now as MacOS support is getting close (see
bug #20323). This issue becomes more important now as MacOS support is getting
close (see bug #20323). It does not implement the IOCTL_CDROM_*_AUDIO and
spits out unneeded err: and fixme: to the console. I mentioned that I'd about
this issue in bug #20323 comment #4 last year.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=20323
Summary: MacOS mcicda does not play audio CD
Product: Wine
Version: 1.1.30
Platform: PC
OS/Version: Mac OS X 10.5
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hoehle(a)users.sourceforge.net
mcicda invokes GetDriveTypeW which returns 3, the same as for C: and other HD
drives. It expects DRIVE_CDROM(5).
E: is not recognized as CD-ROM by Wine, although it is created by the mountmgr.
It points to /Volumes/Audio-CD. Indeed /Volumes/Audio-CD/ is a directory full
of files named "N Titel NN.aiff", e.g. "2 Titel 02.aiff". e:: points to
/dev/rdisk2
GetDriveTypeW in turn calls:
trace:file:CreateFileW returning 0x68
trace:vxd:DeviceIoControl (0x68,6d4084,0x32f2ac,16,0x32f2ac,16,0x0,0x0)
trace:ntdll:NtDeviceIoControlFile (0x68,0x0,0x0,0x0,0x32f018,0x006d4084,0x3
2f2ac,0x00000010,0x32f2ac,0x00000010)
code=006d4084 (device=6d) is weird, as winioctl.h only lists FILE_DEVICE_* 01
.. 39
I have not looked further into the origin of this code.
Bypassing this test allows mcicda to open cdaudio.
mciSendString: open e: type cdaudio alias y
+ status cdaudio length
+ status cdaudio length 2
+ status cdaudio number of tracks work -- so there's hope -- whereas
- status cdaudio position
- status cdaudio current track
- status cdaudio media present
- seek and
- play fail.
fixme:ntdll:server_ioctl_file Unsupported ioctl 2402c (device=2 access=1 func=b
method=0)
fixme:mcicda:MCICDA_GetError Unknown mode 50
status length etc. show that
DeviceIoControl(wmcda->handle, IOCTL_CDROM_READ_TOC
works.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
http://bugs.winehq.org/show_bug.cgi?id=30581
Bug #: 30581
Summary: Dialog windows can get hidden by the main window in
IDA Free 5.0
Product: Wine
Version: 1.5.3
Platform: x86
URL: http://www.hex-rays.com/products/ida/support/download_
freeware.shtml
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Classification: Unclassified
IDA Pro is an interactive disassembler. A freeware version of IDA 5.0 can be
downloaded from
http://www.hex-rays.com/products/ida/support/download_freeware.shtml
I tested IDA Free with Wine 1.5.3 under Lubuntu 11.10, which uses the Openbox
window manager.
When "Allow the window manager to control the windows" is enabled in winecfg,
dialog boxes can get hidden behind the main window. The dialogs are modal, so
the main window doesn't accept any input while a dialog is open. If you
accidentally click in the main window while a dialog is open, the dialog
disappears but the main window does not accept any input.
To reproduce:
- Use winecfg to disable virtual desktop mode and enable "Allow the window
manager to control the windows" if necessary; those are the default settings.
- Download and run the IDA Free 5.0 installer.
- Run the program. Click OK at the About dialog and Go in the Welcome to IDA!
window.
- The maximised main window opens. Bring up a dialog box, e.g. by selecting
Help-> About program... or File -> Open...
- When the dialog opens, click in the main window. The dialog window disappears
behind the main window. (You can reveal it by un-maximising the main window and
moving it out of the way.)
For what it's worth, this problem doesn't happen with the IDA Pro 6.2 demo, but
that uses different GUI code (QT?).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.