[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
Sorry for late response. I filed bug #2025651. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Fix Released Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
** Attachment added: "lunar without fonts-droid-fallback" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5683311/+files/Screenshot%20from%202023-07-02%2013-33-22.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Fix Released Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
@Gunnar Thanks for the advice. I removed fonts-droid-fallback and tried it, and now Japanese glyphs are displayed. However, I am concerned that it only affects the snap package, while the non-snap package seems to select the correct glyphs. I will first check if this also happens in Mantic and then report the problem to language-selector. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Fix Released Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
** Attachment added: "jammy glyph" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5683253/+files/Screenshot%20from%202023-07-01%2021-52-33.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Fix Released Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
Hi all, Does this fix affect Japanese fonts? I installed Ubuntu 23.04 today and encountered a problem where the Japanese in the snap package is incorrectly displayed with Chinese font glyphs. Specifically, the problem occurs in Firefox and Snap Store, but not in gnome-terminal or Text Editor. I have attached a screenshot that shows the difference between Ubuntu 22.04 LTS and Ubuntu 23.04. The letters circled in red should originally look the same in 22.04 and 23.04. ** Attachment added: "lunar glyph" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076/+attachment/5683252/+files/Screenshot%20from%202023-07-01%2021-51-17.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Fix Released Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968459] Re: IBus 1.5.26 does not enable on Xorg sesson
Reported to upstream, https://github.com/ibus/ibus/issues/2397 ** Bug watch added: github.com/ibus/ibus/issues #2397 https://github.com/ibus/ibus/issues/2397 ** Bug watch added: Debian Bug tracker #1009256 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009256 ** Also affects: ibus (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009256 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1968459 Title: IBus 1.5.26 does not enable on Xorg sesson Status in ibus: Unknown Status in ibus package in Ubuntu: Confirmed Status in ibus package in Debian: Unknown Bug description: I tested newly installed Ubuntu 22.04 LTS dev. step to reproduce: 1. boot 2. select user 3. session changes to Ubuntu on Xorg from Ubuntu 4. enter password 5. run gedit 6. put Hankaku/Zenkaku key 7. nothing to happen consideration： Run "ps ax |grep ibus" on terminal: $ ps ax |grep ibus 5774 ?Ss 0:00 sh -c /usr/bin/ibus-daemon --panel disable $([[ $XDG_SESSION_TYPE == "x11" ]] && echo "--xim") 5779 ?Sl 0:00 /usr/bin/ibus-daemon --panel disable 5863 ?Sl 0:00 /usr/libexec/ibus-dconf 5864 ?Sl 0:00 /usr/libexec/ibus-extension-gtk3 5868 ?Sl 0:00 /usr/libexec/ibus-portal 5965 ?Sl 0:00 /usr/lib/ibus-mozc/ibus-engine-mozc --ibus 6831 pts/1R+ 0:00 grep --color=auto ibus It is strange. IBus 1.5.25 introduces systemd user unit files. /usr/lib/systemd/user/org.freedesktop.IBus.session.GNOME.service /usr/lib/systemd/user/org.freedesktop.IBus.session.generic.service above contains "ExecStart=sh -c '/usr/bin/ibus-daemon --panel disable $([[ $XDG_SESSION_TYPE == "x11" ]] && echo "--xim")" https://github.com/ibus/ibus/blob/master/bus/services/org.freedesktop.IBus.session.GNOME.service.in#L21 It may be bashism. I changed to "ExecStart=bash -c '/usr/bin/ibus-daemon --panel disable $([[ $XDG_SESSION_TYPE == "x11" ]] && echo "--xim")" and reboot then works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1968459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964682] Re: IBus not starting properly at login to wayland with gnome-shell 42
Hi, > No package 'systemd' found Simply, is it because ibus version 1.5.26 now requires systemd? https://github.com/ibus/ibus/pull/2377 - Salsa CI: it seems that systemd is not installed (just docker instance?) - PPA builder: systemd is installed - Local: normally systemd is installed I don't know if this fix is necessary for Ubuntu as well, but if im- config handles it well, it may be possible to build with the "--disable- systemd-services" option. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1964682 Title: IBus not starting properly at login to wayland with gnome-shell 42 Status in gnome-shell package in Ubuntu: Invalid Status in ibus package in Ubuntu: In Progress Bug description: To get to the state in the bug summary I did: 1. Installed Ubuntu via the 220312 ISO 2. Made sure that all packages were updated 3. Installed ibus-libpinyin, re-logged in, and added "Intelligent Pinyin" to the input sources 4. Enabled -proposed 5. Run this command: sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 libmutter-10-0 mutter-common 6. Rebooted Now, once logged in, gnome-shell does not include "Intelligent Pinyin" in the input source menu. Several expected processes are missing: $ ps aux | grep ibus gunnar 3057 0.0 0.0 232404 7984 ?Sl 20:05 0:00 ibus-daemon --panel disable -r --xim gunnar 3076 0.0 0.0 157280 6228 ?Sl 20:05 0:00 /usr/libexec/ibus-memconf gunnar 5117 0.0 0.0 24492 2776 pts/0S+ 20:06 0:00 grep --color=auto ibus If I start ibus-setup it shows the attached dialog. From there I can click "Yes" and successfully start IBus that way, and then it works as expected. Note that im-config is not involved. Nowadays, on GNOME desktops, we rely completely on the GNOME mechanisms for starting and configuring IBus. One thought is that ibus upstream has not released since August 20. Can it possibly be that some unreleased upstream ibus commits are needed for gnome-shell 42? https://github.com/ibus/ibus/commits/master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863414] Re: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" o
** Also affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863414 Title: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usage Status in python3-defaults package in Ubuntu: Confirmed Status in python3.8 package in Ubuntu: Won't Fix Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Run regular APT task such as `sudo apt dist-upgrade` 3. Wait it to finish Expected results: * APT runs without any warnings and/or errors Actual results: * APT runs with many python-related warnings like >``` >/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported >in binary mode, the default buffer size will be used > self.stdin = io.open(p2cwrite, 'wb', bufsize) > >``` Full output below: ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: ruby-json ruby-pg ruby-sequel ruby-sequel-pg Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: kdevelop55-libs libxentoolcore1 ubuntu-mate-wallpapers-focal The following packages will be upgraded: atril atril-common debootstrap dmeventd dmsetup dnsmasq-base engrampa engrampa-common fwupd fwupd-signed gir1.2-atrildocument-1.5.0 gir1.2-atrilview-1.5.0 gir1.2-freedesktop gir1.2-glib-2.0 gir1.2-pluma-1.0 initramfs-tools initramfs-tools-bin initramfs-tools-core iproute2 isc-dhcp-client isc-dhcp-common jekyll k3b k3b-data k3b-i18n kdevelop kdevelop-data libatrildocument-dev libatrildocument3 libatrilview-dev libatrilview3 libdevmapper-event1.02.1 libdevmapper1.02.1 libdistro-info-perl libfwupd2 libfwupdplugin1 libgirepository-1.0-1 libk3b7 libk3b7-extracodecs liblvm2cmd2.03 libmate-sensors-applet-plugin-dev libmate-sensors-applet-plugin0 libmate-slab0 libmate-window-settings-dev libmate-window-settings1 libmatedict-dev libmatedict6 libmysqlclient21 libmysqlclient21:i386 libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 libxenstore3.0 libxmlgraphics-commons-java lvm2 mate-applets mate-applets-common mate-common mate-control-center mate-control-center-common mate-core mate-desktop-environment mate-desktop-environment-core mate-desktop-environment-extra mate-desktop-environment-extras mate-dock-applet mate-media mate-media-common mate-netbook mate-netbook-common mate-notification-daemon mate-notification-daemon-common mate-power-manager mate-power-manager-common mate-screensaver mate-screensaver-common mate-sensors-applet mate-sensors-applet-common mate-sensors-applet-nvidia mate-system-monitor mate-system-monitor-common mate-terminal mate-terminal-common mate-user-share mate-user-share-common mate-utils mate-utils-common maxima maxima-doc maxima-share mozo nano pluma pluma-common pluma-dev pluma-doc plymouth-theme-ubuntu-mate-logo plymouth-theme-ubuntu-mate-text python-caja-common python3-caja python3-distro-info python3-macaroonbakery qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils ubuntu-mate-artwork ubuntu-mate-default-settings ubuntu-mate-icon-themes ubuntu-mate-lightdm-theme ubuntu-mate-live-settings ubuntu-mate-themes ubuntu-mate-wallpapers ubuntu-mate-wallpapers-artful ubuntu-mate-wallpapers-bionic ubuntu-mate-wallpapers-common ubuntu-mate-wallpapers-complete ubuntu-mate-wallpapers-cosmic ubuntu-mate-wallpapers-disco ubuntu-mate-wallpapers-eoan ubuntu-mate-wallpapers-legacy ubuntu-mate-wallpapers-photos ubuntu-mate-wallpapers-utopic ubuntu-mate-wallpapers-vivid ubuntu-mate-wallpapers-wily ubuntu-mate-wallpapers-xenial ubuntu-mate-wallpapers-yakkety ubuntu-mate-wallpapers-zesty umbrello 136 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 215 MB of archives. After this operation, 12,8 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu focal/universe amd64 mate-common all 1.24.0-1ubuntu1 [17,0 kB] ... Get:139 http://archive.ubuntu.com/ubuntu focal/universe amd64 mate-dock-applet amd64 20.04.0-0ubuntu1 [91,8 kB] Fetched 215 MB in 4min 4s (882 kB/s) Extracting templates from packages: 100% Preconfiguring package
[Touch-packages] [Bug 1863825] Re: 20.04 apt update of python 3.8 gives errors
We can reproduce following command: $ sudo py3compile -p python3-apport -V 3.0- /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) py3comipe set "bufsize=1" for subprocess.Popen(): https://salsa.debian.org/cpython- team/python3-defaults/blob/master/py3compile#L132-133 process = Popen(cmd, bufsize=1, shell=True, stdin=PIPE, close_fds=True) However newer python (from 3.8?) warn on buffering=1. * https://github.com/python/cpython/commit/a2670565d8f5c502388378aba1fe73023fd8c8d4 * https://bugs.python.org/issue32236 ** Bug watch added: Python Roundup #32236 http://bugs.python.org/issue32236 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863825 Title: 20.04 apt update of python 3.8 gives errors Status in python3-defaults package in Ubuntu: Confirmed Bug description: Run sudo apt dist-upgrade on 20.04 install. Expected result: python3 is updated without issue Actual result: After this operation, 1,114 kB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-minimal amd64 3.8.0-3ubuntu1 [23.3 kB] Get:2 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3 amd64 3.8.0-3ubuntu1 [47.6 kB] Get:3 http://us.archive.ubuntu.com/ubuntu focal/main amd64 libpython3-stdlib amd64 3.8.0-3ubuntu1 [6,872 B] Get:4 http://us.archive.ubuntu.com/ubuntu focal/main amd64 libnewt0.52 amd64 0.52.21-4ubuntu2 [41.1 kB] Get:5 http://us.archive.ubuntu.com/ubuntu focal/main amd64 whiptail amd64 0.52.21-4ubuntu2 [17.0 kB] Get:6 http://us.archive.ubuntu.com/ubuntu focal/main amd64 gnome-disk-utility amd64 3.35.91-1ubuntu1 [186 kB] Get:7 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 onboard-data all 1.4.1-2ubuntu7 [3,803 kB] Get:8 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 onboard amd64 1.4.1-2ubuntu7 [351 kB] Get:9 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 onboard-common all 1.4.1-2ubuntu7 [530 kB] Get:10 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 python3-html5-parser amd64 0.4.9-3build1 [125 kB] Get:11 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-renderpm amd64 3.5.34-1build1 [60.4 kB] Get:12 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-reportlab-accel amd64 3.5.34-1build1 [19.4 kB] Get:13 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-reportlab all 3.5.34-1build1 [546 kB] Get:14 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-systemd amd64 234-3build2 [36.5 kB] Fetched 5,793 kB in 8s (694 kB/s) (Reading database ... 529746 files and directories currently installed.) Preparing to unpack .../python3-minimal_3.8.0-3ubuntu1_amd64.deb ... Unpacking python3-minimal (3.8.0-3ubuntu1) over (3.8.0-3) ... Setting up python3-minimal (3.8.0-3ubuntu1) ... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be use d self.stdin = io.open(p2cwrite, 'wb', bufsize) (Reading database ... 529746 files and directories currently installed.) Preparing to unpack .../00-python3_3.8.0-3ubuntu1_amd64.deb ... running python pre-rtupdate hooks for python3.8... Unpacking python3 (3.8.0-3ubuntu1) over (3.8.0-3) ... Preparing to unpack .../01-libpython3-stdlib_3.8.0-3ubuntu1_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.8.0-3ubuntu1) over (3.8.0-3) ... Preparing to unpack .../02-libnewt0.52_0.52.21-4ubuntu2_amd64.deb ... Unpacking libnewt0.52:amd64 (0.52.21-4ubuntu2) over (0.52.21-4ubuntu1) ... Preparing to unpack .../03-whiptail_0.52.21-4ubuntu2_amd64.deb ... Unpacking whiptail (0.52.21-4ubuntu2) over (0.52.21-4ubuntu1) ... Preparing to unpack .../04-gnome-disk-utility_3.35.91-1ubuntu1_amd64.deb ... Unpacking gnome-disk-utility (3.35.91-1ubuntu1) over (3.35.2-1ubuntu1) ... Preparing to unpack .../05-onboard-data_1.4.1-2ubuntu7_all.deb ... Unpacking onboard-data (1.4.1-2ubuntu7) over (1.4.1-2ubuntu6) ... Preparing to unpack .../06-onboard_1.4.1-2ubuntu7_amd64.deb ... Unpacking onboard (1.4.1-2ubuntu7) over (1.4.1-2ubuntu6) ... Preparing to unpack .../07-onboard-common_1.4.1-2ubuntu7_all.deb ... Unpacking onboard-common (1.4.1-2ubuntu7) over (1.4.1-2
[Touch-packages] [Bug 1823423] Re: ibus ftbfs in disco
Upload debdiff to be applied upstream patch. ** Patch added: "ibus_1.5.19-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1823423/+attachment/5253389/+files/ibus_1.5.19-1ubuntu2.debdiff ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1823423 Title: ibus ftbfs in disco Status in ibus package in Ubuntu: Confirmed Bug description: https://launchpadlibrarian.net/417924597/buildlog_ubuntu-disco- amd64.ibus_1.5.19-1ubuntu1_BUILDING.txt.gz multiple vala/glib errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1823423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823423] Re: ibus ftbfs in disco
FYI: fixed in upstream new release https://github.com/ibus/ibus/commit/4d7c1e00e15921a0448947961183c1c124b6b49f Delete weak pointer in GList.SList for vala 0.43.4 Vala 0.43.4 does not allow to convert a weak pointer to the full one in SList. https://github.com/ibus/ibus/releases/tag/1.5.20 Fix misc build issues aa0f425 6e31597 c1b5543 3172c3b 4d7c1e0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1823423 Title: ibus ftbfs in disco Status in ibus package in Ubuntu: New Bug description: https://launchpadlibrarian.net/417924597/buildlog_ubuntu-disco- amd64.ibus_1.5.19-1ubuntu1_BUILDING.txt.gz multiple vala/glib errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1823423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721023] [NEW] select window is pop up on top left of display
Public bug reported: On wayland session, ibus (or wayland or gtk) display selection window on top left of the display. No problem on xorg session. How to reproduce: 1. Install artful 2. Install ibus-mozc (or install artful as Japanese locale) 3. Login to wayland session 4. Startup gedit or gnome-terminal 5. Press Hankaku/Zenkaku (or enable Japanese input method) 6. Type any words and press space Expected result: The select window pop up on bottom of the cursor. Actual result: The select window pop up on top left of the display. Fireforx hasn't any problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ibus 1.5.14-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 3 21:46:09 2017 InstallationDate: Installed on 2017-09-18 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages wayland-session ** Attachment added: "Screenshot from 2017-10-02 22-46-48.png" https://bugs.launchpad.net/bugs/1721023/+attachment/4961331/+files/Screenshot%20from%202017-10-02%2022-46-48.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1721023 Title: select window is pop up on top left of display Status in ibus package in Ubuntu: New Bug description: On wayland session, ibus (or wayland or gtk) display selection window on top left of the display. No problem on xorg session. How to reproduce: 1. Install artful 2. Install ibus-mozc (or install artful as Japanese locale) 3. Login to wayland session 4. Startup gedit or gnome-terminal 5. Press Hankaku/Zenkaku (or enable Japanese input method) 6. Type any words and press space Expected result: The select window pop up on bottom of the cursor. Actual result: The select window pop up on top left of the display. Fireforx hasn't any problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ibus 1.5.14-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 3 21:46:09 2017 InstallationDate: Installed on 2017-09-18 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1721023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706558] Re: Japanese Input Method doesn't work by default in Ubuntu 17.10 daily build.
Ubuntu 17.10 will adopt ibus-mozc. https://code.launchpad.net/~gunnarhj/ubuntu-seeds/ubuntu.artful_cjkv-fixes/+merge/329857 But new ubuntu-meta isn't released yet. At the moment ibus-mozc isn't included on ISO image. ibus-mozc is moved to main from universe on artful. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Fix Committed ** Changed in: mozc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1706558 Title: Japanese Input Method doesn't work by default in Ubuntu 17.10 daily build. Status in ibus package in Ubuntu: Invalid Status in mozc package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: I installed Ubuntu Desktop 17.10 daily build (selected Japanese Language), but ibus-mozc (Japanese Input Method) is not installed when installing Ubuntu 17.10 daily build. Fcitx and fcitx-mozc are installed when installing Ubuntu 17.10 daily build. But the default is ibus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1706558/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706558] Re: Japanese Input Method doesn't work by default in Ubuntu 17.10 daily build.
First of all, we needs to decide to adopt either fcitx or ibus on Artful. https://lists.ubuntu.com/archives/ubuntu-desktop/2017-July/005054.html If ibus is adopted, next ibus-mozc (note: srcpkg is mozc) is migrated from universe to main. mozc is already included to main, ibus-mozc is just switched by archive admin. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1706558 Title: Japanese Input Method doesn't work by default in Ubuntu 17.10 daily build. Status in ibus package in Ubuntu: Invalid Status in mozc package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: New Bug description: I installed Ubuntu Desktop 17.10 daily build (selected Japanese Language), but ibus-mozc (Japanese Input Method) is not installed when installing Ubuntu 17.10 daily build. Fcitx and fcitx-mozc are installed when installing Ubuntu 17.10 daily build. But the default is ibus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1706558/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706558] Re: Japanese Input Method doesn't work by default in Ubuntu 17.10 daily build.
** Changed in: ibus (Ubuntu) Status: New => Confirmed ** Also affects: mozc (Ubuntu) Importance: Undecided Status: New ** Changed in: mozc (Ubuntu) Status: New => Confirmed ** Changed in: ibus (Ubuntu) Status: Confirmed => Invalid ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1706558 Title: Japanese Input Method doesn't work by default in Ubuntu 17.10 daily build. Status in ibus package in Ubuntu: Invalid Status in mozc package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: New Bug description: I installed Ubuntu Desktop 17.10 daily build (selected Japanese Language), but ibus-mozc (Japanese Input Method) is not installed when installing Ubuntu 17.10 daily build. Fcitx and fcitx-mozc are installed when installing Ubuntu 17.10 daily build. But the default is ibus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1706558/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
> bdmurray Thanks, uploading! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Released Status in less source package in Yakkety: Fix Released Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
no response about failure. removed "verification-failed". ** Tags removed: verification-failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Committed Status in less source package in Yakkety: Fix Committed Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
Hi Brian and G.M., >> until comment #17 is investigated further. > > IMHO, comment #17 is other bug and not affect this patch. > > Is it can reproduce on 16.04 or 16.10? > > If not, could you filed your problem as other bug? Is there any update? Thanks, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Committed Status in less source package in Yakkety: Fix Committed Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
Hi Brian and G.M., > until comment #17 is investigated further. IMHO, comment #17 is other bug and not affect this patch. * The original bug is reproducible by description way. * Already confirmed that the original bag is fixed with this patch. * comment #17 isn't reproducible at least on Brian's and my environment. * Not known whether comment #17 is reproducible with old version. Additionally to this, the original bug and patch is mainly affect wrapped line with wide characters. However sample text on comment #17 has a line with wide character, and it seems that the line isn't wrapped why is very short. > G.M. Could you explain how to reproducible method and upload reproducible file? Is it can reproduce on 16.04 or 16.10? If not, could you filed your problem as other bug? Thanks, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Committed Status in less source package in Yakkety: Fix Committed Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
Hi, G.M. > Opening this file with less, the ngoing up & down with arrows or pgup/pgdown, you'll notice that the lines with '>>>' will merge into a single line. I cannot reproduce it on gnome-terminal 70x24. 1. Could you upload your reproducible file? 2. What about terminal software and its window size? 3. If use "less -N file", what it will be? Thanks, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Committed Status in less source package in Yakkety: Fix Committed Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
Hi Łukasz and Chris, Thank you for SRUing! I done testing new version both on xenial and yakkety without any problem. ** Attachment added: "Test on xenial" https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+attachment/4855863/+files/Screenshot%20from%202017-04-06%2009-53-00.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Committed Status in less source package in Yakkety: Fix Committed Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
** Attachment added: "Test on yakkety" https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+attachment/4855864/+files/Screenshot%20from%202017-04-06%2010-04-18.png ** Tags removed: verification-needed ** Tags added: verification-done yakkety ** Tags removed: xenial yakkety ** Tags added: verification-done-xenial verification-done-yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Fix Released Status in less source package in Xenial: Fix Committed Status in less source package in Yakkety: Fix Committed Bug description: [Impact] Currently less doesn't work correctly with UTF-8 encoded Japanese characters, wrapping the lines in an invalid manner, missing or duplicating them (see original description below for exact error cases). For locale like these it breaks the general workflow, making the tool unreliable. [Test Case] 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top and only the first part of the wrapped line should be shown. 5. Type "k", then you will see "001", "002" and "003" at the top. [Regression Potential] Rather low as the fix is present in the beta version of less for over 5 months already, which seems to be enough time for general audience testing. But since the width tables are modified potentially this could lead to other similar breakages related to wide-character handling. [Original Description] When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
I would like to SRU to xenial and yakkety. Could you set affected distribution? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Confirmed Bug description: When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
Hi Łukasz! Diffs mkutable is just origin of author (between me and upstream author). It seems that mkutable in 487 is more fine. I attach new debdiff based on 487. Please review it. Anyway, normal build process doesn't use mkutable. mkutable script is only used by Makefile.aut when generating source archive for new version. More important components are FOO.uni files. There are generated by mkutable and included source archive. Tanks! ** Patch added: "fix-1562308.debdiff" https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+attachment/4844867/+files/fix-1562308.debdiff ** Tags added: patch patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Confirmed Bug description: When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
Hi Brian, Fixed in less-487, unfortunately it is in BETA yet. http://www.greenwoodsoftware.com/less/ http://www.greenwoodsoftware.com/less/news.487.html > Fix bug in Unicode handling that missed some double width characters. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Confirmed Bug description: When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
** Changed in: less (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Confirmed Bug description: When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
The table of width of characters in less-481 is incorrect. I fixed table generator script and re-generate table files. Because of branch of bazaar is old (wily?), I attached debdiff file instead of merge request. This patch is already forwarded to upstream. Please sponsor it. ** Patch added: "fix-1562308.debdiff" https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+attachment/4741380/+files/fix-1562308.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: In Progress Bug description: When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
** Changed in: less (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: In Progress Bug description: When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1571158] Re: Crash in QXcbWindow::setParent() due to NULL xcbScreen()
Upload minimal code to reproduce it. Patch is here: https://github.com/qtproject/qtbase/commit/eaa3a9d0108cdf692f1686cafefb7b834f0e5af6 ** Attachment added: "Reproducible project" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1571158/+attachment/4638102/+files/Test50081.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1571158 Title: Crash in QXcbWindow::setParent() due to NULL xcbScreen() Status in qtbase-opensource-src package in Ubuntu: New Bug description: Qt 5.5.1 has problem to "[QTBUG-50081] Crash in QXcbWindow::setParent() due to NULL xcbScreen()". This is already fixed in upstream. https://bugreports.qt.io/browse/QTBUG-50081 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1571158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1571158] [NEW] Crash in QXcbWindow::setParent() due to NULL xcbScreen()
Public bug reported: Qt 5.5.1 has problem to "[QTBUG-50081] Crash in QXcbWindow::setParent() due to NULL xcbScreen()". This is already fixed in upstream. https://bugreports.qt.io/browse/QTBUG-50081 ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1571158 Title: Crash in QXcbWindow::setParent() due to NULL xcbScreen() Status in qtbase-opensource-src package in Ubuntu: New Bug description: Qt 5.5.1 has problem to "[QTBUG-50081] Crash in QXcbWindow::setParent() due to NULL xcbScreen()". This is already fixed in upstream. https://bugreports.qt.io/browse/QTBUG-50081 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1571158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1290031] Re: Support japanese language
Hi Michael, Thank you reviewed it. And new candidates is pushed. Could you recheck it? https://code.launchpad.net/~cosmos-door/ubuntu-keyboard/japanese- keyboard-rebooted/+merge/268158/comments/724906 Note: I couldn't reproduce you found problem. sorry. Regards, -- Mitsuya Shibata -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1290031 Title: Support japanese language Status in ubuntu-keyboard: Confirmed Status in ubuntu-keyboard package in Ubuntu: In Progress Bug description: Please support to input japanese language from ubuntu-keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1290031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1290031] Re: Support japanese language
Hi Michael, New codes are pushed to merge proposal. I believe all problems which you pointed out are fixed. Could you review it? Regards, -- Mitsuya Shibata -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1290031 Title: Support japanese language Status in ubuntu-keyboard: Confirmed Status in ubuntu-keyboard package in Ubuntu: In Progress Bug description: Please support to input japanese language from ubuntu-keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1290031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290031] Re: Support japanese language
My apologies for long long long late reply. It seems that my merge request needs to fix a problem pointed by Michael and to be update for QtQuick 2.4 and Ubuntu.Components 1.3. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1290031 Title: Support japanese language Status in ubuntu-keyboard: Confirmed Status in ubuntu-keyboard package in Ubuntu: In Progress Bug description: Please support to input japanese language from ubuntu-keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1290031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290031] Re: Support japanese language
I resubmitted merge proposal, please review it. ** Changed in: ubuntu-keyboard Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1290031 Title: Support japanese language Status in ubuntu-keyboard: Confirmed Status in ubuntu-keyboard package in Ubuntu: In Progress Bug description: Please support to input japanese language from ubuntu-keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1290031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290031] Re: Support japanese language
** Branch linked: lp:~cosmos-door/ubuntu-keyboard/japanese-keyboard- rebooted -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1290031 Title: Support japanese language Status in ubuntu-keyboard: Confirmed Status in ubuntu-keyboard package in Ubuntu: In Progress Bug description: Please support to input japanese language from ubuntu-keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1290031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290031] Re: Support japanese language
I'm reworking with new ubuntu-keyboard layout. ** Changed in: ubuntu-keyboard Assignee: Michael Sheldon (michael-sheldon) => Mitsuya Shibata (cosmos-door) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1290031 Title: Support japanese language Status in Ubuntu Keyboard: In Progress Status in ubuntu-keyboard package in Ubuntu: In Progress Bug description: Please support to input japanese language from ubuntu-keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1290031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352142] Re: Doesn't load Japanese font on Ubuntu Touch
Just FYI: As already mentioned at #1346766, new released "Noto Sans CJK" is very beautiful and multi devices oriented. http://www.google.com/get/noto/cjk.html If noto font cjk will be debian packaged, we should switch to noto as default font for Touch. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 ** Bug watch added: Debian Bug tracker #754926 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1352142 Title: Doesn't load Japanese font on Ubuntu Touch Status in Ubuntu Translations: New Status in “ubuntu-touch-meta” package in Ubuntu: In Progress Bug description: Unity8 on Ubuntu Touch doesn't load Japanese font in Japanese environment. How to reproduce: 1. Install Ubuntu Touch 2. Set environment to Japanese at first boot 3. Reboot system (option) 4. Check whether a glyph come from Japanese font Expected result: Use Japanese gothic font (Droid Sans Japanese), and no Mojibake. Actual result: Use "AR PL Ukai CN" (Chinese serif font), and some glyphs are missing. Please refer attached image. Other information from phablet-shell: $ strings /proc/`pidof unity8`/environ | grep 'LANG\|LC' LANGUAGE=ja LC_TIME=ja_JP.UTF-8 LC_MONETARY=ja_JP.UTF-8 GDM_LANG=ja LC_ADDRESS=ja_JP.UTF-8 LANG=ja_JP.UTF-8 LC_TELEPHONE=ja_JP.UTF-8 LC_NAME=ja_JP.UTF-8 LC_MEASUREMENT=ja_JP.UTF-8 LC_IDENTIFICATION=ja_JP.UTF-8 LC_NUMERIC=ja_JP.UTF-8 LC_PAPER=ja_JP.UTF-8 => It seems that LANG env is vallid. For "音" (U+97F3), the glyph is visible in unity8, but use "AR PL UKai CN". Pleace replace '_' to space. $ fc-match 'sans:charset=!!(Dl___!!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=ja:charset=!!(Dl___!!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=en:charset=!!(Dl___!!rW+' ukai.ttc: "AR PL UKai CN" "Book" => Both of ukai and droid sans have U+97F3, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. For "楽" (U+697D), the glyph is invisible in unity8. Pleace replace '_' to space. $ fc-match 'sans:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=ja:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=en:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" => Because ukai doesn't have U+697D, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. $ sudo lsof -p `pidof unity8` | grep font unity8 2592 phablet memREG7,0 17151049 113683 /usr/share/fonts/truetype/arphic/ukai.ttc unity8 2592 phablet memREG7,0 415552 113610 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-L.ttf unity8 2592 phablet memREG7,0 333616 113622 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf unity8 2592 phablet memREG7,0 353824 113613 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf => Why loads ukai.ttc instead of DroidSansJapanese.ttf? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1352142/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352142] Re: Doesn't load Japanese font on Ubuntu Touch
@Gunnar, It looks good to me. On writbale-iamge, I installed fonts-takao-pgothic and rebooted it: $ sudo lsof -p `pidof unity8` | grep font unity8 2622 phablet memREG7,0 353824 83820 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf unity8 2622 phablet memREG7,0 6234746 104178 /usr/share/fonts/truetype/takao-gothic/TakaoPGothic.ttf unity8 2622 phablet memREG7,0 415552 83818 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-L.ttf unity8 2622 phablet memREG7,0 333616 83809 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf Load only Takao. It seems that displayed glyphs are ok. Thanks! ** Attachment added: "takao.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1352142/+attachment/4169955/+files/takao.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1352142 Title: Doesn't load Japanese font on Ubuntu Touch Status in Ubuntu Translations: New Status in “ubuntu-touch-meta” package in Ubuntu: In Progress Bug description: Unity8 on Ubuntu Touch doesn't load Japanese font in Japanese environment. How to reproduce: 1. Install Ubuntu Touch 2. Set environment to Japanese at first boot 3. Reboot system (option) 4. Check whether a glyph come from Japanese font Expected result: Use Japanese gothic font (Droid Sans Japanese), and no Mojibake. Actual result: Use "AR PL Ukai CN" (Chinese serif font), and some glyphs are missing. Please refer attached image. Other information from phablet-shell: $ strings /proc/`pidof unity8`/environ | grep 'LANG\|LC' LANGUAGE=ja LC_TIME=ja_JP.UTF-8 LC_MONETARY=ja_JP.UTF-8 GDM_LANG=ja LC_ADDRESS=ja_JP.UTF-8 LANG=ja_JP.UTF-8 LC_TELEPHONE=ja_JP.UTF-8 LC_NAME=ja_JP.UTF-8 LC_MEASUREMENT=ja_JP.UTF-8 LC_IDENTIFICATION=ja_JP.UTF-8 LC_NUMERIC=ja_JP.UTF-8 LC_PAPER=ja_JP.UTF-8 => It seems that LANG env is vallid. For "音" (U+97F3), the glyph is visible in unity8, but use "AR PL UKai CN". Pleace replace '_' to space. $ fc-match 'sans:charset=!!(Dl___!!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=ja:charset=!!(Dl___!!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=en:charset=!!(Dl___!!rW+' ukai.ttc: "AR PL UKai CN" "Book" => Both of ukai and droid sans have U+97F3, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. For "楽" (U+697D), the glyph is invisible in unity8. Pleace replace '_' to space. $ fc-match 'sans:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=ja:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=en:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" => Because ukai doesn't have U+697D, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. $ sudo lsof -p `pidof unity8` | grep font unity8 2592 phablet memREG7,0 17151049 113683 /usr/share/fonts/truetype/arphic/ukai.ttc unity8 2592 phablet memREG7,0 415552 113610 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-L.ttf unity8 2592 phablet memREG7,0 333616 113622 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf unity8 2592 phablet memREG7,0 353824 113613 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf => Why loads ukai.ttc instead of DroidSansJapanese.ttf? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1352142/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352142] Re: Doesn't load Japanese font on Ubuntu Touch
Sorry for missing version info. Above result on r157. I updated to r169, but not fixed yet. $ sudo lsof -p `pidof unity8` | grep font unity8 2616 phablet memREG7,0 4343844 83780 /usr/share/fonts/truetype/nanum/NanumGothic.ttf unity8 2616 phablet memREG7,0 415552 83818 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-L.ttf unity8 2616 phablet memREG7,0 333616 83809 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf unity8 2616 phablet memREG7,0 5177387 83822 /usr/share/fonts/truetype/wqy/wqy-microhei.ttc unity8 2616 phablet memREG7,0 353824 83820 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf unity8 2616 phablet memREG7,0 161680 41697 /usr/lib/arm-linux-gnueabihf/libfontconfig.so.1.8.0 NanumGothic.ttf is Korean font. Why is it loaded? Unity8 maily uses MicroHei and in some parts uses NanumGothic.ttf. It seems that does not use Japanese font. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1352142 Title: Doesn't load Japanese font on Ubuntu Touch Status in “unity8” package in Ubuntu: New Bug description: Unity8 on Ubuntu Touch doesn't load Japanese font in Japanese environment. How to reproduce: 1. Install Ubuntu Touch 2. Set environment to Japanese at first boot 3. Reboot system (option) 4. Check whether a glyph come from Japanese font Expected result: Use Japanese gothic font (Droid Sans Japanese), and no Mojibake. Actual result: Use "AR PL Ukai CN" (Chinese serif font), and some glyphs are missing. Please refer attached image. Other information from phablet-shell: $ strings /proc/`pidof unity8`/environ | grep 'LANG\|LC' LANGUAGE=ja LC_TIME=ja_JP.UTF-8 LC_MONETARY=ja_JP.UTF-8 GDM_LANG=ja LC_ADDRESS=ja_JP.UTF-8 LANG=ja_JP.UTF-8 LC_TELEPHONE=ja_JP.UTF-8 LC_NAME=ja_JP.UTF-8 LC_MEASUREMENT=ja_JP.UTF-8 LC_IDENTIFICATION=ja_JP.UTF-8 LC_NUMERIC=ja_JP.UTF-8 LC_PAPER=ja_JP.UTF-8 => It seems that LANG env is vallid. For "音" (U+97F3), the glyph is visible in unity8, but use "AR PL UKai CN". Pleace replace '_' to space. $ fc-match 'sans:charset=!!(Dl___!!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=ja:charset=!!(Dl___!!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=en:charset=!!(Dl___!!rW+' ukai.ttc: "AR PL UKai CN" "Book" => Both of ukai and droid sans have U+97F3, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. For "楽" (U+697D), the glyph is invisible in unity8. Pleace replace '_' to space. $ fc-match 'sans:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=ja:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=en:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" => Because ukai doesn't have U+697D, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. $ sudo lsof -p `pidof unity8` | grep font unity8 2592 phablet memREG7,0 17151049 113683 /usr/share/fonts/truetype/arphic/ukai.ttc unity8 2592 phablet memREG7,0 415552 113610 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-L.ttf unity8 2592 phablet memREG7,0 333616 113622 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf unity8 2592 phablet memREG7,0 353824 113613 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf => Why loads ukai.ttc instead of DroidSansJapanese.ttf? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1352142/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352142] Re: Doesn't load Japanese font on Ubuntu Touch
** Description changed: Unity8 on Ubuntu Touch doesn't load Japanese font in Japanese environment. How to reproduce: 1. Install Ubuntu Touch 2. Set environment to Japanese at first boot 3. Reboot system (option) 4. Check whether a glyph come from Japanese font Expected result: Use Japanese gothic font (Droid Sans Japanese), and no Mojibake. Actual result: Use "AR PL Ukai CN" (Chinese serif font), and some glyphs are missing. Please refer attached image. - Other information from phablet-shell: $ strings /proc/`pidof unity8`/environ | grep 'LANG\|LC' LANGUAGE=ja LC_TIME=ja_JP.UTF-8 LC_MONETARY=ja_JP.UTF-8 GDM_LANG=ja LC_ADDRESS=ja_JP.UTF-8 LANG=ja_JP.UTF-8 LC_TELEPHONE=ja_JP.UTF-8 LC_NAME=ja_JP.UTF-8 LC_MEASUREMENT=ja_JP.UTF-8 LC_IDENTIFICATION=ja_JP.UTF-8 LC_NUMERIC=ja_JP.UTF-8 LC_PAPER=ja_JP.UTF-8 => It seems that LANG env is vallid. For "音" (U+97F3), the glyph is visible in unity8, but use "AR PL UKai CN". - $ fc-match 'sans:charset=!!(Dl !!rW+' + Pleace replace '_' to space. + $ fc-match 'sans:charset=!!(Dl___!!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" - $ fc-match 'sans:lang=ja:charset=!!(Dl !!rW+' + $ fc-match 'sans:lang=ja:charset=!!(Dl___!!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" - $ fc-match 'sans:lang=en:charset=!!(Dl !!rW+' + $ fc-match 'sans:lang=en:charset=!!(Dl___!!rW+' ukai.ttc: "AR PL UKai CN" "Book" => Both of ukai and droid sans have U+97F3, - all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. + all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. For "楽" (U+697D), the glyph is invisible in unity8. - $ fc-match 'sans:charset=!!%g9 /?6HG' + Pleace replace '_' to space. + $ fc-match 'sans:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" - $ fc-match 'sans:lang=ja:charset=!!%g9 /?6HG' + $ fc-match 'sans:lang=ja:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" - $ fc-match 'sans:lang=en:charset=!!%g9 /?6HG' + $ fc-match 'sans:lang=en:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" => Because ukai doesn't have U+697D, - all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. + all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. $ sudo lsof -p `pidof unity8` | grep font unity8 2592 phablet memREG7,0 17151049 113683 /usr/share/fonts/truetype/arphic/ukai.ttc unity8 2592 phablet memREG7,0 415552 113610 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-L.ttf unity8 2592 phablet memREG7,0 333616 113622 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf unity8 2592 phablet memREG7,0 353824 113613 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf => Why loads ukai.ttc instead of DroidSansJapanese.ttf? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1352142 Title: Doesn't load Japanese font on Ubuntu Touch Status in “unity8” package in Ubuntu: New Bug description: Unity8 on Ubuntu Touch doesn't load Japanese font in Japanese environment. How to reproduce: 1. Install Ubuntu Touch 2. Set environment to Japanese at first boot 3. Reboot system (option) 4. Check whether a glyph come from Japanese font Expected result: Use Japanese gothic font (Droid Sans Japanese), and no Mojibake. Actual result: Use "AR PL Ukai CN" (Chinese serif font), and some glyphs are missing. Please refer attached image. Other information from phablet-shell: $ strings /proc/`pidof unity8`/environ | grep 'LANG\|LC' LANGUAGE=ja LC_TIME=ja_JP.UTF-8 LC_MONETARY=ja_JP.UTF-8 GDM_LANG=ja LC_ADDRESS=ja_JP.UTF-8 LANG=ja_JP.UTF-8 LC_TELEPHONE=ja_JP.UTF-8 LC_NAME=ja_JP.UTF-8 LC_MEASUREMENT=ja_JP.UTF-8 LC_IDENTIFICATION=ja_JP.UTF-8 LC_NUMERIC=ja_JP.UTF-8 LC_PAPER=ja_JP.UTF-8 => It seems that LANG env is vallid. For "音" (U+97F3), the glyph is visible in unity8, but use "AR PL UKai CN". Pleace replace '_' to space. $ fc-match 'sans:charset=!!(Dl___!!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=ja:charset=!!(Dl___!!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=en:charset=!!(Dl___!!rW+' ukai.ttc: "AR PL UKai CN" "Book" => Both of ukai and droid sans have U+97F3, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. For "楽" (U+697D), the glyph is invisible in unity8. Pleace replace '_' to space. $ fc-match 'sans:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=ja:charset=!!%g9___/?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=en:charset=!!%g9
[Touch-packages] [Bug 1352142] [NEW] Doesn't load Japanese font on Ubuntu Touch
Public bug reported: Unity8 on Ubuntu Touch doesn't load Japanese font in Japanese environment. How to reproduce: 1. Install Ubuntu Touch 2. Set environment to Japanese at first boot 3. Reboot system (option) 4. Check whether a glyph come from Japanese font Expected result: Use Japanese gothic font (Droid Sans Japanese), and no Mojibake. Actual result: Use "AR PL Ukai CN" (Chinese serif font), and some glyphs are missing. Please refer attached image. Other information from phablet-shell: $ strings /proc/`pidof unity8`/environ | grep 'LANG\|LC' LANGUAGE=ja LC_TIME=ja_JP.UTF-8 LC_MONETARY=ja_JP.UTF-8 GDM_LANG=ja LC_ADDRESS=ja_JP.UTF-8 LANG=ja_JP.UTF-8 LC_TELEPHONE=ja_JP.UTF-8 LC_NAME=ja_JP.UTF-8 LC_MEASUREMENT=ja_JP.UTF-8 LC_IDENTIFICATION=ja_JP.UTF-8 LC_NUMERIC=ja_JP.UTF-8 LC_PAPER=ja_JP.UTF-8 => It seems that LANG env is vallid. For "音" (U+97F3), the glyph is visible in unity8, but use "AR PL UKai CN". $ fc-match 'sans:charset=!!(Dl !!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=ja:charset=!!(Dl !!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=en:charset=!!(Dl !!rW+' ukai.ttc: "AR PL UKai CN" "Book" => Both of ukai and droid sans have U+97F3, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. For "楽" (U+697D), the glyph is invisible in unity8. $ fc-match 'sans:charset=!!%g9 /?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=ja:charset=!!%g9 /?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=en:charset=!!%g9 /?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" => Because ukai doesn't have U+697D, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. $ sudo lsof -p `pidof unity8` | grep font unity8 2592 phablet memREG7,0 17151049 113683 /usr/share/fonts/truetype/arphic/ukai.ttc unity8 2592 phablet memREG7,0 415552 113610 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-L.ttf unity8 2592 phablet memREG7,0 333616 113622 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf unity8 2592 phablet memREG7,0 353824 113613 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf => Why loads ukai.ttc instead of DroidSansJapanese.ttf? ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "font_test.png" https://bugs.launchpad.net/bugs/1352142/+attachment/4169106/+files/font_test.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1352142 Title: Doesn't load Japanese font on Ubuntu Touch Status in “unity8” package in Ubuntu: New Bug description: Unity8 on Ubuntu Touch doesn't load Japanese font in Japanese environment. How to reproduce: 1. Install Ubuntu Touch 2. Set environment to Japanese at first boot 3. Reboot system (option) 4. Check whether a glyph come from Japanese font Expected result: Use Japanese gothic font (Droid Sans Japanese), and no Mojibake. Actual result: Use "AR PL Ukai CN" (Chinese serif font), and some glyphs are missing. Please refer attached image. Other information from phablet-shell: $ strings /proc/`pidof unity8`/environ | grep 'LANG\|LC' LANGUAGE=ja LC_TIME=ja_JP.UTF-8 LC_MONETARY=ja_JP.UTF-8 GDM_LANG=ja LC_ADDRESS=ja_JP.UTF-8 LANG=ja_JP.UTF-8 LC_TELEPHONE=ja_JP.UTF-8 LC_NAME=ja_JP.UTF-8 LC_MEASUREMENT=ja_JP.UTF-8 LC_IDENTIFICATION=ja_JP.UTF-8 LC_NUMERIC=ja_JP.UTF-8 LC_PAPER=ja_JP.UTF-8 => It seems that LANG env is vallid. For "音" (U+97F3), the glyph is visible in unity8, but use "AR PL UKai CN". $ fc-match 'sans:charset=!!(Dl !!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=ja:charset=!!(Dl !!rW+' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=en:charset=!!(Dl !!rW+' ukai.ttc: "AR PL UKai CN" "Book" => Both of ukai and droid sans have U+97F3, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. For "楽" (U+697D), the glyph is invisible in unity8. $ fc-match 'sans:charset=!!%g9 /?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=ja:charset=!!%g9 /?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" $ fc-match 'sans:lang=en:charset=!!%g9 /?6HG' DroidSansJapanese.ttf: "Droid Sans" "Regular" => Because ukai doesn't have U+697D, all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid. $ sudo lsof -p `pidof unity8` | grep font unity8 2592 phablet memREG7,0 17151049 113683 /usr/share/fonts/truetype/arphic/ukai.ttc unity8 2592 phablet memREG7,0 415552 113610 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-L.ttf unity8 2592 phablet memREG7,0 333616 113622 /u
