Porteus

No check if we are out of disk space in the process of saving the todays system-changes to folder "modules",

Result is 2 bad tings:

a script will hang, so the save session eat up 50-99% CPU and that will never finish/end it self, even after psc is closed.
("killall save-session" , is that the correct way to stop it? Or loose all active work when you do a ctrl+alt+backspace, but that will stop the cpu hogging)


But it also say "module ready!", ....even when nothing was actually written to disk (flash).
And no one knows that it is *not* there.
So if you dont look in the folder and not spot that the last changes are not there when it says "ready", then you will loose all work? Danger!

Bump!

francois wrote:Bump!

:-)
it is probably not critical,

but the glibc -bug, and flash & updated firefox module, I wold say that have high prio now

for example new linux-users that build a New iso in the configurator, they should not have insecure setup at start. Right?

How can we help?
(yes, the problem with trust is there for important security base-modules, so it might be hard to actually do something as help?)

Noted. Will add it to my todo list. Thanks for tagging it.