Description of problem: Installation of telegram-desktop from flathub Version-Release number of selected component: gnome-software-43.5-1.fc37 Additional info: reporter: libreport-2.17.10 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Software-3010.scope cmdline: /usr/bin/gnome-software --gapplication-service crash_function: xb_silo_get_node_attr_by_str executable: /usr/bin/gnome-software journald_cursor: s=d6dd9d4d23a741319158af26396934e3;i=472db5;b=1fc8811973d44a918af8f9e3022c9f08;m=3a37e48d;t=5fd5bcdf64477;x=d4c507ffda02f585 kernel: 6.3.5-100.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 xb_silo_get_node_attr_by_str at ../src/xb-node.c:526 #1 xb_node_get_attr at ../src/xb-node.c:526 #2 gs_appstream_refine_app at ../lib/gs-appstream.c:1054 #3 gs_appstream_create_app at ../lib/gs-appstream.c:32 #4 gs_flatpak_refine_wildcard at ../plugins/flatpak/gs-flatpak.c:3649 #5 refine_thread_cb at ../plugins/flatpak/gs-plugin-flatpak.c:627 #6 work_run_cb at ../lib/gs-worker-thread.c:236 #10 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4248 #11 g_main_context_iteration at ../glib/gmain.c:4313 #12 thread_cb at ../lib/gs-worker-thread.c:175 Potential duplicate: bug 2148298
Created attachment 1968957 [details] File: backtrace
Created attachment 1968958 [details] File: core_backtrace
Created attachment 1968959 [details] File: cpuinfo
Created attachment 1968960 [details] File: dso_list
Created attachment 1968961 [details] File: environ
Created attachment 1968962 [details] File: exploitable
Created attachment 1968963 [details] File: limits
Created attachment 1968964 [details] File: maps
Created attachment 1968965 [details] File: mountinfo
Created attachment 1968966 [details] File: open_fds
Created attachment 1968967 [details] File: proc_pid_status
Created attachment 1968968 [details] File: var_log_messages
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate. *** This bug has been marked as a duplicate of bug 2148298 ***