all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 42342@debbugs.gnu.org
Subject: bug#42342: Wine64 segfaults (5.12/staging)
Date: Tue, 28 Jul 2020 19:36:43 +0200	[thread overview]
Message-ID: <d1d54576efda64cb6b226be2bb47c7d1cb73b5b5.camel@student.tugraz.at> (raw)
In-Reply-To: <87ft9bzim7.fsf@nckx>

Am Dienstag, den 28.07.2020, 18:53 +0200 schrieb Tobias Geerinckx-Rice:
> Leo Prikler 写道:
> > I'll use inferiors as a local workaround for the time being and 
> > wait
> > for the problem to be fixed upstream.  I'll also look into 5.9 
> > to 5.11
> > and perhaps provide a proper downgrade patch later on.
> 
> I admit to being a bit confused.  IIRC on #guix you reported that 
> wine-staging was broken, not wine64-staging.  If you only want to 
> downgrade the latter, that's all right by me, but I consider that 
> one of the risks of using the staging branch to begin with.
> 
> Is there a reason you rely on staging, and the 64-bit version to 
> boot?
> 
> Kind regards,
> 
> T G-R
I'm referring to the package "wine64-staging", which is on master.  I
may have been confused myself at the time I mentioned this in #guix,
but now I have tested this a bit more thoroughly.

For one, I've historically been using wine64, since (at least on Guix)
it works with both 32bit and 64bit software and I sometimes stumble
upon the latter.  As a result, I have a 64bit wine prefix and using
wine (or wine-staging) does not really work well with that.  I was able
to determine that plain wine is unaffected by running the same commands
on a machine with no existing prefix.  (Note, that regular wine64 still
fails with a fresh prefix.)  My experiments with wine64-staging were
solely meant as a way of finding the point at which wine64 fails, I
have no intent of actually using it for more than that.
I'm not quite sure, what exactly is at fault here.  It could be
upstream, or it could be the magic that we use to merge 32 and 64 bit
wine.

TL;DR: The affected packages are wine64 and wine64-staging, the latter
of which is broken beyond 5.8 (though 5.9 would work as well).  Since
this affects the 64bit version of wine specifically, we either have to
fix something in our build (not sure what) or desync wine and wine64
(same with -staging variants)

Regards,
Leo





  reply	other threads:[~2020-07-28 17:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13  9:53 bug#42342: Wine64 segfaults (5.12/staging) Leo Prikler
2020-07-13 12:24 ` Leo Prikler
2020-07-28 16:53   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-07-28 17:36     ` Leo Prikler [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d1d54576efda64cb6b226be2bb47c7d1cb73b5b5.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=42342@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.