Skip to content
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

New Document does not work #559

Closed
rasmus91 opened this issue Oct 30, 2018 · 3 comments
Closed

New Document does not work #559

rasmus91 opened this issue Oct 30, 2018 · 3 comments

Comments

@rasmus91
Copy link

rasmus91 commented Oct 30, 2018

If i use the plank context menu to create a new document, the app opens and displays the attached error, and the tabs line is not displayed. If i click the 'plus' icon in the tabs, after opening a folder, nothing happens. So the only way i can type in new documents is by creating an empty file in the folder pane.

The text in the error says: 'The File "<b>(null>)</b>" can not be opened. It is an "unknown" filetype.'
skaermbillede fra 2018-10-30 12-32-07


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@rasmus91
Copy link
Author

rasmus91 commented Nov 3, 2018

I experimented with this on my Desktop computer as well, There, i can simply not replicate the issue.

@rasmus91
Copy link
Author

rasmus91 commented Nov 12, 2018

I did:

io.elementary.code from the commandline to see the errors, when i click the new tab, or do ctrl+n, i get

[FATAL 13:19:04.647999] DocumentView.vala:149: Fejl ved åbning af filen “/home/user/.local/share/io.elementary.code/unsaved/Tekstfil fra 2018-11-12 13:19:04”: Adgang nægtet Which basically means 'Error openeing access denied'

Checking out the ~/.local/share/io.elementary.code i can see that it's owned by root for some reason...

So, solved, i guess, by doing: sudo chown user ~/.local/share/io.elementary.code -R though, I'm not very fond of not knowing why this happened. Perhaps it was after i did sudo io.elementary.code somefile at some point. But I'm not certain.

@davidmhewitt
Copy link
Member

This sounds like a duplicate of #202 then.

It wouldn't have been possible for that folder to become owned as root without something running as root taking ownership of it (which was more than likely Code itself).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants