[Bug 2058451] Re: CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058451 Title: CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2058451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058451] [NEW] CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed
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 following command. $ gnome-control-center system Expected result: * Open "Region & Language" menu. Actual result: * Hang up gnome-control-center. --- In this flow, gnome-control-center dumps following errors. $ gnome-control-center system 16:56:12.1249 cc-system-panel[16533]: WARNING: Could not set system time: GDBus.Error:org.freedesktop.timedate1.AutomaticTimeSyncEnabled: Automatic time synchronization is enabled 16:56:12.1252 cc-system-panel[16533]: WARNING: Could not set system time: GDBus.Error:org.freedesktop.timedate1.AutomaticTimeSyncEnabled: Automatic time synchronization is enabled 16:56:12.6869 **[16533]: WARNING: Couldn't get locale for language: en 16:56:12.6871 GnomeDesktop[16533]:CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed 16:56:12.7022 **[16533]: WARNING: Couldn't get locale for language: en 16:56:12.7023 GnomeDesktop[16533]:CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed My locale is following: $ locale -a C C.utf8 POSIX ja_JP.utf8 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:46~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 16:56:59 2024 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2024-03-20 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240319) ProcEnviron: LANG=ja_JP.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058451 Title: CRITICAL: gnome_get_language_from_locale: assertion '*locale != '\0'' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2058451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971025] Re: missing translation files
** 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 "Extension Manager" + * check UI is translated + + [Where problems could occur] + + * debian/control.in has "X-Ubuntu-Use-Langpack" for launchpad translation + * however Launchpad doesn't setup to translate gnome-shell-extention-manager (yet?) + * This change will just add mo files to package. + * The expected risk is that there is a problem with the translation file and the application cannot be started. + + + Original report: + + according to build log: https://launchpadlibrarian.net/597585355/buildlog_ubuntu-jammy-amd64.gnome-shell-extension-manager_0.3.0-0ubuntu1_BUILDING.txt.gz [1/52] /usr/bin/meson --internal msgfmthelper data/com.mattjakeman.ExtensionManager.desktop.in data/com.mattjakeman.ExtensionManager.desktop desktop ../data/../po [2/52] /usr/bin/meson --internal msgfmthelper data/com.mattjakeman.ExtensionManager.metainfo.xml.in data/com.mattjakeman.ExtensionManager.appdata.xml xml ../data/../po [3/52] msgfmt ../po/ca.po -o po/ca/LC_MESSAGES/extension-manager.mo [4/52] msgfmt ../po/cs.po -o po/cs/LC_MESSAGES/extension-manager.mo [5/52] msgfmt ../po/de.po -o po/de/LC_MESSAGES/extension-manager.mo [6/52] /usr/bin/meson --internal exe --unpickle /<>/obj-x86_64-linux-gnu/meson-private/meson_exe_glib-mkenums_5ae9820e699815ab0293defdd2f2011acb473410.dat [7/52] msgfmt ../po/es.po -o po/es/LC_MESSAGES/extension-manager.mo [8/52] msgfmt ../po/fr.po -o po/fr/LC_MESSAGES/extension-manager.mo [9/52] msgfmt ../po/hu.po -o po/hu/LC_MESSAGES/extension-manager.mo [10/52] msgfmt ../po/id_ID.po -o po/id_ID/LC_MESSAGES/extension-manager.mo [11/52] msgfmt ../po/it.po -o po/it/LC_MESSAGES/extension-manager.mo [12/52] msgfmt ../po/ja.po -o po/ja/LC_MESSAGES/extension-manager.mo [13/52] msgfmt ../po/nb.po -o po/nb/LC_MESSAGES/extension-manager.mo [14/52] msgfmt ../po/nl.po -o po/nl/LC_MESSAGES/extension-manager.mo [15/52] msgfmt ../po/nn.po -o po/nn/LC_MESSAGES/extension-manager.mo [16/52] msgfmt ../po/oc.po -o po/oc/LC_MESSAGES/extension-manager.mo [17/52] msgfmt ../po/pt_BR.po -o po/pt_BR/LC_MESSAGES/extension-manager.mo [18/52] msgfmt ../po/pl.po -o po/pl/LC_MESSAGES/extension-manager.mo [19/52] msgfmt ../po/tr.po -o po/tr/LC_MESSAGES/extension-manager.mo [20/52] msgfmt ../po/ru_RU.po -o po/ru_RU/LC_MESSAGES/extension-manager.mo generate .mo files. Installing po/ca/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/ca/LC_MESSAGES Installing po/cs/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/cs/LC_MESSAGES Installing po/de/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/de/LC_MESSAGES Installing po/es/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/es/LC_MESSAGES Installing po/fr/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/fr/LC_MESSAGES Installing po/hu/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/hu/LC_MESSAGES Installing po/id_ID/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/id_ID/LC_MESSAGES Installing po/it/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/it/LC_MESSAGES Installing po/ja/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/ja/LC_MESSAGES Installing po/nb/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/nb/LC_MESSAGES Installing po/nl/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/nl/LC_MESSAGES Installing po/nn/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/nn/LC_MESSAGES Installing po/oc/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/oc/LC_MESSAGES Installing po/pl/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/pl/LC_MESSAGES Installing po/pt_BR/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/pt_BR/LC_MESSAGES Installing po/tr/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/tr/LC_MESSAGES Installing po/ru_RU/LC_MESSAGES/extension-manager.mo to /<>/debian/gnome-shell-extension-manager/usr/share/locale/ru_RU/LC_MESSAGES install .mo files. drwxr-xr-x root/root 0 2022-04-19 22:32 ./ drwxr-xr-x root/root 0 2022-04-19 22:32 ./usr/
[Bug 1971025] Re: missing translation files
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. https://translations.launchpad.net/ubuntu/kinetic/+source/gnome-shell-extension-manager https://translations.launchpad.net/ubuntu/jammy/+source/gnome-shell-extension-manager At least, I think that "X-Ubuntu-Use-Langpack" should be removed on jammy. -- 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: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-manager/+bug/1971025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971025] Re: missing translation files
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 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: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-manager/+bug/1971025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971025] Re: missing translation files
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: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-manager/+bug/1971025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971025] Re: missing translation files
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: missing translation files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-manager/+bug/1971025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970453] Re: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set
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. https://bugs.launchpad.net/bugs/1970453 Title: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
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 also use another workaround using modprobe commented by kapper1224 instead of editing GRUB. $ echo "options i915 enable_guc=3" | sudo tee -a /etc/modprobe.d/i915.conf $ sudo update-initramfs -u -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
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- us/drivers/driversdetails?driverid=vdyvj&oscode=biosa&productcode=latitude-14-7490-laptop If this bug doesn't fixed with latest bios, please try lockup detector. $ sudo editor /etc/sysctl.d/99-panic.conf kernel.panic = 30 kernel.hardlockup_panic = 1 kernel.softlockup_panic = 1 $ sudo reboot This settings will reboot on a panic with 30 sec waits, and will panic on hard/soft lockup detection. After reboot, please check above settings is applied. $ sudo sysctl -a | grep panic If the freeze bug is reproduced and then the system is automatically rebooted, you can get a kernel crash dump by way of the following URL. https://ubuntu.com/server/docs/kernel-crash-dump -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969637] Re: lookup table appears bottom left of application
** 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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: lookup table appears bottom left of application To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968459 Title: IBus 1.5.26 does not enable on Xorg sesson To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1968459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964682 Title: IBus not starting properly at login to wayland with gnome-shell 42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
> 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 automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1946969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
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 seems that this should be "DISPLAY=:0".
2. Mozc call functions of libxcb on startup even if session is pure
wayland.
https://github.com/google/mozc/blob/master/src/unix/ibus/selection_monitor.cc#L108-L143
3. xcb_connect() will be blocked infinity.
On Ubuntu, xcb_connect(":1") will be blocked infinity.
You can reproduce this behaviour with simple code.
* Downlaod sample XCB code on Wikipedia.
https://en.wikipedia.org/wiki/XCB#Example
* Build sample code
$ sudo apt install gcc libxcb1-dev
$ gcc test.c -o test -lxcb
* Do logout and login and confirm not start Xwayland process
$ ps -fe | grep -i xwayland
(check no xwayland process)
* Check exists ":1" socket
$ ls -l /tmp/.X11-unix/X1
/tmp/.X11-unix/X1
* Execute thesample program with DISPLAY=":1"
DISPLAY=":1" ./test
The sample program will be blocked. You can comfirm this is blocked on
connect() via xcb_connect().
---
However I doesn't investigate how about Debian testing.
Could you check following status?
* What value of $DISPLAY of ibus-engin-mozc:
$ strings /proc/$(pidof ibus-engine-mozc)/environ | grep ^DISPLAY
* How number of x11 unix socket
$ ls -l /tmp/.X11-unix/
--
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 to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1946969/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947790] Re: marisa FTBFS on ppc64el
@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 components can build with gcc-11. To build ruby bindings, debian/rules will execute following steps. 1. extconf.rb geneates Makefile for test tool and bindings to link libmarisa 2. execute make command mkmf module in extconf.rb sets CC and some build related environment variables. But this variables will not refer host system directly, instead of this, mkmf refer to ruby embedded information. That is, mkmf will set CC as same as compile to build ruby. Ruby for ppc64el on impish/jammy has builded by gcc-10, mkmf will generate Makefile in which CC is "powerpc64le-linux-gnu-gcc-10". irb(main):004:0> p RbConfig::CONFIG['CC'] "powerpc64le-linux-gnu-gcc-10" => "powerpc64le-linux-gnu-gcc-10" Summarize, the gcc-10 is only needed to build ruby binding of marisa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947790 Title: marisa FTBFS on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marisa/+bug/1947790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947790] Re: marisa FTBFS on ppc64el
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: https://launchpadlibrarian.net/564182210/buildlog_ubuntu-impish- ppc64el.marisa_0.2.6-3ubuntu1_BUILDING.txt.gz --- (snip) The following packages were automatically installed and are no longer required: g++-10 libstdc++-10-dev Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: libffi8ubuntu1* The following NEW packages will be installed: cpp-11 g++-11 gcc-11 libffi8 libgcc-11-dev libstdc++-11-dev (snip) --- This build system is installed gcc-10 with any reason. As result of this, the build is succeeded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947790 Title: marisa FTBFS on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marisa/+bug/1947790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947790] Re: marisa FTBFS on ppc64el
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# cat mkmf.log
"powerpc64le-linux-gnu-gcc-10 -o conftest
-I/usr/include/powerpc64le-linux-gnu/ruby-2.7.0
-I/usr/include/ruby-2.7.0/ruby/backward -I/usr/include/ruby-2.7.0 -I.
-I../../include -Wdate-time -D_FORTIFY_SOURCE=2 -g -O3
-ffile-prefix-map=/build/ruby2.7-hkfe5T/ruby2.7-2.7.4=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC conftest.c -L.
-L/usr/lib/powerpc64le-linux-gnu -L../../lib/marisa/.libs -L.
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -fstack-protector-strong
-rdynamic -Wl,-export-dynamic -lruby-2.7 -lm -lc"
checked program was:
/* begin */
1: #include "ruby.h"
2:
3: int main(int argc, char **argv)
4: {
5: return !!argv[argc];
6: }
/* end */
root@nuc:/tmp/buildd/marisa-0.2.6/bindings/ruby# which
powerpc64le-linux-gnu-gcc-10
root@nuc:/tmp/buildd/marisa-0.2.6/bindings/ruby# echo $?
1
root@nuc:/tmp/buildd/marisa-0.2.6/bindings/ruby# irb
irb(main):004:0> p RbConfig::CONFIG['CC']
"powerpc64le-linux-gnu-gcc-10"
=> "powerpc64le-linux-gnu-gcc-10"
** Changed in: marisa (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/1947790
Title:
marisa FTBFS on ppc64el
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/marisa/+bug/1947790/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
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 mainly problem is user cannot input Japanese language with
+ IBus/Mozc.
+
+ One of the causes is Xwayland will not start on 21.10.
+ If there is no Xwayland process, gnome-shell/mutter will drop "--xim"
+ option of ibus-daemon and ibus-x11 process doesn't start.
+
+ For reasons unknown, IBus/Mozc does not work as a result.
+
+ Essentially, it should be fixed so that it works without Xwayland
+ and ibus-x11, but it takes time to investigate, so we will workaround
+ it by forcing Xwayland to start by xrefresh command.
+
+
+ [Test Plan]
+
+ 1. run Ubuntu 21.10 installer
+ 2. select Japanese language and keyboard
+ 3. finish to install and reboot
+ 4. login and complete gnome-initial-setup
+ 5. apply the mozc SRU and reboot
+ 6. login
+ 7. press Windows key + Space key and select Japanese (Mozc)
+ 8. startup gedit
+ 9. press Hankaku/Zenkaku key
+
+ If you can input Japanese language, then test is ok.
+
+
+ [Where problems could occur]
+
+ * Only affects to mozc installed machine, it is mainly Japanese user's
machine.
+ * The worst case is that those user cannot input Japanese language if the
update is invalid.
+ * However current 21.10 is already same state.
+
+
+ [Original description]
+
ibus-x11 does not start automatically due to Xwayland on demand by default.
IBus user does not input any cjkv languages before start to ibus-x11 or
xwayland process.
Steps to reproduce:
1. run Ubuntu 21.10 installer
2. select Japanese language
3. finish to install and reboot
4. login
5. reboot
6. login
7. push Windows key + Space key and select Japanese (Mozc)
8. run gedit
9. push Hankaku/Zenkaku key
Expected results:
show any Japanese characters
Actual results:
input any alphabetical key which I push
observation:
This may be mutter's matter.
Xwayland on demand by default
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1673
workaround:
1. run gnome-terminal and run command "ibus-daemon -rxd"
2. run any xwayland application like Libreoffice
3. use X session
4. restart IBus automatically when log in
exaple:
$ sudo editor /etc/xdg/autostart/ibus-autostart.desktop
[Desktop Entry]
Name=ibus-autostart
Exec=sh -c 'if [ "${IM_CONFIG_CHECK_ENV}" = "1" ] && [ "${XDG_SESSION_TYPE}"
= "wayland" ] && [ "${XDG_CURRENT_DESKTOP}" = "ubuntu:GNOME" ] || [
"${XDG_CURRENT_DESKTOP}" = "GNOME" ]; then ibus-daemon -rxd true; fi'
TryExec=ibus-daemon
Type=Application
--
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 to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1946969/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
> 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? -- 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 to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
> 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 ok? > Yeah, I saw that and assumed that it won't hurt... Is that duplication avoided with your idea with xrefresh (a command whose existence I wasn't aware of)? If it is, maybe that's a better approach. Thanks confirm. I agree to adopt im-config approach. Please SRU it. -- 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 to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
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 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu (snip) 143814381438 ?Ssl0:12 /usr/bin/gnome-shell 172414381438 ?Sl 0:00 /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.EDN3A1 -listen 4 -listen 5 -displayfd 6 -initfd 7 177117711438 ?Sl 0:01 ibus-daemon --panel disable -r --xim 179217711438 ?Sl 0:00 /usr/libexec/ibus-dconf 179417711438 ?Sl 0:01 /usr/libexec/ibus-extension-gtk3 184417711438 ?Sl 0:00 /usr/lib/ibus-mozc/ibus-engine-mozc --ibus 184717711438 ?SLl0:00 /usr/lib/mozc/mozc_server (snip) 170416961400 ?Sl 0:00 /usr/libexec/ibus-x11 --kill-daemon 177617761776 ?Ssl0:00 /usr/libexec/gsd-xsettings 180317711438 ?Sl 0:00 /usr/libexec/ibus-x11 --kill-daemon 180713021302 ?Sl 0:00 /usr/libexec/ibus-portal -- 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 to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
> 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 Type=Application EOF --- * xrefresh just refresh X screen. * if there is no ibus, this command will startup xwayland and refresh screen only. * if there is ibus, Mutter will startup XWayland and GNOME Shell restart ibus-daemon with --xim option * at the moment, Mutter doesn't remove xwayland even if all x11 apps exited. -- 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 to: https://bugs.launchpad.net/ubuntu/+bug/1946969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
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 "--xim" option[1] on wayland session[2] and there is no x11 apps. [1] https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/8adfc5b106d373bdae83b9a7b32e995f2a0d8331 [2] https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/1a0ec782b521dbcb66c31fe6f56784127f71926a Anyway, mozc require ibus-x11? or all ibus related ime require ibus-x11 on wayland? -- 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 to: https://bugs.launchpad.net/ubuntu/+bug/1946969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
** 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 to: https://bugs.launchpad.net/ubuntu/+bug/1946969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930880] Re: Booting Ubuntu 21.04 from DVD takes more than 30 minutes and its environment are corrupted
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 snapd.hold.service 1min 23.503s ModemManager.service 1min 19.831s bluetooth.service 1min 19.569s packagekit.service 1min 11.968s rsyslog.service 1min 6.454s gpu-manager.service 1min 2.006s NetworkManager.service 57.190s cups.service 49.711s accounts-daemon.service 40.643s dev-sr0.device -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930880 Title: Booting Ubuntu 21.04 from DVD takes more than 30 minutes and its environment are corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1930880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930880] [NEW] Booting Ubuntu 21.04 from DVD takes more than 30 minutes and its environment are corrupted
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: - Startup installer in 10 minutes at longest. Actual result: - Takes more than 30 minutes and so. - Failed to start installer and show up live desktop environment. Workaround: - Set "fsck.mode=skip" to boot params via GRUB menu entry. Notes: - Integrity check is passed with the DVD-R too. - USB boot can boot in less than few minutes. - The results is the same in both of UEFI and Legacy BIOS. Details: >From 21.04, the casper package will execute integrity check (casper- md5check.service) in any boot time. However intergrity check is very heavy task for physical DVD drive, it will waste CPU time. Therefore many services -- include NetworkManager and related network tasks -- will be timeouted, and then ubiquity and others doesn't startup. Finally interity check is finished after tens of minutes, desktop environment will be work. I attached journalctl log, many services are reached to timeout. $ egrep -i " time o| time[do]" journalctl.log Jun 04 06:04:04 ubuntu systemd[1]: NetworkManager.service: start operation timed out. Terminating. Jun 04 06:04:05 ubuntu systemd[1]: networkd-dispatcher.service: start operation timed out. Terminating. Jun 04 06:04:05 ubuntu systemd[1]: snapd.service: start operation timed out. Terminating. Jun 04 06:04:06 ubuntu systemd[1]: thermald.service: start operation timed out. Terminating. Jun 04 06:04:07 ubuntu systemd[1]: udisks2.service: start operation timed out. Terminating. Jun 04 06:04:07 ubuntu systemd[1]: wpa_supplicant.service: start operation timed out. Terminating. Jun 04 06:04:29 ubuntu systemd[1]: ModemManager.service: start operation timed out. Terminating. Jun 04 06:05:44 ubuntu systemd[1]: snapd.service: start operation timed out. Terminating. Jun 04 06:06:06 ubuntu dbus-daemon[1316]: [system] Failed to activate service 'fi.w1.wpa_supplicant1': timed out (service_start_timeout=25000ms) Jun 04 06:06:15 ubuntu sh[1463]: error: cannot communicate with server: timeout exceeded while waiting for response Jun 04 06:06:15 ubuntu snap[1461]: error: cannot communicate with server: timeout exceeded while waiting for response Jun 04 06:07:18 ubuntu systemd[1]: snapd.service: start operation timed out. Terminating. Jun 04 06:08:01 ubuntu snapd[1553]: daemon.go:440: adjusting startup timeout by 55s (pessimistic estimate of 30s plus 5s per snap) Jun 04 06:11:25 ubuntu systemd[1687]: pulseaudio.service: start operation timed out. Terminating. Jun 04 06:11:25 ubuntu systemd[1687]: tracker-extract.service: start operation timed out. Terminating. Jun 04 06:11:25 ubuntu systemd[1687]: tracker-miner-fs.service: start operation timed out. Terminating. Jun 04 06:12:56 ubuntu systemd[1687]: tracker-miner-fs.service: start operation timed out. Terminating. Jun 04 06:12:57 ubuntu systemd[1687]: tracker-extract.service: start operation timed out. Terminating. Jun 04 06:13:25 ubuntu dbus-daemon[1712]: [session uid=999 pid=1712] Failed to activate service 'org.gnome.OnlineAccounts': timed out (service_start_timeout=12ms) Jun 04 06:14:35 ubuntu systemd[1687]: tracker-extract.service: start operation timed out. Terminating. Jun 04 06:16:01 ubuntu snapd[2629]: daemon.go:440: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap) Jun 04 06:16:06 ubuntu systemd[1687]: org.gnome.Shell@x11.service: start operation timed out. Terminating. Jun 04 06:16:11 ubuntu systemd[1687]: org.gnome.Shell@x11.service: State 'stop-sigterm' timed out. Killing. Jun 04 06:17:43 ubuntu systemd[1687]: org.gnome.Shell@x11.service: start operation timed out. Terminating. Jun 04 06:17:48 ubuntu systemd[1687]: org.gnome.Shell@x11.service: State 'stop-sigterm' timed out. Killing. Jun 04 06:19:19 ubuntu systemd[1687]: org.gnome.Shell@x11.service: start operation timed out. Terminating. Jun 04 06:19:24 ubuntu systemd[1687]: org.gnome.Shell@x11.service: State 'stop-sigterm' timed out. Killing. Jun 04 06:20:08 ubuntu gnome-shell[2760]: Error loading calendars: Error calling StartServiceByName for org.gnome.Shell.CalendarServer: Timeout was reached Jun 04 06:20:14 ubuntu gnome-session[2260]: gnome-session-binary[2260]: GnomeDesktop-WARNING: Could not create transient scope for PID 2830: Timeout was reached Jun 04 06:20:14 ubuntu gnome-session-binary[2260]: GnomeDesktop-WARNING: Could not create transient scope for PID 2830: Timeout was reached Jun 04 06:20:14 ubuntu gnome-session[2260]: gnome-session-binary[2260]: GnomeDesktop-WARNING: Could not create transient scope for PID 2831: Timeout was reached Jun 04 06:20:14 ubuntu gnome-session[2260]: gnome-session-binary[2260]: GnomeDesktop-WARNING: Could not create transient scope for PID 2832: Timeout was reached J
[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
** 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: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1863414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864290] [NEW] FTBFS on python2 removal
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 directory `out_linux/Release' [1/629] cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out" FAILED: gen/proto_out/usage_stats/usage_stats.pb.h gen/proto_out/usage_stats/usage_stats.pb.cc cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out" /bin/sh: 1: python: not found ** Affects: mozc (Ubuntu) Importance: Undecided Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864290 Title: FTBFS on python2 removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1864290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864290] Re: FTBFS on python2 removal
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" https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1864290/+attachment/5330275/+files/workaround_python2_removal.debdiff ** Changed in: mozc (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864290 Title: FTBFS on python2 removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1864290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
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 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) isn't supported in binary mode, the default buffer size will be used" on simple APT usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/1863414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
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) isn't supported in binary mode, the default buffer size will be used" on simple APT usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/1863414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863825 Title: 20.04 apt update of python 3.8 gives errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1863825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843729] Re: byobu ftbfs in eoan
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. https://bugs.launchpad.net/bugs/1843729 Title: byobu ftbfs in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1843729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843729] Re: byobu ftbfs in eoan
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 upstream release until the proper fix lands upstream. 4. the source of package is more different than the original code. B. Not use quilt 1. we needs to revert debian/rules by our memory, when the proper fix upstream. 2. we can't run pep8 (only E117) until the proper fix lands upstream. 3. we can merge more simply in new upstream release. 4. the source of package has no difference with the original code. In my opinion, I think 1. is more useful for the future by A-1. But you worry about A-4/B-4? If so, I'm going to try to drop this differences by skip pep8/E117. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843729 Title: byobu ftbfs in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1843729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843729] Re: byobu ftbfs in eoan
@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. https://bugs.launchpad.net/bugs/1843729 Title: byobu ftbfs in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1843729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845845] Re: follow gnome-terminal libexec migration
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 go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1845845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845845] Re: follow gnome-terminal libexec migration
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 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 go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1845845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845845] Re: follow gnome-terminal libexec migration
** 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. - debian/postinst: + current debian/postinst: --- # Install correct .desktop file - if [ -x /usr/libexec/gnome-terminal-server ]; then + if [ -x /usr/lib/gnome-terminal/gnome-terminal-server ]; then ln -sf /usr/share/$PKG/desktop/$PKG.desktop /usr/share/applications/$PKG.desktop else ln -sf /usr/share/$PKG/desktop/$PKG.desktop.old /usr/share/applications/$PKG.desktop fi --- + + should be: + --- + # Install correct .desktop file + if [ -x /usr/libexec/gnome-terminal-server ]; then + ln -sf /usr/share/$PKG/desktop/$PKG.desktop /usr/share/applications/$PKG.desktop + else + ln -sf /usr/share/$PKG/desktop/$PKG.desktop.old /usr/share/applications/$PKG.desktop + fi + --- -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1845845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845845] [NEW] follow gnome-terminal libexec migration
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: --- # Install correct .desktop file if [ -x /usr/libexec/gnome-terminal-server ]; then ln -sf /usr/share/$PKG/desktop/$PKG.desktop /usr/share/applications/$PKG.desktop else ln -sf /usr/share/$PKG/desktop/$PKG.desktop.old /usr/share/applications/$PKG.desktop fi --- ** Affects: byobu (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/1845845 Title: follow gnome-terminal libexec migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1845845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843729] Re: byobu ftbfs in eoan
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. https://bugs.launchpad.net/bugs/1843729 Title: byobu ftbfs in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1843729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001
** 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 Title: Upgrade Noto Sans CJK fonts to version 2.001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001
** 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 Title: Upgrade Noto Sans CJK fonts to version 2.001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001
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" https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+attachment/5274199/+files/VirtualBox_Eoan_30_06_2019_14_58_27.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 Title: Upgrade Noto Sans CJK fonts to version 2.001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
"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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1828884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019
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. https://bugs.launchpad.net/bugs/1823444 Title: [SRU] The Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019
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. https://bugs.launchpad.net/bugs/1823444 Title: [SRU] The Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019
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. https://bugs.launchpad.net/bugs/1823444 Title: [SRU] The Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019
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 verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-disco verification-done-xenial -- 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 Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826818] Re: Missing openjdk-8 in disco
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. https://bugs.launchpad.net/bugs/1826818 Title: Missing openjdk-8 in disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1826818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826818] Re: Missing openjdk-8 in disco
> (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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826818 Title: Missing openjdk-8 in disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1826818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826818] [NEW] Missing openjdk-8 in disco
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| cosmic/universe | source openjdk-8 | 8u191-b12-2ubuntu0.16.04.1 | xenial-security | source openjdk-8 | 8u191-b12-2ubuntu0.16.04.1 | xenial-updates | source openjdk-8 | 8u191-b12-2ubuntu0.18.04.1 | bionic-security/universe | source openjdk-8 | 8u191-b12-2ubuntu0.18.04.1 | bionic-updates/universe | source openjdk-8 | 8u191-b12-2ubuntu0.18.10.1 | cosmic-security/universe | source openjdk-8 | 8u191-b12-2ubuntu0.18.10.1 | cosmic-updates/universe | source openjdk-8 | 8u212-b01-1| eoan/universe| source openjdk-8 | 8u212-b03-0ubuntu1 | eoan-proposed/universe | source Disco's openjdk-8 is removed at 4/13 accidentaly? https://launchpad.net/ubuntu/+source/openjdk-8/+publishinghistory ** Affects: openjdk-8 (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/1826818 Title: Missing openjdk-8 in disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1826818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019
> 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. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927929 However anthy package in trusty/precise is very very old. It seems that this patch couldn't be applied normally. ** Bug watch added: Debian Bug tracker #927929 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927929 -- 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 Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019
@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" https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1823444/+attachment/5257953/+files/xenial.debdiff -- 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 Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019
@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 Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: The Japanese Era name will be changed on May 1, 2019
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 start on 1 May 2019. - Mozc has A.D. to Japanese Era converter. + https://japan.kantei.go.jp/98_abe/statement/201904/_1.html - * "AD 2018"（２０１８ねん） => "Heisei 30th"（平成三十年） + Mozc has A.D. to Japanese Era converter. - Please support new era too as like following. + * "AD 2018"（２０１８ねん） => "Heisei 30th"（平成三十年） - * "AD 2018"（２０１８ねん） => "Heisei 30th"（平成三十年） - * "AD 2019"（２０１９ねん） => "Heisei 31th"（平成三十一年） - * "AD 2019"（２０１９ねん） => "Reiwa 1st"（令和元年） - * "AD 2020"（２０２０ねん） => "Reiwa 1st"（令和二年） + Please support new era too as like following. + + * "AD 2018"（２０１８ねん） => "Heisei 30th"（平成三十年） + * "AD 2019"（２０１９ねん） => "Heisei 31th"（平成三十一年） + * "AD 2019"（２０１９ねん） => "Reiwa 1st"（令和元年） + + [Test Case] + + * Enable Japanese InputMethod and Mozc. + + * Start "System Settings" + * Open "Regiaon and Language" menu + * Select "Japanese (Mozc)" from "Input Sources" + * Restart GUI session + + * Startup gedit. + + * Input following strings and confirm popping up new era by space key. + + * "れいわ" => "令和" + * "れいわ" => "㋿" (*1) + * "２０１８ねん" => "平成三十年" + * "２０１８ねん" => "平成三十年" + * "２０１９ねん" => "平成三十一年" + * "２０１９ねん" => "令和元年" + * "２０２０ねん" => "令和二年" + + * *1: Current fonts-noto-cjk package has no glyph of U+32FF. + + [Regression Potential] + + * There's basically no regression potential. ** Summary changed: - The Japanese Era name will be changed on May 1, 2019 + [SRU] The Japanese Era name will be changed on May 1, 2019 ** Patch removed: "mozc_2.23.2815.102+dfsg-2ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1823444/+attachment/5253321/+files/mozc_2.23.2815.102+dfsg-2ubuntu2.debdiff ** Patch added: "fix disco pacakage" https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1823444/+attachment/5257497/+files/disco.debdiff -- 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 Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823444 Title: [SRU] The Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019
debdiff mozc_2.20.2673.102+dfsg-2.dsc mozc_2.20.2673.102+dfsg-
2ubuntu1.dsc
Mozc on bionic does not support UTF-8 encoding data in source file.
** Patch added: "fix bionic package"
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1823444/+attachment/5257499/+files/bionic.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) => (unassigned)
** Changed in: mozc (Ubuntu Bionic)
Status: In Progress => Confirmed
** Changed in: mozc (Ubuntu Cosmic)
Status: In Progress => Confirmed
** Changed in: mozc (Ubuntu Disco)
Status: In Progress => Confirmed
--
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 Japanese Era name will be changed on May 1, 2019
To manage notifications about this bug go to:
https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: The Japanese Era name will be changed on May 1, 2019
** 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 (cosmos-door) ** Changed in: mozc (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: mozc (Ubuntu Cosmic) Status: Confirmed => In Progress ** Changed in: mozc (Ubuntu Disco) Status: Confirmed => In Progress -- 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: The Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: The Japanese Era name will be changed on May 1, 2019
> 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823444 Title: The Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: The Japanese Era name will be changed on May 1, 2019
@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. https://bugs.launchpad.net/bugs/1823444 Title: The Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823461] Re: Font hinting lost on chrome like browser
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" https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1823461/+attachment/5253679/+files/compare.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823461 Title: Font hinting lost on chrome like browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1823461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823423 Title: ibus ftbfs in disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1823423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823423 Title: ibus ftbfs in disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1823423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: The Japanese Era name will be changed on May 1, 2019
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" https://bugs.launchpad.net/mozc/+bug/1823444/+attachment/5253321/+files/mozc_2.23.2815.102+dfsg-2ubuntu2.debdiff -- 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: The Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] Re: The Japanese Era name will be changed on May 1, 2019
** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823444 Title: The Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823444] [NEW] The Japanese Era name will be changed on May 1, 2019
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"（２０１８ねん） => "Heisei 30th"（平成三十年） Please support new era too as like following. * "AD 2018"（２０１８ねん） => "Heisei 30th"（平成三十年） * "AD 2019"（２０１９ねん） => "Heisei 31th"（平成三十一年） * "AD 2019"（２０１９ねん） => "Reiwa 1st"（令和元年） * "AD 2020"（２０２０ねん） => "Reiwa 1st"（令和二年） ** Affects: mozc Importance: Unknown Status: Unknown ** Affects: mozc (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/google/mozc/issues #461 https://github.com/google/mozc/issues/461 ** Also affects: mozc via https://github.com/google/mozc/issues/461 Importance: Unknown Status: Unknown -- 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: The Japanese Era name will be changed on May 1, 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733194] Re: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq
** 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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733194 Title: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1733194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803813] [NEW] Please install mozc-utils-gui from language-selector
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, could you set "im:ja:ibus:mozc-utils-gui" and "im:ja:fcitx:mozc-utils-gui"? https://git.launchpad.net/ubuntu/+source/language- selector/tree/data/pkg_depends#n169 Can we add package on universe to pkg_depends? ** Affects: language-selector (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/1803813 Title: Please install mozc-utils-gui from language-selector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1803813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707426] Re: Other languages characters don't show in recovery mode
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 characters don't show in recovery mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1707426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726603] Re: Ubuntu 17.10 で Ubuntu on Xorg が選択されているのに Wayland でログインされる
** 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 ** Summary changed: - Ubuntu 17.10 で Ubuntu on Xorg が選択されているのに Wayland でログインされる + SessionMenuButton on greeter ignores new user session setting ** Description changed: + It seems that SessionMenuButton of js/gdm/loginDialog.js couldn't detect + new account settings. + + gnome-shell greeeter menu ignores new user session setting and login as + previous session selection. + + How to reproduce: + + 1. Existing user (userA) login as "Ubuntu on Xorg" + 2. Create new account (userB) from Settings application + 3. Check new account select default session +$ grep XSession /var/lib/AccountsService/users/userB +XSession= + 4. Logout exisiting user (userA) + 5. Select userB on GDM + 6. Check session selection + + Expected result: + * Mark "Ubuntu" session + * Login userB as Wayland session + * Result of "echo $XDG_SESSION_TYPE" should be "wayland" + + Actual result: + * Mark "Ubuntu on Xorg" + * Login userB as Wayland session + * Result of "echo $XDG_SESSION_TYPE" is "wayland" + + + --- + Original message: + + Ubuntu 17.10 で Ubuntu on Xorg が選択されているのに Wayland でログインされる + 再現方法 1.) 既存のユーザーのログイン画面で Ubuntu on Xorg を選択してログイン 2.) ログインしたユーザーで gnome control center を起動し、ユーザーを新規作成 3.) ログアウトし、ログイン画面で新規ユーザーをクリック 4.) 歯車ボタンをクリックすると自動的に Ubuntu on Xorg が選択されているので、そのままログイン 5.) コマンドを実行して X と Wayland のどちらが動いているか確認 $ loginctl show-session 11 -p Type Type=wayland ログイン画面で勝手に Ubuntu on Xorg が選択されているものの、実際には Wayland が動作しているようです。 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726603 Title: SessionMenuButton on greeter ignores new user session setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-jp-improvement/+bug/1726603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723358] Re: gnome-settings-daemon duplicate input-sources each login
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); <- it will be called
each boot time.
g_variant_unref (sources);
---
add_ibus_sources_from_locale() must be called only at first time (ie. sources
is empty).
---
-if (g_variant_n_children (sources) < 1)
+if (g_variant_n_children (sources) < 1) {
get_sources_from_xkb_config (manager);
+add_ibus_sources_from_locale (settings);
+}
g_variant_unref (sources);
---
Could you confirm this problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723358
Title:
gnome-settings-daemon duplicate input-sources each login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-jp-improvement/+bug/1723358/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723358] Re: Ubuntu 17.10でログインする度にibus-mozcの項目が増殖する
** 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 org.gnome.desktop.input-sources sources
+
+ Expected result:
+ [('xkb', 'us'), ('ibus', 'mozc-jp')]
+
+ Actual result:
+ [('xkb', 'us'), ('ibus', 'mozc-jp'), ('ibus', 'mozc-jp')]
+
+ => Duplicate input sources
+
+ ---
+ Original description:
+ Subject: Ubuntu 17.10でログインする度にibus-mozcの項目が増殖する
+
10月12日付けの artful-desktop-amd64.iso を Virtualbox にインストールし、
何度もログアウトや再起動を繰り返した所、トップバーのキーボードの「あ」が増える現象に遭遇しました。
** Summary changed:
- Ubuntu 17.10でログインする度にibus-mozcの項目が増殖する
+ gnome-settings-daemon duplicate input-sources each login
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-settings-daemon (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/1723358
Title:
gnome-settings-daemon duplicate input-sources each login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-jp-improvement/+bug/1723358/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?
> 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 font has no problem on debian, this problem cause other config on ubuntu system... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581160 Title: Switch to Noto Sans as default font for Japanese and/or Korean? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719938] Re: 17.10: No input method for CJK languages
> 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 => Invalid ** Changed in: gnome-settings-daemon (Ubuntu Artful) 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/1719938 Title: 17.10: No input method for CJK languages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1719938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719938] Re: 17.10: No input method for CJK languages
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" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1719938/+attachment/4965959/+files/initial-setup-input-sources.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719938 Title: 17.10: No input method for CJK languages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1719938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?
> Would that be a hinting configuration issue? You pointed it out clearly! Previous takao font has following configuration. TakaoGothic 18 hintnone false I add above fontconfig settings for Noto (Sans|Seirf|Mono) CJK JP. It works very well in my environment. ** Attachment added: "69-language-selector-ja.conf" https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+attachment/4965737/+files/69-language-selector-ja.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581160 Title: Switch to Noto Sans as default font for Japanese and/or Korean? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?
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" https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+attachment/4964293/+files/noto_glyph.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581160 Title: Switch to Noto Sans as default font for Japanese and/or Korean? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?
** 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. https://bugs.launchpad.net/bugs/1581160 Title: Switch to Noto Sans as default font for Japanese and/or Korean? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?
** 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. https://bugs.launchpad.net/bugs/1581160 Title: Switch to Noto Sans as default font for Japanese and/or Korean? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?
> 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" https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+attachment/4964271/+files/wikipedia_takao.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581160 Title: Switch to Noto Sans as default font for Japanese and/or Korean? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
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 #1719938 : ibus-mozc isn't enabled by default on Japanese locale Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719938] Re: 17.10: No input method for CJK languages
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 gnome-settings-daemon are replaced by gnome-initial-setup. https://github.com/GNOME/gnome-settings-daemon/commit/912c41a1b729d635d3b335c87653141781e9be9e If Ubuntu doesn't use gnome-intial-setup, should be engine_from_locale() reindroduced? ** Also affects: gnome-initial-setup (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/1719938 Title: 17.10: No input method for CJK languages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1719938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
> 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. Filed as another bug #1721023 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721023 Title: select window is pop up on top left of display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1721023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
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" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+attachment/4960511/+files/Screenshot%20from%202017-10-02%2022-46-48.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
> 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 ● im-config.service - Launch and configure input method Loaded: loaded (/usr/lib/systemd/user/im-config.service; disabled; vendor preset: enabled) Active: inactive (dead) since Mon 2017-10-02 22:45:14 JST; 26min ago Main PID: 1266 (code=exited, status=0/SUCCESS) 10月 02 22:45:14 ubuntu-ax2 systemd[1260]: Starting Launch and configure input method... 10月 02 22:45:14 ubuntu-ax2 systemd[1260]: Started Launch and configure input method. As my understand, user session unit is enabled by symlink on ~/.config/systemd/user/. If there is not symlink on the directory, "is-enabled" command will show "disabled". "/usr/lib/systemd/user" is vendor preset directory, and just show "vendor preset: enabled". If you exec "systemctl --user preset", it will create symlink on ~/.config/systemd/user. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
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 session from upstart to systemd, above upstart script is convert to systemd unit on 0.29-1ubuntu14. However this unit file uses initctl command, then this unit work on both of systemd and upstart installed system only. Legacy (Xorg) system will launches /etc/X11/Xsession.d/70im-config_launch and set STARTUP variable to exec /usr/bin/im-launch. All environment variables are set, no problem. Wayland system doesn't exec /etc/X11/Xsession.d, i.e. any mechanism to set environment variables is needed as like on Unity8/Mir. (old) systemd unit doesn't work by two reasons. 1. use initctl command of upstart 2. bind to graphical-session.target which is not launched on ubuntu If I understand correctly, graphical-session.target and graphical-session-pre.target will be launched for unity8 system and others. At artful, this target are not depended by any target and service. /usr/lib/gnome-session/run-systemd-session will stop these targets, but this script will be executed from unity.desktop only. How about use basic.target instead of graphical-session.target? I attach sample im-config.service. sudo cp im-config.service /usr/lib/systemd/user/ systemctl --user daemon-reload systemctl --user enable im-config.service (and restart session by logout and login) This service file will work about environment variables. $ env | grep -E '_IM|XMOD' CLUTTER_IM_MODULE=xim QT4_IM_MODULE=xim QT_IM_MODULE=ibus XMODIFIERS=@im=ibus GTK_IM_MODULE=ibus However suggestion window will be displayed on top left of display, not near cursor on gedit and gnome-termial. The reason isn't known. ** Attachment added: "im-config.service" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+attachment/4959803/+files/im-config.service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
> 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 and others is not be set on Wayland only, I thought this will be caused by systemd service file. However lightdm worked with Wayland, more need to be investigated further... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
> 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 (/usr/lib/systemd/user/im-config.service; static; vendor preset: enabled) Active: inactive (dead) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720184] Re: Please merge im-config 0.32-1 (main) from Debian unstable (main)
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 go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1720184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720250] Re: im-config configuration ignored with gdm3
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720250 Title: im-config configuration ignored with gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1720250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720184] Re: Please merge im-config 0.32-1 (main) from Debian unstable (main)
> 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 IBus 1.5.11 and lator. https://askubuntu.com/questions/746119/upgrade-ibus-or-export-ibus- enable-sync-mode-1-to-fix-intellij-android-studio IBUS_ENABULE_SYNC_MODE=0 means that ibus uses async process keyevent API. I worry that this change will be acceptable final freeze exception. -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1720184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720184] Re: Please merge im-config 0.32-1 (main) from Debian unstable (main)
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 https://github.com/ibus/ibus/issues/1847 ** Patch added: "sample debdiff" https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1720184/+attachment/4958191/+files/im-config.debdiff -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1720184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720184] [NEW] Please merge im-config 0.32-1 (main) from Debian unstable (main)
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, buggy and have alternatives (uim-toolbar-gtk{,3}).
* Use uim-toolbar-qt5 instead of uim-toolbar-qt (nonexistent).
* Wait a sec before starting uim-toolbar.
- uim-toolbar's spawning is too faster than desktop environment's starting.
-- Osamu Aoki Wed, 27 Sep 2017 21:15:24 +0900
im-config (0.31-1) unstable; urgency=medium
[ Osamu Aoki ]
* Start ibus with IBUS_ENABLE_SYNC_MODE=0. Closes: #812826, #838318, #876794
* Add Czech language strings to the desktop file. Closes: #868036
* im-config -l doesn't need GUI. Closes: #804067
* Update PO with trivial unfuzzy.
[ Boyuan Yang ]
* Refresh debian/copyright file as machine-readable format.
-- Osamu Aoki Tue, 26 Sep 2017 22:41:36 +0900
im-config (0.30-1) unstable; urgency=medium
* New upstream release acknowledging all NMU patches.
-- Osamu Aoki Wed, 07 Dec 2016 22:00:16 +0900
** Affects: im-config (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/1720184
Title:
Please merge im-config 0.32-1 (main) from Debian unstable (main)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1720184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718482] Re: byobu launch unknown icon on Ubuntu Dock
$ 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. Warning: DESKTOP_STARTUP_ID not set and no fallback available. Failed to register: Unable to acquire bus name 'us.kirkland.terminals.byobu' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718482 Title: byobu launch unknown icon on Ubuntu Dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1718482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
