Open TheCrewman opened 6 years ago
You need to have MEGAsync running (and logged in IIRC) to avoid that warning. In any case, we will review the extension code to try to avoid that logging flooding. Thanks for reporting.
Just noticed this in my system logs going crazy. Ubuntu 18.04. Once logged in, it goes away, however it still spams in the period after logging in before a connection is established, especially on 4G tethering.
What about a delay to connect upon startup from auto start? That's not hard to implement. It would be convenient if there was some passive event you can just listen to rather than constantly trying to connect.
Thanks for explaining the source of this, it's been a source of concern since I've noticed this and could nott find the cause as the error message isn't very clear.
Hello, the issue persists and also affects Ubuntu 24.04.
I noticed that the MEGAsync extension for Nautilus, in my Fedora 27 workstation, fills my journalctl's logs. When I run journalctl, my logs are filled up (every second) by the following warning message: "nautilus[3178]: connect() failed". What do you think about this issue?