I am using Debian Buster.Both, the AppImage- and the DEB-Package of 0.35 will not start.
The AppImage just dont start.
And when i try the DEB-Installation nothing happens, Starting it as User from Terminal it output me this:
[30763:0710/155919.278734:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/Publii/chrome-sandbox is owned by root and has mode 4755.
So please, fix this and keep on the good work!
I will check this issue soon. I have tested the linux packages on Ubuntu but as I had to create a new environment for preparing Publii packages on Linux, something could go wrong.
I will come back when I prepare some fixes
--Do you appreciate the support you've received today? If so, consider donating to the Publii team by clicking here; we'll be sure to use your donation to make Publii even better!
I suppose that it is a bigger issue with Electron itself: https://github.com/electron/electron/issues/17972
I will try to generate packages with --no-sandbox and I will provide you an updated packages for download to test them.
Hi Thomas, thx i tried to start your packages.
The AppImage 0.35.0 don't start yet, no matter if i klick on the AppImage-Package / LauncherIcon or if i try to start from Terminal.
From Terminal i get this:
The setuid sandbox is not running as root. Common causes:
* An unprivileged process using ptrace on it, like a debugger.
* A parent process set prctl(PR_SET_NO_NEW_PRIVS, ...)
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
The DEB-Package 0.35.0 starts from Launchpanel and also from Terminal.
From Terminal it also shows me this:
(node:11399) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
... before its starts.
That's the same as it shows me already when is start the AppImage 0.34 as user from Terminal ;-)
There's some more incorrect ( in DEB-Package 0.35.0 ), I cant upload my website. I didn't changed anything on my configuration and at around 20% of Process it stops and say:
'An error occurred during rendering of your Website'
after it the "Sync your Website"-Button shows "Preparation error".
AppImage 0.34.1 still works fine ;-)
thanks for the feedback
The AppImage issue is caused by Electron 5 and the only solution for your distribution will be probably starting it with —no-sandbox param in the terminal.
But as the DEB package works then there is no blocker to use Publii on Debian. On my Ubuntu AppImage works without problems and it is strictly related to the differences in the different linux distributions.
The updated packages are available for download from our website
made the AppImage 0.35.0 running. (Only from Terminal of course).But also can't 'Sync my Website' from that AppImage-version.
The issue is not related to an environment where the Publii is packaged. It is an Electron issue: https://github.com/electron/electron/issues/17972
And we cannot too much more with AppImage at this moment :/ It will work only on some distributions. For other distros the DEB/RPM package must be used.
As long the DEB doesn't work completely for me, I will stick with v.0.34.1 for now ;-)
So far, thanks for looking for the problems.
Now I am a little bit confused.
> The DEB-Package 0.35.0 starts from Launchpanel and also from Terminal.
And now you wrote:
> As long the DEB doesn't work completely for me, I will stick with v.0.34.1 for now ;-)
So the DEB package is working for you or no?
Could you check if this issue does not affect you: https://github.com/GetPublii/Publii/issues/515
As this is now a known error which could introduce fail of the website preview.
Hi Thomas, sorry you had to wait for an answer.
I can confirm:
After i changed 'Posts Listing' from ' Random ' to ' By ID descending ' or ' By ID ascending '.
It works fine this ways:
That's great This issue will be fixed in Publii 0.35.1