New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config Directory can not be created #2203
Comments
How did you start geany? |
Ummm, it wouldn't be the piece of crossed out text in the background would it? |
yes, same thing happens if you start over the UI |
Could you start Geany with Based on the output above, it might be the symlink creation which fails: on startup, Geany creates a Unix domain socket in |
Yes but that doesn't happen until after the config creation and the dialog shown has returned, so thats why I was asking if the background message is actually relevant. |
nbeerli@galaxy3: ~/.config/geany nbeerli@galaxy3:~$ ls -la no geany* in /tmp |
This is your problem. Did you tried to start Geany as root (e.g. with To solve your problem: make sure your user can write to his own configuration directory. How to do that depends on the output of the ls command above. |
when I run sudo geany it works, no popup. I use geany since a while. I just checked ls -all shows root:root on the geany folder. |
one other thing. Installing geany from "Ubuntu Software Center" will not work at all. But from the cmdline it worked but with above flaw. Hope this helps to make the install better. |
No, the "install script" doesn't touch anything in your $HOME directory. The reason is probably because you ran Geany as root. To solve your problem: No idea why the installation won't work with the Ubuntu Software Center. We cannot provide support for distribution specifc problems. This is unrelated to Geany. |
The install script would not touch your config directory, as @eht16 asked, did you ever run Geany with sudo? This project doesn't make the packages for the software centre, thats Ubuntus work. |
No description provided.
The text was updated successfully, but these errors were encountered: