From: "Paul E. McKenney" <paulmck@kernel.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH -perfbook 0/3] Work around errors of unstable Inkscape
Date: Sat, 14 Oct 2023 16:57:20 -0700 [thread overview]
Message-ID: <fd871edf-2322-4a2a-893f-6ef56c7593cd@paulmck-laptop> (raw)
In-Reply-To: <d2caff5c-21bf-41c1-874f-194933ce0891@gmail.com>
On Sun, Oct 15, 2023 at 08:22:44AM +0900, Akira Yokosawa wrote:
> On 2023/10/13 23:33, Akira Yokosawa wrote:
> > Hi Paul,
> >
> > I expected the crashing bug in Fedora's distro Inkscape would be
> > resolved by the time of Fedora 39 release.
> > I tested Fedora 39 beta and was disappointed to see more or less the
> > same crashes of command-line runs of Inkscape as those under Fedora 38.
> >
> > As a matter of fact, even when Inkscape crashes, the export of PDF
> > is complete most of the time. So the crashing bug can be worked
> > around by ignoring the error code from Inkscape and continue building.
> >
> > This patch set implements the ad-hoc workaround in build scripts.
> >
> > As you can see in Patch 1/3, the workaround is enabled by default.
> > This is because enabling it won't do any harm on systems with
> > stable Inkscape.
> >
> > I might be able to add some heuristics not to enable the workaround
> > for stable Inkscape installs, but that can wait.
> >
> > Ubuntu releases 22.04LTS, 23.04, and 23.10 are free of this issue.
>
> No, Ubuntu 23.04 shows this symptom, rarer than Fedora but still...
Even more reason for it to be applied, then. ;-)
Again, thank you!
Thanx, Paul
> Thanks, Akira
>
> >
> > Thanks, Akira
> > --
> > Akira Yokosawa (3):
> > Ignore error of unstable Inkscape
> > Ignore emergency-save SVG files from Inkscape
> > Make sure all PDF conversions are complete
> >
> > .gitignore | 1 +
> > Makefile | 17 ++++++++++++++---
> > 2 files changed, 15 insertions(+), 3 deletions(-)
> >
> >
> > base-commit: 84759ebac65a03aa28c5b02007e6c472b3416d3d
prev parent reply other threads:[~2023-10-14 23:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 14:33 [PATCH -perfbook 0/3] Work around errors of unstable Inkscape Akira Yokosawa
2023-10-13 14:38 ` [PATCH -perfbook 1/3] Ignore error " Akira Yokosawa
2023-10-13 14:39 ` [PATCH -perfbook 2/3] Ignore emergency-save SVG files from Inkscape Akira Yokosawa
2023-10-13 14:42 ` [PATCH -perfbook 3/3] Make sure all PDF conversions are complete Akira Yokosawa
2023-10-13 23:43 ` [PATCH -perfbook 0/3] Work around errors of unstable Inkscape Paul E. McKenney
2023-10-14 23:22 ` Akira Yokosawa
2023-10-14 23:57 ` Paul E. McKenney [this message]
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=fd871edf-2322-4a2a-893f-6ef56c7593cd@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=perfbook@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).