Bug 89392

Summary: journalctl unicode message split/ellipsis cuts part of utf8 symbol
Product: systemd Reporter: Konstantin Gribov <grossws>
Component: generalAssignee: systemd-bugs
Status: RESOLVED NOTABUG QA Contact: systemd-bugs
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Konstantin Gribov 2015-03-02 15:32:49 UTC
journalctl splits long messages (in utf8) without knowledge of utf8-encoded codepoints boundary, so some messages are shown as `[2.0K blob data]` because it starts with non-utf8 bytes.

Also journalctl ellipsis can cut line in the middle of utf8-encoded codepoint.

Env: CentOS 7.0, systemd 208, en_US.UTF-8 locale.

Sample from `journalctl -f -u ...` (contains both issues):
> Mar 02 18:32:01 localhost systemd-docker[19345]: 509146375 [http-nio-8983-exec-98] INFO  org.apache.solr.core.SolrCore  – [core0] webapp=/solr path=/select params={facet=true&sort=pubdate+desc&fl=&facet.query=((...�о+продук
> Mar 02 18:32:01 localhost systemd-docker[19345]: [293B blob data]
> Mar 02 18:32:01 localhost systemd-docker[19345]: [293B blob data]
Comment 1 Zbigniew Jedrzejewski-Szmek 2015-03-02 17:35:07 UTC
This was (or should have been) fixed in systemd-209. Can you check with a newer version?
Comment 2 Konstantin Gribov 2015-03-02 18:05:04 UTC
I haven't system with 209, so I tested on 218. It works fine on it (generates unicode ellipsis with `journalctl --no-full`), so can be marked as not a bug.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.