https://bugs.winehq.org/show_bug.cgi?id=6893
joaopa <jeremielapuree(a)yahoo.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeremielapuree(a)yahoo.fr
--- Comment #21 from joaopa <jeremielapuree(a)yahoo.fr> ---
Bug still occurs with wine-5.7.
--
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=39847
Bug ID: 39847
Summary: Installation ABBYY Aligner2
Product: Wine
Version: 1.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: msrom(a)mail.ru
Distribution: ---
Created attachment 53196
--> https://bugs.winehq.org/attachment.cgi?id=53196
log
Cannot install application ABBYY Aligner2
--
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=44077
Bug ID: 44077
Summary: Overwatch: Within the first minute of game play the
entire OS stops rendering (requires hard reboot)
Product: Wine-staging
Version: 2.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sander.smid(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
wine-2.21 (Staging)
Linux oribi 4.13.12-1-ARCH #1 SMP PREEMPT Wed Nov 8 11:54:06 CET 2017 x86_64
GNU/Linux
Graphics: Card: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
470/480/570/580]
Display Server: x11 (X.Org 1.19.5 ) drivers: nvidia (unloaded:
modesetting,fbdev,nv,vesa,nouveau)
Resolution: 1920x1200(a)59.95hz
OpenGL: renderer: AMD Radeon RX 480 Graphics (AMD POLARIS10 / DRM
3.18.0 / 4.13.12-1-ARCH, LLVM 5.0.0)
version: 4.5 Mesa 17.2.5
env WINEPREFIX="/games/BattleNet" /usr/bin/wine
/games/BattleNet/drive_c/Program\ Files\ \(x86\)/Overwatch/Overwatch.exe
--
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=45899
Bug ID: 45899
Summary: Tray icons don't react when you left click or right
click on them
Product: Wine-staging
Version: 3.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: guih.rox(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
All programs with a tray icon that I've tested so far with Wine Staging 3.16
don't work when you try to interact with it, by trying to left or right
clicking on it.
This is not reproducible with Vanilla Wine however.
There's a small program called TurnFlash
(https://www.nirsoft.net/utils/tflash2.html) that can be used to observe this
behavior:
Download link: https://www.nirsoft.net/utils/tflash210.zip
SHA-1 sum for tflash.exe: 15f877867b45d51a2a8257494bb3128f1b0d087f
After you run it, you should get no output from wine, but you'll see a blue
icon added to the system tray of your Desktop Environment (in my case, it's KDE
Plasma 5.13.5).
The first thing I tried was checking checked my journal using `journalctl -f`,
this is the message I got:
Sep 27 03:22:06 arch plasmashell[970]: QQuickItem::stackAfter: Cannot stack
StatusNotifierItem_QMLTYPE_345(0x558c6fb48b50, parent=0x558c6caa47b0,
geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_345(0x558c6f972d20), which
must be a sibling
After that, I tried left clicking the tray icon -- it did nothing at all, and
no logs. But right clicking it made the following message show up in the
journal:
Sep 27 03:24:36 arch plasmashell[970]: Could not find DBusMenu interface,
falling back to calling ContextMenu()
I should mention that I get the exact same messages using Vanilla Wine, the
only difference is that interacting with the tray icon works perfectly fine.
--
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=45291
Bug ID: 45291
Summary: Dauntless Open Beta : Cant play Intro Video resulting
in not responding black screen
Product: Wine
Version: 3.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winegstreamer
Assignee: wine-bugs(a)winehq.org
Reporter: asembus(a)gmail.com
Distribution: ---
Tried to test the open beta version for dauntless with addtional dotnet
installation. the launcher works fine but when the game start it doesnt show
intro video and ends up with black screen.
i've read the log and it seems the error is caused when the video cannot be
shown
[2018-06-02T11:11:33,434][ 0][LogMediaUtils][Error]Cannot play
file://../../../Archon/Content/MoviesPackaged/MediaExample.mp4, because none of
the enabled media player plug-ins support it:
--
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=48132
Bug ID: 48132
Summary: Elite Dangerous launcher broken (regression since
wine-staging-4.20)
Product: Wine-staging
Version: 4.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kolAflash(a)kolahilft.de
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 65724
--> https://bugs.winehq.org/attachment.cgi?id=65724
screenshots
The Elite Dangerous launcher is broken, when using wine-staging-4.20. It's
using 100 % of one CPU core, freezes after the first click and is graphically
broken (see attached screenshots).
It's a regression. Everything is fine when using either wine-4.20 or
wine-staging-4.19.
Something suspicious on the shell: 0065:fixme:d3d9:shader_validator_stub2
./wine-staging-4.20/patches/patchinstall.sh DESTDIR=wine-4.20 --all -W
uxtheme-CloseThemeClass -W uxtheme-GTK_Theming
Tested workarounds: Use d9vk or gallium-nine.
https://github.com/Joshua-Ashton/d9vk/releases (needs a Vulkan capable GPU)
https://github.com/iXit/wine-nine-standalone (needs a Radeon-GPU or a very,
very recent Intel-GPU)
winetricks galliumnine
--
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=44089
Bug ID: 44089
Summary: Strider crashes after loading screen
Product: Wine
Version: 2.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx11
Assignee: wine-bugs(a)winehq.org
Reporter: strider(a)strycore.com
Distribution: ---
Created attachment 59805
--> https://bugs.winehq.org/attachment.cgi?id=59805
backtrace of the crash
While the main menu works fine, when starting a game, the game crashes. This is
a regression that started in Wine Staging 2.16, when the deferred context patch
(https://dev.wine-staging.com/patches/181/) was introduced. I had a build of
Wine Staging 2.15 with that patch enabled and I noticed crashes starting with
that build and onward until the latest tested, Staging 2.21.
--
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=48946
Bug ID: 48946
Summary: Uplay crash when launching Watchdogs with esync patch
applied
Product: Wine-staging
Version: 5.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: guillaume.zin(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 66920
--> https://bugs.winehq.org/attachment.cgi?id=66920
Patch to esync, adds sanity checks in queue_rawinput_message
Hello,
I first decribed the problem here: https://github.com/lutris/wine/issues/25
With wine version 5.5 and 5.6 patched with esync, wineserver crashes most of
the time (sometimes it doesn't) when Uplay is about to launch Watchdogs (when
the dialog box appears to explain that disabling uplay overlay is not such a
good idea, or when telling it is starting the game). It doesn't happen with
vanilla wine.
Wine 5.6 + esync patch + -ggdb option during compilation:
Program received signal SIGSEGV, Segmentation fault.
0x000055baca61f208 in queue_rawinput_message (process=0x55bacb873200,
user=0x7fff020150c0) at ../../wine/server/queue.c:1808
1808 ../../wine/server/queue.c: Aucun fichier ou dossier de ce type.
(gdb) backtrace
#0 0x000055baca61f208 in queue_rawinput_message (process=0x55bacb873200,
user=0x7fff020150c0) at ../../wine/server/queue.c:1808
#1 0x000055baca619558 in enum_processes (cb=cb@entry=0x55baca61f140
<queue_rawinput_message>, user=user@entry=0x7fff020150c0) at
../../wine/server/process.c:1080
#2 0x000055baca620f21 in queue_mouse_message (req_flags=<optimized out>,
sender=0x55bacbae5930, origin=1, input=0x55bacb588eb0, win=0,
desktop=0x55bacb588110) at ../../wine/server/queue.c:1901
#3 req_send_hardware_message (req=0x55bacb588ea0, reply=0x7fff02015160) at
../../wine/server/queue.c:2608
#4 0x000055baca62a8d3 in call_req_handler (thread=thread@entry=0x55bacb588d50)
at ../../wine/server/request.c:311
#5 0x000055baca62b902 in read_request (thread=thread@entry=0x55bacb588d50) at
../../wine/server/request.c:345
#6 0x000055baca6314b0 in thread_poll_event (fd=<optimized out>, event=1) at
../../wine/server/thread.c:319
#7 0x000055baca60a106 in fd_poll_event (event=<optimized out>, fd=<optimized
out>) at ../../wine/server/fd.c:486
#8 main_loop_epoll () at ../../wine/server/fd.c:581
#9 0x000055baca60a37e in main_loop () at ../../wine/server/fd.c:947
#10 0x000055baca5f9989 in main (argc=1, argv=0x7fff02015948) at
../../wine/server/main.c:154
The attached patch, applied after esync patch, fixes the problem.
Guillaume
--
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=48612
Bug ID: 48612
Summary: Left mouse button doesn't work in Mass Effect
Andromeda.
Product: Wine-staging
Version: 5.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mail.aermakov(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Left mouse button doesn't work(can't fire) in game Mass Effect Andromeda in
wine+staging 5.1. But wine 5.1 without staging patches works with mouse fine.
--
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=48089
Bug ID: 48089
Summary: Origin update hangs with Esync enabled
Product: Wine-staging
Version: 4.19
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: ---
Created attachment 65647
--> https://bugs.winehq.org/attachment.cgi?id=65647
+server
When Origin has an update available to be installed and Esync is enabled by
passing WINEESYNC=1 envar, the updater hangs and never finishes.
Disabling Esync solves the issue and allows Origin to complete the update.
Attaching +server log.
How to reproduce:
1) Create a prefix (64-bit will do)
2) Install DXVK using winetricks (app doesn't work correctly without it)
3) Add an override for OriginThinSetupInternal.exe and set it to disabled so
that the app doesn't update during installation and a backup could be made for
testing purposes.
4) Install an older version of Origin (you can use this link
https://lutris.nyc3.cdn.digitaloceanspaces.com/games/origin/OriginSetup.exe)
5) Kill all processes in the prefix and remove override for
OriginThinSetupInternal.exe
6) Run Origin.exe with WINEESYNC=1 envar passed on.
Behavior with Esync disabled: Update window appears, then closes after a while,
reopens and finishes the update.
Behavior with Esync enabled: Update window appears, then closes but never
reopens. The update hangs and never finishes.
During the test, regular wine-staging build was used, but I've also tried it
with a custom build that ports Fsync from Proton to Wine and it has the same
issue when Fsync is in use (which it indicated in the logs).
--
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.