[Touch-packages] [Bug 2045245] Re: ubuntu22.04 ibus Chinese pinying input not response

[Gunnar Hjalmarsson]

Thanks for your report.

It's hard to comment on without more info. Possibly there is a need to
clean the cache in ~/.cache/ibus/libpinyin .

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2045245

Title:
  ubuntu22.04 ibus Chinese pinying input not response

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  I have used 22.04 many times, and I encountered this problem every time. 
During the first period of installing the system, everything was fine, but once 
I used the system for more than a few months, the ibus started to stop 
responding and I could not enter. There is no response when pressing any keys 
on the keyboard. 
  The only solution is to manually click the input method icon in the upper 
right corner, switch to English, and then enter `ibus restart`. But this 
problem of input method not responding is too frequent and occurs every few 
minutes. I can't stand this torture anymore, and I now use a third-party input 
method.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

On 2023-11-24 21:06, BloodyIron wrote:
> For me removing "fonts-wine" "solved" the problem,

Well, it solved *your* problem, which we now know is of another nature
() than the issue with the ubuntu-
release-upgrader UI dealt with in this bug report.

** Bug watch added: Debian Bug tracker #883973
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883973

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2043442] Re: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

[Gunnar Hjalmarsson]

Thanks for your report.

I see Plasma and Wayland, which reminds me of
 and .

* Have you applied the IBus Wayland virtual keyboard?

* If you have, can you please run this command:

  im-config -n none

  and reboot, and then let us know if that improves things.

** Bug watch added: Debian Bug tracker #1052005
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052005

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2043442

Title:
  /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  Apport captured a system freeze [crash] which required a hard reboot.
  However I could not confirm that the report was successfully uploaded.

  The /var/log/apport.log entry is as follows.
  
  ERROR: apport (pid 17772) 2023-11-13 17:17:02,197: this executable already 
crashed 2 times, ignoring
  INFO: apport (pid 27019) 2023-11-13 21:07:39,820: called for pid 17786, 
signal 11, core limit 0, dump mode 1
  INFO: apport (pid 27019) 2023-11-13 21:07:39,821: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
  ERROR: apport (pid 27019) 2023-11-13 21:07:40,821: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  INFO: apport (pid 27019) 2023-11-13 21:07:42,687: wrote report 
/var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
  INFO: apport (pid 29410) 2023-11-13 21:38:11,084: called for pid 27746, 
signal 11, core limit 0, dump mode 1
  INFO: apport (pid 29410) 2023-11-13 21:38:11,085: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
  ERROR: apport (pid 29410) 2023-11-13 21:38:12,085: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  Note:The last line may explain why I could not verify the file
  upload when I performed the following proceedure per:
  https://help.ubuntu.com/community/ReportingBugs

  ---
  luigi@l-g905:~$ ubuntu-bug /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash

  luigi@l-g905:~$ sudo cat /var/lib/whoopsie/whoopsie-id
  
7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80

  
https://errors.ubuntu.com/user/7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80:
 No such file or directory
  -

  
  This upload fialure seemed confirmed when in: 
https://answers.launchpad.net/ubuntu/+questions?
  a search found no Questions matching "ibus-ui-gtk3" for Ubuntu
  "ibus-ui-gtk3" is not mentioned in the release notes bugs section.

  In
  https://errors.ubuntu.com/?release=Ubuntu%2023.10&period=day
  text Searches for _usr_libexec_ibus-ui-gtk3 and the "Whoopsie-id" above both 
returned "phrase not found"

  I reproduced the executable failure using Terminal with these results
  --
  ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

  Returns:
  ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

  (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
  assertion '(offset + len) <= string_length' failed

  (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
  assertion '(offset + len) <= string_length' failed

  ** (ibus-ui-gtk3:9353): ERROR **: 23:11:04.236: No input_method global

  Trace/breakpoint trap (core dumped)
  -

  I am attaching the _usr_libexec_ibus-ui-gtk3.1000.crash file
  /var/crash/ _ust_libexec_ibus-ui-gtk3.1000.crash (3.1 MiB - 1144 lines
  - modified on 11/13/23 9:07 PM - US-ASCII)

  Platform Information 
  Operating System: Ubuntu Studio 23.10
  KDE Plasma Version:   5.27.8
  KDE Frameworks Version:   5.110.0
  Qt Version:   5.15.10
  Kernel Version:   6.5.0-10-lowlatency (64-bit)
  Graphics Platform:Wayland
  Processors:   24 × AMD Ryzen 9 7900X 12-Core Processor
  Memory:   31.0 GiB of RAM
  Graphics Processor:   NV172
  Manufacturer: MicroElectronics
  Product Name: G905
  System Version:   1.0

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


-- 
Mailing list: https://launchpad.net/~touch-pa

[Touch-packages] [Bug 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly

[Gunnar Hjalmarsson]

On 2023-11-13 18:44, Marius Gedminas wrote:
> Debian reverted the change to isolate these low quality fonts from the
> rest of the system in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883973, and now this
> bug is back in Ubuntu 23.10.

Good catch! That Debian bug was filed in 2017, and "the fix" of it was
uploaded in Ubuntu here:

https://launchpad.net/ubuntu/+source/wine/8.0.1~repack-2

So: Some users like that the .ttf files in fonts-wine are treated as
system fonts, and some users dislike it. If you dislike it, please
submit a Debian bug and request that "the fix" of
 gets reverted. Given the subjective
nature of the issue, it would not make sense to change it back in Ubuntu
only.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/412195

Title:
  ttf-tahoma-replacement makes some web-sites look ugly

Status in fontconfig package in Ubuntu:
  Invalid
Status in wine1.2 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: wine1.2

  This font package is good for wine 1.2; however, it also makes sites
  look ugly in Firefox and other browsers. I had to manually remove the
  fonts from /usr/share/fonts/ to rectfiy this, because removing the
  package through apt would have made me remove wine 1.2 and I didn't
  want that.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Aug 12 00:23:40 2009
  DistroRelease: Ubuntu 9.10
  Package: ttf-tahoma-replacement 1.1.27-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: wine1.2
  Uname: Linux 2.6.31-5-generic i686

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly

[Gunnar Hjalmarsson]

@Jaromir, @Bloodyiron: This bug was closed more than a decade ago.
Please don't waste time with adding new comments here.

If you see issues (beyond personal preferences) with fonts-wine, please
submit a new bug:

ubuntu-bug wine

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/412195

Title:
  ttf-tahoma-replacement makes some web-sites look ugly

Status in fontconfig package in Ubuntu:
  Invalid
Status in wine1.2 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: wine1.2

  This font package is good for wine 1.2; however, it also makes sites
  look ugly in Firefox and other browsers. I had to manually remove the
  fonts from /usr/share/fonts/ to rectfiy this, because removing the
  package through apt would have made me remove wine 1.2 and I didn't
  want that.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Aug 12 00:23:40 2009
  DistroRelease: Ubuntu 9.10
  Package: ttf-tahoma-replacement 1.1.27-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: wine1.2
  Uname: Linux 2.6.31-5-generic i686

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2043234] Re: Symlink for resolv.conf is wrong on fresh install

[Gunnar Hjalmarsson]

** Package changed: ubuntu-docs (Ubuntu) => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2043234

Title:
  Symlink for resolv.conf is wrong on fresh install

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello. Sorry for disturb, may I ask you please to confirm if im not doing 
anything wrong with new installation?
  Its being a while since the problem exists AT LEAST IN MY CASE with "faulty 
path" for symlinc at resolv.conf
  I believe its keep happening since 18.04 version and even now in 22.04
  So, in the fresh install the path looks like this:
  lrwxrwxrwx  1 root root 39 Feb 17  2023 resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  but once im running :
  sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

  everything works fine. By everything I mean when I run nslookup.

  Regards,

  Vitalii Sharapov

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

Ok.

This bug is focused on the UI for the upgrader itself. I would recommend
you to ask a question at Ask Ubuntu. That way you'll hopefully get help
to determine if it is a problem with your configuration or some kind of
bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

@Bloodyiron: Does it help to reboot?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

I made a verification attempt for mantic of the 1:23.10.12 changes.

https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/2039356/comments/3

While those changes are included in 1:23.10.13, the specific change in
1:23.10.13 (letting do-release-upgrade set the XDG_CURRENT_DESKTOP
variable) was not included in that verification and needs to be decided
on separately.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

@Nathan: I think you actually describe the underlying reason why this is
an issue. For running processes which use a particular font, you'll see
the characters become corrupted if you replace the related font file,
and it will fix itself when you restart the process.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

@Michael: Then you hadn't installed version version 1:23.04.7 of ubuntu-
release-upgrader first, right? Please compare comment #44.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

Since I propose yet another SRU, I created bug #2039356. This bug report
is quite noisy already...

My examination of the flavors with respect to this issue focused on two
questions:

1. Does the u-r-u model effectively prevent 'the unreadable text issue'
when the desktop font in use — whether default or set by the user — has
changed during the cycle?

After the changes proposed via bug #2039356 I would say "yes" for:

 Ubuntu Desktop
 Ubunu Budgie
 Ubuntu Cinnamon
 Ubuntu Kylin
 Ubuntu MATE
 Ubuntu Unity

while the model (i.e. temporarily changing a dconf value which
represents the desktop font) is not effective for:

 Kubuntu
 Lubuntu
 Xubuntu

In case of Kubuntu and Lubuntu the Qt way of dealing with fonts seems to
require something else, and the Xfce way applied in Xubuntu means
similar difficulties. Fortunately all those flavors use a desktop font
by default (Noto Sans) which was not changed during the cycle, so this
does not need to be addressed for mantic.

But if you like, you can trigger the 23.04 -> 23.10 upgrade issue in for
instance Xubuntu: Go to Settings -> Appearance -> Fonts and change the
"Default Font" from Noto Sans to Ubuntu. Doing so will be reflected both
in the ~/.config/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml file and
in dconf (gsettings get org.gnome.desktop.interface font-name), but
changing the font-name dconf value only to something else during upgrade
(as we do) won't change the effective desktop font in Xubuntu, which
results in 'the unreadable text issue'.

2. Is the temporary desktop font dconf value properly reset at next
login after reboot?

Yes it is, after the changes proposed via bug #2039356.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Committed
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0u

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

On 2023-10-13 22:10, Jeremy Bícha wrote:
> Gunnar, I tested these desktop flavors successfully (23.04 to 23.10):
> - Ubuntu Desktop
> - Ubuntu Budgie
> - Ubuntu Kylin
> - Kubuntu
> - Lubuntu
> - Xubuntu

Thanks for reporting that. I have not found otherwise.

But in most of those cases (not Ubuntu Desktop) the text keeps being
readable simply because they use a font (read: Noto Sans) which hasn't
changed during the cycle.

> That means I also missed Ubuntu Unity.

I think the fix already in place applies to Unity too.

I'll explain more when posting about my next MP. :/

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Committed
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : http

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

I'm investigating the flavors in this respect more systematically, and
just found that a 23.04 -> 23.10 upgrade of Ubuntu Cinnamon is still hit
by this issue (they use the schema org.cinnamon.desktop.interface ...).
So adding the Cinnamon project for now.

I will soon come up with a proposal for mantic to deal with some details
including the Cinnamon issue.

** Also affects: cinnamon-project
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-meta (Ubuntu Lunar)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

On 2023-10-12 18:39, Brian Murray wrote:
> however the title bar was corrupted but that's fine.

Yeah, that's expected. I didn't think it was motivated to play with
multiple dconf keys only for MATE.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

Hmm.. The XDG_CURRENT_DESKTOP variable keeps being present when you use
sudo, which is the reason why we successfully tested the MATE specific
code. Apparently the pkexec environment differs.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

@Ethan: MATE is about to be fixed. Once ubuntu-release-upgrader
1:23.10.10 has made it to mantic-release, you shouldn't be able to
reproduce that. Let us know otherwise.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

I just ran an errand, and thought about that font workaround. The MATE
issue makes me doubt about running the code for all the flavors.

We know that the root cause is changes to the Ubuntu font. That font is
explicitly used for desktop in standard Ubuntu and MATE. But is it used
for desktop by any other flavor?

I fear that we for other flavors mess with their settings unnecessarily.
If the reset succeeds, it doesn't matter much, but maybe more flavors
have not enabled the required systemd integration, and then our
'temporary' change gets persistent. Which may or may not matter in
practice.

So maybe it would be better to only run the code for flavors where we
know that it makes a difference. Something like:

is_mate = False
desktops = os.getenv('XDG_CURRENT_DESKTOP', '').split(':')
if 'MATE' in desktops:
schema = 'org.mate.interface'
is_mate = True
else if 'GNOME' in desktops:
schema = 'org.gnome.desktop.interface'
else if 'xxx' in desktops:
schema = 'yyy'
else:
return

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

** Changed in: ubuntu-release-upgrader (Ubuntu Mantic)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

Thanks Chris! Possibly no other flavor is affected by this issue, at
least not in this cycle.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Triaged

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

I submitted a MP to make the fix apply to MATE. It's not without issues,
though (see the linked MP), and I think we need involvement from the
MATE developers.

** Merge proposal linked:
   
https://code.launchpad.net/~gunnarhj/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/453086

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Triaged

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

To the extent I participated in the resolution of this bug, I had
standard Ubuntu in mind, where the default desktop font can be accessed
like this:

gsettings get org.gnome.desktop.interface font-name

And that's the key whose value is temporarily changed when upgrading to
23.10. But on MATE that does not help, since MATE uses its own schema:

gsettings get org.mate.interface font-name

And since MATE uses the Ubuntu font by default, the issue is identical
to the issue in standard Ubuntu. I think the fix in ubuntu-release-
upgrader can be adjusted so it interacts with the schema which is
actually in use in MATE.

But this makes me wonder if there is a need to special case other
flavors besides MATE.

** Also affects: ubuntu-mate
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Triaged

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers

[Gunnar Hjalmarsson]

Added yelp as affected package too, since you hit this bug if you browse
the desktop guide on X11/NVIDIA.

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

** Changed in: yelp (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/2023322

Title:
  Unable to setup Google Online Accounts with Nvidia drivers

Status in Webkit:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in webkit2gtk package in Ubuntu:
  Incomplete
Status in yelp package in Ubuntu:
  Triaged
Status in webkit2gtk package in Debian:
  Confirmed

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 0

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

On 2023-09-26 22:32, Gunnar Hjalmarsson wrote:
> But one of the changes in mantic is that no font is safely present
> (i.e. the default ones are "Recommends:" only). So later, when people
> will upgrade from 23.10 to 24.04, just using "Sans" temporarily may
> not be the best option. And changing it to a specific font family is
> tricky, since we don't know if the user has uninstalled some of the
> default font packages.
> 
> So my thought is: Can this be a reason to let desktop-common depend
> on, and not only recommend, some font package after all? And if so,
> which package would be suitable for the purpose?

To make it easier to keep 'the temporary font' approach in 24.04 — if
that is what we want by then — I added a hard dependency on fonts-
dejavu-core to desktop-common. No upstream changes to the DejaVu fonts
have been made the last 6 years, so it's more or less unmaintained,
which in this context is an advantage.

** Changed in: ubuntu-meta (Ubuntu Mantic)
   Status: Confirmed => In Progress

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  In Progress
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

@Nick: That would be an improvement indeed. Guess you abandon /tmp then.
;)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

On 2023-09-26 22:52, Steve Langasek wrote:
> Trying to think in terms of robust general solutions to this problem,
> what if update-manager were to notice when fonts were upgraded, and
> when they are, shut down the GUI connection and reinitialize it?
> This might require saving a bit of state information in
> update-manager in order to be able to restore it.

If I was in a nitpicking mode I would mention that the unreadable
character problem also affects the desktop itself and possible open
programs (even if the latter is advised against). So it's not obvious to
me that the approach you mention would be better.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

Hopefully an ubuntu-release-upgrader workaround will be in place soon.

But in a sense this is an ubuntu-meta matter as well. The code in my
merge proposal sets the "Sans" font temporarily, which in lunar means
that either DejaVu Sans or Noto Sans will be used in the UI during the
upgrade (unless the user has configured fontconfig to use some other
font...). And that is fine in lunar, since DejaVu Sans is always
present, and neither DejaVu Sans nor Noto Sans were changed during the
mantic cycle.

But one of the changes in mantic is that no font is safely present (i.e.
the default ones are "Recommends:" only). So later, when people will
upgrade from 23.10 to 24.04, just using "Sans" temporarily may not be
the best option. And changing it to a specific font family is tricky,
since we don't know if the user has uninstalled some of the default font
packages.

So my thought is: Can this be a reason to let desktop-common depend on,
and not only recommend, some font package after all? And if so, which
package would be suitable for the purpose?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

@Daniel: Maybe I answered a bit hasty. I see this issue over and over
again without any Nvidia driver. But I do have a Nvidia card, if that
may be related.

Not sure about the root cause of this bug. We know that it happens with
the Ubuntu font and that that font was changed in the mantic cycle. But
is the font change to blame, or is it maybe some inability in
Gtk/Pango/whatever to deal with a font change smoothly? Or is it a
limitation in fontconfig? Would the issue show up if some other font in
use had been changed, even if it was not set via the font-name dconf
value?

Those are thoughts in my head.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

** Changed in: ubuntu-release-upgrader (Ubuntu Mantic)
   Status: Confirmed => In Progress

** Changed in: ubuntu-release-upgrader (Ubuntu Mantic)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  In Progress

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

On 2023-09-25 03:15, Daniel van Vugt wrote:
> is it specific to Nvidia desktops like bug 1876632?

No.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

@Steve: I made such a change to the MR.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

** Merge proposal linked:
   
https://code.launchpad.net/~gunnarhj/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/451815

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

The attached script is an attempt to express my idea in python code. I
don't know where exactly I'd put those commands, though, so that's why I
abstain from a merge request.

** Attachment added: "proposed_commands.py"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2034986/+attachment/5702529/+files/proposed_commands.py

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

Without my workaround, I didn't even get that far, but it hanged before
the "Cleaning up" phase. I could reboot manually, though.

With the workaround, the upgrade completed including "Cleaning up".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

Gunnar Hjalmarsson wrote:
> Maybe it would be sufficient to drop the Ubuntu font as the first choice and
> simply let fontconfig deal with it for everyone.

I tested that approach. On an updated lunar I run this command:

gsettings set org.gnome.desktop.interface font-name 'Sans 11'

before doing "update-manager -d". The upgrade completed successfully
without font rendering issues.

So as a workaround I'm thinking that an equivalent of that command could
be added to the beginning of the main function in DistUpgradeViewGtk3.py
file (before the first "Gtk.main()" call), while the equivalent of this
command:

gsettings reset org.gnome.desktop.interface font-name

could be executed right before the computer is restarted.

Or maybe just a wrapper.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

> What about this idea for a workaround: have the upgrader temporarily
switch the UI font to a font that hasn't been changed since Jammy?

That sounds as a reasonable idea. Maybe it would be sufficient to drop
the Ubuntu font as the first choice and simply let fontconfig deal with
it for everyone.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2034986

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1966552] Re: IBus input method candidate box cannot follow the cursor

[Gunnar Hjalmarsson]

Marking this as invalid for ibus and ibus-libpinyin. ibus upstream
provided an explanation and confirmed that the workaround makes sense.

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

** Changed in: ibus-libpinyin (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1966552

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus:
  Fix Released
Status in ibus package in Ubuntu:
  Invalid
Status in ibus-libpinyin package in Ubuntu:
  Invalid

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here：https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

[Gunnar Hjalmarsson]

>   1. Patch to revert to a colon in the default US English translation.
> 
>   2. Propose to upstream to not use RATIO in future because fonts don't
> often implement the Mathematical Operators block.

Those were my reflexive thoughts too, especially item 2. But then I saw
that RATIO has been used for several years at the request of GNOME's
design team, and I don't have the energy right now to argue with those
folks. :/

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-gnome-en in
Ubuntu.
https://bugs.launchpad.net/bugs/2033377

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-desktop package in Ubuntu:
  Won't Fix
Status in language-pack-gnome-en package in Ubuntu:
  Won't Fix
Status in language-pack-gnome-en-base package in Ubuntu:
  Won't Fix
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  Package: gnome-shell 44.3-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

[Gunnar Hjalmarsson]

For the record: The different results depending on locale is a
"translation" matter. While the default time separator is \u2236, it has
been "translated" for e.g. en_GB in Ubuntu into \u003A:

https://translations.launchpad.net/ubuntu/mantic/+source/gnome-
desktop/+pots/gnome-desktop-3.0/en_GB/24

$ printf '\u2236\n'
∶
$ printf '\u003A\n'
:

So with the en_GB.UTF-8 locale it displays a regular colon character,
which the Ubuntu font can render.

(Daniel: I can't explain how you hid the issue by using en_AU.UTF-8,
though.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-gnome-en in
Ubuntu.
https://bugs.launchpad.net/bugs/2033377

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-desktop package in Ubuntu:
  Confirmed
Status in language-pack-gnome-en package in Ubuntu:
  New
Status in language-pack-gnome-en-base package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  Package: gnome-shell 44.3-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

[Gunnar Hjalmarsson]

Why do they mess with that math symbol in gnome-desktop?

Anyway, the issue surfaced because of the font changes I made.
Previously DejaVu Sans was used to render the Ratio character, and now,
when the fonts-dejavu-core package is not present, DejaVu Sans Mono
seems to be used instead. Hence the extra whitespace.

I uploaded a language-selector change so it uses Noto Sans Math for
rendering Ratio.

https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/language-
selector/commit/?id=fc7ec106

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

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

** Changed in: language-selector (Ubuntu)
   Status: New => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-gnome-en in
Ubuntu.
https://bugs.launchpad.net/bugs/2033377

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-desktop package in Ubuntu:
  Confirmed
Status in language-pack-gnome-en package in Ubuntu:
  New
Status in language-pack-gnome-en-base package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  Fix Committed

Bug description:
  This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  Package: gnome-shell 44.3-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2033129] Re: hplip is in universe and was dropped from Recommends

[Gunnar Hjalmarsson]

hplip is back in main and shipped on the ISO again. Closing this to
reduce unnecessary noise.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2033129

Title:
  hplip is in universe and was dropped from Recommends

Status in hplip package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  When preparing the upload of ubuntu-meta 1.516 I wasn't enough
  attentive. Only afterwards I noticed that the update script had caused
  hplip to be removed from the meta packages, even if it is still here:

  https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/platform/tree/desktop-common#n69

  I don't know how to properly correct this. Please help.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

[Gunnar Hjalmarsson]

@Sebastien: Is this bug ready to be closed again?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2024560

Title:
  Check if 0010-set-language needs to be update for the new languages
  property

Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  Upstream did changes to add a languages properties

  
https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7

  I've rebased 0010-set-language to apply correctly but we should review
  if we need to adapt the patch to apply a similar logic to the new
  languages property that it's doing for old language one

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

[Gunnar Hjalmarsson]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1996652

Title:
  Nautilus search is slow and jumbles keyboard input on 22.10

Status in ibus:
  Fix Released
Status in ibus package in Ubuntu:
  In Progress

Bug description:
  Since my upgrade to 22.10, I've found the search box in Nautilus
  (files) essentially unusable.  It is notably sluggish to launch and
  browse in general.  But most detrimental to the usability is this:

  The characters do not appear in real time as I type. When they do
  appear, they are sometimes jumbled or in reverse (consistently
  reproducible).  As I type in the file search box, the circular cursor
  spins intermittently, then the UI catches up and it's not what I
  typed.

  For example, I just typed "umbrella" into the search box, and Nautilus 
searched for:
  "umballer"

  Off-the-cuff test #2, searched for "Ubuntu" and I ended up with
  "Ubunut" ... you can't make this up. :-)

  Test #3, typed Launchpad, ended up with a search for "Laudaphcn".

  Keyboard input everywhere else on the system is otherwise normal and
  snappy.  No pun intended, really.

  FWIW Nautilus files preferences are as default (Search in subfolders,
  Show thumbnails, File count == This computer only).

  

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:43.0-1ubuntu1
Candidate: 1:43.0-1ubuntu1
Version table:
   *** 1:43.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ uname -r
  5.19.0-23-generic

  $ lsb_release -rd
  Description:Ubuntu 22.10
  Release:22.10

  $ snap list
  Name   Version   RevTracking 
Publisher  Notes
  bare   1.0   5  latest/stable
canonical✓ base
  core   16-2.57.2 13886  latest/stable
canonical✓ core
  core18 20221027  2620   latest/stable
canonical✓ base
  core20 20221027  1695   latest/stable
canonical✓ base
  gnome-3-34-18040+git.3556cb3 77 latest/stable/…  
canonical✓ -
  gnome-3-38-20040+git.6f39565 119latest/stable
canonical✓ -
  google-cloud-sdk   409.0.0   298latest/stable
google-cloud-sdk✓  classic
  gtk-common-themes  0.1-81-g442e511   1535   latest/stable/…  
canonical✓ -
  snap-store 41.3-64-g512c0ff  599latest/stable/…  
canonical✓ -
  snapd  2.57.417336  latest/stable
canonical✓ snapd
  snapd-desktop-integration  0.1   14 latest/stable/…  
canonical✓ -

  
  Side question:  Since this system has transitioned across several upgrades 
from 20.04 to 22.10, do I really need all of these core* and gnome* snaps?

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

[Gunnar Hjalmarsson]

@Federico: The x11 issue you spotted has now been fixed through updated
patches, and the PPA has been updated with the latest patch versions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1996652

Title:
  Nautilus search is slow and jumbles keyboard input on 22.10

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade to 22.10, I've found the search box in Nautilus
  (files) essentially unusable.  It is notably sluggish to launch and
  browse in general.  But most detrimental to the usability is this:

  The characters do not appear in real time as I type. When they do
  appear, they are sometimes jumbled or in reverse (consistently
  reproducible).  As I type in the file search box, the circular cursor
  spins intermittently, then the UI catches up and it's not what I
  typed.

  For example, I just typed "umbrella" into the search box, and Nautilus 
searched for:
  "umballer"

  Off-the-cuff test #2, searched for "Ubuntu" and I ended up with
  "Ubunut" ... you can't make this up. :-)

  Test #3, typed Launchpad, ended up with a search for "Laudaphcn".

  Keyboard input everywhere else on the system is otherwise normal and
  snappy.  No pun intended, really.

  FWIW Nautilus files preferences are as default (Search in subfolders,
  Show thumbnails, File count == This computer only).

  

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:43.0-1ubuntu1
Candidate: 1:43.0-1ubuntu1
Version table:
   *** 1:43.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ uname -r
  5.19.0-23-generic

  $ lsb_release -rd
  Description:Ubuntu 22.10
  Release:22.10

  $ snap list
  Name   Version   RevTracking 
Publisher  Notes
  bare   1.0   5  latest/stable
canonical✓ base
  core   16-2.57.2 13886  latest/stable
canonical✓ core
  core18 20221027  2620   latest/stable
canonical✓ base
  core20 20221027  1695   latest/stable
canonical✓ base
  gnome-3-34-18040+git.3556cb3 77 latest/stable/…  
canonical✓ -
  gnome-3-38-20040+git.6f39565 119latest/stable
canonical✓ -
  google-cloud-sdk   409.0.0   298latest/stable
google-cloud-sdk✓  classic
  gtk-common-themes  0.1-81-g442e511   1535   latest/stable/…  
canonical✓ -
  snap-store 41.3-64-g512c0ff  599latest/stable/…  
canonical✓ -
  snapd  2.57.417336  latest/stable
canonical✓ snapd
  snapd-desktop-integration  0.1   14 latest/stable/…  
canonical✓ -

  
  Side question:  Since this system has transitioned across several upgrades 
from 20.04 to 22.10, do I really need all of these core* and gnome* snaps?

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

[Gunnar Hjalmarsson]

Nah, it's fine to test on lunar. I do it on mantic since I don't have a
lunar installation easily available.

Previously, when I couldn't reproduce, I tested in a Wayland session.
Now I have tried "Ubuntu on Xorg", and there I see bad things when using
gnome-terminal or gedit, i.e. gtk3 applications. When trying to use a
dead key followed by a character, it all disappears. And it's not only
dead keys: The same happens when trying to input a character using
Ctrl+Shift+U or when trying to use some advanced input method, e.g.
ibus-libpinyin.

Are you able to confirm that the issue is limited to gtk3 applications
in X sessions?

I reported the observation on the upstream issue:
https://github.com/ibus/ibus/issues/2486#issuecomment-1625042967

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1996652

Title:
  Nautilus search is slow and jumbles keyboard input on 22.10

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade to 22.10, I've found the search box in Nautilus
  (files) essentially unusable.  It is notably sluggish to launch and
  browse in general.  But most detrimental to the usability is this:

  The characters do not appear in real time as I type. When they do
  appear, they are sometimes jumbled or in reverse (consistently
  reproducible).  As I type in the file search box, the circular cursor
  spins intermittently, then the UI catches up and it's not what I
  typed.

  For example, I just typed "umbrella" into the search box, and Nautilus 
searched for:
  "umballer"

  Off-the-cuff test #2, searched for "Ubuntu" and I ended up with
  "Ubunut" ... you can't make this up. :-)

  Test #3, typed Launchpad, ended up with a search for "Laudaphcn".

  Keyboard input everywhere else on the system is otherwise normal and
  snappy.  No pun intended, really.

  FWIW Nautilus files preferences are as default (Search in subfolders,
  Show thumbnails, File count == This computer only).

  

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:43.0-1ubuntu1
Candidate: 1:43.0-1ubuntu1
Version table:
   *** 1:43.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ uname -r
  5.19.0-23-generic

  $ lsb_release -rd
  Description:Ubuntu 22.10
  Release:22.10

  $ snap list
  Name   Version   RevTracking 
Publisher  Notes
  bare   1.0   5  latest/stable
canonical✓ base
  core   16-2.57.2 13886  latest/stable
canonical✓ core
  core18 20221027  2620   latest/stable
canonical✓ base
  core20 20221027  1695   latest/stable
canonical✓ base
  gnome-3-34-18040+git.3556cb3 77 latest/stable/…  
canonical✓ -
  gnome-3-38-20040+git.6f39565 119latest/stable
canonical✓ -
  google-cloud-sdk   409.0.0   298latest/stable
google-cloud-sdk✓  classic
  gtk-common-themes  0.1-81-g442e511   1535   latest/stable/…  
canonical✓ -
  snap-store 41.3-64-g512c0ff  599latest/stable/…  
canonical✓ -
  snapd  2.57.417336  latest/stable
canonical✓ snapd
  snapd-desktop-integration  0.1   14 latest/stable/…  
canonical✓ -

  
  Side question:  Since this system has transitioned across several upgrades 
from 20.04 to 22.10, do I really need all of these core* and gnome* snaps?

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

[Gunnar Hjalmarsson]

@Federico: Thanks for testing and reporting that observation!

I can't reproduce it (on mantic), though. Dead keys work as expected for
me, also with the keyboard layout you mentioned.

Are you sure that the issue is related to the proposed ibus version?
Does the issue go away if you downgrade to the released version? Are you
testing on lunar or mantic?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1996652

Title:
  Nautilus search is slow and jumbles keyboard input on 22.10

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade to 22.10, I've found the search box in Nautilus
  (files) essentially unusable.  It is notably sluggish to launch and
  browse in general.  But most detrimental to the usability is this:

  The characters do not appear in real time as I type. When they do
  appear, they are sometimes jumbled or in reverse (consistently
  reproducible).  As I type in the file search box, the circular cursor
  spins intermittently, then the UI catches up and it's not what I
  typed.

  For example, I just typed "umbrella" into the search box, and Nautilus 
searched for:
  "umballer"

  Off-the-cuff test #2, searched for "Ubuntu" and I ended up with
  "Ubunut" ... you can't make this up. :-)

  Test #3, typed Launchpad, ended up with a search for "Laudaphcn".

  Keyboard input everywhere else on the system is otherwise normal and
  snappy.  No pun intended, really.

  FWIW Nautilus files preferences are as default (Search in subfolders,
  Show thumbnails, File count == This computer only).

  

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:43.0-1ubuntu1
Candidate: 1:43.0-1ubuntu1
Version table:
   *** 1:43.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ uname -r
  5.19.0-23-generic

  $ lsb_release -rd
  Description:Ubuntu 22.10
  Release:22.10

  $ snap list
  Name   Version   RevTracking 
Publisher  Notes
  bare   1.0   5  latest/stable
canonical✓ base
  core   16-2.57.2 13886  latest/stable
canonical✓ core
  core18 20221027  2620   latest/stable
canonical✓ base
  core20 20221027  1695   latest/stable
canonical✓ base
  gnome-3-34-18040+git.3556cb3 77 latest/stable/…  
canonical✓ -
  gnome-3-38-20040+git.6f39565 119latest/stable
canonical✓ -
  google-cloud-sdk   409.0.0   298latest/stable
google-cloud-sdk✓  classic
  gtk-common-themes  0.1-81-g442e511   1535   latest/stable/…  
canonical✓ -
  snap-store 41.3-64-g512c0ff  599latest/stable/…  
canonical✓ -
  snapd  2.57.417336  latest/stable
canonical✓ snapd
  snapd-desktop-integration  0.1   14 latest/stable/…  
canonical✓ -

  
  Side question:  Since this system has transitioned across several upgrades 
from 20.04 to 22.10, do I really need all of these core* and gnome* snaps?

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

[Gunnar Hjalmarsson]

My first upload to the PPA proved to not be complete. Corrected now.
(Wait for the builds to finish and the packages to be published before
updating).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1996652

Title:
  Nautilus search is slow and jumbles keyboard input on 22.10

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade to 22.10, I've found the search box in Nautilus
  (files) essentially unusable.  It is notably sluggish to launch and
  browse in general.  But most detrimental to the usability is this:

  The characters do not appear in real time as I type. When they do
  appear, they are sometimes jumbled or in reverse (consistently
  reproducible).  As I type in the file search box, the circular cursor
  spins intermittently, then the UI catches up and it's not what I
  typed.

  For example, I just typed "umbrella" into the search box, and Nautilus 
searched for:
  "umballer"

  Off-the-cuff test #2, searched for "Ubuntu" and I ended up with
  "Ubunut" ... you can't make this up. :-)

  Test #3, typed Launchpad, ended up with a search for "Laudaphcn".

  Keyboard input everywhere else on the system is otherwise normal and
  snappy.  No pun intended, really.

  FWIW Nautilus files preferences are as default (Search in subfolders,
  Show thumbnails, File count == This computer only).

  

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:43.0-1ubuntu1
Candidate: 1:43.0-1ubuntu1
Version table:
   *** 1:43.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ uname -r
  5.19.0-23-generic

  $ lsb_release -rd
  Description:Ubuntu 22.10
  Release:22.10

  $ snap list
  Name   Version   RevTracking 
Publisher  Notes
  bare   1.0   5  latest/stable
canonical✓ base
  core   16-2.57.2 13886  latest/stable
canonical✓ core
  core18 20221027  2620   latest/stable
canonical✓ base
  core20 20221027  1695   latest/stable
canonical✓ base
  gnome-3-34-18040+git.3556cb3 77 latest/stable/…  
canonical✓ -
  gnome-3-38-20040+git.6f39565 119latest/stable
canonical✓ -
  google-cloud-sdk   409.0.0   298latest/stable
google-cloud-sdk✓  classic
  gtk-common-themes  0.1-81-g442e511   1535   latest/stable/…  
canonical✓ -
  snap-store 41.3-64-g512c0ff  599latest/stable/…  
canonical✓ -
  snapd  2.57.417336  latest/stable
canonical✓ snapd
  snapd-desktop-integration  0.1   14 latest/stable/…  
canonical✓ -

  
  Side question:  Since this system has transitioned across several upgrades 
from 20.04 to 22.10, do I really need all of these core* and gnome* snaps?

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

On 2023-07-03 12:59, Gunnar Hjalmarsson wrote:
> (But I notice another weird issue: In the FF Settings it shows Ubuntu
> as the default serif font irrespective of locale. How come?)

Pls disregard that. User error.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  Fix Released
Status in fontconfig package in Ubuntu:
  Invalid
Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

On 2023-07-03 11:08, Sebastien Bacher wrote:
> Could you use a new bug to discuss the japanese issue?

Yes, Mitsuya plans to submit a new bug once he has checked mantic. (I
have used this one in the meantime to share a couple of thoughts.)

> It could help also to know if you are using the core20 or core22
> version of firefox and they have the same issue.

Mitsuya doesn't see it in jammy, and neither do I:

$ snap run --shell firefox
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

/home/gunnar$ LC_CTYPE=ja_JP.UTF-8 fc-match sans-serif
NotoSansCJK-Regular.ttc: "Noto Sans CJK JP" "Regular"

Even if fonts-droid-fallback is present there too.

(But I notice another weird issue: In the FF Settings it shows Ubuntu as
the default serif font irrespective of locale. How come?)

> Is the configuration in the snap environment matching the real
> system one?

It is not per se, is it? At least not in lunar and mantic, where we use
an upgraded fontconfig in the system.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  Fix Released
Status in fontconfig package in Ubuntu:
  Invalid
Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

I think the reason why fonts-droid-fallback is installed by default is
this dependency chain:

ubuntu-desktop -> ghostscript-x -> ghostscript -> libgs10 ->
libgs10-common -> (recommends) fonts-droid-fallback

A fragile workaround might be to somehow stop fonts-droid-fallback from
being pulled (change libgs10-common so it Suggests instead of Recommends
fonts-droid-fallback). Or maybe we could drop the font configuration
file from the fonts-droid-fallback package.

OTOH, neither would address the root cause — why do the snaps behave as
they do with respect to font configuration?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  Fix Released
Status in fontconfig package in Ubuntu:
  Invalid
Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

> I am concerned that it only affects the snap package, while
> the non-snap package seems to select the correct glyphs.

Yes, that's what it looks like.

$ lsb_release -c
No LSB modules are available.
Codename:   mantic
$ dpkg-query -W fonts-droid-fallback
fonts-droid-fallback1:6.0.1r16-1.1build1
$ snap run --shell firefox
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

/home/gunnar$ LC_CTYPE=ja_JP.UTF-8 fc-match sans-serif
DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular"
/home/gunnar$ exit
exit
$ LC_CTYPE=ja_JP.UTF-8 fc-match sans-serif
NotoSansCJK-Regular.ttc: "Noto Sans CJK JP" "Regular"

So the font configuration of the snaps prioritizes differently compared
to the font configuration of the system. Reason unclear to me ATM.

I also checked in Debian testing, where Firefox is conventionally
packaged. Starting FF there with the Japanese locale results in the
default sans-serif font "VL Gothic". But that's what's expected from the
system font configuration:

$ LC_CTYPE=ja_JP.UTF-8 fc-match sans-serif
VL-Gothic-Regular.ttf: "VL ゴシック" "regular"

(Debian with GNOME has a lot of fonts installed.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  Fix Released
Status in fontconfig package in Ubuntu:
  Invalid
Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

@Mitsuya Shibata: Well, yes it *affects* Japanese fonts too, but it
makes no sense that *this change* would increase the risk of picking
Chinese glyphs under a Japanese locale.

OTOH, if I start Firefox with:

env LC_CTYPE=ja_JP.UTF-8 firefox

the default sans-serif font for me according to FF Settings is Droid
Sans Fallback!! That might have something to do with it.

I see now that the fonts-droid-fallback package is shipped on the ISO
(did we simply forget to drop it?). So as a test, can you please
uninstall that package:

sudo apt purge fonts-droid-fallback

and let us know if it makes a difference.

In any case I think there is a need to reconsider the default font
configuation for Japanese. The
/usr/share/fontconfig/conf.avail/70-fonts-noto-cjk.conf file includes:



ja


sans-serif


Noto Sans CJK JP



while the Chinese equivalents have:



So, Mitsuya Shibata, it would be great if you could submit a new bug
where we can focus on the Japanese font configuration. The
reconsideration would probably affect multiple packages, but language-
selector may be a proper affected package to start with.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  Fix Released
Status in fontconfig package in Ubuntu:
  Invalid
Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

[Gunnar Hjalmarsson]

The IBus maintainer Takao Fujiwara has submitted a pull request which is
intended to address this issue. I applied the pull request and uploaded
IBus (for 23.04 and 23.10) to this PPA:

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

Can users who are affected by the issue please install ibus from my PPA
and let us know — either here or at the upstream issue
https://github.com/ibus/ibus/issues/2486 — if it improves things.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1996652

Title:
  Nautilus search is slow and jumbles keyboard input on 22.10

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade to 22.10, I've found the search box in Nautilus
  (files) essentially unusable.  It is notably sluggish to launch and
  browse in general.  But most detrimental to the usability is this:

  The characters do not appear in real time as I type. When they do
  appear, they are sometimes jumbled or in reverse (consistently
  reproducible).  As I type in the file search box, the circular cursor
  spins intermittently, then the UI catches up and it's not what I
  typed.

  For example, I just typed "umbrella" into the search box, and Nautilus 
searched for:
  "umballer"

  Off-the-cuff test #2, searched for "Ubuntu" and I ended up with
  "Ubunut" ... you can't make this up. :-)

  Test #3, typed Launchpad, ended up with a search for "Laudaphcn".

  Keyboard input everywhere else on the system is otherwise normal and
  snappy.  No pun intended, really.

  FWIW Nautilus files preferences are as default (Search in subfolders,
  Show thumbnails, File count == This computer only).

  

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:43.0-1ubuntu1
Candidate: 1:43.0-1ubuntu1
Version table:
   *** 1:43.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ uname -r
  5.19.0-23-generic

  $ lsb_release -rd
  Description:Ubuntu 22.10
  Release:22.10

  $ snap list
  Name   Version   RevTracking 
Publisher  Notes
  bare   1.0   5  latest/stable
canonical✓ base
  core   16-2.57.2 13886  latest/stable
canonical✓ core
  core18 20221027  2620   latest/stable
canonical✓ base
  core20 20221027  1695   latest/stable
canonical✓ base
  gnome-3-34-18040+git.3556cb3 77 latest/stable/…  
canonical✓ -
  gnome-3-38-20040+git.6f39565 119latest/stable
canonical✓ -
  google-cloud-sdk   409.0.0   298latest/stable
google-cloud-sdk✓  classic
  gtk-common-themes  0.1-81-g442e511   1535   latest/stable/…  
canonical✓ -
  snap-store 41.3-64-g512c0ff  599latest/stable/…  
canonical✓ -
  snapd  2.57.417336  latest/stable
canonical✓ snapd
  snapd-desktop-integration  0.1   14 latest/stable/…  
canonical✓ -

  
  Side question:  Since this system has transitioned across several upgrades 
from 20.04 to 22.10, do I really need all of these core* and gnome* snaps?

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

[Gunnar Hjalmarsson]

It's probably because you still have that colon separated list in your
keyfile in /var/lib/AccountsService/users after having played with
version 23.13.9-1ubuntu1.

* Go to Settings -> Region & Language (it will complain there too)

* Change the language to French, which alters the applicable keyfile
entry to "Languages=fr;"

Does that fix it?

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2024560

Title:
  Check if 0010-set-language needs to be update for the new languages
  property

Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  Upstream did changes to add a languages properties

  
https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7

  I've rebased 0010-set-language to apply correctly but we should review
  if we need to adapt the patch to apply a similar logic to the new
  languages property that it's doing for old language one

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2024870] Re: accountsservice package

[Gunnar Hjalmarsson]

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024870/+attachment/5681555/+files/CoreDump.gz

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2024870

Title:
  accountsservice package

Status in accountsservice package in Ubuntu:
  New

Bug description:
  Error encountered after first boot ubuntu-gnome-desktop installed on
  LiveServer Daily 23.10 attempting to set AutoLogin in Settings>User.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: accountsservice 23.13.9-1ubuntu1
  Uname: Linux 6.3.0-7-generic x86_64
  Architecture: amd64
  Date: Thu Jun 22 21:28:14 2023
  ExecutablePath: /usr/libexec/accounts-daemon
  ExecutableTimestamp: 1687359023
  ProcCmdline: /usr/libexec/accounts-daemon
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 11
  SourcePackage: accountsservice
  UserGroups: N/A

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

[Gunnar Hjalmarsson]

I did some tests and identified a problem. If I use language-selector-
gnome to change from English (US) to Swedish, it looks like this:

$ sudo cat /var/lib/AccountsService/users/gunnar | grep Lang
Languages=sv:en_US:en;

Next:
* Relogin
* Open g-c-c from terminal and switch to Region & Language

Then you see this error message:

00:59:54.0364   **[11007]: WARNING: Couldn't get locale for 
language: sv:en_US:en
00:59:54.0366 GnomeDesktop[11007]:CRITICAL: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed

This can be dealt with in different ways, but for now I think it's
better to change 0010-set-language.patch so it does not write the colon
separated language list into the accountsservice keyfile. That way the
language selector in lightdm-gtk-greeter keeps working as well.

So I have uploaded a change, which also allowed me to drop language-not-
xpg.patch.

Not sure if the upstream project is at all useful for us. In any case I
kind of fear the it will cause more issues...

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2024560

Title:
  Check if 0010-set-language needs to be update for the new languages
  property

Status in accountsservice package in Ubuntu:
  Fix Committed

Bug description:
  Upstream did changes to add a languages properties

  
https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7

  I've rebased 0010-set-language to apply correctly but we should review
  if we need to adapt the patch to apply a similar logic to the new
  languages property that it's doing for old language one

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

[Gunnar Hjalmarsson]

@Sebastien: The new "Languages" property is described as an optional
one, but it still looks like language changes are now stored in the
"Languages" property instead of "Language".

The backend patches in accountsservice, g-c-c, etc. (which I'm guilty
of)

1. serve the purpose of keeping language-selector-gnome useful for both
Ubuntu and all the flavors (except for Kubuntu, which relies on KDE
stuff), and

2. make the language selection control in language-selector-gnome play
well with the equivalent in Region & Language.

I'll try to find out if GetLanguage and SetLanguage still works as
intended for us at this point.

If a UI control for maintaining "Languages" directly is added to g-c-c,
I imagine that we need to re-evaluate our approch more thoroghly. Do you
know if there is such a plan?

As regards disabling of that test, I wouldn't worry too much. Our code
does the right thing when a string like "fr_FR:en" is passed to
SetLanguage, and makes sure that only a valid locale name of a locale
which has actually been generated on the system is assigned to LANG via
~/.pam_environment.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2024560

Title:
  Check if 0010-set-language needs to be update for the new languages
  property

Status in accountsservice package in Ubuntu:
  New

Bug description:
  Upstream did changes to add a languages properties

  
https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7

  I've rebased 0010-set-language to apply correctly but we should review
  if we need to adapt the patch to apply a similar logic to the new
  languages property that it's doing for old language one

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

[Gunnar Hjalmarsson]

I'll comment on this in a bit. Busy with another thing ATM.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2024560

Title:
  Check if 0010-set-language needs to be update for the new languages
  property

Status in accountsservice package in Ubuntu:
  New

Bug description:
  Upstream did changes to add a languages properties

  
https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7

  I've rebased 0010-set-language to apply correctly but we should review
  if we need to adapt the patch to apply a similar logic to the new
  languages property that it's doing for old language one

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

@Sebastien: Sorry for confusing the installer with the ISO (which is
used for installing...).

My point was that at first login after a Chinese install, you have the
versions of firefox and core22 from April, and thus see the issue if you
open FF before having refreshed the snaps.

One concern of mine was that I feared that the FF default font would be
stuck somehow at the value when FF was first opened. ( Yes, I'm a snap
illiterate. :/ ) But I just tested, and saw that the FF default font
changed to the expected one once I had run "snap refresh".

So yes, the issue has been resolved.

** Changed in: snappy
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  Fix Released
Status in fontconfig package in Ubuntu:
  Invalid
Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

The installer is mentioned in the first sentence in the bug description.
:)

I was thinking that the installer still ships the old snap without the
fix. Then, if the user opens FF before refreshing the snaps, they would
still have the wrong default in FF.

Maybe I'm wrong. I haven't done any tests.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  Confirmed
Status in fontconfig package in Ubuntu:
  Invalid
Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

This seems to be fixed in Firefox latest/stable/ubuntu-23.04 114.0.1.

@Sebastien: But that doesn't fix the 23.04 installer, does it?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  Confirmed
Status in fontconfig package in Ubuntu:
  Invalid
Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Gunnar Hjalmarsson]

I made some changes to this bug report, such as replacing fontconfig
with plasma-desktop as the affected package. While I'm not sure about
that either, it's a way to call the Kubuntu developers' attention to the
issue.

** Package changed: fontconfig (Ubuntu) => plasma-desktop (Ubuntu)

** Changed in: plasma-desktop (Ubuntu)
   Status: Incomplete => New

** Summary changed:

- Font hinting broken on 23.04
+ Font hinting broken on Plasma 23.04

** Tags added: lunar regression-release

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017573

Title:
  Font hinting broken on Plasma 23.04

Status in plasma-desktop package in Ubuntu:
  New

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Gunnar Hjalmarsson]

Thanks again.

You mentioned "under Wayland". Does that mean that the issue is not
present if you log in to a Plasma (X11) session instead of a Plasma
(Wayland) one?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Gunnar Hjalmarsson]

On 2023-04-24 23:00, mrvanes wrote:
> It's written to ~/.config/fontconfig/fonts.conf

For me it's not. Wonder why.

> and it certainly is used.

Right, it should be, because that file path is not deprecated.

Thanks for clarifications.

Then, if I understand it correctly, the problem is specific to Plasma
somehow, i.e. the Plasma desktop does no longer honor the font
configuration. Is that a correct interpretation of the issue?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Gunnar Hjalmarsson]

I had a look in a Kubuntu 23.04 install I have in a VM, and it looks
like changes via the KDE UI for managing fonts alters the file
~/.fonts.conf. If that is the way you do it, can you please attach your
~/.fonts.conf file to this bug report.

The ~/.fonts-conf file has been considered deprecated for quite a while.
I wonder if they possibly have stopped to read that file now, which
would explain your observation.

Otherwise, if ~/.fonts.conf still is a valid place for fontconfig rules,
it might be a Plasma issue...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Gunnar Hjalmarsson]

Ok, thanks. You said "I use full hinting". Are you referring to some
custom font configuration?

I'm asking because I'm not aware of any general Ubuntu changes with
respect to hinting. And the file names of the Ubuntu and Ubuntu Mono
font files were changed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017573] Re: Font hinting broken on 23.04

[Gunnar Hjalmarsson]

Thanks for your report!

I recall a couple of fonts related changes and issues. Since you mention
the Ubuntu and Ubuntu Mono fonts, they were indeed upgraded.

But to start with it would be good if you could let us know the exact
context where you see that hinting has changed. Is it in connection with
rendering web pages, or is it about the font used in menus etc. on the
desktop?

Please clarify.

** Changed in: fontconfig (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017573

Title:
  Font hinting broken on 23.04

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting
  for all non-commercial fonts seems broken. I used to have decent if
  not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only
  fonts that still hint correctly are Microsoft's Verdana and Tahoma
  etc. Not sure whether the devide is exactly along this line, but it
  stands out.

  Tried regenerating font cache (fc-cache -rv) but that didn't help.

  Operating System: Kubuntu 23.04
  KDE Plasma Version: 5.27.4
  KDE Frameworks Version: 5.104.0
  Qt Version: 5.15.8
  Kernel Version: 6.3.0 (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 31.1 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics
  Manufacturer: Notebook
  Product Name: N141CU
  System Version: Not Applicable

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2003579] Re: Simulating Secondary mouse key fails

[Gunnar Hjalmarsson]

** Package changed: xkeyboard-config (Ubuntu) => gnome-shell (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/2003579

Title:
  Simulating Secondary mouse key fails

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I want to simulate the secondary mouse button via the keyboard.
  (By clicking the secondary mouse button, then normally a menu appears.)

  So, I opened the Accessibility menu and enabled the option "Mouse Keys".
  Additionally, I opened the sub-menu of "Click Assist" and enabled the option 
"Simulated Secondary Click".
  You can see these two configuration options enabled - in the attached image 
"MouseKeys_SecondaryClick.png".

  The following Ubuntu Help page explains it:
  https://help.ubuntu.com/stable/ubuntu-help/a11y-right-click.html.en

  
  The actual result:
  When continuously clicking the number "5" on the numpad of my keyboard, then 
it looks like the left mouse button is being clicked repeatedly.

  The expected result:
  Simulating a click of the right mouse button (for the current location of the 
mouse pointer).

  ---

  Probably this bug is related to either of the following packages:
  "gnome-control-center"
  or
  "xkb-data"

  ---

  Details about the system:

  Ubuntu 22.04.1 LTS

  gnome-control-center/jammy-updates,now 1:41.7-0ubuntu0.22.04.5

  xkb-data/jammy,jammy,now 2.33-1 all

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2003581] Re: Mouse keys fails to work after a restart

[Gunnar Hjalmarsson]

Thanks for additional info. Well, it was a guess..

Replacing xkeyboard-config with gnome-shell, since I think this is a
gnome-shell feature.

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

** Package changed: xkeyboard-config (Ubuntu) => gnome-shell (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/2003581

Title:
  Mouse keys fails to work after a restart

Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Regarding the "Mouse Keys" feature in Ubuntu:

  The "Mouse Keys" feature's purpose is to simulate the mouse by using the 
numpad of the keyboard.
  For example, a click on the left mouse button is simulated by clicking the 
number "5" on the numpad of the keyboard.

  This is explained in the following Ubuntu Help page:
  https://help.ubuntu.com/stable/ubuntu-help/mouse-mousekeys.html.en

  You can see that this feature is enabled in my system - in the
  attached picture "MouseKeys.png".

  I noticed that if that Mouse keys option is enabled, then after a
  restart - the feature fails to work, despite that the GUI shows that
  the feature is enabled.

  In order to make the feature to work after a restart, first I need to
  disable the Mouse Keys feature (the GUI shows that the feature is
  enabled) and then I need to enable it.

  ---

  Probably this bug is related to either of the following packages:
  "gnome-control-center"
  or
  "xkb-data"

  ---

  Details about the system:

  Ubuntu 22.04.1 LTS

  gnome-control-center/jammy-updates,now 1:41.7-0ubuntu0.22.04.5

  xkb-data/jammy,jammy,now 2.33-1 all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2003581/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2003581] Re: Mouse keys fails to work after a restart

[Gunnar Hjalmarsson]

This comment is a guess, and I may be completely wrong, but I wonder if
this happens in Ubuntu on Xorg only. If so, it may be related to the
fact that ibus wasn't always automatically enabled at the start of the
session.

That issue was fixed in 22.04 via bug #2007379. So, @nix, it would be
interesting to know if the issue is still present after you have
upgraded the im-config package to version 0.50-2ubuntu22.04.1.

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

** Changed in: im-config (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/2003581

Title:
  Mouse keys fails to work after a restart

Status in gnome-control-center package in Ubuntu:
  New
Status in im-config package in Ubuntu:
  Incomplete
Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  Regarding the "Mouse Keys" feature in Ubuntu:

  The "Mouse Keys" feature's purpose is to simulate the mouse by using the 
numpad of the keyboard.
  For example, a click on the left mouse button is simulated by clicking the 
number "5" on the numpad of the keyboard.

  This is explained in the following Ubuntu Help page:
  https://help.ubuntu.com/stable/ubuntu-help/mouse-mousekeys.html.en

  You can see that this feature is enabled in my system - in the
  attached picture "MouseKeys.png".

  I noticed that if that Mouse keys option is enabled, then after a
  restart - the feature fails to work, despite that the GUI shows that
  the feature is enabled.

  In order to make the feature to work after a restart, first I need to
  disable the Mouse Keys feature (the GUI shows that the feature is
  enabled) and then I need to enable it.

  ---

  Probably this bug is related to either of the following packages:
  "gnome-control-center"
  or
  "xkb-data"

  ---

  Details about the system:

  Ubuntu 22.04.1 LTS

  gnome-control-center/jammy-updates,now 1:41.7-0ubuntu0.22.04.5

  xkb-data/jammy,jammy,now 2.33-1 all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2003581/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

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

** Changed in: fontconfig (Ubuntu)
   Status: New => Invalid

** Changed in: language-selector (Ubuntu)
   Status: New => Invalid

** Changed in: snappy
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  Confirmed
Status in fontconfig package in Ubuntu:
  Invalid
Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

On 2023-04-21 21:18, Sebastien Bacher wrote:
> @Gunnar, that's because the only channel which has the core22
> firefox atm is stable/ubuntu-23.04 (which is specific to Lunar).

So, then I just learned that if you are on lunar aka 23.04 and install
firefox from the latest/stable channel, you get something different
compared to installing it from the latest/stable/ubuntu-23.04 channel.
Hmm.. I recall someone who talked earlier today about the need to be an
expert... ;)

> Your testing suggest that the issue was the one I mentioned earlier
> that https://github.com/ubuntu/gnome-sdk/pull/72 is missing from the
> core22 based gnome sdk

Right, by doing

snap refresh firefox --channel=latest/stable/ubuntu-23.04

(with the Chinese locale) I could finally reproduce the default font
issue. So that seems to be it for this bug.

This exercise raised a few other font related issues in my head, but
they are less urgent. Let's take those separately later.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  Confirmed
Status in fontconfig package in Ubuntu:
  Invalid
Status in language-selector package in Ubuntu:
  Invalid

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

This is confusing. If you install Ubuntu 23.04, you get FF from
latest/stable/23.04 together with core22.

Now I did a test where I removed FF, set the zh_CN.UTF-8 locale, and
installed FF again. Whichever channel I pick (tried latest/stable,
latest/beta and latest/edge) it pulls core20, and then it defaults to
Noto CJK fonts.

So I wasn't able to reproduce the issue with "AR PL UMing" as default
this way. I get the same result as Shengjing Zhu got when installing
from esr.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  New
Status in fontconfig package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

I had an IRC conversion with Sebastien Bacher and learned that things no
longer work as I thought they did. Unlike what I thought, the snaps do
no longer honor the font configuration of the host system, but live in
their own world in this respect.

https://github.com/ubuntu/gnome-sdk/issues/49#issuecomment-1216321729

So, what's determining the default font for a snap application is this
list:

https://github.com/ubuntu/gnome-sdk/pull/72/files

There is an apparent need to reconsider that list, but that's a separate
thing. Let's first try to understand how the specific issue reported in
this bug could happen.

The list includes the fonts-noto-cjk package, which also installs
70-fonts-noto-cjk.conf. The latter includes:



zh-cn


sans-serif


Noto Sans CJK SC



Well, fonts-arphic-uming is also included currently, and it installs
65-fonts-arphic-uming.conf which includes:


sans-serif

AR PL UMing CN
AR PL UMing HK
AR PL UMing TW



Note that this one is not language guarded, so it's effective
irrespective of locale.

But still, with the zh_CN.UTF-8 locale 70-fonts-noto-cjk.conf should
safely result in Noto Sans CJK SC being preferred over AR PL UMing CN.
To confirm that I installed the Chinese (Simplified) language in 23.04
and purged language-selector-common (which made gnome-control-center
being uninstalled...). And yes:

$ LC_CTYPE=zh_CN.UTF-8 fc-match
NotoSansCJK-Regular.ttc: "Noto Sans CJK SC" "Regular"

More playing with fc-match:

$ LC_CTYPE=zh_CN.UTF-8 fc-match -a | grep -iE 'cjk sc|uming cn' | head -3
NotoSansCJK-Regular.ttc: "Noto Sans CJK SC" "Regular"
NotoSansCJK-Bold.ttc: "Noto Sans CJK SC" "Bold"
uming.ttc: "AR PL UMing CN" "Light"
$ LC_CTYPE=en_US.UTF-8 fc-match -a | grep -iE 'cjk sc|uming cn' | head -3
uming.ttc: "AR PL UMing CN" "Light"
NotoSansCJK-Regular.ttc: "Noto Sans CJK SC" "Regular"
NotoSansCJK-Regular.ttc: "Noto Sans Mono CJK SC" "Regular"

So I now have a (vague) theory about what happens when you install
Ubuntu using the zh_CN.UTF-8 locale:

While it honors the locale when determining which packages get installed
(apparently, since fonts-arphic-uming is there), the locale is not
properly taken into account at the stage when the default Chinese
(Simplified) font of the snaps is determined.

** Bug watch added: github.com/ubuntu/gnome-sdk/issues #49
   https://github.com/ubuntu/gnome-sdk/issues/49

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  New
Status in fontconfig package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

Adding the language-selector package, since many fontconfig files
affecting Chinese rendering are provided by language-selector-common.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  New
Status in fontconfig package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly

[Gunnar Hjalmarsson]

One thought is to ask why we still install the fonts-arphic-uming
package when installing Chinese (Simplified as well as Traditional).
Probably it is of historical reasons from the time before Noto existed.
But let's consider that to be a matter of its own. Even if AR PL UMing
is available, Noto Sans CJK should have higher precedence.

With a Chinese locale, it's not possible to have fontconfig give Noto
Sans CJK higher precedence that it currently has:

$ LC_CTYPE=zh_CN.UTF-8 fc-match
NotoSansCJK-Regular.ttc: "Noto Sans CJK SC" "Regular"

But also with non-Chinese locales, Noto Sans CJK ought to be preferred
over AR PL UMing:

$ LC_CTYPE=en_US.UTF-8 fc-match -a | grep -iE 'uming|cjk' | head -38
NotoSansCJK-Regular.ttc: "Noto Sans CJK JP" "Regular"
NotoSansCJK-Medium.ttc: "Noto Sans CJK JP" "Medium"
NotoSansCJK-DemiLight.ttc: "Noto Sans CJK JP" "DemiLight"
NotoSansCJK-Light.ttc: "Noto Sans CJK JP" "Light"
NotoSansCJK-Thin.ttc: "Noto Sans CJK JP" "Thin"
NotoSansCJK-Bold.ttc: "Noto Sans CJK JP" "Bold"
NotoSansCJK-Black.ttc: "Noto Sans CJK JP" "Black"
NotoSansCJK-Regular.ttc: "Noto Sans CJK KR" "Regular"
NotoSansCJK-Medium.ttc: "Noto Sans CJK KR" "Medium"
NotoSansCJK-DemiLight.ttc: "Noto Sans CJK KR" "DemiLight"
NotoSansCJK-Light.ttc: "Noto Sans CJK KR" "Light"
NotoSansCJK-Thin.ttc: "Noto Sans CJK KR" "Thin"
NotoSansCJK-Bold.ttc: "Noto Sans CJK KR" "Bold"
NotoSansCJK-Black.ttc: "Noto Sans CJK KR" "Black"
NotoSansCJK-Regular.ttc: "Noto Sans CJK SC" "Regular"
NotoSansCJK-Medium.ttc: "Noto Sans CJK SC" "Medium"
NotoSansCJK-DemiLight.ttc: "Noto Sans CJK SC" "DemiLight"
NotoSansCJK-Light.ttc: "Noto Sans CJK SC" "Light"
NotoSansCJK-Thin.ttc: "Noto Sans CJK SC" "Thin"
NotoSansCJK-Bold.ttc: "Noto Sans CJK SC" "Bold"
NotoSansCJK-Black.ttc: "Noto Sans CJK SC" "Black"
NotoSansCJK-Regular.ttc: "Noto Sans CJK TC" "Regular"
NotoSansCJK-Medium.ttc: "Noto Sans CJK TC" "Medium"
NotoSansCJK-DemiLight.ttc: "Noto Sans CJK TC" "DemiLight"
NotoSansCJK-Light.ttc: "Noto Sans CJK TC" "Light"
NotoSansCJK-Thin.ttc: "Noto Sans CJK TC" "Thin"
NotoSansCJK-Bold.ttc: "Noto Sans CJK TC" "Bold"
NotoSansCJK-Black.ttc: "Noto Sans CJK TC" "Black"
NotoSansCJK-Regular.ttc: "Noto Sans CJK HK" "Regular"
NotoSansCJK-Medium.ttc: "Noto Sans CJK HK" "Medium"
NotoSansCJK-DemiLight.ttc: "Noto Sans CJK HK" "DemiLight"
NotoSansCJK-Light.ttc: "Noto Sans CJK HK" "Light"
NotoSansCJK-Thin.ttc: "Noto Sans CJK HK" "Thin"
NotoSansCJK-Bold.ttc: "Noto Sans CJK HK" "Bold"
NotoSansCJK-Black.ttc: "Noto Sans CJK HK" "Black"
uming.ttc: "AR PL UMing CN" "Light"
uming.ttc: "AR PL UMing HK" "Light"
uming.ttc: "AR PL UMing TW" "Light"

But apparently the snap applications don't query fontconfig dynamically
about the default font. Instead a default font seems to be established
during installation, based on to me unknown criteria, and that default
font does not change.

We need help from the snap folks to sort this out, I think.

Another thought is that many available fontconfig files were moved from
/etc/fonts/conf.avail to /usr/share/fontconfig/conf.avail during the
lunar development cycle. Can this possibly have created a dissonance
between the snaps and the system in this respect? If I understand it
correctly, the snaps honor the symlinks in /etc/fonts/conf.d:

$ cat ~/snap/firefox/current/.config/fontconfig/fonts.conf

  /snap/firefox/2517/gnome-platform/usr/share/fonts
  /usr/local/share//fonts
  /usr/share//fonts
  /etc/fonts/conf.d
  conf.d
  fontconfig
  /var/snap/firefox/common/fontconfig


But many of those symlinks on the system now point to /usr instead of
/etc.

One reason why I suspect that this has something to do with it is that
/etc/fonts/conf.avail/65-fonts-arphic-uming.conf — which prefers AR PL
UMing —is one of the files which was *not* moved to /usr.

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

** Changed in: fontconfig (Ubuntu)
   Status: Incomplete => New

** Also affects: snappy
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font in snap apps is ugly

Status in Snappy:
  New
Status in fontconfig package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  Installation

[Touch-packages] [Bug 2017076] Re: default Chinese font is ugly

[Gunnar Hjalmarsson]

@Shengjing Zhu: Can you confirm that it's only in snap applications you
see UMing instead of Noto? Btw, is it limited to Snap Store, or is the
FF snap affected as well?

Also: Is Noto used as expected
- when browsing web sites with Chinese contents
- in the desktop itself, e.g. Settings

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2017076

Title:
  default Chinese font is ugly

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  After installs Ubuntu 23.04 with Chinese language selected, the
  default font is chosen to AR PL UMing CN, which is very ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: fontconfig 2.14.1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 20 14:18:45 2023
  InstallationDate: Installed on 2023-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=zh_CN.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object

[Gunnar Hjalmarsson]

Since im_accounts_service_dispose() is mentioned in the bug title, can
this possibly have something to do with bug #2015610?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2015962

Title:
  indicator-messages-service crashed with SIGSEGV in
  g_type_check_instance() from g_signal_handlers_disconnect_matched()
  from act_user_manager_finalize() from g_object_unref() from
  im_accounts_service_dispose()

Status in accountsservice:
  Fix Released
Status in accountsservice package in Ubuntu:
  Incomplete
Status in indicator-messages package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
indicator-messages.  This problem was most recently seen with package version 
13.10.1+18.10.20180918-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 
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/accountsservice/+bug/2015962/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2016318] Re: free command: in Italian header is misaligned and wrongly translated

[Gunnar Hjalmarsson]

** Changed in: ubuntu-translations
   Importance: Undecided => Medium

** Changed in: ubuntu-translations
   Status: New => Confirmed

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Traduttori Italiani del software di Ubuntu 
(ubuntu-l10n-it)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/2016318

Title:
  free command: in Italian header is misaligned and wrongly translated

Status in Ubuntu Translations:
  Confirmed
Status in procps package in Ubuntu:
  New

Bug description:
  free command: in Italian header is misaligned and wrongly translated
  gratuiti is 'for free' or 'gratis' or 'toll free' 
  'free' may be translated with 'liberi'  

  total  = totali ... ok
  used   = usati  ... ok
  free   = liberi ... to be changed 
  shared = condivisi  ... ok
  buff/cache  ... ok 
  available = disponibili  ... ok

  corrado@corrado-n4-ll-beta:~$ free
 totalusedfree  shared  buff/cache   
available
  Mem:16151400 223667211599888  517412 3171440
13914728
  Swap:8388604   0 8388604
  corrado@corrado-n4-ll-beta:~$ 

  corradi@corrado-n4-ll-beta:~$ free
 buff/cache condivisi gratuiti totali utilizzati disponibili
  Mem:16151400 175200411850636  333144 3227540
14399396
  Swap:8388604   0 8388604
  corradi@corrado-n4-ll-beta:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: procps 2:4.0.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 14 18:34:49 2023
  InstallationDate: Installed on 2023-03-31 (14 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: procps
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2015619] Re: IBus Pinyin automatically backspaces selection

[Gunnar Hjalmarsson]

Thanks for your report.

ibus-pinyin is deprecated, and we recommend to use ibus-libpinyin
(Intelligent Pinyin) instead.

A problem with a specific IBus plugin is not an ibus bug per se, so
closing.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2015619

Title:
  IBus Pinyin automatically backspaces selection

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  When my input method is set to IBus Pinyin, any time I select a span
  of text with the cursor, with Shift + Arrow keys, or by giving a
  textbox focus, the selected text gets automatically removed.

  The deletion of the selection behaves as if the input method pressed
  the backspace key for me. I can undo the text removal by using Ctrl-Z.

  I did not observe the same problem on the Ubuntu default English (US)
  input, or with IBus WuBi Jidian 86 and IBus Mozc.

  I use IBus Pinyin 1.5.0, Ubuntu 20.04 LTS, Kernel 5.4.0-146-generic.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2012788] Re: Entering Unicode characters with code points broken

[Gunnar Hjalmarsson]

This is under control now. An upstream ibus commit fixes it (see
discussion at upstream issue).

Fix uploaded to Debian experimental.

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

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

** No longer affects: glib2.0 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2012788

Title:
  Entering Unicode characters with code points broken

Status in ibus:
  New
Status in ibus package in Ubuntu:
  In Progress

Bug description:
  On an updated lunar, following this instruction:

  https://help.ubuntu.com/stable/ubuntu-help/tips-
  specialchars.html#ctrlshiftu

  no longer works. If I press for instance

  Ctrl+Shift+U followed by 2014

  I see u2014 (underlined) on the screen. But it's not replaced with the
  expected character (in this case an Em Dash) when I confirm with Space
  or Enter — it just disappears.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2012788] Re: Entering Unicode characters with code points broken

[Gunnar Hjalmarsson]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2012788

Title:
  Entering Unicode characters with code points broken

Status in ibus:
  Unknown
Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  On an updated lunar, following this instruction:

  https://help.ubuntu.com/stable/ubuntu-help/tips-
  specialchars.html#ctrlshiftu

  no longer works. If I press for instance

  Ctrl+Shift+U followed by 2014

  I see u2014 (underlined) on the screen. But it's not replaced with the
  expected character (in this case an Em Dash) when I confirm with Space
  or Enter — it just disappears.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2012788] Re: Entering Unicode characters with code points broken

[Gunnar Hjalmarsson]

If I install ibus 1.5.28-2 from experimental on Debian, there is no code
point issue. While the source is identical with 1.5.28-2 on Ubuntu, the
binaries on Debian were built with older versions of some libraries.

I'm not sure that the problem lies in glib. It's simply my intuition. ;)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2012788

Title:
  Entering Unicode characters with code points broken

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  On an updated lunar, following this instruction:

  https://help.ubuntu.com/stable/ubuntu-help/tips-
  specialchars.html#ctrlshiftu

  no longer works. If I press for instance

  Ctrl+Shift+U followed by 2014

  I see u2014 (underlined) on the screen. But it's not replaced with the
  expected character (in this case an Em Dash) when I confirm with Space
  or Enter — it just disappears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2012788/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2012788] Re: Entering Unicode characters with code points broken

[Gunnar Hjalmarsson]

Yes, Heinrich, on the surface this seems to be an ibus issue. But I
think the root cause lies in some package which ibus is built with.

If I downgrade to the binaries built by ibus 1.5.28-1 on February 23,
using code points works fine. In 1.5.28-2 two upstream commits were
added as patches, but if I now build ibus with those patches disabled,
it doesn't help. A no-change rebuild does not help either.

Maybe glib is the culprit? ibus 1.5.28-1 was built with glib 2.74.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2012788

Title:
  Entering Unicode characters with code points broken

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  On an updated lunar, following this instruction:

  https://help.ubuntu.com/stable/ubuntu-help/tips-
  specialchars.html#ctrlshiftu

  no longer works. If I press for instance

  Ctrl+Shift+U followed by 2014

  I see u2014 (underlined) on the screen. But it's not replaced with the
  expected character (in this case an Em Dash) when I confirm with Space
  or Enter — it just disappears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2012788/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2012552] Re: /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now

[Gunnar Hjalmarsson]

Now I have tested too. :/ Switching language does not result in an
attempt to reset region, and seems to work as expected. I can no longer
reproduce any errors or warnings when starting g-c-c from terminal.

** Changed in: accountsservice (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2012552

Title:
  /usr/libexec/accounts-
  
daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now

Status in accountsservice package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
accountsservice.  This problem was most recently seen with package version 
22.08.8-1ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/8aec6774e070650ea5d4ded3cd3d4c0ebdbf9335 
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/accountsservice/+bug/2012552/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2012552] Re: /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now

[Gunnar Hjalmarsson]

I think I found it:

https://salsa.debian.org/gnome-team/gnome-control-
center/-/commit/5400a142

Uploaded g-c-c, but keeping the accountsservice task open for now until
we see that the problem is no longer present.

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2012552

Title:
  /usr/libexec/accounts-
  
daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now

Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
accountsservice.  This problem was most recently seen with package version 
22.08.8-1ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/8aec6774e070650ea5d4ded3cd3d4c0ebdbf9335 
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/accountsservice/+bug/2012552/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2012552] Re: /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now

[Gunnar Hjalmarsson]

The latter comment reminds me of bug #2011313, where the underlying
issue was a failure (for some reason) to fetch user data. One side
effect in that case was that it resulted in a language variable having a
NULL value, and then it failed when trying to convert it to a valid
locale name.

Anyway, the wording "is not a valid locale name" comes probably from the
user_locale_validate() function in accountsservice (0010-set-
language.patch).

And "Couldn't set FormatsLocale" comes from the set_formats_locale()
function in g-c-c (Adapts-the-region-capplet-and-the-language-chooser-
in-the.patch).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/2012552

Title:
  /usr/libexec/accounts-
  
daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now

Status in accountsservice package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
accountsservice.  This problem was most recently seen with package version 
22.08.8-1ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/8aec6774e070650ea5d4ded3cd3d4c0ebdbf9335 
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/accountsservice/+bug/2012552/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive

[Gunnar Hjalmarsson]

And thanks for reporting it to ibus upstream too. :)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2012146

Title:
  very high cpu usage, system unresponsive

Status in ibus:
  Unknown
Status in ardour package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in ardour package in Debian:
  Unknown

Bug description:
  may be related to Ardour 7.3, when I start ardour and start working
  with the app, the system slows down and htop shows 100% cpu usage for
  ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ibus 1.5.28-2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 18 15:21:55 2023
  InstallationDate: Installed on 2022-05-13 (308 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive

[Gunnar Hjalmarsson]

@enorrmann: The latter is valuable info. I submitted an ardour Debian
bug, which you should have received a copy of. Please feel free to add
relevant info to that bug, if you think that I missed something.

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

** Bug watch added: Debian Bug tracker #1033293
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033293

** Also affects: ardour (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033293
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2012146

Title:
  very high cpu usage, system unresponsive

Status in ardour package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New
Status in ardour package in Debian:
  Unknown

Bug description:
  may be related to Ardour 7.3, when I start ardour and start working
  with the app, the system slows down and htop shows 100% cpu usage for
  ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ibus 1.5.28-2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 18 15:21:55 2023
  InstallationDate: Installed on 2022-05-13 (308 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive

[Gunnar Hjalmarsson]

Thanks for clarifying. It means that we can't tell whether the issue is
related to the specific changes in ibus 1.5.28-2, or if it is a general
ibus 1.5.28 problem (or an ardour 7.3 problem...).

In any case my plea to also report it to ibus upstream still stands.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2012146

Title:
  very high cpu usage, system unresponsive

Status in ibus package in Ubuntu:
  New

Bug description:
  may be related to Ardour 7.3, when I start ardour and start working
  with the app, the system slows down and htop shows 100% cpu usage for
  ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ibus 1.5.28-2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 18 15:21:55 2023
  InstallationDate: Installed on 2022-05-13 (308 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive

[Gunnar Hjalmarsson]

Ok.. But when exactly did you do that? If it was very recently, you may
have upgraded ibus from 1.5.27-2 directly to 1.5.28-2.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2012146

Title:
  very high cpu usage, system unresponsive

Status in ibus package in Ubuntu:
  New

Bug description:
  may be related to Ardour 7.3, when I start ardour and start working
  with the app, the system slows down and htop shows 100% cpu usage for
  ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ibus 1.5.28-2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 18 15:21:55 2023
  InstallationDate: Installed on 2022-05-13 (308 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2012146] Re: very high cpu usage, system unresponsive

[Gunnar Hjalmarsson]

Thanks for your report!

I see that you installed your system last year. Can you possibly tell if
it's a regression from ibus 1.5.28-1, i.e. did it work smoothly with
that version and the issue started with ibus 1.5.28-2?

I'm asking because 1.5.28-2 includes two patches which are not yet in
the upstream git repo, but only in the repo of the upstream maintainer.
Those patches are supposed to fix bug #2009700.

Whatever the answer to that question is, I would ask you to report this
issue also to the upstream issue tracker:

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

If you do, please post the URL to the issue in a comment here. And, btw,
please state in the upstream issue that ibus 1.5.28-2 in Ubuntu includes
the patches I mentioned.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2012146

Title:
  very high cpu usage, system unresponsive

Status in ibus package in Ubuntu:
  New

Bug description:
  may be related to Ardour 7.3, when I start ardour and start working
  with the app, the system slows down and htop shows 100% cpu usage for
  ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ibus 1.5.28-2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 18 15:21:55 2023
  InstallationDate: Installed on 2022-05-13 (308 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to lunar on 2023-03-17 (1 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2011656] Re: ibus-x11 crashed with SIGSEGV in _int_malloc()

[Gunnar Hjalmarsson]

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2011656/+attachment/5654564/+files/CoreDump.gz

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2011656

Title:
  ibus-x11 crashed with SIGSEGV in _int_malloc()

Status in ibus package in Ubuntu:
  New

Bug description:
  editing python code with idle, doing a select with shift-arrow in prep
  to a cut operation

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: ibus 1.5.28-1
  ProcVersionSignature: Ubuntu 5.19.0-1012.19-raspi 5.19.17
  Uname: Linux 5.19.0-1012-raspi aarch64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 14 23:41:55 2023
  ExecutablePath: /usr/libexec/ibus-x11
  ImageMediaBuild: 20221018.1
  JournalErrors: -- No entries --
  ProcCmdline: /usr/libexec/ibus-x11
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   _int_malloc (av=av@entry=0x892f0b00 , bytes=bytes@entry=48) 
at ./malloc/malloc.c:3923
   __GI___libc_malloc (bytes=48) at ./malloc/malloc.c:3305
   g_malloc () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
   g_source_new () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
   g_timeout_source_new () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
  Title: ibus-x11 crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to lunar on 2023-01-31 (42 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004241] Re: Update to glib >= 2.75.1

[Gunnar Hjalmarsson]

@Daniel: It's already in -proposed. And there are more packages which
depend on glib >=2.75.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004241

Title:
  Update to glib >= 2.75.1

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Update to glib >= 2.75.1 because that's what mutter 44 now requires.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2007785] Re: Livepatch tab missing PT(-BR) translation after language pack 1:22.04+20230209 update

[Gunnar Hjalmarsson]

Correction:

So you are now talking about update-manager... That string was changed a
bit, and the changed string has not yet been translated to Brazilian
Portuguese. It's as simple as that.

https://translations.launchpad.net/ubuntu/lunar/+source/update-
manager/+pots/update-manager/pt_BR?search=Ubuntu+Pro

** No longer affects: software-properties (Ubuntu)

** Summary changed:

- Livepatch tab missing PT(-BR) translation after language pack 
1:22.04+20230209 update
+ Changed string in ubuntu-manager needs pt-br translation

** Changed in: ubuntu-translations
   Status: Invalid => Triaged

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Ubuntu Brazilian Portuguese Translators 
(ubuntu-l10n-pt-br)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2007785

Title:
  Changed string in ubuntu-manager needs pt-br translation

Status in Ubuntu Translations:
  Triaged

Bug description:
  1:22.04+20230209

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2007785] Re: Livepatch tab missing PT(-BR) translation after language pack 1:22.04+20230209 update

[Gunnar Hjalmarsson]

That one beats me. Adding a software-properties bug task, so the
maintainer can determine the cause of that lack of translation. (I don't
find the string in the POT file.)

** Also affects: software-properties (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2007785

Title:
  Livepatch tab missing PT(-BR) translation after language pack
  1:22.04+20230209 update

Status in Ubuntu Translations:
  Invalid
Status in software-properties package in Ubuntu:
  New

Bug description:
  1:22.04+20230209

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

[Gunnar Hjalmarsson]

Added the block-proposed tag to bug #2004241 instead.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2008279

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
  IBus is turned on

Status in glib2.0 package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  Test Case
  -
  From Ubuntu 23.04, install glib >= 2.75.3-3

  Test 1:
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  Test 2:
  Install the ibus-libpinyin package.
  Log out and log in again.
  Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)"
   to your input sources.
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu (on Wayland).
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  What Happens
  
  No text is inputted

  Other Info
  --
  You see the issue as soon as IBus has been 'turned on'. With the current 
g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 
session IBus is always turned on due to im-config 0.55-1. In a Wayland session 
you need to tell it to turn IBus on by either adding an IBus input method to 
your input sources or make use of the Screen Keyboard feature.

  And I've only seen the issue with the Firefox and Chromium snaps.

  Warning message if you start firefox from terminal:

  [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could
  not connect: Permission denied: 'glib warning', file
  /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167

  (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to
  ibus: Could not connect: Permission denied

  gnome-settings-daemon
  -
  gnome-settings-daemon 44 Beta makes the situation worse since it always turns 
IBus on in both Wayland and X11, but I reverted 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that 
we could continue with the update. See 
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004241] Re: Update to glib >= 2.75.1

[Gunnar Hjalmarsson]

While the issue in bug #2008279 will be fixed via a snapd change, it was
caused by a glib change. We don't want glib2.0 >=2.75 to migrate before
snapd 2.58.3+23.04ubuntu1 has made it to lunar-release and has been
confirmed to fix the issue.

** Tags added: block-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004241

Title:
  Update to glib >= 2.75.1

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Update to glib >= 2.75.1 because that's what mutter 44 now requires.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

[Gunnar Hjalmarsson]

Removing block-proposed again after a short IRC talk with Sebastien. We
don't want to prevent snapd from migrating.

** Tags removed: block-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2008279

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
  IBus is turned on

Status in glib2.0 package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  Test Case
  -
  From Ubuntu 23.04, install glib >= 2.75.3-3

  Test 1:
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  Test 2:
  Install the ibus-libpinyin package.
  Log out and log in again.
  Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)"
   to your input sources.
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu (on Wayland).
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  What Happens
  
  No text is inputted

  Other Info
  --
  You see the issue as soon as IBus has been 'turned on'. With the current 
g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 
session IBus is always turned on due to im-config 0.55-1. In a Wayland session 
you need to tell it to turn IBus on by either adding an IBus input method to 
your input sources or make use of the Screen Keyboard feature.

  And I've only seen the issue with the Firefox and Chromium snaps.

  Warning message if you start firefox from terminal:

  [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could
  not connect: Permission denied: 'glib warning', file
  /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167

  (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to
  ibus: Could not connect: Permission denied

  gnome-settings-daemon
  -
  gnome-settings-daemon 44 Beta makes the situation worse since it always turns 
IBus on in both Wayland and X11, but I reverted 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that 
we could continue with the update. See 
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

[Gunnar Hjalmarsson]

Great, Seb. Guess we'd better remove the block-proposed tag then.

** Tags removed: block-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2008279

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
  IBus is turned on

Status in glib2.0 package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  Test Case
  -
  From Ubuntu 23.04, install glib >= 2.75.3-3

  Test 1:
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  Test 2:
  Install the ibus-libpinyin package.
  Log out and log in again.
  Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)"
   to your input sources.
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu (on Wayland).
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  What Happens
  
  No text is inputted

  Other Info
  --
  You see the issue as soon as IBus has been 'turned on'. With the current 
g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 
session IBus is always turned on due to im-config 0.55-1. In a Wayland session 
you need to tell it to turn IBus on by either adding an IBus input method to 
your input sources or make use of the Screen Keyboard feature.

  And I've only seen the issue with the Firefox and Chromium snaps.

  Warning message if you start firefox from terminal:

  [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could
  not connect: Permission denied: 'glib warning', file
  /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167

  (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to
  ibus: Could not connect: Permission denied

  gnome-settings-daemon
  -
  gnome-settings-daemon 44 Beta makes the situation worse since it always turns 
IBus on in both Wayland and X11, but I reverted 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that 
we could continue with the update. See 
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp