In Linux Mint's Cinnamon environment, many applications either don't work or only work partially -- Nobody can, for example, make Clipboard work (it just doesn't work), Copy Q (locks the clipboard, pastes but doesn't copy) Packages Appimage doesn't work at all; just to name the most common cases -- but nothing is as irritating as Diodon, which works, but after a while it doesn't start, and after we've struggled for a solution, it works for a few weeks, and then it stops. start again, and this keeps repeating itself with each repair, as if it were a Ruindows XP bug... Namely, at first, it does not start, or is unstable, closing at the same time it is opening. Running it in a terminal doesn't work, because when you close the terminal, it crashes. My first solution was to add the nohup command to Diodon's syntax ( sudo nohup diodon ), which fixed the problem for 2 weeks, causing the application to start stably, but then it stopped working, and worse, nohup stopped working also. Like everyone who has had problems with the diodon, I've tried sudo -- but of course that doesn't work for autostart, which doesn't support sudo, nor does creating a diodon group and registering it in sudoers; and starting Diodon manually every day is frustrating and irritating, but it worked, until it stopped working. So the next solution was to abandon nohup and use the screen command ( screen -d -m diodon ) and I sincerely recommend that, and include screen in Diodon's dependencies, since screen has to be installed. It worked well, and it still works. But after 2 months it stopped working too. Then I ran into a permissions problem in the application ( in /usr/share/applications/diodon.desktop ). All permissions were root, with no user permissions, and read-only, with no execute permissions -- a very common bug in apps installed on Mint, when written by developers with no knowledge or experience of Cinnammon : Cinnamon has one of the Stricter security policies (read: permissions) for applications, although it is no Sabayon. When installing a new application, it installs it only with the default Mint permissions, unless something else is clearly specified. You can't improvise with it. So much so that it has constant problems with git packages (read: most don't work anyway). I now have to start it manually with sudo, and I can't figure out where the startup bug is. But it appears that Diodon is not recognized as a user process, or at least not as a user process that can access root space. If I start exclusively as an administrator, it works without any problems. But if I log in as a user, or use automatic login (called "guest-user" in Ubuntu, where you can log in as an unspecified user) Diodon won't start, and I can't make myself available to users to start Diodon with sudo for them.
My only clue : When I say, Mint installs only with Mint's default permissions, unless something else is clearly specified, I mean something like specifying root access, even though it's a user session (the area Mint transfer, like all instances of Cinnamon , is considered root ).
Addition by the same author about the failure: I found that Diodon starts by autostart in Linux Mint, but it is necessary to run two consecutive launches: In the first one (screen -d -m diodon or sudo screen -d -m diodon ) nothing happens; in the second, finally, the application appears in the system tray. I don't know why two tries, but you can automate launching by autostart if you make two entries, 10 seconds apart (less than 5 doesn't work, more than 10 seconds, other processes in autstart can break the stream -- by " stream" I say the "2 times in a row" as it's almost like it was ) So, to ensure two init calls in a row, I've successfully built 2 entries 10 seconds apart. Making a single call like "screen -d -m dion & screen -d -m dion" does not work. It's definitely a bug, and in any case, you shouldn't need the screen or nohup command. That's it.