On Wed, 08 Mar 2023 10:47:25 +0100 Laurent Bigonville <bi...@debian.org> wrote:
$ pkcon what-provides application/x-keepass2
Getting provides                        [=========================]
Loading cache                           [=========================]
Querying                                [=========================]         e 
daemon crashed mid-transaction!
Finished                                [                         ] (0%)

               Stack trace of thread 10447:
                #0  0x00007faf3ef75ccc __pthread_kill_implementation (libc.so.6 
+ 0x8accc)
                #1  0x00007faf3ef26ef2 __GI_raise (libc.so.6 + 0x3bef2)
                #2  0x00007faf3ef11472 __GI_abort (libc.so.6 + 0x26472)
                #3  0x00007faf3c89d919 
_ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6 + 0x9d919)
                #4  0x00007faf3c8a8e1a _ZN10__cxxabiv111__terminateEPFvvE 
(libstdc++.so.6 + 0xa8e1a)
                #5  0x00007faf3c8a8e85 _ZSt9terminatev (libstdc++.so.6 + 
0xa8e85)
                #6  0x00007faf3c8a90d8 __cxa_throw (libstdc++.so.6 + 0xa90d8)
                #7  0x00007faf3c8a00e4 _ZSt19__throw_logic_errorPKc 
(libstdc++.so.6 + 0xa00e4)
                #8  0x00007faf3e96cb3a 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC4IS3_EEPKcRKS3_ 
(libpk_backend_apt.so + 0x2cb3a)
                #9  0x00007faf3e95d122 backend_what_provides_thread 
(libpk_backend_apt.so + 0x1d122)
                #10 0x00005644cb0c7aca pk_backend_job_thread_setup (packagekitd 
+ 0x23aca)
                #11 0x00007faf3f5dbcfd g_thread_proxy (libglib-2.0.so.0 + 
0x7ecfd)
                #12 0x00007faf3ef73fd4 start_thread (libc.so.6 + 0x88fd4)
                #13 0x00007faf3eff466c __clone3 (libc.so.6 + 0x10966c)


Hello Laurent,
I am just looking at some random crash reports.
Unfortunately I cannot reproduce the crash in a
current QEMU VM, neither minimal nor with a Gnome desktop.
I cannot even convince the pkcon processes to load the
library libpk_backend_apt.so.

Can you still reproduce it. And do you probably have
done some changes to the configuration?
It looks like the system wide packagekitd is contacted,
maybe that shows something in the journal.

Kind regards,
Bernhard

Reply via email to