Kubuntu KDE autostart did not show tray icon

Bugs and issues Linux
#1

I believe it is connected to the fact it is creating a reboot cronjob to act as an autostart:

romulo@rbenedettiN:~$ insync -v
1.2.13.35166
romulo@rbenedettiN:~$ crontab -u romulo -l

@reboot insync-headless start >/dev/null 2>&1

I wasn’t able to remove autostar through insync GUI. And so it avoid any attempt to restart it, without quitting the cronjob started one.

Why don’t you guys use the rc.d appropriated level (as insync appears to be a service), or so, any xdg autostart folder? Those two are very global autostart points in Linux.

Thanks the attention.

Update 1:

Ok… I found a (dirty) workaround, I removed old cronjob and add another one to run a script with:

sleep 6

export DISPLAY=:0
insync start

I’m pretty sure it have something to do with session variables…

Update 2:

romulo@rbenedettiN:~/.local/bin$ sysv-rc-conf --list | grep cron
anacron      2:on       3:on    4:on    5:on
cron         2:on       3:on    4:on    5:on

Ok the problem is much probably the fact Cronjob run @reboot jobs in level 2 of init (which moreover is neither a suitable console mode :worried: what can explain no variables presence too). As pointed, I’m pretty sure using init level 5 will make sure In-sync start at correct boot time :smile: .

Insync not working
#2

@Romulo_Benedetti The crontab entry is for insync-headless. For insync with GUI it adds an entry in ~/.config/autostart, which should be enabled in your case. Please check it out.

#3

Ah, thanks, but:

  1. why it created a cronjob if I always used the GUI insync? Does any attempt to start headless in-sync results in automatic cronjob creation?
  2. It is confusing:
  • interface give no clue, isn’t aware of headless interference.
  • interference restart can’t take control of situation (remove cronjob, advise, ?).
  • both process have same name and only statement in terminal is that insync is “trying to open again”.

So I believe it is somewhat confusing :confused:

#4
  1. In the current implementation if you installed the insync-headless package and ran insync-headless for the first time it would add an entry to your crontab. I’m not sure why it added one in your case, perhaps you tried the insync-headless package before?
  2. I agree that this could be improved, we’ll work on it when we have time.