[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#974856: RFS: klatexformula/4.1.0-1 [RC] -- GUI to easily get an image from a LaTeX formula or equation



On Friday 25 December 2020 22:57:59 CET you wrote:
> Apologies if I said this before, but at start-up it prints to the CLI
> Warning: libpng warning: iCCP: known incorrect sRGB profile
> though I can't tell you what that means.

Some pngs shipped with klf have embedded ICC profiles about which libpng 
complains, see also: 

https://stackoverflow.com/questions/22745076/libpng-warning-iccp-known-incorrect-srgb-profile
 
Using mogrify on all pngs as suggested in the linked discussion does work 
here. I reported this issue upstream - However, I do not think that this 
justifies modifying the pngs and repacking the source. 

> Are effects supposed to show up in the preview window? I've yet to figure
> out what they're supposed to look like. If I click directly on the preview
> after having enabled an effect, I get

The effects do not appear in the preview window. The fire effect is quite 
drastic, others more subtle. 

> Warning: ***** In function KLFUserScriptExporter::getData()  *****
>         Error: Error running user script imagemagickeffect: <p><b>User
> Script /
> usr/share/klatexformula/userscripts/imagemagickeffect.klfuserscript</b>
> reported an error (exit status 1). Here is full stderr output:</p> <pre>
> 
> This script is part of the Python argcomplete package (https://github.com/
> kislyuk/argcomplete).
> It is used to check if an EASY-INSTALL-SCRIPT wrapper redirects to a script
> that contains the string
> "PYTHON_ARGCOMPLETE_OK". If you have enabled global completion in
> argcomplete, the completion hook will run it every
> time you press &lt;TAB&gt; in your shell.

The reason is that in a fresh installation klatexformula finds

/usr/bin/python-argcomplete-check-easy-install-script3

as python interpreter. This was for me /usr/bin/python3 due to an unclean 
build/test environment.

I reported this also upstream and added a patch to directly look up python3. 

> found" It's also unexpected that it prints HTML-style output both to my
> shell and in the user script log.

When using the `View user script log ...' button the html is rendered for me - 
having the html on the shell is indeed confusing.


Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: