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.
https://bugs.winehq.org/show_bug.cgi?id=46224
Bug ID: 46224
Summary: ddraw-Create-rendering-targets-in-video-memory patch
got borked between 3.19 and 3.20
Product: Wine-staging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Testing application - The Sims Complete Collection
With 3.19, the game launches just fine, and I get
`0009:fixme:ddraw:ddraw_surface_create Application wants to create rendering
target in system memory, using video memory instead` fixmes in the terminal
output, and the game starts.
In 3.20, the game aborts the launch, and I don't get the fixmes.
I suspect this rebase might have broke it:
https://github.com/wine-staging/wine-staging/commit/a423a7087ff2dad6f2def0c…
--
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=41107
Bug ID: 41107
Summary: Total Commander 8.52a Final has VERY slow folder icons
rendering
Product: Wine
Version: 1.9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: katsunori.kumatani(a)gmail.com
Distribution: ---
Created attachment 55313
--> https://bugs.winehq.org/attachment.cgi?id=55313
Terminal Output, not very useful
Using the 32-bit version of Total Commander 8.52a Final (latest non-beta), when
drawing/rendering the icons for folders, it is VERY slow. Download the 32-bit
version here: http://totalcmd2.s3.amazonaws.com/tcmd852ax32.exe
After installing and launching it, please do the following to reproduce:
1) Maximize the Window to have more folders on screen.
2) Near the top-left, to the right of the green "Refresh" button, click on the
"Source: Only file names" button, this enables more folders visible at once to
show the slow effect more.
3) Go/navigate to a folder which has around 200 folders, such as Z:\usr\share
(depends on your Linux distro), it doesn't matter, just make sure it has a lot
of folders to see how painfully slow it is.
This problem of course is not present in Windows.
Terminal output has been attached, however I don't think it has any useful
information because [b]Total Commander version 7 exhibits almost the same
terminal output, but IT IS NOT SLOW like 8.52a![/b] In fact it is almost
instant when rendering folder icons, which look the exact same.
If you turn off folder icons in Preferences, it is fast, so I know that they
are the culprit, 100%.
Btw, the version 9 beta does not seem to have this problem because it uses the
system's folder icons (which are blue on my system) instead of internal. The
internal ones are yellow.
I hope you can track down and fix this bug with this information.
--
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=45278
Bug ID: 45278
Summary: Vietcong: invisible objects (staging 3.9)
Product: Wine-staging
Version: 3.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: havran.jan(a)email.cz
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ArchLinux
Created attachment 61538
--> https://bugs.winehq.org/attachment.cgi?id=61538
Wine staging 3.9 rendering issues in Vietcong
Wine-staging 3.9 has an issue with rendering objects in Vietcong - some parts
of soldier models are invisible (see attachment).
This problem does not exist in Wine-testing and all other Wine-staging versions
(so its only Wine-staging 3.9 issue).
Reproducible in Vietcong full [1] and demo [2] versions. See notes in AppDB how
to run the game.
Tested SW
Kernel 4.16.11
Mesa 18.0.4
Tested HW
Processor: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz
GPU 1: Intel HD Graphics 4600
GPU 2: AMD Radeon R7 M265
PS: Different Vietcong rendering bug occured also in Wine-staging 3.3, but it
has been fixed: bug #44712
PPS: Also note that some missions will crash without stagged
"wined3d-Indexed_Vertex_Blending" patch, see bug #39057 or #9337
[1] https://appdb.winehq.org/objectManager.php?sClass=version&iId=8864
[2] https://appdb.winehq.org/objectManager.php?sClass=version&iId=35621
--
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=46733
Bug ID: 46733
Summary: IDirect3DTexture9_LockRect failed inside
ID3DXFontImpl_DrawTextW with OblivionReloaded
Product: Wine-staging
Version: 4.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lorenzofer(a)live.it
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 63724
--> https://bugs.winehq.org/attachment.cgi?id=63724
+d3dx,+d3d9,+d3d log
Hi,
While testing OblivionReloaded (a patcher/extender for TES4:Oblivion), I
discovered that in some place where there was supposed to be a rendered text,
wasn't. One of these place is the options menu (by default it came up with the
key O).
Digging inside OR sourcecode, I saw that it use DrawTextA from ID3DXFont.
However the functions was silently failing and there wasn't any message from
the log.
I put some TRACE messages inside the functions and discovered that was failing
in IDirect3DTexture9_LockRect.
After getting a +d3dx,+d3d9,+d3d log I got:
0046:warn:d3d:wined3d_resource_map Resource does not have MAP_W access.
on a Texture created by the DrawTextW function.
Now, I don't have aviable other games that use the DrawText functions,and were
reported working. But considering where is failing, it's possible that a change
(in wine or another staging patch) broke this patch en passant?
The attachment uploader is crying when trying to upload the compressed log.
Will retry tomorrow.
--
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=39424
Bug ID: 39424
Summary: CodeCharge Studio 5.2 Does Not Load
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: api-ms-win-*
Assignee: wine-bugs(a)winehq.org
Reporter: tmp(a)pc-homepage.com
Distribution: ---
Created attachment 52538
--> https://bugs.winehq.org/attachment.cgi?id=52538
Error dump file
Installation of CodeCharge Studio 5.2 gave errors but it seemed to install.
However, it will not run.
--
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.