[Desktop-packages] [Bug 2063383] [NEW] [SRU] Ubuntu Unity takes 90 seconds to log out

[Simon Quigley]

Public bug reported:

[ Impact ]

Ubuntu Unity reliably takes 90 seconds to log out. This is due to the
user-level gnome-session.service systemd unit not properly terminating
gnome-session on logout. An attempt is made to send SIGTERM to the
process, which gnome-session does not care about.

Instead, gnome-session-quit should be invoked when the systemd unit
shuts down, which acts effectively and immediately.

[ Test Plan ]

Actual behavior:
 1. Log in to a Unity session on Ubuntu Unity 24.04.
 2. Log out of Ubuntu Unity.
 3. Observe that only the wallpaper is shown for 90 seconds prior to the login 
manager showing again.

Expected behavior:
 1. Log in to a Unity session on Ubuntu Unity 24.04.
 2. Log out of Ubuntu Unity.
 3. Observe that logging out takes a few seconds at most, and you are able to 
log back in as the same user, or a different one.

[ Where problems could occur ]

If the gnome-session or gnome-session-quit binaries change the arguments
they accept by default, log in and log out functionality on Unity
sessions are likely to break.

Additionally, if lightdm or systemd changes in a non-reverse-compatible
way, this increases the chance of a user-facing regression.

** Affects: gnome-session (Ubuntu)
 Importance: High
 Assignee: Simon Quigley (tsimonq2)
 Status: Confirmed

** Affects: gnome-session (Ubuntu Noble)
 Importance: High
 Assignee: Simon Quigley (tsimonq2)
 Status: Confirmed

** Summary changed:

- Ubuntu Unity takes 90 seconds to log out
+ [SRU] Ubuntu Unity takes 90 seconds to log out

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

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

** Changed in: gnome-session (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Also affects: gnome-session (Ubuntu Noble)
   Importance: High
 Assignee: Simon Quigley (tsimonq2)
   Status: Confirmed

** Changed in: gnome-session (Ubuntu Noble)
Milestone: None => noble-updates

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

Title:
  [SRU] Ubuntu Unity takes 90 seconds to log out

Status in gnome-session package in Ubuntu:
  Confirmed
Status in gnome-session source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  Ubuntu Unity reliably takes 90 seconds to log out. This is due to the
  user-level gnome-session.service systemd unit not properly terminating
  gnome-session on logout. An attempt is made to send SIGTERM to the
  process, which gnome-session does not care about.

  Instead, gnome-session-quit should be invoked when the systemd unit
  shuts down, which acts effectively and immediately.

  [ Test Plan ]

  Actual behavior:
   1. Log in to a Unity session on Ubuntu Unity 24.04.
   2. Log out of Ubuntu Unity.
   3. Observe that only the wallpaper is shown for 90 seconds prior to the 
login manager showing again.

  Expected behavior:
   1. Log in to a Unity session on Ubuntu Unity 24.04.
   2. Log out of Ubuntu Unity.
   3. Observe that logging out takes a few seconds at most, and you are able to 
log back in as the same user, or a different one.

  [ Where problems could occur ]

  If the gnome-session or gnome-session-quit binaries change the
  arguments they accept by default, log in and log out functionality on
  Unity sessions are likely to break.

  Additionally, if lightdm or systemd changes in a non-reverse-
  compatible way, this increases the chance of a user-facing regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383/+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 2061214] Re: [SRU] Software Sources is not compatible with deb822

[Simon Quigley]

** Description changed:

+ [ Impact ]
+ 
+ Ubuntu 24.04 now uses deb822 to represent software sources for deb
+ packages, instead of /etc/apt/sources.list. The complete rationale for
+ this change can be found here: https://discourse.ubuntu.com/t/spec-apt-
+ deb822-sources-by-default/29333
+ 
+ software-properties has two graphical frontends for editing these
+ software sources, one is GTK-based and the other is Qt-based. When the
+ underlying change to deb822 sources was made, the GTK-based frontend and
+ the DBus backend interface gained support.
+ 
+ The original bug report shown below informed us of the lack of deb822
+ support in the Qt frontend, which results in a broken, non-functional
+ interface when attempting to view or edit most values on the first two
+ tabs. The fix for this is to implement a Qt dialog for deb822 sources
+ that somewhat matches the existing GTK interface.
+ 
+ [ Test Plan ]
+ 
+ Install software-properties-qt 0.99.48 or earlier.
+ 
+ Reproducing the bug:
+  1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
+  2. Observe that all four checkboxes on the Ubuntu Software tab (main, 
universe, restricted, and multiverse) are unchecked.
+  3. Move to the Other Software tab and observe that there are no items in the 
list.
+ 
+ Upgrade to software-properties-qt 0.99.49.
+ 
+ Intended functionality:
+  1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
+  2. Observe that one or more checkboxes on the Ubuntu Software tab 
(representing main, universe, restricted, or multiverse) are checked. Toggle 
one or more of the checkboxes.
+  3. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.
+  4. Switch to the Other Software tab, there should be one item in the list.
+  5. Select that item, then click Edit at the bottom of the dialog. Make a 
modification to every field on the screen, or a combination of fields you would 
like to test. All fields should work.
+  6. Click the OK button at the bottom of the dialog to confirm the changes, 
then click Edit for that item again. The changes you made should be reflected 
(meaning, the changes were saved.)
+  7. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.
+ 
+ [ Where problems could occur ]
+ 
+ This is well-tested code. That being said, the following small edge cases 
exist:
+  - If you create a very large amount of rows, it infinitely expands the 
dialog without a scroll wheel. This is the same functionality as the GTK 
frontend.
+  - Error validation is not performed on the deb822 lines, they are simply 
written to the ubuntu.sources file. This is good as a starting point, but also 
relies on the appropriate update notifier handling these errors. This is the 
same functionality as the GTK frontend.
+ 
+ In a future update, this functionality could be broken by one or more of the 
following underlying changes:
+  - Changes to the software-properties backend which are only implemented for 
the GTK frontend.
+  - Changes to the location or formatting of the ubuntu.sources file.
+  - Regressions in the Python bindings for Qt 5, which are rare but possible.
+  - Regressions in Python itself.
+ 
+ [ Other Info ]
+  
+ Ubuntu Studio's live ISO and installed system are affected by this. Only 
Lubuntu's installed system is affected by this.
+ 
+ [ Original Report ]
+ 
  Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software
  sources" not correctly updated after upgrade. Prompt= shows normal and
  not LTS
  
  Used command sudo do-release-upgrade -d
  
  Otherwise the upgrade is good
  
  see attached screenshot
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.46
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Sat Apr 13 11:44:28 2024
  InstallationDate: Installed on 2024-04-13 (0 days ago)
  InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240331)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00

** Also affects: software-properties (Ubuntu Noble)
   Importance: Critical
 Assignee: Simon Quigley (tsimonq2)
   Status: Confirmed

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

Title:
  [SRU] Software Sources is not compatible with deb822

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Nob

[Desktop-packages] [Bug 2063109] [NEW] Splash screen not rendering correctly on several flavors

[Simon Quigley]

Public bug reported:

On several flavors (I have confirmed Ubuntu Unity and Lubuntu thus far),
if the machine does not have much resources, it falls back to the text-
based Plymouth boot screen.

Steps to reproduce:
 - Find a machine with 1 core and 2 GB of RAM, a virtual machine will do.
 - Boot up a live ISO of Lubuntu or Ubuntu Unity.

Expected result: the appropriate graphical splash screen is shown.
Actual result: Only the text-based splash screen for Plymouth is shown.

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

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

Title:
  Splash screen not rendering correctly on several flavors

Status in plymouth package in Ubuntu:
  New

Bug description:
  On several flavors (I have confirmed Ubuntu Unity and Lubuntu thus
  far), if the machine does not have much resources, it falls back to
  the text-based Plymouth boot screen.

  Steps to reproduce:
   - Find a machine with 1 core and 2 GB of RAM, a virtual machine will do.
   - Boot up a live ISO of Lubuntu or Ubuntu Unity.

  Expected result: the appropriate graphical splash screen is shown.
  Actual result: Only the text-based splash screen for Plymouth is shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2063109/+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 2062956] Re: CVE-2024-32462 - Need to update to the last secure patch

[Simon McVittie]

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

This is the same vulnerability as LP: #2062406.

** This bug has been marked a duplicate of bug 2062406
   CVE-2024-32462: Sandbox escape via RequestBackground portal and CWE-88

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

Title:
  CVE-2024-32462 - Need to update to the last secure patch

Status in flatpak package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  There is a security issue in flatpack package, see: 
https://www.cve.org/CVERecord?id=CVE-2024-32462
  To fix that, according to Ubuntu version we have to update the package to one 
of these versions: 1.10.9, 1.12.9, 1.14.6, and 1.15.8,

  Here is the current statut:

  Noble = OK
  Mantic = update required
  Jammy = update required
  Focal = update required

  Could you please check that and provide the patched version?

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2062956/+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 2059158] Re: proposed-migration for gtk4 4.14.1+ds-0ubuntu1

[Simon Chopin]

That's not time-t. Some scripts in /usr/libexec/installed-
tests/gtk-4.0/tools used to be executable and now are not:

noble-dev ❯ ls -lh /usr/libexec/installed-tests/gtk-4.0/tools/simplify
.rwxr-xr-x root root 1.0 KB Fri Jan 26 20:26:45 2024  
/usr/libexec/installed-tests/gtk-4.0/tools/simplify

noble-dev ❯ dpkg-deb -c gtk-4-tests_4.14.1+ds-0ubuntu2_amd64.deb | egrep 
'simplify$'
-rw-r--r-- root/root  1030 2024-03-30 23:52 
./usr/libexec/installed-tests/gtk-4.0/tools/simplify

(the 'settings' script is also affected)

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

Title:
  proposed-migration for gtk4 4.14.1+ds-0ubuntu1

Status in gtk4 package in Ubuntu:
  New

Bug description:
  gtk4 4.14.1+ds-0ubuntu1 is stuck in -proposed with test regressions on
  armhf.

  1706s # Running test: gtk-4.0/tools/settings.test
  1706s # FAIL: gtk-4.0/tools/settings.test (Child process exited with code 126)
  1706s not ok - gtk-4.0/tools/settings.test

  2100s # Running test: gtk-4.0/tools/simplify.test
  2100s # FAIL: gtk-4.0/tools/simplify.test (Child process exited with code 126)
  2100s not ok - gtk-4.0/tools/simplify.test

  almost certainly time-t related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2059158/+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 2060154] Re: Sort by "Modified" uses lexicographic ordering

[Simon Kuang]

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

-- 
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/2060154

Title:
  Sort by "Modified" uses lexicographic ordering

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  I have opened a folder where the subfolder dates go back a few years.

  Expect 16 Feb 2024 <  9 Feb 2024
  Actual 9 Feb 2024 <  16 Feb 2024

  It seems that the folders are sorted lexicographically by their date
  string, not chronologically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2060154/+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 2060154] Re: Sort by "Modified" uses lexicographic ordering

[Simon Kuang]

nautilus --version

GNOME nautilus 45.rc

-- 
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/2060154

Title:
  Sort by "Modified" uses lexicographic ordering

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have opened a folder where the subfolder dates go back a few years.

  Expect 16 Feb 2024 <  9 Feb 2024
  Actual 9 Feb 2024 <  16 Feb 2024

  It seems that the folders are sorted lexicographically by their date
  string, not chronologically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2060154/+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 2060154] [NEW] Sort by "Modified" uses lexicographic ordering

[Simon Kuang]

Public bug reported:

I have opened a folder where the subfolder dates go back a few years.

Expect 16 Feb 2024 <  9 Feb 2024
Actual 9 Feb 2024 <  16 Feb 2024

It seems that the folders are sorted lexicographically by their date
string, not chronologically.

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

** Attachment added: "Screenshot from 2024-04-03 11-58-15.png"
   
https://bugs.launchpad.net/bugs/2060154/+attachment/5761500/+files/Screenshot%20from%202024-04-03%2011-58-15.png

-- 
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/2060154

Title:
  Sort by "Modified" uses lexicographic ordering

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have opened a folder where the subfolder dates go back a few years.

  Expect 16 Feb 2024 <  9 Feb 2024
  Actual 9 Feb 2024 <  16 Feb 2024

  It seems that the folders are sorted lexicographically by their date
  string, not chronologically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2060154/+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 2059293] [NEW] autopkgtests fail on i386 on the new testsuite

[Simon Chopin]

Public bug reported:

The autopkgtests fail on i386 for version 2:1.0.27-1. In the previous
version the test name was "stress" while the failing one is "testsuite",
so presumably this isn't a regression so much as the new testsuite
failing due to i386 being a partial arch.

Relevant parts of the logs:

506s config.status: creating tests/Makefile
506s config.status: executing depfiles commands
506s   CC   stress.o
507s   CC   testlib.o
507s   CCLD stress
507s /usr/bin/ld: cannot find -lusb-1.0: No such file or directory
507s collect2: error: ld returned 1 exit status

** Affects: libusb-1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  autopkgtests fail on i386 on the new testsuite

Status in libusb-1.0 package in Ubuntu:
  New

Bug description:
  The autopkgtests fail on i386 for version 2:1.0.27-1. In the previous
  version the test name was "stress" while the failing one is
  "testsuite", so presumably this isn't a regression so much as the new
  testsuite failing due to i386 being a partial arch.

  Relevant parts of the logs:

  506s config.status: creating tests/Makefile
  506s config.status: executing depfiles commands
  506s   CC   stress.o
  507s   CC   testlib.o
  507s   CCLD stress
  507s /usr/bin/ld: cannot find -lusb-1.0: No such file or directory
  507s collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libusb-1.0/+bug/2059293/+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 2058769] Re: proposed-migration for click 0.5.2-2

[Simon Chopin]

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

** Description changed:

- click 0.5.2-2 is stuck in -proposed.  autopkgtest now fails on armhf,
- and possibly on all archs.
+ click 0.5.2-2 is stuck in -proposed.  autopkgtest now fails on ppc64el,
+ s390x.
  
- armhf binary will be removed from the release pocket.
+ In order to be able to run the tests without all-proposed=1, glib 2.0 is
+ needed, which is why I marked it as affected.
+ 
+ Excerpt of the test logs:
+ 
+ ERROR: test_list_simple 
(click_package.tests.integration.test_list.TestList.test_list_simple)
+ --
+ Traceback (most recent call last):
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py",
 line 29, in test_list_simple
+ self.click_install(path_to_click, name, user)
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py",
 line 99, in click_install
+ subprocess.check_call(cmd)
+   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
+ raise CalledProcessError(retcode, cmd)
+ subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--user=root', '--allow-unauthenticated', 
'/tmp/tmpqhzp18eh/com.ubuntu.verify-ok_1.0_all.click']' returned non-zero exit 
status 1.
+ 
+ ==
+ ERROR: test_debsig_install_valid_signature 
(click_package.tests.integration.test_signatures.TestSignatureVerification.test_debsig_install_valid_signature)
+ --
+ Traceback (most recent call last):
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 207, in test_debsig_install_valid_signature
+ subprocess.check_call(
+   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
+ raise CalledProcessError(retcode, cmd)
+ subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--user=root', '/tmp/tmpymtfsjg9/org.example.debsig-valid-sig_1.0_all.click']' 
returned non-zero exit status 1.
+ 
+ ==
+ ERROR: test_debsig_install_can_install_with_sig_override 
(click_package.tests.integration.test_signatures.TestSignatureVerificationNoSignature.test_debsig_install_can_install_with_sig_override)
+ --
+ Traceback (most recent call last):
+   File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 164, in test_debsig_install_can_install_with_sig_override
+ subprocess.check_call(
+   File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
+ raise CalledProcessError(retcode, cmd)
+ subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--allow-unauthenticated', '--user=root', 
'/tmp/tmpheysy9ze/org.example.debsig-no-sig_1.0_all.click']' returned non-zero 
exit status 1.

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

Title:
  proposed-migration for click 0.5.2-2

Status in click package in Ubuntu:
  New
Status in glib2.0 package in Ubuntu:
  New

Bug description:
  click 0.5.2-2 is stuck in -proposed.  autopkgtest now fails on
  ppc64el, s390x.

  In order to be able to run the tests without all-proposed=1, glib 2.0
  is needed, which is why I marked it as affected.

  Excerpt of the test logs:

  ERROR: test_list_simple 
(click_package.tests.integration.test_list.TestList.test_list_simple)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py",
 line 29, in test_list_simple
  self.click_install(path_to_click, name, user)
File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py",
 line 99, in click_install
  subprocess.check_call(cmd)
File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', 
'--user=root', '--allow-unauthenticated', 
'/tmp/tmpqhzp18eh/com.ubuntu.verify-ok_1.0_all.click']' returned non-zero exit 
status 1.

  ==
  ERROR: test_debsig_install_valid_signature 
(click_package.tests.integration.test_signatures.TestSignatureVerification.test_debsig_install_valid_signature)
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py",
 line 207, in 

[Desktop-packages] [Bug 1798967] Re: bubblewrap has wrong description after setuid bit was removed

[Simon McVittie]

This was fixed in 0.4.1-3 (2021).

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

Title:
  bubblewrap has wrong description after setuid bit was removed

Status in bubblewrap package in Ubuntu:
  Confirmed

Bug description:
  After setuid bit was removed from default installation in cosmic (and
  soon in bionic) the description doesn't match actual behavior anymore:

  "setuid wrapper for unprivileged chroot and namespace manipulation"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1798967/+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 2056561] Re: Libc6 bug in gvfs-udisk

[Simon Chopin]

Unless I'm missing something, the issue you're linking is about glib,
not glibc. Reassigning the bug accordingly.

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

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

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

Title:
  Libc6 bug in gvfs-udisk

Status in glib2.0 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Invalid

Bug description:
  Hi,

  Please see https://gitlab.gnome.org/GNOME/glib/-/issues/3168, which is
  a result of https://gitlab.gnome.org/GNOME/glib/-/issues/3168, which
  is fixed but needs a backport or something.

  Thanks,

  tg

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libc6 2.38-1ubuntu6.1
  ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Fri Mar  8 15:15:39 2024
  Dependencies:
   gcc-13-base 13.2.0-4ubuntu3
   libc6 2.38-1ubuntu6.1
   libgcc-s1 13.2.0-4ubuntu3
   libidn2-0 2.3.4-1
   libunistring2 1.0-2
  InstallationDate: Installed on 2022-12-08 (456 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: glibc
  UpgradeStatus: Upgraded to mantic on 2023-10-01 (159 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2056561/+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 2056196] [NEW] BT headset is disconnected when remotely changing from A2DP to HSP

[Simon Chopin]

Public bug reported:

Release of Ubuntu: Noble
Package Version: 5.72-0ubuntu1

My headset changed profile from A2DP to HSP as I received a phone call on my 
phone (the headset can connect to multiple BT devices).
I'd expect the system to adapt to the new profile (add a new source, change the 
properties of the sink to signal that it's crappy now, etc...), but instead it 
completely disconnected the headset.

I'd assume this line in the logs is the reason:

mars 05 16:01:44 pug bluetoothd[2644]:
src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free
Voice gateway: getpeername: Transport endpoint is not connected (107)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: bluez 5.72-0ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Tue Mar  5 16:03:31 2024
InstallationDate: Installed on 2021-07-05 (974 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. XPS 13 9310
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic 
root=UUID=6bfcd06c-aed1-4da7-949a-dffbf9878bda ro quiet splash 
i915.enable_psr=0 vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to noble on 2024-03-05 (0 days ago)
dmi.bios.date: 12/19/2023
dmi.bios.release: 3.20
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 3.20.0
dmi.board.name: 0DXP1F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr3.20.0:bd12/19/2023:br3.20:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
dmi.product.family: XPS
dmi.product.name: XPS 13 9310
dmi.product.sku: 0991
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 68:54:5A:94:85:F3  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:20697414 acl:97 sco:328138 events:3546 errors:0
TX bytes:21468970 acl:107 sco:327713 commands:3406 errors:0

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


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

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

Title:
  BT headset is disconnected when remotely changing from A2DP to HSP

Status in bluez package in Ubuntu:
  New

Bug description:
  Release of Ubuntu: Noble
  Package Version: 5.72-0ubuntu1

  My headset changed profile from A2DP to HSP as I received a phone call on my 
phone (the headset can connect to multiple BT devices).
  I'd expect the system to adapt to the new profile (add a new source, change 
the properties of the sink to signal that it's crappy now, etc...), but instead 
it completely disconnected the headset.

  I'd assume this line in the logs is the reason:

  mars 05 16:01:44 pug bluetoothd[2644]:
  src/profile.c:ext_io_disconnected() Unable to get io data for Hands-
  Free Voice gateway: getpeername: Transport endpoint is not connected
  (107)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: bluez 5.72-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Tue Mar  5 16:03:31 2024
  InstallationDate: Installed on 2021-07-05 (974 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9310
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic 
root=UUID=6bfcd06c-aed1-4da7-949a-dffbf9878bda ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to noble on 2024-03-05 (0 days ago)
  dmi.bios.date: 12/19/2023
  dmi.bios.release: 3.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.20.0
  dmi.board.name: 0DXP1F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.20.0:bd12/19/2023:br3.20:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:54:5A:94:85:F3  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:20697414 acl:97 sco:328138 events:3546 

[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[Simon Chopin]

We had a mitigation for this in glibc but the latest change from simply
denying the unshare() call to allowing it but then denying anything
requiring capabilities *presumably* broke the glibc test suite again.
I'm only basing this from looking at the test logs, as I'm temporarily
unable to run autopkgtests locally and am lacking the time to fix it.

2 classes of errors:

2770s FAIL: stdlib/tst-system
2770s original exit status 1
2770s error: test-container.c:1136: could not create a private mount namespace

That one is clearly userns-related, as it's due to a failing mount()
call right after unshare()

2770s FAIL: sunrpc/tst-svc_register
2770s original exit status 1
2770s error: xwrite.c:32: write of 12 bytes failed after 0: Operation not 
permitted
2770s error: 1 test failures

I can't tell for sure what this one is about since this is your basic
write() call and I don't have a stack trace at hand, but the EPERM would
suggest that it's related.

I think a first fix would be to amend the test script to disable the
userns restriction entirely for the duration of the tests (using 'needs-
sudo'), while I'll still need to patch the test suite eventually to
handle this new failure mode gracefully and simply ignore the tests,
akin to https://sourceware.org/pipermail/libc-
alpha/2024-February/154754.html

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  In Progress
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Fix Committed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 1961508] Re: Dock displaying over window after resuming from blank screen

[Simon Déziel]

The workaround from #71 worked almost perfectly out of the box, I've
only seen 1-2 windows staying under the dock. I probably simply need
bump the delay a bit from the default value.

Thanks a lot @popov895. @ballogy, thanks for working on this with
upstream!

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-desktop package in Fedora:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

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

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-02-18 (328 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: wayland-session third-party-packages kinetic
  Uname: Linux 5.19.0-28-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 2054879] [NEW] Syntax warnings after upgrade to Python 3.12

[Simon Quigley]

Public bug reported:

Today during regular system updates, I was presented with this
information:

Setting up python3 (3.12.1-0ubuntu1) ...
running python rtupdate hooks for python3.12...
/usr/share/hplip/base/LedmWifi.py:34: SyntaxWarning: invalid escape sequence 
'\d'
  http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/device.py:49: SyntaxWarning: invalid escape sequence '\d'
  http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/g.py:304: SyntaxWarning: invalid escape sequence '\|'
  spinner = "\|/-\|/-"
/usr/share/hplip/base/g.py:354: SyntaxWarning: invalid escape sequence '\d'
  m = re.search('python(\d(\.\d){0,2})', ext_path)#get the python 
version where the .so file is found
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape sequence 
'\#'
  re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape sequence 
'\/'
  re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape sequence 
'\*'
  re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/base/logger.py:439: SyntaxWarning: invalid escape sequence '\<'
  elem_start = re.findall("(\<\W{0,1}\w+) ?", line)[0]
/usr/share/hplip/base/logger.py:440: SyntaxWarning: invalid escape sequence '\]'
  elem_finished = re.findall("([?|\]\]]*\>)", line)[0]
/usr/share/hplip/base/logger.py:442: SyntaxWarning: invalid escape sequence '\S'
  attrs = re.findall("(\S*?\=\".*?\")", line)
/usr/share/hplip/base/models.py:37: SyntaxWarning: invalid escape sequence '\d'
  pat_prod_num = re.compile("""(\d+)""", re.I)
/usr/share/hplip/base/models.py:428: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^r(\d+)-agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:429: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^r(\d+)-agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:430: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^r(\d+)-agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:431: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:432: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-virgin', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:433: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-dvc', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:434: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:435: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:436: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-id', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:437: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-hp-ink', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:438: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-health-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:439: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-health$', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:440: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-known', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:441: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-level', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:442: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-ack', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:443: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:444: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^in-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:445: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^out-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:446: SyntaxWarning: invalid escape sequence '\d'
  re.compile('^model(\d+)', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/password.py:212: SyntaxWarning: invalid escape sequence 
'\['
  cb = cb.replace("[", "\[")
/usr/share/hplip/base/password.py:213: SyntaxWarning: invalid escape sequence 
'\]'
  cb = cb.replace("]", "\]")
/usr/share/hplip/base/queues.py:48: SyntaxWarning: invalid escape sequence '\*'
  NICKNAME_PATTERN = re.compile(b'''\*NickName:\s*\"(.*)"''', re.MULTILINE)
/usr/share/hplip/base/status.py:1335: SyntaxWarning: invalid escape sequence 
'\s'
  pjl_code_pat = re.compile("""^CODE\s*=\s*(\d.*)$""", 

[Desktop-packages] [Bug 2051572] Re: Always preseed core and snapd snap in server seed

[Simon Déziel]

FYI, snapd is a "base-less" snap:

$ lxc launch ubuntu-minimal-daily:22.04 c1
$ lxc shell c1
root@c1:~# snap list
No snaps are installed yet. Try 'snap install hello-world'.
root@c1:~# snap install snapd
2024-02-15T21:17:09Z INFO Waiting for automatic snapd restart...
snapd 2.61.1 from Canonical✓ installed
root@c1:~# snap list
Name   Version  RevTracking   Publisher   Notes
snapd  2.61.1   20671  latest/stable  canonical✓  snapd


This is also visible by not having any `base:` while LXD currently uses core22:

root@c1:~# snap info --verbose snapd | grep base:
root@c1:~# snap info --verbose lxd | grep base:
base:core22

-- 
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/2051572

Title:
  Always preseed core and snapd snap in server seed

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Noble:
  New

Bug description:
  In removing the LXD snap from preseeding in the server seed for Ubuntu
  24.04 as part LP #2051346 [1] we also removed the snapd snap and the
  core22 snap.

  This means that are subsequent snap install, like LXD, will take much
  longer than expected for a non minimized image.

  Time taken to install LXD snap using the lxd-installer package without
  snapd and core22 preinstalled/seeded

  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19

  real  0m29.107s
  user  0m0.006s
  sys   0m0.005s
  ```

  Time taken to install LXD snap using the lxd-installer package with
  snapd and core22 already installed.

  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19

  real  0m15.034s
  user  0m0.005s
  sys   0m0.005s
  ```

  This is a significant difference and for a workload we intend to
  remain as a core tested and tracked workload. As such I propose we re-
  introduce core22 and snapd snaps to our seed.

  LXD do intend to move to the core24 snap as their base as I'm sure
  snapd does too so when that does happen we need to update the
  preseeded core snap.

  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#n69

  [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+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 2020110] Re: Migrate netplan settings to this package

[Simon Quigley]

** Tags added: rls-nn-incoming

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

Title:
  Migrate netplan settings to this package

Status in network-manager package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  The current netplan configuration that specifies Network Manager as
  the renderer comes from a livecd-rootfs hack and results in an
  "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was
  decided at the engineering sprint to migrate this to /lib/netplan
  (with a slightly tweaked filename starting 00- for precedence) owned
  by ubuntu-settings which will ease maintenance (and image builds) in
  future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2020110/+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 2020110] Re: Migrate netplan settings to this package

[Simon Quigley]

Per discussions in the appropriate PR for Calamares[1], this should be
done in network-manager itself.

The appeal is more custom approaches. Downstreams and vendors of Ubuntu.

[1] https://github.com/calamares/calamares/pull/2284

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Migrate netplan settings to this package

Status in network-manager package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  The current netplan configuration that specifies Network Manager as
  the renderer comes from a livecd-rootfs hack and results in an
  "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was
  decided at the engineering sprint to migrate this to /lib/netplan
  (with a slightly tweaked filename starting 00- for precedence) owned
  by ubuntu-settings which will ease maintenance (and image builds) in
  future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2020110/+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 2051572] Re: Always preseed core and snapd snap in server seed

[Simon Déziel]

** Description changed:

  In removing the LXD snap from preseeding in the server seed for Ubuntu
- 24.04 as part LP #2051346 [1] we also removed the snaps snap and the
+ 24.04 as part LP #2051346 [1] we also removed the snapd snap and the
  core22 snap.
  
  This means that are subsequent snap install, like LXD, will take much
  longer than expected for a non minimized image.
  
- 
- Time taken to install LXD snap using the lxd-installer package without snapd 
and core22 preinstalled/seeded
+ Time taken to install LXD snap using the lxd-installer package without
+ snapd and core22 preinstalled/seeded
  
  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19
  
  real  0m29.107s
  user  0m0.006s
  sys   0m0.005s
  ```
  
- 
- Time taken to install LXD snap using the lxd-installer package with snapd and 
core22 already installed.
+ Time taken to install LXD snap using the lxd-installer package with
+ snapd and core22 already installed.
  
  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19
  
  real  0m15.034s
  user  0m0.005s
  sys   0m0.005s
  ```
  
  This is a significant difference and for a workload we intend to remain
  as a core tested and tracked workload. As such I propose we re-introduce
  core22 and snaps snaps to our seed.
  
  LXD do intend to move to the core24 snap as their base as I'm sure snapd
  does too so when that does happen we need to update the preseeded core
  snap.
  
  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#n69
  
- 
  [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346

** Description changed:

  In removing the LXD snap from preseeding in the server seed for Ubuntu
  24.04 as part LP #2051346 [1] we also removed the snapd snap and the
  core22 snap.
  
  This means that are subsequent snap install, like LXD, will take much
  longer than expected for a non minimized image.
  
  Time taken to install LXD snap using the lxd-installer package without
  snapd and core22 preinstalled/seeded
  
  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19
  
  real  0m29.107s
  user  0m0.006s
  sys   0m0.005s
  ```
  
  Time taken to install LXD snap using the lxd-installer package with
  snapd and core22 already installed.
  
  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19
  
  real  0m15.034s
  user  0m0.005s
  sys   0m0.005s
  ```
  
  This is a significant difference and for a workload we intend to remain
  as a core tested and tracked workload. As such I propose we re-introduce
- core22 and snaps snaps to our seed.
+ core22 and snapd snaps to our seed.
  
  LXD do intend to move to the core24 snap as their base as I'm sure snapd
  does too so when that does happen we need to update the preseeded core
  snap.
  
  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#n69
  
  [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346

-- 
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/2051572

Title:
  Always preseed core and snapd snap in server seed

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Noble:
  New

Bug description:
  In removing the LXD snap from preseeding in the server seed for Ubuntu
  24.04 as part LP #2051346 [1] we also removed the snapd snap and the
  core22 snap.

  This means that are subsequent snap install, like LXD, will take much
  longer than expected for a non minimized image.

  Time taken to install LXD snap using the lxd-installer package without
  snapd and core22 preinstalled/seeded

  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19

  real  0m29.107s
  user  0m0.006s
  sys   0m0.005s
  ```

  Time taken to install LXD snap using the lxd-installer package with
  snapd and core22 already installed.

  ```
  ubuntu@cloudimg:~$ time sudo lxd --version
  Installing LXD snap, please be patient.
  5.19

  real  0m15.034s
  user  0m0.005s
  sys   0m0.005s
  ```

  This is a significant difference and for a workload we intend to
  remain as a core tested and tracked workload. As such I propose we re-
  introduce core22 and snapd snaps to our seed.

  LXD do intend to move to the core24 snap as their base as I'm sure
  snapd does too so when that does happen we need to update the
  preseeded core snap.

  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#n69

  [1] 

[Desktop-packages] [Bug 2049895] Re: Distorted mouse pointer in the remote window

[Simon Sadetsky]

With non-factional scale like 100%/200% the issue is not reproducible.

Also, rare after OS restart the pointer is correct, but then there is an
another issue: pointer cannot "touch" the upper edge of the screen so
the autohided top bar does never show up on the remote screen.

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

Title:
  Distorted mouse pointer in the remote window

Status in mutter package in Ubuntu:
  New

Bug description:
  Distorted mouse poitner in the remote window (see the photo attched)

  The bug is reproducable with Wayland only. Whith xorg all works fine
  on the same machine. I experience it more than a year.

  I'm using fraqtional scale 125%.

  $ gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling', 'scale-monitor-framebuffer']

  Video is AMD integrated Radeon 4750G.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-remote-desktop 42.9-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 15:35:25 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-remote-desktop
  UpgradeStatus: Upgraded to jammy on 2022-06-05 (592 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2049895/+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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot

[Simon Chopin]

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

** Changed in: pango1.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  pango1.0: FTBFS against glibc 2.39 snapshot

Status in glibc package in Ubuntu:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Invalid

Bug description:
  Hi,

  The package pango1.0 failed to build during the recent full archive
  test rebuild against a snapshot of the the development branch for the
  upcoming glibc 2.39, expected to land in Noble. This was subsequently
  confirmed locally against a more recent snapshot.

  Full logs for the FTBFS: 
https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz
  Full report: 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html
  PPA with glibc snapshot: 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc

  Snippet showing the failure:

  === 22/27 
  test: test-fonts
  start time:   10:25:39
  duration: 0.11s
  result:   exit status 1
  command:  G_TEST_SRCDIR=/<>/tests 
srcdir=/<>/tests LC_ALL=en_US.UTF-8 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango 
G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k 
--tap
  --- stdout ---
  TAP version 13
  # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d
  1..4
  # Start of fontsets tests
  ok 1 /fontsets/cantarell2
  # Contents don't match expected contents
  # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100
  # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 2 /fontsets/mono2
  ok 3 /fontsets/cantarell
  # Contents don't match expected contents
  # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100
  # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 4 /fontsets/mono
  # End of fontsets tests
  --- stderr ---

  (test program exited with status code 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot

[Simon Chopin]

So, after some fairly exhausting debugging, I kind of gave up on that
bug, but as a last ditch effort I tried a rebuild against the latest
snapshot (even though the changelog didn't seem particularly relevant),
nd... Now it builds.

I'm so tired.

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

Title:
  pango1.0: FTBFS against glibc 2.39 snapshot

Status in glibc package in Ubuntu:
  Triaged
Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Hi,

  The package pango1.0 failed to build during the recent full archive
  test rebuild against a snapshot of the the development branch for the
  upcoming glibc 2.39, expected to land in Noble. This was subsequently
  confirmed locally against a more recent snapshot.

  Full logs for the FTBFS: 
https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz
  Full report: 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html
  PPA with glibc snapshot: 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc

  Snippet showing the failure:

  === 22/27 
  test: test-fonts
  start time:   10:25:39
  duration: 0.11s
  result:   exit status 1
  command:  G_TEST_SRCDIR=/<>/tests 
srcdir=/<>/tests LC_ALL=en_US.UTF-8 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango 
G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k 
--tap
  --- stdout ---
  TAP version 13
  # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d
  1..4
  # Start of fontsets tests
  ok 1 /fontsets/cantarell2
  # Contents don't match expected contents
  # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100
  # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 2 /fontsets/mono2
  ok 3 /fontsets/cantarell
  # Contents don't match expected contents
  # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100
  # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 4 /fontsets/mono
  # End of fontsets tests
  --- stderr ---

  (test program exited with status code 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+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 2049895] [NEW] Distorted mouse poitner in the remote window

[Simon Sadetsky]

Public bug reported:

Distorted mouse poitner in the remote window (see the photo attched)

The bug is reproducable with Wayland only. Whith xorg all works fine on
the same machine. I experience it more than a year.

I'm using fraqtional scale 125%.

$ gsettings get org.gnome.mutter experimental-features
['x11-randr-fractional-scaling', 'scale-monitor-framebuffer']

Video is AMD integrated Radeon 4750G.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-remote-desktop 42.9-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 19 15:35:25 2024
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-remote-desktop
UpgradeStatus: Upgraded to jammy on 2022-06-05 (592 days ago)

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


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

** Attachment added: "bug photo"
   
https://bugs.launchpad.net/bugs/2049895/+attachment/5740761/+files/1705668457716.JPEG

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

Title:
  Distorted mouse poitner in the remote window

Status in gnome-remote-desktop package in Ubuntu:
  New

Bug description:
  Distorted mouse poitner in the remote window (see the photo attched)

  The bug is reproducable with Wayland only. Whith xorg all works fine
  on the same machine. I experience it more than a year.

  I'm using fraqtional scale 125%.

  $ gsettings get org.gnome.mutter experimental-features
  ['x11-randr-fractional-scaling', 'scale-monitor-framebuffer']

  Video is AMD integrated Radeon 4750G.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-remote-desktop 42.9-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 15:35:25 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-remote-desktop
  UpgradeStatus: Upgraded to jammy on 2022-06-05 (592 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2049895/+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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot

[Simon Chopin]

** Changed in: glibc (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: glibc (Ubuntu)
 Assignee: (unassigned) => Simon Chopin (schopin)

** Tags added: foundations-todo

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

Title:
  pango1.0: FTBFS against glibc 2.39 snapshot

Status in glibc package in Ubuntu:
  Triaged
Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Hi,

  The package pango1.0 failed to build during the recent full archive
  test rebuild against a snapshot of the the development branch for the
  upcoming glibc 2.39, expected to land in Noble. This was subsequently
  confirmed locally against a more recent snapshot.

  Full logs for the FTBFS: 
https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz
  Full report: 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html
  PPA with glibc snapshot: 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc

  Snippet showing the failure:

  === 22/27 
  test: test-fonts
  start time:   10:25:39
  duration: 0.11s
  result:   exit status 1
  command:  G_TEST_SRCDIR=/<>/tests 
srcdir=/<>/tests LC_ALL=en_US.UTF-8 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango 
G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k 
--tap
  --- stdout ---
  TAP version 13
  # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d
  1..4
  # Start of fontsets tests
  ok 1 /fontsets/cantarell2
  # Contents don't match expected contents
  # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100
  # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 2 /fontsets/mono2
  ok 3 /fontsets/cantarell
  # Contents don't match expected contents
  # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100
  # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 4 /fontsets/mono
  # End of fontsets tests
  --- stderr ---

  (test program exited with status code 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot

[Simon Chopin]

I'm currently focused on cataloguing failures, but I'll try to
investigate it if nobody has picked it up by then.

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

Title:
  pango1.0: FTBFS against glibc 2.39 snapshot

Status in glibc package in Ubuntu:
  New
Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Hi,

  The package pango1.0 failed to build during the recent full archive
  test rebuild against a snapshot of the the development branch for the
  upcoming glibc 2.39, expected to land in Noble. This was subsequently
  confirmed locally against a more recent snapshot.

  Full logs for the FTBFS: 
https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz
  Full report: 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html
  PPA with glibc snapshot: 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc

  Snippet showing the failure:

  === 22/27 
  test: test-fonts
  start time:   10:25:39
  duration: 0.11s
  result:   exit status 1
  command:  G_TEST_SRCDIR=/<>/tests 
srcdir=/<>/tests LC_ALL=en_US.UTF-8 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango 
G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k 
--tap
  --- stdout ---
  TAP version 13
  # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d
  1..4
  # Start of fontsets tests
  ok 1 /fontsets/cantarell2
  # Contents don't match expected contents
  # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100
  # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 2 /fontsets/mono2
  ok 3 /fontsets/cantarell
  # Contents don't match expected contents
  # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100
  # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 4 /fontsets/mono
  # End of fontsets tests
  --- stderr ---

  (test program exited with status code 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+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 2049881] [NEW] pango1.0: FTBFS against glibc 2.39 snapshot

[Simon Chopin]

Public bug reported:

Hi,

The package pango1.0 failed to build during the recent full archive test
rebuild against a snapshot of the the development branch for the
upcoming glibc 2.39, expected to land in Noble. This was subsequently
confirmed locally against a more recent snapshot.

Full logs for the FTBFS: 
https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz
Full report: 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html
PPA with glibc snapshot: 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc

Snippet showing the failure:

=== 22/27 
test: test-fonts
start time:   10:25:39
duration: 0.11s
result:   exit status 1
command:  G_TEST_SRCDIR=/<>/tests 
srcdir=/<>/tests LC_ALL=en_US.UTF-8 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango 
G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k 
--tap
--- stdout ---
TAP version 13
# random seed: R02Sd064b2e790c11a865b61afd5b0b7909d
1..4
# Start of fontsets tests
ok 1 /fontsets/cantarell2
# Contents don't match expected contents
# --- /tmp/.OQTQH2  2024-01-19 11:25:39.214546169 +0100
# +++ /tmp/.OSTQH2  2024-01-19 11:25:39.214546169 +0100
# @@ -4,7 +4,7 @@
#  DejaVu Sans 20
#  Noto Sans CJK JP 20
#  Droid Sans Japanese 20
# -Cantarell 20
# +Cantarell 20 @wght=400
#  Amiri 20
#  DejaVu Sans Bold 20
#  Font Awesome 5 Free Solid Heavy 20
#
not ok 2 /fontsets/mono2
ok 3 /fontsets/cantarell
# Contents don't match expected contents
# --- /tmp/.X3URH2  2024-01-19 11:25:39.234546069 +0100
# +++ /tmp/.FJURH2  2024-01-19 11:25:39.234546069 +0100
# @@ -4,7 +4,7 @@
#  DejaVu Sans 20
#  Noto Sans CJK JP 20
#  Droid Sans Japanese 20
# -Cantarell 20
# +Cantarell 20 @wght=400
#  Amiri 20
#  DejaVu Sans Bold 20
#  Font Awesome 5 Free Solid Heavy 20
#
not ok 4 /fontsets/mono
# End of fontsets tests
--- stderr ---

(test program exited with status code 1)

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

** Affects: pango1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: test-rebuild-glibc-noble

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

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

Title:
  pango1.0: FTBFS against glibc 2.39 snapshot

Status in glibc package in Ubuntu:
  New
Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Hi,

  The package pango1.0 failed to build during the recent full archive
  test rebuild against a snapshot of the the development branch for the
  upcoming glibc 2.39, expected to land in Noble. This was subsequently
  confirmed locally against a more recent snapshot.

  Full logs for the FTBFS: 
https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz
  Full report: 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html
  PPA with glibc snapshot: 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc

  Snippet showing the failure:

  === 22/27 
  test: test-fonts
  start time:   10:25:39
  duration: 0.11s
  result:   exit status 1
  command:  G_TEST_SRCDIR=/<>/tests 
srcdir=/<>/tests LC_ALL=en_US.UTF-8 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango 
G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k 
--tap
  --- stdout ---
  TAP version 13
  # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d
  1..4
  # Start of fontsets tests
  ok 1 /fontsets/cantarell2
  # Contents don't match expected contents
  # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100
  # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 2 /fontsets/mono2
  ok 3 /fontsets/cantarell
  # Contents don't match expected contents
  # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100
  # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100
  # 

[Desktop-packages] [Bug 2047780] Re: BlueZ release 5.71

[Simon Quigley]

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

** Summary changed:

- BlueZ release 5.71
+ BlueZ release 5.71 and merge from Debian

** Changed in: bluez (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Simon Quigley (tsimonq2)

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

Title:
  BlueZ release 5.71 and merge from Debian

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration

[Simon Quigley]

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

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

** Changed in: lxqt-session (Ubuntu)
   Importance: Undecided => High

** Changed in: lxqt-session (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

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

Title:
  Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to
  Yaru and preventing flavors from overriding it with XDG configuration

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in lxqt-session package in Ubuntu:
  In Progress

Bug description:
  Lubuntu uses Qt as the primary framework for most of the apps we ship.
  However, some functionality we ship in Lubuntu doesn't have a Qt
  application that provides that functionality, so we have some GTK3
  apps that we ship as well. Starting in Lubuntu 24.04, we are adding
  and enabling the breeze-gtk-theme package, providing more uniform
  theming between Qt and GTK apps on Lubuntu. However, this bug makes
  this impossible.

  As we do not ship xsettingsd, but instead use the XDG specification
  for shipping configuration, we are attempting to place the default
  configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg-
  Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini.
  This solutions works for GTK2 apps, however GTK3 apps silently ignore
  the vendored configuration file and are using a different theme.

  As it turns out, this is because the /etc directory is given higher
  priority than /etc/xdg/xdg-Lubuntu when searching for XDG
  configuration files, and as it happens, libgtk-3-0 ships a
  /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme.
  GTK3 applications end up selecting this configuration file rather than
  /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini.

  /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's
  settings.ini file should go, as it makes it difficult for flavors who
  rely on XDG configuration to override it without risking a file
  conflict. (Technically I guess a flavor package *could* use dpkg-
  divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but
  that seems like the wrong way to approach this.)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libgtk-3-0 3.24.38-5ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Fri Dec 29 10:08:23 2023
  InstallationDate: Installed on 2023-10-22 (69 days ago)
  InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+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 2047008] Re: [SRU] Add Telit FN990 compositions

[Simon Quigley]

Uploaded with a changelog tweak. It looks like there is precedent for
this, but it's in the SRU team's hands now.

DEP-3 patch headers next time? ;)

** Also affects: modemmanager (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: modemmanager (Ubuntu Jammy)
 Assignee: (unassigned) => Laider Lai (laiderlai)

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

Title:
  [SRU] Add Telit FN990 compositions

Status in OEM Priority Project:
  New
Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Jammy:
  In Progress

Bug description:
  [SRU] Add Telit FN990 compositions

  [ Impact ]

  The modemmanager v1.20.0 doesn't have Telit FN990 compositions.
  It works with compatibility mode.
  (lp: #2046699)

  [ Test Plan ]

  Under Jammy environment,
  check modemmanager can identify Telit FN990 modem correctly.

  [ Where problems could occur ]

  The Telit FN990 compositions is upstreamed to modemmanager v1.20.6
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2

  Noble and Mantic already working with modemmanager v1.20.6.
  The target platform modem function works well on Mantic.

  The change parts just only add VID/PIDs for Telit's FN990 modems under
  the Telit plugin.

  [ Other Info ]

  N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2047008/+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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

[Simon Quigley]

** Changed in: lubuntu-update-notifier (Ubuntu)
   Importance: Undecided => Medium

** Changed in: lubuntu-update-notifier (Ubuntu)
   Status: New => Confirmed

** Changed in: lubuntu-update-notifier (Ubuntu)
Milestone: None => ubuntu-24.04-feature-freeze

** Changed in: lubuntu-update-notifier (Ubuntu)
 Assignee: (unassigned) => Aaron Rainbolt (arraybolt3)

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in lubuntu-update-notifier package in Ubuntu:
  Confirmed
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in oem-config package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 2019940] Re: Directly manipulating NetworkManager keyfiles

[Simon Quigley]

I patched this upstream in Calamares a month or two ago, and it made it
into the 3.3.0 tag, which Lubuntu now has.

Calamares will support both, it just now *also* supports Netplan. (If
the NM config doesn't exist, no harm no foul no error.)

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

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

** Changed in: calamares (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: calamares (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

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

Title:
  Directly manipulating NetworkManager keyfiles

Status in augeas package in Ubuntu:
  New
Status in calamares package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Invalid
Status in cruft package in Ubuntu:
  Won't Fix
Status in cruft-ng package in Ubuntu:
  Fix Released
Status in dracut package in Ubuntu:
  New
Status in forensic-artifacts package in Ubuntu:
  New
Status in guestfs-tools package in Ubuntu:
  New
Status in guix package in Ubuntu:
  New
Status in ltsp package in Ubuntu:
  Invalid
Status in netcfg package in Ubuntu:
  Won't Fix
Status in netplan.io package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  New
Status in refpolicy package in Ubuntu:
  New
Status in sosreport package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  New
Status in uhd package in Ubuntu:
  New
Status in vagrant package in Ubuntu:
  New

Bug description:
  The affected packages can manipulate NetworkManager keyfiles directly
  on disk, which might not be appropriate anymore on Ubuntu, since the
  Netplan integration was enabled in NetworkManager (starting with
  Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 2046944] Re: Sync wireplumber 0.4.17-1 (main) from Debian testing (main)

[Simon Quigley]

$ syncpackage -f -b 2046944 -s daissi wireplumber
Source wireplumber -> noble/Proposed: current version 0.4.14-4ubuntu1, new 
version 0.4.17-1
Downloading wireplumber_0.4.17-1.dsc from deb.debian.org (0.003 MiB)
[=>]100%
Downloading wireplumber_0.4.14-4ubuntu1.dsc from archive.ubuntu.com (0.003 MiB)
[=>]100%
Downloading changelog from launchpadlibrarian.net (0.010 MiB)
[=>]100%
New changes:
wireplumber (0.4.17-1) unstable; urgency=medium

  * New upstream version

 -- Dylan Aïssi   Mon, 04 Dec 2023 10:18:53 +0100

wireplumber (0.4.16-1) unstable; urgency=medium

  [ Dylan Aïssi ]
  * New upstream version
  * Drop patch included in upstream release:
  - policy-dsp: add ability to hide parent nodes
  * Bump minimum pipewire to 0.3.68
  * Update symbols file

  [ Andreas Henriksson ]
  * Use ${gir:Depends} and ${gir:Provides}

 -- Dylan Aïssi   Wed, 22 Nov 2023 17:59:06 +0100

wireplumber (0.4.15-2) unstable; urgency=medium

  * Team upload.
  * Cherry-pick upstream patch for ability to hide parent nodes

 -- Andreas Henriksson   Mon, 13 Nov 2023 18:14:25
+0100

wireplumber (0.4.15-1) unstable; urgency=medium

  [ Dylan Aïssi ]
  * New upstream version
  * Install zsh completions file


  * Update symbols file 





  [ Lena Voytek ]
  * d/control: Upgrade lua build dependency to 5.4

 -- Dylan Aïssi   Fri, 13 Oct 2023 12:06:12 +0200
Sponsoring this sync for Dylan Aïssi (daissi)
Sync this package [y|N]? y
Request succeeded; you should get an e-mail once it is processed.
Launchpad bugs to be closed: 2046944
Please wait for the sync to be successful before closing bugs.
Close bugs [Y|n]?

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

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

Title:
  Sync wireplumber 0.4.17-1 (main) from Debian testing (main)

Status in wireplumber package in Ubuntu:
  Fix Released

Bug description:
  Please sync wireplumber 0.4.17-1 from Debian.

  The Ubuntu delta was merged in Debian:

  wireplumber (0.4.17-1) unstable; urgency=medium

* New upstream version

   -- Dylan Aïssi   Mon, 04 Dec 2023 10:18:53 +0100

  wireplumber (0.4.16-1) unstable; urgency=medium

[ Dylan Aïssi ]
* New upstream version
* Drop patch included in upstream release:
- policy-dsp: add ability to hide parent nodes
* Bump minimum pipewire to 0.3.68
* Update symbols file

[ Andreas Henriksson ]
* Use ${gir:Depends} and ${gir:Provides}

   -- Dylan Aïssi   Wed, 22 Nov 2023 17:59:06 +0100

  wireplumber (0.4.15-2) unstable; urgency=medium

* Team upload.
* Cherry-pick upstream patch for ability to hide parent nodes

   -- Andreas Henriksson   Mon, 13 Nov 2023 18:14:25
  +0100

  wireplumber (0.4.15-1) unstable; urgency=medium

[ Dylan Aïssi ]
* New upstream version
* Install zsh completions file
* Update symbols file

[ Lena Voytek ]
* d/control: Upgrade lua build dependency to 5.4

   -- Dylan Aïssi   Fri, 13 Oct 2023 12:06:12 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/2046944/+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 1967593] Re: kernel modules going missing after reboot

[Simon Roscic]

I have the same problem, this bug has been around for quite some time as
it seems. Is there no fix available?

I have this problem with multiple machines, but I don't even find any
useful information about the copymods package aside from this bugreport
and the related posts.

-- 
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/1967593

Title:
  kernel modules going missing after reboot

Status in cloud-initramfs-tools package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-lowlatency package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  EDIT: There are no accurate results in the package search, but it is
  for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for
  the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it
  is not kernel specific. It must be a problem with configuration, but
  reinstalling doesnt fix it.

  EDIT2: it turns out this is caused by the cloud-initramfs-copymods
  package mounting over modules locations. Removed it and reinstalled
  kernel modules package (extras didnt seem necessary, but probably
  prudent too).


  This affects several different kernels I've tried in 22.04.

  This post basically sums it up:
  
https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot
  detailed answer: https://unix.stackexchange.com/a/499580/346155

  And this one from upgrading from 20.04 to 22.04:
  
https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade

  Basically, for some reason the kernel modules are being mounted over
  after reboot.

  My image was built on top of a cloud-init image, but removing the recommeded 
package "cloud-initramfs-copymods" that mounts over modules didnt work for me. 
Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules 
did fix my issue for this module. But how many others will not be available?
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill:

  Tags:  jammy uec-images
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago)
  UserGroups: libvirt sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root 

[Desktop-packages] [Bug 2043306] Re: Sync tepl 6.8.0-2 (universe) from Debian unstable (main)

[Simon Quigley]

This bug was fixed in the package tepl - 6.8.0-2
Sponsored for Hans Joachim Desserud (hjd)

---
tepl (6.8.0-2) unstable; urgency=medium

  * Stop using debian/control.in
  * Drop X-Ubuntu-Use-Langpack from debian/control
  * Drop the now unnecessary dh-sequence-gnome from Build-Depends

 -- Amin Bandali   Wed, 08 Nov 2023 16:43:37 +0200

tepl (6.8.0-1) experimental; urgency=medium

  * New upstream release
  * debian/control.in: Add myself to uploaders
  * debian/control.in: Adjust dependencies according to upstream
  * debian/control.in: Update standards version to 4.6.2, no changes needed
  * debian/control.in: Rename library package to match soversion bump
  * debian/libtepl-6-4.symbols: Update symbols following upstream
  * debian/copyright: Bump copyright years and list contributors to
debian/* thus far

 -- Amin Bandali   Wed, 18 Oct 2023 16:05:30 -0400

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

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

Title:
  Sync tepl 6.8.0-2 (universe) from Debian unstable (main)

Status in tepl package in Ubuntu:
  Fix Released

Bug description:
  Please sync tepl 6.8.0-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* No change upload to trigger a translations import on launchpad,
  the template was not correctly set for the new ABI version and the
  existing translations weren't imported in the previous upload
* No change upload to trigger a translations import on launchpad,
  the template was not correctly set for the new ABI version and the
  existing translations weren't imported in the previous upload
* debian/control.in:
  - remove 'X-Ubuntu-Use-Langpack: yes', the template name changed and the
one wasn't accepted on launchpad so the translations are missing from
the langpacks, we aren't going to get a respin of those for lunar so
go back to have the translations included in the deb. Resolve the
issue when some strings in gedit show untranslated (lp: #2016923)
* Rebuild against latest icu
* Rebuild against latest icu

  X-Ubuntu-Use-Langpack was removed from the control file in Debian too
  
https://salsa.debian.org/gnome-team/tepl/-/commit/f550e49edab938302eae6c2bb582b51148935e1d
  And control.in was dropped which is why the above commit only lists changes 
in one file
  
https://salsa.debian.org/gnome-team/tepl/-/commit/50b77ecd10434a97307886aadb20d755b8c3ab54

  
  Changelog entries since current noble version 6.4.0-7ubuntu2:

  tepl (6.8.0-2) unstable; urgency=medium

* Stop using debian/control.in
* Drop X-Ubuntu-Use-Langpack from debian/control
* Drop the now unnecessary dh-sequence-gnome from Build-Depends

   -- Amin Bandali   Wed, 08 Nov 2023 16:43:37 +0200

  tepl (6.8.0-1) experimental; urgency=medium

* New upstream release
* debian/control.in: Add myself to uploaders
* debian/control.in: Adjust dependencies according to upstream
* debian/control.in: Update standards version to 4.6.2, no changes needed
* debian/control.in: Rename library package to match soversion bump
* debian/libtepl-6-4.symbols: Update symbols following upstream
* debian/copyright: Bump copyright years and list contributors to
  debian/* thus far

   -- Amin Bandali   Wed, 18 Oct 2023 16:05:30 -0400

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tepl/+bug/2043306/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead

[Simon Engelsman]

Hello,

The priority of manic-proposed is lower (100) than mantic (500). You can
override it in `/etc/apt/preferences.d`, see
`/usr/share/doc/apt/examples` or manually install the package you want
from mantic-proposed:

```
apt-get install gnome-shell-extension-ubuntu-dock=87ubuntu2
```

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

Title:
  Meta.Rectangle is deprecated, use Mtk.Rectangle instead

Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-tiling-assistant source package in Mantic:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  The gnome-shell 45.rc log fills with:

  Meta.Rectangle is deprecated, use Mtk.Rectangle instead

  [ Test case ]

  Run ubuntu with ubuntu extensions enabled (only).
  journalctl /usr/bin/gnome-shell should not contain any reference to 
Meta.Rectangle deprecation

  [ Regression potential ]

  Introspected types are not defined and so extensions may try to use
  undefined code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2039460] Re: Please merge network-manager-applet 1.34.0-1 from Debian unstable

[Simon Quigley]

By the way...

> Should I always propose the debdiff with the release name instead of
UNRELEASED[...]?

Yes, that's correct. Great question, sorry that I missed it!

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

Title:
  Please merge network-manager-applet 1.34.0-1 from Debian unstable

Status in network-manager-applet package in Ubuntu:
  In Progress

Bug description:
  Builds successfully in Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2039460/+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 2039460] Re: Please merge network-manager-applet 1.34.0-1 from Debian unstable

[Simon Quigley]

This is just a minor note, but "resynchronize" implies a pure sync,
merging is slightly different. Not blocking the sponsorship request.

Sponsoring, thank you!

** Changed in: network-manager-applet (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: network-manager-applet (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

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

Title:
  Please merge network-manager-applet 1.34.0-1 from Debian unstable

Status in network-manager-applet package in Ubuntu:
  In Progress

Bug description:
  Builds successfully in Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2039460/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list

[Simon Chopin]

Hi Dirk,

Thanks for the revised patch. However, it needs to be based on top of
the version currently in -proposed. The archive can't overwrite a
version that's already published, which is basically whenever its
sources hit the -proposed pocket (that happened when Steve accepted the
SRU back in #21).

Unsubscribing ubuntu-sponsors, please resubscribe when you feel the
patch is ready for review :)

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

Title:
  [SRU] Support to install nvidia driver by allowing list

Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Confirmed
Status in ubuntu-drivers-common source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

   * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
  OEM/ODM for production.

  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
  to use a specific nvidia version to development/production.

  NVIDIA and OEN/ODM will announce the next generation combination at
  the same time usually when the factory ready to ship the product.

  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.

  [ Test Plan ]

   * Steps to make sure it works:

  1. pick a cutting edge nvidia graphic.
  2. remove nv-525 from the pool by removing restricted in jammy-updates and 
jammy-security
  3. check the nv support status:
  ```
  $ ubuntu-drivers list
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta
  ```
  4. modify custom file
  ```
  $ cat /etc/custom_supported_gpus.json
  {
    "chips": [
  {
    "devid": "0x24BA",
    "name": "TEST 24BA",
    "branch": "580.1234",
    "features": [
  "runtimepm"
    ]
  },
  {
    "devid": "0x25BC",
    "name": "TEST 25BC",
    "branch": "510",
    "features": [
  "runtimepm"
    ]
  }
    ]
  }
  ```
  5. make sure the hook works
  ```
  $ ubuntu-drivers list
  nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta

  [ Where problems could occur ]

   * This feature only impact target system has a custom file
  "/etc/custom_supported_gpus.json". And it won't generate automatically
  which should not impact normal users

  [ Other Info ]

   * the patches are picked from
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
   * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1989964] Re: Segmentation fault crocus_dri.so (X server dies)

[Simon IJskes]

libgl1-mesa-dri:amd64 23.0.4-0ubuntu1~22.04.1

-- 
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/1989964

Title:
  Segmentation fault crocus_dri.so (X server dies)

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The desktop session is running for 0 or more days. Suddenly the X
  server dies, and login screen reappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Sep 16 14:45:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.release: 2.59
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.59
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.product.sku: C8N27AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1989964/+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 1989964] Re: Segmentation fault crocus_dri.so (X server dies)

[Simon IJskes]

The problem still exists:

 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE)
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) Backtrace:
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 0: 
/usr/lib/xorg/Xorg (?+0x0) [0x5614c77b0939]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 1: 
/lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7faa02b2d520]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 2: 
/lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7faa02c8baf7]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa0040eed2]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa0094570f]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa00f1cbc3]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa0046337b]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa0043568f]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa004390c9]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/crocus_dri.so (?+0x0) [0x7faa0043f899]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 10: 
/usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7faa0236ea53]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 11: 
/usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7faa0235daa1]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 12: 
/usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7faa02368233]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 13: 
/usr/lib/xorg/modules/libglamoregl.so (?+0x0) [0x7faa0236871e]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 14: 
/usr/lib/xorg/Xorg (?+0x0) [0x5614c771d890]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 15: 
/usr/lib/xorg/Xorg (?+0x0) [0x5614c7713b33]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 16: 
/usr/lib/xorg/Xorg (?+0x0) [0x5614c763a4c5]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 17: 
/usr/lib/xorg/Xorg (?+0x0) [0x5614c763e544]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 18: 
/lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7faa02b14d90]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 19: 
/lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7faa02b14e40]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) 20: 
/usr/lib/xorg/Xorg (?+0x0) [0x5614c7627605]
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE)
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) Segmentation 
fault at address 0x20
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE)
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: Fatal server error:
 Aug 29 18:35:21 titan /usr/libexec/gdm-x-session[582536]: (EE) Caught signal 
11 (Segmentation fault). Server aborting

-- 
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/1989964

Title:
  Segmentation fault crocus_dri.so (X server dies)

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The desktop session is running for 0 or more days. Suddenly the X
  server dies, and login screen reappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Sep 16 14:45:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.release: 2.59
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.59
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: 

[Desktop-packages] [Bug 1989964] Re: Segmentation fault crocus_dri.so (X server dies)

[Simon IJskes]

@oibaf, read your request. unfort i just started rebuilding my profile
from scratch. i'm in the process of re-adding all the applets, and other
X stuff. will keep you posted.

-- 
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/1989964

Title:
  Segmentation fault crocus_dri.so (X server dies)

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The desktop session is running for 0 or more days. Suddenly the X
  server dies, and login screen reappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Sep 16 14:45:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.release: 2.59
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.59
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.product.sku: C8N27AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1989964/+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 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy

[Simon Quigley]

Ah, right. Debootstrap is more low-level, thanks.

-- 
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/2028769

Title:
  [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal
  in Jammy

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  [ Impact ]

  Without packages ubuntu-desktop, ubuntu-desktop-minimal it is
  unnecessarily difficult to setup the Ubuntu desktop on systems like
  the SiFive HiFive Unmatched.

  All dependent packages are available.

  We just need to add the riscv64 architecture in debian/control.

  [ Test Plan ]

  Reproducing the issue:

  * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are
  not available for riscv64 in the archive.

  Testing:

  * Install Ubuntu Jammy using the live installer on the SiFive HiFive 
Unmatched board.
  * Install package ubuntu-desktop-minimal.
  * Install package ubuntu-desktop.
  * Reboot
  * Login
  * Check that you have a function desktop by opening a preinstalled 
application.

  [ Where problems could occur ]

  * The packages might not be installable due to missing dependencies.
  * The Gnome desktop might fail.

  [ Other Info ]
   
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+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 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy

[Simon Quigley]

I'm just generally curious, does debootstrap function differently
with/without this patch?

I'd imagine it either goes off the task, or a level lower than the
metapackages.

-- 
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/2028769

Title:
  [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal
  in Jammy

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  [ Impact ]

  Without packages ubuntu-desktop, ubuntu-desktop-minimal it is
  unnecessarily difficult to setup the Ubuntu desktop on systems like
  the SiFive HiFive Unmatched.

  All dependent packages are available.

  We just need to add the riscv64 architecture in debian/control.

  [ Test Plan ]

  Reproducing the issue:

  * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are
  not available for riscv64 in the archive.

  Testing:

  * Install Ubuntu Jammy using the live installer on the SiFive HiFive 
Unmatched board.
  * Install package ubuntu-desktop-minimal.
  * Install package ubuntu-desktop.
  * Reboot
  * Login
  * Check that you have a function desktop by opening a preinstalled 
application.

  [ Where problems could occur ]

  * The packages might not be installable due to missing dependencies.
  * The Gnome desktop might fail.

  [ Other Info ]
   
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list

[Simon Chopin]

Hi,

Thanks for your contribution. Since Kinetic is going to be skipped and
the Jammy debdiff has been uploaded, I'm unsubscribing ubuntu-sponsors
from this bug. Feel free to re-subscribe the team should the need arise.

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

Title:
  [SRU] Support to install nvidia driver by allowing list

Status in OEM Priority Project:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed
Status in ubuntu-drivers-common source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

   * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
  OEM/ODM for production.

  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
  to use a specific nvidia version to development/production.

  NVIDIA and OEN/ODM will announce the next generation combination at
  the same time usually when the factory ready to ship the product.

  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.

  [ Test Plan ]

   * Steps to make sure it works:

  1. pick a cutting edge nvidia graphic.
  2. remove nv-525 from the pool.
  3. check the nv support status:
  ```
  $ ubuntu-drivers list
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta
  ```
  4. modify custom file
  ```
  $ cat /etc/custom_supported_gpus.json
  {
    "chips": [
  {
    "devid": "0x24BA",
    "name": "TEST 24BA",
    "branch": "580.1234",
    "features": [
  "runtimepm"
    ]
  },
  {
    "devid": "0x25BC",
    "name": "TEST 25BC",
    "branch": "510",
    "features": [
  "runtimepm"
    ]
  }
    ]
  }
  ```
  5. make sure the hook works
  ```
  $ ubuntu-drivers list
  nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta

  [ Where problems could occur ]

   * This feature only impact target system has a custom file
  "/etc/custom_supported_gpus.json". And it won't generate automatically
  which should not impact normal users

  [ Other Info ]

   * the patches are picked from 
 - 
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
 - 
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
 - 
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
 
   * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 2006110] Re: [SRU] Update to latest bugfix release for jammy

[Simon McVittie]

> [flatpak search meld] produces 3,010 spurious identical error messages

That's https://github.com/ximion/appstream/issues/384, which is a
libappstream bug that cannot be fixed by a Flatpak change (as much as we
might like to). I contributed a fix which was included in appstream
0.15.3, so this SRU would incorporate that fix.

** Bug watch added: github.com/ximion/appstream/issues #384
   https://github.com/ximion/appstream/issues/384

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

Title:
  [SRU] Update to latest bugfix release for jammy

Status in Flatpak:
  New
Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  Appstream 0.15.6 is available since December, 2022 and comes with lots
  of crash fixes

  [ Impact ]

   * Appstream is used by GNOME Software, KDE Discover, Flatpak, Snaps
  and probably lot of other components, since the release of Jammy, a
  few point releases have been made to appstream that fixes crashes and
  optimizations.

  [ Test Plan ]

   * Open GNOME Software and KDE Discover and see that it is still
  populatedwith data

  [ Where problems could occur ]

   * GNOME Software and KDE Discover could be affected by a sudden
  crashes but that is unlikely.

  [ Other Info ]
   
   *

To manage notifications about this bug go to:
https://bugs.launchpad.net/flatpak/+bug/2006110/+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 1972654] Re: [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian unstable

[Simon McVittie]

Is this going to happen in 23.10? It seems to have been stalled in
-proposed since May.

After the imminent Debian 12 release (which includes polkit 122), I
intend to start removing legacy polkit 0.105 support, with my goal being
polkitd-pkla no longer existing in Debian 13, and packages no longer
shipping legacy polkitd-pkla configuration in /var/lib.

If Ubuntu still needs this after that point, then you'll have to patch
it back in where necessary.

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

Title:
  [security review] Sync policykit-1 121+compat0.1-5 (main) from Debian
  unstable

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Please sync policykit-1 121+compat0.1-5 (main) from Debian unstable
  for Ubuntu 23.04

  Changelog entries since current kinetic version 0.105-33:
  
https://metadata.ftp-master.debian.org/changelogs/main/p/policykit-1/policykit-1_121%2Bcompat0.1-4_changelog

  In particular, see the 0.120-4 changelog entry.

  I am filing a bug for Security Team review.
  Previously, Debian and Ubuntu developers agreed to keep using
  the last version of policykit before it switched to using JavaScript rules.

  But that was years ago. I believe Debian & Ubuntu are the only distros
  to have opted out of the new policykit. It is harder to maintain
  the old style rules when upstream rules use the new format. And it is
  a challenge to backport security and other bugfixes from the new
  series, without making mistakes or missing important details.

  There was a proposal to use duktape instead of mozjs for the JavaScript
  interpreter but I don't think that's been merged yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 2010561] Re: The Netplan Everywhere NetworkManager fails to supply Netplan with networking information until a connection is deleted and re-created

[Simon Déziel]

@slyon I saw that https://git.launchpad.net/network-
manager/commit/?h=netplan/lunar-
gu=900b2e15bce37363b263a224e60674f804114693 requires the `file`
package to be available. Some systems don't have installed, albeit
probably not common on desktops but I though I'd mention just in case.

That same commit also seem to have a bogus error handling if `nm-online
-qs` fails:

```
nm-online -qs || (echo "SKIP: NetworkManager is not ready ..." 1>&2 && continue)
```

The `continue` will be run in the `()` subshell. I think this could be
fixed by using `{}` instead.

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

Title:
  The Netplan Everywhere NetworkManager fails to supply Netplan with
  networking information until a connection is deleted and re-created

Status in netplan:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  1. Install Ubuntu Lunar or a flavor thereof onto physical hardware with a 
WiFi adapter. (I used Lubuntu Lunar.)
  2. Connect to WiFi and install all updates.
  3. Enable the Netplan Everywhere PPA and install the updated NetworkManager 
from it (further details at 
https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-settings/32420?u=arraybolt3)
  4. When the installation finishes, run "sudo netplan get".

  Expected result: Networking information related to the WiFi connection
  should appear in the "sudo netplan get" output.

  Actual result: "sudo netplan get" returns the following:

  ** (process:4088): WARNING **: 12:41:41.394; Permissions for 
/etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration 
should NOT be accessible by others.
  network:
    version: 2
    renderer: NetworkManager

  End of output. Additionally, the /etc/netplan folder does not contain
  files that I would expect to be there that would contain the
  networking info.

  Additional information:

  If I disconnect from WiFi, then delete my WiFi connection entirely in
  nmtui, and *then* reconnect to the same WiFi network, "sudo netplan
  get" returns the expected networking information. /etc/netplan is also
  properly populated after doing this.

  This bug seems like it will probably cause unintended behavior after
  an upgrade from 23.04 (which uses normal NetworkManager) to 23.10
  (which is supposed to be using the Netplan Everywhere NetworkManager).
  People probably won't know to entirely delete the WiFi and other
  connections and then reconnect them in order for the netplan output to
  be usable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2010561/+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 2018583] Re: evince does not store setting "Select page size using document page size"

[Simon IJskes]

** Description changed:

+ Version: 42.3-0ubuntu3
+ 
  evince does not store setting "Select page size using document page
  size".
  
  the setting is overwritten by the setting "Draw border around pages"
  
  fix:
  
  diff -r evince-42.3/libview/ev-print-operation.c 
evince-42.3-patched/libview/ev-print-operation.c
  2778c2778
  < gtk_print_settings_set_bool (settings, EV_PRINT_SETTING_PAGE_SIZE, 
print->draw_borders);
  ---
  > gtk_print_settings_set_bool (settings, EV_PRINT_SETTING_DRAW_BORDERS, 
print->draw_borders);

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

Title:
  evince does not store setting "Select page size using document page
  size"

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Version: 42.3-0ubuntu3

  evince does not store setting "Select page size using document page
  size".

  the setting is overwritten by the setting "Draw border around pages"

  fix:

  diff -r evince-42.3/libview/ev-print-operation.c 
evince-42.3-patched/libview/ev-print-operation.c
  2778c2778
  < gtk_print_settings_set_bool (settings, EV_PRINT_SETTING_PAGE_SIZE, 
print->draw_borders);
  ---
  > gtk_print_settings_set_bool (settings, EV_PRINT_SETTING_DRAW_BORDERS, 
print->draw_borders);

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2018583/+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 2018583] [NEW] evince does not store setting "Select page size using document page size"

[Simon IJskes]

Public bug reported:

evince does not store setting "Select page size using document page
size".

the setting is overwritten by the setting "Draw border around pages"

fix:

diff -r evince-42.3/libview/ev-print-operation.c 
evince-42.3-patched/libview/ev-print-operation.c
2778c2778
<   gtk_print_settings_set_bool (settings, EV_PRINT_SETTING_PAGE_SIZE, 
print->draw_borders);
---
>   gtk_print_settings_set_bool (settings, EV_PRINT_SETTING_DRAW_BORDERS, 
> print->draw_borders);

** Affects: evince (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Package changed: fontconfig (Ubuntu) => evince (Ubuntu)

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

-- 
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/2018583

Title:
  evince does not store setting "Select page size using document page
  size"

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  evince does not store setting "Select page size using document page
  size".

  the setting is overwritten by the setting "Draw border around pages"

  fix:

  diff -r evince-42.3/libview/ev-print-operation.c 
evince-42.3-patched/libview/ev-print-operation.c
  2778c2778
  < gtk_print_settings_set_bool (settings, EV_PRINT_SETTING_PAGE_SIZE, 
print->draw_borders);
  ---
  > gtk_print_settings_set_bool (settings, EV_PRINT_SETTING_DRAW_BORDERS, 
print->draw_borders);

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2018583/+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 2017011] [NEW] [snap] unable to read /proc/pressure/{cpu, io, memory}

[Simon Déziel]

Public bug reported:

During normal operation, chromium wants to read
/proc/pressure/{cpu,io,memory} but is denied by the Apparmor policy:

$ journalctl -b0 -k --grep 'chromium.chromium' | grep -F 'name="/proc/pressure/'
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400 
audit(1681915227.726:817): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=395005 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400 
audit(1681915227.726:818): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=395005 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400 
audit(1681915227.726:819): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=395005 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Note that simply starting the browser doesn't prompt it try and read
those files, you need to do something more involving like watching
Youtube for example.

Additional information:

$ snap list chromium core20
Name  VersionRev   Tracking   Publisher   Notes
chromium  112.0.5615.49  2424  latest/stable  canonical✓  -
core2020230308   1852  latest/stable  canonical✓  base

$ lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04

$ uname -a
Linux sdeziel-lemur 5.19.0-40-generic #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 
Fri Mar 31 16:00:14 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/2017011

Title:
  [snap] unable to read /proc/pressure/{cpu,io,memory}

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  During normal operation, chromium wants to read
  /proc/pressure/{cpu,io,memory} but is denied by the Apparmor policy:

  $ journalctl -b0 -k --grep 'chromium.chromium' | grep -F 
'name="/proc/pressure/'
  Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400 
audit(1681915227.726:817): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=395005 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400 
audit(1681915227.726:818): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/io" pid=395005 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Apr 19 10:40:27 sdeziel-lemur kernel: audit: type=1400 
audit(1681915227.726:819): apparmor="DENIED" operation="open" class="file" 
profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=395005 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  Note that simply starting the browser doesn't prompt it try and read
  those files, you need to do something more involving like watching
  Youtube for example.

  Additional information:

  $ snap list chromium core20
  Name  VersionRev   Tracking   Publisher   Notes
  chromium  112.0.5615.49  2424  latest/stable  canonical✓  -
  core2020230308   1852  latest/stable  canonical✓  base

  $ lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  $ uname -a
  Linux sdeziel-lemur 5.19.0-40-generic #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 
Fri Mar 31 16:00:14 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017011/+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 2007623] Re: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main)

[Simon Quigley]

Sponsored, thank you!

** Changed in: grilo-plugins (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main)

Status in grilo-plugins package in Ubuntu:
  Fix Committed

Bug description:
  Please merge grilo-plugins 0.3.15-2 (universe) from Debian unstable
  (main)

  Changelog entries since current lunar version 0.3.15-1ubuntu1:

  grilo-plugins (0.3.15-2) unstable; urgency=medium

* debian/control:
  - Stop recommending dleyna-server (Closes: #1030125).
  - Update Standards-Version to 4.6.2 (no changes).
* debian/copyright:
  - Update copyright years.

   -- Alberto Garcia   Tue, 31 Jan 2023 16:45:49 +0100

  Remaining differences with grilo-plugins from Debian unstable:

  - Split package into -base and -extra (Closes: #805609)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/2007623/+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 2006110] Re: [SRU] Update to latest bugfix release for jammy

[Simon McVittie]

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

** Package changed: flatpak (Ubuntu) => flatpak

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

Title:
  [SRU] Update to latest bugfix release for jammy

Status in Flatpak:
  New
Status in appstream package in Ubuntu:
  New

Bug description:
  Appstream 0.15.6 is available since December, 2022 and comes with lots
  of crash fixes

  [ Impact ]

   * Appstream is used by GNOME Software, KDE Discover, Flatpak, Snaps
  and probably lot of other components, since the release of Jammy, a
  few point releases have been made to appstream that fixes crashes and
  optimizations.

  [ Test Plan ]

   * Open GNOME Software and KDE Discover and see that it is still
  populatedwith data

  [ Where problems could occur ]

   * GNOME Software and KDE Discover could be affected by a sudden
  crashes but that is unlikely.

  [ Other Info ]
   
   *

To manage notifications about this bug go to:
https://bugs.launchpad.net/flatpak/+bug/2006110/+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 1989964] Re: Segmentation fault crocus_dri.so (X server dies)

[Simon IJskes]

also on libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1

-- 
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/1989964

Title:
  Segmentation fault crocus_dri.so (X server dies)

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The desktop session is running for 0 or more days. Suddenly the X
  server dies, and login screen reappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Sep 16 14:45:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.release: 2.59
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.59
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.product.sku: C8N27AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1989964/+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 2006633] Re: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

[Simon Quigley]

Please remember to mention the bug number in the changelog entry.
Additionally, for stylistic purposes, I changed this:

  * Merge from Debian unstable.  The remaining difference is the change
for ignoring test results on i386 to avoir failure.

To this:

  * Merge from Debian Unstable (LP: #2006633). Remaining changes:
- Don't fail the build on tests error for i386

Otherwise, looks good to me, uploading. Please keep this in mind for a
later upload.

Thanks!

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

Title:
  Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

Status in librsvg package in Ubuntu:
  New

Bug description:
  Please merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

  Changelog entries since current lunar version 2.54.4+dfsg-1ubuntu1:

  librsvg (2.54.5+dfsg-1) unstable; urgency=medium

* New upstream release
* debian/librsvg2-2.docs: NEWS.md -> NEWS

   -- Jeremy Bicha   Thu, 22 Sep 2022 17:00:54 -0400

  Remaining differences with librsvg from Debian unstable:

* Don't fail the build on tests error for i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2006633/+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 2004264] Re: FTBFS against glibc 2.37

[Simon Chopin]

The issue has been fixed upstream just before the final 2.37 release,
thus closing this.

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

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

Title:
  FTBFS against glibc 2.37

Status in GLibC:
  Unknown
Status in libunistring package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  During a mass rebuild of Lunar, the package libunistring failed to
  build against a snapshot of the upcoming glibc 2.37, while building
  fine using 2.36 as present in the archive.

  
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html
  
https://launchpadlibrarian.net/644139079/buildlog_ubuntu-lunar-amd64.libunistring_1.0-2_BUILDING.txt.gz

  I was able to reproduce this when building against my latest snapshot
  (done this morning), published in this PPA:

  https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot/+packages

  The failing tests appear to be test-strncat and test-u8-strncat.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/2004264/+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 2004264] Re: FTBFS against glibc 2.37

[Simon Chopin]

The failure is in a gnulib test. I've bisected it to the following glibc
upstream commit:

https://sourceware.org/git/?p=glibc.git;a=commit;h=642933158e7cf072d873231b1a9bb03291f2b989

The issue has been reported upstream.

** Bug watch added: Sourceware.org Bugzilla #30065
   https://sourceware.org/bugzilla/show_bug.cgi?id=30065

** Also affects: libunistring via
   https://sourceware.org/bugzilla/show_bug.cgi?id=30065
   Importance: Unknown
   Status: Unknown

** Project changed: libunistring => glibc

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

Title:
  FTBFS against glibc 2.37

Status in GLibC:
  Unknown
Status in libunistring package in Ubuntu:
  New

Bug description:
  Hi,

  During a mass rebuild of Lunar, the package libunistring failed to
  build against a snapshot of the upcoming glibc 2.37, while building
  fine using 2.36 as present in the archive.

  
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html
  
https://launchpadlibrarian.net/644139079/buildlog_ubuntu-lunar-amd64.libunistring_1.0-2_BUILDING.txt.gz

  I was able to reproduce this when building against my latest snapshot
  (done this morning), published in this PPA:

  https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot/+packages

  The failing tests appear to be test-strncat and test-u8-strncat.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/2004264/+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 2004264] [NEW] FTBFS against glibc 2.37

[Simon Chopin]

Public bug reported:

Hi,

During a mass rebuild of Lunar, the package libunistring failed to build
against a snapshot of the upcoming glibc 2.37, while building fine using
2.36 as present in the archive.

https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html
https://launchpadlibrarian.net/644139079/buildlog_ubuntu-lunar-amd64.libunistring_1.0-2_BUILDING.txt.gz

I was able to reproduce this when building against my latest snapshot
(done this morning), published in this PPA:

https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot/+packages

The failing tests appear to be test-strncat and test-u8-strncat.

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

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

Title:
  FTBFS against glibc 2.37

Status in libunistring package in Ubuntu:
  New

Bug description:
  Hi,

  During a mass rebuild of Lunar, the package libunistring failed to
  build against a snapshot of the upcoming glibc 2.37, while building
  fine using 2.36 as present in the archive.

  
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html
  
https://launchpadlibrarian.net/644139079/buildlog_ubuntu-lunar-amd64.libunistring_1.0-2_BUILDING.txt.gz

  I was able to reproduce this when building against my latest snapshot
  (done this morning), published in this PPA:

  https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot/+packages

  The failing tests appear to be test-strncat and test-u8-strncat.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/2004264/+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 1993191] Re: apport hook that collects snap's information is outdated

[Simon Quigley]

Uploaded to Lunar, currently in the SRU queue for Kinetic, Jammy, and
Focal. Unsubscribing sponsors.

Thanks for your contributions!

** Changed in: chromium-browser (Ubuntu)
   Status: In Progress => Fix Committed

-- 
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/1993191

Title:
  apport hook that collects snap's information is outdated

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in chromium-browser source package in Focal:
  In Progress
Status in chromium-browser source package in Jammy:
  In Progress
Status in chromium-browser source package in Kinetic:
  In Progress

Bug description:
  
  Impact
  --

  The Apport hook of the Chromium browser is outdated. It collects
  information about core18, but the snap uses core20.

  Moreover, it does not collect information about other interface
  providers.

  Test plan
  -

  1. Install the current chromium-browser.

  2. Generate a report with

apport-bug --save /tmp/c1 chromium-browser
   
  3. Install chromium-browser from proposed.

  4. Generate another report with

apport-bug --save /tmp/c2 chromium-browser

  Note: If the package was built and generated locally, you will need
  APPORT_DISABLE_DISTRO_CHECK=1 in the environment.

  5. Compare the files. The meaningful differences should be in the
  Snap.Info. sections, namely:

- Snap.Info.core18 -> Snap.Info.core20
- {None} -> Snap.Info.cups
- {None} -> Snap.Info.gnome-3-38-2004

  Differences should not be observed in Snap.Info.{chromium,core,gtk-
  common-themes}.

  Regression potential
  

  Being Apport a bug reporting program, an incorrect parsing of the
  SNAP_META file could lead to insertion of unwanted information in the
  report or to suppress the insertion of information about the relevant
  interfaces.

  
  Original report
  ---

  See https://bazaar.launchpad.net/~chromium-team/chromium-
  browser/groovy-stable/view/head:/debian/apport/chromium-
  browser.py#L59.

  It collects information about core18, but the chromium snap was
  rebased on core20 almost a year ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+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 1993191] Re: apport hook that collects snap's information is outdated

[Simon Quigley]

Hi, is this still an issue? If so, could you please fill out the
description as an SRU? (Or explain why it should not be.)

Thanks.

-- 
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/1993191

Title:
  apport hook that collects snap's information is outdated

Status in chromium-browser package in Ubuntu:
  In Progress
Status in chromium-browser source package in Focal:
  In Progress
Status in chromium-browser source package in Jammy:
  In Progress
Status in chromium-browser source package in Kinetic:
  In Progress

Bug description:
  See https://bazaar.launchpad.net/~chromium-team/chromium-
  browser/groovy-stable/view/head:/debian/apport/chromium-
  browser.py#L59.

  It collects information about core18, but the chromium snap was
  rebased on core20 almost a year ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+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 1991022] Re: [FFe] Socket activation

[Simon Quigley]

This package exists in Lunar again and the fix has been released
upstream, marking as Fix Released.

** Changed in: speech-dispatcher (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [FFe] Socket activation

Status in speech-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  [Description]

  Systemd socket activation for Speech Dispatcher.

    - Creates the speech-dispatcher.socket;
    - Modifies the server so that it can detect it was automatically launched 
by that socket activation; and
    - Modifies the Autotools files accordingly.

  [Rationale]

  It's relevance is described in [1], of which I quote the essential
  parts [my notes in brackets]:

  > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle 
it inside of the sandbox, so that each application has its own "private" 
instance of Speech Dispatcher running. This works more or less, but it has the 
downside that speech dispatcher cannot coordinate simultaneous messages from 
multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same 
time, the text reading overlaps.
  >
  > In order to solve this issue, I would really like to give sandboxed apps 
access to the Speech Dispatcher instance of the host.

  And then,

  > The only issue I see is having it auto launch. I think it would
  probably be a good step forward for speech-dispatcher to be auto
  launched by a systemd socket like other daemons already do on demand.
  That way the host speech-dispatcher with it's configuration would be
  used by all snaps,

  [Additional information]

  The changes are already merged upstream[2], but still not released.

  I have built and installed the package in Kinetic and verified that
  spd-say still causes the dispatcher spawn and emits sound. Upstream
  test can also confirm this.

  [1]: https://github.com/brailcom/speechd/issues/335
  [2]: https://github.com/brailcom/speechd/pull/763

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+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 1992101] Re: No sound devices listed in Settings

[Simon Quigley]

** No longer affects: wireplumber (Ubuntu)

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

Title:
  No sound devices listed in Settings

Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire package in Debian:
  Fix Released

Bug description:
  Hi, in ubuntu 22.10 beta, there is no sound (only dummy output device
  is present in Settings->Sound). The systemctl --user status pipewire
  is:

   Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: 
enabled)
   Active: active (running) since Thu 2022-10-06 22:51:13 CEST; 27min ago
  TriggeredBy: ● pipewire.socket
 Main PID: 10075 (pipewire)
Tasks: 2 (limit: 115618)
   Memory: 4.7M
  CPU: 65ms
   CGroup: 
/user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
   └─10075 /usr/bin/pipewire

  Oct 06 22:51:13 testosteron systemd[10061]: Started PipeWire Multimedia 
Service.
  Oct 06 22:51:13 testosteron pipewire[10075]: mod.rt: Can't find xdg-portal: 
(null)
  Oct 06 22:51:13 testosteron pipewire[10075]: mod.rt: found session bus but no 
portal
  Oct 06 22:51:13 testosteron pipewire[10075]: mod.rt: RTKit error: 
org.freedesktop.DBus.Error.AccessDenied
  Oct 06 22:51:13 testosteron pipewire[10075]: mod.rt: could not make thread 
10106 realtime using RTKit: Permission denied

  The installed pipewire packages are:
  ii  gstreamer1.0-pipewire:amd64   0.3.57-1
amd64GStreamer 1.0 plugin for the PipeWire 
multimedia server
  ii  libpipewire-0.3-0:amd64   0.3.57-1
amd64libraries for the PipeWire multimedia server
  ii  libpipewire-0.3-common0.3.57-1
all  libraries for the PipeWire multimedia server - 
common files
  ii  libpipewire-0.3-dev:amd64 0.3.57-1
amd64libraries for the PipeWire multimedia server - 
development
  ii  libpipewire-0.3-modules:amd64 0.3.57-1
amd64libraries for the PipeWire multimedia server - 
modules
  ii  pipewire:amd640.3.57-1
amd64audio and video processing engine multimedia 
server
  ii  pipewire-alsa:amd64   0.3.57-1
amd64PipeWire ALSA plugin
  ii  pipewire-audio-client-libraries   0.3.57-1
all  transitional package for pipewire-alsa and 
pipewire-jack
  ii  pipewire-bin  0.3.57-1
amd64PipeWire multimedia server - programs
  ii  pipewire-jack:amd64   0.3.57-1
amd64PipeWire JACK plugin
  ii  pipewire-media-session0.4.1-4 
amd64example session manager for PipeWire
  ii  pipewire-pulse0.3.57-1
amd64PipeWire PulseAudio daemon
  ii  pipewire-tests0.3.57-1
amd64PipeWire multimedia server - tests and examples
  ii  vlc-plugin-pipewire:amd64 3-2 
amd64PipeWire audio plugins for VLC

  Moreover:
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.57-1
  ProcVersionSignature: Ubuntu 5.19.0-18.18-generic 5.19.7
  Uname: Linux 5.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  6 23:15:59 2022
  EcryptfsInUse: Yes
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-06 (0 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1992101/+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 2003889] Re: Pleae merge wpa 2.10-10 from Debian

[Simon Quigley]

Hi Nathan!

I have no problem with the patch, given the author. That being said, it
would be useful to send this delta up to Debian if at all possible.
Please consider it. :)

Also, it's best not to modify changelog entries that exist in Debian.
I'm dropping this before uploading:

 wpa (2:2.10-9) unstable; urgency=medium

-  [ Sebastien Bacher ]
   * debian/patches/allow-legacy-renegotiation.patch:
-Allow legacy renegotiation to fix PEAP issues with some servers
-(Closes: #1010603, LP: #1962541)
+allow legacy renegotiation to fix PEAP issues with some servers
+(Closes: #1010603)

- -- Andrej Shadura   Thu, 05 May 2022 11:23:33 +0100
+ -- Sebastien Bacher   Thu, 05 May 2022 11:31:26 +0200

Thanks!

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

Title:
  Pleae merge wpa 2.10-10 from Debian

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  I built it successfully in Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+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 2003564] Re: Sync xfonts-scalable 1:1.0.3-1.3 (main) from Debian unstable (main)

[Simon Quigley]

This bug was fixed in the package xfonts-scalable - 1:1.0.3-1.3
Sponsored for Hans Joachim Desserud (hjd)

---
xfonts-scalable (1:1.0.3-1.3) unstable; urgency=medium

  * Non-maintainer upload, incorporating changes from the maintainers'
packaging repository

  [ Julien Cristau ]
  * Remove Cyril and David from Uploaders.
  * Add Vcs-* control fields.
  * Use https URL in debian/watch.

  [ Simon McVittie ]
  * d/control: Update Vcs-* for migration to salsa.debian.org
  * Use recommended debhelper compat level 13 (Closes: #965894)
  * d/rules: Add missing build-arch, build-indep targets (Policy §4.9)
  * d/control: Declare that the build does not require (fake)root

 -- Simon McVittie   Sun, 15 Jan 2023 14:18:32 +

** Changed in: xfonts-scalable (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync xfonts-scalable 1:1.0.3-1.3 (main) from Debian unstable (main)

Status in xfonts-scalable package in Ubuntu:
  Fix Released

Bug description:
  Please sync xfonts-scalable 1:1.0.3-1.3 (main) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Update to dh7 to fix the build
* Update to dh7 to fix the build
* Update to dh7 to fix the build

  Current Ubuntu delta:
  
https://patches.ubuntu.com/x/xfonts-scalable/xfonts-scalable_1:1.0.3-1.2ubuntu1.patch

  Debian has updated debhelper dependency from 5 to 13 now.
  Relevant commit:
  
https://salsa.debian.org/xorg-team/font/xfonts-scalable/-/commit/020b14f4ce6c9add3e4a7d71578771c66547656e
  resulting in curent control file:
  https://tracker.debian.org/media/packages/x/xfonts-scalable/control-11.0.3-1.3

  
  Changelog entries since current lunar version 1:1.0.3-1.2ubuntu1:

  xfonts-scalable (1:1.0.3-1.3) unstable; urgency=medium

* Non-maintainer upload, incorporating changes from the maintainers'
  packaging repository

[ Julien Cristau ]
* Remove Cyril and David from Uploaders.
* Add Vcs-* control fields.
* Use https URL in debian/watch.

    [ Simon McVittie ]
* d/control: Update Vcs-* for migration to salsa.debian.org
* Use recommended debhelper compat level 13 (Closes: #965894)
* d/rules: Add missing build-arch, build-indep targets (Policy §4.9)
* d/control: Declare that the build does not require (fake)root

   -- Simon McVittie   Sun, 15 Jan 2023 14:18:32 +

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfonts-scalable/+bug/2003564/+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 2000175] [NEW] [snap] latest/candidate/hwacc channel cause lots of Apparmor noise

[Simon Déziel]

Public bug reported:

# Issue description

After installing chromium with hwacc (snap refresh chromium --channel
latest/candidate/hwacc) I notice a lot of those new messages in dmesg:

Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 
audit(1671561493.126:3297): apparmor="DENIED" operation="mknod" 
profile="snap.chromium.chromium" name="/etc/igfx_user_feature.txt" pid=515408 
comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 
audit(1671561493.126:3298): apparmor="DENIED" operation="mknod" 
profile="snap.chromium.chromium" name="/etc/igfx_user_feature_next.txt" 
pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000


Those 2 files do not exist in the host's filesystem:

$ ls /etc/igfx_user_feature.txt /etc/igfx_user_feature_next.txt
ls: cannot access '/etc/igfx_user_feature.txt': No such file or directory
ls: cannot access '/etc/igfx_user_feature_next.txt': No such file or directory


# Additional information
$ uname -a
Linux sdeziel-lemur 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04

$ snap list chromium core20 snapd
Name  Version   RevTrackingPublisher   Notes
chromium  107.0.5304.121-hwacc  2224   latest/candidate/…  canonical✓  -
core2020221123  1738   latest/stable   canonical✓  base
snapd 2.57.617883  latest/stable   canonical✓  snapd

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/2000175

Title:
  [snap] latest/candidate/hwacc channel cause lots of Apparmor noise

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  # Issue description

  After installing chromium with hwacc (snap refresh chromium --channel
  latest/candidate/hwacc) I notice a lot of those new messages in dmesg:

  Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 
audit(1671561493.126:3297): apparmor="DENIED" operation="mknod" 
profile="snap.chromium.chromium" name="/etc/igfx_user_feature.txt" pid=515408 
comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  Dec 20 13:38:13 sdeziel-lemur kernel: audit: type=1400 
audit(1671561493.126:3298): apparmor="DENIED" operation="mknod" 
profile="snap.chromium.chromium" name="/etc/igfx_user_feature_next.txt" 
pid=515408 comm="chrome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

  
  Those 2 files do not exist in the host's filesystem:

  $ ls /etc/igfx_user_feature.txt /etc/igfx_user_feature_next.txt
  ls: cannot access '/etc/igfx_user_feature.txt': No such file or directory
  ls: cannot access '/etc/igfx_user_feature_next.txt': No such file or directory

  
  # Additional information
  $ uname -a
  Linux sdeziel-lemur 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  $ snap list chromium core20 snapd
  Name  Version   RevTrackingPublisher   Notes
  chromium  107.0.5304.121-hwacc  2224   latest/candidate/…  canonical✓  -
  core2020221123  1738   latest/stable   canonical✓  base
  snapd 2.57.617883  latest/stable   canonical✓  snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000175/+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 1989964] Re: Segmentation fault crocus_dri.so (X server dies)

[Simon IJskes]

reported upstream:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/7626

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #7626
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/7626

-- 
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/1989964

Title:
  Segmentation fault crocus_dri.so (X server dies)

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The desktop session is running for 0 or more days. Suddenly the X
  server dies, and login screen reappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Sep 16 14:45:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.release: 2.59
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.59
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.product.sku: C8N27AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1989964/+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 1989964] Re: Segmentation fault crocus_dri.so (X server dies)

[Simon IJskes]

is this read/followed by upstream? or should i find upstream myself to
report it?

-- 
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/1989964

Title:
  Segmentation fault crocus_dri.so (X server dies)

Status in mesa package in Ubuntu:
  New

Bug description:
  The desktop session is running for 0 or more days. Suddenly the X
  server dies, and login screen reappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Sep 16 14:45:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.release: 2.59
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.59
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.product.sku: C8N27AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1989964/+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 1993562] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor

[Simon Déziel]

Thanks for the test build Nathan, it works as I no longer see those
denials with the provided snap (chromium 107.0.5304.62). Thanks again!

-- 
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/1993562

Title:
  [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor,
  bios_version, board_name and board_vendor

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  When starting chromium's snap, those messages are logged:

  $ journalctl -o cat -k --grep 'apparmor="DENIED"' | grep -F 
snap.chromium.chromium
  audit: type=1400 audit(1666201583.608:610): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/board_vendor" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  audit: type=1400 audit(1666201583.608:611): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/board_name" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  audit: type=1400 audit(1666201583.608:612): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_vendor" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  audit: type=1400 audit(1666201583.608:613): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_version" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  Chromium behaves OK but generates log pollution.

  Additional info:

  $ snap list chromium snapd
  Name  Version RevTracking   Publisher   Notes
  chromium  106.0.5249.119  2136   latest/stable  canonical✓  -
  snapd 2.57.4  17336  latest/stable  canonical✓  snapd

  $ uname -rm
  5.15.0-52-generic x86_64

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993562/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf

[Simon Brahan]

This bug: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1970047
describes a similar problem.

The following command:

gsettings set org.gnome.desktop.sound input-feedback-sounds false

fixed things for me.

-- 
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/1970148

Title:
  Brave & Chrome browsers freezes on download and print to pdf

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Whenever any file is downloaded, the browser will freeze. Download
  files, from any page does not work. Same issue with Firefox.

  Similarly, the browser will freeze when a page is printed to pdf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1818987] Re: broken symlink to changelog.Debian.gz in chromium-browser

[Simon Déziel]

I just checked 105.0.5195.102-0ubuntu0.18.04.1 and the
changelog.Debian.gz is a file so marking as fix released.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1818987

Title:
  broken symlink to changelog.Debian.gz in chromium-browser

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Related to https://bugs.launchpad.net/ubuntu/+source/cdbs/+bug/194574,
  which has to do with saving space, for some reason, the chromium-
  browser has its changelog symlinked to an optional package.

  Version: 72.0.3626.119-0ubuntu0.18

  Right now, I have chromium-codecs-ffmpeg installed, but the changelog
  links to documentation in chromium-codecs-ffmpeg-extra.

  ```
  $ dpkg -L chromium-browser | grep changelog.Debian
  /usr/share/doc/chromium-browser/changelog.Debian.gz

  $ dpkg -l | grep chromium-
  ii chromium-browser 72.0.3626.119-0ubuntu0.18.04.1 amd64 Chromium web 
browser, open-source version of Chrome
  ii chromium-codecs-ffmpeg 72.0.3626.119-0ubuntu0.18.04.1 amd64 Free ffmpeg 
codecs for the Chromium Browser

  $ ls -l /usr/share/doc/chromium-browser/changelog.Debian.gz
  lrwxrwxrwx 1 root root 51 feb 25 15:56 
/usr/share/doc/chromium-browser/changelog.Debian.gz -> 
../chromium-codecs-ffmpeg-extra/changelog.Debian.gz

  $ ls -l ../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
  ls: cannot access '../chromium-codecs-ffmpeg-extra/changelog.Debian.gz': No 
such file or directory
  ```

  I don't think saving 2k warrants breaking sane access to the changelog:
  ```
  $ ls -l /usr/share/doc/chromium-browser/
  total 1108
  lrwxrwxrwx 1 root root 51 feb 25 15:56 changelog.Debian.gz -> 
../chromium-codecs-ffmpeg-extra/changelog.Debian.gz
  -rw-r--r-- 1 root root 1126239 okt 25 2017 copyright
  -rw-r--r-- 1 root root 2512 okt 25 2017 copyright.problems.gz
  -rw-r--r-- 1 root root 2975 okt 25 2017 README.source

  $ ls -l /usr/share/doc/chromium-codecs-ffmpeg/
  total 1104
  -rw-r--r-- 1 root root 2263 feb 25 15:56 changelog.Debian.gz
  -rw-r--r-- 1 root root 1126239 okt 25 2017 copyright
  ```

  That copyright file takes up actual space but is not symlinked, 
:thinking_face:
  ```
  $ md5sum /usr/share/doc/chromium-{browser,codecs-ffmpeg}/copyright
  983091d3a4c4e207f2146a911a7f7387 /usr/share/doc/chromium-browser/copyright
  983091d3a4c4e207f2146a911a7f7387 
/usr/share/doc/chromium-codecs-ffmpeg/copyright
  ```

  If anything, I would guess that the symlink should be the other way
  around:

  - chromium-codecs-ffmpeg/changelog.Debian.gz symlinked to 
../chromium-browser/changelog.Debian.gz
  - chromium-codecs-ffmpeg-extra/changelog.Debian.gz symlinked to 
../chromium-browser/changelog.Debian.gz

  (And optionally that copyright file as well.)

  Cheers,
  Walter Doekes
  OSSO B.V.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1818987/+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 1993562] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, bios_version, board_name and board_vendor

[Simon Déziel]

** Summary changed:

-  [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, 
board_name and board_vendor
+ [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, 
bios_version, board_name and board_vendor

** Description changed:

  When starting chromium's snap, those messages are logged:
  
  $ journalctl -o cat -k --grep 'apparmor="DENIED"' | grep -F 
snap.chromium.chromium
- audit: type=1400 audit(1666194773.600:424): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/board_name" pid=210441 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
- audit: type=1400 audit(1666194773.600:425): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_vendor" pid=210441 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
- audit: type=1400 audit(1666194773.600:426): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_version" pid=210441 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
- 
+ audit: type=1400 audit(1666201583.608:610): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/board_vendor" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
+ audit: type=1400 audit(1666201583.608:611): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/board_name" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
+ audit: type=1400 audit(1666201583.608:612): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_vendor" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
+ audit: type=1400 audit(1666201583.608:613): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_version" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  
  Chromium behaves OK but generates log pollution.
  
  Additional info:
  
  $ snap list chromium snapd
  Name  Version RevTracking   Publisher   Notes
  chromium  106.0.5249.119  2136   latest/stable  canonical✓  -
  snapd 2.57.4  17336  latest/stable  canonical✓  snapd
  
  $ uname -rm
  5.15.0-52-generic x86_64
  
  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

-- 
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/1993562

Title:
  [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor,
  bios_version, board_name and board_vendor

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When starting chromium's snap, those messages are logged:

  $ journalctl -o cat -k --grep 'apparmor="DENIED"' | grep -F 
snap.chromium.chromium
  audit: type=1400 audit(1666201583.608:610): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/board_vendor" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  audit: type=1400 audit(1666201583.608:611): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/board_name" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  audit: type=1400 audit(1666201583.608:612): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_vendor" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  audit: type=1400 audit(1666201583.608:613): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_version" pid=320950 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  Chromium behaves OK but generates log pollution.

  Additional info:

  $ snap list chromium snapd
  Name  Version RevTracking   Publisher   Notes
  chromium  106.0.5249.119  2136   latest/stable  canonical✓  -
  snapd 2.57.4  17336  latest/stable  canonical✓  snapd

  $ uname -rm
  5.15.0-52-generic x86_64

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993562/+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 1993562] [NEW] [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor, board_name and board_vendor

[Simon Déziel]

Public bug reported:

When starting chromium's snap, those messages are logged:

$ journalctl -o cat -k --grep 'apparmor="DENIED"' | grep -F 
snap.chromium.chromium
audit: type=1400 audit(1666194773.600:424): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/board_name" 
pid=210441 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
audit: type=1400 audit(1666194773.600:425): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/bios_vendor" 
pid=210441 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
audit: type=1400 audit(1666194773.600:426): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_version" pid=210441 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0


Chromium behaves OK but generates log pollution.

Additional info:

$ snap list chromium snapd
Name  Version RevTracking   Publisher   Notes
chromium  106.0.5249.119  2136   latest/stable  canonical✓  -
snapd 2.57.4  17336  latest/stable  canonical✓  snapd

$ uname -rm
5.15.0-52-generic x86_64

$ lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1993562

Title:
   [snap] apparmor denials on /sys/devices/virtual/dmi/id/bios_vendor,
  board_name and board_vendor

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When starting chromium's snap, those messages are logged:

  $ journalctl -o cat -k --grep 'apparmor="DENIED"' | grep -F 
snap.chromium.chromium
  audit: type=1400 audit(1666194773.600:424): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/board_name" pid=210441 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  audit: type=1400 audit(1666194773.600:425): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_vendor" pid=210441 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  audit: type=1400 audit(1666194773.600:426): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/bios_version" pid=210441 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  
  Chromium behaves OK but generates log pollution.

  Additional info:

  $ snap list chromium snapd
  Name  Version RevTracking   Publisher   Notes
  chromium  106.0.5249.119  2136   latest/stable  canonical✓  -
  snapd 2.57.4  17336  latest/stable  canonical✓  snapd

  $ uname -rm
  5.15.0-52-generic x86_64

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993562/+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 1570111] Re: many seccomp denials for set_robust_list in xenial

[Simon Déziel]

Marking as fix released because newer chromium/snapd do not get any
denials for syscall=273 on amd64.

Tested with:

$ snap list snapd chromium
Name  Version RevTracking   Publisher   Notes
chromium  106.0.5249.119  2136   latest/stable  canonical✓  -
snapd 2.57.4  17336  latest/stable  canonical✓  snapd

$ lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04

$ uname -r
5.15.0-52-generic


** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1570111

Title:
  many seccomp denials for set_robust_list in xenial

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  I have 517 messages and counting like this:
  kernel: [ 2899.006553] audit: type=1326 audit(1460584187.442:1256): 
auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=18839 
comm="chromium-browse" exe="/usr/lib/chromium-browser/chromium-browser" sig=0 
arch=c03e syscall=273 compat=0 ip=0x7fa52f21a694 code=0x5

  $ scmp_sys_resolver 273
  set_robust_list

  It seems that chromium's seccomp sandbox needs to enable this call or
  chromium adjusted to not use it.

  $ cat /proc/version_signature
  Ubuntu 4.4.0-18.34-generic 4.4.6

  $ apt-cache policy chromium-browser
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 49.0.2623.108-0ubuntu1.1233
Candidate: 49.0.2623.108-0ubuntu1.1233
Version table:
   *** 49.0.2623.108-0ubuntu1.1233 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1570111/+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 1876442] Re: [snap] chromium causing many audit messages in syslog

[Simon Déziel]

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

Chromium's snap is causing a lot of apparmor/seccomp noise (see other
bugs) but this bug only mentions syscall=203 (sched_setaffinity) which
is now fixed as mentioned in LP: #1900679.

** This bug has been marked a duplicate of bug 1900679
   [snap] Apparmor audit messages for calls to sched_setaffinity

-- 
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/1876442

Title:
  [snap] chromium causing many audit messages in syslog

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  chromium as installed through snap:
  chromium   81.0.4044.129   1135  latest/stable  
canonical✓   -

  $ tail -f /var/log/syslog
  May  2 12:46:20 master3900x kernel: [56493.196311] audit: type=1326 
audit(1588416380.844:3238): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" 
exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5
  May  2 12:46:20 master3900x kernel: [56493.196389] audit: type=1326 
audit(1588416380.844:3239): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" 
exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5
  May  2 12:46:29 master3900x kernel: [56501.999823] audit: type=1326 
audit(1588416389.648:3240): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" 
exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5
  May  2 12:46:29 master3900x kernel: [56501.35] audit: type=1326 
audit(1588416389.648:3241): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" 
exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5
  May  2 12:46:30 master3900x kernel: [56502.993348] audit: type=1326 
audit(1588416390.644:3242): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" 
exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5
  May  2 12:46:30 master3900x kernel: [56502.993410] audit: type=1326 
audit(1588416390.644:3243): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" 
exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5
  May  2 12:46:30 master3900x kernel: [56503.104490] audit: type=1326 
audit(1588416390.752:3244): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" 
exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5
  May  2 12:46:30 master3900x kernel: [56503.104561] audit: type=1326 
audit(1588416390.752:3245): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" 
exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5
  May  2 12:46:34 master3900x kernel: [56506.398229] audit: type=1326 
audit(1588416394.048:3246): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" 
exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5
  May  2 12:46:34 master3900x kernel: [56506.398318] audit: type=1326 
audit(1588416394.048:3247): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" 
exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5
  May  2 12:46:49 master3900x kernel: [56521.357592] audit: type=1326 
audit(1588416409.004:3248): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" 
exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5
  May  2 12:46:49 master3900x kernel: [56521.357678] audit: type=1326 
audit(1588416409.004:3249): auid=4294967295 uid=1000 gid=1000 ses=4294967295 
subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" 
exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7fdf221bdb8f 

[Desktop-packages] [Bug 1900679] Re: [snap] Apparmor audit messages for calls to sched_setaffinity

[Simon Déziel]

I've marked the chromium bug as invalid since snapd now allows
sched_setaffinity with browser-sandbox: true (see comment 16). I checked
here with firefox and chromium (both snaps) and the only syscall=203
denial is unrelated:

$ journalctl -o cat -b-1 -k --grep syscall=203
audit: type=1326 audit(1666098873.038:90): auid=1000 uid=1000 gid=1000 ses=3 
subj=? pid=3817 comm="snapd-desktop-i" 
exe="/snap/snapd-desktop-integration/14/bin/snapd-desktop-integration" sig=0 
arch=c03e syscall=203 compat=0 ip=0x7078b4388741 code=0x5

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1900679

Title:
  [snap] Apparmor audit messages for calls to sched_setaffinity

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  [T okt   20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210734): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210735): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210736): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210737): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210738): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210739): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5

  Things like these just get repeated endlessly and very often, making
  any potential debugging very annoying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+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 1862262] Re: [snap] apparmor denials on /sys/devices/virtual/dmi/id/sys_vendor and product_name

[Simon Déziel]

I can confirm the denials on /sys/devices/virtual/dmi/id/sys_vendor and
product_name are gone now, thanks!

$ snap list snapd
Name   Version  RevTracking   Publisher   Notes
snapd  2.57.4   17336  latest/stable  canonical✓  snapd

** Changed in: chromium-browser (Ubuntu)
   Status: New => Fix Released

-- 
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/1862262

Title:
  [snap] apparmor denials on /sys/devices/virtual/dmi/id/sys_vendor and
  product_name

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  When starting chromium's snap, those messages are logged:

  Feb  6 12:34:17 foo kernel: [106190.836260] audit: type=1400 
audit(1581010457.097:1372): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor" 
pid=20044 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
  Feb  6 12:34:17 foo kernel: [106190.836401] audit: type=1400 
audit(1581010457.097:1373): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" 
name="/sys/devices/virtual/dmi/id/product_name" pid=20044 
comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Feb  6 12:34:17 foo chromium_chromium.desktop[20044]: 
[20191:20191:0206/123417.177438:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.

  Chromium seemingly behaves OK but possibly with reduced sandboxing?

  
  Additional info:

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more 
stable way for all
Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: stable
  refresh-date: yesterday at 17:45 EST
  channels:
stable:80.0.3987.87 2020-02-05 (1016) 160MB -
candidate: 80.0.3987.87 2020-02-05 (1016) 160MB -
beta:  80.0.3987.85 2020-02-04 (1014) 160MB -
edge:  81.0.4040.5  2020-02-06 (1018) 161MB -
  installed:   80.0.3987.87(1016) 160MB -

  $ uname -a
  Linux simon-lemur 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862262/+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 1991761] Re: Backport packages for 22.04.2 HWE stack

[Simon Chopin]

** Tags added: foundations-triage-discuss

-- 
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/1991761

Title:
  Backport packages for 22.04.2 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-15 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  New
Status in libdrm source package in Jammy:
  New
Status in llvm-toolchain-15 source package in Jammy:
  New
Status in mesa source package in Jammy:
  New

Bug description:
  WIP

  directx-headers

  libdrm

  llvm-15

  mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

[Simon Iremonger]

Thunderbird in Ubuntu is now lagging-behind on Security, Debian have released 
102.3.0 as an LTS update, ubuntu version is some versions behind in 91.x ..
https://www.ubuntuupdates.org/ppa/ubuntu_mozilla_security  would suggest 
102.2.2 at least started to be prepared?
Hope this nudge helps =).

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

Title:
  Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in thunderbird source package in Focal:
  Fix Released
Status in thunderbird source package in Hirsute:
  Fix Released

Bug description:
  Similarly to bug #1895643, which was about upgrading thunderbird from
  68 to 78 in all supported Ubuntu releases, this bug is to track the
  update from thunderbird 78 to 91 in hirsute, focal and bionic.

  The rationale is that series 78 will soon be out of support (the last
  release, 78.14.0, was made public on September 7, 2021).

  Thunderbird follows the Firefox ESR release cycle, and the
  next/current series is 91 (already available in impish and jammy).

  User-facing announcement: https://discourse.ubuntu.com/t/thunderbird-
  lts-update-78-to-91/25391.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1949605/+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 1894090] Re: Consolidate thunderbird Ubuntu packaging with Debian for versions >= 78

[Simon Iremonger]

What is now happening, in any case, is Ubuntu LTS Thunderbird packaging
is lagging behind on important security updates.  I think a
consideration of sharing packaging could help this, in my opinion,
unless there is a problem with the arrangement ..  may be key
differences in using separate vs. included libnss and so-on 

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

Title:
  Consolidate thunderbird Ubuntu packaging with Debian for versions >=
  78

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  I suggest consolidating the thunderbird Ubuntu packaging with Debian
  for versions >= 78. Now that the lightning calendar extension is part
  of thunderbird, the thunderbird packaging between Ubuntu and Debian is
  getting closer except for the naming of the locale packages.

  The latest thunderbird version always gets updated in Debian 10
  stable-security and Debian 9 oldstable-security since thunderbird
  follows the Firefox ESR versioning and Debian follows that. Ubuntu
  does a similar thing with its stable LTS releases, and hence could
  benefit from the Debian packaging. And when a new major release of
  Thunderbird is out, it gets updated in Debian unstable/experimental
  then backported to stable and oldstable. A similar thing happens in
  Ubuntu development and stable LTS releases.

  So I suggest a plan like this:
  1. Transition the thunderbird locale packages in Ubuntu to the Debian naming
  2. Merge the latest thunderbird with Debian unstable/experimental to Ubuntu 
development

  If the Debian maintainer agrees, the Ubuntu packaging could also
  happen in Debian salsa similar to what is already happening with GNOME
  packaging.

  I think sharing the thunderbird packaging between Ubuntu and Debian is
  beneficial to both sides going forward in the future, and especially
  if thunderbird packaging gets more complicated to backport to stable
  releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1894090/+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 1989964] Re: Segmentation fault crocus_dri.so (X server dies)

[Simon IJskes]

[335842.604] (WW) glamor: Failed to allocate 128x88 FBO due to GL_OUT_OF_MEMORY.
[335842.604] (WW) glamor: Expect reduced performance.
[335844.555] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glMapBuffer(map failed)

followed by

[335844.561] (EE) glamor0: GL error: GL_INVALID_OPERATION in
glUnmapBuffer(buffer is not mapped)

It looks like a failed allocation is not detected, and an illegal unmap
follows.

>From a distant it looks like an application is exhausting the Xserver
memory, en the Xserver is not robust enough to report these problems to
the application program and stay unaffected.

When it is followed by a segmentation error later it sure looks like
memory corruption, due to not detecting the failure return from
glMapBuffer.

-- 
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/1989964

Title:
  Segmentation fault crocus_dri.so (X server dies)

Status in mesa package in Ubuntu:
  New

Bug description:
  The desktop session is running for 0 or more days. Suddenly the X
  server dies, and login screen reappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Sep 16 14:45:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.release: 2.59
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.59
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.product.sku: C8N27AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1989964/+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 1956950] Re: iwd FTBFS with LTO enabled

[Simon Chopin]

Fixed in https://launchpad.net/ubuntu/+source/iwd/1.30-1ubuntu1

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

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

Title:
  iwd FTBFS with LTO enabled

Status in iwd package in Ubuntu:
  Fix Released
Status in lto-disabled-list package in Ubuntu:
  Fix Released
Status in iwd package in Debian:
  New

Bug description:
  Excerpt from the build log:

  /bin/bash ./libtool  --tag=CC   --mode=link gcc  -fvisibility=hidden 
-DUNITDIR=\""./unit/"\" -DCERTDIR=\""./unit/"\" -DJSMN_PARENT_LINKS 
-DJSMN_STRICT  -g -O2 -ffile-prefix-map=/<>=. -flto=auto 
-ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong 
-Wformat -Werror=format-security  -Wl,-Bsymbolic-functions -flto=auto 
-ffat-lto-objects -flto=auto -Wl,-z,relro -Wl,-z,now -o unit/test-ssid-security 
unit/test-ssid-security.o src/ie.o src/common.o -lell 
  libtool: link: gcc -fvisibility=hidden -DUNITDIR=\"./unit/\" 
-DCERTDIR=\"./unit/\" -DJSMN_PARENT_LINKS -DJSMN_STRICT -g -O2 
-ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z 
-Wl,relro -Wl,-z -Wl,now -o unit/test-ssid-security unit/test-ssid-security.o 
src/ie.o src/common.o  -lell
  /usr/bin/ld: /tmp/ccjo7giz.ltrans0.ltrans.o: in function 
`sae_choose_next_group':
  ./src/sae.c:141: undefined reference to `__wrap_l_ecc_supported_ike_groups'
  /usr/bin/ld: /tmp/ccjo7giz.ltrans0.ltrans.o: in function 
`sae_rx_authenticate':
  ./src/sae.c:183: undefined reference to `__wrap_l_ecc_supported_ike_groups'
  /usr/bin/ld: /tmp/ccjo7giz.ltrans0.ltrans.o: in function 
`handshake_state_free':
  ./src/handshake.c:49: undefined reference to 
`__wrap_l_ecc_supported_ike_groups'
  /usr/bin/ld: /tmp/ccjo7giz.ltrans0.ltrans.o:./src/handshake.c:49: undefined 
reference to `__wrap_l_ecc_supported_ike_groups'
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1956950/+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 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )

[Simon Chopin]

Out of curiosity, would it work if you rename Vidéos into Videos?

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

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

Title:
  Cannot move file to trash, do you want to delete immediately?" on EXT4
  partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on
  ubuntu 20.04 )

Status in glib2.0 package in Ubuntu:
  New
Status in glib2.0 source package in Jammy:
  New

Bug description:
  Hi , when i delete a file where is in another partition than " / " or
  mounted in /media/ , i obtain the message in title.

  how can i use trash again please ?

  iznobe@iznobe-PC:~$ cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # 
 
  # / was on /dev/nvme0n1p2 during installation
  UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e /   ext4
noatime,errors=remount-ro   0   1

  # /boot/efi was on /dev/nvme0n1p1 during installation
  UUID=C071-9050/boot/efi   
vfatdefaults0   0

  # swap was on /dev/sdc3 during installation
  UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap
sw,pri=10   0

  # partition de données separée comune aux OS linux
  UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas  ext4
defaults0   0
  LABEL=WD8 /Vidéos/WD8 ext4
defaults0   0
  #/dev/disk/by-label/WD8PRO2  /media/WD8PRO2 ext4  
  defaults0   0

  LABEL=WD8PRO2   /Vidéos/WD8PRO2
  ext4defaults 0   0

  LABEL=WD8PRO1 /media/WD8PRO1  ext4
defaults0   0
  LABEL=Seagate_4T  /media/Seagate_4T   ext4
defaults,noauto 0   0

  trash is working for filesysteme mounted on /media/WD8PRO1 but not in
  FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS
  .

  Exactly same file systeme mounted on same directory , with same trash
  directory is working fine on ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+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 1990189] Re: brlttty claiming CH341 usbtty device blocking access

[Simon Chopin]

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

** Description changed:

  While this problem seems to have been fixed for FTDI and CP210 based
  devices CH340/CH341 based (and possibly other USB serial adapters) are
  unusable except by brltty.
+ 
+ Workaround: disable brltty
+ sudo systemctl stop brltty-udev.service
+ sudo systemctl mask brltty-udev.service
+ sudo systemctl stop brltty.service
+ sudo systemctl disable brltty.service
  
  [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using 
xhci_hcd
  [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, 
idProduct=7523, bcdDevice= 2.63
  [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0
  [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial
  [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected
  [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0
  [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input24
  [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 
'brltty' sets config #1
  [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected 
from ttyUSB0
  [139100.786136] ch341 1-2.1.2:1.0: device disconnected
  [143917.740171] usb 1-2.1.2: USB disconnect, device number 17
  
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"
  
- ProblemType: Bug
- DistroRelease: Ubuntu 22.04
+ ProblemType: BugDistroRelease: Ubuntu 22.04
  Package: brltty 6.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Sep 19 12:01:21 2022
  InstallationDate: Installed on 2022-08-23 (27 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- SourcePackage: brltty
+  LANGUAGE=en_US
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bashSourcePackage: brltty
  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 brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1990189

Title:
  brlttty claiming CH341 usbtty device blocking access

Status in brltty package in Ubuntu:
  New

Bug description:
  While this problem seems to have been fixed for FTDI and CP210 based
  devices CH340/CH341 based (and possibly other USB serial adapters) are
  unusable except by brltty.

  Workaround: disable brltty
  sudo systemctl stop brltty-udev.service
  sudo systemctl mask brltty-udev.service
  sudo systemctl stop brltty.service
  sudo systemctl disable brltty.service

  [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using 
xhci_hcd
  [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, 
idProduct=7523, bcdDevice= 2.63
  [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0
  [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial
  [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected
  [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0
  [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input24
  [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 
'brltty' sets config #1
  [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected 
from ttyUSB0
  [139100.786136] ch341 1-2.1.2:1.0: device disconnected
  [143917.740171] usb 1-2.1.2: USB disconnect, device number 17

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"

  ProblemType: BugDistroRelease: Ubuntu 22.04
  Package: brltty 6.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Sep 19 12:01:21 2022
  InstallationDate: Installed on 2022-08-23 (27 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+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 1989964] [NEW] Segmentation fault crocus_dri.so (X server dies)

[Simon IJskes]

Public bug reported:

The desktop session is running for 0 or more days. Suddenly the X server
dies, and login screen reappears.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: MATE
Date: Fri Sep 16 14:45:54 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2015
dmi.bios.release: 2.59
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.59
dmi.board.name: 18E4
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP EliteDesk 800 G1 TWR
dmi.product.sku: C8N27AV
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

-- 
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/1989964

Title:
  Segmentation fault crocus_dri.so (X server dies)

Status in mesa package in Ubuntu:
  New

Bug description:
  The desktop session is running for 0 or more days. Suddenly the X
  server dies, and login screen reappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Sep 16 14:45:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.release: 2.59
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.59
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.product.sku: C8N27AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: 

[Desktop-packages] [Bug 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental

[Simon McVittie]

As of version 121+compat0.1-1, the relationship between packages has
changed to this:

* polkitd always requires polkitd-javascript and duktape, and always
interprets JavaScript policies

* polkitd-pkla is now an optional addon (the upstream polkit-pkla-compat
project, as shipped in e.g. Fedora) which evaluates legacy .pkla files
and reports their results via a JavaScript policy

polkitd currently Suggests polkitd-pkla, but this might change to either
a stronger or weaker dependency.

> Get Debian to transition all packages in the archive from PKLA policy
files to JS policy files

I've reported bugs which are collected in .

I do not intend to take further action to modify those packages. If it
is a blocker for Ubuntu that they are fixed, then someone from Ubuntu
will need to do that work.

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

Title:
  [security review] Sync policykit-1 0.120-6 (main) from Debian
  experimental

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Please sync policykit-1 0.120-6 (main) from Debian experimental

  Changelog entries since current kinetic version 0.105-33:
  https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6

  In particular, see the 0.120-4 changelog entry.

  I am filing a bug for Security Team review.
  Previously, Debian and Ubuntu developers agreed to keep using
  the last version of policykit before it switched to using JavaScript rules.

  But that was years ago. I believe Debian & Ubuntu are the only distros
  to have opted out of the new policykit. It is harder to maintain
  the old style rules when upstream rules use the new format. And it is
  a challenge to backport security and other bugfixes from the new
  series, without making mistakes or missing important details.

  There was a proposal to use duktape instead of mozjs for the JavaScript
  interpreter but I don't think that's been merged yet.

  It appears the Debian maintainer is considering switching Debian to the
  updated version in time for the next Debian Stable release (so uploading
  to unstable later this year).

  My requested deadline is August 25, Ubuntu 22.10 Feature Freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1987051] Re: libvpx: merge 1.12.0-1 from Debian unstable

[Simon Chopin]

** Changed in: libvpx (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  libvpx: merge 1.12.0-1 from Debian unstable

Status in libvpx package in Ubuntu:
  Fix Committed

Bug description:
  Merge new upstream version into kinetic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1987051/+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 1987051] [NEW] libvpx: merge 1.12.0-1 from Debian unstable

[Simon Chopin]

Public bug reported:

Merge new upstream version into kinetic.

** Affects: libvpx (Ubuntu)
 Importance: High
 Assignee: Simon Chopin (schopin)
 Status: In Progress

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

Title:
  libvpx: merge 1.12.0-1 from Debian unstable

Status in libvpx package in Ubuntu:
  In Progress

Bug description:
  Merge new upstream version into kinetic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1987051/+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 1983859] Re: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04

[Simon Chopin]

** Also affects: ubuntu-release-upgrader (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: tracker-miners (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04

Status in tracker-miners package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in tracker-miners source package in Focal:
  New
Status in ubuntu-release-upgrader source package in Focal:
  New

Bug description:
  When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often
  (pretty much always) a crash from tracker-extract, as described in the
  following error report:

  https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0

  The crash occurs during the upgrade, which means it's fairly hard to
  investigate exactly what's going on as apport fails to extract a stack
  trace, the binaries being overwritten during the upgrade.

  However, the crash occurs because of a unhandled SIGSYS, meaning a
  seccomp filter issue. I've tried backporting this patch fixing a
  similar issue:

  https://gitlab.gnome.org/GNOME/tracker-
  miners/-/commit/4cda983b02e49f6bd28b94a6b96c9fe7026887ef

  but it doesn't apply, likely due to the code having diverged too much
  since.

  My proposal is thus to disable tracker-extract during upgrade,
  including in all user sessions. I'm assuming that the new version will
  be enabled automatically as its unit file changed name anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1983859/+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 1983859] Re: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04

[Simon Chopin]

** Package changed: tracker (Ubuntu) => tracker-miners (Ubuntu)

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

Title:
  tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04

Status in tracker-miners package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often
  (pretty much always) a crash from tracker-extract, as described in the
  following error report:

  https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0

  The crash occurs during the upgrade, which means it's fairly hard to
  investigate exactly what's going on as apport fails to extract a stack
  trace, the binaries being overwritten during the upgrade.

  However, the crash occurs because of a unhandled SIGSYS, meaning a
  seccomp filter issue. I've tried backporting this patch fixing a
  similar issue:

  https://gitlab.gnome.org/GNOME/tracker-
  miners/-/commit/4cda983b02e49f6bd28b94a6b96c9fe7026887ef

  but it doesn't apply, likely due to the code having diverged too much
  since.

  My proposal is thus to disable tracker-extract during upgrade,
  including in all user sessions. I'm assuming that the new version will
  be enabled automatically as its unit file changed name anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1983859/+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 1983859] [NEW] tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04

[Simon Chopin]

Public bug reported:

When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty
much always) a crash from tracker-extract, as described in the following
error report:

https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0

The crash occurs during the upgrade, which means it's fairly hard to
investigate exactly what's going on as apport fails to extract a stack
trace, the binaries being overwritten during the upgrade.

However, the crash occurs because of a unhandled SIGSYS, meaning a
seccomp filter issue. I've tried backporting this patch fixing a similar
issue:

https://gitlab.gnome.org/GNOME/tracker-
miners/-/commit/4cda983b02e49f6bd28b94a6b96c9fe7026887ef

but it doesn't apply, likely due to the code having diverged too much
since.

My proposal is thus to disable tracker-extract during upgrade, including
in all user sessions. I'm assuming that the new version will be enabled
automatically as its unit file changed name anyway.

** Affects: tracker (Ubuntu)
 Importance: High
 Status: Confirmed

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: fr-2595

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

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

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => High

** Tags added: fr-2595

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

Title:
  tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04

Status in tracker package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often
  (pretty much always) a crash from tracker-extract, as described in the
  following error report:

  https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0

  The crash occurs during the upgrade, which means it's fairly hard to
  investigate exactly what's going on as apport fails to extract a stack
  trace, the binaries being overwritten during the upgrade.

  However, the crash occurs because of a unhandled SIGSYS, meaning a
  seccomp filter issue. I've tried backporting this patch fixing a
  similar issue:

  https://gitlab.gnome.org/GNOME/tracker-
  miners/-/commit/4cda983b02e49f6bd28b94a6b96c9fe7026887ef

  but it doesn't apply, likely due to the code having diverged too much
  since.

  My proposal is thus to disable tracker-extract during upgrade,
  including in all user sessions. I'm assuming that the new version will
  be enabled automatically as its unit file changed name anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1983859/+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 1983502] Re: [snap] seccomp denials for syscall=314 on amd64

[Simon Déziel]

Awesome, thank you Olivier!

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

Title:
  [snap] seccomp denials for syscall=314 on amd64

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  $ snap list thunderbird
  Name VersionRev  Tracking   Publisher   Notes
  thunderbird  102.1.0-2  237  latest/stable  canonical✓  -

  During normal operation, the following is logged:

  Aug 03 12:07:58 foo kernel: audit: type=1326
  audit(1659542878.718:511): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=154377 comm="thunderbird-bin"
  exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e4137c4473d code=0x5

  And something similar when the crash reporter executes:

  Aug 03 12:02:04 foo kernel: audit: type=1326
  audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=150188 comm="crashreporter"
  exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e5f095e773d code=0x5

  
  # Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  $ uname -a
  Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983502/+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 1983502] Re: [snap] seccomp denials for syscall=314 on amd64

[Simon Déziel]

There are quite a few "pending" crash reports and one from the day I
opened this bug so I'd say yes, it's failing to submit them:

sdeziel@sdeziel-lemur:~/snap/thunderbird/common/.thunderbird/Crash 
Reports/pending$ ls -ltr | tail
-rw--- 1 sdeziel sdeziel 2088424 May 27 14:04 
5f6acf74-091e-649d-d405-8f515d115c43.dmp
-rw--- 1 sdeziel sdeziel   11518 May 27 14:04 
5f6acf74-091e-649d-d405-8f515d115c43.extra
-rw--- 1 sdeziel sdeziel 1790080 Jun  2 12:07 
36f475a4-a06d-805a-f37c-3537f767db0d.dmp
-rw--- 1 sdeziel sdeziel   12510 Jun  2 12:07 
36f475a4-a06d-805a-f37c-3537f767db0d.extra
-rw--- 1 sdeziel sdeziel 1752936 Jun 30 09:27 
42252ef9-1b81-6337-f078-a16915f5a550.dmp
-rw--- 1 sdeziel sdeziel8111 Jun 30 09:27 
42252ef9-1b81-6337-f078-a16915f5a550.extra
-rw-rw-r-- 1 sdeziel sdeziel  344429 Jul 26 13:34 
44fcac7c-c079-c1c2-d25b-a421fdc9b60b.dmp
-rw--- 1 sdeziel sdeziel9526 Jul 26 13:34 
44fcac7c-c079-c1c2-d25b-a421fdc9b60b.extra
-rw--- 1 sdeziel sdeziel 1667280 Aug  3 12:02 
09575f30-efa8-4267-8875-7c78e787f556.dmp
-rw--- 1 sdeziel sdeziel   11198 Aug  3 12:02 
09575f30-efa8-4267-8875-7c78e787f556.extra

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

Title:
  [snap] seccomp denials for syscall=314 on amd64

Status in thunderbird package in Ubuntu:
  New

Bug description:
  $ snap list thunderbird
  Name VersionRev  Tracking   Publisher   Notes
  thunderbird  102.1.0-2  237  latest/stable  canonical✓  -

  During normal operation, the following is logged:

  Aug 03 12:07:58 foo kernel: audit: type=1326
  audit(1659542878.718:511): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=154377 comm="thunderbird-bin"
  exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e4137c4473d code=0x5

  And something similar when the crash reporter executes:

  Aug 03 12:02:04 foo kernel: audit: type=1326
  audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=150188 comm="crashreporter"
  exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e5f095e773d code=0x5

  
  # Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  $ uname -a
  Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983502/+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 1983502] Re: [snap] seccomp denials for syscall=314 on amd64

[Simon Déziel]

thunderbird itself seems to be working fine but the crashreport seemed
to have other issues due to Apparmor:

Aug  3 12:02:04 sdeziel-lemur thunderbird_thunderbird.desktop[32515]: 
ExceptionHandler::GenerateDump cloned child 150187
Aug  3 12:02:04 sdeziel-lemur thunderbird_thunderbird.desktop[150187]: 
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Aug  3 12:02:04 sdeziel-lemur thunderbird_thunderbird.desktop[32515]: 
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
Aug  3 12:02:04 sdeziel-lemur kernel: [13893.569377] audit: type=1400 
audit(1659542524.386:509): apparmor="DENIED" operation="open" 
profile="snap.thunderbird.thunderbird" name="/proc/32515/environ" pid=150187 
comm="thunderbird-bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Aug  3 12:02:04 sdeziel-lemur thunderbird_thunderbird.desktop[32711]: Exiting 
due to channel error.
Aug  3 12:02:04 sdeziel-lemur kernel: [13893.827373] audit: type=1326 
audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=? pid=150188 
comm="crashreporter" exe="/snap/thunderbird/237/crashreporter" sig=0 
arch=c03e syscall=314 compat=0 ip=0x7e5f095e773d code=0x5
Aug  3 12:02:07 sdeziel-lemur thunderbird_thunderbird.desktop[150188]: Failed 
to open curl lib from binary, use libcurl.so instead

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

Title:
  [snap] seccomp denials for syscall=314 on amd64

Status in thunderbird package in Ubuntu:
  New

Bug description:
  $ snap list thunderbird
  Name VersionRev  Tracking   Publisher   Notes
  thunderbird  102.1.0-2  237  latest/stable  canonical✓  -

  During normal operation, the following is logged:

  Aug 03 12:07:58 foo kernel: audit: type=1326
  audit(1659542878.718:511): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=154377 comm="thunderbird-bin"
  exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e4137c4473d code=0x5

  And something similar when the crash reporter executes:

  Aug 03 12:02:04 foo kernel: audit: type=1326
  audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=150188 comm="crashreporter"
  exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e5f095e773d code=0x5

  
  # Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  $ uname -a
  Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983502/+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 1491249] Re: Regression: Visual new email notification no longer working in 38.2.0

[Simon Déziel]

This bug was reported against an old Ubuntu release and an old
Thunderbird version. Please try to reproduce with current
Ubuntu/Thunderbird version and open a new bug if needed. Thanks!

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

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

Title:
  Regression: Visual new email notification no longer working in 38.2.0

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  One feature of Thunderbird is a notification through the system
  notification system whenever a new email arrives in the inbox. With
  the recent update to version 38.2 this notification no longer works.
  The "new email" sound plays, but the visual notification is no longer
  displayed.

  This is clearly a regression, since it worked with the previous
  versions of Thunderbird.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: thunderbird 1:38.2.0+build1-0ubuntu0.15.04.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   jan2434 F...m pulseaudio
   /dev/snd/controlC1:  jan2434 F pulseaudio
   /dev/snd/controlC0:  jan2434 F pulseaudio
  BuildID: 20150818212443
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Wed Sep  2 08:35:06 2015
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-01-30 (214 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.30
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-90222358-6460-4247-96c9-9500e2150311
  Plugins: Gnome Shell Integration - 
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
  PrefSources:
   prefs.js
   
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=38.2.0/20150818212443 (In use)
  RelatedPackageVersions: gnome-shell 3.14.4-0ubuntu1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs: bp-90222358-6460-4247-96c9-9500e2150311
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1491249/+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 1983502] [NEW] [snap] seccomp denials for syscall=314 on amd64

[Simon Déziel]

Public bug reported:

$ snap list thunderbird
Name VersionRev  Tracking   Publisher   Notes
thunderbird  102.1.0-2  237  latest/stable  canonical✓  -

During normal operation, the following is logged:

Aug 03 12:07:58 foo kernel: audit: type=1326 audit(1659542878.718:511):
auid=1000 uid=1000 gid=1000 ses=9 subj=? pid=154377 comm="thunderbird-
bin" exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e
syscall=314 compat=0 ip=0x7e4137c4473d code=0x5

And something similar when the crash reporter executes:

Aug 03 12:02:04 foo kernel: audit: type=1326 audit(1659542524.642:510):
auid=1000 uid=1000 gid=1000 ses=9 subj=? pid=150188 comm="crashreporter"
exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e
syscall=314 compat=0 ip=0x7e5f095e773d code=0x5


# Additional information:

$ lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04
$ uname -a
Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

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

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

Title:
  [snap] seccomp denials for syscall=314 on amd64

Status in thunderbird package in Ubuntu:
  New

Bug description:
  $ snap list thunderbird
  Name VersionRev  Tracking   Publisher   Notes
  thunderbird  102.1.0-2  237  latest/stable  canonical✓  -

  During normal operation, the following is logged:

  Aug 03 12:07:58 foo kernel: audit: type=1326
  audit(1659542878.718:511): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=154377 comm="thunderbird-bin"
  exe="/snap/thunderbird/237/thunderbird-bin" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e4137c4473d code=0x5

  And something similar when the crash reporter executes:

  Aug 03 12:02:04 foo kernel: audit: type=1326
  audit(1659542524.642:510): auid=1000 uid=1000 gid=1000 ses=9 subj=?
  pid=150188 comm="crashreporter"
  exe="/snap/thunderbird/237/crashreporter" sig=0 arch=c03e
  syscall=314 compat=0 ip=0x7e5f095e773d code=0x5

  
  # Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  $ uname -a
  Linux foo 5.15.0-43-generic #46~20.04.1-Ubuntu SMP Thu Jul 14 15:20:17 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983502/+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 1959604] Re: [upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp readable to everyone

[Simon Déziel]

Marking as fix released because the upstream bug was closed and the fix
was verified to work in comment 20 (version 91.7.0). Ubuntu currently
ships version 91.11.0.

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

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

Title:
  [upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp
  readable to everyone

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  thunderbird saves opened attachments to /tmp with permissions
  according to umask setting. This was fixed a long time ago with a
  protected folder /tmp/mozilla_${USER}0 and was still working correctly
  as of version 78.14.0+build1-0ubuntu0.20.04.2. The recent update to
  1:91.5.0+build1-0ubuntu0.20.04.1 reintroduced the bug.

  Ubuntu 20.04.3 LTS
  Kernel release:5.13.0-25-generic
  Architecture:  x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959604/+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 1970131] Re: Can't rotate display with AMD graphics on 22.04 LTS

[Simon Iremonger]

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

This bug is fixed by packages now released to jammy-updates (22.04LTS updates):-
xserver-xorg-video-radeon  1:19.1.0-2ubuntu1
xserver-xorg-video-ati 1:19.1.0-2ubuntu1
Due to phasing these may not install immediately on any particular system.

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

Title:
  Can't rotate display with AMD graphics on 22.04 LTS

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using Settings/Display/Orientation/Portret right and Apply then X
  crashes and login screen is displayed. Tested with 3 different AMD
  systems (older). Bug is not present with Intel graphics

  Ubuntu 22.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970131/+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 1970473] Re: [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

[Simon Iremonger]

Versions tested against jammy (retrieved via jammy-proposed updates):-
ii  xserver-xorg-video-ati 1:19.1.0-2ubuntu1 
ii  xserver-xorg-video-radeon 1:19.1.0-2ubuntu1 
Tried these updates alone, tried in combination with other jammy-proposed too.
Tried on previously-crashing radeon system.  Tried on intel system.
All ways tested:-
* rotation works
* 3d applications work
* no other errors/issues apparent to me.

tag -verification-needed-jammy
tag verification-done-jammy

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

Title:
  [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

Status in xserver-xorg-video-ati package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-ati source package in Jammy:
  Fix Committed
Status in xserver-xorg-video-ati package in Debian:
  Fix Released

Bug description:
  * Impact

  The xserver crash, closing the session, when trying to rotate the
  screen when using the ati driver

  * Test case
  - start an xorg based session
  - try to rotate the screen by 90°

  -> the session shouldn't close

  * Regression potential

  if the fix was incorrect it could lead to screen parameters not being
  set correctly. Try changing the resolution and rotation and ensure the
  changes are what is expected

  

  
  When using Settings/Display/Orientation/Portret right and Apply then X 
crashes and login screen is displayed. Tested with 3 different AMD systems 
(older). Bug is not present with Intel graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:30:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ro_RO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2010
  dmi.bios.release: 1.11
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.11
  dmi.board.asset.tag: CZC1332VBJ
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC1332VBJ
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:br1.11:svnHewlett-Packard:pnHPCompaq6005ProMTPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct6:cvr:skuAT493AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq 6005 Pro MT PC
  dmi.product.sku: AT493AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1970473/+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 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

[Simon Chopin]

** Tags added: fr-2537

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

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  New
Status in nettle package in Ubuntu:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+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 1970473] Re: [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

[Simon Iremonger]

I can confirm the same crash happening with 22.04 Xorg and radeon card:-

VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar
[Radeon HD 5000/6000/7350/8350 Series]

... when trying to rotate... which always used to work before e.g. in
20.04LTS.

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

Title:
  [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

Status in xserver-xorg-video-ati package in Ubuntu:
  Confirmed

Bug description:
  When using Settings/Display/Orientation/Portret right and Apply then X
  crashes and login screen is displayed. Tested with 3 different AMD
  systems (older). Bug is not present with Intel graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:30:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ro_RO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2010
  dmi.bios.release: 1.11
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.11
  dmi.board.asset.tag: CZC1332VBJ
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC1332VBJ
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:br1.11:svnHewlett-Packard:pnHPCompaq6005ProMTPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct6:cvr:skuAT493AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq 6005 Pro MT PC
  dmi.product.sku: AT493AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1970473/+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