https://bugs.winehq.org/show_bug.cgi?id=46766
Bug ID: 46766
Summary: Royal Quest minimap layer missing
Product: Wine-staging
Version: 4.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: spoon0042(a)hotmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 63775
--> https://bugs.winehq.org/attachment.cgi?id=63775
4.3 staging screenshot
With 4.3 staging the map outline in the minimap has disappeared in Royal Quest.
I haven't noticed any other graphical glitches. Works as usual in 4.2 staging
and 4.3 base.
--
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=46587
Bug ID: 46587
Summary: Paint.net v4 crashes with GTK3 Theming
Product: Wine-staging
Version: 4.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: toe_head2001(a)yahoo.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 63480
--> https://bugs.winehq.org/attachment.cgi?id=63480
Screenshot showing the EntryPointNotFoundException
It is "Unable to find an entry point named 'BufferedPaintStopAllAnimations' in
DLL 'uxtheme.dll'."
I assume this due to the DLL redirect to uxtheme-gtk.dll from uxtheme.dll.
This crash does not occur when GTK3 Theming is disabled.
--
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=46850
Bug ID: 46850
Summary: joystick buttons not mapped correctly
Product: Wine-staging
Version: 4.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mickski56(a)hotmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
0001-dinput-Allow-remapping-of-joystick-buttons.patch
defines MAX_MAP_BUTTONS 16
Sony dualshock3 has 17 buttons leading to dpad right and X button both
producing button 1 when pressed.
Increasing MAX_MAP_BUTTONS to 17 resolves this although an arbitrarily larger
number like 24 or 32 might be better.
plus the rest of the patch will want adjusting to accommodate however many
buttons are defined as mappable.
--
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=40060
Bug ID: 40060
Summary: Crash dialog button unclickable
Product: Wine-staging
Version: 1.9.2
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: isakov-sl(a)bk.ru
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Created attachment 53538
--> https://bugs.winehq.org/attachment.cgi?id=53538
The windows in question
If a game crashes (for example elevated_1024x768.exe) then dialog windows
appeared with two buttons "Show details" and "Close".
These buttons are unclickable because of patch
https://github.com/wine-compholio/wine-staging/blob/master/patches/user32-M…
Reverting the patch resolves the 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=45856
Bug ID: 45856
Summary: wine stuck installing python in silent mode
Product: Wine-staging
Version: 3.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sbonazzo(a)redhat.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: Fedora
On Fedora 28:
download https://www.python.org/ftp/python/2.7.14/python-2.7.14.msi
$ wine msiexec /i /tmp/python-2.7.14.msi /qn ADDLOCAL=ALL
000b:fixme:winediag:start_process Wine Staging 3.16 is a testing version
containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing
bug reports on winehq.org.
0028:fixme:dwmapi:DwmIsCompositionEnabled 0x6dc825d4
002d:fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69ec7e28,
context 0x91e480, init_notify 0, handle 0x11dfa10): stub
003f:fixme:dwmapi:DwmIsCompositionEnabled 0x6dc825d4
0041:fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69ec7e28,
context 0x91e480, init_notify 0, handle 0x11dfa10): stub
wine: configuration in '/home/sbonazzo/.wine' has been updated.
0009:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
0053:err:msiexec:custom_action_server Failed to create custom action server
pipe: 2
wine get stuck here and doesn't complete the silent install.
Reproducible 100% with wine 3.14-1.fc28 and 3.16-1.fc28
Worked fine in wine 3.8-1.fc28
(https://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc28…)
--
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=46704
Bug ID: 46704
Summary: League Of Legends 9.4, Connection issue - We're unable
to log you in because you may be offline.
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: werifGX(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 63664
--> https://bugs.winehq.org/attachment.cgi?id=63664
Screenshot of the issue.
League Of Legends (9.4-15540347.15540320) is unable to log-in on wine-4.2
(Staging) with vcrun2017, adobeair and corefonts due "We're unable to log you
in because you may be offline" error
Same problem on Lutris's League Of Legends
(https://lutris.net/games/install/3552/view)
Both of which worked without any noticable issues yesterday (22.02.2019).
Results in : https://i.imgur.com/wIJ4Zit.png
--
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=45578
Bug ID: 45578
Summary: GTA 5 doesn't launch in 3.13, works in 3.12
Product: Wine-staging
Version: 3.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: electrodexsnet(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 61994
--> https://bugs.winehq.org/attachment.cgi?id=61994
crash log - crash at line 19,541
I have GTA5 installed in a wine prefix with dxvk. Using wine builtin vulkan
(vulkan-1.dll).
In wine-staging 3.12, GTA 5 runs without issue.
In 3.13, it now hangs at a blank screen after the police siren intro. You can
close it by pressing Alt F4, then Enter. After reverting to 3.12, it works as
expected again.
Versions/System:
GPU: Nvidia GTX 970 | proprietary driver: 396.45
OS: Manjaro stable
DXVK: tested 0.54, 0.63, 0.64 - no difference
winetricks: allfonts, steam
Noteable error messages (line 19,541 in gta5_wine-staging-3.13-crash01):
wine: Unhandled page fault on write access to 0x00000000 at address 0x141275cbc
(thread 013c), starting debugger...
Unhandled exception: page fault on write access to 0x00000000 in 64-bit code
(0x0000000141275cbc).
--
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=46148
Bug ID: 46148
Summary: In World of Warcraft 8 background and water are solid
color and flashes of various color appear many times
per second
Product: Wine-staging
Version: 3.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kgrittn(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
World of Warcraft 8.0.1 (28153)(Release x64)
OS is Ubuntu, both show the same symptoms and were fine before Wine 3.20
(Staging):
Linux kevin-desktop 4.15.0-39-generic #42~16.04.1-Ubuntu SMP Wed Oct 24
17:09:54 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
16GB
Intel HD Graphics 4000 (Ivybridge) (on motherboard, no expansion slot)
Linux kgrittn-Precision-7720 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2
17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz
32GB RAM
NVIDIA GeForce GTX 470
Symptoms in WoW:
- Backgrounds such as terrain show as a single color (always black?) with no
"litter" or detail -- a roadway looks the same as wild ground which is the same
as the side of a cliff.
- Water shows as a single block of color with no shorline features, reflection,
or transparency to underlying features.
- Random patches of color appear, apparently changing with each screen draw.
- Small animated areas like torch flames show lots of rectangle enclosing the
area with little or none of the normal animation.
--
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=44032
Bug ID: 44032
Summary: Diablo 3 2.6.1: Mouse-downs register as mouse clicks
Product: Wine
Version: 2.20
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sts33nvyb(a)gmail.com
Distribution: ---
Created attachment 59696
--> https://bugs.winehq.org/attachment.cgi?id=59696
Terminal output (not that I expect this to be useful)
In Diablo 3, mouse-downs (pressing and holding the mouse button) often register
as mouse clicks (pressing and immediately releasing the mouse button). This
happens for approximately 50% of the mouse-downs when playing the game, which
dramatically changes how the game plays, since holding down the mouse button is
used for both moving and attacking continuously in the game.
I'm running wine-staging 2.20 on OpenSuse 42.3 x86_64.
This is for the current version of Diablo 3, version 2.6.1.47919 32-bit. Note
that Diablo 3 recently dropped support for Windows XP; since this change,
Diablo 3 no longer works in non-staging wine at all. Also, the 64-bit version
of Diablo 3 has severe performance problems in wine-staging 2.20, so this is
using the 32-bit version of Diablo 3.
I speculate that some bug in wine is causing bogus mouse-up events to sometimes
be generated immediately after mouse-down events.
Note that this is a completely different bug from bug 31262. Note that user
"pakos" has mistakenly commented about this bug in that bug report, dated
2017-11-13. He reports that this problem is present in versions of
wine-staging at least back to 2.5.
There has been some discussion of this bug on the application page. Some users
have reported that changing wine's virtual desktop setting, forcing 32-bit
using setarch, or changing Diablo 3's settings to windowed-fullscreen instead
of fullscreen alleviated the problem. None of these helped for me.
--
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=45826
Bug ID: 45826
Summary: Doom 2016 - Rendering issues
Product: Wine-staging
Version: 3.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ahmed.com(a)aol.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 62283
--> https://bugs.winehq.org/attachment.cgi?id=62283
wine error log
I can't run Doom 2016 with Mesa 18.1.7 or Mesa 18.1.8, so I tried Mesa 18.2.0-1
and the game started but it look so weird, and I can hear the menu sounds but I
can't see the menu.
System information:
Operating system: Manjaro KDE
GPU: AMD HD 8750M
Driver: Mesa 18.2.0-1
Wine version: 3.15 staging-nine
--
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.