[Bug 2058451] Re: CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed

2024-04-07 Thread Mitsuya Shibata
This bug does not reproduce on gnome-control-center 1:46.0.1-1ubuntu2. It is believed to have been fixed at some point. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 2058451] [NEW] CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed

2024-03-20 Thread Mitsuya Shibata
Public bug reported: On noble, gnome-control-center hangs to open system menu. How to reproduce: * Install Ubuntu 24.04 Desktop without en locale (for example, select Japanese language). * Open System settings app, and select "System" * Click "Region & Language" menu. or you can simplify

[Bug 1971025] Re: missing translation files

2022-05-04 Thread Mitsuya Shibata
** Description changed: + gnome-shell-extension-manager package is missing translation data. + + [Impact] + + * Only in gnome-shell-extension-manager UI. + + [Test Plan] + + * prepare an environment other than English locale + * install gnome-shell-extension-manager package + * start up

[Bug 1971025] Re: missing translation files

2022-05-04 Thread Mitsuya Shibata
According to the following URL, this field seems to be for translating universe packages. https://wiki.ubuntu.com/Translations/Universe_Translations_in_LP However translation pages of jammy and kinetic is not prepared.

[Bug 1971025] Re: missing translation files

2022-05-04 Thread Mitsuya Shibata
Could you remove "X-Ubuntu-Use-Langpack" for universe package? ** Patch added: "gnome-shell-extension-manager.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-manager/+bug/1971025/+attachment/5586818/+files/gnome-shell-extension-manager.debdiff -- You received this

[Bug 1971025] Re: missing translation files

2022-05-04 Thread Mitsuya Shibata
Ah, ok. debian/control.in has "X-Ubuntu-Use-Langpack: yes". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971025 Title: missing translation files To manage notifications about this bug go to:

[Bug 1971025] Re: missing translation files

2022-05-04 Thread Mitsuya Shibata
I tried to build on jammy, but mo files are archived to package. - debuild: ok - pbuilder-dist: ok This problem is on launchpad buildd? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971025 Title:

[Bug 1970453] Re: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set

2022-04-29 Thread Mitsuya Shibata
Is this related? https://lists.linuxfoundation.org/pipermail/iommu/2021-October/059955.html https://lists.linuxfoundation.org/pipermail/iommu/2021-November/060249.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11

2022-04-29 Thread Mitsuya Shibata
Thank you for your confirmation. If your system did not reboot, then CPU or other HWs hung up. This is firmware and/or hardware related bug, not software. I think this problem cannot is fixed by generic method, there is only workaround by "i915.enable_guc=3" on specific device. FYI, you can

[Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11

2022-04-28 Thread Mitsuya Shibata
Hi, 2. add "i915.enable_guc=3" to CMD line 3. Install/ Upgrade to Ubuntu 22.04 4. Use stock kernel 5.15 kernel from Ubuntu 22.04 This 2-4 is really needed? For example, you remove "i915.enable_guc=3" from CMD line, you can reproduce this bug? -- You received this bug notification because you

[Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11

2022-04-25 Thread Mitsuya Shibata
It seems like a problem on the firmware side. How about updating bios to latest? Especially in 1.20.0, there are some interesting comments. > - Fixed the issue where nothing is displayed on the screen when powering on the system. https://www.dell.com/support/home/en-

[Bug 1969637] Re: lookup table appears bottom left of application

2022-04-21 Thread Mitsuya Shibata
** Bug watch added: bugzilla.opensuse.org/ #1197873 https://bugzilla.opensuse.org/show_bug.cgi?id=1197873 ** Also affects: opensuse via https://bugzilla.opensuse.org/show_bug.cgi?id=1197873 Importance: Unknown Status: Unknown -- You received this bug notification because you are

[Bug 1968459] Re: IBus 1.5.26 does not enable on Xorg sesson

2022-04-10 Thread Mitsuya Shibata
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

[Bug 1964682] Re: IBus not starting properly at login to wayland with gnome-shell 42

2022-03-14 Thread Mitsuya Shibata
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

[Bug 1946969] Re: ibus-x11 does not start automatically

2021-10-24 Thread Mitsuya Shibata
> This was run on Debian testing (GNOME / Wayland): Thanks! Umm... It seems that "DISPLAY=:1" is valid... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946969 Title: ibus-x11 does not start

[Bug 1946969] Re: ibus-x11 does not start automatically

2021-10-24 Thread Mitsuya Shibata
Hi Gunnar, For future release, I'm trying to figure out the cause this problem. Here's what we know at this point. 1. DISPLAY=:1 For some reason, the DISPLAY env of ibus-daemon/ibus-engine-mozc is set to ":1". $ strings /proc/$(pidof ibus-engine-mozc)/environ | grep ^DISPLAY DISPLAY=:1 It

[Bug 1947790] Re: marisa FTBFS on ppc64el

2021-10-23 Thread Mitsuya Shibata
@Gunnar, > I see that only installing g++-10 would have been sufficient. Yes, g++-10 on build-depends is only needed for the bug. The source package of marisa will generate some components, libmarisa, perl/python/ruby bindings. This gcc-10/gcc-11 problem only affects ruby bindings. Other

[Bug 1947790] Re: marisa FTBFS on ppc64el

2021-10-23 Thread Mitsuya Shibata
Hi Gunnar, > The workaround for ruby was applied already in impish, but the marisa source which fails in jammy builds successfully in impish. I tried on impish, and it was FTBFS as same as jammy. The your build log of impish show following messages:

[Bug 1947790] Re: marisa FTBFS on ppc64el

2021-10-23 Thread Mitsuya Shibata
It seems that ruby on ppc64el requires gcc-10 instead of system defaults gcc-11. ref: https://bugs.launchpad.net/ubuntu/+source/ruby2.7/+bug/1943823 We should be add "g++-10 [ppc64el]," to Build-Depends in debian/control? --- In build system: root@nuc:/tmp/buildd/marisa-0.2.6/bindings/ruby#

[Bug 1946969] Re: ibus-x11 does not start automatically

2021-10-16 Thread Mitsuya Shibata
Hi Gunnar, > New proposal in this PPA: Many many thanks, confirmation and new patch. I tried it on 21.10, and works great. > Also, can someone please make the bug description 'SRU compatible': I updated description. ** Description changed: + [Impact] + + This is bugfix SRU. + + The

[Bug 1946969] Re: ibus-x11 does not start automatically

2021-10-15 Thread Mitsuya Shibata
> I just found that this problem is not present in Debian testing Indeed, Xwayland is living on Debian/testing and ibus-daemon is restarted with --xim by gnome-shell. However xlsclients show only ibus-x11/gsd-xsettings/gnome-shell only. Is any X11 related process started and then closed? --

[Bug 1946969] Re: ibus-x11 does not start automatically

2021-10-14 Thread Mitsuya Shibata
> When that reaches Debian, there is a risk that Ubuntu's desktop team won't accept to keep mozc in main (and on the ISO). I think so too. Unfortunately the Qt renderer and Gtk renderer seem to be exclusive at the moment. We still need Gtk renderer. > > However ibus-x11 process is doubled, it is

[Bug 1946969] Re: ibus-x11 does not start automatically

2021-10-14 Thread Mitsuya Shibata
Hi Gunnar, > In the meantime im-config is the natural package for a workaround. This PPA: It works for me. Thank you for your quick response! However ibus-x11 process is doubled, it is ok? PIDPGID SID TTY STAT TIME COMMAND 140014001400 ?Ssl0:00

[Bug 1946969] Re: ibus-x11 does not start automatically

2021-10-13 Thread Mitsuya Shibata
> 4. restart IBus automatically when log in More simple, but identical workaround: --- cat <<'EOF' | sudo tee /etc/xdg/autostart/launch-xwayland.desktop [Desktop Entry] Name=Launch XWayland on startup Exec=sh -c 'if [ "x$XDG_SESSION_TYPE" = "xwayland" ] ; then xrefresh; fi' TryExec=xrefresh

[Bug 1946969] Re: ibus-x11 does not start automatically

2021-10-13 Thread Mitsuya Shibata
I can reproduced this issue in new installed impish. However to reproduce this behaviour, you need to reboot on twice, isn't it? First reboot will startup gnome-initial setup with GNOME_SETUP_DISPLAY, this environment variable will cause starting ibus-daemon with "--xim" option. GNOME Shell drop

[Bug 1946969] Re: ibus-x11 does not start automatically

2021-10-13 Thread Mitsuya Shibata
** Changed in: ubuntu Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946969 Title: ibus-x11 does not start automatically To manage notifications about this bug go

[Bug 1930880] Re: Booting Ubuntu 21.04 from DVD takes more than 30 minutes and its environment are corrupted

2021-06-04 Thread Mitsuya Shibata
And result of systemd-analyze: 1h 10min 36.589s casper-md5check.service 6min 25.653s ubiquity.service 2min 18.423s plymouth-quit-wait.service 2min 1.331s snapd.seeded.service 1min 36.987s networkd-dispatcher.service 1min 26.938s apport.service 1min 25.643s

[Bug 1930880] [NEW] Booting Ubuntu 21.04 from DVD takes more than 30 minutes and its environment are corrupted

2021-06-04 Thread Mitsuya Shibata
Public bug reported: Booting Ubuntu 21.04 from DVD takes more than 30 minutes, and fails to start "Ubuntu Live CD installer" and many services. How to reproduce: - Burn Ubuntu 21.04 installer to DVD-R. - Start-up PC from the DVD-R. - Wait until the instaleler is displayed. Expected result: -

[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" on simple APT usag

2020-02-22 Thread Mitsuya Shibata
** Also affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863414 Title: Have many "/usr/lib/python3.8/subprocess.py:838:

[Bug 1864290] [NEW] FTBFS on python2 removal

2020-02-22 Thread Mitsuya Shibata
Public bug reported: mozc cannot build current focal because /usr/bin/python is removed. https://launchpad.net/ubuntu/+source/mozc/2.23.2815.102+dfsg-8build1 INFO: Running: ninja -v -C out_linux/Release ibus_mozc mozc_emacs_helper mozc_server mozc_renderer fcitx-mozc uim-mozc ninja: Entering

[Bug 1864290] Re: FTBFS on python2 removal

2020-02-22 Thread Mitsuya Shibata
Upstream of mozc package doesn't prepare to support python3 yet. I attach patch which just use "/usr/bin/python2" instead of "/usr/bin/python" on build package. Could you sponsor it? ** Patch added: "workaround_python2_removal.debdiff"

[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" on simple APT usag

2020-02-22 Thread Mitsuya Shibata
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

[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" on simple APT usag

2020-02-22 Thread Mitsuya Shibata
sorry, i commented to wrong ticket. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863414 Title: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1)

[Bug 1863825] Re: 20.04 apt update of python 3.8 gives errors

2020-02-22 Thread Mitsuya Shibata
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

[Bug 1843729] Re: byobu ftbfs in eoan

2019-10-11 Thread Mitsuya Shibata
Hi, @legovini I applied your suggestion. Could you review it? https://code.launchpad.net/~cosmos- door/ubuntu/+source/byobu/+git/byobu/+merge/373861 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1843729] Re: byobu ftbfs in eoan

2019-10-10 Thread Mitsuya Shibata
Hi, @legovini > Skip to be kept until the proper fix lands upstream. I want to ask about this in detail. A. Use quilt 1. we can just drop patch by dep3 tag, when the proper fix lands upstream. 2. we can run pep8 (all) until the proper fix lands upstream. 3. we needs to merge in new

[Bug 1843729] Re: byobu ftbfs in eoan

2019-10-09 Thread Mitsuya Shibata
@ahasenack Send merge request for package and set you as reviewer. Coudld you review it? https://code.launchpad.net/~cosmos-door/ubuntu/+source/byobu/+git/byobu/+merge/373861 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1845845] Re: follow gnome-terminal libexec migration

2019-09-30 Thread Mitsuya Shibata
Thank you for your follow-up regarding my fault status! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845845 Title: follow gnome-terminal libexec migration To manage notifications about this bug

[Bug 1845845] Re: follow gnome-terminal libexec migration

2019-09-29 Thread Mitsuya Shibata
Proposed merge request. could you review it? https://code.launchpad.net/~cosmos-door/byobu/lp1845485/+merge/373378 ** Branch linked: lp:~cosmos-door/byobu/lp1845485 ** Changed in: byobu (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member

[Bug 1845845] Re: follow gnome-terminal libexec migration

2019-09-29 Thread Mitsuya Shibata
** Description changed: Debian/Ubuntu package of gnome-terminal 3.34.0 moved the server binary from /usr/lib/gnome-terminal to /usr/libexec. byobu check /usr/lib/gnome-terminal/gnome-terminal-server in debian/postinst to decide installing which byobu.desktop or byobu.desktop.old.

[Bug 1845845] [NEW] follow gnome-terminal libexec migration

2019-09-29 Thread Mitsuya Shibata
Public bug reported: Debian/Ubuntu package of gnome-terminal 3.34.0 moved the server binary from /usr/lib/gnome-terminal to /usr/libexec. byobu check /usr/lib/gnome-terminal/gnome-terminal-server in debian/postinst to decide installing which byobu.desktop or byobu.desktop.old. debian/postinst:

[Bug 1843729] Re: byobu ftbfs in eoan

2019-09-29 Thread Mitsuya Shibata
I send Merge Request to fix ftbfs. https://code.launchpad.net/~cosmos-door/byobu/lp1843729/+merge/373372 Could you review it? ** Branch linked: lp:~cosmos-door/byobu/lp1843729 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001

2019-07-07 Thread Mitsuya Shibata
** Attachment added: "disco.png" https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+attachment/5275478/+files/disco.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834406

[Bug 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001

2019-07-07 Thread Mitsuya Shibata
Sorry for lately testing... On disco and bionic, I found no problem with Japanese locale. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834406 Title: Upgrade Noto Sans CJK fonts to version 2.001

[Bug 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001

2019-07-07 Thread Mitsuya Shibata
** Attachment added: "bionic.png" https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+attachment/5275479/+files/bionic.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834406

[Bug 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001

2019-06-30 Thread Mitsuya Shibata
Hi Gunnar, Łukasz, Thank you for your consideration! I confirmed fixed for eoan. And I'm going to test bionic/disco, if package upload to proposed. ** Attachment added: "VirtualBox_Eoan_30_06_2019_14_58_27.png"

[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

2019-05-19 Thread Mitsuya Shibata
"LC_ALL=ja_JP.utf8 date +%EY -d 20190501" depends on /usr/share/i18n/locales/ja_JP in locales package (src:glibc). And other related packages are listed here. https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2019-May/018309.html -- You received this bug notification because you are a

[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019

2019-05-04 Thread Mitsuya Shibata
I verified fixed in cosmic. ** Attachment added: "cosmic.png" https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1823444/+attachment/5261494/+files/cosmic.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019

2019-05-04 Thread Mitsuya Shibata
I verified fixed in disco. ** Attachment added: "disco.png" https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1823444/+attachment/5261493/+files/disco.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019

2019-05-04 Thread Mitsuya Shibata
I verified fixed in bionic. ** Attachment added: "bionic.png" https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1823444/+attachment/5261495/+files/bionic.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019

2019-05-04 Thread Mitsuya Shibata
I verified fixed in xenial. ** Attachment added: "xenial.png" https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1823444/+attachment/5261496/+files/xenial.png ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco

[Bug 1826818] Re: Missing openjdk-8 in disco

2019-04-30 Thread Mitsuya Shibata
Uploaded 8u212-b01-1 to disco. https://launchpad.net/ubuntu/+source/openjdk-8/8u212-b01-1 ** Changed in: openjdk-8 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1826818] Re: Missing openjdk-8 in disco

2019-04-28 Thread Mitsuya Shibata
> (From Debian) ROM; replaced by newer versions; Debian bug #915620 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915620 openjdk-8 should be removed from eoan too? ** Bug watch added: Debian Bug tracker #915620 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915620 -- You received

[Bug 1826818] [NEW] Missing openjdk-8 in disco

2019-04-28 Thread Mitsuya Shibata
Public bug reported: There is no openjdk-8 package in disco, but there is in eoan. $ rmadison openjdk-8 openjdk-8 | 8u77-b03-3ubuntu3 | xenial | source openjdk-8 | 8u162-b12-1| bionic/universe | source openjdk-8 | 8u181-b13-1

[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019

2019-04-25 Thread Mitsuya Shibata
> Sponsored to Eoan, Disco, Cosmic, and Bionic. > Sponsored to Xenial. Thanks. I will wait verification request. > Does someone have an ESM contact they can poke just in case they support ibus-anthy? I have no contact. Anyway, a patch for anthy is here.

[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019

2019-04-22 Thread Mitsuya Shibata
@Gunnar and @Simon Thanks! > Will these need to be done for Xenial and Trusty as well? > Possibly Xenial; Mitsuya has to decide how important it would be. Indeed. I attach a patch for xenial. ** Patch added: "xenial.debdiff"

[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019

2019-04-21 Thread Mitsuya Shibata
@Gunnar and ubuntu-sponsors I re-generated debdiff with debian's patch for disco, cosmic, bionic. Could you sponsor for this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823444 Title: [SRU] The

[Bug 1823444] Re: The Japanese Era name will be changed on May 1, 2019

2019-04-21 Thread Mitsuya Shibata
debdiff mozc_2.23.2815.102+dfsg-2ubuntu1.dsc mozc_2.23.2815.102+dfsg- 2ubuntu2.dsc ** Description changed: - New Japaenese era 'Reiwa' is expected to start on 1 May 2019 + [Impact] - https://japan.kantei.go.jp/98_abe/statement/201904/_1.html + New Japaenese era 'Reiwa' is expected to

[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019

2019-04-21 Thread Mitsuya Shibata
ic.debdiff ** Changed in: mozc (Ubuntu Bionic) Assignee: Mitsuya Shibata (cosmos-door) => (unassigned) ** Changed in: mozc (Ubuntu Cosmic) Assignee: Mitsuya Shibata (cosmos-door) => (unassigned) ** Changed in: mozc (Ubuntu Disco) Assignee: Mitsuya Shibata (cosmos-door) => (unas

[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019

2019-04-21 Thread Mitsuya Shibata
debdiff mozc_2.23.2815.102+dfsg-2.dsc mozc_2.23.2815.102+dfsg- 2ubuntu1.dsc ** Patch added: "fix cosmic package" https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1823444/+attachment/5257498/+files/cosmic.debdiff -- You received this bug notification because you are a member of Ubuntu

[Bug 1823444] Re: The Japanese Era name will be changed on May 1, 2019

2019-04-21 Thread Mitsuya Shibata
** Changed in: mozc (Ubuntu Disco) Assignee: (unassigned) => Mitsuya Shibata (cosmos-door) ** Changed in: mozc (Ubuntu Cosmic) Assignee: (unassigned) => Mitsuya Shibata (cosmos-door) ** Changed in: mozc (Ubuntu Bionic) Assignee: (unassigned) => Mitsuya Shibata (co

[Bug 1823444] Re: The Japanese Era name will be changed on May 1, 2019

2019-04-08 Thread Mitsuya Shibata
> As regards Debian, I happened to have a local git repository ready, so I have submitted a merge request: Thanks! I notified to Debian JP team. https://lists.debian.or.jp/pipermail/debian-devel/2019-April/000269.html -- You received this bug notification because you are a member of Ubuntu

[Bug 1823444] Re: The Japanese Era name will be changed on May 1, 2019

2019-04-08 Thread Mitsuya Shibata
@Gunnar Sure. I will try file the bug. Anyway, Do we have a time to merge mozc from debian until disco become final freeze? And I would like to make SRU for bionic andcosmic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1823461] Re: Font hinting lost on chrome like browser

2019-04-07 Thread Mitsuya Shibata
Thank you for notify. Gunnar's patch looks good to me. I attach compared image on 18.10. Top: original config Middle: Mohammad's patch: Use embedded font for example "生み出された". Bottom: Gunnar's patch: Looks the same as like original config. ** Attachment added: "compare.png"

[Bug 1823423] Re: ibus ftbfs in disco

2019-04-06 Thread Mitsuya Shibata
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 1823423] Re: ibus ftbfs in disco

2019-04-06 Thread Mitsuya Shibata
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.

[Bug 1823444] Re: The Japanese Era name will be changed on May 1, 2019

2019-04-06 Thread Mitsuya Shibata
Add DEP-3 fields to patch ** Patch removed: "mozc_2.23.2815.102+dfsg-2ubuntu2.debdiff" https://bugs.launchpad.net/mozc/+bug/1823444/+attachment/5253320/+files/mozc_2.23.2815.102+dfsg-2ubuntu2.debdiff ** Patch added: "mozc_2.23.2815.102+dfsg-2ubuntu2.debdiff"

[Bug 1823444] Re: The Japanese Era name will be changed on May 1, 2019

2019-04-06 Thread Mitsuya Shibata
** Patch added: "mozc_2.23.2815.102+dfsg-2ubuntu2.debdiff" https://bugs.launchpad.net/mozc/+bug/1823444/+attachment/5253320/+files/mozc_2.23.2815.102+dfsg-2ubuntu2.debdiff ** Tags added: bionic cosmic disco patch -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1823444] [NEW] The Japanese Era name will be changed on May 1, 2019

2019-04-06 Thread Mitsuya Shibata
Public bug reported: New Japaenese era 'Reiwa' is expected to start on 1 May 2019 https://japan.kantei.go.jp/98_abe/statement/201904/_1.html Mozc has A.D. to Japanese Era converter. * "AD 2018"(2018ねん) => "Heisei 30th"(平成三十年) Please support new era too as like following. * "AD

[Bug 1733194] Re: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq

2018-11-17 Thread Mitsuya Shibata
** Bug watch added: Debian Bug tracker #901389 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901389 ** Also affects: linux (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901389 Importance: Unknown Status: Unknown -- You received this bug notification because

[Bug 1803813] [NEW] Please install mozc-utils-gui from language-selector

2018-11-17 Thread Mitsuya Shibata
Public bug reported: mozc-utils-gui is removed from live image and will be dropped to universe. * https://lists.ubuntu.com/archives/ubuntu-desktop/2017-September/005212.html * https://discourse.ubuntu.com/t/removing-mozc-utils-gui-from-19-04/ To install mozc-utils-gui on installed environment,

[Bug 1707426] Re: Other languages characters don't show in recovery mode

2018-03-20 Thread Mitsuya Shibata
Already fixed via LP: #1752362 ** Changed in: friendly-recovery (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707426 Title: Other languages

[Bug 1726603] Re: Ubuntu 17.10 で Ubuntu on Xorg が選択されているのに Wayland でログインされる

2017-10-29 Thread Mitsuya Shibata
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-jp-improvement Status: New => Incomplete ** Changed in: ubuntu-jp-improvement Status: Incomplete => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed

[Bug 1723358] Re: gnome-settings-daemon duplicate input-sources each login

2017-10-13 Thread Mitsuya Shibata
Hi seb128, It seems that this bug occur from 3.26.1-0ubuntu2 for bug #1719938. In debian/patches/ubuntu_ibus_configs.patch: --- if (g_variant_n_children (sources) < 1) get_sources_from_xkb_config (manager); +add_ibus_sources_from_locale (settings); <-

[Bug 1723358] Re: Ubuntu 17.10でログインする度にibus-mozcの項目が増殖する

2017-10-13 Thread Mitsuya Shibata
** Description changed: + How to reproduce: + 1. Login to Ubuntu 17.10 + 2. Exec on terminal + $ gsettings get org.gnome.desktop.input-sources sources + [('xkb', 'us'), ('ibus', 'mozc-jp')] + 3. Logout + 4. (re-)Login to Ubuntu 17.10 + 5. Exec on terminal + $ gsettings get

[Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

2017-10-11 Thread Mitsuya Shibata
> Hmm.. Wondering if that hinting configuration would improve the experience for Chinese and Korean too. Sorry, I don't know. Anyway, fonts-ipafont/fonts-ipaexfont/fonts-vlgothic has a similar patches as "ubuntu specific patch", i.e. original debian packages don't have its patches. If smaller

[Bug 1719938] Re: 17.10: No input method for CJK languages

2017-10-11 Thread Mitsuya Shibata
> gnome-settings-daemon 3.26.1-0ubuntu2 was released with similar patch. Thank you for your information. I confirmed it and close this ticket. Thanks! ** Changed in: ubuntu-translations Status: New => Invalid ** Changed in: gnome-initial-setup (Ubuntu Artful) Status: Confirmed =>

[Bug 1719938] Re: 17.10: No input method for CJK languages

2017-10-09 Thread Mitsuya Shibata
I created patch. This patch will fix but #1514544 too. Building patched package is completed successfully. I'll test the package after tomorrow. ** Patch added: "initial-setup-input-sources.patch"

[Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

2017-10-09 Thread Mitsuya Shibata
> Would that be a hinting configuration issue? You pointed it out clearly! Previous takao font has following configuration. TakaoGothic 18 hintnone false

[Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

2017-10-07 Thread Mitsuya Shibata
For example "全", its spaces between vertical bars should be same. But displayed glyph has more space for 1st and 2nd vertical bars than 2nd and 3rd vertical bars. Is this settings problem? or is other glyph used? ** Attachment added: "noto_glyph.png"

[Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

2017-10-07 Thread Mitsuya Shibata
** Attachment added: "terminal_noto.png" https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+attachment/4964272/+files/terminal_noto.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

2017-10-07 Thread Mitsuya Shibata
** Attachment added: "wikipedia_noto.png" https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+attachment/4964273/+files/wikipedia_noto.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

2017-10-07 Thread Mitsuya Shibata
> sudo apt purge fonts-takao-* > sudo apt install fonts-noto-cjk-extra I tried it. Displayed glyphs are not so bad. However all glyphs are slightly thin. And it seems that some glyphs are not Noto's glyph... ** Attachment added: "wikipedia_takao.png"

[Bug 1720250] Re: im-config configuration ignored with gdm3

2017-10-04 Thread Mitsuya Shibata
My apologies for late and sparse reply... > So I have uploaded yet another variant to the PPA. Thank you for your upload. Suggestion window become to visible! -- I will tackle following issues related to input method until 18.04 release. - bug #1721023 : suggestion window position - bug

[Bug 1719938] Re: 17.10: No input method for CJK languages

2017-10-03 Thread Mitsuya Shibata
Before artful, unity-settings-daemon (based on gnome-settings-daemon) setup input sources by locale. http://bazaar.launchpad.net/~unity-settings-daemon-team/unity-settings-daemon/trunk/view/head:/plugins/keyboard/gsd-keyboard-manager.c#L505 However already commented, this code in

[Bug 1720250] Re: im-config configuration ignored with gdm3

2017-10-03 Thread Mitsuya Shibata
Hi Ian and Gunnar, Thank you for details about systemd target and new package! The profile.d version works on my environment too with gedit (gtk app) and setup-mozc (qt app). However suggestion window doesn't show up... -- You received this bug notification because you are a member of Ubuntu

[Bug 1720250] Re: im-config configuration ignored with gdm3

2017-10-03 Thread Mitsuya Shibata
> So no need to set a symlink in the users' HOME. > Maybe it's not a problem at all. I just noticed a difference. Yes, you are right. My old comment is just reason why "list-unit-files" show "disabled". > Then it's probably not related to im-config at all, but rather ibus/wayland/whatever.

[Bug 1721023] [NEW] select window is pop up on top left of display

2017-10-03 Thread Mitsuya Shibata
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

[Bug 1720250] Re: im-config configuration ignored with gdm3

2017-10-02 Thread Mitsuya Shibata
Unfortunately, gnome-terminal and gedit show select window on top left... (this behavior same as old im-config on wayland, not problem on xorg). ** Attachment added: "Screenshot from 2017-10-02 22-46-48.png"

[Bug 1720250] Re: im-config configuration ignored with gdm3

2017-10-02 Thread Mitsuya Shibata
Just for your information, I attached zesty's result about systemd. ** Attachment added: "imservice.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+attachment/4960512/+files/imservice.log -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1720250] Re: im-config configuration ignored with gdm3

2017-10-02 Thread Mitsuya Shibata
> I uploaded a test version of im-config here: Thanks! > Even if the variables seem to be properly set, I made this observation: > > $ systemctl --user list-unit-files | grep im-config > im-config.service disabled $ systemctl --user status im-config.service

[Bug 1720250] Re: im-config configuration ignored with gdm3

2017-10-01 Thread Mitsuya Shibata
Fist of all, I don't know details about history of upstart/unity and user session system. There is no conclusion, just my research. --- For Unity8/Mir, upstart script of im-config was added LP #1433831 This Ubuntu only script should be removed from im-config package. Since switching user

[Bug 1720250] Re: im-config configuration ignored with gdm3

2017-09-29 Thread Mitsuya Shibata
> With lightdm the im-config variables are preserved also on GNOME shell (with or without Wayland). Umm... With GDM3, Ubuntu.Xorg session correctly set GTK_IM_MODULE and other environments. In this case, im-config will be launched from /etc/X11/Xsession.d/70im-config_launch. If GTK_IM_MODULE

[Bug 1720250] Re: im-config configuration ignored with gdm3

2017-09-29 Thread Mitsuya Shibata
> im-config provides a systemd *user* service. Oh, sorry... $ systemctl --user list-unit-files | grep im-config im-config.service static $ systemctl --user status im-config.service ● im-config.service - Launch and configure input method Loaded: loaded

[Bug 1720184] Re: Please merge im-config 0.32-1 (main) from Debian unstable (main)

2017-09-29 Thread Mitsuya Shibata
I see. Thank you for uploading! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720184 Title: Please merge im-config 0.32-1 (main) from Debian unstable (main) To manage notifications about this bug

[Bug 1720250] Re: im-config configuration ignored with gdm3

2017-09-29 Thread Mitsuya Shibata
My wayland session is same result. Anyway, /usr/lib/systemd/user/im-config.service is installed, but systemctl doesn't show that unit file. Is it OK? $ systemctl list-unit-files | grep im-config (nothing) -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1720184] Re: Please merge im-config 0.32-1 (main) from Debian unstable (main)

2017-09-29 Thread Mitsuya Shibata
> As regards "IBUS_ENABLE_SYNC_MODE=0", how serious do you consider the issue Sorry, I don,t know how serious. At least, my environment is no problem. As following link, Android Studio users are use "IBUS_ENABLE_SYNC_MODE=1" to avoid IBus+Java problem. However it seems that it will be fixed

[Bug 1720184] Re: Please merge im-config 0.32-1 (main) from Debian unstable (main)

2017-09-28 Thread Mitsuya Shibata
NOTE: "IBUS_ENABLE_SYNC_MODE=0" will be fix on Korean and xim problems. However this fix will be cause with Java application. Please refer: https://github.com/ibus/ibus/issues/1847#issuecomment-205230677 ** Bug watch added: github.com/ibus/ibus/issues #1847

[Bug 1720184] [NEW] Please merge im-config 0.32-1 (main) from Debian unstable (main)

2017-09-28 Thread Mitsuya Shibata
Public bug reported: Please merge im-config 0.32-1 (main) from Debian unstable (main) Changelogs from ubuntu package: im-config (0.32-1) unstable; urgency=medium [ HIGUCHI Daisuke (VDR dai) ] * Disable uim-toolbar-gtk{,3}-systray due to outdated. - They are outdated,

[Bug 1718482] Re: byobu launch unknown icon on Ubuntu Dock

2017-09-24 Thread Mitsuya Shibata
$ gnome-terminal --app-id us.kirkland.terminals.byobu -e bash Option “-e” is deprecated and might be removed in a later version of gnome-terminal. Use “-- ” to terminate the options and put the command line to execute after it.

  1   2   3   4   5   >