(appstreamcli:22616): GLib-DEBUG: 14:07:53.742: posix_spawn avoided (fd close requested) (appstreamcli:22616): GLib-DEBUG: 14:07:53.738: posix_spawn avoided (fd close requested) (appstreamcli:22616): GLib-DEBUG: 14:07:53.733: posix_spawn avoided (fd close requested) ** (appstreamcli:22616): DEBUG: 14:07:53.621: Added /var/lib/app-info/yaml to YAML metadata search path. ** (appstreamcli:22616): DEBUG: 14:07:53.621: Added /usr/share/app-info/xmls to XML metadata search path. service filesĭernière modification par Debian Alain (25-12-2019 19:54:15) service filesġ7:18:27:0839 Gs not handling error not-supported for action get-updates-historical: The name was not provided by any. service filesġ7:18:27:0838 Gs not handling error failed for action refresh: The name was not provided by any. Most of this information was taken from the Flatpak wiki.17:18:27:0703 Gs plugin appstream took 2,0 seconds to do setupġ7:18:27:0706 Gs enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, shell-extensions, appstream, desktop-menu-path, hardcoded-blacklist, hardcoded-featured, hardcoded-popular, modalias, odrs, packagekit-refine, rewrite-resource, steam, packagekit-history, provenance, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadataġ7:18:27:0706 Gs disabled plugins: dpkg, dummy, repos, epiphanyġ7:18:27:0778 Gs not GsPlugin error FwupdError:10: The name was not provided by any. So, for the most useful stacktraces, make sure that you have the Debug extensions for the apps and runtimes in question installed. When you use the –devel option, flatpak automatically includes the Debug extensions for the application and runtime, if they are available. So the debug info for is in the extension. Flatpak does something similar and splits all the debug information of runtimes and apps into separate ”runtime extensions”, which by convention have. In rpm-based distributions, the debug symbols are split off into debuginfo packages. Now for the last trick: I was complaining about stacktraces without symbols at the beginning. The –devel option tells flatpak to use the sdk instead of the runtime and do some other things that make debugging in the sandbox work. And flatpak has a handy commandline option to use the sdk instead of the regular runtime: flatpak run -devel -command=sh Thankfully, for each runtime, there is a corresponding sdk, which is just like the runtime, except it includes the stuff you need to develop and debug: headers, compilers, debuggers and other useful tools. Remember that we are inside the sandbox, so we can only run what is either shipped with the app in /app/bin or with the runtime in /usr/bin. This is great, because we can now launch our app under gdb (note that the application gets installed in the /app prefix): $ gdb /app/bin/recipesĮxcept… this fails because there is no gdb. Running this command, you’ll end up with a shell prompt ”inside” the recipes sandbox. Here is how you do that: flatpak run -command=sh What happens behind the scenes here is that flatpak finds the metadata for, determines which runtime it needs, sets up the sandbox by mounting the app in /app and the runtime in /usr, does some more sandboxy stuff, and eventually launches the app.įirst problem for bug reporting: we want to run the app under gdb to get a stacktrace when it crashes. But lets assume you’re launching flatpak from the commandline. Well, that’s not quite true the ”normal” way to launch the Flatpak is just the same as launching a non-Flatpak app: click on the icon, or hit the Super key, type recipes, hit Enter. Normally, you run your Flatpak app like this: flatpak run This post is a quick attempt to spread some basics about Flatpak debugging. But how does one create a useful bug report when something goes wrong in a Flatpak sandbox ? Some of the stacktraces I’ve seen have not been very useful, since they are lacking symbols. Since I’ve been asking people to try the recipes app with Flatpak, I can’t complain too much if I get bug reports back.
0 Comments
Leave a Reply. |