{"action":"reopened","issue":{"url":"https://api.github.com/repos/urandom/readeef/issues/11","repository_url":"https://api.github.com/repos/urandom/readeef","labels_url":"https://api.github.com/repos/urandom/readeef/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/urandom/readeef/issues/11/comments","events_url":"https://api.github.com/repos/urandom/readeef/issues/11/events","html_url":"https://github.com/urandom/readeef/issues/11","id":151253337,"number":11,"title":"Can't login","user":{"login":"klingtnet","id":1538057,"avatar_url":"https://avatars.githubusercontent.com/u/1538057?v=3","gravatar_id":"","url":"https://api.github.com/users/klingtnet","html_url":"https://github.com/klingtnet","followers_url":"https://api.github.com/users/klingtnet/followers","following_url":"https://api.github.com/users/klingtnet/following{/other_user}","gists_url":"https://api.github.com/users/klingtnet/gists{/gist_id}","starred_url":"https://api.github.com/users/klingtnet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/klingtnet/subscriptions","organizations_url":"https://api.github.com/users/klingtnet/orgs","repos_url":"https://api.github.com/users/klingtnet/repos","events_url":"https://api.github.com/users/klingtnet/events{/privacy}","received_events_url":"https://api.github.com/users/klingtnet/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/urandom/readeef/labels/bug","name":"bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-04-26T22:21:15Z","updated_at":"2016-04-27T12:30:10Z","closed_at":null,"body":"I can't login into readeef because of the following error:\r\n`Error: \"Error writing session data: mkdir /usr/bin/session: permission denied\", type: ` (The whole error message wasn't shown in the login screens error popup)\r\n\r\nI'm using `readeef 1.1.0` on Arch Linux. `readeef` is started through systemd with a custom user that, obviously, has no write permission for `/usr/bin` where the executable is located. I'm not sure but it was possible to set the session dir in some previous version."}}