'ascii' codec can't encode character '\u29f8' in position 19: ordinal not in range(128)
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed as abandoned. The snapcraft cleanbuild ASCII encoding error was not addressed, despite a suggested fix from snapd PR #1468.
Suggested action: —
No scores available.
Issue body
Trying to build in an lxc container using "snapcraft cleanbuild" and it barfs with:-
Setting up x11proto-composite-dev (1:0.4.2-2) ...
Setting up libxcomposite-dev (1:0.4.4-1) ...
Setting up x11proto-damage-dev (1:1.2.1-2) ...
Setting up libxdamage-dev:amd64 (1:1.1.4-2) ...
Setting up libxml2-utils (2.9.3+dfsg1-1ubuntu0.1) ...
Setting up libgtk2.0-dev (2.24.30-1ubuntu1) ...
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Processing triggers for systemd (229-4ubuntu7) ...
Processing triggers for ureadahead (0.100.0-19) ...
'ascii' codec can't encode character '\u29f8' in position 19: ordinal not in range(128)
Command '['lxc', 'exec', 'snapcraft-painfully-epigrammatic-jonathon', '--', 'snapcraft', 'snap', '--output', 'webtorrent_0.9.0_amd64.snap']' returned non-zero exit status 1
Here's the yaml, which builds fine outside lxc.
-----------------------------------------------------------------
name: webtorrent
version: 0.9.0
summary: Streaming torrent client for OS X, Windows, and Linux
description: |
confinement: devmode
apps:
webtorrent:
command: desktop-launch $SNAP/bin/webtorrent-desktop
plugs: [network, network-bind, unity7, X11, opengl, pulseaudio]
parts:
webtorrent:
after: [desktop/gtk2]
source: https://github.com/feross/webtorrent-desktop.git
source-tag: v0.9.0
plugin: nodejs
stage-packages:
- gconf-service
- gconf2
- git
- gvfs-bin
- libasound2
- libcap2
- libgcrypt20
- libgtk2.0-0
- libnotify4
- libnss3
- libudev1
- libxtst6
- python
- xdg-utils
- unity-gtk2-module
stage: [-usr/share/pkgconfig/shared-mime-info.pc]
snap: [-usr/share/pkgconfig/shared-mime-info.pc]
-----------------------------------------------------------------
timothy on irc suggested we should fix it like he did in snapd:-
http://github.com/snapcore/snapd/pull/1468/commits/b66d3ea328ee42d3d4f56ed9736c315833dee67d
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed as abandoned. The snapcraft cleanbuild ASCII encoding error was not addressed, despite a suggested fix from snapd PR #1468. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed by addressing the ASCII encoding error in snapcraft cleanbuild. The resolution adopted the referenced snapd commit to properly handle non-ASCII characters, preventing the UnicodeEncodeError. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed after applying a Unicode encoding fix to resolve the ASCII codec error during snapcraft cleanbuild. The issue was fixed by implementing proper UTF-8 handling in the build process, matching the referenced snapd patch. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1662456 snapcraft fails if desktop file included "ascii" cannot decode byte | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft build failures triggered by non-ASCII characters in desktop files caused an ASCII codec decode error. The report received no comments or patches and was abandoned, likely superseded by upstream UTF-8 handling improvements. | |
| #1649181 snapcraft search: 'ascii' codec can't encode character '\xae' in position 40: ordinal not in range(128) | snapcraft (launchpad) | open | snapcraft search crashes with an 'ascii' codec error when a part description contains a non-ASCII character (e.g. ®). Reported against snapcraft 2.22.1 on a classic dragonboard; no maintainer response, labels, or activity for ~10 years. |