From: Leo Prikler <leo.prikler@student.tugraz.at>
To: 42342@debbugs.gnu.org
Subject: bug#42342: Wine64 segfaults (5.12/staging)
Date: Mon, 13 Jul 2020 11:53:51 +0200 [thread overview]
Message-ID: <0f14a6d95dbdd04c8ff9da03a47f0d205a5e1002.camel@student.tugraz.at> (raw)
Since commit 065a5ed677cdd1a65acae20f185d7c4bd23b1f2c wine and wine64
are upgraded to version 5.12. The latter segfaults when doing anything
other than wine --help or wine --version. (Try for example wine
regedit or winecfg).
The old 5.3 version continues to work after roll-back, and would
probably also work through inferiors. I am currently checking previous
versions of wine64-staging with guix time-machine to see at which point
the error might have been introduced. Until now, version 5.6 from
7b23a69d6b97c463cb1ef237931af11c22c19c67 fails with the following
output:
000b:fixme:winediag:__wine_start_process Wine Staging 5.6 is a testing
version containing experimental patches.
000b:fixme:winediag:__wine_start_process Please mention your exact
version when filing bug reports on winehq.org.
0009:err:module:LdrInitializeThunk "kernelbase.dll" failed to
initialize, aborting
0009:err:module:LdrInitializeThunk Initializing dlls for
L"C:\\windows\\system32\\winecfg.exe" failed, status c0000005
Regards, Leo
next reply other threads:[~2020-07-13 9:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 9:53 Leo Prikler [this message]
2020-07-13 12:24 ` bug#42342: Wine64 segfaults (5.12/staging) Leo Prikler
2020-07-28 16:53 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-07-28 17:36 ` Leo Prikler
2020-07-28 10:01 ` Pierre Neidhardt
2020-07-28 15:58 ` Pierre Neidhardt
2020-07-28 16:22 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-07-28 16:28 ` Pierre Neidhardt
2020-07-28 16:41 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-07-29 10:33 ` Pierre Neidhardt
2020-07-30 14:54 ` Jakub Kądziołka
2020-07-31 12:37 ` pelzflorian (Florian Pelz)
2020-08-09 13:38 ` Pierre Neidhardt
2020-08-09 14:03 ` Pierre Neidhardt
2020-08-09 15:03 ` Jakub Kądziołka
2021-05-11 15:40 ` Leo Prikler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0f14a6d95dbdd04c8ff9da03a47f0d205a5e1002.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=42342@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).