Variety fails to start/crashes on autostart, but not when started manually

[Ben Fox]

I have variety 0.6.3 that starts - or should start :) - when I log in to my desktop.
It crashes EVERY time.
I have Gnome3 on both my PCs, one with ubuntu 14.04 and this one from which I'm writing is freshly updated to 16.04.

Gnome reports Variety has crashed, and asks me to leave it closed or relaunch it: I always relaunch it and then it works fine.

I don't know how to do the -v thing you ask here in the bottom to create a log file, because I don't know where to put it to make it work at login (and if I start variety by hand, it works fine).

thanks a lot
I really like variety and I will continue to click "relaunch" without being annoyed by that; just wanted to let you know.

cheers!

Bernardo from Firenze

[magix (mw99)]

Same here on Ubuntu 16.04 (Unity) and Variety 0.6.3 installed from the official PPA.

I added the -v to the startup entry, but had some trouble with the log getting messed up. I could give it another go if requested.

Sometimes Ubuntu will pop up an error message about it, and sometimes not, but 90% of the time Variety does not launch correctly on startup and I have to launch it manually.

[James Lu (jlu5)]

What do you mean by messed up? Does the file ~/.config/variety/variety.log not exist?

[magix (mw99)]

It somehow got corrupted and just showed a bunch of 0s when opened in a text editor.

Anyway, I gave it another shot and got the log this time.
I set the startup entry to use the -v flag and rebooted.

Variety did not launch, and Ubuntu didn't show any error messages:

[magix (mw99)]

Any update on this? It still occurs at almost every startup.

[James Lu (jlu5)]

I'll try to take a closer look with GNOME and Unity specifically in the coming days. The log doesn't give any information about an error, which means that something is probably causing python/Variety to crash entirely.

This might be the same issue as https://bugs.launchpad.net/variety/+bug/1558605, but I haven't been able to reproduce that either yet.

[magix (mw99)]

In reference to the similar report you linked to, I'm also using an external monitor connected via my laptop's HDMI port, so perhaps that has something to do with it.