Which channel did you use for snapweb? It could be that edge, per example, is broken.
Try a snap list to see if it’s enabled.
Type journalctl -xe to see if the service did start properly
No, because the .htaccess file is injected inside our Apache config instead of being read at runtime in order to improve performance. Since this is the only use-case I found for making that file read-write, I think the best option is to just enable pretty-urls by default.
I haven’t opened an issue about that yet, so feel free to do it
10.0.1 is being tested right now. There is a snap you can download, but that won’t tell you if the migration is successful. It would be a new instance of NC.
Best thing to do wold be to load a VM with snapd on it, install NC9 from the command line, load some data and then upgrade with that snap.
In the future, it should be easier to test these upgrades by placing a lot of test data in the /media folder.
I’ve tried to run the snap manually, and this is what I see:
ubuntu@ubuntu-standard:~$ sudo snap run snapweb
runtime: this CPU has no floating point hardware, so it cannot run
this GOARM=6 binary. Recompile using GOARM=5.
Aargh… yes. I did completely forget about that. Thanks for the shell output.
Snapd is broken on ARM since last week. I wasted hours trying to figure out why and trying to find a workaround and that’s one reason I didn’t push any new snaps or releases.
Any snap you install will not run.
There is a workaround if you’re interested. It works because we’re not on Ubuntu Core yet.
Well, I’m not sure it’s that safe to tell everyone to follow these steps. I’m hoping to get a better answer from Canonical, but it may be that we simply have to wait for the fixes to get pushed.
Trying to install new snaps is not going to break anything, but it will be frustrating for new users since new snap installation on the Box has been promoted a lot by Canonical.
oh wow, I now know why stuff started breaking on reinstalling snaps, any word on having images to reflash the card, I’ve been waiting for a reliable start over point before doing any messing around with the device, oh wait just saw your github link - so you can do a clean install with the SD card? nice!
Is anyone else suffering with a super slow interface? I’ve uploaded now around 17GB of data, 16 of that images and I could brew a tea between clicking on an image and waiting for it to load up.
Similarly log in and general navigation seems so slow. Coming from a hex-core 3.5GHz-backed container I was expecting a less snappy (see what I did there? Snappy? Har har) system, but this is like watching paint dry.
Thanks for bringing this to our attention! The new wd.com website shop went live and apparently there are some issues…
Will post here once the store is back online.
