[Group.of.nepali.translators] [Bug 1871471] Re: flash end of life soon, suggest remove from hirsute and also handle stable releases

[Gunnar Hjalmarsson]

Dummies of pepperflashplugin-nonfree are now in place in the stable
releases.

As regards hirsute it's no longer urgent, since there is a dummy there
too. Probably it's easiest to just wait until Debian drops it from
unstable.

** Changed in: pepperflashplugin-nonfree (Ubuntu Groovy)
   Status: Triaged => Fix Released

** Changed in: pepperflashplugin-nonfree (Ubuntu Focal)
   Status: Triaged => Fix Released

** Changed in: pepperflashplugin-nonfree (Ubuntu Bionic)
   Status: Triaged => Fix Released

** Changed in: pepperflashplugin-nonfree (Ubuntu Xenial)
   Status: Triaged => Fix Released

** Changed in: oem-priority
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1871471

Title:
  flash end of life soon, suggest remove from hirsute and also handle
  stable releases

Status in OEM Priority Project:
  Fix Released
Status in adobe-flashplugin package in Ubuntu:
  Fix Released
Status in flashplugin-nonfree package in Ubuntu:
  Fix Released
Status in pepperflashplugin-nonfree package in Ubuntu:
  Confirmed
Status in adobe-flashplugin source package in Xenial:
  Fix Released
Status in flashplugin-nonfree source package in Xenial:
  Fix Released
Status in pepperflashplugin-nonfree source package in Xenial:
  Fix Released
Status in adobe-flashplugin source package in Bionic:
  Fix Released
Status in flashplugin-nonfree source package in Bionic:
  Fix Released
Status in pepperflashplugin-nonfree source package in Bionic:
  Fix Released
Status in adobe-flashplugin source package in Focal:
  Fix Released
Status in flashplugin-nonfree source package in Focal:
  Fix Released
Status in pepperflashplugin-nonfree source package in Focal:
  Fix Released
Status in adobe-flashplugin source package in Groovy:
  Fix Released
Status in pepperflashplugin-nonfree source package in Groovy:
  Fix Released
Status in adobe-flashplugin source package in Hirsute:
  Fix Released
Status in pepperflashplugin-nonfree source package in Hirsute:
  Confirmed
Status in pepperflashplugin-nonfree package in Debian:
  Unknown

Bug description:
  Hello, Adobe has said they will not be supporting Flash beyond 2020:

  https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html
  https://theblog.adobe.com/adobe-flash-update/

  I think we shouldn't ship Flash in hirsute. Does our agreement with
  Adobe for distributing Flash installers or code allow us to skip
  shipping Flash in hirsute?

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1871471/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1871471] Re: flash end of life soon, suggest remove from hirsute

[Gunnar Hjalmarsson]

** Also affects: flashplugin-nonfree (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: adobe-flashplugin (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: pepperflashplugin-nonfree (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: flashplugin-nonfree (Ubuntu Hirsute)
   Importance: Undecided
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
   Status: Fix Released

** Also affects: adobe-flashplugin (Ubuntu Hirsute)
   Importance: Undecided
 Assignee: Chris Coulson (chrisccoulson)
   Status: Fix Released

** Also affects: pepperflashplugin-nonfree (Ubuntu Hirsute)
   Importance: Undecided
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
   Status: Confirmed

** Also affects: flashplugin-nonfree (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: adobe-flashplugin (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: pepperflashplugin-nonfree (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: flashplugin-nonfree (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: adobe-flashplugin (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: pepperflashplugin-nonfree (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: flashplugin-nonfree (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: adobe-flashplugin (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: pepperflashplugin-nonfree (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: adobe-flashplugin (Ubuntu Groovy)
   Status: New => Fix Released

** Changed in: adobe-flashplugin (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: adobe-flashplugin (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: adobe-flashplugin (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: flashplugin-nonfree (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: flashplugin-nonfree (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: flashplugin-nonfree (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: flashplugin-nonfree (Ubuntu Groovy)
   Status: New => Fix Released

** Changed in: flashplugin-nonfree (Ubuntu Groovy)
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** No longer affects: flashplugin-nonfree (Ubuntu Hirsute)

** No longer affects: flashplugin-nonfree (Ubuntu Groovy)

** Changed in: pepperflashplugin-nonfree (Ubuntu Groovy)
   Importance: Undecided => High

** Changed in: pepperflashplugin-nonfree (Ubuntu Groovy)
   Status: New => Triaged

** Changed in: pepperflashplugin-nonfree (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: pepperflashplugin-nonfree (Ubuntu Focal)
   Status: New => Triaged

** Changed in: pepperflashplugin-nonfree (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: pepperflashplugin-nonfree (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: pepperflashplugin-nonfree (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: pepperflashplugin-nonfree (Ubuntu Xenial)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1871471

Title:
  flash end of life soon, suggest remove from hirsute

Status in OEM Priority Project:
  Triaged
Status in adobe-flashplugin package in Ubuntu:
  Fix Released
Status in flashplugin-nonfree package in Ubuntu:
  Fix Released
Status in pepperflashplugin-nonfree package in Ubuntu:
  Confirmed
Status in adobe-flashplugin source package in Xenial:
  Fix Released
Status in flashplugin-nonfree source package in Xenial:
  Fix Released
Status in pepperflashplugin-nonfree source package in Xenial:
  Triaged
Status in adobe-flashplugin source package in Bionic:
  Fix Released
Status in flashplugin-nonfree source package in Bionic:
  Fix Released
Status in pepperflashplugin-nonfree source package in Bionic:
  Triaged
Status in adobe-flashplugin source package in Focal:
  Fix Released
Status in flashplugin-nonfree source package in Focal:
  Fix Released
Status in pepperflashplugin-nonfree source package in Focal:
  Triaged
Status in adobe-flashplugin source package in Groovy:
  Fix Released
Status in pepperflashplugin-nonfree source package in Groovy:
  Triaged
Status in adobe-flashplugin source package in Hirsute:
  Fix Released
Status in pepperflashplugin-nonfree source package in Hirsute:
  Confirmed
Status in pepperflashplugin-nonfree package in Debian:
  Unknown

Bug description:
  Hello, Adobe has said they will not be supporting Flash beyond 2020:

  

[Group.of.nepali.translators] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

[Gunnar Hjalmarsson]

I have verified the testcase

- on bionic using version 2.56.4-0ubuntu0.18.04.5 of the libglib2.0-*
packages from bionic-proposed and version 1.5.17-3ubuntu5.3 of the ibus
packages from ppa:ubuntu-security-proposed/ppa

- on xenial using version 2.48.2-0ubuntu4.5 of the libglib2.0-* packages
from xenial-proposed and version 1.5.11-1ubuntu2.4 of the ibus packages
from ppa:ubuntu-security-proposed/ppa

As regards the autopkgtest failures, please see comment #29.

Marked the disco bug task as "Won't Fix" since disco is EOL.

** Tags removed: verification-needed-bionic verification-needed-xenial
** Tags added: verification-done-bionic verification-done-xenial

** Changed in: glib2.0 (Ubuntu Disco)
   Importance: High => Undecided

** Changed in: glib2.0 (Ubuntu Disco)
   Status: Fix Committed => Won't Fix

** Changed in: glib2.0 (Ubuntu Disco)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1844853

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Committed
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in glib2.0 source package in Disco:
  Won't Fix
Status in glib2.0 source package in Eoan:
  Fix Committed
Status in glib2.0 source package in Focal:
  Fix Released
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali

[Group.of.nepali.translators] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Gunnar Hjalmarsson]

** Changed in: ibus (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1580463

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is restarted. This was omitted from the initial im-config
  upload which resulted in bug #1588197. Test cases ensuring this is
  working properly 

[Group.of.nepali.translators] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

[Gunnar Hjalmarsson]

** Changed in: glib2.0 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1844853

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Fix Committed
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in glib2.0 source package in Disco:
  Fix Committed
Status in glib2.0 source package in Eoan:
  Fix Committed
Status in glib2.0 source package in Focal:
  Fix Released
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

[Gunnar Hjalmarsson]

** Description changed:

+ [Impact]
+ 
+ IBus was broken for Qt applications as a regression due to the fix of
+ CVE-2019-14822. As a result the IBus patch was disabled temporarily,
+ which fixed IBus from a usability POV.
+ 
+ The real fix has been made in glib2.0, and the proposed updates in the
+ below PPA will allow the IBus patch to be re-enabled.
+ 
+ https://launchpad.net/~gunnarhj/+archive/ubuntu/glib2.0
+ 
+ [Test Case]
+ 
+  * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
+- Upgrade the ibus packages from
+  https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
+- Install some IBus input method, e.g. ibus-libpinyin
+- Install some Qt application, e.g. Kate
+ 
+ * Relogin
+ 
+ * Add the input method to the input sources
+ 
+ * Open the Qt app and try to input something using the IBus IM
+ 
+ => Find that only latin letters get inputted
+ 
+ * Upgrade the glib2.0 packages from {eoan,disco,bionic,xenial}-proposed
+ 
+ * Relogin (maybe reboot)
+ 
+ * Open the Qt app and try to input something using the IBus IM
+ 
+ => Find that the transliteration works as expected
+ 
+ [Regression Potential]
+ 
+ The applicable patches origin from glib upstream:
+ https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
+ Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30. 
+ 
+ [Original description]
+ 
  Kubuntu Release 18.04.3 LTS
  
  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
  
  Observed behavior:
  ibus is not usable anymore in Qt applications.
  
  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:
  
- Bus::open: Connect ibus failed! 
+ Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon
  
  This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed
  that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus
  functionality in Qt applications.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

** Also affects: glib2.0 (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: ibus (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Focal)
   Importance: High
   Status: Fix Committed

** Also affects: ibus (Ubuntu Focal)
   Importance: High
   Status: Fix Released

** Also affects: glib2.0 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ibus (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ibus (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: ibus (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** No longer affects: ibus (Ubuntu Xenial)

** No longer affects: ibus (Ubuntu Bionic)

** No longer affects: ibus (Ubuntu Disco)

** No longer affects: ibus (Ubuntu Eoan)

** Changed in: glib2.0 (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: glib2.0 (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: glib2.0 (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu Disco)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Disco)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: glib2.0 (Ubuntu Eoan)
   Importance

[Group.of.nepali.translators] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Gunnar Hjalmarsson]

Reopening the ibus (ubuntu) task.

Background:
The change in ibus 1.5.19-1ubuntu3, which set the abstract socket path to 
'unix:tmpdir=/tmp/ibus', was upstreamed and is now included in the 1.5.21 
source. However, the path proved to not work well on BSD systems:

https://github.com/ibus/ibus/issues/2116

That resulted in a new upstream approach to make the path
indistinguishable, and to make a long story short, the path is about to
be changed in 1.5.22 to 'unix:tmpdir=$XDG_CACHE_HOME/ibus'. To prevent
yet another change in this respect in the ff cycle, I propose that we
change it in eoan again and add two upstream commits so Ubuntu 19.10 is
released with the new (final?) path.

Proposed upload in this PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus

** Bug watch added: github.com/ibus/ibus/issues #2116
   https://github.com/ibus/ibus/issues/2116

** Changed in: ibus (Ubuntu)
   Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1580463

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes 

[Group.of.nepali.translators] [Bug 1838346] Re: Support Japanese new era "令和 (Reiwa)"

[Gunnar Hjalmarsson]

Fixed in unstable/eoan AFAICT.

** Changed in: anthy (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1838346

Title:
  Support Japanese new era "令和 (Reiwa)"

Status in anthy package in Ubuntu:
  Fix Released
Status in anthy source package in Xenial:
  New

Bug description:
  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）

  [Impact]
  Users who run Ubuntu in Japanese.

  [Test cases]
  == Character maps / font support ==

  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

   - SQUARE ERA NAME HEISEI: ㍻
   - SQUARE ERA NAME REIWA: 令和 (in a single glyph)

  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex characters. If that is the
  case, the unicode data supports the new character, but the selected
  font does not include the new glyph.

  == Typing / input methods ==

  1) Type in 'heisei'
  2) Verify that the input method in use gives you an option "平成", and 
optionally also the square era glyph.
  3) Type in 'reiwa'
  4) Verify that the input method in use gives you an option that includes 
"令和", and possibly also the square era glyph (if supported for Heisei)

  5) Type in the following strings, and verify that the options are provided in 
the input method:
  * "れいわ"(reiwa) => "令和"
  * "れいわ"(reiwa) => "㋿"
  * "２０１８ねん"(2018nenn) => "平成三十年"
  * "２０１９ねん"(2019nenn) => "平成三十一年"
  * "２０１９ねん"(2019nenn) => "令和元年"
  * "２０２０ねん"(2020nenn) => "令和二年"

  [Regression potential]
  This is a potentially large change as it impacts font display, character sets 
as well as date conversions. As such, extreme care should be taken to ensure 
that regressions are avoided, such that dates previous to May 1, 2019 continue 
to display as before, and dates onward are displayed with the new era symbols. 
The included test cases account for verifying the continued behavior or 
previous dates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/anthy/+bug/1838346/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

[Gunnar Hjalmarsson]

fonts-noto-cjk fixed in disco and bionic via bug #1834406.

** Changed in: fonts-noto-cjk (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: fonts-noto-cjk (Ubuntu Disco)
   Status: New => Fix Released

** No longer affects: fonts-noto-cjk (Ubuntu Cosmic)

** No longer affects: gnome-characters (Ubuntu Cosmic)

** No longer affects: gucharmap (Ubuntu Cosmic)

** No longer affects: icu (Ubuntu Cosmic)

** No longer affects: openjdk-8 (Ubuntu Cosmic)

** No longer affects: poppler-data (Ubuntu Cosmic)

** No longer affects: unicode-data (Ubuntu Cosmic)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1828884

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

Status in Poppler:
  New
Status in fonts-noto-cjk package in Ubuntu:
  Fix Released
Status in gucharmap package in Ubuntu:
  New
Status in icu package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in poppler-data package in Ubuntu:
  New
Status in unicode-data package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Xenial:
  New
Status in gucharmap source package in Xenial:
  New
Status in icu source package in Xenial:
  New
Status in libreoffice source package in Xenial:
  Fix Released
Status in libreoffice-l10n source package in Xenial:
  Fix Released
Status in mozc source package in Xenial:
  Fix Released
Status in openjdk-8 source package in Xenial:
  New
Status in poppler-data source package in Xenial:
  New
Status in unicode-data source package in Xenial:
  New
Status in fonts-noto-cjk source package in Bionic:
  Fix Released
Status in gucharmap source package in Bionic:
  New
Status in icu source package in Bionic:
  New
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Released
Status in mozc source package in Bionic:
  Fix Released
Status in openjdk-8 source package in Bionic:
  New
Status in poppler-data source package in Bionic:
  New
Status in unicode-data source package in Bionic:
  New
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released
Status in mozc source package in Cosmic:
  Fix Released
Status in fonts-noto-cjk source package in Disco:
  Fix Released
Status in gnome-characters source package in Disco:
  New
Status in gucharmap source package in Disco:
  New
Status in icu source package in Disco:
  New
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released
Status in mozc source package in Disco:
  Fix Released
Status in openjdk-8 source package in Disco:
  New
Status in poppler-data source package in Disco:
  New
Status in unicode-data source package in Disco:
  New

Bug description:
  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）

  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the
  work needed, and general test cases for verifying that things are
  working as expected.

  [Impact]
  Users who run Ubuntu in Japanese.

  [Test cases]

  == Date conversion ==

  On applications that support writing dates in long form, or with
  symbols to denote era (either in X00.00.00 format or in GG1G5G1G
  format  (G- glyph; X- character):

  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"

  == Date output ==

  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"

  === Displaying formatted year for Japanese era with glibc ===

  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)

  == Character maps / font support ==

  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

   - SQUARE ERA NAME HEISEI:  ㍻
   - SQUARE ERA NAME REIWA:   令和 (in a single glyph)

  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex characters. If that is the
  case, the 

[Group.of.nepali.translators] [Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

[Gunnar Hjalmarsson]

** Changed in: fonts-noto-cjk (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1828884

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

Status in Poppler:
  New
Status in fonts-noto-cjk package in Ubuntu:
  Fix Released
Status in gucharmap package in Ubuntu:
  New
Status in icu package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in poppler-data package in Ubuntu:
  New
Status in unicode-data package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Xenial:
  New
Status in gucharmap source package in Xenial:
  New
Status in icu source package in Xenial:
  New
Status in libreoffice source package in Xenial:
  Fix Released
Status in libreoffice-l10n source package in Xenial:
  Fix Released
Status in mozc source package in Xenial:
  Fix Released
Status in openjdk-8 source package in Xenial:
  New
Status in poppler-data source package in Xenial:
  New
Status in unicode-data source package in Xenial:
  New
Status in fonts-noto-cjk source package in Bionic:
  New
Status in gucharmap source package in Bionic:
  New
Status in icu source package in Bionic:
  New
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Released
Status in mozc source package in Bionic:
  Fix Released
Status in openjdk-8 source package in Bionic:
  New
Status in poppler-data source package in Bionic:
  New
Status in unicode-data source package in Bionic:
  New
Status in fonts-noto-cjk source package in Cosmic:
  New
Status in gnome-characters source package in Cosmic:
  New
Status in gucharmap source package in Cosmic:
  New
Status in icu source package in Cosmic:
  New
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released
Status in mozc source package in Cosmic:
  Fix Released
Status in openjdk-8 source package in Cosmic:
  New
Status in poppler-data source package in Cosmic:
  New
Status in unicode-data source package in Cosmic:
  New
Status in fonts-noto-cjk source package in Disco:
  New
Status in gnome-characters source package in Disco:
  New
Status in gucharmap source package in Disco:
  New
Status in icu source package in Disco:
  New
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released
Status in mozc source package in Disco:
  Fix Released
Status in openjdk-8 source package in Disco:
  New
Status in poppler-data source package in Disco:
  New
Status in unicode-data source package in Disco:
  New

Bug description:
  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）

  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the
  work needed, and general test cases for verifying that things are
  working as expected.

  [Impact]
  Users who run Ubuntu in Japanese.

  [Test cases]

  == Date conversion ==

  On applications that support writing dates in long form, or with
  symbols to denote era (either in X00.00.00 format or in GG1G5G1G
  format  (G- glyph; X- character):

  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"

  == Date output ==

  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"

  === Displaying formatted year for Japanese era with glibc ===

  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)

  == Character maps / font support ==

  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

   - SQUARE ERA NAME HEISEI:  ㍻
   - SQUARE ERA NAME REIWA:   令和 (in a single glyph)

  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex characters. If that is the
  case, the unicode data supports the new character, but the selected
  font does not include the new glyph.

  == Typing / input methods ==

  1) Type in 

[Group.of.nepali.translators] [Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

[Gunnar Hjalmarsson]

Dropping the fonts-noto-cjk Xenial task, since Noto is not default font
for Japanese in Xenial. (Takao is.)

** No longer affects: fonts-noto-cjk (Ubuntu Xenial)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1828884

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

Status in fonts-noto-cjk package in Ubuntu:
  New
Status in gnome-characters package in Ubuntu:
  New
Status in gucharmap package in Ubuntu:
  New
Status in icu package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in poppler-data package in Ubuntu:
  New
Status in unicode-data package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Xenial:
  New
Status in gucharmap source package in Xenial:
  New
Status in icu source package in Xenial:
  New
Status in libreoffice source package in Xenial:
  New
Status in libreoffice-l10n source package in Xenial:
  New
Status in mozc source package in Xenial:
  Fix Released
Status in openjdk-8 source package in Xenial:
  New
Status in poppler-data source package in Xenial:
  New
Status in unicode-data source package in Xenial:
  New
Status in fonts-noto-cjk source package in Bionic:
  New
Status in gnome-characters source package in Bionic:
  New
Status in gucharmap source package in Bionic:
  New
Status in icu source package in Bionic:
  New
Status in libreoffice source package in Bionic:
  New
Status in libreoffice-l10n source package in Bionic:
  New
Status in mozc source package in Bionic:
  Fix Released
Status in openjdk-8 source package in Bionic:
  New
Status in poppler-data source package in Bionic:
  New
Status in unicode-data source package in Bionic:
  New
Status in fonts-noto-cjk source package in Cosmic:
  New
Status in gnome-characters source package in Cosmic:
  New
Status in gucharmap source package in Cosmic:
  New
Status in icu source package in Cosmic:
  New
Status in libreoffice source package in Cosmic:
  New
Status in libreoffice-l10n source package in Cosmic:
  New
Status in mozc source package in Cosmic:
  Fix Released
Status in openjdk-8 source package in Cosmic:
  New
Status in poppler-data source package in Cosmic:
  New
Status in unicode-data source package in Cosmic:
  New
Status in fonts-noto-cjk source package in Disco:
  New
Status in gnome-characters source package in Disco:
  New
Status in gucharmap source package in Disco:
  New
Status in icu source package in Disco:
  New
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released
Status in mozc source package in Disco:
  Fix Released
Status in openjdk-8 source package in Disco:
  New
Status in poppler-data source package in Disco:
  New
Status in unicode-data source package in Disco:
  New

Bug description:
  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）

  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the
  work needed, and general test cases for verifying that things are
  working as expected.

  [Impact]
  Users who run Ubuntu in Japanese.

  [Test cases]

  == Date conversion ==

  On applications that support writing dates in long form, or with
  symbols to denote era (either in X00.00.00 format or in GG1G5G1G
  format  (G- glyph; X- character):

  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"

  == Date output ==

  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"

  === Displaying formatted year for Japanese era with glibc ===

  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)

  == Character maps / font support ==

  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

   - SQUARE ERA NAME HEISEI:  ㍻
   - SQUARE ERA NAME REIWA:   令和 (in a single glyph)

  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex characters. If that is the
  case, the unicode data supports the new 

[Group.of.nepali.translators] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Gunnar Hjalmarsson]

** Bug watch added: github.com/ibus/ibus/issues #2095
   https://github.com/ibus/ibus/issues/2095

** Also affects: ibus via
   https://github.com/ibus/ibus/issues/2095
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1580463

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Unknown
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is 

[Group.of.nepali.translators] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Gunnar Hjalmarsson]

IBus is not always launched via im-config when GNOME is involved. In
Ubuntu 19.10 im-config will be disabled by default in Wayland sessions.
So to achieve a consistent address of ibus daemon, it's better to change
the default in ibus itself. Attached please find a debdiff with a
proposed fix.

Once this change is in the archive, the equivalent im-config patch can
be dropped.

** Patch added: "ibus-fix-eoan_lp1580463.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463/+attachment/5259090/+files/ibus-fix-eoan_lp1580463.debdiff

** Tags added: patch

** Also affects: ibus (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ibus (Ubuntu Xenial)

** No longer affects: ibus (Ubuntu Yakkety)

** Changed in: ibus (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ibus (Ubuntu)
   Status: New => In Progress

** Changed in: ibus (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1580463

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are

[Group.of.nepali.translators] [Bug 1823444] Re: [SRU] The Japanese Era name will be changed on May 1, 2019

[Gunnar Hjalmarsson]

** Also affects: mozc (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: mozc (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: mozc (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: mozc (Ubuntu Xenial)
 Assignee: (unassigned) => Mitsuya Shibata (cosmos-door)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1823444

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

Status in Mozc:
  New
Status in mozc package in Ubuntu:
  Fix Released
Status in mozc source package in Xenial:
  In Progress
Status in mozc source package in Bionic:
  In Progress
Status in mozc source package in Cosmic:
  In Progress
Status in mozc source package in Disco:
  In Progress
Status in mozc source package in Eoan:
  Fix Released

Bug description:
  [Impact]

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"（令和元年）

  [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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mozc/+bug/1823444/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1760758] Re: /usr/lib/ibus/ibus-engine-libpinyin:ibus-engine-libpinyin: pinyin.cpp:991\357\274\232bool pinyin_set_zhuyin_scheme(pinyin_context_t*, ZhuyinScheme): \34

[Gunnar Hjalmarsson]

In 16.04 och 17.10 ibus-sunpinyin is the default IM for Simplified
Chinese through IBus, and ibus-libpinyin just an option available in
universe. Setting priority "Low".

** Also affects: im-config (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: im-config (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ibus-libpinyin (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: im-config (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ibus-libpinyin (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: im-config (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: ibus-libpinyin (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: ibus-libpinyin (Ubuntu Bionic)
   Status: New => Fix Released

** No longer affects: im-config (Ubuntu Bionic)

** No longer affects: im-config (Ubuntu Artful)

** No longer affects: im-config (Ubuntu Xenial)

** No longer affects: im-config (Ubuntu)

** Changed in: ibus-libpinyin (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: ibus-libpinyin (Ubuntu Artful)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1760758

Title:
  /usr/lib/ibus/ibus-engine-libpinyin:ibus-engine-libpinyin:
  pinyin.cpp:991\357\274\232bool
  pinyin_set_zhuyin_scheme(pinyin_context_t*, ZhuyinScheme):
  \345\201\207\350\256\276 \342\200\230(0)\342\200\231
  \345\244\261\350\264\245\343\200\202

Status in ibus-libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin source package in Xenial:
  New
Status in ibus-libpinyin source package in Artful:
  New
Status in ibus-libpinyin source package in Bionic:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
ibus-libpinyin.  This problem was most recently seen with package version 
1.7.3-2, the problem page at 
https://errors.ubuntu.com/problem/93033df7be22fcd00507d4744cd85fe4a72b727f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1760758/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1760124] [NEW] Unnecessary conflicts fields for -hinted and -unhinted packages

[Gunnar Hjalmarsson]

Public bug reported:

[Impact]

Conflicts fields unnecessarily prevent users from installing both fonts-
roboto-hinted and fonts-roboto-unhinted on 16.04. The issue has been
fixed:

https://salsa.debian.org/fonts-team/fonts-roboto/commit/47e35245

and is not present in 17.10 or bionic.

[Test Case]

Install fonts-roboto-hinted and fonts-roboto-unhinted from xenial-
proposed and confirm that they can coexist.

[Regression Potential]

None.

** Affects: fonts-roboto (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: fonts-roboto (Ubuntu Xenial)
 Importance: Medium
 Assignee: Gunnar Hjalmarsson (gunnarhj)
 Status: In Progress

** Affects: fonts-roboto (Ubuntu Artful)
 Importance: Undecided
 Status: Fix Released

** Also affects: fonts-roboto (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: fonts-roboto (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: fonts-roboto (Ubuntu)
   Importance: Medium => Undecided

** Changed in: fonts-roboto (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: fonts-roboto (Ubuntu)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

** Changed in: fonts-roboto (Ubuntu Artful)
   Status: New => Fix Released

** Changed in: fonts-roboto (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: fonts-roboto (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: fonts-roboto (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1760124

Title:
  Unnecessary conflicts fields for -hinted and -unhinted packages

Status in fonts-roboto package in Ubuntu:
  Fix Released
Status in fonts-roboto source package in Xenial:
  In Progress
Status in fonts-roboto source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Conflicts fields unnecessarily prevent users from installing both
  fonts-roboto-hinted and fonts-roboto-unhinted on 16.04. The issue has
  been fixed:

  https://salsa.debian.org/fonts-team/fonts-roboto/commit/47e35245

  and is not present in 17.10 or bionic.

  [Test Case]

  Install fonts-roboto-hinted and fonts-roboto-unhinted from xenial-
  proposed and confirm that they can coexist.

  [Regression Potential]

  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-roboto/+bug/1760124/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Gunnar Hjalmarsson]

On 2017-12-11 14:58, Gunnar Hjalmarsson wrote:> Discussed the proposal in 
comment #21 with Sebastien Bacher, and
> changed the template name and translation domain to "libgweather-3.0"
> in LP for bionic.
With version 1:18.04+20180118 of language-pack-gnome-*-base and version 
3.26.1-2 of libgweather-common this has now been fixed the correct way in 
bionic.

** Changed in: ubuntu-translations
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1704533

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  Fix Released
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Released
Status in libgweather source package in Zesty:
  Fix Released
Status in libgweather source package in Artful:
  Fix Released

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1575222] Re: Translate session action in dash

[Gunnar Hjalmarsson]

** Also affects: language-selector (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: session-shortcuts (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: session-shortcuts (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: language-selector (Ubuntu Zesty)

** No longer affects: language-selector (Ubuntu Xenial)

** No longer affects: language-selector (Ubuntu)

** Changed in: session-shortcuts (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: session-shortcuts (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: session-shortcuts (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: session-shortcuts (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: session-shortcuts (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: session-shortcuts (Ubuntu Zesty)
   Importance: Undecided => Low

** Changed in: session-shortcuts (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: session-shortcuts (Ubuntu Zesty)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Description changed:

+ [Impact]
+ 
  Session actions (shutdown, reboot, logout) are now available from Unity
- Dash on ubuntu 16.04 but are not translated
+ Dash on ubuntu 16.04 but are not translated.
+ 
+ The proposed upload adds X-Ubuntu-Gettext-Domain=session-shortcuts to
+ the .desktop files to make them load the translations.
+ 
+ To the sponsor: A debdiff for artful has been attached. Please use the
+ same for zesty and xenial, while changing the first line in the
+ changelog.
+ 
+ [Test Case]
+ 
+ Install the updated package, start a non-English session, and find that
+ the action names are now localized.
+ 
+ [Regression Potential]
+ 
+ None.

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1575222

Title:
  Translate session action in dash

Status in Ubuntu Translations:
  In Progress
Status in session-shortcuts package in Ubuntu:
  In Progress
Status in session-shortcuts source package in Xenial:
  In Progress
Status in session-shortcuts source package in Zesty:
  In Progress

Bug description:
  [Impact]

  Session actions (shutdown, reboot, logout) are now available from
  Unity Dash on ubuntu 16.04 but are not translated.

  The proposed upload adds X-Ubuntu-Gettext-Domain=session-shortcuts to
  the .desktop files to make them load the translations.

  To the sponsor: A debdiff for artful has been attached. Please use the
  same for zesty and xenial, while changing the first line in the
  changelog.

  [Test Case]

  Install the updated package, start a non-English session, and find
  that the action names are now localized.

  [Regression Potential]

  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1575222/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1675452] Re: submit button of find field is shifted down

[Gunnar Hjalmarsson]

** Changed in: help.ubuntu.com
   Status: Fix Committed => Fix Released

** Changed in: serverguide/trunk
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-docs (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-docs (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-docs (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1675452

Title:
  submit button of find field is shifted down

Status in Online publishing of the Ubuntu documentation:
  Fix Released
Status in Ubuntu Server Guide:
  Fix Released
Status in Ubuntu Server Guide precise series:
  Won't Fix
Status in Ubuntu Server Guide trunk series:
  Fix Released
Status in Ubuntu Server Guide trusty series:
  In Progress
Status in ubuntu-docs package in Ubuntu:
  Fix Committed
Status in ubuntu-docs source package in Trusty:
  Fix Released
Status in ubuntu-docs source package in Xenial:
  Fix Released
Status in ubuntu-docs source package in Yakkety:
  Fix Released

Bug description:
  This bug was misfiled in www.ubuntu.com - https://github.com
  /canonical-websites/www.ubuntu.com/issues/1452

  
  > 
https://www.dropbox.com/s/244nql4xsqyq3gh/Screenshot_2017-03-22_22-02-41.png?dl=0
  >
  > from pdragon - https://github.com/pdragon

To manage notifications about this bug go to:
https://bugs.launchpad.net/help.ubuntu.com/+bug/1675452/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1675452] Re: submit button of find field is shifted down

[Gunnar Hjalmarsson]

** Also affects: help.ubuntu.com
   Importance: Undecided
   Status: New

** Changed in: help.ubuntu.com
   Importance: Undecided => Medium

** Changed in: help.ubuntu.com
   Status: New => Fix Committed

** Changed in: help.ubuntu.com
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1675452

Title:
  submit button of find field is shifted down

Status in Online publishing of the Ubuntu documentation:
  Fix Committed
Status in Ubuntu Server Guide:
  In Progress
Status in Ubuntu Server Guide precise series:
  Won't Fix
Status in Ubuntu Server Guide trunk series:
  In Progress
Status in Ubuntu Server Guide trusty series:
  Triaged
Status in ubuntu-docs package in Ubuntu:
  Fix Committed
Status in ubuntu-docs source package in Trusty:
  Fix Committed
Status in ubuntu-docs source package in Xenial:
  Fix Committed
Status in ubuntu-docs source package in Yakkety:
  Fix Committed

Bug description:
  This bug was misfiled in www.ubuntu.com - https://github.com
  /canonical-websites/www.ubuntu.com/issues/1452

  
  > 
https://www.dropbox.com/s/244nql4xsqyq3gh/Screenshot_2017-03-22_22-02-41.png?dl=0
  >
  > from pdragon - https://github.com/pdragon

To manage notifications about this bug go to:
https://bugs.launchpad.net/help.ubuntu.com/+bug/1675452/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1675452] Re: submit button of find field is shifted down

[Gunnar Hjalmarsson]

** Project changed: firefox => installation-guide

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1675452

Title:
  submit button of find field is shifted down

Status in Ubuntu Server Guide:
  Triaged
Status in ubuntu-docs package in Ubuntu:
  Fix Committed
Status in ubuntu-docs source package in Trusty:
  Triaged
Status in ubuntu-docs source package in Xenial:
  Triaged
Status in ubuntu-docs source package in Yakkety:
  Triaged

Bug description:
  This bug was misfiled in www.ubuntu.com - https://github.com
  /canonical-websites/www.ubuntu.com/issues/1452

  
  > 
https://www.dropbox.com/s/244nql4xsqyq3gh/Screenshot_2017-03-22_22-02-41.png?dl=0
  >
  > from pdragon - https://github.com/pdragon

To manage notifications about this bug go to:
https://bugs.launchpad.net/serverguide/+bug/1675452/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1632870] Re: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux

[Gunnar Hjalmarsson]

Nominated and approved (the latter via a workaround...)

On 2017-02-14 21:40, Naël wrote:
> @Gunnar: Yes, probably too late for Zesty. Besides, we should
> probably leave the package in Zesty for now, if it is to be
> backported to the previous releases via SRUs. We'll make the request
> later.

+1

** Also affects: ubuntu-docs (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-docs (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: pepperflashplugin-nonfree (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-docs (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: pepperflashplugin-nonfree (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-docs (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: pepperflashplugin-nonfree (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-docs (Ubuntu Yakkety)

** No longer affects: ubuntu-docs (Ubuntu Xenial)

** No longer affects: ubuntu-docs (Ubuntu Trusty)

** No longer affects: ubuntu-docs (Ubuntu)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1632870

Title:
  Package is broken since Google stopped shipping Flash with Chrome 54
  for Linux

Status in pepperflashplugin-nonfree package in Ubuntu:
  Fix Released
Status in pepperflashplugin-nonfree source package in Trusty:
  New
Status in pepperflashplugin-nonfree source package in Xenial:
  New
Status in pepperflashplugin-nonfree source package in Yakkety:
  New
Status in pepperflashplugin-nonfree package in Debian:
  Fix Released

Bug description:
  [Impact]

  Pepperflashplugin-nonfree is a Debian package, slightly modified for
  Ubuntu, and available in multiverse, that downloads the PPAPI Flash
  plugin from Google (up to v1.8.3 in Debian and v1.8.2+nmu1ubuntu1 in
  Ubuntu 16.10) or Adobe (starting with v1.8.3+nmu1 in Debian and
  v1.8.3+nmu1ubuntu1 in Ubuntu 17.04), and installs it as /usr/lib
  /pepperflashplugin-nonfree/libpepflashplayer.so.

  Versions that download the PPAPI plugin from Google are currently
  broken since Google decided to unbundle the plugin from Chrome 54,
  released in late 2016-10. Until that date, ripping the PPAPI plugin
  from a download of Google Chrome (which comes as a .deb package) was a
  popular way to get it, and the only possible way on Linux in the early
  days of the PPAPI plugin, when it was only available to Google. Then
  Adobe made the Linux PPAPI plugin available to Canonical and on their
  download site.

  The Debian package was changed to download the plugin from Adobe, in
  version 1.8.3+nmu1 on 2017-01-14, and that fix landed in
  1.8.3+nmu1ubuntu1 in Ubuntu 17.04 (the current development release) on
  2017-01-22.

  The package is still broken in the published releases: 16.10 16.04
  14.04. It could be repaired by merging the changes made between
  1.8.3ubuntu1 and 1.8.3+nmu1ubuntu1 into the published releases'
  versions of the package.

  This would qualify for an SRU because the bug comes from a change in a
  web service that made the package stop being installable. This change
  also causes a security vulnerability in so far as the Flash plugin can
  no longer be updated (updates were processed by downloading a new
  version of Google Chrome and extracting the bundled Flash plugin).

  [Test Case]

  On Ubuntu < 17.04, installation and reinstallation of
  pepperflashplugin-nonfree (v < 1.8.3+nmu1ubuntu1) fails. On Ubuntu
  17.04 (v = 1.8.3+nmu1ubuntu1), it succeeds.

  [Regression Potential]

  I can't think of any. The new version has been in Debian Sid for one
  month without any report of a regression, so that's a good sign. It
  was initially tested in debbug 833741.

  [Why not to SRU]

  On the one hand, it's bad form to leave an utterly broken package in
  the published releases when it has been fixed in the development
  release and works there. Theoretically, SRUs should be performed.

  On the other hand, pepperflashplugin-nonfree is The Debian's Way to
  install the PPAPI Flash plugin. Ubuntu users are recommended to
  install adobe-flashplugin from Canonical's partner repository instead.
  Not all Ubuntu users are aware of that. See:

  https://help.ubuntu.com/stable/ubuntu-help/net-install-flash.html
  https://wiki.ubuntu.com/Chromium/Getting-Flash

  We can consider intentionally not fixing that package in the published
  releases, in which case this bug report should be marked Won't Fix in
  Yakkety, Xenial, Trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pepperflashplugin-nonfree/+bug/1632870/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : 

[Group.of.nepali.translators] [Bug 1655036] Re: HIME rc doesn't assign QT_IM_MODULE, breaks usage in Qt5 application

[Gunnar Hjalmarsson]

** Also affects: ubuntu-docs (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-docs (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: im-config (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-docs (Ubuntu Yakkety)

** No longer affects: ubuntu-docs (Ubuntu Xenial)

** No longer affects: ubuntu-docs (Ubuntu)

** Changed in: im-config (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

** Changed in: im-config (Ubuntu Yakkety)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: im-config (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: im-config (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: im-config (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1655036

Title:
  HIME rc doesn't assign QT_IM_MODULE, breaks usage in Qt5 application

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Xenial:
  In Progress
Status in im-config source package in Yakkety:
  Fix Committed
Status in im-config package in Debian:
  Fix Released

Bug description:
  Currently(in Ubuntu 16.04, may affect other releases) im-config
  provides a rc for hime input method that doesn't assign QT_IM_MODULE,
  rendering Qt5-based applications including but not limited to, ReText
  unable to use input method.

  NOTE: hime currently provides Qt5 immodule via hime-qt5-immodule
  package

  ## Patch & Workaround ##
  insert the following code in /usr/share/im-config/data/25_hime.rc's "if [ 
"$IM_CONFIG_PHASE" = 1 ]" section, then restart X session

  ```
  # use immodule when available for Qt5
  for IM_CONFIG_MARKER in 
/usr/lib/*/qt5/plugins/platforminputcontexts/im-hime.so \
  /usr/lib/qt5/plugins/platforminputcontexts/im-hime.so 
; do
  if [ -e $IM_CONFIG_MARKER ]; then
  QT_IM_MODULE=hime
  break
  fi
  done
  ```

  Upstream tracking issue: https://github.com/hime-ime/hime/issues/558

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: im-config 0.29-1ubuntu12.3
  Uname: Linux 4.8.0-pf5-ubuntu-taiwan-autodetected-optimized x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan  9 22:15:57 2017
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=zh_TW:zh_HK:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_TW.UTF-8
   SHELL=/bin/bash
  SourcePackage: im-config
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1655036/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1247528] Re: Build and distribute intel-virtual-output

[Gunnar Hjalmarsson]

Since I made some noise on the ubuntu-devel list about this, I thought
I'd help out.

I added those build dependencies, and could build it successfully:

https://launchpad.net/~gunnarhj/+archive/ubuntu/intel-virtual-output

New debdiff attached.

Thanks LocutusOfBorg and Dmitry for your assistance!

** Patch added: "bugfix2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1247528/+attachment/4787664/+files/bugfix2.debdiff

** Changed in: xserver-xorg-video-intel (Ubuntu Trusty)
   Importance: Undecided => Wishlist

** Changed in: xserver-xorg-video-intel (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: xserver-xorg-video-intel (Ubuntu Trusty)
 Assignee: (unassigned) => Daniel Gimpelevich (daniel-gimpelevich)

** No longer affects: xserver-xorg-video-intel (Ubuntu Xenial)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1247528

Title:
  Build and distribute intel-virtual-output

Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel source package in Trusty:
  In Progress
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Impact]

  xserver-xorg-video-intel 2.99.904 adds support for virtual displays
  that can be used to clone to discrete outputs. The tool to do this is
  included with the xserver-xorg-video-intel source (with not-so-great
  man page and all), but the binary is currently not shipped by Ubuntu
  trusty, despite being built. It is shipped in utopic and later.

  The tool will allocate a virtual output for the specified outputs on a
  different X server (or for all outputs with the -a parameter). It will
  also copy over resolution information etc from xrandr. You can then
  use your desktop environment's display tool to configure these
  external displays the way you would normally do in a non-hybrid
  situation.

  Since the trusty release is LTS, this bug qualifies for SRU status "to
  enable new hardware," or rather, newly supported at the time of the
  trusty release.

  [Test Case]

  1) Install the package.
  2) Attempt to execute /usr/bin/intel-virtual-output in a shell.

  [Regression Potential]

  Absolutely none.

  [Other Info]

  The intel-gpu-tools package is the only reverse dependency, and that
  package has no reverse dependencies in turn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1247528/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1482938] Re: im-config gcin qt5

[Gunnar Hjalmarsson]

** Also affects: language-selector (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: im-config (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: language-selector (Ubuntu Yakkety)

** No longer affects: language-selector (Ubuntu Xenial)

** No longer affects: language-selector (Ubuntu)

** Changed in: im-config (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: im-config (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: im-config (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1482938

Title:
  im-config gcin qt5

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Xenial:
  In Progress
Status in im-config source package in Yakkety:
  Fix Committed
Status in im-config package in Debian:
  Fix Released

Bug description:
  [Impact]

  missing

  QT_IM_MODULE=gcin

  in /usr/share/im-config/data/26_gcin.rc

  QT5 needs this.

  Fix uploaded to yakkety queue; xenial patch attached to bug #1642001.

  [Test Case]

  After the change, this command:

  grep -A3 QT_IM_MODULE /usr/share/im-config/data/26_gcin.rc

  should output:

  QT_IM_MODULE=xim
  # use immodule when available for Qt5
  for IM_CONFIG_MARKER in 
/usr/lib/*/qt5/plugins/platforminputcontexts/libgcinplatforminputcontextplugin.so
 ; do
  if [ -e $IM_CONFIG_MARKER ]; then
  QT_IM_MODULE=gcin
  break
  fi
  done

  [Regression Potential]

  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1482938/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1443052] Re: User accounts login history showing incorrect history - patch

[Gunnar Hjalmarsson]

Precise is soon EOL anyway, so non-essential changes are not worth it.

I have sponsored the accountsservice debdiff to the trusty queue. Please
unsubscribe ubuntu-sponsors again. ;)

** No longer affects: gnome-control-center (Ubuntu Xenial)

** No longer affects: unity-control-center (Ubuntu Xenial)

** Also affects: accountsservice (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: accountsservice (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: accountsservice (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: accountsservice (Ubuntu Trusty)
 Assignee: (unassigned) => Nikita Yerenkov-Scott (yerenkov-scott)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1443052

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  In Progress
Status in accountsservice source package in Xenial:
  In Progress

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  Regression potential
  

  I have not encountered any regressions while testing this patch.


  --

  Original description:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1572661] Re: Ubuntu Gnome Bug -evolution translation

[Gunnar Hjalmarsson]

Yeah, there are quite a few untranslated strings in Launchpad:

https://translations.launchpad.net/ubuntu/yakkety/+source/evolution/+pots/evolution/it/+translate?show=untranslated

@Gianvito: I don't think this is quite the same issue. Can you please
file a new bug about yakkety.

** Changed in: evolution (Ubuntu Xenial)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1572661

Title:
  Ubuntu Gnome Bug -evolution translation

Status in evolution package in Ubuntu:
  Invalid
Status in evolution source package in Xenial:
  Fix Released

Bug description:
  * Impact
  evolution is not translated

  * Test case
  start evolution under a non english locale, it should be translated

  * Regression potential
  none, that's a small packaging change to add translations to the deb

  -

  Ubuntu Gnome 16.04 RC

  Evolution is not translated in another language. It is in english
  only.

  Affects at least french (canadian), Norwegian (Bokmål) and german
  (seen on a Google Plus post :

  https://plus.google.com/+UbuntuGNOMEorg/posts/bsFL3SLf6ot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1572661/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1599264] Re: [SRU] "When power is critically low" setting does nothing

[Gunnar Hjalmarsson]

** Also affects: ubuntu-docs (Ubuntu Z-series)
   Importance: Undecided
   Status: New

** Also affects: unity-control-center (Ubuntu Z-series)
   Importance: Undecided
   Status: New

** No longer affects: unity-control-center (Ubuntu Z-series)

** Changed in: ubuntu-docs (Ubuntu Yakkety)
   Importance: Medium => Undecided

** Changed in: ubuntu-docs (Ubuntu Yakkety)
   Status: Triaged => Won't Fix

** Changed in: ubuntu-docs (Ubuntu Z-series)
   Importance: Undecided => Medium

** Changed in: ubuntu-docs (Ubuntu Z-series)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1599264

Title:
  [SRU] "When power is critically low" setting does nothing

Status in One Hundred Papercuts:
  Triaged
Status in ubuntu-docs package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in ubuntu-docs source package in Xenial:
  Won't Fix
Status in unity-control-center source package in Xenial:
  Triaged
Status in ubuntu-docs source package in Yakkety:
  Won't Fix
Status in unity-control-center source package in Yakkety:
  Fix Released
Status in ubuntu-docs source package in z-series:
  Triaged

Bug description:
  [Impact]

  In unity-control-center (u-c-c) there is an option for taking an
  action when "Power is critically low".  The choices are "Hibernate" or
  "Power off".  Often Hibernate is a disabled option because of problems
  with hibernate on various systems.

  However - what to do in the event of a critically low power situation
  is now handled by Upowerd automatically and so making a choice in
  u-c-c does nothing at all.

  As such, leaving that option accessible to users will lead to
  confusion.

  This patch removes the option from the UI.

  [Test Case]

  On an unpatched machine with a battery (i.e. laptop) open the power
  panel in u-c-c (Power/Settings menu in the top right corner -> System
  Settings -> Power.  Note that the 2nd option down is "When power is
  critically low".

  Once this update is applied and u-c-c is closed and reopened, this
  option is no longer present.

  [Regression Potential]
  There are some deletions from the ui file and some corresponding code 
deletions from the associated c file (cc-power-panel.c).

  It is possible that extra code has been removed that could cause a
  crash or affect other options in the power panel.

  However, the changes are fairly small and easy to review.  Nothing
  looks out of place.  Also testing has not shown any problems.

  [Other Info]

  Verbal (IRC) +1 from design via mpt.
  +1 from docs team via mailing list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1599264/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1594681] Re: Don't override IM variables

[Gunnar Hjalmarsson]

** Changed in: ubuntu-gnome
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1594681

Title:
  Don't override IM variables

Status in gnome-session:
  Fix Released
Status in Ubuntu GNOME:
  Fix Released
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-session source package in Xenial:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently these variable settings are hardcoded in gnome-session and
  gnome-settings-daemon:

  QT_IM_MODULE=ibus
  XMODIFIERS=@im=ibus

  That way the use of alternative IM frameworks, for instance fcitx, is
  prevented. The variables should only be set if they are empty, so the
  values set by im-config are honored.

  [Test Case]

  * Install Ubuntu GNOME
  * Install both the gnome-session and gnome-settings-daemon proposed updates
  * Install fcitx
  * Set fcitx as the input method:
    im-config -n fcitx
  * Relogin
  * Check the IM-related environment variables:
    env | grep -E '_IM|XMOD'

  After the proposed uploads of gnome-session and gnome-settings-daemon,
  those variables are consistently (unlike before) set to "fcitx".

  [Regression Potential]

  Low. im-config sets "ibus" by default in Ubuntu GNOME anyway. This
  change prevents an inconsistent input method configuration for users
  who have actively chosen some other IM framework.

  The gnome-settings-daemon change was included upstream in 3.19.3 and
  the gnome-session change was included upstream in 3.21.90.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1594681/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1594681] Re: Don't set ibus variables from gnome-session

[Gunnar Hjalmarsson]

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-session (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gnome-settings-daemon (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: language-selector (Ubuntu Xenial)

** No longer affects: language-selector (Ubuntu)

** Bug watch added: GNOME Bug Tracker #769863
   https://bugzilla.gnome.org/show_bug.cgi?id=769863

** Also affects: gnome-session via
   https://bugzilla.gnome.org/show_bug.cgi?id=769863
   Importance: Unknown
   Status: Unknown

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: gnome-session (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: gnome-session (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: gnome-session (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: gnome-session (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: gnome-settings-daemon (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: gnome-settings-daemon (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: gnome-settings-daemon (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Fix Released

** Patch removed: "gnome-session_no-ibus-vars.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1594681/+attachment/4687934/+files/gnome-session_no-ibus-vars.patch

** Summary changed:

- Don't set ibus variables from gnome-session
+ Don't override IM variables

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1594681

Title:
  Don't override IM variables

Status in gnome-session:
  Unknown
Status in Ubuntu GNOME:
  New
Status in gnome-session package in Ubuntu:
  In Progress
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-session source package in Xenial:
  In Progress
Status in gnome-settings-daemon source package in Xenial:
  In Progress

Bug description:
  Currently these variable settings are hardcoded in gnome-session:

  QT_IM_MODULE=ibus
  XMODIFIERS=@im=ibus

  That way the use of alternative IM frameworks, for instance fcitx, is
  prevented. gnome-session should drop those variable assignments, and
  rely on im-config instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1594681/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1607937] Re: font viewer starred from dash: Unknown option --gapplication-service

[Gunnar Hjalmarsson]

** Also affects: language-selector (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gnome-font-viewer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: language-selector (Ubuntu)

** No longer affects: language-selector (Ubuntu Xenial)

** Changed in: gnome-font-viewer (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: gnome-font-viewer (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: gnome-font-viewer (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: gnome-font-viewer (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Description changed:

+ [Impact]
+ 
+ While gnome-font-viewer can be started from command line, it fails to
+ start via the .desktop file. As can be seen in comment #3, it seems to
+ be related to DBus somehow.
+ 
+ The problem is not present in version 3.20.2-1 in yakkety, and since
+ there is no obvious single commit in the upstream source which could be
+ patched, the proposal is to backport the yakkety version as an SRU. It's
+ built in this PPA:
+ 
+ https://launchpad.net/~gunnarhj/+archive/ubuntu/font-viewer
+ 
+ and there are no runtime dependency blockers.
+ 
+ [Test Case]
+ 
+ Try to start gnome-font-viewer from the Dash and find that the launch
+ fails.
+ 
+ After having installed the proposed upload, starting the application
+ from the Dash works fine.
+ 
+ [Regression Potential]
+ 
+ gnome-font-viewer is an independent tool, which doesn't affect other
+ parts of the system. Hence the regression risk should be low.
+ 
+ [Original description]
+ 
  Ubuntu 16.04.1 Fully updated.
  
  $ gnome-font-viewer  --version
  GNOME Font Viewer 3.16.2
  
  - starting from command-line: no problems.
  - starting from dash: application is shown in launcher but kills itself.
  - /var/log/syslog shows ...
  
-Jul 29 22:18:08 schijfwereld org.gnome.font-viewer[3361]: Unknown option 
--gapplication-service
-Jul 29 22:18:08 schijfwereld org.gnome.font-viewer[3361]: Run 
'/usr/bin/gnome-font-viewer --help' to see a full list of available command 
line options.
+    Jul 29 22:18:08 schijfwereld org.gnome.font-viewer[3361]: Unknown option 
--gapplication-service
+    Jul 29 22:18:08 schijfwereld org.gnome.font-viewer[3361]: Run 
'/usr/bin/gnome-font-viewer --help' to see a full list of available command 
line options.

** Tags added: xenial

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1607937

Title:
  font viewer starred from dash: Unknown option --gapplication-service

Status in gnome-font-viewer package in Ubuntu:
  Fix Released
Status in gnome-font-viewer source package in Xenial:
  In Progress

Bug description:
  [Impact]

  While gnome-font-viewer can be started from command line, it fails to
  start via the .desktop file. As can be seen in comment #3, it seems to
  be related to DBus somehow.

  The problem is not present in version 3.20.2-1 in yakkety, and since
  there is no obvious single commit in the upstream source which could
  be patched, the proposal is to backport the yakkety version as an SRU.
  It's built in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/font-viewer

  and there are no runtime dependency blockers.

  [Test Case]

  Try to start gnome-font-viewer from the Dash and find that the launch
  fails.

  After having installed the proposed upload, starting the application
  from the Dash works fine.

  [Regression Potential]

  gnome-font-viewer is an independent tool, which doesn't affect other
  parts of the system. Hence the regression risk should be low.

  [Original description]

  Ubuntu 16.04.1 Fully updated.

  $ gnome-font-viewer  --version
  GNOME Font Viewer 3.16.2

  - starting from command-line: no problems.
  - starting from dash: application is shown in launcher but kills itself.
  - /var/log/syslog shows ...

     Jul 29 22:18:08 schijfwereld org.gnome.font-viewer[3361]: Unknown option 
--gapplication-service
     Jul 29 22:18:08 schijfwereld org.gnome.font-viewer[3361]: Run 
'/usr/bin/gnome-font-viewer --help' to see a full list of available command 
line options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1607937/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1605408] [NEW] Don't set IM "xim" by default

[Gunnar Hjalmarsson]

Public bug reported:

[Impact]

Since the fix of <https://launchpad.net/bugs/1481025> "cjkv" has been
the system default in im-config for some flavors (e.g. Xubuntu,
Lubuntu), which means that an IM framework is started and configured
only if one of the CJKV languages is the selected display language. For
other languages "cjkv" means that no IM related environment variables
are set (value "none"). However, when starting gnome-language-selector
first time after installation of one of those flavors, the selected IM
method is set to "xim" automatically. This is undocumented behavior, and
the background is commented in the bug description of
<https://launchpad.net/bugs/1585797>.

As illustrated in <https://launchpad.net/bugs/1573755>, the "xim" input
method occasionally causes hard to debug keyboard problems. For this
reason gnome-language-selector should not set "xim", but simply confirm
the "none" default value from im-config.

Some users need "xim" to access X11 dead key and compose key variants,
and this means that they will always need to set it explicitly. The
upside is that users who encounter problems with "xim" will do so as a
result of an active measure, which increases the chance that they
understand the causality.

[Test Case]

On a Xubuntu or Lubuntu system with a non-CJKV display language:

* Remove already set user specific IM configuration:

  rm -f ~/.xinputrc

* Open gnome-language-selector, and find that the selected "keyboard
  input method system" is "XIM".

After installing the proposed version of language-selector-gnome, those
steps instead result in the value "none".

[Regression Potential]

Low. This is only about the default value applied by gnome-language-
selector, so it doesn't change an already set user specific IM
configuration.

** Affects: language-selector (Ubuntu)
 Importance: Medium
 Assignee: Gunnar Hjalmarsson (gunnarhj)
 Status: In Progress

** Affects: language-selector (Ubuntu Xenial)
 Importance: Medium
 Assignee: Gunnar Hjalmarsson (gunnarhj)
 Status: In Progress

** Also affects: language-selector (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: language-selector (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: language-selector (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: language-selector (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1605408

Title:
  Don't set IM "xim" by default

Status in language-selector package in Ubuntu:
  In Progress
Status in language-selector source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Since the fix of <https://launchpad.net/bugs/1481025> "cjkv" has been
  the system default in im-config for some flavors (e.g. Xubuntu,
  Lubuntu), which means that an IM framework is started and configured
  only if one of the CJKV languages is the selected display language.
  For other languages "cjkv" means that no IM related environment
  variables are set (value "none"). However, when starting gnome-
  language-selector first time after installation of one of those
  flavors, the selected IM method is set to "xim" automatically. This is
  undocumented behavior, and the background is commented in the bug
  description of <https://launchpad.net/bugs/1585797>.

  As illustrated in <https://launchpad.net/bugs/1573755>, the "xim"
  input method occasionally causes hard to debug keyboard problems. For
  this reason gnome-language-selector should not set "xim", but simply
  confirm the "none" default value from im-config.

  Some users need "xim" to access X11 dead key and compose key variants,
  and this means that they will always need to set it explicitly. The
  upside is that users who encounter problems with "xim" will do so as a
  result of an active measure, which increases the chance that they
  understand the causality.

  [Test Case]

  On a Xubuntu or Lubuntu system with a non-CJKV display language:

  * Remove already set user specific IM configuration:

rm -f ~/.xinputrc

  * Open gnome-language-selector, and find that the selected "keyboard
input method system" is "XIM".

  After installing the proposed version of language-selector-gnome,
  those steps instead result in the value "none".

  [Regression Potential]

  Low. This is only about the default value applied by gnome-language-
  selector, so it doesn't change an already set user specific IM
  configuration.

To manage notifications ab

[Group.of.nepali.translators] [Bug 1599264] Re: [SRU] "When power is critically low" setting does nothing

[Gunnar Hjalmarsson]

On 2016-07-07 00:27, Alberto Salvia Novella wrote:
> The official held criteria for setting if a bug fix should go into a
> stable release update ...

There are no general criteria for determining when a bug fix *should* be
backported. The purpose of the SRU criteria is to make clear under which
circumstances backporting *may* take place. Obviously they don't
override 'cost-benefit' considerations.

** Changed in: ubuntu-docs (Ubuntu Xenial)
   Importance: Medium => Undecided

** Changed in: ubuntu-docs (Ubuntu Xenial)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1599264

Title:
  [SRU] "When power is critically low" setting does nothing

Status in One Hundred Papercuts:
  Triaged
Status in ubuntu-docs package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Triaged
Status in ubuntu-docs source package in Xenial:
  Won't Fix
Status in unity-control-center source package in Xenial:
  Triaged
Status in ubuntu-docs source package in Yakkety:
  Triaged
Status in unity-control-center source package in Yakkety:
  Triaged

Bug description:
  [Impact]

  In unity-control-center (u-c-c) there is an option for taking an
  action when "Power is critically low".  The choices are "Hibernate" or
  "Power off".  Often Hibernate is a disabled option because of problems
  with hibernate on various systems.

  However - what to do in the event of a critically low power situation
  is now handled by Upowerd automatically and so making a choice in
  u-c-c does nothing at all.

  As such, leaving that option accessible to users will lead to
  confusion.

  This patch removes the option from the UI.

  [Test Case]

  On an unpatched machine with a battery (i.e. laptop) open the power
  panel in u-c-c (Power/Settings menu in the top right corner -> System
  Settings -> Power.  Note that the 2nd option down is "When power is
  critically low".

  Once this update is applied and u-c-c is closed and reopened, this
  option is no longer present.

  [Regression Potential]
  There are some deletions from the ui file and some corresponding code 
deletions from the associated c file (cc-power-panel.c).

  It is possible that extra code has been removed that could cause a
  crash or affect other options in the power panel.

  However, the changes are fairly small and easy to review.  Nothing
  looks out of place.  Also testing has not shown any problems.

  [Other Info]

  Verbal (IRC) +1 from design via mpt.
  +1 from docs team via mailing list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1599264/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1599264] Re: "When power is critically low" setting does nothing

[Gunnar Hjalmarsson]

Thanks for the docs hint, Will. Suppose it affects this page:

https://help.ubuntu.com/stable/ubuntu-help/power-lowpower.html

** Changed in: ubuntu-docs (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-docs (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-docs (Ubuntu Xenial)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1599264

Title:
  "When power is critically low" setting does nothing

Status in ubuntu-docs package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed
Status in ubuntu-docs source package in Xenial:
  Won't Fix
Status in unity-control-center source package in Xenial:
  New
Status in ubuntu-docs source package in Yakkety:
  Confirmed
Status in unity-control-center source package in Yakkety:
  Confirmed

Bug description:
  Since the move to systemd (I think) the setting in unity-control-
  center under "Power" that says:

  When power is critically low: [Hibernate | Power Off]

  doesn't actually do anything any more.

  That action is now controlled by Upower config in
  /etc/UPower/UPower.conf.  At the end of that file you can see:

  # The action to take when "TimeAction" or "PercentageAction" above has been
  # reached for the batteries (UPS or laptop batteries) supplying the computer
  # 
  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep
  #
  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used
  CriticalPowerAction=HybridSleep

  
  So the default action is HybridSleep and is not configurable by the user in 
the control center anymore.

  FWIW - I think the best thing to do is just remove that setting from
  u-c-c altogether.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1599264/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1591503] Re: missing fcitx-mozc.mo

[Gunnar Hjalmarsson]

** Also affects: mozc (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: language-pack-ja-base (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: language-pack-zh-hans-base (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: language-pack-zh-hant-base (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: mozc (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: language-pack-ja-base (Ubuntu Xenial)

** No longer affects: language-pack-zh-hans-base (Ubuntu Xenial)

** No longer affects: language-pack-zh-hant-base (Ubuntu Xenial)

** No longer affects: language-selector (Ubuntu Xenial)

** No longer affects: language-selector (Ubuntu)

** Changed in: mozc (Ubuntu)
   Importance: Undecided => Medium

** Changed in: mozc (Ubuntu)
   Status: New => In Progress

** Changed in: mozc (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: mozc (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: mozc (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: mozc (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.1

** Changed in: mozc (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1591503

Title:
  missing fcitx-mozc.mo

Status in langpack-o-matic:
  Triaged
Status in language-pack-ja-base package in Ubuntu:
  Confirmed
Status in language-pack-zh-hans-base package in Ubuntu:
  Confirmed
Status in language-pack-zh-hant-base package in Ubuntu:
  Confirmed
Status in mozc package in Ubuntu:
  In Progress
Status in mozc source package in Xenial:
  In Progress

Bug description:
  $ LANG=C dpkg -S fcitx-mozc.mo
  dpkg-query: no path found matching pattern *fcitx-mozc.mo*

  Please include it for upcoming next translation update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/langpack-o-matic/+bug/1591503/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "

[Gunnar Hjalmarsson]

The rule in /etc/apparmor.d/lightdm-guest-session has proved to break
AppArmor, and thus can't be added, so unfortunately this bug is still
not fixed.

** Changed in: lightdm (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: lightdm (Ubuntu)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

** Changed in: lightdm (Ubuntu Xenial)
   Status: Fix Committed => Confirmed

** Changed in: lightdm/1.18
   Status: Fix Committed => Confirmed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1273524

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Triaged
Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in lxsession package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Confirmed
Status in lxsession source package in Xenial:
  New

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1592162] [NEW] Translation update + extras

[Gunnar Hjalmarsson]

Public bug reported:

[Impact]

This upload combines a regular translation update of the 16.04 desktop
guide with changes of 30+ translatable strings.

Normally we don't do SRUs of translatable strings in ubuntu-docs, but
there was a late name change of the new software management application
from just "Software" to "Ubuntu Software", which was not reflected in
the desktop guide at release time. The relative importance of Ubuntu
Software, and its mentioning in the desktop guide in several places,
justifies this exception.

We have taken this 'opportunity' to SRU a few other bug fixes; please
see the changelog.

The translators have been notified:

https://lists.ubuntu.com/archives/ubuntu-
translators/2016-May/007174.html

and reminded:

https://lists.ubuntu.com/archives/ubuntu-
translators/2016-June/007178.html

[Test Case]

As an example, this page:

https://help.ubuntu.com/16.04/ubuntu-help/addremove-install.html

refers to "Software" only. With the update it's changed to "Ubuntu
Software".

[Regression Potential]

For some languages, some strings, which were translated at release time,
may be untranslated after this update. That's unfortunate, but these
changes of original strings carry greater weight. It's also possible to
improve this through translation updates later on.

Otherwise the regression risk is low. This is only documentation, which
does not affect other parts of the system.

** Affects: ubuntu-docs (Ubuntu)
 Importance: Medium
 Assignee: Gunnar Hjalmarsson (gunnarhj)
 Status: Triaged

** Affects: ubuntu-docs (Ubuntu Xenial)
 Importance: Medium
 Assignee: Gunnar Hjalmarsson (gunnarhj)
 Status: Triaged

** Also affects: ubuntu-docs (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-docs (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: ubuntu-docs (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: ubuntu-docs (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.1

** Changed in: ubuntu-docs (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1592162

Title:
  Translation update + extras

Status in ubuntu-docs package in Ubuntu:
  Triaged
Status in ubuntu-docs source package in Xenial:
  Triaged

Bug description:
  [Impact]

  This upload combines a regular translation update of the 16.04 desktop
  guide with changes of 30+ translatable strings.

  Normally we don't do SRUs of translatable strings in ubuntu-docs, but
  there was a late name change of the new software management
  application from just "Software" to "Ubuntu Software", which was not
  reflected in the desktop guide at release time. The relative
  importance of Ubuntu Software, and its mentioning in the desktop guide
  in several places, justifies this exception.

  We have taken this 'opportunity' to SRU a few other bug fixes; please
  see the changelog.

  The translators have been notified:

  https://lists.ubuntu.com/archives/ubuntu-
  translators/2016-May/007174.html

  and reminded:

  https://lists.ubuntu.com/archives/ubuntu-
  translators/2016-June/007178.html

  [Test Case]

  As an example, this page:

  https://help.ubuntu.com/16.04/ubuntu-help/addremove-install.html

  refers to "Software" only. With the update it's changed to "Ubuntu
  Software".

  [Regression Potential]

  For some languages, some strings, which were translated at release
  time, may be untranslated after this update. That's unfortunate, but
  these changes of original strings carry greater weight. It's also
  possible to improve this through translation updates later on.

  Otherwise the regression risk is low. This is only documentation,
  which does not affect other parts of the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1592162/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1585797] [NEW] Distinguish between input method "XIM" and "none"

[Gunnar Hjalmarsson]

Public bug reported:

[Impact]

language-selector-gnome includes a GUI to configure the input method via
im-config. Besides the installed IM frameworks (IBus, Fcitx, etc.) the
IM selector shows a "none" option, which actually represents the value
"xim". This was an intentional simplification, made under the assumption
that "none" and "xim" are approximately the same. However, it has proven
to be an oversimplification. For example there is a need sometimes to
control whether the X11 compose keys should be active or not.

This SRU adds an explicit "XIM" option, and converts the "none" option
to actually set "none".

A recent reason why an explicit "none" option is needed is Ubuntu MATE,
which does not install any IM framework by default for non-CJKV users.
Currently, when such a user opens Language Support for the first time,
the input method selector shows a blank value. With this SRU it will
correctly show "none".

[Test Case]

An example test case would be:

* Make a fresh install of Ubuntu MATE 16.04.
* Open Language Support and find that the input method value is blank.

[Regression Potential]

Low. This won't *change* the input method setting, but the currently set
value will be showed more correctly in some cases.

** Affects: language-selector (Ubuntu)
 Importance: Medium
 Assignee: Gunnar Hjalmarsson (gunnarhj)
 Status: In Progress

** Affects: language-selector (Ubuntu Xenial)
 Importance: Medium
 Assignee: Gunnar Hjalmarsson (gunnarhj)
 Status: In Progress

** Also affects: language-selector (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: language-selector (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: language-selector (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: language-selector (Ubuntu Xenial)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1585797

Title:
  Distinguish between input method "XIM" and "none"

Status in language-selector package in Ubuntu:
  In Progress
Status in language-selector source package in Xenial:
  In Progress

Bug description:
  [Impact]

  language-selector-gnome includes a GUI to configure the input method
  via im-config. Besides the installed IM frameworks (IBus, Fcitx, etc.)
  the IM selector shows a "none" option, which actually represents the
  value "xim". This was an intentional simplification, made under the
  assumption that "none" and "xim" are approximately the same. However,
  it has proven to be an oversimplification. For example there is a need
  sometimes to control whether the X11 compose keys should be active or
  not.

  This SRU adds an explicit "XIM" option, and converts the "none" option
  to actually set "none".

  A recent reason why an explicit "none" option is needed is Ubuntu
  MATE, which does not install any IM framework by default for non-CJKV
  users. Currently, when such a user opens Language Support for the
  first time, the input method selector shows a blank value. With this
  SRU it will correctly show "none".

  [Test Case]

  An example test case would be:

  * Make a fresh install of Ubuntu MATE 16.04.
  * Open Language Support and find that the input method value is blank.

  [Regression Potential]

  Low. This won't *change* the input method setting, but the currently
  set value will be showed more correctly in some cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1585797/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1584106] Re: Login to Unity session fails with linux 4.4.0-22

[Gunnar Hjalmarsson]

I installed linux 4.4.0-23.41 from yakkety-proposed, and that fixed the
issue.

Fortunately I didn't meet the problem on xenial; the problem was linux
4.4.0-22 on Ubuntu 16.10, but since it's fixed in -proposed, it will
soon be history, right?

(don't know how to use apport-collect in a situation like this)

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: unity (Ubuntu Xenial)

** Tags removed: xenial

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1584106

Title:
  Login to Unity session fails with linux 4.4.0-22

Status in linux package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  New

Bug description:
  My attempts to launch Unity sessions on an updated yakkety fails with
  linux 4.4.0-22 (both 4.4.0-22.39 and 4.4.0-22.40). Just some blinking
  on the screen, and I'm thrown back to the greeter. It happens when I
  try to launch a guest session too, so it shouldn't be anything in my
  $HOME.

  linux 4.4.0-21.37 does not trigger this issue.

  Attaching .xsession-errors.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584106/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1581470] Re: gnome-language-selector crashes when trying to drag English to the top

[Gunnar Hjalmarsson]

*** This bug is a duplicate of bug 1581567 ***
https://bugs.launchpad.net/bugs/1581567

Thanks for your report, Po-Hsu Lin. This is actually an issue with
accountsservice, and will be fixed when accountsservice
0.6.40-2ubuntu11.1 makes it into xenial-updates (it's currently in
xenial-proposed).

** Package changed: language-selector (Ubuntu) => accountsservice
(Ubuntu)

** Changed in: accountsservice (Ubuntu)
   Importance: Undecided => High

** Changed in: accountsservice (Ubuntu)
   Status: Confirmed => Fix Committed

** Also affects: accountsservice (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: accountsservice (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: accountsservice (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: accountsservice (Ubuntu Xenial)
   Status: New => Fix Committed

** This bug has been marked a duplicate of bug 1581567
   SRU regression, can't change own data

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1581470

Title:
  gnome-language-selector crashes when trying to drag English to the top

Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Xenial:
  Fix Committed

Bug description:
  CID: 201409-15485

  I have this 16.04 system configured in Traditional Chinese (Taiwan),
  but when I was trying to drag "English (United States)" back to the
  top, the language selector will crash.

  Steps:
  1. Boot and make sure the system using Traditional Chinese (Taiwan)
  2. Open Language Settings
  3. Try to change the order by dragging English (United States) to the top.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: language-selector-gnome 0.165.1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 13 06:55:03 2016
  InstallationDate: Installed on 2016-05-04 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: language-selector
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1581470/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1578821] Re: I'm not able to install galician language in Ubuntu 16.04

[Gunnar Hjalmarsson]

Considering how this will be fixed in Debian, we will need to replace
the hunspell-gl exception in language-selector with a hunspell-gl-es
exception, so I reopen the language-selector task for the development
release.

** Changed in: language-selector (Ubuntu)
   Importance: High => Medium

** Changed in: language-selector (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: libreoffice-dictionaries (Ubuntu)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

** No longer affects: libreoffice-dictionaries (Ubuntu Xenial)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1578821

Title:
  I'm not able to install galician language in Ubuntu 16.04

Status in language-selector package in Ubuntu:
  Confirmed
Status in libreoffice-dictionaries package in Ubuntu:
  Confirmed
Status in language-selector source package in Xenial:
  Fix Committed
Status in libreoffice-dictionaries package in Debian:
  New

Bug description:
  [Impact]

  Installing the Galician language via Language Support fails. The
  reason is that there is currently two hunspell spellchecking packages
  in the archive:

  * hunspell-gl-es, provided by the hunspell-gl-es source package
  * hunspell-gl, provided by the libreoffice-dictionaries source package

  Even if hunspell-gl-es conflicts to hunspell-gl, having both of them
  available in the archive is not compatible with the way the writing
  aids is pulled via Language Selector. The proposed upload in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/lo-dicts-symlinks

  drops the hunspell-gl binary from libreoffice-dictionaries.

  [Test Case]

   * Open Language Support
   * Try to install Galician

  [Regression Potential]

  Low.

  [Original description]

  Hi

  I just installed Ubuntu 16.04. So as I try to install galician
  language I get this notification:

  Transaction failed: Package dependencies cannot be resolved
   The following packages have unmet dependencies:

  hunspell-gl-es:

  Then nothing happens. Several fellows got the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1578821/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1575555] Re: Chrome/Chromium use "Thin" as default font weight

[Gunnar Hjalmarsson]

Fixed via autosync

** Changed in: fonts-noto-cjk (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/157

Title:
  Chrome/Chromium use "Thin" as default font weight

Status in fonts-noto-cjk package in Ubuntu:
  Fix Released
Status in fonts-noto-cjk source package in Xenial:
  In Progress
Status in fonts-noto-cjk package in Debian:
  Fix Released

Bug description:
  [Impact]

  Chromium and Google Chrome use "Thin" as the default Noto Sans CJK
  font weight, which makes some Chinese and Japanese web pages difficult
  to read, and thus gives a bad user experience.

  The fonts-noto-cjk version in the PPA

  https://launchpad.net/~gunnarhj/+archive/ubuntu/fonts-noto-cjk

  installs 7 weight specific font files instead of a single "super"
  file. This works around the Chromium/Chrome issue.

  Note: It has been fixed in yakkety via autosync, so "backporting"
  yakkety (as an SRU) instead of uploading from the PPA is an option.

  [Test Case]

  To reproduce the bug:

  * Install Chromium or Google Chrome.
  * Go to  and notice the very thin characters.
  * Install fonts-noto-cjk from the PPA and notice the difference.

  [Regression Potential]

  This is about another font packaging form, without any change in glyph
  coverage, so the the regression risk should be low.

  [Original description]

  The package seems to only "thin" variant of the font, which makes it
  very unreadable in applications such as Chrome (when it has to fall
  back on Chinese fonts on a mostly-English page). I had to remove the
  package and then manually download the font from Google website and
  install it to make the regular weight available

  Release: 16.04 LTS
  Package Version: 1.004+repack1-1
  Expected: All weights of the noto cjk font to be installed
  Happened: Only the "thin" weight of the font seems to be installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/157/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "

[Gunnar Hjalmarsson]

Fixed in lightdm 1.19.0-0ubuntu1

** Changed in: lightdm (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1273524

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Triaged
Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lxsession package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Fix Committed
Status in lxsession source package in Xenial:
  New

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1575555] Re: Chrome/Chromium use "Thin" as default font weight

[Gunnar Hjalmarsson]

** Bug watch added: Debian Bug tracker #823374
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823374

** Also affects: fonts-noto-cjk (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823374
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/157

Title:
  Chrome/Chromium use "Thin" as default font weight

Status in fonts-noto-cjk package in Ubuntu:
  In Progress
Status in fonts-noto-cjk source package in Xenial:
  In Progress
Status in fonts-noto-cjk package in Debian:
  Unknown

Bug description:
  [Impact]

  Chromium and Google Chrome use "Thin" as the default Noto Sans CJK
  font weight, which makes some Chinese and Japanese web pages difficult
  to read, and thus gives a bad user experience.

  The fonts-noto-cjk version in the PPA

  https://launchpad.net/~gunnarhj/+archive/ubuntu/fonts-noto-cjk

  installs 7 weight specific font files instead of a single "super"
  file. This works around the Chromium/Chrome issue.

  [Test Case]

  To reproduce the bug:

  * Install Chromium or Google Chrome.
  * Go to  and notice the very thin characters.
  * Install fonts-noto-cjk from the PPA and notice the difference.

  [Regression Potential]

  This is about another font packaging form, without any change in glyph
  coverage, so the the regression risk should be low.

  [Original description]

  The package seems to only "thin" variant of the font, which makes it
  very unreadable in applications such as Chrome (when it has to fall
  back on Chinese fonts on a mostly-English page). I had to remove the
  package and then manually download the font from Google website and
  install it to make the regular weight available

  Release: 16.04 LTS
  Package Version: 1.004+repack1-1
  Expected: All weights of the noto cjk font to be installed
  Happened: Only the "thin" weight of the font seems to be installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/157/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1575555] Re: Chrome/Chromium use "Thin" as default font weight

[Gunnar Hjalmarsson]

** Description changed:

  [Impact]
  
  Chromium and Google Chrome use "Thin" as the default Noto Sans CJK font
  weight, which makes some Chinese and Japanese web pages difficult to
  read, and thus gives a bad user experience.
  
  The fonts-noto-cjk version in the PPA
  
  https://launchpad.net/~gunnarhj/+archive/ubuntu/fonts-noto-cjk
  
- installs 36 separate font files instead of a bundled OTC file. This
- works around the Chromium/Chrome issue.
+ installs 7 weight specific font files instead of a single "super" file.
+ This works around the Chromium/Chrome issue.
  
  [Test Case]
  
  To reproduce the bug:
  
  * Install Chromium or Google Chrome.
  * Go to  and notice the very thin characters.
  * Install fonts-noto-cjk from the PPA and notice the difference.
  
  [Regression Potential]
  
- Due to ISO space concerns, the solution includes the creation of the
- fonts-noto-cjk-extras binary, which will not be seeded. fonts-noto-cjk
- installs only the 8 most important font files, while the rest are
- installed by fonts-noto-cjk-extras. Consequently 28 fonts will be
- dropped when the 16.04 users upgrade to the new fonts-noto-cjk package.
- However,
- 
- - they will be prompted to install fonts-noto-cjk-extras via Language
-   Support,
- 
- - fixing the Chromium/Chrome issue carries greater weight, and
- 
- - it's not a regression compared to 14.04 or 15.10, since the previous
-   package for rendering Chinese contents (fonts-droid) does not include
-   all those font weights.
+ This is about another font packaging form, without any change in glyph
+ coverage, so the the regression risk should be low.
  
  [Original description]
  
  The package seems to only "thin" variant of the font, which makes it
  very unreadable in applications such as Chrome (when it has to fall back
  on Chinese fonts on a mostly-English page). I had to remove the package
  and then manually download the font from Google website and install it
  to make the regular weight available
  
  Release: 16.04 LTS
  Package Version: 1.004+repack1-1
  Expected: All weights of the noto cjk font to be installed
  Happened: Only the "thin" weight of the font seems to be installed

** No longer affects: language-selector (Ubuntu Xenial)

** No longer affects: language-selector (Ubuntu)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/157

Title:
  Chrome/Chromium use "Thin" as default font weight

Status in fonts-noto-cjk package in Ubuntu:
  In Progress
Status in fonts-noto-cjk source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Chromium and Google Chrome use "Thin" as the default Noto Sans CJK
  font weight, which makes some Chinese and Japanese web pages difficult
  to read, and thus gives a bad user experience.

  The fonts-noto-cjk version in the PPA

  https://launchpad.net/~gunnarhj/+archive/ubuntu/fonts-noto-cjk

  installs 7 weight specific font files instead of a single "super"
  file. This works around the Chromium/Chrome issue.

  [Test Case]

  To reproduce the bug:

  * Install Chromium or Google Chrome.
  * Go to  and notice the very thin characters.
  * Install fonts-noto-cjk from the PPA and notice the difference.

  [Regression Potential]

  This is about another font packaging form, without any change in glyph
  coverage, so the the regression risk should be low.

  [Original description]

  The package seems to only "thin" variant of the font, which makes it
  very unreadable in applications such as Chrome (when it has to fall
  back on Chinese fonts on a mostly-English page). I had to remove the
  package and then manually download the font from Google website and
  install it to make the regular weight available

  Release: 16.04 LTS
  Package Version: 1.004+repack1-1
  Expected: All weights of the noto cjk font to be installed
  Happened: Only the "thin" weight of the font seems to be installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/157/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1551986] Re: [FFe][UIFe] HUD hotkey assignment is suboptimal

[Gunnar Hjalmarsson]

** Also affects: ubuntu-docs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-docs (Ubuntu)
Milestone: None => later

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1551986

Title:
  [FFe][UIFe] HUD hotkey assignment is suboptimal

Status in bamf package in Ubuntu:
  In Progress
Status in compiz package in Ubuntu:
  In Progress
Status in hud package in Ubuntu:
  In Progress
Status in libwnck3 package in Ubuntu:
  In Progress
Status in ubuntu-docs package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  In Progress
Status in bamf source package in Xenial:
  In Progress
Status in compiz source package in Xenial:
  In Progress
Status in hud source package in Xenial:
  In Progress
Status in libwnck3 source package in Xenial:
  In Progress
Status in unity source package in Xenial:
  In Progress

Bug description:
  = Proposed Change =
  The suggestion (subject to Design approval) is to remap HUD to alt-space and 
also expose window controls in to the HUD such that people used to using 
"alt-space n"to minimize a window still can.

  = Motivation =
  Having HUD trigger on alt tap is not working so this is a request to change 
it. It conflicts with several other applications such as full screen games, etc.

  = Potential Regressions =
  * Hud fails to open on alt+space
  * Hud fails to show normal menu entries for gtk applications
  * Hud fails to show normal menu entries for qt applications

  == Links to mailing lists ==
  * https://lists.ubuntu.com/archives/ubuntu-translators/2016-April/007138.html
  * https://lists.ubuntu.com/archives/ubuntu-doc/2016-April/019870.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1551986/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp