Other infos:
- if performed under kvm, the same debian installation that previously was
failed (see previous tests), under emulator it works correctly in all cases.
- when inkscape started on a physical machine, for each occurrence of the
bug, this line appears in the journal:
kernel: nouveau
I did some other tests:
on my system:
- I removed all noto fonts + font cache reindex
- test inkscape -> fonts preview ok
- I edited ~/.config/gtk-3.0/settings.ini and changed line "gtk-font-name"
with
another existing font (for example Arundina)
"gtk-font-name=Noto Sans 10" ->
I have adopted this workaround:
copy gtk-3.0 specific setting to inkscape config subdir:
cp -a ~/.config/gtk-3.0 ~/.config/inkscape/
editing file ~/.config/inkscape/gtk-3.0/settings.ini
comment line:
; gtk-font-name=Noto Sans 10
modify command start application in:
Quoting Antonio (2020-05-09 09:09:16)
> >Noto fonts are known to provide many entries in font menus.
> in fact I had to reinstall these fonts as they were used from the desktop
With "these fonts" do you mean _all_ fonts-noto-* packages, or only (as
I suggest) all except -extra?
Did you
>Indeed, that's considered a lot. For comparison, I have 481 :)
it doesn't depend on the number of fonts, even if with more fonts it slows
down a lot
>In theory, if you leave the program at it long enough (which effectively
>means you won't be able to use the system during that time...) it
>Noto fonts are known to provide many entries in font menus.
in fact I had to reinstall these fonts as they were used from the desktop
>Should be fine if avoiding only the *-extra packages (and the fonts-noto
>metapackage which recommends them)
This is true, but there is also a correlation with
Quoting Mattia Rizzolo (2020-05-08 21:27:44)
> On Fri, May 08, 2020 at 09:25:13PM +0200, Antonio wrote:
> > After several tests I realized that the problem depends on these fonts:
> > "fonts-noto, fonts-noto-cjk, fonts-noto-cjk-extra, fonts-noto-color-emoji,
> > fonts-noto-core, fonts-noto-extra,
On Fri, May 08, 2020 at 09:25:13PM +0200, Antonio wrote:
> After several tests I realized that the problem depends on these fonts:
> "fonts-noto, fonts-noto-cjk, fonts-noto-cjk-extra, fonts-noto-color-emoji,
> fonts-noto-core, fonts-noto-extra, known-fonts-hinted, known-fonts-mono,
>
Processing control commands:
> tag -1 -moreinfo
Bug #960036 [inkscape] inkscape takes 100% CPU when opening font combobox
Removed tag(s) moreinfo.
> forwarded -1 https://gitlab.com/inkscape/inkscape/-/issues/841
Bug #960036 [inkscape] inkscape takes 100% CPU when opening font combobox
Set Bug
Control: tag -1 -moreinfo
Control: forwarded -1 https://gitlab.com/inkscape/inkscape/-/issues/841
Control: severity -1 normal
On Fri, May 08, 2020 at 07:55:19PM +0200, Antonio wrote:
> >Could you please provide us:
> >fc-list | wc -l
> 4083
Indeed, that's considered a lot. For comparison, I
On Fri, May 08, 2020 at 06:13:26PM +0200, Antonio wrote:
> >Could you please give me more details?
>
> step for reproduce:
> - start program
> - open a blank document
> - select tool "create and modify textual object"
> - open combo for select the font (click on lateral arrow)
Which, I believe,
>Could you please give me more details?
step for reproduce:
- start program
- open a blank document
- select tool "create and modify textual object"
- open combo for select the font (click on lateral arrow)
-> a black vertical rectangle appears under the combo box and the desktop
freezes due to
Processing control commands:
> severity -1 important
Bug #960036 [inkscape] inkscape takes 100% CPU when opening font combobox
Severity set to 'important' from 'normal'
> tag -1 moreinfo upstream
Bug #960036 [inkscape] inkscape takes 100% CPU when opening font combobox
Added tag(s) moreinfo and
Control: severity -1 important
Control: tag -1 moreinfo upstream
Hi Antonio, thank you for the report.
On Fri, May 08, 2020 at 04:10:32PM +0200, Antonio wrote:
> after updating inkscape to version 1.0, when I open the combobox to select a
> font, the program consumes 100% of the cpu and the
14 matches
Mail list logo
