https://bugs.winehq.org/show_bug.cgi?id=56468
Bug ID: 56468
Summary: The program jcef_helperexe encountered a serious
problem and needs to be closed. We apologize for any
inconvenience this may have caused
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yu.liao.davcai(a)gmail.com
Distribution: ---
Created attachment 76234
--> https://bugs.winehq.org/attachment.cgi?id=76234
Unhandled exception: illegal instruction in 64-bit code (0x006ffff4344d99).
The program jcef_helperexe encountered a serious problem and needs to be
closed. We apologize for any inconvenience this may have caused.
--
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=48068
Bug ID: 48068
Summary: Mostly black window in Epic Games Launcher
Product: Wine
Version: 4.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: michelle(a)iheartmichelle.com
Distribution: ---
Created attachment 65617
--> https://bugs.winehq.org/attachment.cgi?id=65617
Output of % wine {Prefix}/drive_c/Program Files (x86)/Epic
Games/Launcher/Portal/Binaries/Win64/EpicGamesLauncher.exe
-SkipBuildPatchPrereq
I have installed the Epic Games Launcher. It opens up with a mostly black
window. However, the app draws its own window controls, such as minimize and
close, and those work. Also, there's a "Settings" icon in the corner. When I
click that, it takes me to a settings screen which appears to work. However,
the rest of the window is black and I cannot install the untitled goose game,
as I so desperately want to do.
I'm using wine 4.19-staging. The Epic Games Launcher version ... well, I have
a story about that: While I was gathering info for this bug report, I started
the launcher and this time, the "Settings" icon had a dot on it. So I clicked
the Settings icon, and it said there was a new version of the launcher and I
should click here to install the new version and restart the launcher, and I
did and it worked. So at least that much of the app is working.
Anyway, the version (which is visible from the Settings screen) is now
10.9.1-10088168+++Portal+Release-Live
I don't think this is related to the ancient #40376 since that was last updated
2 years ago and seems to be caused by a bug which was fixed in a prior version
of wine.
--
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=55824
Bug ID: 55824
Summary: Unable to enter text in Epic Game Launcher
Product: Wine
Version: 8.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: guidoj2269(a)gmail.com
Distribution: ---
The most recent version of Epic Game Launcher 15.7.0 installs and starts up in
Wine 8.18 without any problems. On a clean install the Epic Game Launcher opens
a window and asks you to sign up or sign in. There is a textbox where you are
required to enter an email address. This textbox can be selected, but it is
impossible to enter any text. Nothing happens when hitting keys on the keyboard
when this textbox is active. This leaves the Epic Games not accessible.
Console output gives the following messaging, although maybe not every line is
related to this problem:
02f0:fixme:win:GetPointerDevices (00007FFFFEC7EE84 0000000000000000): partial
stub
02f0:fixme:system:NtUserQueryDisplayConfig flags 0x2, paths_count
0x7ffffec7ee50, paths 0x7998007bbb70, modes_count 0x7ffffec7ee84, modes
0x799800705580, topology_id (nil) semi-stub
02f0:fixme:system:NtUserDisplayConfigGetDeviceInfo Unimplemented packet type
11.
02f0:fixme:ui:uisettings2_get_TextScaleFactor iface 00007F655C7822E8, value
00007FFFFEC7ED60 stub!
02f0:fixme:msctf:TextStoreACPSink_OnLayoutChange STUB:(00007F655C95A930)
02f0:fixme:msctf:TextStoreACPSink_OnLayoutChange STUB:(00007F655C95A930)
The most recent version of the Epic Games Launcher can be freely downloaded
here:
https://launcher-public-service-prod06.ol.epicgames.com/launcher/api/instal…
Note that previous versions of both the Epic Games Launcher and Wine worked
well together, but I do not know which versions, nor do I have them available.
--
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=57104
Bug ID: 57104
Summary: every game I try segfaults in the same way in
Experimental WOW64 mode
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: redwindwanderer(a)gmail.com
Distribution: ---
Created attachment 76986
--> https://bugs.winehq.org/attachment.cgi?id=76986
WINE Experimental WOW64 crash log
Hi,
I build WINE latest gitlab master branch code in a 64bit-only Debian Stable
system.
I build it like this:
./configure --enable-win64 --without-x --with-wayland
--enable-archs=x86_64,i386
However, any games using Directx crash before even starting (backtrace log
attached).
Is that expected at this point? Shouldn't many games work by now in
experimental WOW64 mode or is it still early days?
Thanks!
--
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=56927
Bug ID: 56927
Summary: msys2-64/cygwin64: rsync fails with 'Socket operation
on non-socket'
Product: Wine
Version: 9.12
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Created attachment 76749
--> https://bugs.winehq.org/attachment.cgi?id=76749
Notes to reproduce, a backtrace in cygwin/wine.
I tried to check if bug #19858 is still an issue.
Unfortunately I hit a rsync call which fails:
$ rsync -aq --delete-before dir-a dir-b
rsync: [Receiver] Failed to dup/close: Socket operation on non-socket (108)
rsync error: error in IPC code (code 14) at pipe.c(157) [Receiver=3.2.7]
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(231)
It looks like rsync forks a child process, and the child tries then to close
the derived socket, which cannot be found in closesocket/socket_list_remove.
This seems kind of similar to bug #54995.
--
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=56925
Bug ID: 56925
Summary: msys2-64/cygwin64: unlink of read-only file fails
Product: Wine
Version: 9.12
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Created attachment 76744
--> https://bugs.winehq.org/attachment.cgi?id=76744
A few notes and backtraces in wine and cygwin.
In another attempt to check the state of msys2 or cygwin I found following
issue trying to update a msys2-64 installation:
# LANG=C pacman -Suy
:: Synchronizing package databases...
...
warning: could not remove lock file /var/lib/pacman/db.lck
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
...
A simpler version to reproduce is this:
rm -f test.txt
LANG=C wine cmd
echo test > test.txt
attrib +r test.txt
c:\msys64\usr\bin\rm.exe -f -v test.txt
Returns:
/usr/bin/rm: cannot remove 'test.txt': Permission denied
This tests were done with a wine tree including patches for this bugs:
52105
55138
53574
54995
--
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=55970
Bug ID: 55970
Summary: Switching sound devices does not work correctly
Product: Wine
Version: unspecified
Hardware: aarch64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: preston(a)babypuncher.net
App tested: foobar2000
Behavior when switching sound devices is inconsistent.
Switching from headphone jack to internal speaker does work when "Primary Sound
Driver is selected" and output device is changed in macOS or by unplugging
headphones.
The inverse does not work, Wine will continue playing audio through the
internal speakers after macOS has switched back to the headphone jack.
Manually changing sound devices away from "Primary Sound Driver" in foobar2000
itself causes playback errors.
--
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=57114
Bug ID: 57114
Summary: Fading text still visible when "opacity:0" set
Product: Wine
Version: 9.16
Hardware: x86-64
URL: https://cef-builds.spotifycdn.com/cef_binary_127.3.5%2
Bg114ea2a%2Bchromium-127.0.6533.120_windows64_client.t
ar.bz2
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
Distribution: Ubuntu
Created attachment 77005
--> https://bugs.winehq.org/attachment.cgi?id=77005
Screencast
The drag and drop test at https://bestvpn.org/html5demos/drag/ does not behave
as expected with the Chrome Embedded Framework sample application.
In Windows 10 the text that appears fades away (opacity:0 is set). See attached
video. The same is true using Chrome on Windows and Linux.
With Wine 9.16 the text remains visible until another element is activated with
the pointer.
I don't know if the effect is down to CSS, Javascript or a combination of the
two.
--
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=19153
Summary: DX3 game does not recognize graphics capabilities
Product: Wine
Version: 1.1.24
Platform: PC
URL: http://appdb.winehq.org/objectManager.php?sClass=versi
on&iId=9396
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bobbyg(a)gmx.net
Resident Evil 1 does not start giving the error "Failed to initialize the
Graphics Hardware Device.(3)". It's a DirectX 3 game using immediate mode.
After some debugging I found that it relies on 3 (three) entries returned by
EnumDevices whereas wine returns only the Direct3D HAL entry in this case
(d3dversion == 1). Removing the if-clause in ddraw/direct3d.c and duplicating
the HAL entry solves the problem and the game actually runs almost perfectly
(Garbage -> Platinum).
I checked a Windows installation which returns "HAL", "RGB Emulation" and "Ramp
Emulation" but the comments in the file suggest that not all games are happy
about that. So how to fix this properly?
--
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.