[12:57] <dob1> hi, running skanlite I get this error https://dpaste.org/ubkRn
[13:32] <ogra_> dob1, thats crlarly a packaging bug ... seems their snapcraft.yaml has a layout that breaks /etc (by overmounting it with their own from the snap) so /etc/machine-id (which is usually populated into the snap env) from the host can not be found 
[13:33] <ogra_> dob1, file it by looking at the contact line in snap info skanlite ... 
[13:34] <dob1> ogra_: hi, it can depends by the fact that I don't use gnome?
[13:34] <ogra_> no
[13:35] <dob1> ok
[13:36] <ogra_> dob1, the issue is here: https://github.com/KDE/skanlite/blob/release/23.08/snapcraft.yaml#L74
[13:36] <ogra_> thats fatal ... 
[13:37] <dob1> can I open an issue on github for it?
[13:37] <dob1> ah they disabled issues
[13:37] <ogra_> (i assume they do that to get sane.d configs in place .... but instead of binding the /etc/sane.d dirs they just overwrite all of /etc)
[13:38] <ogra_> right, check snap info for the package, it has a bug link in "contact:"
[13:38] <dob1> ok I just to understand
[13:38] <dob1> ops
[13:38] <dob1> ok but just to understand
[13:38] <dob1> this is a fatal bug right?
[13:38] <dob1> have they tried to run it once?
[13:38] <ogra_> yes, i doubt it will run for anyone 
[13:38] <ogra_> no idea, i dont know them 🙂
[13:39] <dob1> it's a bit bad
[13:39] <ogra_> i just took a look at the package and it is clearly packaged buggy 
[13:39] <dob1> that they didn't try
[13:39] <ogra_> dunno if they tried ... perhaps they did but in a hacked up test env or some such
[13:39] <dob1> ok it can be
[13:40] <ogra_> either way, they should only bind the subdirs they need and not all of etc ...  then it should be fine