Segfault 28 #352
Comments
|
Please compare #278, which concerns segfaults on restore (obviously: very bad) and contains thorough debugging and an identification of what seems to be the - or at least a - culprit. |
|
Can I please add also to this or some other thread?: I selected 56 snapshots at once, only after 20 I think, I got a segfault, do not really understand it so deep, so this something like a bug report. Thank you in advance for your kind elaboration, if that is an error on Timeshift-GTK side of course. Cheers grep NVM /etc/fstabUUID=62575d63-cff1-4653-8fce-b8164d24ef93 /mnt/nvm ext4 nofail,nouser,auto,rw,async,x-gvfs-show,x-gvfs-name=NVM 0 0 timeshift-gtkApp config loaded: /etc/timeshift/timeshift.json Removing '2024-09-03_19-00-01'...
|
|
I'm still getting periodic segfaults. It's very disconcerting. |
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)The text was updated successfully, but these errors were encountered: