https://bugs.winehq.org/show_bug.cgi?id=49744
Bug ID: 49744
Summary: fbclid should be a numeric value
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: huupoke12(a)gmail.com
Distribution: ---
URLs to AppDB posted on Facebook will generate an fbclid parameter in the URL.
But that parameter is currently a long alphanumeric string, not a numeric only
string, so the bug will happen.
But why does the AppDB processing this parameter? Can it just ignore the
parameter?
--
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=49008
Bug ID: 49008
Summary: Invalid To: tag in registration confirmation email
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lxahotqu2zbx(a)mail.ru
Distribution: ---
Created attachment 66984
--> https://bugs.winehq.org/attachment.cgi?id=66984
The email file
Hello,
The site sends an email to confirm registration. The To: tag must contain the
address of the user to whom the e-mail is addressed following the e-mail
standards. Letters from you are placed in the spam folder because the tag
currently has the value appdb-noreply(a)winehq.org. I ask you fix the problem.
I attached the email file to this report.
Kind Regards,
Ilia
--
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=48468
Bug ID: 48468
Summary: Add "Bronze" and "Garbage" top-10 lists to the appdb
landing page
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jonwsb(a)gmail.com
Distribution: ---
The top-10 lists on appdb.winehq.org are a very nice feature of the site. Their
purpose of showing off what popular programs work in wine is very useful to new
users and I think adding the "Bronze" and "Garbage" ratings to the page will
also provide valuable information to new users as well as contributors. For new
users it will give quick access to information on programs they may be planning
on attempting to use with wine. For advanced users and contributors it will be
a useful tool to gauge which programs need high quality testing and possibly
give inspiration for developing patches to improve bronze and garbage rating
entries.
My biggest concern with adding these top-10 lists would be increasing the size
of the page even more than it already is though it will also probably drive
users of the appdb to vote for more applications overall.
--
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=43702
Bug ID: 43702
Summary: No comments shown if no maintainers for app
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: azrdev(a)qrdn.de
Distribution: ---
If an app has no maintainers, it shows "comments disabled", and one cannot
enter new comments. This is useful, because no one would moderate them.
However, it would still be useful to see the backlog of old comments, which may
contain hints and workarounds posted by users (when there still were
maintainers).
--
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=43849
Bug ID: 43849
Summary: Heroes of the Storm; crashes when Call Mech effect is
on-screen
Product: Wine
Version: 2.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jonathan(a)pearce.name
Distribution: ---
Steps to reproduce:
Start Heroes of the Storm.
Enter Try mode with D.Va.
Take tower damage until your mech is dead.
Shoot enemies until your Call Mech cooldown is activated.
Use Call Mech 'E'.
The mech arrival effect will begin but the game will crash before the mech
becomes visible on-screen. A dialog box pops up with a
e_gfxerrorshadercompilefailed error.
Relevant wine stdout:
fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x80004.
fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x80004.
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:hlsl_parser:hlsl_parse Check for valued return on void function.
fixme:hlsl_parser:hlsl_parse Implicit conversion to the return type if needed,
error out if conversion not possible.
err:d3dcompiler:compile_shader HLSL shader parsing failed.
fixme:dbghelp:elf_search_auxv can't find symbol in module
fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x80004.
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
I experimented with
winetricks d3dx9_43
but that didn't fix the crash (it does change the error signature).
I also tried
d3dcompiler_43 (native)
but it didn't seem to matter.
--
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=43775
Bug ID: 43775
Summary: Heroes of the Storm crash on start with d3d11
Product: Wine
Version: 2.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maxi.cass11(a)gmail.com
Distribution: ---
Created attachment 59282
--> https://bugs.winehq.org/attachment.cgi?id=59282
terminal Output 2.17-staging with dx11
I don't know if the bug is in the non-staging version because Battlenet crash
in non-staging.
My game crash on my laptop with d3d11, I need to set the -dx9 argument to
correct this.
--
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=23015
Summary: PL\SQL Developer: shows standard message boxes behind
main window
Product: Wine
Version: 1.2-rc2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: comdlg32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: chaostya(a)gmail.com
When I write a query in PL\SQL Developer window, then issue it against DB and
then want to close the window I click [x] and it looks like nothing happens,
but if I move main window down I would see a standard "question" message dialog
box asking me if I want to save my changes. I'm on 1.2-rc2 and it's a
regression from 1.2-rc1
--
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=45039
Bug ID: 45039
Summary: Mono: System.UnauthorizedAccessException when trying
to read from stdin when both stdout and stderr are
redirected
Product: Wine
Version: 3.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mk+winehq1803(a)pimpmybyte.de
Distribution: ---
I wrote a simple C# program that reads a line from stdin and prints it in
uppercase (01_shout.cs in [1]).
The exe (compiled on Ubuntu with "mcs") is available for download at
http://l.proggr.de/?1839m7ier
It accepts interactive input when run in cmd.exe on windows 7, even with both
stdout and stderr redirected (02_log_win7.txt in [1]).
In Ubuntu, it crashes when trying to read the line while stdin is a TTY and
both stdout and stderr are redirected (03_log_wine.txt in [1]).
Ubuntu 14.04.5 LTS trusty, wine-3.6,
Mono JIT compiler version 3.2.8 (Debian 3.2.8+dfsg-4ubuntu1.1)
Kernel 3.13.0-142-generic #191-Ubuntu SMP Fri Feb 2 12:14:37 UTC 2018 i686 i686
i686 GNU/Linux
[1] https://gist.github.com/mk-pmb/adae211e875ff11274d9b81248d033a3
--
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=44840
Bug ID: 44840
Summary: Icewind Dale unusably glitchy starting with Wine
Version 3.2
Product: Wine
Version: 3.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wodencafe(a)gmail.com
Distribution: ---
Starting with Wine 3.2 and on, Icewind Dale (2.0.0.11 (GOG)) is having very
strange input / glitchy rendering issues.
I have attached a video comparison with 3.1 where it works fine.
Tested with 3.2, 3.3, and 3.4, and all have the strange input and glitchy
problem.
There are no additional wine modifications.
Please see the video for example of problem, and comparison of when it was
working with 3.1
--
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.