New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rescuezilla last version cancel to start backup #402
Comments
Ahh duplicate error to #412 Exact same command too. Highest priority bug current in Rescuezilla, will figure out the root cause and fix for next release. |
shasheene
added
bug
Something isn't working
duplicate
This issue or pull request already exists
labels
Apr 14, 2023
shasheene
added a commit
to shasheene/rescuezilla-dev
that referenced
this issue
Aug 19, 2023
shasheene
added a commit
to shasheene/rescuezilla-dev
that referenced
this issue
Oct 29, 2023
shasheene
added a commit
that referenced
this issue
Oct 29, 2023
shasheene
added a commit
to shasheene/rescuezilla-dev
that referenced
this issue
Nov 26, 2023
Revert (unreleased) change where "lshw" and "efibootmgr" were producing binary data, and custom 'None' encoding was used. The change is likely valid, but there are other circumstances where things are being handled incorrectly (rescuezilla#454) that require further thought, ideally based on a true reproducible test case. Also "efibootmgr" is used during the restore process so further examination in also warranted. The change will likely be adjusted and reapplied in future. This reverts commit d423de0. Reverts PR rescuezilla#443. Issue references rescuezilla#402, rescuezilla#412, rescuezilla#443, rescuezilla#454
shasheene
added a commit
that referenced
this issue
Nov 26, 2023
…ing release (#458) Revert (unreleased) change where "lshw" and "efibootmgr" were producing binary data, and custom 'None' encoding was used. **The purpose of the revert is to unblock releasing the existing work (as a quite stable, well-tested rolling release) without introducing behavior different to Rescuezilla v2.4.2 that was only tested against synthetic data** The change is likely valid, but there are other circumstances where things are being handled incorrectly (#454) that require further thought, ideally based on a true reproducible test case. Also "efibootmgr" is used during the restore process so further examination in also warranted. The change will likely be adjusted and reapplied in future. This reverts commit d423de0. Reverts PR #443. Issue references #402, #412, #443, #454
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Backup operation failed:
Error creating backup: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/rescuezilla/backup_manager.py", line 131, in do_backup_wrapper
self.do_backup()
File "/usr/lib/python3/dist-packages/rescuezilla/backup_manager.py", line 413, in do_backup
process, flat_command_string, failed_message = Utility.run("Saving EFI NVRAM info",
File "/usr/lib/python3/dist-packages/rescuezilla/utility.py", line 502, in run
process = subprocess.run(cmd_list, encoding='utf-8', capture_output=True, env=env)
File "/usr/lib/python3.10/subprocess.py", line 503, in run
stdout, stderr = process.communicate(input, timeout=timeout)
File "/usr/lib/python3.10/subprocess.py", line 1149, in communicate
stdout, stderr = self._communicate(input, endtime, timeout)
File "/usr/lib/python3.10/subprocess.py", line 2038, in _communicate
stdout = self._translate_newlines(stdout,
File "/usr/lib/python3.10/subprocess.py", line 1026, in _translate_newlines
data = data.decode(encoding, errors)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 106: invalid start byte
The text was updated successfully, but these errors were encountered: