The "Open.." button in Openshot/Avidemux/VLC/QT-based apps doesn't work

• VLC-appimage

  7 22 8.4 Shell

  VLC Video and Media Player AppImages built from JuNest (Arch Linux) and PPA.

The other poster asked you to check so the file chooser window, the window that asks you what file to open which didn't appear for you when you pressed the "Open..." button, isn't just appearing behind the window of the program. This is in order to see if your issue is an already existing one or whether it's a potentially new one. Literally the same troubleshooting procedure you've asked people to do yourself in your own repositories: https://github.com/ivan-hc/VLC-AppImage/issues/1 https://github.com/ivan-hc/GIMP-AppImage/issues/1

• GIMP-appimage

  6 41 9.0 Shell

  GNU Image Manipulation Program Stable & Developer Edition built from PPAs and JuNest (Arch Linux). (by ivan-hc)

The other poster asked you to check so the file chooser window, the window that asks you what file to open which didn't appear for you when you pressed the "Open..." button, isn't just appearing behind the window of the program. This is in order to see if your issue is an already existing one or whether it's a potentially new one. Literally the same troubleshooting procedure you've asked people to do yourself in your own repositories: https://github.com/ivan-hc/VLC-AppImage/issues/1 https://github.com/ivan-hc/GIMP-AppImage/issues/1

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• AM

  76 318 9.9 Shell

  An "AUR-inspired" Database of AppImage packages and a CLI to manage/install/update them system-wide! This repo lists 1900+ standalone apps for GNU/Linux. You can extend it with custom repositories, create your own installation scripts and even build AppImages on the fly! "AM" Application Manager: Easy to use like APT and Powerful like PacMan!

this is not an issue related to the package format, Flatpak should work better than AppImage because it uses shared libraries among the other flatpaks installed, while AppImage has all its dependencies inside... I work a lot with AppImages and all of them have not the same problems I've faced in the Flatpak's counterpart (you can compare them using this project).

Suggest a related project