On the system that worked, this triggers it again as it will run apt-cache policy.
root@n:~# pro attach C...
An unexpected error occurred: 'utf-8' codec can't decode byte 0xa0 in position 18: invalid start byte
For more details, see the log: /var/log/ubuntu-advantage.log
If you think this is a bug, please run: ubuntu-bug ubuntu-advantage-tools
root@n:~# pro detach
An unexpected error occurred: 'utf-8' codec can't decode byte 0xa0 in position 18: invalid start byte
For more details, see the log: /var/log/ubuntu-advantage.log
If you think this is a bug, please run: ubuntu-bug ubuntu-advantage-tools
The problem is that the problem that this was is fixed "apt list --installed".
But this turns out to now be other calls, in that case apt-cache policy.
root@n:~# apt-cache policy
Fichiers du paquet�:
100 /var/lib/dpkg/status
...
You see the bad char here.
So it is more that all kind of calls could return unparseable, based on the language settings, and hit a bug quite similar to this.
So it seems:
- the original bug is actually fixed
- at least one more similar case is open still
- If we can we will try to ignore parsing errors kind of everywhere.
- If not, then this would need to become a new issue as it would need a bigger fix.
Out of a discussion with Renan.
On the system that worked, this triggers it again as it will run apt-cache policy.
root@n:~# pro attach C... ubuntu- advantage. log advantage- tools
An unexpected error occurred: 'utf-8' codec can't decode byte 0xa0 in position 18: invalid start byte
For more details, see the log: /var/log/
If you think this is a bug, please run: ubuntu-bug ubuntu-
root@n:~# pro detach ubuntu- advantage. log advantage- tools
An unexpected error occurred: 'utf-8' codec can't decode byte 0xa0 in position 18: invalid start byte
For more details, see the log: /var/log/
If you think this is a bug, please run: ubuntu-bug ubuntu-
The problem is that the problem that this was is fixed "apt list --installed".
But this turns out to now be other calls, in that case apt-cache policy.
root@n:~# apt-cache policy dpkg/status
Fichiers du paquet�:
100 /var/lib/
...
You see the bad char here.
So it is more that all kind of calls could return unparseable, based on the language settings, and hit a bug quite similar to this.
So it seems:
- the original bug is actually fixed
- at least one more similar case is open still
- If we can we will try to ignore parsing errors kind of everywhere.
- If not, then this would need to become a new issue as it would need a bigger fix.