[Desktop-packages] [Bug 2051188] Re: Firefox 122 update breaks webextensions permission

[Paul Rouget]

Thanks for the quick fix! It's all working now.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2051188

Title:
  Firefox 122 update breaks webextensions permission

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  We build webextensions for Firefox.

  Since the latest update to Firefox 122, the native webextension bridge
  stopped working.

  ```
  $ flatpak permission-show snap.firefox
  Table ObjectApp  
Permissions   Data
  desktop-used-apps application/vnd.debian.binary-package snap.firefox 
gnome-software-local-file,1,3 0x00
  webextensions net.downloadhelper.coapp  snap.firefox yes  
 0x00
  ```

  This used to work and be enough, but not anymore.

  In the logs I see:

  
  ```
  Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”
  Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop 
firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”: 'glib warning', file 
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187
  ```

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


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

[Desktop-packages] [Bug 2039045] Re: GNOME Shell locking hard when Telegram opens a full-screen photo

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2039045

Title:
  GNOME Shell locking hard when Telegram opens a full-screen photo

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Steps:
  - run https://snapcraft.io/telegram-desktop
  - open a full-screen image preview

  Expected:
  - the image preview opens
  - and can be closed

  Current:
  - the image preview opens
  - the shell becomes unresponsive

  Often it's possible to wait a few seconds to close the preview again,
  but sometimes it just locks up hard with no way to recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 14:30:31 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-10-06 (5 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=screen-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2012430] Re: attribute breaks dashes

[Kevin Wilke]

This bug must have been introduced between Ubuntu 18.04 and 18.10.

It doesn't happen with Ubuntu 18.04 which shipped with Firefox 59. It
first appeared in Ubuntu 18.10 which comes with Firefox 63.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2012430

Title:
   attribute breaks dashes

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  The attached HTML file should be rendered as two lines of text, one
  with dashes between the words and one with spaces. However, Firefox
  renders the file with no dashes whatsoever. Instead of dashes, it
  shows double-width spaces.

  The HTML renders correctly if lang="de-x-formal" attribute is changed
  to lang="de". Please note that de-x-formal is a valid language code,
  as verified with http://schneegans.de/lv/ and it is found in the HTML
  generated by MediaWiki when the language is set to de-formal.

  I also noticed that the extra wide spaces Firefox incorrectly shows
  instead of dashes are in the ori1Uni font while the regular letters
  are in DejaVu Serif. With lang="de", everything is in DejaVu Serif,
  including dashes which render correctly.

  This problem does not occur with Chromium on Ubuntu, nor with Firefox
  on Debian, nor Firefox on Windows.

  Ubuntu version: Ubuntu 22.04.2 LTS
  Firefox version: firefox 111.0-2 from snap

  Thank you very much for looking into this.

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


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

[Desktop-packages] [Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble

[Erich Eickmeyer]

This happened during a test upgrade from Ubuntu Studio 22.04 -> 24.04,
but instead of Firefox, it tried to pull-in chromium??? We don't even
seed chromium in any way.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2043820

Title:
  Unable to contact snap store on Xubuntu from Jammy to Noble

Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade
  fails consistently at the `Installing the firefox snap` step.

  This was first detected on Jenkins [1], then reproduced locally with
  `auto-upgrade-testing`, then finally by manually running a `do-
  release-upgrade -d` in a VM.

  [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade-
  list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull
  (Jenkins full log attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.17
  ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Fri Nov 17 18:24:22 2023
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: snapd (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2043820

Title:
  Unable to contact snap store on Xubuntu from Jammy to Noble

Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade
  fails consistently at the `Installing the firefox snap` step.

  This was first detected on Jenkins [1], then reproduced locally with
  `auto-upgrade-testing`, then finally by manually running a `do-
  release-upgrade -d` in a VM.

  [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade-
  list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull
  (Jenkins full log attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.17
  ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Fri Nov 17 18:24:22 2023
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04

[Erich Eickmeyer]

Tested in a VM and could not duplicate the issue using a fully upgraded
22.04 install and using `do-release-upgrade -d` from the terminal to
upgrade to Noble Numbat (future 24.04) in order to see the terminal
output.

The only issue I noticed is that it tried to pull-in chromium from the
snap store (??), but that would be an issue related to ubuntu-release-
upgrader and is a known issue there. The issue described in this bug
report did not occur.

Looking at Kubuntu's analogous fix (https://git.launchpad.net/~kubuntu-
packagers/kubuntu-packaging/+git/kubuntu-
settings/commit/?h=kubuntu_lunar_archive=ea776d7a69057b6c30ae8bceaa21393eec47cbad)
which was done at around the same time   as
https://git.launchpad.net/ubuntustudio-default-
settings/commit/?id=4bdc9d5b9ac18cf0aa5035646e4b4016faa62d3d, in fact,
within a couple weeks of each other, they are nearly identical.

With that in mind, and the fact that neither fix currently warrants a
"Conflicts:" line which would cause even more problems as we would
*never* want to conflict with fontconfig, I'm more than willing to bet
the original poster in askubuntu.com didn't have a fully-updated system
prior to attempting an upgrade.

With that in mind, I will have to re-close this as invalid as the fix
was already done prior to 23.04's release and this isn't even a bug.
Thanks for the report, though!

** Changed in: ubuntustudio-default-settings (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2051313

Title:
  font-config confilcts ubuntustudio-default-settings upgrading from
  22.04 to 24.04

Status in fontconfig package in Ubuntu:
  Invalid
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid

Bug description:
  This bug was migrated from https://askubuntu.com/q/1501240/1004020 .

  A nearly identical bug is
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It
  fixed things for `kubuntu-settings-desktop` but not `ubuntustudio-
  default-settings`. Please add an analogous fix.

  A similar but potentially unrelated bug is
  https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-
  settings/+bug/2037471 .

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Not my computer.

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Not my computer.

  3) What you expected to happen

  The AskUbuntu user's upgrade from 22.04 to 24.04 to complete
  successfully.

  4) What happened instead

  The upgrade failed and they posted to AskUbuntu.

  # Copy of their question body

  After an upgrade to 
  ```
  Distributor ID: Ubuntu
  Description:Ubuntu Noble Numbat (development branch)
  Release: 24.04
  Codename:noble 

  ```
  apt won't update bcs of unmet dependencies.

  ``` 
  The following packages have unmet dependencies:
   libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1)
   libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1)
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution). 
  ```
  I've tried: 

  ``` 
  apt --fix-broken install

  ```
  ```
  dpkg: error processing archive 
/var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack):
   trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also 
in package ubuntustudio-default-settings 22.04.26.3
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Errors were encountered while processing:
   /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```

  # Copy of workaround in my answer body

  The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel-
  rgb.conf` out of `ubuntustudio-default-settings`
  ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default-
  settings/filelist),
  [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default-
  settings/filelist)) and into [`fontconfig-
  config`](https://packages.ubuntu.com/noble/all/fontconfig-
  config/filelist). The `ubuntustudio-default-settings` package needs to
  be updated first but the maintainers forgot to add an automatic
  `Conflicts:` line.

  You can retry installing the package in the correct order by running
  `sudo apt install --upgrade ubuntustudio-default-settings`. If that
  does not work, you need to forcibly reinstall things in the correct
  order:

  ```bash
  sudo -i

  

[Desktop-packages] [Bug 2051188] Re: Firefox 122 update breaks webextensions permission

[Amin Bandali]

Hi again Paul, (all,)

A new build of Firefox snap with version string "122.0-2.1" is now
available on the 'stable' channel which includes fixed support for
native messaging for Ubuntu 22.04 users.  My apologies for any
inconvenience this issue may have caused.

I've posted a quick post-mortem write up on the Ubuntu Discourse for
folks who may be interested in reading what exactly happened:

https://discourse.ubuntu.com/t/firefox-122-snap-temporary-native-
messaging-breakage-for-ubuntu-22-04-users-fixed-since/41940

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2051188

Title:
  Firefox 122 update breaks webextensions permission

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  We build webextensions for Firefox.

  Since the latest update to Firefox 122, the native webextension bridge
  stopped working.

  ```
  $ flatpak permission-show snap.firefox
  Table ObjectApp  
Permissions   Data
  desktop-used-apps application/vnd.debian.binary-package snap.firefox 
gnome-software-local-file,1,3 0x00
  webextensions net.downloadhelper.coapp  snap.firefox yes  
 0x00
  ```

  This used to work and be enough, but not anymore.

  In the logs I see:

  
  ```
  Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”
  Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop 
firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”: 'glib warning', file 
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187
  ```

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


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

[Desktop-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04

[Erich Eickmeyer]

Ok, upon further inspection, I'm switching this back to "new" simply
because it has not been "confirmed" by more than one person. The
original reporter is not the person filing the bug, which means this
needs to be "confirmed" by someone other than the reporter.

Furthermore, LP: #2005124 doesn't apply here as it was a completely
separate issue.

The reason I was a little hesitant is because it looked like, mostly
based on the askubuntu question, the person was legitimately asking for
support not filing a bug report. Launchpad is for bug reports, not
support questions, unless it's on the support tracker. This part
(bugs.launchpad.net) is the bug tracker.

Either way, I apologize for my earlier response as I shouldn't be
punishing people for pointing out problems where they might exist. I'm
testing right now.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2051313

Title:
  font-config confilcts ubuntustudio-default-settings upgrading from
  22.04 to 24.04

Status in fontconfig package in Ubuntu:
  Invalid
Status in ubuntustudio-default-settings package in Ubuntu:
  New

Bug description:
  This bug was migrated from https://askubuntu.com/q/1501240/1004020 .

  A nearly identical bug is
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It
  fixed things for `kubuntu-settings-desktop` but not `ubuntustudio-
  default-settings`. Please add an analogous fix.

  A similar but potentially unrelated bug is
  https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-
  settings/+bug/2037471 .

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Not my computer.

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Not my computer.

  3) What you expected to happen

  The AskUbuntu user's upgrade from 22.04 to 24.04 to complete
  successfully.

  4) What happened instead

  The upgrade failed and they posted to AskUbuntu.

  # Copy of their question body

  After an upgrade to 
  ```
  Distributor ID: Ubuntu
  Description:Ubuntu Noble Numbat (development branch)
  Release: 24.04
  Codename:noble 

  ```
  apt won't update bcs of unmet dependencies.

  ``` 
  The following packages have unmet dependencies:
   libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1)
   libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1)
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution). 
  ```
  I've tried: 

  ``` 
  apt --fix-broken install

  ```
  ```
  dpkg: error processing archive 
/var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack):
   trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also 
in package ubuntustudio-default-settings 22.04.26.3
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Errors were encountered while processing:
   /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```

  # Copy of workaround in my answer body

  The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel-
  rgb.conf` out of `ubuntustudio-default-settings`
  ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default-
  settings/filelist),
  [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default-
  settings/filelist)) and into [`fontconfig-
  config`](https://packages.ubuntu.com/noble/all/fontconfig-
  config/filelist). The `ubuntustudio-default-settings` package needs to
  be updated first but the maintainers forgot to add an automatic
  `Conflicts:` line.

  You can retry installing the package in the correct order by running
  `sudo apt install --upgrade ubuntustudio-default-settings`. If that
  does not work, you need to forcibly reinstall things in the correct
  order:

  ```bash
  sudo -i

  apt update
  apt download ubuntustudio-default-settings
  apt download fontconfig-config

  # Temporarily force-uninstall only ubuntustudio-default-settings
  # so that we DON'T uninstall ubuntustudio-desktop
  dpkg --force-all -r ubuntustudio-default-settings
  dpkg --force-all -i ./fontconfig-config_*
  dpkg --force-all -i ./ubuntustudio-default-settings_*

  dpkg --configure -a
  apt --fix-broken install
  apt upgrade
  apt dist-upgrade
  ```

  # Analysis

  Please apply an analogous fix. Where I mentioned `Conflicts:` on
  AskUbuntu, a `Pre-Depends:` may be necessary instead as I read
  somewhere on Launchpad.

To 

[Desktop-packages] [Bug 2051371] Re: Backspace in gnome-terminal often deletes cluster

[Egmont Koblinger]

Maybe the bug you _really_ wanted to report is that gnome-terminal
doesn't use the "surrounding text" feature of input methods?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2051371

Title:
  Backspace in gnome-terminal often deletes cluster

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  If I have ខែ្ (U+1781 U+17c2 U+17d2) in the terminal and press
  backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left
  with ខ (U+1781). Instead it should only delete the last codepoint,
  U+17d2.

  If I have ខែ (U+1781 U+17c2) a backspace deletes only U+17c2,
  similarly if I have ខ្ (U+1781 U+17d2) where the backspace deletes
  U+17d2.

  Further investigations show that backspace often deletes the entire
  cluster, i.e. diacritic(s) plus the base character, for example with
  x̣́ (U+0078 U+0301 U+0323) where a backspace deletes all three
  codepoints.

  gnome-terminal should only delete the last codepoint [1].

  A real live example where this behavior is problematic is when using
  ibus-keyman with the Khmer Angkor keyboard [2]. When typing xEjmr the
  expected output is ខ្មែរ (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman
  does some reordering while typing to put the codepoints in a
  standardized order. Because gnome-terminal lacks support for
  surrounding text, the codepoints have to be deleted by emitting
  several backspace keypresses. Because of the deletion of the cluster
  the result in gnome-terminal is ្មែរ (U+17d2 U+1798 U+17c2 U+179a).

  [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-deletion
  [2] https://github.com/keymanapp/keyman/issues/10481

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-terminal 3.44.0-1ubuntu1 [modified: 
usr/libexec/gnome-terminal-server]
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 12:21:42 2024
  InstallationDate: Installed on 2022-04-12 (653 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2051371] Re: Backspace in gnome-terminal often deletes cluster

[Egmont Koblinger]

By the way... absolutely independently from terminals...

U+17d2 is a combining accent. When I checked (many years ago), major
graphical toolkits (e.g. GTK and QT) disagreed whether the backspace
keypress should delete only the combining accent, or the entire glyph
(base character + combining accents) at once. GTK did one, QT did the
other (I can't recall which one did which).

I don't know if the world has changed since and has settled with one of
these behaviors, having found out that one of these behaviors is clearly
superior to the other. I would _guess_ that not much has changed. That
is, both possible behaviors are reasonable, both have their pros and
cons, and probably you cannot claim that the behavior _must_ be the one
you're looking for.

If your input method cannot generate the symbols you need, and you need
to press backspace as a workaround to get that, moreover, you need to
rely on one particular behavior of backspace, then I'd argue that it's
all the fault of your input method, it should be able to produce
straight away whatever you wish to end up with.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2051371

Title:
  Backspace in gnome-terminal often deletes cluster

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  If I have ខែ្ (U+1781 U+17c2 U+17d2) in the terminal and press
  backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left
  with ខ (U+1781). Instead it should only delete the last codepoint,
  U+17d2.

  If I have ខែ (U+1781 U+17c2) a backspace deletes only U+17c2,
  similarly if I have ខ្ (U+1781 U+17d2) where the backspace deletes
  U+17d2.

  Further investigations show that backspace often deletes the entire
  cluster, i.e. diacritic(s) plus the base character, for example with
  x̣́ (U+0078 U+0301 U+0323) where a backspace deletes all three
  codepoints.

  gnome-terminal should only delete the last codepoint [1].

  A real live example where this behavior is problematic is when using
  ibus-keyman with the Khmer Angkor keyboard [2]. When typing xEjmr the
  expected output is ខ្មែរ (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman
  does some reordering while typing to put the codepoints in a
  standardized order. Because gnome-terminal lacks support for
  surrounding text, the codepoints have to be deleted by emitting
  several backspace keypresses. Because of the deletion of the cluster
  the result in gnome-terminal is ្មែរ (U+17d2 U+1798 U+17c2 U+179a).

  [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-deletion
  [2] https://github.com/keymanapp/keyman/issues/10481

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-terminal 3.44.0-1ubuntu1 [modified: 
usr/libexec/gnome-terminal-server]
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 12:21:42 2024
  InstallationDate: Installed on 2022-04-12 (653 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04

[Erich Eickmeyer]

** Changed in: ubuntustudio-default-settings (Ubuntu)
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2051313

Title:
  font-config confilcts ubuntustudio-default-settings upgrading from
  22.04 to 24.04

Status in fontconfig package in Ubuntu:
  Invalid
Status in ubuntustudio-default-settings package in Ubuntu:
  New

Bug description:
  This bug was migrated from https://askubuntu.com/q/1501240/1004020 .

  A nearly identical bug is
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It
  fixed things for `kubuntu-settings-desktop` but not `ubuntustudio-
  default-settings`. Please add an analogous fix.

  A similar but potentially unrelated bug is
  https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-
  settings/+bug/2037471 .

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Not my computer.

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Not my computer.

  3) What you expected to happen

  The AskUbuntu user's upgrade from 22.04 to 24.04 to complete
  successfully.

  4) What happened instead

  The upgrade failed and they posted to AskUbuntu.

  # Copy of their question body

  After an upgrade to 
  ```
  Distributor ID: Ubuntu
  Description:Ubuntu Noble Numbat (development branch)
  Release: 24.04
  Codename:noble 

  ```
  apt won't update bcs of unmet dependencies.

  ``` 
  The following packages have unmet dependencies:
   libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1)
   libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1)
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution). 
  ```
  I've tried: 

  ``` 
  apt --fix-broken install

  ```
  ```
  dpkg: error processing archive 
/var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack):
   trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also 
in package ubuntustudio-default-settings 22.04.26.3
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Errors were encountered while processing:
   /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```

  # Copy of workaround in my answer body

  The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel-
  rgb.conf` out of `ubuntustudio-default-settings`
  ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default-
  settings/filelist),
  [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default-
  settings/filelist)) and into [`fontconfig-
  config`](https://packages.ubuntu.com/noble/all/fontconfig-
  config/filelist). The `ubuntustudio-default-settings` package needs to
  be updated first but the maintainers forgot to add an automatic
  `Conflicts:` line.

  You can retry installing the package in the correct order by running
  `sudo apt install --upgrade ubuntustudio-default-settings`. If that
  does not work, you need to forcibly reinstall things in the correct
  order:

  ```bash
  sudo -i

  apt update
  apt download ubuntustudio-default-settings
  apt download fontconfig-config

  # Temporarily force-uninstall only ubuntustudio-default-settings
  # so that we DON'T uninstall ubuntustudio-desktop
  dpkg --force-all -r ubuntustudio-default-settings
  dpkg --force-all -i ./fontconfig-config_*
  dpkg --force-all -i ./ubuntustudio-default-settings_*

  dpkg --configure -a
  apt --fix-broken install
  apt upgrade
  apt dist-upgrade
  ```

  # Analysis

  Please apply an analogous fix. Where I mentioned `Conflicts:` on
  AskUbuntu, a `Pre-Depends:` may be necessary instead as I read
  somewhere on Launchpad.

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


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

[Desktop-packages] [Bug 2051383] [NEW] gnome-shell high CPU utilization when moving mouse cursor

[Sergey Zolotarev]

Public bug reported:

When I simply move my mouse cursor on an empty desktop, gnome-shell's
CPU usage goes up from 20% (when idle) to 60%, which causes stuttering.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 26 23:31:26 2024
DisplayManager: gdm3
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-03-17 (2140 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 42.9-0ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2051383

Title:
  gnome-shell high CPU utilization when moving mouse cursor

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I simply move my mouse cursor on an empty desktop, gnome-shell's
  CPU usage goes up from 20% (when idle) to 60%, which causes
  stuttering.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 23:31:26 2024
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-03-17 (2140 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-06-02 (603 days ago)

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


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

[Desktop-packages] [Bug 2051363] Re: Cannot perform certificate auto-enroll without NDES installed

[Launchpad Bug Tracker]

This bug was fixed in the package adsys - 0.13.3

---
adsys (0.13.3) noble; urgency=medium

  * Fix cert auto-enroll without NDES (LP: #2051363)
  * Refresh policy definition files (remove Lunar support)
  * CI and quality of life changes not impacting package functionality:
- Bump github actions to latest:
  - actions/download-artifact
  - actions/setup-go
  - actions/upload-artifact
  * Update dependencies to latest:
- github.com/charmbracelet/bubbles
- github.com/charmbracelet/bubbletea
- github.com/google/uuid
- github.com/spf13/viper
- golang.org/x/crypto
- golang.org/x/net
- golang.org/x/sync
- golang.org/x/sys
- google.golang.org/grpc
- google.golang.org/protobuf

 -- Gabriel Nagy   Fri, 26 Jan 2024 13:57:46
+0200

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2051363

Title:
  Cannot perform certificate auto-enroll without NDES installed

Status in adsys package in Ubuntu:
  Fix Released

Bug description:
  NDES role should not be mandatory in order to perform certificate
  auto-enrollment with adsys.

  Samba/ADSys is able to take advantage of the NDES endpoint to install
  the root certificate chain, but is also able to infer the certificate
  information from LDAP.

  Due to a bug in the Samba implementation of cert-autoenroll, the root
  cert is not parsed properly if the NDES component is not installed --
  so in the current state attempting auto-enrollment without NDES
  installed will result in an error like the following:

  2024-01-08 16:11:07.809|[W26775]| Failed to fetch the root certificate chain. 
| {}
  2024-01-08 16:11:07.809|[W05621]| The Network Device Enrollment Service is 
either not installed or not configured. | {}
  2024-01-08 16:11:07.809|[W11946]| Installing the server certificate only. | {}
  Traceback (most recent call last):
File "", line 142, in 
File "", line 89, in main
File "", line 20, in enroll
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 502, in __enroll
  self.apply(guid, ca, cert_enroll, ca, ldb, trust_dir,
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 369, in apply
  data = applier_func(*args, **kwargs)
 ^
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 274, in cert_enroll
  root_certs = getca(ca, url, trust_dir)
   ^
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 221, in getca
  cert = load_der_x509_certificate(ca['cACertificate'],
 ^^
File "/usr/lib/python3/dist-packages/cryptography/x509/base.py", line 528, 
in load_der_x509_certificate
  return rust_x509.load_der_x509_certificate(data)
 ^
  TypeError: argument 'data': 'str' object cannot be converted to 'PyBytes'

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


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

[Desktop-packages] [Bug 2051381] Re: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset()

[Egmont Koblinger]

Correct me please if I'm wrong, but it looks to me that you have studied
the relevant source code and even located the problem in one of the ibus
related package.

So I'm wondering, shouldn't you have filed this bug against that
component, rather than gnome-terminal?

Is there anything gnome-terminal's developers could and should do to fix
this crash? As far as I understand you, it doesn't look the case to me.

Could you please re-assign this bug to the software package where the
bug actually is and whose developers thus have a chance of fixing it?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2051381

Title:
  gnome-terminal-server crashed with SIGSEGV in
  g_utf8_pointer_to_offset()

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When I'm using ibus-keyman with the IPA (SIL) keyboard in gnome-
  terminal and type n> (or just backspace after the n), gnome-terminal
  crashes.

  The reason is that in text_input_delete_surrounding_text()
  (modules/input/imwayland.c:253) before_length doesn't get checked. If
  we don't have surrounding text (as in this case) cursor_pointer is
  NULL and thus (cursor_pointer - before_length) results in an invalid
  pointer.

  The other question is why we don't have surrounding text, but that's a
  different problem. In any case we shouldn't crash in
  text_input_delete_surrounding_text().

  I believe this is a different bug from #2036647 because of the
  different callstack and that we shouldn't call
  g_utf8_pointer_to_offset with invalid pointers.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-terminal 3.49.92-2ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 17:43:54 2024
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2024-01-23 (3 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  JournalErrors:
   Jan 26 17:43:53 hostname gnome-terminal-[4907]: g_atomic_ref_count_dec: 
assertion 'old_value > 0' failed
   Jan 26 17:43:53 hostname gnome-terminal-[4907]: g_atomic_ref_count_dec: 
assertion 'old_value > 0' failed
   Jan 26 17:44:00 hostname systemd[1623]: gnome-terminal-server.service: Main 
process exited, code=dumped, status=11/SEGV
   Jan 26 17:44:00 hostname systemd[1623]: gnome-terminal-server.service: 
Failed with result 'core-dump'.
  ProcCmdline: /usr/libexec/gnome-terminal-server
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f884099c180 :  movzbl 
(%rsi),%ecx
   PC (0x7f884099c180) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   g_utf8_pointer_to_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8
  Title: gnome-terminal-server crashed with SIGSEGV in 
g_utf8_pointer_to_offset()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users vboxsf
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2024-01-26T17:42:28.299334
  separator:

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


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

[Desktop-packages] [Bug 2051371] Re: Backspace in gnome-terminal often deletes cluster

[Egmont Koblinger]

It's never the terminal emulator (whether GNOME Terminal or any other
terminal app) that decides what to print on a backspace. The only thing
it does is that it tells over the tty line that the backspace key has
been pressed.

It's the remote party, which could be the application running inside
(such as "bash", "vim" etc.), or the kernel's cooked mode handler code
(e.g. if you're running "cat") that decides what to tell to the terminal
how to update its canvas (such as e.g. retreat the cursor by one, print
a space, and retreat the cursor again -> to achieve the visual effect of
deleting the last single-cell character). The terminal emulator has no
other choice than to blindly execute these instructions and update its
canvas accordingly. (It cannot even tell if this requested display
update was in any way connected to the backspace keypress or not, nor
should it care.)

That's just the way this whole architecture looks like. You have to file
a bugreport against whichever applications where backspace doesn't work
as you'd expect it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2051371

Title:
  Backspace in gnome-terminal often deletes cluster

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  If I have ខែ្ (U+1781 U+17c2 U+17d2) in the terminal and press
  backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left
  with ខ (U+1781). Instead it should only delete the last codepoint,
  U+17d2.

  If I have ខែ (U+1781 U+17c2) a backspace deletes only U+17c2,
  similarly if I have ខ្ (U+1781 U+17d2) where the backspace deletes
  U+17d2.

  Further investigations show that backspace often deletes the entire
  cluster, i.e. diacritic(s) plus the base character, for example with
  x̣́ (U+0078 U+0301 U+0323) where a backspace deletes all three
  codepoints.

  gnome-terminal should only delete the last codepoint [1].

  A real live example where this behavior is problematic is when using
  ibus-keyman with the Khmer Angkor keyboard [2]. When typing xEjmr the
  expected output is ខ្មែរ (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman
  does some reordering while typing to put the codepoints in a
  standardized order. Because gnome-terminal lacks support for
  surrounding text, the codepoints have to be deleted by emitting
  several backspace keypresses. Because of the deletion of the cluster
  the result in gnome-terminal is ្មែរ (U+17d2 U+1798 U+17c2 U+179a).

  [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-deletion
  [2] https://github.com/keymanapp/keyman/issues/10481

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-terminal 3.44.0-1ubuntu1 [modified: 
usr/libexec/gnome-terminal-server]
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 12:21:42 2024
  InstallationDate: Installed on 2022-04-12 (653 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2051381] [NEW] gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset()

[Eberhard Beilharz]

Public bug reported:

When I'm using ibus-keyman with the IPA (SIL) keyboard in gnome-terminal
and type n> (or just backspace after the n), gnome-terminal crashes.

The reason is that in text_input_delete_surrounding_text()
(modules/input/imwayland.c:253) before_length doesn't get checked. If we
don't have surrounding text (as in this case) cursor_pointer is NULL and
thus (cursor_pointer - before_length) results in an invalid pointer.

The other question is why we don't have surrounding text, but that's a
different problem. In any case we shouldn't crash in
text_input_delete_surrounding_text().

I believe this is a different bug from #2036647 because of the different
callstack and that we shouldn't call g_utf8_pointer_to_offset with
invalid pointers.

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-terminal 3.49.92-2ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 26 17:43:54 2024
ExecutablePath: /usr/libexec/gnome-terminal-server
InstallationDate: Installed on 2024-01-23 (3 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
JournalErrors:
 Jan 26 17:43:53 hostname gnome-terminal-[4907]: g_atomic_ref_count_dec: 
assertion 'old_value > 0' failed
 Jan 26 17:43:53 hostname gnome-terminal-[4907]: g_atomic_ref_count_dec: 
assertion 'old_value > 0' failed
 Jan 26 17:44:00 hostname systemd[1623]: gnome-terminal-server.service: Main 
process exited, code=dumped, status=11/SEGV
 Jan 26 17:44:00 hostname systemd[1623]: gnome-terminal-server.service: Failed 
with result 'core-dump'.
ProcCmdline: /usr/libexec/gnome-terminal-server
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7f884099c180 :movzbl 
(%rsi),%ecx
 PC (0x7f884099c180) ok
 source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 g_utf8_pointer_to_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so
 ?? () from /lib/x86_64-linux-gnu/libffi.so.8
 ?? () from /lib/x86_64-linux-gnu/libffi.so.8
 ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8
Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users vboxsf
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2024-01-26T17:42:28.299334
separator:

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash mantic need-amd64-retrace wayland-session

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2051381

Title:
  gnome-terminal-server crashed with SIGSEGV in
  g_utf8_pointer_to_offset()

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When I'm using ibus-keyman with the IPA (SIL) keyboard in gnome-
  terminal and type n> (or just backspace after the n), gnome-terminal
  crashes.

  The reason is that in text_input_delete_surrounding_text()
  (modules/input/imwayland.c:253) before_length doesn't get checked. If
  we don't have surrounding text (as in this case) cursor_pointer is
  NULL and thus (cursor_pointer - before_length) results in an invalid
  pointer.

  The other question is why we don't have surrounding text, but that's a
  different problem. In any case we shouldn't crash in
  text_input_delete_surrounding_text().

  I believe this is a different bug from #2036647 because of the
  different callstack and that we shouldn't call
  g_utf8_pointer_to_offset with invalid pointers.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-terminal 3.49.92-2ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 17:43:54 2024
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2024-01-23 (3 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  JournalErrors:
   Jan 26 17:43:53 hostname gnome-terminal-[4907]: g_atomic_ref_count_dec: 
assertion 'old_value > 0' failed
   Jan 26 17:43:53 hostname gnome-terminal-[4907]: g_atomic_ref_count_dec: 
assertion 'old_value > 0' failed
   Jan 26 17:44:00 hostname 

[Desktop-packages] [Bug 2051367] Re: [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2051367

Title:
  [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When using 2 external monitors via a dual HDMI adapter plugged on the
  usb-c port, when i go to play sound at all, 1 of the external monitors
  is always selected as the default output device when this should still
  be the laptop internal speakers. Annoying as hell to have to go into
  the settings everytime i switch the laptop on and there is no sound on
  sound output. It would be great if you could fix it so it leaves its
  always "laptop internal speakers" as default.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-92.102-generic 5.15.131
  Uname: Linux 5.15.0-92-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  smiler 7478 F pulseaudio
   /dev/snd/pcmC2D0c:   smiler 7478 F...m pulseaudio
   /dev/snd/controlC1:  smiler 7478 F pulseaudio
   /dev/snd/controlC0:  smiler 7478 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 14:17:02 2024
  InstallationDate: Installed on 2022-02-04 (720 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Renoir Radeon High Definition Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2021
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DTCN25WW(V1.11)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14ARE05
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrDTCN25WW(V1.11):bd09/14/2021:br1.25:efr1.25:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad514ARE05:skuLENOVO_MT_81YM_BU_idea_FM_IdeaPad514ARE05:
  dmi.product.family: IdeaPad 5 14ARE05
  dmi.product.name: 81YM
  dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05
  dmi.product.version: IdeaPad 5 14ARE05
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 2051367] [NEW] [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When using 2 external monitors via a dual HDMI adapter plugged on the
usb-c port, when i go to play sound at all, 1 of the external monitors
is always selected as the default output device when this should still
be the laptop internal speakers. Annoying as hell to have to go into the
settings everytime i switch the laptop on and there is no sound on sound
output. It would be great if you could fix it so it leaves its always
"laptop internal speakers" as default.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-92.102-generic 5.15.131
Uname: Linux 5.15.0-92-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  smiler 7478 F pulseaudio
 /dev/snd/pcmC2D0c:   smiler 7478 F...m pulseaudio
 /dev/snd/controlC1:  smiler 7478 F pulseaudio
 /dev/snd/controlC0:  smiler 7478 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 26 14:17:02 2024
InstallationDate: Installed on 2022-02-04 (720 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Renoir Radeon High Definition Audio Controller - HD-Audio Generic
Symptom_Jack: Digital Out, HDMI
Symptom_Type: None of the above
Title: [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2021
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: DTCN25WW(V1.11)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 5 14ARE05
dmi.ec.firmware.release: 1.25
dmi.modalias: 
dmi:bvnLENOVO:bvrDTCN25WW(V1.11):bd09/14/2021:br1.25:efr1.25:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad514ARE05:skuLENOVO_MT_81YM_BU_idea_FM_IdeaPad514ARE05:
dmi.product.family: IdeaPad 5 14ARE05
dmi.product.name: 81YM
dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05
dmi.product.version: IdeaPad 5 14ARE05
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session
-- 
[81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem
https://bugs.launchpad.net/bugs/2051367
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to alsa-driver in Ubuntu.

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

[Desktop-packages] [Bug 2051371] Re: Backspace in gnome-terminal often deletes cluster

[Eberhard Beilharz]

** Description changed:

  If I have ខែ្ (U+1781 U+17c2 U+17d2) in the terminal and press
  backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left
  with ខ (U+1781). Instead it should only delete the last codepoint,
  U+17d2.
  
  If I have ខែ (U+1781 U+17c2) a backspace deletes only U+17c2, similarly
  if I have ខ្ (U+1781 U+17d2) where the backspace deletes U+17d2.
  
  Further investigations show that backspace often deletes the entire
  cluster, i.e. diacritic(s) plus the base character, for example with x̣́
  (U+0078 U+0301 U+0323) where a backspace deletes all three codepoints.
  
  gnome-terminal should only delete the last codepoint [1].
  
  A real live example where this behavior is problematic is when using
- ibus-keyman with the Khmer Angkor keyboard. When typing xEjmr the
+ ibus-keyman with the Khmer Angkor keyboard [2]. When typing xEjmr the
  expected output is ខ្មែរ (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman
  does some reordering while typing to put the codepoints in a
  standardized order. Because gnome-terminal lacks support for surrounding
  text, the codepoints have to be deleted by emitting several backspace
  keypresses. Because of the deletion of the cluster the result in gnome-
  terminal is ្មែរ (U+17d2 U+1798 U+17c2 U+179a).
  
- [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-
- deletion
+ [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-deletion
+ [2] https://github.com/keymanapp/keyman/issues/10481
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-terminal 3.44.0-1ubuntu1 [modified: 
usr/libexec/gnome-terminal-server]
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 12:21:42 2024
  InstallationDate: Installed on 2022-04-12 (653 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2051371

Title:
  Backspace in gnome-terminal often deletes cluster

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  If I have ខែ្ (U+1781 U+17c2 U+17d2) in the terminal and press
  backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left
  with ខ (U+1781). Instead it should only delete the last codepoint,
  U+17d2.

  If I have ខែ (U+1781 U+17c2) a backspace deletes only U+17c2,
  similarly if I have ខ្ (U+1781 U+17d2) where the backspace deletes
  U+17d2.

  Further investigations show that backspace often deletes the entire
  cluster, i.e. diacritic(s) plus the base character, for example with
  x̣́ (U+0078 U+0301 U+0323) where a backspace deletes all three
  codepoints.

  gnome-terminal should only delete the last codepoint [1].

  A real live example where this behavior is problematic is when using
  ibus-keyman with the Khmer Angkor keyboard [2]. When typing xEjmr the
  expected output is ខ្មែរ (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman
  does some reordering while typing to put the codepoints in a
  standardized order. Because gnome-terminal lacks support for
  surrounding text, the codepoints have to be deleted by emitting
  several backspace keypresses. Because of the deletion of the cluster
  the result in gnome-terminal is ្មែរ (U+17d2 U+1798 U+17c2 U+179a).

  [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-deletion
  [2] https://github.com/keymanapp/keyman/issues/10481

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-terminal 3.44.0-1ubuntu1 [modified: 
usr/libexec/gnome-terminal-server]
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 12:21:42 2024
  InstallationDate: Installed on 2022-04-12 (653 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2051371] Re: Backspace in gnome-terminal often deletes cluster

[Eberhard Beilharz]

** Description changed:

  If I have `ខែ្` (U+1781 U+17c2 U+17d2) in the terminal and press
  backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left
  with `ខ` (U+1781). Instead it should only delete the last codepoint,
  U+17d2.
  
  If I have `ខែ` (U+1781 U+17c2) a backspace deletes only U+17c2,
  similarly if I have `ខ្` (U+1781 U+17d2) where the backspace deletes
  U+17d2.
  
  Further investigations show that backspace often deletes the entire
  cluster, i.e. diacritic(s) plus the base character, for example with
  `x̣́` (U+0078 U+0301 U+0323) where a backspace deletes all three
  codepoints.
  
  gnome-terminal should only delete the last codepoint [1].
  
  A real live example where this behavior is problematic is when using
  ibus-keyman with the Khmer Angkor keyboard. When typing
  xEjmr the
  expected output is `ខ្មែរ` (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman
  does some reordering while typing to put the codepoints in a
  standardized order. Because gnome-terminal lacks support for surrounding
  text, the codepoints have to be deleted by emitting several backspace
  keypresses. Because of the deletion of the cluster the result in gnome-
- terminal is `មែរ` (U+1798 U+17c2 U+179a).
+ terminal is ` ្មែរ` (U+17d2 U+1798 U+17c2 U+179a).
  
  [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-
  deletion
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-terminal 3.44.0-1ubuntu1 [modified: 
usr/libexec/gnome-terminal-server]
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 12:21:42 2024
  InstallationDate: Installed on 2022-04-12 (653 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

- If I have `ខែ្` (U+1781 U+17c2 U+17d2) in the terminal and press
+ If I have ខែ្ (U+1781 U+17c2 U+17d2) in the terminal and press
  backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left
- with `ខ` (U+1781). Instead it should only delete the last codepoint,
+ with ខ (U+1781). Instead it should only delete the last codepoint,
  U+17d2.
  
- If I have `ខែ` (U+1781 U+17c2) a backspace deletes only U+17c2,
- similarly if I have `ខ្` (U+1781 U+17d2) where the backspace deletes
- U+17d2.
+ If I have ខែ (U+1781 U+17c2) a backspace deletes only U+17c2, similarly
+ if I have ខ្ (U+1781 U+17d2) where the backspace deletes U+17d2.
  
  Further investigations show that backspace often deletes the entire
- cluster, i.e. diacritic(s) plus the base character, for example with
- `x̣́` (U+0078 U+0301 U+0323) where a backspace deletes all three
- codepoints.
+ cluster, i.e. diacritic(s) plus the base character, for example with x̣́
+ (U+0078 U+0301 U+0323) where a backspace deletes all three codepoints.
  
  gnome-terminal should only delete the last codepoint [1].
  
  A real live example where this behavior is problematic is when using
- ibus-keyman with the Khmer Angkor keyboard. When typing
- xEjmr the
- expected output is `ខ្មែរ` (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman
+ ibus-keyman with the Khmer Angkor keyboard. When typing xEjmr the
+ expected output is ខ្មែរ (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman
  does some reordering while typing to put the codepoints in a
  standardized order. Because gnome-terminal lacks support for surrounding
  text, the codepoints have to be deleted by emitting several backspace
  keypresses. Because of the deletion of the cluster the result in gnome-
- terminal is ` ្មែរ` (U+17d2 U+1798 U+17c2 U+179a).
+ terminal is ្មែរ (U+17d2 U+1798 U+17c2 U+179a).
  
  [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-
  deletion
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-terminal 3.44.0-1ubuntu1 [modified: 
usr/libexec/gnome-terminal-server]
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 12:21:42 2024
  InstallationDate: Installed on 2022-04-12 (653 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2051371

Title:
  Backspace in gnome-terminal often deletes cluster

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  If I have ខែ្ (U+1781 U+17c2 U+17d2) in the terminal and press
  backspace, the first backspace deletes U+17c2 U+17d2 

[Desktop-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

[Treviño]

Sorry, I missed the previous comments.

> Do I read the gnome-settings-daemon patches correctly, and this
actually just entirely drops support for auth via NSS? So the regression
potential is that if someone has set up auth via a custom system nss
database, this *will* break login for them?

Well, yes that's a regression potential that may indeed be mentioned,
it's also something that we never supported though, since that required
some extra setup in various places (write a gdm pam configuration,
create the NSS database and configure pam-pkcs11/pam_sss). But indeed it
could potentially affect someone who went through all this.

However... The SSSD side of this (lp:1905790), if one had configured a
NSS database in the canonical location, it will be migrated (using this
tool https://github.com/3v1n0/nss-database-pem-exporter).

So, it's quite a remote possibility but worth to mention in a clearer
way (it was somewhat written already).

> Unrelatedly, patches like smartcard-Use-autopointers.patch and
smartcard-manager-Use-mutex-auto-lockers-when-convenient.patch are the
sort of refactoring patches that we prefer not to see in SRUs. I don't
think they're a blocker, but they make reviewing more difficult

Let me know if I should drop them, one reason why they were added is
that they were part of the upstream changes too, and so it made easier
to ensure that we're both in the same line if problems may happen,
making easier to backport patches in future if needed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1865226

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

Status in GNOME Settings Daemon:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in sssd package in Ubuntu:
  Fix Released
Status in gdm3 source package in Focal:
  In Progress
Status in gnome-settings-daemon source package in Focal:
  Incomplete
Status in sssd source package in Focal:
  In Progress
Status in gdm3 package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  the pam profile for gdm-smartcard is missing. gdm refuses to login
  with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are
  pregenerated into debian/ and installed from there; gdm-smartcard is
  left out.

  [ Test case ]

  1. When in GDM, insert a smartcard
  2. The GDM interface should require for an user
  3. The user should be set (or empty may be provided,
     depending on sssd configuration)
  4. The smartcard PIN should be requested and once introduce the
     user must login.

  Note that this requires configuring sssd before, a simple local
  configuration could require having sssd.conf filled with:

  ```ini
  [sssd]
  enable_files_domain = True
  services = pam

  [certmap/implicit_files/$USER]
  matchrule = .*YOUR CARD IDENTIFIER*

  [pam]
  pam_cert_auth = True
  ```

  The UI authentication can also be simulated via pamtester:

  # Must be ran as user
  sudo apt install pamtester
  pamtester -v gdm-smartcard $USER authenticate

  Expected output is
  + pamtester -v gdm-smartcard ubuntu authenticate
  pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...)
  pamtester: performing operation - authenticate
  PIN for Test Organization Sub Int Token:
  pamtester: successfully authenticated

  ---

  Alternatively, if no smartcard or hardware is available, this can be tested 
and simulated using these scripts (they will reset the system setup at each 
run, but it's suggested to run them in a VM, lxd container or in a test 
installation):
   https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a

  - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \
    sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin
  - wget 
https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh
  - wget 
https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh
  - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh

  The script will generate some fake CA authority, issue some
  certificates, will install them in some software-based smartcards
  (using softhsm2) and test that they work properly to login with gdm-
  smartcard.

  Using `WAIT` environment variable set (to any value) will make it to
  restart gdm at each iteration so that an user can try to access, using
  the username that launched the script and the pin of 123456.

  [ Regression potential ]

  Smartcard authentication using custom methods using via a custom
  configured system nss database may not work anymore.

  ---

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.4
  ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  

[Desktop-packages] [Bug 1925683] Re: Cursor Tracking with Gnome Shell Magnifier on Wayland

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1925683

Title:
  Cursor Tracking with Gnome Shell Magnifier on Wayland

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Affected version
  GNOME 3.36 - 3.40.
  Ubuntu 20.04, 20.10, 21.04 and Fedora 34 Beta.
  Wayland only.
  Bug summary
  When running GNOME shell with Wayland, the cursor and focus tracking 
functionality of the magnifier (a11y feature) do not correctly compute the 
cursor/focus location. The position is calculated from the top left of the 
window but the windows position is not included. This causes the magnifier to 
track the wrong location when the window is not maximiser or is on a second 
monitor.

  I suspect this is related to the way in which wayland is designed. But
  my experience in this area is minimal. When using X11 this feature
  works correctly.

  The wiki page states that under wayland the cursor and focus tracking
  work but this information is either out dated or was not tested
  correctly.

  Steps to reproduce
  From the Gnome desktop, open a terminal by pressing ctrl + alt + t or by 
opening the activities overlay and searching for "terminal".
  Press super + left arrow key to maximize the terminal window on the left side 
of the screen.
  Activity the magnifier by pressing super + alt + 8.
  Type text into the terminal window. The magnified view will move with the 
text cursor.
  Press super + right arrow key to maximize the terminal windows on the right 
side of the screen.
  Type text into the terminal. The magnified view will move but it will not 
show the text cursor. It will move when text is entered but will focus on the 
left side of the screen.
  What happened
  The magnified view does not follow the text/focus cursor correctly.

  What did you expect to happen
  The magnified view should follow the cursor and show the cursor as it does 
when the widnows is maximized. The correct behaviour can also be seen in Gnome 
shell running with X11.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 22 20:55:25 2021
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2021-04-22 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2051371] [NEW] Backspace in gnome-terminal often deletes cluster

[Eberhard Beilharz]

Public bug reported:

If I have `ខែ្` (U+1781 U+17c2 U+17d2) in the terminal and press
backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left
with `ខ` (U+1781). Instead it should only delete the last codepoint,
U+17d2.

If I have `ខែ` (U+1781 U+17c2) a backspace deletes only U+17c2,
similarly if I have `ខ្` (U+1781 U+17d2) where the backspace deletes
U+17d2.

Further investigations show that backspace often deletes the entire
cluster, i.e. diacritic(s) plus the base character, for example with
`x̣́` (U+0078 U+0301 U+0323) where a backspace deletes all three
codepoints.

gnome-terminal should only delete the last codepoint [1].

A real live example where this behavior is problematic is when using
ibus-keyman with the Khmer Angkor keyboard. When typing
xEjmr the
expected output is `ខ្មែរ` (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman
does some reordering while typing to put the codepoints in a
standardized order. Because gnome-terminal lacks support for surrounding
text, the codepoints have to be deleted by emitting several backspace
keypresses. Because of the deletion of the cluster the result in gnome-
terminal is `មែរ` (U+1798 U+17c2 U+179a).

[1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-
deletion

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-terminal 3.44.0-1ubuntu1 [modified: 
usr/libexec/gnome-terminal-server]
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 26 12:21:42 2024
InstallationDate: Installed on 2022-04-12 (653 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2051371

Title:
  Backspace in gnome-terminal often deletes cluster

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  If I have `ខែ្` (U+1781 U+17c2 U+17d2) in the terminal and press
  backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left
  with `ខ` (U+1781). Instead it should only delete the last codepoint,
  U+17d2.

  If I have `ខែ` (U+1781 U+17c2) a backspace deletes only U+17c2,
  similarly if I have `ខ្` (U+1781 U+17d2) where the backspace deletes
  U+17d2.

  Further investigations show that backspace often deletes the entire
  cluster, i.e. diacritic(s) plus the base character, for example with
  `x̣́` (U+0078 U+0301 U+0323) where a backspace deletes all three
  codepoints.

  gnome-terminal should only delete the last codepoint [1].

  A real live example where this behavior is problematic is when using
  ibus-keyman with the Khmer Angkor keyboard. When typing
  xEjmr the
  expected output is `ខ្មែរ` (U+1781 U+17d2 U+1798 U+17c2 U+179a).
  Keyman does some reordering while typing to put the codepoints in a
  standardized order. Because gnome-terminal lacks support for
  surrounding text, the codepoints have to be deleted by emitting
  several backspace keypresses. Because of the deletion of the cluster
  the result in gnome-terminal is `មែរ` (U+1798 U+17c2 U+179a).

  [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-
  deletion

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-terminal 3.44.0-1ubuntu1 [modified: 
usr/libexec/gnome-terminal-server]
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 12:21:42 2024
  InstallationDate: Installed on 2022-04-12 (653 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

[Timo Aaltonen]

What's the status here? Questions are still unanswered after four
months.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1865226

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

Status in GNOME Settings Daemon:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in sssd package in Ubuntu:
  Fix Released
Status in gdm3 source package in Focal:
  In Progress
Status in gnome-settings-daemon source package in Focal:
  Incomplete
Status in sssd source package in Focal:
  In Progress
Status in gdm3 package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  the pam profile for gdm-smartcard is missing. gdm refuses to login
  with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are
  pregenerated into debian/ and installed from there; gdm-smartcard is
  left out.

  [ Test case ]

  1. When in GDM, insert a smartcard
  2. The GDM interface should require for an user
  3. The user should be set (or empty may be provided,
     depending on sssd configuration)
  4. The smartcard PIN should be requested and once introduce the
     user must login.

  Note that this requires configuring sssd before, a simple local
  configuration could require having sssd.conf filled with:

  ```ini
  [sssd]
  enable_files_domain = True
  services = pam

  [certmap/implicit_files/$USER]
  matchrule = .*YOUR CARD IDENTIFIER*

  [pam]
  pam_cert_auth = True
  ```

  The UI authentication can also be simulated via pamtester:

  # Must be ran as user
  sudo apt install pamtester
  pamtester -v gdm-smartcard $USER authenticate

  Expected output is
  + pamtester -v gdm-smartcard ubuntu authenticate
  pamtester: invoking pam_start(gdm-smartcard, ubuntu, ...)
  pamtester: performing operation - authenticate
  PIN for Test Organization Sub Int Token:
  pamtester: successfully authenticated

  ---

  Alternatively, if no smartcard or hardware is available, this can be tested 
and simulated using these scripts (they will reset the system setup at each 
run, but it's suggested to run them in a VM, lxd container or in a test 
installation):
   https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a

  - sudo apt install gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin && \
    sudo apt-mark auto gdm3 pamtester softhsm2 openssl wget sssd gnutls-bin
  - wget 
https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-gdm-smartcard-pam-auth-tester.sh
  - wget 
https://gist.github.com/3v1n0/287d02ca8e03936f1c7bba992173d47a/raw/sssd-softhism2-certificates-tests.sh
  - sudo bash ./sssd-gdm-smartcard-pam-auth-tester.sh

  The script will generate some fake CA authority, issue some
  certificates, will install them in some software-based smartcards
  (using softhsm2) and test that they work properly to login with gdm-
  smartcard.

  Using `WAIT` environment variable set (to any value) will make it to
  restart gdm at each iteration so that an user can try to access, using
  the username that launched the script and the pin of 123456.

  [ Regression potential ]

  Smartcard authentication using custom methods using via a custom
  configured system nss database may not work anymore.

  ---

  ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.4
  ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 14:30:30 2020
  InstallationDate: Installed on 2016-05-23 (1376 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions


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

[Desktop-packages] [Bug 2051346] Re: No longer preseed LXD snap to allow for LXD 5.20 release

[Łukasz Zemczak]

If the impact on first-time start is acceptable by the server team
(which seems to be the case), this looks like a reasonable ask.

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

Title:
  No longer preseed LXD snap to allow for LXD  5.20 release

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  With LXD 5.20 there is a license change to AGPL and it has been
  decided to no longer seed the snap in Ubuntu 24.04 and later and
  instead seed the lxd-installer package instead.

  This bug is to track the work of making that change in the server seed
  @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/tree/server#n60

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


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

[Desktop-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack

[Timo Aaltonen]

regression fix is in, so this can be marked as verified

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037604

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 
(TGL/ADL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

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


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

[Desktop-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

[Timo Aaltonen]

tested on my hw, works as planned

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2051068

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
  (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
  gpu on boot, causing a blank screen with no GDM running (with wayland,
  and fallback to X failed too).

  [Fix]

  Revert the commit that allows using 64k page size, since that's what
  the current version in jammy-updates is using. OEM-6.1 kernel is going
  away, no need to patch that anymore. No other kernel is affected, >6.2
  works fine and thus this revert is not necessary in mantic or noble.

  [Test case]

  Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't
  matter). The login screen should appear.

  [Where things could go wrong]
  Hard to see how this could regress anything, as it just restores the limits 
for intel gfx12.5 as they were in the current mesa version in jammy.

  ---

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

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


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

[Desktop-packages] [Bug 2051363] Re: Cannot perform certificate auto-enroll without NDES installed

[Gabriel Nagy]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2051363

Title:
  Cannot perform certificate auto-enroll without NDES installed

Status in adsys package in Ubuntu:
  Fix Committed

Bug description:
  NDES role should not be mandatory in order to perform certificate
  auto-enrollment with adsys.

  Samba/ADSys is able to take advantage of the NDES endpoint to install
  the root certificate chain, but is also able to infer the certificate
  information from LDAP.

  Due to a bug in the Samba implementation of cert-autoenroll, the root
  cert is not parsed properly if the NDES component is not installed --
  so in the current state attempting auto-enrollment without NDES
  installed will result in an error like the following:

  2024-01-08 16:11:07.809|[W26775]| Failed to fetch the root certificate chain. 
| {}
  2024-01-08 16:11:07.809|[W05621]| The Network Device Enrollment Service is 
either not installed or not configured. | {}
  2024-01-08 16:11:07.809|[W11946]| Installing the server certificate only. | {}
  Traceback (most recent call last):
File "", line 142, in 
File "", line 89, in main
File "", line 20, in enroll
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 502, in __enroll
  self.apply(guid, ca, cert_enroll, ca, ldb, trust_dir,
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 369, in apply
  data = applier_func(*args, **kwargs)
 ^
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 274, in cert_enroll
  root_certs = getca(ca, url, trust_dir)
   ^
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 221, in getca
  cert = load_der_x509_certificate(ca['cACertificate'],
 ^^
File "/usr/lib/python3/dist-packages/cryptography/x509/base.py", line 528, 
in load_der_x509_certificate
  return rust_x509.load_der_x509_certificate(data)
 ^
  TypeError: argument 'data': 'str' object cannot be converted to 'PyBytes'

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


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

[Desktop-packages] [Bug 2051363] [NEW] Cannot perform certificate auto-enroll without NDES installed

[Gabriel Nagy]

Public bug reported:

NDES role should not be mandatory in order to perform certificate auto-
enrollment with adsys.

Samba/ADSys is able to take advantage of the NDES endpoint to install
the root certificate chain, but is also able to infer the certificate
information from LDAP.

Due to a bug in the Samba implementation of cert-autoenroll, the root
cert is not parsed properly if the NDES component is not installed -- so
in the current state attempting auto-enrollment without NDES installed
will result in an error like the following:

2024-01-08 16:11:07.809|[W26775]| Failed to fetch the root certificate chain. | 
{}
2024-01-08 16:11:07.809|[W05621]| The Network Device Enrollment Service is 
either not installed or not configured. | {}
2024-01-08 16:11:07.809|[W11946]| Installing the server certificate only. | {}
Traceback (most recent call last):
  File "", line 142, in 
  File "", line 89, in main
  File "", line 20, in enroll
  File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 502, in __enroll
self.apply(guid, ca, cert_enroll, ca, ldb, trust_dir,
  File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 369, in apply
data = applier_func(*args, **kwargs)
   ^
  File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 274, in cert_enroll
root_certs = getca(ca, url, trust_dir)
 ^
  File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 221, in getca
cert = load_der_x509_certificate(ca['cACertificate'],
   ^^
  File "/usr/lib/python3/dist-packages/cryptography/x509/base.py", line 528, in 
load_der_x509_certificate
return rust_x509.load_der_x509_certificate(data)
   ^
TypeError: argument 'data': 'str' object cannot be converted to 'PyBytes'

** Affects: adsys (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2051363

Title:
  Cannot perform certificate auto-enroll without NDES installed

Status in adsys package in Ubuntu:
  New

Bug description:
  NDES role should not be mandatory in order to perform certificate
  auto-enrollment with adsys.

  Samba/ADSys is able to take advantage of the NDES endpoint to install
  the root certificate chain, but is also able to infer the certificate
  information from LDAP.

  Due to a bug in the Samba implementation of cert-autoenroll, the root
  cert is not parsed properly if the NDES component is not installed --
  so in the current state attempting auto-enrollment without NDES
  installed will result in an error like the following:

  2024-01-08 16:11:07.809|[W26775]| Failed to fetch the root certificate chain. 
| {}
  2024-01-08 16:11:07.809|[W05621]| The Network Device Enrollment Service is 
either not installed or not configured. | {}
  2024-01-08 16:11:07.809|[W11946]| Installing the server certificate only. | {}
  Traceback (most recent call last):
File "", line 142, in 
File "", line 89, in main
File "", line 20, in enroll
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 502, in __enroll
  self.apply(guid, ca, cert_enroll, ca, ldb, trust_dir,
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 369, in apply
  data = applier_func(*args, **kwargs)
 ^
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 274, in cert_enroll
  root_certs = getca(ca, url, trust_dir)
   ^
File "/usr/share/adsys/python/vendor_samba/gp/gp_cert_auto_enroll_ext.py", 
line 221, in getca
  cert = load_der_x509_certificate(ca['cACertificate'],
 ^^
File "/usr/lib/python3/dist-packages/cryptography/x509/base.py", line 528, 
in load_der_x509_certificate
  return rust_x509.load_der_x509_certificate(data)
 ^
  TypeError: argument 'data': 'str' object cannot be converted to 'PyBytes'

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


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

[Desktop-packages] [Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

[jjjttwkr]

** Attachment added: "DKMS make.log for nvidia-390.157 for kernel 
6.5.0-15-generic (x86_64)"
   https://pastebin.ubuntu.com/p/sK4SFppMPr/

** Attachment removed: "APT and DKMS make.log"
   https://pastebin.ubuntu.com/p/sK4SFppMPr/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1573508

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions


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

[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

[Sebastien Bacher]

It should also just be working with the firefox snap, what's your
testcase?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux 
browsers.
  We will close this bug when both browsers will have Va-api decoding working 
OOTB without user interaction like in WinOS and MacOS

  August 2022 :

  * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with
  intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1
  )

     -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works
 -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need 
to fix this as most youtube is AV1 now.

  * In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497

  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  * In 2015 I opened this bug , no easy solution was available and
  battery drained when playing video in browser was crazy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions


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

[Desktop-packages] [Bug 1424201] Re: Web browsers lacking hardware-accelerated video decoding

[Michel-Ekimia]

Vaapi in Flatpak Firefox works OOTB now ( Just a flag away) so
definitely the best solution.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1424201

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  This is a Meta Bug for GPU accelerated video decoding on Ubuntu/Linux 
browsers.
  We will close this bug when both browsers will have Va-api decoding working 
OOTB without user interaction like in WinOS and MacOS

  August 2022 :

  * Ubuntu 22.04 : Launch firefox snap on Intel Tiger lake -> Check with
  intel_gpu_top that no codec are GPU decoded ( either VP9 , H264 or AV1
  )

     -> change media.ffmpeg.vaapi.enabled to true = VP9 and H264 decoding works
 -> AV1 hwdec does not work in Firefox or VLC , but does with MPV . We need 
to fix this as most youtube is AV1 now.

  * In july 2020, things are getting better :

  - Chromium :

  A patch is used on most distro packages. , more info here
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1816497

  - Firefox :

  Firefox team has done a great job and now Va-api decoding in Wayland
  is possible and X11 is possible in nightly !

  Follow it here : https://bugzilla.mozilla.org/show_bug.cgi?id=1210727

  * In 2015 I opened this bug , no easy solution was available and
  battery drained when playing video in browser was crazy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1424201/+subscriptions


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

[Desktop-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

[Timo Aaltonen]

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2051068

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
  (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
  gpu on boot, causing a blank screen with no GDM running (with wayland,
  and fallback to X failed too).

  [Fix]

  Revert the commit that allows using 64k page size, since that's what
  the current version in jammy-updates is using. OEM-6.1 kernel is going
  away, no need to patch that anymore. No other kernel is affected, >6.2
  works fine and thus this revert is not necessary in mantic or noble.

  [Test case]

  Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't
  matter). The login screen should appear.

  [Where things could go wrong]
  Hard to see how this could regress anything, as it just restores the limits 
for intel gfx12.5 as they were in the current mesa version in jammy.

  ---

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

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


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

[Desktop-packages] [Bug 2051346] Re: No longer preseed LXD snap to allow for LXD 5.20 release

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~philroche/ubuntu-seeds/+git/ubuntu/+merge/459502

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

Title:
  No longer preseed LXD snap to allow for LXD  5.20 release

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  With LXD 5.20 there is a license change to AGPL and it has been
  decided to no longer seed the snap in Ubuntu 24.04 and later and
  instead seed the lxd-installer package instead.

  This bug is to track the work of making that change in the server seed
  @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/tree/server#n60

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


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

[Desktop-packages] [Bug 2051346] [NEW] No longer preseed LXD snap to allow for LXD 5.20 release

[Philip Roche]

Public bug reported:

With LXD 5.20 there is a license change to AGPL and it has been decided
to no longer seed the snap in Ubuntu 24.04 and later and instead seed
the lxd-installer package instead.

This bug is to track the work of making that change in the server seed @
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/ubuntu/tree/server#n60

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  With LXD 5.20 there is a license change to AGPL and it has been decided
- to no longer seed the snap in Ubuntu 22.04 and later and instead seed
+ to no longer seed the snap in Ubuntu 24.04 and later and instead seed
  the lxd-installer package instead.
  
  This bug is to track the work of making that change in the server seed @
  https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/tree/server#n60

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

Title:
  No longer preseed LXD snap to allow for LXD  5.20 release

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  With LXD 5.20 there is a license change to AGPL and it has been
  decided to no longer seed the snap in Ubuntu 24.04 and later and
  instead seed the lxd-installer package instead.

  This bug is to track the work of making that change in the server seed
  @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/tree/server#n60

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


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

[Desktop-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

[Timo Aaltonen]

GA kernel doesn't support DG2, oem-6.1 was the first one, hwe-6.2 does
too and works more or less fine (doesn't suffer from this issue)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2051068

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
  (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
  gpu on boot, causing a blank screen with no GDM running (with wayland,
  and fallback to X failed too).

  [Fix]

  Revert the commit that allows using 64k page size, since that's what
  the current version in jammy-updates is using. OEM-6.1 kernel is going
  away, no need to patch that anymore. No other kernel is affected, >6.2
  works fine and thus this revert is not necessary in mantic or noble.

  [Test case]

  Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't
  matter). The login screen should appear.

  [Where things could go wrong]
  Hard to see how this could regress anything, as it just restores the limits 
for intel gfx12.5 as they were in the current mesa version in jammy.

  ---

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

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


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

[Desktop-packages] [Bug 2018539] Re: File selector extremely slow

[Andres Hernandez]

I also have this issue. The first time the file dialog opens (e.g. in
Firefox, when you right-click and do save as on an image) the dialog
appears instantly. However, each subsequent file save seems to take
exponentially longer. To the second time it's 1 second, then 2 seconds,
5 seconds, and keeps going until it's like 1 minute (at this point I
stop). Strangely, if I then attempt to open Nautilus (through the OS
menu) then Nautilus also takes 10 seconds or whatever to open. However
(with Firefox still open) if I do save as at that point, then it becomes
instant for the first save (and then continues to increase as before).
Is there any information I can provide to assist in solving this?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2018539

Title:
  File selector extremely slow

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When you try to upload/download a file in an application (e.g.
  Firefox, Signal, etc) the file selector that opens is extremely slow
  to appear, search and change directory.

  Often times, if I try to search for a file in it, I have to wait 10 or
  more second before the letters I typed appear, and most of the time
  the last letter I pressed when typing, will appear before the rest of
  what I wrote, meaning I have to wait for my query to be deleted before
  I re-type it again.

  This has only just started since upgrading to Ubuntu 23.04.  I noticed
  that Nautilus has been faster in general since the update, but in the
  file selector specifically, it's become unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  4 20:39:48 2023
  InstallationDate: Installed on 2022-10-22 (194 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.48.0-1ubuntu1
   python3-nautilus  4.0-1build1

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


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

[Desktop-packages] [Bug 1793124] Re: [upstream] Scrolling on Calc leaves content invisible if cell is higher than screen

[Bug Watch Updater]

** Bug watch added: bz.apache.org/ooo/ #7722
   https://bz.apache.org/ooo/show_bug.cgi?id=7722

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1793124

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+subscriptions


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

[Desktop-packages] [Bug 1793124]

[Daniel-schaaaf]

The formula bar is helpful only to edit the content of an oversized
cell. But it doesn't help navigating/viewing the spread sheet itself.

A "scroll by screen pixel" sounds like a difficult change. At the same
time, it would not only solve the problem with oversized cells, it would
also be an advantage over Microsoft Excel.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1793124

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+subscriptions


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

[Desktop-packages] [Bug 1793124]

[Vsfoote]

(In reply to gulpen from comment #39)

> Please give this issue some love!

We have.

Two options for working with wide columns or tall rows. Or with
undersized displays.

One would be to adjust the sheet scroll from default spreadsheet centric
"scroll by cell edge" to a "scroll by screen pixel" and requiring new
implementation.

The other option was implemented to expose the content of oversize cells
to edit engine and UI control via an expandable input window on the
FormulaBar (View ->  Formula Bar) where you will find a "Expand Formula
Bar" and "Collapse Formula Bar" toggle triangle.

The collapsed formula bar is one character row in height. The expanded
formula bar input window can be dragged as tall as 25 lines. Default is
6 lines, but the UI value is recorded into the spreadsheet on save, so
it keeps it handy.  For really large cell content (an actual sc formula
or text strings), the input window has a vertical scroll to work with
the entire cell (up to 64,000 characters IANM).

Pixel level scrolling a sheet would be nice to implement, but you
already are able to work with cells larger than the display or the app
window using the Formula Bar's input window, without having to zoom the
sheet out.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1793124

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+subscriptions


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

[Desktop-packages] [Bug 1793124]

[Gulpen]

Still this issue is making my usage of LibreOffice on several projects a
living hell. I find it very strange some people try to downplay it,
while many have attested to its importance, over a period spanning
decades. I can find an OpenOffice ticket all the way from 2002 attesting
to the same. https://bz.apache.org/ooo/show_bug.cgi?id=7722

Working on a laptop - a small screen - as I often do these days, makes
this even more problematic. MS Excel had the same issue for decades
though has meanwhile solved it (using v16 on Mac), so apparently saw the
rationale after all.

Please give this issue some love!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1793124

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+subscriptions


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

[Desktop-packages] [Bug 2051188] Re: Firefox 122 update breaks webextensions permission

[Bug Watch Updater]

Launchpad has imported 13 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1876447.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-01-25T05:06:07+00:00 Me+bz wrote:

Steps to reproduce:

- Update to Firefox 122 on Ubuntu
- Install Video DownloadHelper and its Companion App.
- In the settings of the addon, see that the Companion App is not recognized

The command:

```
$ flatpak permission-show snap.firefox
``

Shows that Firefox is allowed to read the manifest.

But it doesn't. The logs say:

```
Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”
Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop firefox_firefox.desktop[154219]: 
[Parent 154219, Main Thread] WARNING: OnGetManifestDone error: 
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 
“GetManifest”: 'glib warning', file 
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187
```

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/1


On 2024-01-25T05:07:58+00:00 Me+bz wrote:

launchpad bug: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/2051188

@Sylvestre Can you see if you find anyone who could assist?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/2


On 2024-01-25T05:15:14+00:00 Me+bz wrote:

I'm working on the Video DownloadHelper extension (100_000+ Linux users,
mostly Ubuntu), and the Snap sandbox has always been a problem, but that
specific update made it worse. We're getting those bug reports since the
yesterday.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/3


On 2024-01-25T05:41:16+00:00 Release-mgmt-account-bot wrote:

:me+bz, if you think that's a regression, could you try to find a
regression range using for example
[mozregression](https://wiki.mozilla.org/Auto-
tools/Projects/Mozregression)?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/4


On 2024-01-25T05:41:56+00:00 Release-mgmt-account-bot wrote:

The [Bugbug](https://github.com/mozilla/bugbug/) bot thinks this bug
should belong to the 'Core::Widget: Gtk' component, and is moving the
bug to that component. Please correct in case you think the bot is
wrong.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/5


On 2024-01-25T05:44:28+00:00 Me+bz wrote:

(In reply to BugBot [:suhaib / :marco/ :calixte] from comment #3)
> :me+bz, if you think that's a regression, could you try to find a regression 
> range using for example 
> [mozregression](https://wiki.mozilla.org/Auto-tools/Projects/Mozregression)?

That's a little tricky because it's a snap-sandbox specific issue, and
mozregression doesn't work with Snap:
https://bugzilla.mozilla.org/show_bug.cgi?id=1763188

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/6


On 2024-01-25T06:00:02+00:00 Me+bz wrote:

Created attachment 9376384
Screenshot 1 of the exception

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/8


On 2024-01-25T06:00:56+00:00 Me+bz wrote:

I've attached the exception from the js console.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/9


On 2024-01-25T06:10:18+00:00 Me+bz wrote:

More investigation: the code that's throwing comes from a patch by
Canonical: https://github.com/canonical/firefox-
snap/blob/stable/patches/native-messaging-portal.patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/11


On 2024-01-25T06:19:58+00:00 Me+bz wrote:

This is the code that's breaking the extension:
https://github.com/canonical/firefox-
snap/blob/7f87c2af624891313906abe7fdccfda1ad76a0f7/patches/native-
messaging-portal.patch#L748

Commit: https://github.com/canonical/firefox-
snap/commit/f1bf0d6dd649e13a1a9a159de63ae74068966c0c

If you guys have a quick access to Canonical, help would be appreciated.

Reply at: