5

Yesterday I installed MegaSync with the Nautilus extension and when I restarted the computer (running Ubuntu Desktop 15.04) the MegaSync app doesn't start at all.

I tried running megasync in the terminal and nothing, System Monitor does not see MegaSync running. What can I do?

user.dz
  • 47,137
  • 13
  • 140
  • 258
J. Doe
  • 53
  • 1
  • 4
  • What does exactly "nothing" mean? No output and goes back to the input line? Or it does not return to the line? Can you also post the output of `ps axu | grep megasync`? – dadexix86 Aug 31 '15 at 07:35
  • Nothing means that MegaSync doesn't start, I type in the terminal megasync and the machine automatically gives me back the command line. – J. Doe Aug 31 '15 at 14:50
  • $ ps axu | grep megasync fer 14427 0.0 0.1 5756 1980 pts/3 S+ 15:52 0:00 grep --color=auto megasync That is what Terminal gives me back. – J. Doe Aug 31 '15 at 14:52
  • Use Pastebin and post the output of `strace megasync`. – dadexix86 Aug 31 '15 at 17:15
  • http://pastebin.com/XgpxWX1k Thanks for the help :) – J. Doe Aug 31 '15 at 18:15
  • Post `ls -l "/home/fer/.local/share/data/Mega Limited/MEGAsync/megasync.lock"` – dadexix86 Aug 31 '15 at 18:38
  • fer@fer-S6FM:~$ ls -l "/home/fer/.local/share/data/Mega Limited/MEGAsync/megasync.lock" -rw-r--r-- 1 root root 0 ago 31 02:21 /home/fer/.local/share/data/Mega Limited/MEGAsync/megasync.lock fer@fer-S6FM:~$ sudo ls -l "/home/fer/.local/share/data/Mega Limited/MEGAsync/megasync.lock" [sudo] password for fer: -rw-r--r-- 1 root root 0 ago 31 02:21 /home/fer/.local/share/data/Mega Limited/MEGAsync/megasync.lock fer@fer-S6FM:~$ – J. Doe Sep 01 '15 at 21:07
  • 1
    Why "`sudo`"? Typing random command in your CLI can result in **serious** damage. Avoid typing commands if you don't know what they do and no one tells you so (and clearly you don't know what `ls` does, otherwise you would not have done it with `sudo`). BTW the problem is that that file is owned by `root`. Is not the case that you tried to run Mega with `sudo`, right?... – dadexix86 Sep 01 '15 at 22:21
  • 1
    Running programs with `sudo`, especially graphical programs, may lead to some major problems like this (wrong ownership of files, that might result in you not being able to log into your system *at all*!). If you really can't avoid messing around with higher privileges on your system, at least use `gksudo` to launch graphical programs. – dadexix86 Sep 01 '15 at 22:23
  • Just want to point the origin of your issue: initially you started MEGAsync as a root user (at this point it created directories and files using root as an owner) and then you try to launch MEGAsync as a normal user. – Paul Oct 08 '15 at 16:37

2 Answers2

7

The answer of dadexix86 doesn't work all the time. At first, I did what he proposed and it worked.

But later on, when the issue reappeared, I found that I had to delete/rename the megasync.lock file inside "~/.local/share/data/Mega Limited/MEGAsync/":

Doing that, it worked like a charm.

Pablo Bianchi
  • 14,308
  • 4
  • 74
  • 117
milia
  • 171
  • 2
  • 5
4

The problem is a wrong ownership of some files in the home directory.

Acquire again the property of all the files in that directory via

sudo chown -R $USER:$USER "/home/$USER/.local/share/data/Mega Limited"

Where $USER is an environment variable with your current username.

Pablo Bianchi
  • 14,308
  • 4
  • 74
  • 117
dadexix86
  • 6,596
  • 2
  • 39
  • 113