Vladimir, The ContainersConfig.json found in "/custom/click/.click/users/@all/com.ubuntu.puritine/libertine- config/libertine" is the copy that "ships" with the click and should not affect any functionality after a fresh install of the image. I'm surprised to see that article suggesting a "copy/paste" situation as that's not necessary - libertine-container-manager will take care of that for you. Since Puritine did not update, your original ContainersConfig.json should have still been in-tact. There were dependency issues preventing the scope from showing any results for the last couple of weeks, but those were resolved with the OTA-13 release.
If everything is working and your puritine apps are showing up in the scope, you should just be able to use the libertine-container-manager to start creating containers and installing apps again. If you want to delete your old container, you'll probably need to do a raw `rm -rf $HOME/.cache/libertine-container/my-container/`. I do not recommend using `rm` to manage libertine containers in normal scenarios, but this is a special situation. As for all the apps that don't quite work, I'm sorry to hear that. You can often find some of the libertine developers and enthusiasts on #ubuntu-libertine on freenode irc, but it's a pretty small group so you might not be able to find help at all hours of the day. You could also ask questions on AskUbuntu to broaden the audience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626180 Title: Desktop Apps scope hangs unity8-dash To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
