https://bugs.winehq.org/show_bug.cgi?id=49695
Bug ID: 49695
Summary: Euro Truck Simulator 2 / American Truck Simulator
Multiplayer: Crash when trying to change "Player tag"
color
Product: Wine
Version: 5.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kakurasan(a)gmail.com
CC: aeikum(a)codeweavers.com
Distribution: Ubuntu
Created attachment 67937
--> https://bugs.winehq.org/attachment.cgi?id=67937
Game crash log (ETS2MP)
When clicking the colored square in "Settings - General - Player tag", the game
crashes instead of showing a color picker and it outputs "My
Documents/ETS2MP/last_crash.log" (ETS2MP) or "My
Documents/ATSMP/last_crash.log" (ATSMP).
Steps to reproduce (Note: No need to create/use TruckersMP account to reproduce
this):
1. Create a Steam account if you don't have one already
2. Buy Euro Truck Simulator 2 or American Truck Simulator on Steam if you have
neither of these
3. Install *Windows version* of Steam client with Wine
4. Start the Steam client with Wine ("-no-cef-sandbox" option is recommended,
logging in is required)
5. Install Euro Truck Simulator 2 or American Truck Simulator
6. When downgrading is needed for multiplayer, set the "BETAS" ("Properties"
dialog) to the supported branch (e.g. "temporary_1_37" when version 1.37.x is
required, see https://stats.truckersmp.com/ and
https://truckersmp.com/knowledge-base/article/26)
7. Install the unofficial launcher called "truckersmp-cli"
(https://github.com/lhark/truckersmp-cli)
8. Start game via truckersmp-cli (e.g. truckersmp-cli --ets2 --wine --start
--prefixdir /path/to/wineprefix) when the Steam client is running
9. Click the "gear" icon (at top-left) in the login screen
10. Click the colored square in "Settings - General - Player tag"
truckersmp-cli allows users to install/use Proton instead of Wine (Linux
version of Steam is required) but Proton (as of 5.0) has the same issue.
--
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=47805
Bug ID: 47805
Summary: SkyUI mod for Skyrim Special Edition with SKSE64 fails
to show HUD active effect icons (other functions of
mod work)
Product: Wine
Version: 4.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: cyan255(a)gmail.com
Distribution: ---
1. Set up a 64-bit prefix.
2. Install Skyrim Special Edition via Steam.
3. Install SKSE64.
4. Install SkyUI from NexusMods
https://www.nexusmods.com/skyrimspecialedition/mods/12604
5. Launch skseloader.exe(via Mod Manager, such as MO, or directly, doesn't
matter)
6. create a character and check that SKSE has loaded correctly (skse version
shown in MENU>System on bottom left.
7.Make sure that Active Effects HUD is enabled in MENU> Mod Configuration>
SkyUI> General.
8. during play consume an item that causes a active effect (like salt pile or
something poisonous)
9. Notice that active effect shows the timer bar in the HUD (top right by
default) but its icon does not show.
This setup works in Windows but not with Wine 4.16
Skyrim SE 1.5.80.08
SkyUI_5_2_SE-12604-5-2SE
Skyrim Script Extender 64 v2.0.16 beta
https://i.imgur.com/P6NOJBc.png (effect status time in top right)
--
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=30853
Bug #: 30853
Summary: Wine doesn’t always handle "right alt" properly
Product: Wine
Version: 1.5.5
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sloonz(a)gmail.com
Classification: Unclassified
Created attachment 40410
--> http://bugs.winehq.org/attachment.cgi?id=40410
workaround/quick and dirty fix
I’m trying to get World of Warcraft working under Wine. However, I have huge
trouble with key bindings (I use unusual key bindings : I use the right half of
my keyboard, whereas most players use the left half).
After investigation, I found 3 bugs (different behaviors between Wine and my
Windows installation). The first one is the management of the right "Alt" key
(labeled "Alt-Gr" on my keyboard). When I press AltGr+l under Windows with
Spy++, I get the followings events :
<03637> 0007045A P WM_KEYDOWN nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D
fExtended:0 fAltDown:0 fRepeat:0 fUp:0
<03638> 0007045A P WM_KEYDOWN nVirtKey:VK_MENU cRepeat:1 ScanCode:38
fExtended:1 fAltDown:1 fRepeat:0 fUp:0
<03639> 0007045A P WM_KEYDOWN nVirtKey:'L' cRepeat:1 ScanCode:18
fExtended:0 fAltDown:1 fRepeat:0 fUp:0
<03640> 0007045A P WM_DEADCHAR chCharCode:'002F' (47) cRepeat:1 ScanCode:18
fExtended:0 fAltDown:1 fRepeat:0 fUp:0
<03641> 0007045A P WM_KEYUP nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0
fAltDown:1 fRepeat:1 fUp:1
<03642> 0007045A P WM_SYSKEYUP nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D
fExtended:0 fAltDown:1 fRepeat:1 fUp:1
<03643> 0007045A P WM_KEYUP nVirtKey:VK_MENU cRepeat:1 ScanCode:38
fExtended:1 fAltDown:0 fRepeat:1 fUp:1
Under Wine 1.5.5 however (WINEDEBUG=+msg), I get those :
trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x6007e wp eb
lp 760001 [note: wp = VK_OEM_PA2]
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp 4c lp
c0260001 [note: wp = 'L']
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp eb lp
c0760001 [note: wp = VK_OEM_PA2]
With xev, I get :
KeyPress event, serial 93, synthetic NO, window 0x4000001,
root 0xbc, subw 0x0, time 5086996, (1585,410), root:(2578,425),
state 0x0, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen
YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 93, synthetic NO, window 0x4000001,
root 0xbc, subw 0x0, time 5087052, (1585,410), root:(2578,425),
state 0x80, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen
YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes:
XFilterEvent returns: False
After "setxkbmap us", AltGr is bound to Alt_R under X (checked with xev), and I
get this under Wine :
trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp
a5 lp 21380001 [wp = VK_RMENU]
trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp
4c lp 20260001 [wp = 'L']
trace:msg:peek_message got type 6 msg 106 (WM_SYSCHAR) hwnd 0x10046 wp 6c
lp 20260001 [wp = 'l']
trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10046 wp 4c
lp e0260001 [wp = 'L']
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10046 wp a5 lp
c1380001 [wp = VK_RMENU]
(yes, I have a KEYUP without KEYDOWN)
Wich is still not the same as Windows. So I think there is two problems here :
- ISO_Level3_Shift is not properly recognized by Wine
- "AltGr" doesn't have the same behavior under Wine and Windows
FYI, attached patch is a workaround to have the same behavior than Windows.
With it, I get this under Wine :
trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a2
lp 1d0001 [note: wp = VK_LCONTROL]
trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a4
lp 20380001 [note: wp = VK_LMENU]
trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp 4c
lp 20260001 [note: wp = 'L']
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp 4c lp
e0260001
trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10062 wp a2
lp e01d0001
trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp a4 lp
c0380001
Which is still not the same as Windows :
- Windows uses (right) control + menu (with fExtended flag for menu) whereas
Wine uses left control + left menu. Not investigated if this is related to
TranslateMessage.
- AltGr+L is a dead symbol on my keymap. Windows send a DEADCHAR message,
wheras Wine send nothing. Note that I had to disable the XFilterEvent test in
event.c to have those messages, otherwise nothing is sent to the program (but
that’s another story for another bug report)
But it suffice for my use case (WoW key bindings with right alt)
--
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=47604
Bug ID: 47604
Summary: Cannot use the app
Product: Packaging
Version: unspecified
Hardware: aarch64
OS: Android
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: fzh2003(a)yeah.net
CC: dimesio(a)earthlink.net, michael(a)fds-team.de,
sebastian(a)fds-team.de
Created attachment 65029
--> https://bugs.winehq.org/attachment.cgi?id=65029
screenshot
Android 9 kernel 4.9.154 model Huawei SEA-AL00
--
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=41000
Bug ID: 41000
Summary: wineconsole curses backend 64bit: Some uppercase chars
broken on Crysis Wars Dedicated Server
Product: Wine
Version: 1.9.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: main.haarp(a)gmail.com
Distribution: ---
I am running the Crysis Wars Dedicated Server in wineconsole. The server offers
both 32bit and 64bit binaries.
Using wineconsole's user backend, both 32 and 64bit work fine.
Using the curses backend, 32bit works fine. 64bit however experiences a bug.
Some uppercase characters cannot be typed or pasted at all. There is no
reaction. wineconsole will display them just fine, but simply will not let them
be typed.
The affected chars are uppercase versions of these: 2 4 6 0 - f h j k ; [] q r
t y o p x c v m , . / (assuming US keyboard layout)
--
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=30193
Bug #: 30193
Summary: Crysis Wars ded server doesn't resize with wineconsole
(curses backend)
Product: Wine
Version: 1.4-rc6
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: liquitsnake(a)gmx.net
Classification: Unclassified
Created attachment 39410
--> http://bugs.winehq.org/attachment.cgi?id=39410
screen
The Crysis Wars dedicated server, when running under wineconsole with the
curses backend, does not resize its viewport. It is stuck at the default 80x25,
even if the terminal is considerably larger (see attachment).
This produces some unexpected output, as some commands expect a larger size but
have to be split over 2 lines via \
My terminal and wineconsole interact just fine, as I have verified with cmd.
It's just this app that sticks to 80x25 no matter what.
On Windows, it would normally spawn a console window with a size of 132x60 (or
less if the desktop resolution can't fit that)
Could it be that wineconsole first starts at 80x25 and only later resizes to
terminal size? In that case, I can imagine that the app polls the size once
during startup and sticks to that, thus limiting itself to 80x25.
--
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=49723
Bug ID: 49723
Summary: After update to wine-5.15 "1c" start crashed with
error Unhandled exception
Product: Wine
Version: 5.15
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: virex(a)mail.ru
Distribution: ---
After update to wine-5.15 "1c" start crashed with error Unhandled exception
It is also was with the build 5.12
(https://bugs.winehq.org/show_bug.cgi?id=49561) but after update to 5.15
version this error persist again
--
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=37928
Bug ID: 37928
Summary: Photoshop CS6: Mini-bridge panel does not show
directory entries in alphabetical order
Product: Wine
Version: 1.7.34
Hardware: arm
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: robert.munteanu(a)gmail.com
Distribution: ---
Steps to reproduce:
1. Launch Photoshop
2. Click File -> Open in mini bridge
3. Navigate to a folder with multiple subfolders
The subfolders are not ordered alphabetically, but in an apparently random
manner. They are definitely not ordered by creation date ( I created the
situation in my screenshot using a simple "mkdir a b c d e f g h i j k l" .
--
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=9127
--- Comment #98 from Bryan Kirk <Zero3K(a)teknik.io> ---
1. PL_MPEG is smaller in size than GStreamer and wouldn't require its
installation and the installation of a GStreamer plugin.
2. PL_MPEG's player program works for me under Ubuntu 16.04 (except for the
colors being messed up and the audio being played slowly). Maybe I did
something wrong and someone else will have better results (that or its because
I am using VirtualBox to virtualize Ubuntu).
--
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.