null directory and file variables crash ctags plugin

[Frank Claessen]

~$ pantheon-files
[INFO 08:06:56.104382] Application.vala:155: Files version: 0.3.0.4
[INFO 08:06:56.104443] Application.vala:157: Kernel version: 4.4.0-53-generic
[INFO 08:06:56.165708] Application.vala:83: Report any issues/bugs you might find to http://bugs.launchpad.net/pantheon-files
[WARNING 08:06:56.935906] plugin.vala:108: Color tag plugin consume knowns queue called with null directory
Segmentation fault (core dumped)

[Jeremy Wootten (jeremywootten)]

Thanks for the report Frank. If you can give more information about the circumstances in which the crash occurred it will enable us to find the root cause of the null directory file in the colour tagging polug in. As it is we can only stop the crash in the plugin if this happens but not cure any related bugs.

[Frank Claessen (f-a-n-claessen)]

Hi Jeremy,

I have a few confessions to make. I did a fresh install of EOS Loki and everything worked fine.
Then I looked for 2 things: a spotify-client and a dropbox-client, both not available out of the box for EOS.
So - I followed a link for the spotity-client (http://howtoelementaryos.org/how-to-install-spotify-in-elementary-os) which caused trouble in paradise since this repository turned out to be not authenticable. I removed it again.

Dropbox I managed to install through https://github.com/zant95/elementary-dropbox

I guess after all this trouble started.

So - this might be a bug caused by other problems. Hope this helps a bit.
I cannot help you by installing everthing fresh again.
If you need a debug - let me know. I can try that for sure

Regards Frank

[Jeremy Wootten (jeremywootten)]

Hi Frank,

Presumably you have the pantheon-files-plugin-dropbox installed? The color tags plugin does have trouble with some "non standard" folders - I have seen similar warnings when using an MTP device for example - although it doesnt usually crash. I guess all I can do for now is to add some more sanity checking to the color tag plugin.

[Frank Claessen (f-a-n-claessen)]

See screenshot nr 1 ...

[Frank Claessen (f-a-n-claessen)]

and screenshot nr 2 :)

Regards

Frank

[Frank Claessen (f-a-n-claessen)]

and yet another screenshot

Regards

Frank

[Jeremy Wootten (jeremywootten)]

Looks like you do not have it installed. I am not sure if it is in the stable repository - I am using the daily one.

[Frank Claessen (f-a-n-claessen)]

I did a test with the debug option.

Interesting!!

Without debugging I get the afore mentioned error
WITH debugging the app starts normal - no crash

See attachment for both results

Hope this helps

[Jeremy Wootten (jeremywootten)]

Looks like a race condition. The extra time taken to print the debug messages affects which process wins.