Comment 5 for bug 1978404

Al right, I run the command "sudo journalctl --since=yesterday | grep snap-store" to see if it displays more information instead of just displaying "segment violation" on the terminal. the command displayed this:

 " sep 02 14:23:41 T470 systemd[1573]: snap.snap-store.snap-store.7cb4ddce-830b-43cb-8ff5-464d0dece6f0.scope: Consumed 1.081s CPU time.
sep 02 14:31:54 T470 systemd[1573]: Started snap.snap-store.ubuntu-software.73d6bc1d-d009-43eb-82b5-6e6bea9abfd9.scope.
sep 02 14:31:54 T470 audit[9360]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=? pid=9360 comm="snap-store" exe="/snap/snap-store/582/usr/bin/snap-store" sig=0 arch=c000003e syscall=314 compat=0 ip=0x7f5615d6c73d code=0x50000
sep 02 14:31:54 T470 kernel: audit: type=1326 audit(1662147114.239:120): auid=1000 uid=1000 gid=1000 ses=3 subj=? pid=9360 comm="snap-store" exe="/snap/snap-store/582/usr/bin/snap-store" sig=0 arch=c000003e syscall=314 compat=0 ip=0x7f5615d6c73d code=0x50000
sep 02 14:31:55 T470 kernel: traps: snap-store[9360] general protection fault ip:7f5615c254a2 sp:7ffd370e85b0 error:0 in libxmlb.so.2.0.0[7f5615c1f000+20000]"

I've noticed that it says error in a library, specially the libxmlb.so.2.0.0 library, I think that can be the cause of the problem, the library is broken and needs to be updated, I don´t know what else can I do, since I don't have experience about snaps, hopefully that information helps the developers to find a solution.