GPX export (GoPro) failed with exit code 127

Hello,

according to https://forum.shotcut.org/t/gps-text-video-filter/29278 , I wanted to try out the GPX export feature for my GoPro Videos (instead of using exiftool -p gpx.fmt -ee video.MP4 > gpx_output.gpx)

When I click on export to gpx in the hamburger menu it immediately fails. The only log it displays is “Failed with exit code 127”.

This error appears on all my (GoPro) videos I tested it. The exiftool command from above works and I can also import and work with the gpx files. I’m just curious why this won’t work within the Shotcut Workflow.

Any Suggestions? Thanks in advance.

Not to forget to mention: “export to GPX” integrated in Shotcut is a great feature!

Additional Information:

  • OS: Fedora 43 (GNOME)
  • CPU: AMD Ryzen 7 7840U
  • Shotcut Version: 25.10.31
  • Shotcut Installation: GNOME Software as RPM

That is probably the reason. Shotcut runs a companion executable named gopro2gpx that is very unlikely available in Fedora as a runtime dependency. Moreover, for recent model GoPros, that project had to be forked and updated since it is no longer maintained. The builds we link to on our Download page includes this.

If you choose to build that yourself, Shotcut expects the gopro2gpx executable in the same dir as shotcut.

The bug you report is not something I will address further.

1 Like

just to confirm: yes the Flatpak solved it :slight_smile: thanks!

Just to check - my understanding is that using the flatpak rather than the .rpm will cause some features not to work because of the way it is sandboxed. Is that still correct?

Yes, the flatpak can only run things included in its flatpak bundle or its runtime (a base layer of many common user space libs plus a flavor such as KDE that includes Qt). The Shotcut flatpak includes many things it needs and builds itself such as this gopro2gpx utility, ffmpeg, glaxnimate, etc. However, it does not include whatever image editor you happen to prefer, for example.

1 Like