Description of problem:
I logged into Plasma 5.15.5 on Wayland in an F30 KDE Plasma spin installation. I started Back in time (root) from the menu. I added a new profile to backup / . I selected to save the file permissions and extended attributes. I added /usr/src/debug and /usr/lib/debug to the exclude list.
I started a snapshot to backup to an external USB hard drive. The snapshot stopped around 60% of the way, and Done was shown in the bottom of the screen. I had selected to check the snapshot log which showed the snapshot had stopped midway. No completed snapshot was in the list on the left of the window. I found this error in gnome-abrt later. The second time I tried this snapshot, it completed correctly without this error.
This problem with the same error and trace was reported by others at https://github.com/bit-team/backintime/issues/1003
Version-Release number of selected component:
cmdline: python3 -Es /usr/share/backintime/common/backintime.py --profile-id 3 backup
runlevel: N 5
snapshotlog.py:203:flush:RuntimeError: reentrant call inside <_io.BufferedWriter name='/root/.local/share/backintime/takesnapshot_3.log'>
Traceback (most recent call last):
File "/usr/share/backintime/common/backintime.py", line 1165, in <module>
File "/usr/share/backintime/common/backintime.py", line 517, in startApp
File "/usr/share/backintime/common/backintime.py", line 739, in backup
ret = takeSnapshot(cfg, force)
File "/usr/share/backintime/common/backintime.py", line 94, in takeSnapshot
ret = snapshots.Snapshots(cfg).backup(force)
File "/usr/share/backintime/common/snapshots.py", line 692, in backup
ret_val, ret_error = self.takeSnapshot(sid, now, include_folders)
File "/usr/share/backintime/common/snapshots.py", line 1036, in takeSnapshot
File "/usr/share/backintime/common/tools.py", line 1981, in run
File "/usr/share/backintime/common/snapshots.py", line 809, in rsyncCallback
self.snapshotLog.append('[C] ' + line[12:], 2)
File "/usr/share/backintime/common/snapshotlog.py", line 195, in append
self.logFile.write(msg + '\n')
File "/usr/share/backintime/common/tools.py", line 1513, in handler
File "/usr/share/backintime/common/snapshotlog.py", line 203, in flush
RuntimeError: reentrant call inside <_io.BufferedWriter name='/root/.local/share/backintime/takesnapshot_3.log'>
Local variables in innermost frame:
self: <snapshotlog.SnapshotLog object at 0x7faa6a4e2e10>
Created attachment 1590511 [details]
Created attachment 1590512 [details]
Created attachment 1590513 [details]
Created attachment 1590514 [details]
Created attachment 1590515 [details]
*** Bug 1733803 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 30 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.