Arch Linux User Repository

@sanerb electron21 need to be rebuilded both for new icu and dav1d versions

You should probably review the deps, because something wild is going on.

So icu73 should be a build dep:

node: error while loading shared libraries: libicui18n.so.73: cannot open shared object file: No such file or directory ==> ERROR: A failure occurred in build(). Aborting...

https://aur.archlinux.org/packages/icu73 https://aur.archlinux.org/packages/icu73-bin

(I used the latter; they're two different maintainers but probably either is acceptable. Latter provides former.)

BUT icu-72 is a runtime dep:

$ pencil /usr/lib/electron21/electron: error while loading shared libraries: libicui18n.so.72: cannot open shared object file: No such file or directory

https://aur.archlinux.org/packages/icu72-bin

There's also this dep:

$ pencil /usr/lib/electron21/electron: error while loading shared libraries: libdav1d.so.6: cannot open shared object file: No such file or directory

which isn't even available in Arch repos or AUR; current is dav1d-1.3.0 which provides libdav1d.so.7, so....

All these are likely tied to the electron version used. I'd see if it can use a newer electron version.

Hi @lkrms, sorry for the late reply: noticed that the upstream's electron is somehow unsupported version.

Also, the failure of start may due to previous brutal patch applied.

Maybe also check that you're compiling under clean chroot.

Anyway, hope this release fix some issue on your side.

@alerque: noted.

With this package installed, I wasn't able to get Pencil to progress past its startup/splash screen, presumably because a recent release of Electron broke backward compatibility. Using an older release of Electron worked but there were additional issues, e.g. an Unsupported document type error on startup, which appeared to have been fixed upstream.

To remedy all of this while removing potentially dangerous calls to rm -rfv, I've reworked PKGBUILD to build [and run] against the same node [and electron] versions used upstream, apply additional upstream patches, and use electron-builder to create an optimised static app build.

This approach may be problematic for reasons I'm not aware of, and I'm not expecting such a significant refactor to be adopted by the maintainer, but in case it helps others and/or @BrLi would like to incorporate any of the changes: https://github.com/lkrms-pkgbuilds/pkgbuild-pencil

Please remove both of the conflicts entries. The -bin package should specify it's own provides/conflicts relative to the base package name (this one) not the other way around. This is documented in the Wiki on package naming. Also the same goes for the v2 alternative package, that should provide/conflict this, not the other way around as this is the stable normalized package name and the others are alternates.

Same issue here with the eternal blinking logo on electron v13. Works with electron v11 though (thx @jle64 !).

Pencil has just the logo blinking, when launching i just have this in terminal:

useHWAConfig: undefined Hardware acceleration disabled for Linux. Background web-printer started. Shortcut main service started. (node:15007) ProtocolDeprecateCallback: The callback argument of protocol module APIs is no longer needed. (Use electron --trace-warnings ... to show where the warning was created)

i read some line about exec command in desktop file, but i juste have:

Exec=/usr/bin/pencil %u

i've tried to add --trace-warnings in /usr/bin/pencil

exec electron --trace-warnings /usr/lib/pencil "$@"

but nothing more displayed in terminal.

what could i do ?

i'm runnin electron 12.0.9-1 pencil 3.1.0-7 yarn 1.22.10-1

How did @jle64 run it with electron11?

@alfredo.ardito just install the electron11 package, then run "electron11 /usr/lib/pencil" or copy the /usr/bin/electron script somewhere in your PATH to take priority over the default and change electron to electron11 inside.

Same for me. It starts and stays on the blinking logo and nothing else.
How did @jle64 run it with electron11?