https://bugs.winehq.org/show_bug.cgi?id=39246
Bug ID: 39246
Summary: user32:edit fails in Japanese and Korean locales
Product: Wine
Version: unspecified
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The following error only happens on the WineTest's Japanese and Korean boxes:
edit.c:1521: Test failed: got 1, 1
More specifically one can see this error on the following boxes:
fg-win7u64-1spie9-ja - Japanese locale
fg-win7u64-1spie9-ko - Korean locale
fg-win7u64-1spie9-mx - Japanese locale as far as this test is concerned
newtb-w7u - Japanese locale
This test regression was introduced by the following commit:
commit ba3a6d1f4b9db64c12301d0d83d559dd6f1e83b4
Author: Nikolay Sivov <nsivov(a)codeweavers.com>
Date: Fri Apr 4 21:45:28 2014 +0400
user32: Fix Edit margins calculation for empty client area case.
See:
https://test.winehq.org/data/tests/user32:edit.html
--
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=41251
Bug ID: 41251
Summary: SWTOR client does not start up (import_dll Library not
found)
Product: Wine
Version: 1.9.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pyramid(a)sapo.pt
Distribution: ---
SWTOR launcher.exe starts, then executes the loading of the client with console
output:
Waiting for swtor...
Found, PID: 138
Waiting for threads to end..
After that, the wine processes (wineserver, winedevices.exe) just terminate.
Enabling wine logs reveals:
err:module:import_dll Library MSVCP90.dll (which is needed by
L"C:\\...\\swtor.exe") not found
All required libraries (dll) are installed on the wine 32bit prefix correctly.
Downgrading from wine 1.9.17 to 1.9.15 (don't have 1.9.16 handy for testing)
allows for game client start without errors.
Additional info:
# uname -a
Linux ... 4.7.2-1-default #1 SMP PREEMPT Sun Aug 21 08:59:11 UTC 2016 (34ba8d6)
x86_64 x86_64 x86_64 GN
# wine --version
wine-1.9.17
# set | grep WINE
WINEARCH=win32
WINEPREFIX=/data/machines/wine32/
--
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=24644
Summary: AstroburnLite fails to install
Product: Wine
Version: 1.3.4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lukasz.wojnilowicz(a)gmail.com
Created an attachment (id=31146)
--> (http://bugs.winehq.org/attachment.cgi?id=31146)
Error message
Steps to reproduce:
1) remove ~/.wine
2) wine AstroburnLite130-0100.exe
Behaviour:
error (see attachment)
Expected behaviour:
Application should start installing
--
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=32106
Bug #: 32106
Summary: Caps Lock doesn't work correctly with WinUAE with
DirectInput
Product: Wine
Version: 1.5.16
Platform: x86-64
URL: http://www.winuae.net/files/InstallWinUAE2410.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Classification: Unclassified
Created attachment 42334
--> http://bugs.winehq.org/attachment.cgi?id=42334
Dummy/empty bootable Amiga floppy disk image
This issue shows up with the WinUAE Amiga emulator.
For keyboard and mouse input, WinUAE uses raw input if available, falling back
to DirectInput otherwise. This bug only shows up when WinUAE is using
DirectInput. Raw input was first working in Wine 1.5.16, so if using 1.5.16 or
later, run WinUAE with the -norawinput argument.
Pressing Caps Lock does not affect typed letters properly. For example,
repeatedly mashing the d-f-g letters on the keyboard, and occasionally pressing
Caps Lock might result in something like this (where [CL] denotes Caps Lock
being pressed and released):
gfd [CL] gfd [CL] gFDgFDgFD [CL] GFDGFDGFD [CL] GdGfDGfd [CL] gfdgdgfd [CL]
gFDgdFgdF [CL] GDFGFDGFD [CL] GfdGfDGDf
That should actually look like:
gfd [CL] GFD [CL] gfdgfdgfd [CL] GFDGFDGFD [CL] gdgfdgfd [CL] GFDGDGFD [CL]
gfdgdfgdf [CL] GDFGFDGFD [CL] gfdgfdgdf
I tested using Wine 1.5.16 built from source on Lubuntu 11.10 x86-64.
To reproduce:
- Download and run the WinUAE installer.
- You need to obtain an Amiga ROM image. Try googling for "kick12.rom" OR
"kick13.rom" and you should find the required file easily. Download the file
and copy to a directory accessible by Wine.
- Run wine winuae.exe -norawinput
- When the WinUAE Properties window appears, click ROM under Hardware in the
tree-view at the left side. Click the "..." button to the right of "Main ROM
file" and select the ROM image file.
- Click Floppy drives under Hardware in the tree-view. Click the "..." button
at the upper right of the window to select a floppy disk image. Select the
test.adf file attached to this bug report. (That's a dummy/empty bootable disk;
its only purpose is to leave you in a CLI window where you can type text.)
- Click Start at the bottom of the window. The emulation will start. After a
few seconds you should be presented with a CLI window.
- While mashing various letter keys on the keyboard, press and release Caps
Lock from time to time. Notice the issue described above.
- You can quit WinUAE and run it again without the -norawinput argument.
Repeating the same steps as above, pressing the keys should give the
correct/expected result.
--
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=30406
Bug #: 30406
Summary: WinUAE crashes when the emulation window is resized
Product: Wine
Version: 1.5.1
Platform: x86-64
URL: http://www.winuae.net/files/InstallWinUAE2400.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Classification: Unclassified
Created attachment 39747
--> http://bugs.winehq.org/attachment.cgi?id=39747
Backtrace output for crash when resizing window
I'm testing with Wine 1.5.1, Lubuntu 11.10 64-bit, Nvidia driver 295.20.
This bug applies to version 2.4.0 of the WinUAE Amiga emulator. WinUAE can use
either DirectDraw or Direct3D for its graphics output. The default is
DirectDraw (at least when installed under Wine in XP mode). I get a crash on
resizing the emulation window. In my testing, it seems to happen more often
when graphics API is set to Direct3D.
To reproduce the problem:
- Download and run the WinUAE installer. Run WinUAE.
- Click Start. The emulation window opens and after a few seconds the insert
media screen appears. There's a red mouse pointer which you can move.
- Click the middle mouse button to un-capture the mouse, then resize the
emulation window several times. You may get a crash at this point.
- Press F12 to bring up the settings window. Click Miscellanous in the treeview
and change Graphics API to Direct3D.
- To work around Wine bug 10643, click in the emulation window then press and
release F12.
- Click OK to continue the emulation.
- Repeatedly resize the window. You should get a crash sooner or later.
When it crashes, a dialog box appears with caption Crash, and text like this:
Crash detected. MiniDump saved as:
C:\Program Files\WinUAE\winuae_240_yyyymmdd_hhmmss.dmp
On clicking OK a Wine Program Error window appears. Backtrace output from that
is attached.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=41056
Bug ID: 41056
Summary: 1 888 811 4532 Cisco Headquarters Address
Product: Wine
Version: 1.9.15
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: advpack
Assignee: wine-bugs(a)winehq.org
Reporter: jacksftt(a)gmail.com
Distribution: ---
cisco contact number
cisco customer service
cisco support number
cisco tech support number
cisco tech support
cisco phone number
cisco customer service number
cisco phone support
cisco customer support
contact cisco
cisco number
cisco support phone number
cisco systems phone number
cisco router customer service
cisco router tech support
cisco router tech support phone number
contact number
cisco conference call
cisco router customer support phone number
cisco hr phone number
cisco service contract
cisco services
cisco unified contact center express
--
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=41312
Bug ID: 41312
Summary: Regedit on a 64 bit machine only displays the
Wow6432Node structure
Product: Wine
Version: 1.9.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: registry
Assignee: wine-bugs(a)winehq.org
Reporter: reinhold.hoffmann(a)hotmail.com
Distribution: ---
Regedit on a Wine 64 bit machine behaves differently compared to Windows 64
bit. Comparing the Regedit view on Wine of a 32 bit vs. Wine on a 64 bit
machine is different and confusing.
On a 64 bit machine Regedit only displays the Wow6432Node content in the
regular HKEY_LOCAL_MACHINE structure. This is confusing because Windows 64 bit
displays the regular setup (that is related to 64 bit installation) and
Wow6432Node separately. To view the non-32 bit structure in Wine related to
KEY_WOW64_64KEY the system.reg needs to be manually accessed by an editor. The
recommendation for Regedit is to display the same structure as on Windows 64.
--
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.