DaviMG07
commented
6 months ago I saw a similar issue on flutter github here. Using Flatseal, I exported the variable export LIBGL_ALWAYS_SOFTWARE=1. At least it shows the application now, but it's still not running as expected.
A comparison between how flatseal and appimagepool are being displayed. the app doesn't follow the desktop theme, nor the size:
Running from terminal I got that:
flutter: PathNotFoundException: Cannot open file, path = '/var/home/davi/.var/app/io.github.prateekmedia.appimagepool/config/dconf/user' (OS Error: No such file or directory, errno = 2)
flutter: Unsupported operation: Unsupported clipPath child g
flutter: #0 debugPrintStack (package:flutter/src/foundation/assertions.dart:1209)
flutter: #1 FlutterError.dumpErrorToConsole (package:flutter/src/foundation/assertions.dart:1028)
flutter: #2 FlutterError.reportError (package:flutter/src/foundation/assertions.dart:1189)
flutter: #3 _Elements.clipPath (package:flutter_svg/src/svg/parser_state.dart:491)
flutter: #4 SvgParserState.parse (package:flutter_svg/src/svg/parser_state.dart:887)
flutter:
I tried running both the Flatpak and AppImage versions of the application, but it only displays a blank page. I'm getting these errors:
(appimagepool:4264): WARNING : 18:02:02.085: Failed to start Flutter renderer: Unable to create a GL context
(appimagepool:4264): WARNING : 18:02:03.948: Unable to retrieve framework response: No engine to send to
(appimagepool:4264): WARNING : 18:02:03.972: Unable to retrieve framework response: No engine to send to