#0 g_logv
(log_domain=0x7f5e3982300e "GLib", log_level=G_LOG_LEVEL_CRITICAL, format=<optimized out>, args=<optimized out>)
at ../../../glib/gmessages.c:1417
#1 0x00007f5e397d678f in g_log (log_domain=<optimized out>, log_level=<optimized out>, format=<optimized out>)
at ../../../glib/gmessages.c:1455
#2 0x00007f5e3a1af451 in as_component_search_matches
(cpt=cpt@entry=0x55cc24af1200 [AsComponent], term=term@entry=0x7ffc50fcf003 "org.test.Hello")
at ../src/as-component.c:2942
#3 0x000055cc22a57ddd in flatpak_builtin_search
(argc=<optimized out>, argv=<optimized out>, cancellable=<optimized out>, error=<optimized out>)
at /home/smcv/src/flatpak/app/flatpak-builtins-search.c:296
#4 0x000055cc22a2e0e6 in flatpak_run (argc=<optimized out>, argc@entry=3, argv=<optimized out>,
argv@entry=0x7ffc50fce198, res_error=res_error@entry=0x7ffc50fce078)
at /home/smcv/src/flatpak/app/flatpak-main.c:854
#5 0x000055cc22a2ee68 in main (argc=3, argv=0x7ffc50fce198) at /home/smcv/src/flatpak/app/flatpak-main.c:959
This seems to be a bug in libappstream rather than a bug in Flatpak. The assertion failure is here:
/* ensure the token cache is created */
if (g_once_init_enter (&priv->token_cache_valid)) {
as_component_create_token_cache (cpt);
g_once_init_leave (&priv->token_cache_valid, TRUE); <-- here
}
because both as_component_create_token_cache() and the g_once_init_enter()/g_once_init_leave() pair are trying to be responsible for writing to priv->token_cache_valid:
Relevant package versions:
with flatpak git HEAD, on Debian unstable. (Note that flatpak 1.12.x used libappstream-glib, but git HEAD has switched to libappstream.)
Steps to reproduce: run the Flatpak test suite
Expected result: tests succeed
Actual result: several tests fail with this assertion failure in libappstream:
Backtrace:
This seems to be a bug in libappstream rather than a bug in Flatpak. The assertion failure is here:
because both
as_component_create_token_cache()and theg_once_init_enter()/g_once_init_leave()pair are trying to be responsible for writing topriv->token_cache_valid:The text was updated successfully, but these errors were encountered: