You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
caja-1.27.2-0.3.git20231201.84fa213.el9.ml.x86_64 (custom build, based on a spec file from Fedora)
Linux Distribution
Rocky Linux 9.3
Link to bugreport of your Distribution (requirement)
No bug report, as it is not their package.
The following error is logged in /var/log/messages: kernel: traps: caja[6013] trap divide error ip:7f82424949b0 sp:7ffcbd869eb0 error:0 in libglib-2.0.so.0.6800.4[7f8242472000+91000]
I wouldn't report it, as it is my custom build (what may cause the error), but googling I've found a very similar error here: traps: caja[1878] trap divide error ip:7f6c1039bfe8 sp:7ffc005057d0 error:0 in libglib-2.0.so.0.6400.2 (deleted)[7f6c10379000+84000]
what make me guess that there is actually a part of the caja code, which in certain circumstances (doesn't happen on all machines and always, only on one machine and only on the forst start after boot...) can lead to a divide by zero condition in libglib.
Is there a way to find out which part of the caja code is "responsible" for this behavior (from ip:7f82424949b0 address, for instance)?
The text was updated successfully, but these errors were encountered:
Expected behaviour
No divide error
Actual behaviour
kernel trap - caja divide error 0 in libglib
Steps to reproduce the behaviour
From the log file, I guess it happens upon the first start (login). Probably caja is restarted after, and seem to run fine when logged in...
MATE general version
1.27.2 git commit 84fa213 (from Dec. 1st, 2023), with pull-request "image properties: Handle rotated images #1657" patch applied
Package version
caja-1.27.2-0.3.git20231201.84fa213.el9.ml.x86_64 (custom build, based on a spec file from Fedora)
Linux Distribution
Rocky Linux 9.3
Link to bugreport of your Distribution (requirement)
No bug report, as it is not their package.
The following error is logged in /var/log/messages:
kernel: traps: caja[6013] trap divide error ip:7f82424949b0 sp:7ffcbd869eb0 error:0 in libglib-2.0.so.0.6800.4[7f8242472000+91000]
I wouldn't report it, as it is my custom build (what may cause the error), but googling I've found a very similar error here:
traps: caja[1878] trap divide error ip:7f6c1039bfe8 sp:7ffc005057d0 error:0 in libglib-2.0.so.0.6400.2 (deleted)[7f6c10379000+84000]
what make me guess that there is actually a part of the caja code, which in certain circumstances (doesn't happen on all machines and always, only on one machine and only on the forst start after boot...) can lead to a divide by zero condition in libglib.
Is there a way to find out which part of the caja code is "responsible" for this behavior (from ip:7f82424949b0 address, for instance)?
The text was updated successfully, but these errors were encountered: