{"action":"created","issue":{"url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/416","repository_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy","labels_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/416/labels{/name}","comments_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/416/comments","events_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/416/events","html_url":"https://github.com/jedisct1/dnscrypt-proxy/issues/416","id":156624650,"number":416,"title":"Installation problems in Ubuntu 16.04","user":{"login":"rowyourboat","id":19560231,"avatar_url":"https://avatars.githubusercontent.com/u/19560231?v=3","gravatar_id":"","url":"https://api.github.com/users/rowyourboat","html_url":"https://github.com/rowyourboat","followers_url":"https://api.github.com/users/rowyourboat/followers","following_url":"https://api.github.com/users/rowyourboat/following{/other_user}","gists_url":"https://api.github.com/users/rowyourboat/gists{/gist_id}","starred_url":"https://api.github.com/users/rowyourboat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rowyourboat/subscriptions","organizations_url":"https://api.github.com/users/rowyourboat/orgs","repos_url":"https://api.github.com/users/rowyourboat/repos","events_url":"https://api.github.com/users/rowyourboat/events{/privacy}","received_events_url":"https://api.github.com/users/rowyourboat/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-05-24T22:32:48Z","updated_at":"2016-05-24T22:53:51Z","closed_at":null,"body":"This may hurt some feelings, but it needs to be said\r\n\r\nI just did a fresh install of Ubuntu 16.04. I installed dnscrypt-proxy via Synaptic Package Manager, and the installation failed with errors:\r\n\"E: dnscrypt-proxy: subprocess installed post-installation script returned error exit status 1\"\r\nIt tried to submit it's crash report, but all internet access failed. I had to uninstall the package to get Internet access back. I tried again, same result.\r\n\r\nAs a linux newbie, this concerned me. I really want DNScrypt, but it doesn't even work out of the box.\r\nI tried again, this time looking at the install log.\r\n\r\nThe install details log suggests looking at:\r\nsystemctl status dnscrypt-proxy.service and journalctl -xe, so I did. It appears it's trying to use cisco as the server, and can't get the certificates, so the service shuts down, starts up, and tries again. Meanwhile Internet access on the machine is broken. Eventually I got it to work by pointing it to soltysiak.\r\n\r\nWonderful, I got it to work.  However, the point needs to be made, this makes the project look bad, and this is the kind of thing that makes people go back to Windows or Mac. Many people agree with the philosophy of Linux.  They like it a lot, but they can't use it. When they try to make the switch, they have to put their lives on hold to fuck around with all the unfinished buggy crap they run into as soon as they try to get started. Soon, they give up, and go back to Windows, as in my case.\r\n\r\nLinux is very important to the computing world.  I love Linux, but I end up banging my head against the wall every time I try to switch. However, with the recent developments in the Windows OS, I'm determined to make it work this time.  I only learned of DNScrypt a few days ago, and now that I know about it, I consider it a critical piece of software for the future of secure computing.  This is something that everyone in the world should have running on their computer and phone.  If that's ever going to happen, it needs to JUST WORK as they say. It can be done.\r\n\r\nMy specific suggestion at this time is, when DNScrypt is preparing to install, gathering the dependencies, it also downloads the latest dnscrypt-resolvers.csv. That is basic and obvious, and it should be easy to implement.  Next, the program should test the resolvers until it finds one that works, before completing the install. You can have it select them at random if you like, until it finds one that works. In fact, it should do this check every time the service starts. By default. Simplicity for the users, guys.\r\nThis basic check will bring a lot more legitimacy to the project, and less headbanging will bring more people to Linux and keep them there. People with lives, and/or not in IT, are not going to open a terminal. And they should never have to.\r\nThanks for listening.  Sorry for the rant, but I'm on your side. I hope to see this implemented.\r\n\r\nI also log fairly thoroughly my steps when I install an operating system.  I always end up reusing them later on when I want a fresh install, so that I can complete them very quickly without forgetting anything, and I can avoid problems I have run into in previous builds.  I volunteer my newbie-proof DNScrypt install notes for 16.04, once I have it up and running.  I would like to see it on the DNScrypt webpage.  Many websites I went to for instructions had me doing all kinds of crazy stuff in the command line, but I just eventually found in sitting there in the Synaptic package manager. I would like to make sure anyone coming in behind me finds it right where they need it and have it up and running in a few minutes (like you can in Windows), versus fucking around all day with out-of-date methods.\r\n\r\n<bountysource-plugin>\r\n---\r\nWant to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/34543483-installation-problems-in-ubuntu-16-04?utm_campaign=plugin&utm_content=tracker%2F417785&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F417785&utm_medium=issues&utm_source=github).\r\n</bountysource-plugin>"},"comment":{"url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/comments/221426123","html_url":"https://github.com/jedisct1/dnscrypt-proxy/issues/416#issuecomment-221426123","issue_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/416","id":221426123,"user":{"login":"rowyourboat","id":19560231,"avatar_url":"https://avatars.githubusercontent.com/u/19560231?v=3","gravatar_id":"","url":"https://api.github.com/users/rowyourboat","html_url":"https://github.com/rowyourboat","followers_url":"https://api.github.com/users/rowyourboat/followers","following_url":"https://api.github.com/users/rowyourboat/following{/other_user}","gists_url":"https://api.github.com/users/rowyourboat/gists{/gist_id}","starred_url":"https://api.github.com/users/rowyourboat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rowyourboat/subscriptions","organizations_url":"https://api.github.com/users/rowyourboat/orgs","repos_url":"https://api.github.com/users/rowyourboat/repos","events_url":"https://api.github.com/users/rowyourboat/events{/privacy}","received_events_url":"https://api.github.com/users/rowyourboat/received_events","type":"User","site_admin":false},"created_at":"2016-05-24T22:53:50Z","updated_at":"2016-05-24T22:53:50Z","body":"OK, I will resubmit without rant.  However, this isn't just about the package, this is about the core functionality of dnscrypt-proxy, isn't it? I would have the same problem if installed through another method other than synaptic, and if I had done it on Fedora or something else."}}
{"actor":{"display_login":"rowyourboat"}}