Le mardi 30 mai 2023 à 22:40 +0200, Jean Abou Samra a écrit :
> Le dimanche 28 mai 2023 à 14:37 +0200, Jean Abou Samra a écrit :
> >
> > One thing I will try when I can is building in a Kubuntu VM. So far, I used
> > a VM with the default Ubuntu variant, with GNOME. That would normally not
> >
Le dimanche 28 mai 2023 à 14:37 +0200, Jean Abou Samra a écrit :
>
> One thing I will try when I can is building in a Kubuntu VM. So far, I used a
> VM with the default Ubuntu variant, with GNOME. That would normally not
> matter, but since the desktop environments are
> different, maybe
> Le 28 mai 2023 à 05:29, Colin Campbell a écrit :
>
> Just in case it might help, I uninstalled the font, and reran the test file,
> successfully. Logs attached to compare against failed run.
These logs sound like I was wrong to blame Pango. Apparently, the introduction
of emoji
On 2023-05-27 20:36, Colin Campbell wrote:
Well, colour me embarrassed! First, I had applied your patches using
git cola, and received a confirmation screen saying the patches were
applied. Being suspicious, I had a look at the actual files with Kate,
and found no patches had actually been
On 2023-05-27 16:45, Jean Abou Samra wrote:
Le dimanche 28 mai 2023 à 00:38 +0200, Jean Abou Samra a écrit :
Le samedi 27 mai 2023 à 16:31 -0600, Colin Campbell a écrit :
I generally keep my system current, and libpango is at 1.0-0 already.
The "1.0" version number denotes an ABI
Le dimanche 28 mai 2023 à 00:38 +0200, Jean Abou Samra a écrit :
> Le samedi 27 mai 2023 à 16:31 -0600, Colin Campbell a écrit :
> > I generally keep my system current, and libpango is at 1.0-0 already.
> The "1.0" version number denotes an ABI compatibility promise as far as I
> understand;
Le samedi 27 mai 2023 à 16:31 -0600, Colin Campbell a écrit :
> I generally keep my system current, and libpango is at 1.0-0 already.
The "1.0" version number denotes an ABI compatibility promise as far as I
understand; current versions of Pango are actually around 1.50. (1.0.0 is from
around
On 2023-05-27 16:10, Jean Abou Samra wrote:
Le dimanche 28 mai 2023 à 00:05 +0200, Jean Abou Samra a écrit :
If Pango fails to correctly substitute values in the FcConfig, it
could potentially mean that it's passed with some fields
uninitialized to Fontconfig. That could explain why the
Le dimanche 28 mai 2023 à 00:05 +0200, Jean Abou Samra a écrit :
> If Pango fails to correctly substitute values in the FcConfig, it could
> potentially mean that it's passed with some fields uninitialized to
> Fontconfig. That could explain why the error is not
> reproducible; the value of
Le samedi 27 mai 2023 à 07:50 +0200, Jean Abou Samra a écrit :
> > With lilypond 2.25.6 and your second patch applied, here are 2 .PDFs:
> > first is without the offending font installed, the second is the temporary
> > file produced when the font is present.
>
>
> Thanks, but I am more
>
> With lilypond 2.25.6 and your second patch applied, here are 2 .PDFs: first
> is without the offending font installed, the second is the temporary file
> produced when the font is present.
>
Thanks, but I am more interested in the log than the PDF for this one.
On 2023-05-26 02:24, Jean Abou Samra wrote:
Good that you can reproduce again. Now, can you try the patch with
FcPatternPrint and send the log? (No need for FC_DEBUG or --verbose or
--ps this time.)
With lilypond 2.25.6 and your second patch applied, here are 2 .PDFs:
first is without
Le jeudi 25 mai 2023 à 19:06 -0600, Colin Campbell a écrit :
> I believe we now have a Bingo!
>
> I d/l and built lilypond 2.25.5 from the website, and ran it against the
> test file; it ran successfully.
>
> I re-installed the fonts-noto-color-emoji package, and ran lilypond
> 2.25.5 again,
Le mercredi 24 mai 2023 à 20:31 -0600, Colin Campbell a écrit :
> Applied this on top of your previous patch; let me know if you want it
> done differently.
>
> Again, no problems applying, compiling lilypond, nor compiling the test
> file.
>
> Resulting .PDF attached
Sorry for not being
On 2023-05-23 14:38, Jean Abou Samra wrote:
Le mardi 23 mai 2023 à 22:08 +0200, Jean Abou Samra a écrit :
So Pango is apparently requesting a font with colored glyphs from Fontconfig...
Speaking of which, I would also be interested in the output with
```
diff --git
On 2023-05-23 13:28, Jean Abou Samra wrote:
Colin: it's really hard to debug this remotely (we might have to resort to VNC
or such, I'm afraid...) but there is one simple thing I would be interested in:
if you apply this patch, recompile LilyPond and redo the test, what happens?
```
diff
Le mercredi 24 mai 2023 à 09:08 +, Werner LEMBERG a écrit :
> > So Pango is apparently requesting a font with colored glyphs from
> > Fontconfig...
>
> A bug?
Probably.
So far, I've been unable to understand where this happens; "git grep FC_COLOR"
yields no results in the Pango source
> So Pango is apparently requesting a font with colored glyphs from
> Fontconfig...
A bug?
Werner
Le mardi 23 mai 2023 à 22:08 +0200, Jean Abou Samra a écrit :
> So Pango is apparently requesting a font with colored glyphs from
> Fontconfig...
Speaking of which, I would also be interested in the output with
```
diff --git a/lily/all-font-metrics.cc b/lily/all-font-metrics.cc
index
Le mardi 23 mai 2023 à 21:15 +0200, Jean Abou Samra a écrit :
> Le lundi 22 mai 2023 à 08:07 +, Werner LEMBERG a écrit :
>
> > Regarding (2) I'm not sure where exactly the problem lies (i.e., whether it
> > is a LilyPond or a Pango issue).
>
> I'm rather sure it's a Pango or Fontconfig
Le mardi 23 mai 2023 à 21:15 +0200, Jean Abou Samra a écrit :
> Le lundi 22 mai 2023 à 08:07 +, Werner LEMBERG a écrit :
>
> > Regarding (2) I'm not sure where exactly the problem lies (i.e., whether it
> > is a LilyPond or a Pango issue).
>
> I'm rather sure it's a Pango or Fontconfig
Le lundi 22 mai 2023 à 08:07 +, Werner LEMBERG a écrit :
> Regarding (2) I'm not sure where exactly the problem lies (i.e., whether it
> is a LilyPond or a Pango issue).
I'm rather sure it's a Pango or Fontconfig issue.
Based on the fact that we use Pango's FreeType backend, which is not
> Following your suggestion, Werner, I tried the test file with the
> cairo back end, and it worked as expected.
Great, please send me the created PDF for further analysis – just to
be sure :-)
> I then deleted the Noto Color Emoji font (synaptic also deleted
> texlive fonts extra links), and
On 2023-05-22 02:07, Werner LEMBERG wrote:
(1) You have the font 'Noto Color Emoji' installed on your system (the
new one, with scalable glyphs using the 'COLR' v1 format). Say
`fc-list | less` to find out where it is located. This font
format is not supported by GhostScript
Colin,
>> All this comes about as I'm thinking of getting back to
>> some documentation work, and wanted to compile docs locally. I'll
>> still keep that goal in mind.
>>
>> If you can still reproduce the problem after this cleaning, could
>> you run
>>
>> ```
>> FC_DEBUG=2025
(Adding back the bug list)
Le samedi 20 mai 2023 à 17:51 -0600, Colin Campbell a écrit :
>
> I redid git bisect today, doing everything on the command line (I used
> Frescobaldi last night). Each time, I ran "
>
> ```
> colin@Calvin:/Work/lilypond/lilypond$ cd build
>
Le vendredi 19 mai 2023 à 23:00 -0600, Colin Campbell a écrit :
> The result of git bisect:
>
> 1db87a2537d6d5ef6631cfbda63954c0a6ee095 is the first bad commit
> commit d1db87a2537d6d5ef6631cfbda63954c0a6ee095
> Author: Jonas Hahnfeld
> Date: Mon Apr 3 22:57:26 2023 +0200
>
> Doc: Avoid
The result of git bisect:
1db87a2537d6d5ef6631cfbda63954c0a6ee095 is the first bad commit
commit d1db87a2537d6d5ef6631cfbda63954c0a6ee095
Author: Jonas Hahnfeld
Date: Mon Apr 3 22:57:26 2023 +0200
Doc: Avoid full stop in node names
This propagates the changes from commit c245707e4f to
On 2023-05-19 15:43, Jean Abou Samra wrote:
Le vendredi 19 mai 2023 à 21:00 +0200, Jean Abou Samra a écrit :
Can you try to find which commit introduced the problem for you, using 'git
bisect'?
Alternatively: what's your Ubuntu version? I just installed a fresh Ubuntu
23.04 VM and compiled
Le vendredi 19 mai 2023 à 21:00 +0200, Jean Abou Samra a écrit :
> Can you try to find which commit introduced the problem for you, using 'git
> bisect'?
Alternatively: what's your Ubuntu version? I just installed a fresh Ubuntu
23.04 VM and compiled LilyPond in it but I cannot reproduce the
Le vendredi 19 mai 2023 à 12:26 -0600, Colin Campbell a écrit :
>
> On 2023-05-19 11:03, Jean Abou Samra wrote:
> > \version "2.25.5"
> >
> > #(define-markup-command (db layout props arg) (markup?)
> > (let ((stil (interpret-markup layout props arg)))
> > (pretty-print (ly:stencil-expr
On 2023-05-19 11:03, Jean Abou Samra wrote:
\version "2.25.5"
#(define-markup-command (db layout props arg) (markup?)
(let ((stil (interpret-markup layout props arg)))
(pretty-print (ly:stencil-expr stil))
stil))
\markup \db abc
Terminal output:
###
Le vendredi 19 mai 2023 à 09:43 -0600, Colin Campbell a écrit :
> > Of all the errors you posted, which one is it now?
> ```
> colin@Calvin:/Work$ lilypond Non-Musical.ly
> GNU LilyPond 2.25.5 (running Guile 2.2)
> Processing `Non-Musical.ly'
> Parsing...
> Interpreting music...
On 2023-05-18 23:30, Jean Abou Samra wrote
Thanks, Werner, for the suggestion. I just tried it, and lilypond still errors
as before.
Of all the errors you posted, which one is it now?
colin@Calvin:/Work$ lilypond Non-Musical.ly
GNU LilyPond 2.25.5 (running Guile 2.2)
Processing
> Thanks, Werner, for the suggestion. I just tried it, and lilypond still
> errors as before.
Of all the errors you posted, which one is it now?
On 2023-05-18 22:09, Werner LEMBERG wrote:
ran make successfully, got carried away and may have shot myself in
the foot by running sudo make install.
You should actually do
```
make bytecode
sudo make install-bytecode
```
Without installing the Guile bytecode, LilyPond is slooow.
Thanks,
> ran make successfully, got carried away and may have shot myself in
> the foot by running sudo make install.
You should actually do
```
make bytecode
sudo make install-bytecode
```
Without installing the Guile bytecode, LilyPond is slooow.
Werner
On 2023-05-18 21:07, Colin Campbell wrote:
On 2023-05-18 01:55, Jean Abou Samra wrote:
I'm going nuclear tomorrow: delete my clone, and start over.
No need to be *that* nuclear, you can just remove the build directory
and start a fresh build.
Deleted /build,
mkdir build,
cd build
On 2023-05-18 01:55, Jean Abou Samra wrote:
I'm going nuclear tomorrow: delete my clone, and start over.
No need to be *that* nuclear, you can just remove the build directory and start
a fresh build.
Deleted /build,
mkdir build,
cd build
ran make successfully, got carried away and
Wonderful, thank you!
\--
Gwyn Ciesla
she/her/hers
\
in your fear, seek only peace
in your fear, seek only love
\-d. bowie
Sent from Proton Mail mobile
\ Original Message
On May 18, 2023, 12:53 PM, Jean Abou
Le jeudi 18 mai 2023 à 11:27 +0200, Jean Abou Samra a écrit :
> Gwyn, is it convenient for you to test patches? I think I see what this is
> caused by, but I cannot reproduce the bug in a local build (knowing what
> exact compiler flags are used in Fedora's builds
> might help).
> I'd like to
Gwyn, is it convenient for you to test patches? I think I see what this is
caused by, but I cannot reproduce the bug in a local build (knowing what exact
compiler flags are used in Fedora's builds might help).
I'd like to know if this fixes it:
```
diff --git a/lily/all-font-metrics-scheme.cc
> I'm going nuclear tomorrow: delete my clone, and start over.
No need to be *that* nuclear, you can just remove the build directory and start
a fresh build.
> Le 18 mai 2023 à 05:49, Colin Campbell a écrit :
>
> Attached console output. I'll do a git pull and recompile a bit later, and
> report what happens. Note that the same test file when compiled using
> Frescobaldi as a front end, produces the following output:
>
>
> Starting lilypond
On 2023-05-17 18:25, Jean Abou Samra wrote:
Could you please run with `lilypond --verbose` and send the output?
Thanks,
Jean
Now lilypond blows up in make:
colin@Calvin:/Work/lilypond/lilypond/build$ make -j3 SILENT=1
PythonUI_Init()
PythonUI_Init()
PythonUI_Init()
Attached console output. I'll do a git pull and recompile a bit later,
and report what happens. Note that the same test file when compiled
using Frescobaldi as a front end, produces the following output:
Starting lilypond 2.25.5 [Non-Musical.ly]...
programming error: unknown context mod tag
Le mercredi 17 mai 2023 à 17:48 -0600, Colin Campbell a écrit :
> Happens to me on Ubuntu as well:
I don't think that's the same bug. Regarding this:
> Fontconfig error: No writable cache directories
This error popped up at some point during the current cycle before being fixed
shortly
Happens to me on Ubuntu as well:
&&
colin@Calvin:/Work$ lilypond Non-Musical.ly
GNU LilyPond 2.25.5 (running Guile 2.2)
Fontconfig error: No writable cache directories
Processing `Non-Musical.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Le mercredi 17 mai 2023 à 20:02 +, Gwyn Ciesla via bug-lilypond a écrit :
> Attaching reproducer.
>
> From Fedora bug:
>
> When I attempt to build a score using a PianoStaff or GrandStaff (which
> contains more than one sub-staff), lilypond crashes.
>
> Reproducible: Always
>
> Steps to
49 matches
Mail list logo
