For some strange reason Canola2 b8 was running fine before I ran Canola2 Cleanup which brought up a strange bug on my end. While I cannot figure out why b8 won't run for me upon a fresh install (missing dependency - I'll run -vv and whatever other options and report back later) I did come across this very peculiar (and reproducible) oddity. If this has been reported already then forgive me.

A while ago I installed Xournal but for some reason couldn't get it to update through the app manager. it would download but couldn't install the update for whatever reason and I forgot about it. When I recently ran Canola2 Cleanup, it (predictably) hosed the most recent Canola2 beta8 install which was working nicely BUT in the process of finishing up it executed and caused failed Xournal install to successfully install (weird, right?).

To reproduce this I tried from scratch, uninstalled Canola2 and Xournal and rebooted. First grabbed Canola2 again, rebooted. Launched Canola2 which doesn't start so then I grabbed Xournal (which downloads but fails to install), rebooted again for the fun of it.

NOW the fun part. Grabbed Canola2 Cleanup and ran it, it runs through it's processes and about half way through a dialog pops up asking where I want to put Xournal in the applications menu...

I think we have a collision here.