https://bugs.kde.org/show_bug.cgi?id=469091
--- Comment #10 from Nate Graham <n...@kde.org> --- There's a better backtrace with debug symbols in Bug 496166. Here's the relevant part: #4 _flatpak_installation_get_dir (self=self@entry=0x0, ensure_repo=ensure_repo@entry=0, error=error@entry=0x0) at common/flatpak-installation.c:383 #5 0x00007fd3a410f40f in flatpak_installation_get_dir_maybe_no_repo (self=0x0) at common/flatpak-installation.c:399 #6 flatpak_installation_list_installed_refs_by_kind (self=self@entry=0x0, kind=kind@entry=FLATPAK_REF_KIND_APP, cancellable=cancellable@entry=0x0, error=error@entry=0x0) at common/flatpak-installation.c:954 #7 0x00007fd3a41d4a2d in getSystemInstalledFlatpakAppRefs () at /usr/src/debug/kcm_flatpak-5.27.11-bp156.1.1.x86_64/flatpakreference.cpp:168 #8 FlatpakReferencesModel::FlatpakReferencesModel (this=0x55c90cbc44f0, parent=<optimized out>) at /usr/src/debug/kcm_flatpak-5.27.11-bp156.1.1.x86_64/flatpakreference.cpp:182 #9 0x00007fd3a41ce2fa in KCMFlatpak::KCMFlatpak (this=0x55c90cbc4820, parent=<optimized out>, data=..., args=...) at /usr/src/debug/kcm_flatpak-5.27.11-bp156.1.1.x86_64/kcm.cpp:17 Looks like this can happen on systems with no Flatpak repos active? I suspect we never tested that case. -- You are receiving this mail because: You are watching all bug changes.
