Dima Krasner
Dima Krasner
This could be a race condition, reproduces 10/10 times here on a fast laptop.
> Obvious question, what has changed since https://github.com/puppylinux-woof-CE/woof-CE/pull/2080? Time > Maybe there needs to be a dicussion about which files are considered as appropriate to be persistent. I don't see...
> The difficulty is in identifying it. The easiest way to identify it is to align Puppy with all other distros by making /run a tmpfs, and wait 😸
Is the woof-CE tree used to build F96 available anywhere?
Word of caution: at some point I tried to remove the `--no-check-certificate` in https://github.com/puppylinux-woof-CE/woof-CE/blob/38e2eaf135598b2a8f48d1e0955f6955f069c566/woof-code/support/download_file.sh#L32, but it looks like in some cases, woof-CE uses HTTPS URLs with broken certificates.
AFAIK git:// is plaintext too
> I'm also researching the possibility of building a Puppy distribution from user's local sources, so it could be built without active Internet connection. If you use file:// URLs, it...
> But these days Puppy is also running on Wayland... ? Yes, xrandr won't work.
xdpyinfo won't work in a Puppy that uses Wayland. Make sure you have some fallback if xdpyinfo fails (or if it's missing).
@TDFKAOlli I used Valgrind and `-fsanitize=address`. I can help with conflict resolution and code review, if needed.