Czkawka : Installation Snap ou execution binaire crash

Since new installation of Manjaro Plasma : 22.0.0 (Sikaris)

libEGL warning: MESA-LOADER: failed to open iris: /usr/lib/dri/iris_dri.so: échec d’adressage (mapping) du segment de l’objet partagé (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open iris: /usr/lib/dri/iris_dri.so: échec d’adressage (mapping) du segment de l’objet partagé (search paths /usr/lib/dri, suffix _dri)

libEGL warning: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: échec d’adressage (mapping) du segment de l’objet partagé (search paths /usr/lib/dri, suffix _dri)

libGL error: MESA-LOADER: failed to open iris: /usr/lib/dri/iris_dri.so: échec d’adressage (mapping) du segment de l’objet partagé (search paths /usr/lib/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open iris: /usr/lib/dri/iris_dri.so: échec d’adressage (mapping) du segment de l’objet partagé (search paths /usr/lib/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: échec d’adressage (mapping) du segment de l’objet partagé (search paths /usr/lib/dri, suffix _dri)
libGL error: failed to load driver: swrast

(linux_czkawka_gui:2782): GLib-ERROR **: 15:45:01.122: …/glib/glib/gmem.c:131: failed to allocate 3 bytes
Trappe pour point d’arrêt et de trace (core dumped)

idea ???

Why from SNAP? Why not from AUR?

:point_right: AUR (en) - czkawka-gui-bin :point_left:

Iven in binary it crash with a segfault .
I have not try from AUR , i will try.

But i have this segment memory problem even witjh youtube-dl

Thanks

lol@darkstar:~ > yay -S czkawka
fatal error: failed to reserve page summary memory

runtime stack:
runtime.throw({0x55ca57b543bf?, 0x7ffca9090030?})
runtime/panic.go:1047 +0x5f fp=0x7ffca908ffe0 sp=0x7ffca908ffb0 pc=0x55ca578500ff
runtime.(*pageAlloc).sysInit(0x55ca57e94290)
runtime/mpagealloc_64bit.go:82 +0x195 fp=0x7ffca9090068 sp=0x7ffca908ffe0 pc=0x55ca57846f75
runtime.(*pageAlloc).init(0x55ca57e94290, 0x55ca57e94280, 0x0?)
runtime/mpagealloc.go:324 +0x70 fp=0x7ffca9090090 sp=0x7ffca9090068 pc=0x55ca57844bd0
runtime.(*mheap).init(0x55ca57e94280)
runtime/mheap.go:721 +0x13f fp=0x7ffca90900c8 sp=0x7ffca9090090 pc=0x55ca57841fdf
runtime.mallocinit()
runtime/malloc.go:407 +0xb2 fp=0x7ffca90900f0 sp=0x7ffca90900c8 pc=0x55ca57826e32
runtime.schedinit()
runtime/proc.go:693 +0xab fp=0x7ffca9090150 sp=0x7ffca90900f0 pc=0x55ca57853acb
runtime.rt0_go()
runtime/asm_amd64.s:345 +0x120 fp=0x7ffca9090158 sp=0x7ffca9090150 pc=0x55ca5787dde0
lol@darkstar:~ >

This looks like the failing programs aren’t your problem.
It’s much rather your hardware that is failing here, causing these crashes.

1 Like

How can i test it ?

If you know how to manage computer hardware, you could try to make sure cables are properly connected (most likely not it), the CPU is not overheating (most likely not it), that your RAM is properly seated (maybe this is it; remove and reseat them).

Now if you want to do some software test, you could verify your RAM has no issue by running mprime with LargeFTTs test for at least multiple cycles but would be better to test very long time, and see if it errors out at some point, it should NEVER produce an error. If you have an error, it is possible that one or both RAM modules are bad (we have no info about your system so I assume you have a desktop and two sticks of RAM).

Sorry for all your efforts,
i find the cause of the problem,
i sounds it might be a config file import from backup.

All run fine by now

Thanks
Laurent

Can you give details about the issue, and also the solution so the thread can help others later?

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.