"Open in Player" failure on Ubuntu MATE 17.04 vs Ubuntu MATE 17.10 regression Picard v 1.3.2(17.04) vs 1.4.2(17.10)

Tags: #<Tag:0x00007f2a0b6d7798> #<Tag:0x00007f2a0b6d7630> #<Tag:0x00007f2a0b6d74f0> #<Tag:0x00007f2a0b6d7360> #<Tag:0x00007f2a0b6d71a8> #<Tag:0x00007f2a0b6d7018>


On Ubuntu 17.04 I apparently had version 1.3.2 of Picard. Now I have Picard 1.4.2 on Ubuntu 17.10.

I’ve seen ticket PICARD-692 and PICARD-315 but Ι don’t see they addressing my issue of “Play File” working on my Picard 1.3.2 Ubuntu 17.04 but not on my upgraded system 17.10 with Picard 1.4.2…

and now in Ubuntu 17.10 Picard 1.4.2 with “Open in Player” doesn’t launch my ‘totem’ app as it used to.

Is this new version of Picard 1.4.2 based on Unity or does it read some obscure app preference somewhere that I’m not aware of yet? Thanks for developing this app and honestly I don’t care if this stays regressed as I’m happy with the program for all other functions. Thank you!


Does a different application launch and plays the file?

If you open the command line on Ubuntu 17.10, navigate to the file and do xdg-open <filename> and gnome-open <filename>, does any of them launch totem?


Thank you very much for that reply. All I needed was a hint. What I’m doing now is to search for how I can follow the xdg standard in my desktop environment. Thanks for your reply.

Also I see I made an error in how I described these systems as Ubuntu 17.04 and 17.10 instead of Ubuntu MATE 17.04 and 17.10. I use Ubuntu MATE 17.10 which I upgraded from Ubuntu MATE 17.04.