Describe the bug
From the syslog:
kernel: timeshift[19966]: segfault at 28 ip 000073bbfc0f23fb sp 000073bbf65ff6f0 error 4 in libgobject-2.0.so.0.8000.0[73bbfc0dd000+37000] likely on CPU 8 (core 4, socket 0)
To Reproduce
Unknown. I suspect that Timeshift was running an automated job.
Expected behavior
No segfault reported in the log.
Other information
I have set Timeshift to backup /home, and to put all its backups on a separate partition. (I did this after a crash wiped out stuff beyond recovery.) But I have had segfaults on Timeshift before I adopted that strategy.
On my other Mint PC, and on a now dead PC that ran Mint, System Report never supplied crash dumps. Now, on a new PC, System Report does provide crash dumps - sometimes; there is no dump for this timeshift crash.
I have not seen any adverse behaviour from Timeshift, but possibly a scheduled action was aborted or did not write data properly. Anyhow, segfaults are bad (which is why I have a script to report them to me).
System:
- Linux Distribution Name and Version: Mint 22
- Desktop: Cinnamon
- Application version: 24.06.03
- Framwork 13 laptop (but, as I say above, I have had segfaults on a variety of hardware)
- Kernel: 6.8
EDIT: This too appeared in the log:
kernel: snapshot-taker[483769]: segfault at 30 ip 000079dc3f28c61a sp 000079dc333ff780 error 4 in libgobject-2.0.so.0.8000.0[79dc3f277000+37000] likely on CPU 1 (core 0, socket 0)
Describe the bug
From the syslog:
kernel: timeshift[19966]: segfault at 28 ip 000073bbfc0f23fb sp 000073bbf65ff6f0 error 4 in libgobject-2.0.so.0.8000.0[73bbfc0dd000+37000] likely on CPU 8 (core 4, socket 0)To Reproduce
Unknown. I suspect that Timeshift was running an automated job.
Expected behavior
No segfault reported in the log.
Other information
I have set Timeshift to backup /home, and to put all its backups on a separate partition. (I did this after a crash wiped out stuff beyond recovery.) But I have had segfaults on Timeshift before I adopted that strategy.
On my other Mint PC, and on a now dead PC that ran Mint, System Report never supplied crash dumps. Now, on a new PC, System Report does provide crash dumps - sometimes; there is no dump for this timeshift crash.
I have not seen any adverse behaviour from Timeshift, but possibly a scheduled action was aborted or did not write data properly. Anyhow, segfaults are bad (which is why I have a script to report them to me).
System:
EDIT: This too appeared in the log:
kernel: snapshot-taker[483769]: segfault at 30 ip 000079dc3f28c61a sp 000079dc333ff780 error 4 in libgobject-2.0.so.0.8000.0[79dc3f277000+37000] likely on CPU 1 (core 0, socket 0)