From: foopub <foopub@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: FreeCAD 0.18.3 crashing on wayland
Date: Tue, 23 Nov 2021 01:39:02 +0100 [thread overview]
Message-ID: <20211123003902.Yn1-1zs46hjl2O5hzmwAt_qFI7XLNJ9sk8sq4VUKi7A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14626@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
New comment by foopub on void-packages repository
https://github.com/void-linux/void-packages/issues/14626#issuecomment-976041712
Comment:
I've tested the patch from that website on coin3 package and it seems to work so far.
`./xbps-src pkg -j24 coin3`
`doas xbps-install -fR hostdir/binpkgs/ coin3`
I'll be using FreeCAD the next few days and if something seemingly relevant breaks, I'll update. @yopito how do you recon this should be handled?
I don't know what this functionality that's being removed does, but if it's important in general, we can patch it only when a `wayland` option is passed. Otherwise patch it normally, and add back the functionality with a `glx` option.
next prev parent reply other threads:[~2021-11-23 0:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 10:44 [ISSUE] " voidlinux-github
2019-10-01 4:29 ` voidlinux-github
2019-12-29 13:27 ` voidlinux-github
2021-11-22 16:37 ` foopub
2021-11-23 0:39 ` foopub [this message]
2021-11-29 12:21 ` yopito
2022-03-02 19:20 ` luzpaz
2022-03-02 21:17 ` SammyTheSnake
2022-06-01 2:14 ` github-actions
2022-06-15 2:16 ` [ISSUE] [CLOSED] " github-actions
2023-10-22 13:35 ` gmelikov
2023-10-22 13:35 ` gmelikov
2023-10-22 20:48 ` gmelikov
2023-10-23 4:07 ` [ISSUE] [CLOSED] " sgn
2023-10-23 4:07 ` sgn
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=20211123003902.Yn1-1zs46hjl2O5hzmwAt_qFI7XLNJ9sk8sq4VUKi7A@z \
--to=foopub@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).