A JavaScript error occurred in the main process about zettlr

[nathanlesage]

I'm afraid not. Just the one. And it happens whichever directory I open. I even created a new directory in the app with one file in it, and when I opened it this error still fired.

So it indeed seems that it's some hiccup inside chokidar. Well, the package has had its problems. I'll look into possible alternatives once I finish some other work! But I may have an idea to catch the error to alleviate your pain (and that of others experiencing the same problem) until I find a viable solution!

I should have said that after dismissing each error by pressing "Ok", the app works fine.

Understandably — the only thing is that it then doesn't watch your directory for remote changes.

I'll get back to you once I manage to find something!

P.S.: To all others, please share your ENOSPC errors, in case you encounter them. Just for me to get a picture of how many linux OS's are actually affected.

[nathanlesage]

Hey,

I start to really dislike watching files using chokidar …

So the most obvious follow-up questions would be: Are there a lot (and I mean: A LOT) files in this directory? I suppose not, but just for clarification.

And then: Are there some strange chmod-settings on any of the files? (If your user account does not have read-permissions on a file, it may fail in this way, although this more likely results in an EPERM-error …)

Or any other idea that might point towards it?

Cheers!

[jacklenox]

Hey Nathan, thank you for the quick response! Haha, I haven't dug into it too much myself yet.

Are there *a lot* (and I mean: A LOT) files in this directory? I suppose not, but just for clarification.

I'm afraid not. Just the one. And it happens whichever directory I open. I even created a new directory in the app with one file in it, and when I opened it this error still fired.

Are there some strange chmod-settings on any of the files?

I don't think so. Just in my regular user directory, with standard permissions. I'll have a deeper look later. I should have said that after dismissing each error by pressing "Ok", the app works fine. Great work, I love it! Cheers.

…

On Sat, 15 Sep 2018, 10:00 Nathan LeSage, ***@***.***> wrote: Hey, I start to really dislike watching files using chokidar … So the most obvious follow-up questions would be: Are there *a lot* (and I mean: A LOT) files in this directory? I suppose not, but just for clarification. And then: Are there some strange chmod-settings on any of the files? (If your user account does not have read-permissions on a file, it may fail in this way, although this more likely results in an EPERM-error …) Or any other idea that might point towards it? Cheers! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#34 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAt3dEh7SejyNWwEhyGXJnxF3lmeYtePks5ubLOTgaJpZM4WprDs> .

[scrxdn]

Hey there,
first of all: I am not running a plain Vanilla Ubuntu 18.04 LTS, but ElementaryOS - but this is basically a Ubuntu flavor with some extra elementary-repos, which shouldn't affect the situation.

For now I couldn't verify these errors. I tried opening/closing serveral folders/files and also opened/reopened Zettlr many times (Dev-Branch from Git and Zettlr 0.20.0).
I'll try both a Vanilla 18.04 LTS and a PopOS later, and we'll see.

Just in case: @jacklenox have you tried building Zettlr for popOS yourself? Is there any warning during build or whatever?

Thanks!

[scrxdn]

So, there we go:
Today I set up Ubuntu 18.04 LTS and the current Pop_OS! 18.10 release. Then I testet both the 0.20.0 .debs as well als the current develop branch on both systems.
I experienced some other strange things (which are off topic here) - but I was not able to reproduce or verify this issue at this time.

[jacklenox]

@escapedsalmon Apologies for the slow response. I actually didn't notice that this seemed to have fixed itself, but I have been happily using Zettlr without this error for the past month or so. It looks as though updating from Pop_OS 18.04 to 18.10 must have fixed this for me. I think that's the only notable thing I've done since I first reported this issue! Thank you for digging in.

[scrxdn]

@jacklenox This somehow fits into the pattern I expected. I assumed it might have to do with some security settings in AppArmor or some other security enhancements Ubuntu is using - but it was just a guess (knowing that SELinux is a common source of unknown and completely unrelated errors on Fedora).
Even though there's still a small chance @nathanlesage fixed the Bug in 0.20. without noticing it.

[nathanlesage]

@jacklenox Thanks a lot for the response!

As I did not touch the watchdog for months, I assume that @escapedsalmon is correct in stating that something in the security of your OS was not working correctly, which in turn prompted these errors.

But it's good to know it works now! :)