from:"Jean\-"

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059756

Title:
  [SRU] adsys 0.14.1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059756] [NEW] [SRU] adsys 0.14.1

Public bug reported:

[context]
ADSys is a tool designed for administering and implementing Group Policy 
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of 
services and commands that empower administrators to efficiently manage policy 
updates and maintain compliance with organizational business rules.

Given that ADSys directly interfaces with Active Directory and needs to
align with new business requirements in LTS releases, it has been
essential to keep the package consistently updated with the latest
changes of ADSys upstream source. As ADSys is a key component of our
commercial offerings, our customers anticipate the availability of
recently implemented features in the 22.04 release.

Now that ADSys has a complete set of features, the request is to proceed
with a one-off release of ADSys 0.14.1 to 22.04. Please note that any
new features introduced in subsequent versions will be exclusively
available in 24.04 and later releases.

This version includes a comprehensive end to end automated test suite
that runs ADSys against a real Active directory environment.

[references]
LP: https://launchpad.net/ubuntu/+source/adsys
LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys
GitHub: https://github.com/ubuntu/adsys/
GH Bugs: https://github.com/ubuntu/adsys/issues
Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ 
Initial SRU discussion: 
https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html

[changes]
Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog 
 * New features
   * New policies:
 - Add mount / network shares policy manager
 - Add AppArmor policy manager
 - Support multiple AD backends and implement Winbind support
 - Add system proxy policy manager
 - Add certificate policy manager for machines
 - Add adsysctl policy purge command to purge applied policies
 - Full documentation
 - Full end to end automated test suite.

 * Enhancements
  * Add a --machine / -m flag to adsysctl applied, indicating the policies 
applied to the current machine
  * Expose Ubuntu Pro status in the "status" command
  * Update scripts manager creation
  * List Pro policy types in service status output
  * Warn when Pro-only rules are configured
  * Use systemd via D-Bus instead of systemctl commands
  * Add placeholder notes for entry types
  * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation 
of Kerberos
  * Rework policy application sync strategy
  * Print logs when policies are up to date
  * Update policy definitions to include dconf key for dark mode background
  * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061)
  * Allow sssd backend to work without ad_domain being set (LP: #2054445)
  * Update apport hook to include journal errors and package logs

 * Bug fixes
  * Fix policy update failing when GPT.INI contains no version key
  * Fix object lookup for users having a FQDN as their hostname
  * Support special characters in domains when parsing sssd configuration
  * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf
  * Ensure empty state for dconf policy
  * Handle case mismatches in GPT.INI file name
  * Ensure GPO URLs contain the FQDN of the domain controller
  * Add runtime dependency on nfs-common

 * Other
  * Updates to latest versions of Go (fixing known Go vulnerabilities)
  * Updates to latest versions of the Go dependencies
  * Updates and improvements to CI and QoL
  * Migrate translation support to native approach using go-i18n + gotext and 
switch to upstream gotext version

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059756

Title:
  [SRU] adsys 0.14.1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059756] Re: [SRU] adsys 0.14.1

** Description changed:

  [context]
  ADSys is a tool designed for administering and implementing Group Policy 
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of 
services and commands that empower administrators to efficiently manage policy 
updates and maintain compliance with organizational business rules.
  
  Given that ADSys directly interfaces with Active Directory and needs to
  align with new business requirements in LTS releases, it has been
  essential to keep the package consistently updated with the latest
  changes of ADSys upstream source. As ADSys is a key component of our
  commercial offerings, our customers anticipate the availability of
  recently implemented features in the 22.04 release.
  
  Now that ADSys has a complete set of features, the request is to proceed
  with a one-off release of ADSys 0.14.1 to 22.04. Please note that any
  new features introduced in subsequent versions will be exclusively
  available in 24.04 and later releases.
  
  This version includes a comprehensive end to end automated test suite
  that runs ADSys against a real Active directory environment.
  
+ Version 0.14.1 is available for 22.04 in a PPA and already used in
+ production by customers.
+ 
  [references]
  LP: https://launchpad.net/ubuntu/+source/adsys
  LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys
  GitHub: https://github.com/ubuntu/adsys/
  GH Bugs: https://github.com/ubuntu/adsys/issues
- Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ 
+ Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/
  Initial SRU discussion: 
https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html
  
  [changes]
- Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog 
-  * New features
-* New policies:
-  - Add mount / network shares policy manager
-  - Add AppArmor policy manager
-  - Support multiple AD backends and implement Winbind support
-  - Add system proxy policy manager
-  - Add certificate policy manager for machines
-  - Add adsysctl policy purge command to purge applied policies
-  - Full documentation
-  - Full end to end automated test suite.
+ Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog
+  * New features
+    * New policies:
+  - Add mount / network shares policy manager
+  - Add AppArmor policy manager
+  - Support multiple AD backends and implement Winbind support
+  - Add system proxy policy manager
+  - Add certificate policy manager for machines
+  - Add adsysctl policy purge command to purge applied policies
+  - Full documentation
+  - Full end to end automated test suite.
  
-  * Enhancements
-   * Add a --machine / -m flag to adsysctl applied, indicating the policies 
applied to the current machine
-   * Expose Ubuntu Pro status in the "status" command
-   * Update scripts manager creation
-   * List Pro policy types in service status output
-   * Warn when Pro-only rules are configured
-   * Use systemd via D-Bus instead of systemctl commands
-   * Add placeholder notes for entry types
-   * Rework Kerberos ticket handling logic to satisfy the Heimdal 
implementation of Kerberos
-   * Rework policy application sync strategy
-   * Print logs when policies are up to date
-   * Update policy definitions to include dconf key for dark mode background
-   * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061)
-   * Allow sssd backend to work without ad_domain being set (LP: #2054445)
-   * Update apport hook to include journal errors and package logs
+  * Enhancements
+   * Add a --machine / -m flag to adsysctl applied, indicating the policies 
applied to the current machine
+   * Expose Ubuntu Pro status in the "status" command
+   * Update scripts manager creation
+   * List Pro policy types in service status output
+   * Warn when Pro-only rules are configured
+   * Use systemd via D-Bus instead of systemctl commands
+   * Add placeholder notes for entry types
+   * Rework Kerberos ticket handling logic to satisfy the Heimdal 
implementation of Kerberos
+   * Rework policy application sync strategy
+   * Print logs when policies are up to date
+   * Update policy definitions to include dconf key for dark mode background
+   * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061)
+   * Allow sssd backend to work without ad_domain being set (LP: #2054445)
+   * Update apport hook to include journal errors and package logs
  
-  * Bug fixes
-   * Fix policy update failing when GPT.INI contains no version key
-   * Fix object lookup for users having a FQDN as their hostname
-   * Support special characters in domains when parsing sssd configuration
-   * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf
-   * Ensure empty state for dconf policy
-   * Handle case mismatches in GPT.INI file name
-   * Ensure GPO URLs contain the FQDN of the domain

[Bug 2059756] Re: [SRU] adsys 0.14.1

** Description changed:

  [context]
  ADSys is a tool designed for administering and implementing Group Policy 
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of 
services and commands that empower administrators to efficiently manage policy 
updates and maintain compliance with organizational business rules.
  
  Given that ADSys directly interfaces with Active Directory and needs to
  align with new business requirements in LTS releases, it has been
  essential to keep the package consistently updated with the latest
  changes of ADSys upstream source. As ADSys is a key component of our
  commercial offerings, our customers anticipate the availability of
  recently implemented features in the 22.04 release.
  
  Now that ADSys has a complete set of features, the request is to proceed
  with a one-off release of ADSys 0.14.1 to 22.04. Please note that any
  new features introduced in subsequent versions will be exclusively
  available in 24.04 and later releases.
  
  This version includes a comprehensive end to end automated test suite
  that runs ADSys against a real Active directory environment.
  
  Version 0.14.1 is available for 22.04 in a PPA
  (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys)
  and already used in production by customers.
  
  At this time of writing the number of open issues is 1 in Launchpad and
  16 in GitHub including 6 enhancements. None of them have a high or
  critical importance.
  
  [references]
  LP: https://launchpad.net/ubuntu/+source/adsys
  LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys
  GitHub: https://github.com/ubuntu/adsys/
  GH Bugs: https://github.com/ubuntu/adsys/issues
  Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/
  Initial SRU discussion: 
https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html
  
  [changes]
  Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog
   * New features
     * New policies:
   - Add mount / network shares policy manager
   - Add AppArmor policy manager
   - Support multiple AD backends and implement Winbind support
   - Add system proxy policy manager
   - Add certificate policy manager for machines
   - Add adsysctl policy purge command to purge applied policies
   - Full documentation
   - Full end to end automated test suite.
  
   * Enhancements
    * Add a --machine / -m flag to adsysctl applied, indicating the policies 
applied to the current machine
    * Expose Ubuntu Pro status in the "status" command
    * Update scripts manager creation
    * List Pro policy types in service status output
    * Warn when Pro-only rules are configured
    * Use systemd via D-Bus instead of systemctl commands
    * Add placeholder notes for entry types
    * Rework Kerberos ticket handling logic to satisfy the Heimdal 
implementation of Kerberos
    * Rework policy application sync strategy
    * Print logs when policies are up to date
    * Update policy definitions to include dconf key for dark mode background
    * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061)
    * Allow sssd backend to work without ad_domain being set (LP: #2054445)
    * Update apport hook to include journal errors and package logs
  
   * Bug fixes
    * Fix policy update failing when GPT.INI contains no version key
    * Fix object lookup for users having a FQDN as their hostname
    * Support special characters in domains when parsing sssd configuration
    * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf
    * Ensure empty state for dconf policy
    * Handle case mismatches in GPT.INI file name
    * Ensure GPO URLs contain the FQDN of the domain controller
    * Add runtime dependency on nfs-common
  
   * Other
    * Updates to latest versions of Go (fixing known Go vulnerabilities)
    * Updates to latest versions of the Go dependencies
    * Updates and improvements to CI and QoL
    * Migrate translation support to native approach using go-i18n + gotext and 
switch to upstream gotext version
  
  Dependencies:
  * Build-dep: golang-go (>= 2:1.22~)
  
  * Dependencies to backport to 22.04:
    * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will 
be disabled otherwise)
    * python3-cepces (suggest. Required for Certificates autoenrollment support 
- feature will be disabled otherwise)
  
  [test plan]
  # Process
- Adsys follows a robust continuous integration and testing process. It is 
covered by a comprehensive automated tests suite 
(https://github.com/ubuntu/adsys/actions/workflows/qa.yaml) and an automated 
end to end test suite that runs in a real active directory environment.
+ Adsys follows a robust continuous integration and testing process. It is 
covered by a comprehensive automated tests suite 
(https://github.com/ubuntu/adsys/actions/workflows/qa.yaml) and an automated 
end to end test suite that runs in a real active

[Bug 2059756] Re: [SRU] adsys 0.14.1

** Description changed:

  [context]
  ADSys is a tool designed for administering and implementing Group Policy 
Objects (GPOs) from Active Directory on Linux systems. It includes a suite of 
services and commands that empower administrators to efficiently manage policy 
updates and maintain compliance with organizational business rules.
  
  Given that ADSys directly interfaces with Active Directory and needs to
  align with new business requirements in LTS releases, it has been
  essential to keep the package consistently updated with the latest
  changes of ADSys upstream source. As ADSys is a key component of our
  commercial offerings, our customers anticipate the availability of
  recently implemented features in the 22.04 release.
  
  Now that ADSys has a complete set of features, the request is to proceed
  with a one-off release of ADSys 0.14.1 to 22.04. Please note that any
  new features introduced in subsequent versions will be exclusively
  available in 24.04 and later releases.
  
  This version includes a comprehensive end to end automated test suite
  that runs ADSys against a real Active directory environment.
  
  Version 0.14.1 is available for 22.04 in a PPA
  (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys)
  and already used in production by customers.
  
  At this time of writing the number of open issues is 1 in Launchpad and
  16 in GitHub including 6 enhancements. None of them have a high or
  critical importance.
  
  [references]
  LP: https://launchpad.net/ubuntu/+source/adsys
  LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys
  GitHub: https://github.com/ubuntu/adsys/
  GH Bugs: https://github.com/ubuntu/adsys/issues
  Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/
  Initial SRU discussion: 
https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html
  
  [changes]
  Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog
   * New features
     * New policies:
   - Add mount / network shares policy manager
   - Add AppArmor policy manager
   - Support multiple AD backends and implement Winbind support
   - Add system proxy policy manager
   - Add certificate policy manager for machines
   - Add adsysctl policy purge command to purge applied policies
   - Full documentation
   - Full end to end automated test suite.
  
   * Enhancements
    * Add a --machine / -m flag to adsysctl applied, indicating the policies 
applied to the current machine
    * Expose Ubuntu Pro status in the "status" command
    * Update scripts manager creation
    * List Pro policy types in service status output
    * Warn when Pro-only rules are configured
    * Use systemd via D-Bus instead of systemctl commands
    * Add placeholder notes for entry types
    * Rework Kerberos ticket handling logic to satisfy the Heimdal 
implementation of Kerberos
    * Rework policy application sync strategy
    * Print logs when policies are up to date
    * Update policy definitions to include dconf key for dark mode background
    * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061)
    * Allow sssd backend to work without ad_domain being set (LP: #2054445)
    * Update apport hook to include journal errors and package logs
  
   * Bug fixes
    * Fix policy update failing when GPT.INI contains no version key
    * Fix object lookup for users having a FQDN as their hostname
    * Support special characters in domains when parsing sssd configuration
    * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf
    * Ensure empty state for dconf policy
    * Handle case mismatches in GPT.INI file name
    * Ensure GPO URLs contain the FQDN of the domain controller
    * Add runtime dependency on nfs-common
  
   * Other
    * Updates to latest versions of Go (fixing known Go vulnerabilities)
    * Updates to latest versions of the Go dependencies
    * Updates and improvements to CI and QoL
    * Migrate translation support to native approach using go-i18n + gotext and 
switch to upstream gotext version
  
  Dependencies:
  * Build-dep: golang-go (>= 2:1.22~)
  
  * Dependencies to backport to 22.04:
    * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will 
be disabled otherwise)
    * python3-cepces (suggest. Required for Certificates autoenrollment support 
- feature will be disabled otherwise)
+   * Note: Both are currently in the new queue of 22.04 : 
https://launchpad.net/ubuntu/jammy/+queue?queue_state=0_text=
  
  [test plan]
  # Process
  Adsys follows a robust continuous integration and testing process. It is 
covered by a comprehensive automated tests suite 
(https://github.com/ubuntu/adsys/actions/workflows/qa.yaml) and an automated 
end to end test suite that runs in a real active directory environment 
(https://github.com/ubuntu/adsys/actions/workflows/e2e-tests.yaml).
  
  The team applied the following quality criteria:
   * All changes

[Bug 2043376] Re: adsys cant fetch gpos ubuntu 22.04.3

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2043376

Title:
  adsys cant fetch gpos ubuntu 22.04.3

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055300] Re: DEP8 failures in noble/armhf with samba 4.19.5

2024-03-11 Thread Jean-Baptiste Lallement

There is a passing run with samba/2:4.19.5+dfsg-1ubuntu1

This could be a flaky test on armhf. I'm closing this report for now and
will look further if it becomes a blocker on this arch in the futur.

** Changed in: adsys (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055300

Title:
  DEP8 failures in noble/armhf with samba 4.19.5

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055300] Re: DEP8 failures in noble/armhf with samba 4.19.5

2024-02-28 Thread Jean-Baptiste Lallement

** Changed in: adsys (Ubuntu)
 Assignee: (unassigned) => Gabriel Nagy (gabuscus)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055300

Title:
  DEP8 failures in noble/armhf with samba 4.19.5

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977689] [NEW] Wrong error msg: "state file /var/lib/logrotate/status is world-readable" although it is not

2022-06-05 Thread jean-christophe manciot

Public bug reported:

Ubuntu 22.04
logrotate 3.19.0-1ubuntu1.1

Every hour, I receive this wrong message:

Subject:Cron >cd / && run-parts --report 
/etc/cron.hourly
/etc/cron.hourly/logrotate:
error: state file /var/lib/logrotate/status is world-readable and thus can be 
locked from other unprivileged users. Skipping lock acquisition...

despite:

# ls -al /var/lib/logrotate
total 40
drwxr-x---  2 root root  4096 Jun  5 17:17 .
drwxr-xr-x 66 root root  4096 Jun  3 20:02 ..
-rw-r-  1 root root 31974 Jun  5 17:17 status

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

** Description changed:

  Ubuntu 22.04
  logrotate 3.19.0-1ubuntu1.1
  
  Every hour, I receive this wrong message:
+ 
+ Subject:  Cron >cd / && run-parts --report 
/etc/cron.hourly
  /etc/cron.hourly/logrotate:
  error: state file /var/lib/logrotate/status is world-readable and thus can be 
locked from other unprivileged users. Skipping lock acquisition...
  
  despite:
  
  # ls -al /var/lib/logrotate
  total 40
  drwxr-x---  2 root root  4096 Jun  5 17:17 .
  drwxr-xr-x 66 root root  4096 Jun  3 20:02 ..
  -rw-r-  1 root root 31974 Jun  5 17:17 status

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977689

Title:
  Wrong error msg: "state file /var/lib/logrotate/status is world-
  readable" although it is not

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975426] [NEW] package libinput-bin 1.15.5-1ubuntu0.3 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer.

2022-05-22 Thread jean vernin

Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libinput-bin 1.15.5-1ubuntu0.3
ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
AptOrdering:
 thunderbird-locale-en:amd64: Install
 thunderbird-locale-fr:amd64: Install
 thunderbird:amd64: Install
 thunderbird-gnome-support:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sun May 22 17:28:56 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  le 
réinstaller avant de tenter de le configurer.
GraphicsCard:
 NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: PNY TU116 [GeForce GTX 1650 SUPER] [196e:1350]
InstallationDate: Installed on 2021-09-22 (242 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic 
root=UUID=5c263473-36e2-410e-95e7-1174764ce9f8 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: libinput
Title: package libinput-bin 1.15.5-1ubuntu0.3 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F50
dmi.board.asset.tag: Default string
dmi.board.name: B450M DS3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: B450M DS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-package focal ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975426

Title:
  package libinput-bin 1.15.5-1ubuntu0.3 failed to install/upgrade: le
  paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929038] Re: [SRU] Backport to 20.04 LTS

2022-05-17 Thread Jean-Baptiste Lallement

It's a desktop package that we do not need on riscv64

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929038

Title:
  [SRU] Backport to 20.04 LTS

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958668] Re: Do not propose to reboot on WSL

2022-05-16 Thread Jean-Baptiste Lallement

** Changed in: update-manager (Ubuntu)
   Status: New => Triaged

** Changed in: update-manager (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958668

Title:
  Do not propose to reboot on WSL

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929038] Re: [SRU] Backport to 20.04 LTS

2022-05-13 Thread Jean-Baptiste Lallement

This has been verified a while ago and already deployed in production for 
customers.
Marking as verification-done.

** Tags removed: removal-candidate verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929038

Title:
  [SRU] Backport to 20.04 LTS

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969787] [NEW] package libinput-bin 1.15.5-1ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2022-04-21 Thread jean vernin

Public bug reported:

No idea

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libinput-bin 1.15.5-1ubuntu0.3
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.23
AptOrdering:
 libinput10:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Thu Apr 21 16:01:58 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DuplicateSignature:
 package:libinput-bin:1.15.5-1ubuntu0.3
 Unpacking libinput10:amd64 (1.15.5-1ubuntu0.3) over (1.15.5-1ubuntu0.2) ...
 dpkg: error processing package libinput-bin (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
GraphicsCard:
 NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: PNY TU116 [GeForce GTX 1650 SUPER] [196e:1350]
InstallationDate: Installed on 2021-09-22 (211 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-40-generic 
root=UUID=5c263473-36e2-410e-95e7-1174764ce9f8 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: libinput
Title: package libinput-bin 1.15.5-1ubuntu0.3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F50
dmi.board.asset.tag: Default string
dmi.board.name: B450M DS3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: B450M DS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-package focal need-duplicate-check ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969787

Title:
  package libinput-bin 1.15.5-1ubuntu0.3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1728354] Re: ntfs: unsupported reparse point

2022-04-12 Thread Jean-Pierre

@geole (post #82)

The file shown is "system compressed", which is the case for most
Windows 10 system files. You need the "system-compressed" plugin to read
it with ntfs-3g, and unfortunately Ubuntu has not packaged it yet.

You can get the source from :
https://github.com/ebiggers/ntfs-3g-system-compression
and compile it yourself the usual way (./configure; make), the move the 
generated file ntfs-plugin-8017.so to 
/usr/lib/x86_64-linux-gnu/ntfs-3g/ntfs-plugin-8017.so (after you have 
created the directory /usr/lib/x86_64-linux-gnu/ntfs-3g).

If you do not want to compile it yourself, you can download an earlier version 
from
https://jp-andre.pagesperso-orange.fr/systcomp.zip
just extract the linux-64 version of ntfs-plugin-8017.so and move it to 
/usr/lib/x86_64-linux-gnu/ntfs-3g/ntfs-plugin-8017.so

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728354

Title:
  ntfs: unsupported reparse point

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1728354/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968612] Re: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm

2022-04-11 Thread Éric St-Jean

steve - that's a fair point
pinging kernel

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968612

Title:
  Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1968612/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968612] Re: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm

2022-04-11 Thread Éric St-Jean

closing this but please feel free to comment if you have additional
questions or concerns

** Changed in: cloud-images
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968612

Title:
  Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1968612/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968612] Re: Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm

2022-04-11 Thread Éric St-Jean

indeed, this image has a minimal kernel
you can either install the generic kernel, or use the full ubuntu server image 
which contains the generic kernel, which will have the necessary support

** Also affects: cloud-images
   Importance: Undecided
   Status: New

** Changed in: linux-meta-kvm (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968612

Title:
  Ubuntu 20.04 Cloud Image: missing nfsd.ko module in linux-kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1968612/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1728354] Re: ntfs: unsupported reparse point

2022-04-08 Thread Jean-Pierre

> Same problème with 22.04 Beta Jammy

Which one ?

Your attachment is missing.

Please post the output of the commands described at the bottom of 
https://github.com/tuxera/ntfs-3g/wiki/Junctions-Points,-Symbolic-Links-and-Reparse-Points#other-types-of-reparse-points

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728354

Title:
  ntfs: unsupported reparse point

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1728354/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1941785] Re: ec2-hibinit-agent: Add support for IMDSv2

2022-04-07 Thread Éric St-Jean

** Also affects: cloud-images
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941785

Title:
  ec2-hibinit-agent: Add support for IMDSv2

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1941785/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968150] [NEW] [FFe] Remove zsys from installer

2022-04-07 Thread Jean-Baptiste Lallement

Public bug reported:

Zsys is in very low maintenance mode (critical bug fixes only) and must be 
removed from the LTS.
However ZFS and encrypted ZFS are still available as an installation option but 
the package ZSys is not installed.
The ZFS layout remains unchanged.

https://git.launchpad.net/ubiquity/commit/?id=76e7718dbdd9dde7a7609f754cf8719469bbf0e5

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

** Description changed:

  Zsys is in very low maintenance mode (critical bug fixes only) and must be 
removed from the LTS.
  However ZFS and encrypted ZFS are still available as an installation option 
but the package ZSys is not installed.
  The ZFS layout remains unchanged.
+ 
+ 
https://git.launchpad.net/ubiquity/commit/?id=76e7718dbdd9dde7a7609f754cf8719469bbf0e5

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968150

Title:
  [FFe] Remove zsys from installer

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967585] Re: Failed to start ZSYS daemon service (panic: runtime error)

2022-04-06 Thread Jean-Baptiste Lallement

** Changed in: zsys (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967585

Title:
  Failed to start ZSYS daemon service (panic: runtime error)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967585] Re: Failed to start ZSYS daemon service (panic: runtime error)

2022-04-06 Thread Jean-Baptiste Lallement

A pool compatibility property has been added to ZFS 2.1 but not to the
go binding.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967585

Title:
  Failed to start ZSYS daemon service (panic: runtime error)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967901] Re: Jammy fails to boot to live session in virt-manager with QXL

** Summary changed:

- Jammy fails to boot to live session
+ Jammy fails to boot to live session in virt-manager with QXL

** Description changed:

  Ubuntu Desktop Jammy 20220405
  
  It fails to boot to the live session in virt-manager and gnome-boxes.
  ubiquity-dm starts fine but the live session does. The graphical session 
keeps dying. There are crashes of gnome-shell and xorg in /var/crash.
  
- From the journal 
+ From the journal
  avril 05 16:15:55 ubuntu kernel: gnome-shell[1383]: segfault at 3f1d5d20 
ip 7fa1ca256f44 sp 7fff16f7c2a0 error 4 in 
libmozjs-91.so.91.7.0[7fa1ca1d7000+8e6000]
  avril 05 16:15:55 ubuntu kernel: Code: 00 00 00 0f 85 73 05 00 00 48 83 c4 38 
5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 0f 1f 44 00 00 48 85 f6 74 d2 48 81 e6 00 
00 f0 ff <48> 8b 06 48 85 c0 74 c3 80 b8 61 01 00 00 00 74 ba 48 3b 98 d0 00
  avril 05 16:15:55 ubuntu systemd[1]: Started crash report submission
+ 
+ 
+ If I switch from QXL to Virtio then it works.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967901

Title:
  Jammy fails to boot to live session in virt-manager with QXL

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967901] Re: Jammy fails to boot to live session

** Attachment added: "_usr_lib_xorg_Xorg.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577348/+files/_usr_lib_xorg_Xorg.0.crash

** Description changed:

  Ubuntu Desktop Jammy 20220405
  
  It fails to boot to the live session in virt-manager and gnome-boxes.
  ubiquity-dm starts fine but the live session does. The graphical session 
keeps dying. There are crashes of gnome-shell and xorg in /var/crash.
+ 
+ I'm on Jammy with libvirt 8.0.0-1ubuntu6 and qemu 6.2+dfsg-2ubuntu5

** Description changed:

  Ubuntu Desktop Jammy 20220405
  
  It fails to boot to the live session in virt-manager and gnome-boxes.
  ubiquity-dm starts fine but the live session does. The graphical session 
keeps dying. There are crashes of gnome-shell and xorg in /var/crash.
  
- I'm on Jammy with libvirt 8.0.0-1ubuntu6 and qemu 6.2+dfsg-2ubuntu5
+ From the journal 
+ avril 05 16:15:55 ubuntu kernel: gnome-shell[1383]: segfault at 3f1d5d20 
ip 7fa1ca256f44 sp 7fff16f7c2a0 error 4 in 
libmozjs-91.so.91.7.0[7fa1ca1d7000+8e6000]
+ avril 05 16:15:55 ubuntu kernel: Code: 00 00 00 0f 85 73 05 00 00 48 83 c4 38 
5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 0f 1f 44 00 00 48 85 f6 74 d2 48 81 e6 00 
00 f0 ff <48> 8b 06 48 85 c0 74 c3 80 b8 61 01 00 00 00 74 ba 48 3b 98 d0 00
+ avril 05 16:15:55 ubuntu systemd[1]: Started crash report submission

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967901

Title:
  Jammy fails to boot to live session

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967901] Re: Jammy fails to boot to live session

** Attachment added: "_usr_bin_gnome-shell.999.crash"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577347/+files/_usr_bin_gnome-shell.999.crash

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967901

Title:
  Jammy fails to boot to live session

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967901] Re: Jammy fails to boot to live session

** Attachment added: "journal.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577346/+files/journal.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967901

Title:
  Jammy fails to boot to live session

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967901] Re: Jammy fails to boot to live session

** Attachment added: "debug"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577344/+files/debug

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967901

Title:
  Jammy fails to boot to live session

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967901] Re: Jammy fails to boot to live session

** Attachment added: "dm"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1967901/+attachment/5577345/+files/dm

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967901

Title:
  Jammy fails to boot to live session

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967901] [NEW] Jammy fails to boot to live session

Public bug reported:

Ubuntu Desktop Jammy 20220405

It fails to boot to the live session in virt-manager and gnome-boxes.
ubiquity-dm starts fine but the live session does. The graphical session keeps 
dying. There are crashes of gnome-shell and xorg in /var/crash.

From the journal 
avril 05 16:15:55 ubuntu kernel: gnome-shell[1383]: segfault at 3f1d5d20 ip 
7fa1ca256f44 sp 7fff16f7c2a0 error 4 in 
libmozjs-91.so.91.7.0[7fa1ca1d7000+8e6000]
avril 05 16:15:55 ubuntu kernel: Code: 00 00 00 0f 85 73 05 00 00 48 83 c4 38 
5b 5d 41 5c 41 5d 41 5e 41 5f c3 66 0f 1f 44 00 00 48 85 f6 74 d2 48 81 e6 00 
00 f0 ff <48> 8b 06 48 85 c0 74 c3 80 b8 61 01 00 00 00 74 ba 48 3b 98 d0 00
avril 05 16:15:55 ubuntu systemd[1]: Started crash report submission

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


** Tags: jammy

** Tags added: jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967901

Title:
  Jammy fails to boot to live session

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966818] Re: zsys crashing on snap mounts

2022-04-03 Thread Jean-Baptiste Lallement

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

** This bug has been marked a duplicate of bug 1967585
   Failed to start ZSYS daemon service (panic: runtime error)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966818

Title:
  zsys crashing on snap mounts

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967585] Re: Failed to start ZSYS daemon service (panic: runtime error)

2022-04-02 Thread Jean-Baptiste Lallement

Thanks for your report. Confirmed with 0.5.8build2.

Downgrading and pinning to 0.5.8 is the workaround for now.
https://launchpad.net/ubuntu/+source/zsys/0.5.8/+build/21362897/+files/zsys_0.5.8_amd64.deb

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

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

** Changed in: zsys (Ubuntu)
 Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)

** Changed in: zsys (Ubuntu)
Milestone: None => ubuntu-22.04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967585

Title:
  Failed to start ZSYS daemon service (panic: runtime error)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929201] Re: Packages in PPA are not installed if version higher than in a release pocket

2022-03-16 Thread Jean-Baptiste Lallement

I confirm that adding XB-Task addresses the issue and the package from
the PPA is installed. However, when there is no task defined, the
package from archive should be installed.

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929201

Title:
  Packages in PPA are not installed if version higher than in a release
  pocket

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964325] [NEW] Fails to print due to apparmor denied connect operation for cupsd - /run/systemd/userdb/io.systemd.Machine

2022-03-09 Thread Jean-Baptiste Lallement

Public bug reported:

On an up to date Jammy machine, printing fails and there is the
following apparmor denied message in the journal:

apparmor="DENIED" operation="connect" profile="/usr/sbin/cupsd"
name="/run/systemd/userdb/io.systemd.Machine" pid=892182 comm="cupsd"
requested_mask="w" denied_mask="w" fsuid=0 ouid=0

Printing works after running aa-complain cupsd.

The printer is a driverless HP Envy 5020

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apparmor 3.0.4-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  9 10:25:10 2022
InstallationDate: Installed on 2020-05-31 (647 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
ProcKernelCmdline: BOOT_IMAGE=/BOOT/ubuntu_nt06gx@/vmlinuz-5.15.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_nt06gx ro snd-intel-dspcfg.dsp_driver=1
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: apparmor
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy rls-jj-incoming

** Tags added: rls-jj-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964325

Title:
  Fails to print due to apparmor denied connect operation for cupsd -
  /run/systemd/userdb/io.systemd.Machine

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936907] Re: [MIR] ADSys

2022-02-07 Thread Jean-Baptiste Lallement

** Description changed:

  [Availability]
  
  Available on all archs, available starting hirsute. It will be
  backported to Focal once an FFe has been accepted.
  
  [Rationale]
  
  We are supporting GPO Active Directory support on ubuntu starting
  hirsute. This features allows for an administrator to configure their
  Active Directory server to deploy per-machine and per-user
  configurations, enforce rules and other domain policies.
  
- Right now, dconf keys are supported.
+ Right now, dconf keys, sudo administration rights and computer and user
+ scripts are supported.
  
  This feature is built and use the krb5 tickets which are provided by SSSD. 
Basically:
  - SSSD is dealing with user and machine registration/authentification and 
enforce password policies
  - ADSys is handling GPO enforcement and support. The Ubuntu specific policies 
needs to be installed on the Active Directory server (they are contained in the 
daemon).
  
  [Security]
  
  The daemon is started is running as a root user to be able to enforce
  machine policies, like rebuilding dconf databases, setting profiles.
  User only interacts with the client side (both sides communicates over
  GRPC), which can be ran as any user.
  
  Polkit is used to restrain access to some part of the API.
  
  There is a PAM module to build on demand per-user policy once
  authenticated with SSSD. They are rejected if the authentication or not
  all affected policies could be downloaded.
  
  [Quality assurance]
  
  Joining a domain in the ubiquity desktop installer makes the machine
  joining the AD domain and install adsys functionality. The package will
  be seeded directly on the desktop ISO.
  
- An extensive testsuite (more than 700) is included and available as
+ An extensive testsuite (more than 1k) is included and available as
  autopkgtests for rdepends. The whole stack is tested (even the
  client/daemon interaction) and coverage is measured (including in the
  small python script). However, tests with a real Active Directory server
  can only be done manually as there is no setup available in the
  autopkgtests infrastructure.
  
  [Dependencies]
  
  Main dependencies are libsmbclient, python3 (an embeeded script allows,
  via samba, connecting to AD LDAP) and SSSD/KRB5.
  
  This is a Go package, and all dependencies are vendored, and versions
  are controlled via go.mod. We are using dependabot (from Github) to
  automatically get notified of any dependencies updates (and security
  issues), which opens a PR, rebuild and run all tests to report it there.
  We are thus able to quickly merge them.
  
  [Standards compliance]
  
  Standard debhelper packaging, including a systemd service.
  
  [Maintenance]
  
  The desktop team will maintain it.
  
  * we commit to test no-change-rebuilds triggered by a dependent 
library/compiler and to fix any issues found for the lifetime of the release 
(including ESM when included)
  * we will provide timely testing of no-change-rebuilds from the security 
team, fixing the rebuilt package as necessary
  * we commit to  provide updates to the security team for any affected 
vendored code for the lifetime of the release (including ESM when included)
  * we will provide timely, high quality updates for the security team to 
sponsor to fix issues in the affected vendored code
  
- 
  [Background information]
  
  ADSys is composed of:
  - a daemon, named adsysd, running as root. This one will shutdown after a 
period of inactivity without any active request. It is socket activated.
  - a client, named adsysctl (which is a symlink to adsysd and only differ 
behavior from its executable name), which is running as the user (or root on 
boot for machine update). This ones optionally wakes up adsysd, connect through 
an Unix socket with SO_PEERCRED to communicate current user running the 
process. We are using grpc to communicate between the client and service.
  
  Each client request is validated through polkit, matching user name and
  permissions. The daemon will reject any unauthorized client connections.
  Note that all actions are always performed from executing the client,
  even the scheduled one by a cron.
  
- The daemon contains a python embeeded script to reuse samba utilities to
- connect with GSSAPI to the AD LDAP server and list available GPOs. GPOs
- are then downloaded in a cache directory which isn’t accessible to
+ The daemon contains a python embedded script that uses samba utilities
+ to connect with GSSAPI to the AD LDAP server and list available GPOs.
+ GPOs are then downloaded in a cache directory which isn’t accessible to
  users.
  
  The daemon also contains all GPOs policies to install on the Active
  Directory side to reflect them in the UI. This could be accessed online
  or dumped directly via the command line tool. Finally, those are
  automatically refreshed for any supported LTSes and intermediate
  versions. The availability of features can be different

[Bug 1959667] [NEW] non informative error message when enabling a non available UA service

2022-02-01 Thread Jean-Baptiste Lallement

Public bug reported:

Jammy / software-properties-gtk:
  Installed: 0.99.17

When trying to enable a service that is not available the error message
provide no useful information about what went wrong (cf screenshot)


and in the journal:
ubuntu-advantag[1461382]: Failed to parse UA status: Operation was cancelled


In both cases the error message should be similar to UA CLI:

UA Infra: ESM is not available for Ubuntu 22.04 (Jammy Jellyfish).

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "2022-02-01_12-06.png"
   
https://bugs.launchpad.net/bugs/1959667/+attachment/5558588/+files/2022-02-01_12-06.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959667

Title:
  non informative error message when enabling a non available UA service

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958668] [NEW] Do not propose to reboot on WSL

2022-01-21 Thread Jean-Baptiste Lallement

Public bug reported:

On WSL, at the end of a do-release-upgrade, the upgrader proposes to
reboot the machine. Although on WSL it is not possible to reboot due to
the lack of systemd and it ends with an error.

The message at the end should be different if it is running on a system
where systemd is not available or specifically on WSL and do not propose
a reboot but to manually shutdown and restart the instance.

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958668

Title:
  Do not propose to reboot on WSL

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958412] [NEW] at startup and shutdown screen gets white noise

2022-01-19 Thread Jean Dejonghe

Public bug reported:

After the kernel release 5.13.0-27-generic was installed today, the startup and 
shutdown processes finish with white noise screens.
The workaround at startup is to disable "quiet" in /etc/default/grub, variable 
GRUB_CMDLINE_LINUX_DEFAULT. (GRUB_CMDLINE_LINUX_DEFAULT="splash" works, 
GRUB_CMDLINE_LINUX_DEFAULT=" quiet splash" doesn't).
No workaround found for shutdown until now. Can you help me find one ?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Jan 19 16:17:35 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c2) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:18b2]
InstallationDate: Installed on 2022-01-19 (0 days ago)
InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP420UA_TM420UA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=c4ec4ae8-c14c-4c0b-9922-9142270cef97 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: TP420UA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: TP420UA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.2
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP420UA.302:bd09/06/2021:br5.19:efr3.2:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP420UA_TM420UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP420UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
dmi.product.family: VivoBook Flip
dmi.product.name: VivoBook_ASUSLaptop TP420UA_TM420UA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal kubuntu resolution ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958412

Title:
  at startup and shutdown screen gets white noise

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958284] Re: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec

2022-01-18 Thread Jean Raby

** Description changed:

  With systemd v245 as shipped with 20.04, the shutdown sequence does not
  use the value of `DefaultTimeoutStopSec` to wait for remaining
  processes, it instead uses the compiled in default of 90s.
  
  This is most visible with services that use `KillMode=process` (docker,
  k8s, k3s, etc...), especially if the remaining processes do not handle
  `SIGTERM` or choose to ignore it.
  
  For example:
  ```
  [ OK ] Finished Reboot.
  [ OK ] Reached target Reboot.
  [ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, 
containerd-shim, containerd-shim, fluent-bit
  
  --- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower
  value ---
  
  ```
  
  The bug has been fixed upstream here:
  https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22
  
  Marc was kind enough to package the patch for 20.04 so I could test it
  
(https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing-
  archive-extra) and with that package, I can confirm that it indeed fixes
  the issue.
  
  Here's a few github issues I stumbled upon while trying to debug this,
  along with a short writeup of the workaround I ended up using:
  
  - https://github.com/moby/moby/issues/41831
  - https://github.com/k3s-io/k3s/issues/2400
- - 
http://localhost:8000/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html
+ - https://github.com/systemd/systemd/issues/16991
+ - https://raby.sh/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html
  
  Of course, it would be much better if all the processes would properly
  handle `SIGTERM`, but having a way to enforce a maximum wait time at
  shutdown is a decent workaround.
  
  Given that the patch is relatively simple, would it be possible to add
  it the package for 20.04?
  
  Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958284

Title:
  shutdown hangs at "Waiting for process: ..." for 90s, ignoring
  DefaultTimeoutStopSec

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958284] [NEW] shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec

2022-01-18 Thread Jean Raby

Public bug reported:

With systemd v245 as shipped with 20.04, the shutdown sequence does not
use the value of `DefaultTimeoutStopSec` to wait for remaining
processes, it instead uses the compiled in default of 90s.

This is most visible with services that use `KillMode=process` (docker,
k8s, k3s, etc...), especially if the remaining processes do not handle
`SIGTERM` or choose to ignore it.

For example:
```
[ OK ] Finished Reboot.
[ OK ] Reached target Reboot.
[ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, 
containerd-shim, containerd-shim, fluent-bit

--- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower
value ---

```

The bug has been fixed upstream here:
https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22

Marc was kind enough to package the patch for 20.04 so I could test it
(https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing-
archive-extra) and with that package, I can confirm that it indeed fixes
the issue.

Here's a few github issues I stumbled upon while trying to debug this,
along with a short writeup of the workaround I ended up using:

- https://github.com/moby/moby/issues/41831
- https://github.com/k3s-io/k3s/issues/2400
- http://localhost:8000/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html

Of course, it would be much better if all the processes would properly
handle `SIGTERM`, but having a way to enforce a maximum wait time at
shutdown is a decent workaround.

Given that the patch is relatively simple, would it be possible to add
it the package for 20.04?

Thanks

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958284

Title:
  shutdown hangs at "Waiting for process: ..." for 90s, ignoring
  DefaultTimeoutStopSec

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958180] Re: "not in multiple of 0x10000" chkdsk errors for sparse files

2022-01-18 Thread Jean-Pierre

Nothing to be worried about, this is not a bug and the message is just a
technical warning. The chkdsk conclusion is "Windows has scanned the
file system and found no problems."

Since about 2016, Windows allocates space by chunks of multiple
clusters, but it still correctly processes files allocated by a single
cluster at a time. You need not make a copy to use it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958180

Title:
  "not in multiple of 0x1" chkdsk errors for sparse files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1958180/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

2022-01-11 Thread Jean-

Hi everyone,

small progress report :

I tried the pipewire trick and it didn't work out for me, while it initially 
seemed to work: auto switch to the HSP/HPF profile didn't work and after a 
manual switch the headset would drop out during a conversation.
I reverted to pulseaudio and invested a bit more time, now I am _almost_ there :

I had to add the following to ~/.config/pulse/default.pa

.include /etc/pulse/default.pa
.nofail
unload-module module-bluetooth-policy
.fail
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy auto_switch=2
.endif

.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif

to get the autoswitch to work.

I am happy to report that in slack (from snap) the audio now behaves just right 
and friends tell me I no longer sound like a robot. 
Unfortunately this still doesn't work with zoom and there seems to be multiple 
issues. They probably come from zoom itself but I am unsure what to report to 
them. 

according to https://gavv.github.io/articles/pulseaudio-under-the-
hood/#autodetecting-properties  it should be possible to make pulseaudio
understand that it has to switch profiles by changing
/usr/share/applications/Zoom.desktop and adding Telephony to the
categories. I have not been able to make this work without auto_switch=2

Here are two scenarios that fail: 
after a fresh boot (so all the stars are aligned), start zoom, create a new 
meeting, start the recording, say a few words, stop the recording, stop the 
meeting, open the resulting audio or video file 
the sound is bad when it is expected to be good. 

After a fresh boot (so all the stars are aligned), start zoom, go to
settings-> audio, after doing this my headset is non functional and I
must shut it down and start it back up to restore functionality.

can someone help me determine what zoom is doing wrong ?

I will also try a few other apps in the coming weeks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838151

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1957013] [NEW] package mysql-server-8.0 8.0.27-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

2022-01-10 Thread Jean Bosco Kalenga

Public bug reported:

i am not able to make an update for this one.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.27-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Jan 10 23:39:35 2022
ErrorMessage: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2021-01-27 (348 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Logs.var.log.daemon.log:
 
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Trop de niveaux de liens 
symboliques: '/etc/mysql/my.cnf'
MySQLVarLibDirListing: ['client-cert.pem', 'ib_logfile1', 'binlog.000104', 
'binlog.000102', 'binlog.000105', 'binlog.000100', 'sys', 'debian-5.7.flag', 
'ibdata1', 'binlog.000103', 'ib_logfile0', 'ib_buffer_pool', 'binlog.97', 
'binlog.000101', 'binlog.000107', 'mysql_upgrade_info', 'binlog.000098', 
'jean-desktop.pid', 'binlog.index', 'public_key.pem', 'binlog.000108', 
'binlog.99', 'undo_002', 'mysql', 'undo_001', 'server-cert.pem', 
'#innodb_temp', 'ca.pem', 'ca-key.pem', 'binlog.000106', 'server-key.pem', 
'#ib_16384_0.dblwr', 'performance_schema', 'client-key.pem', 'auto.cnf', 
'#ib_16384_1.dblwr', 'private_key.pem', 'mysql.ibd', 'ibtmp1']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic 
root=UUID=dcddafc6-2e54-4ad3-8798-5fb5f24419b1 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: mysql-8.0
Title: package mysql-server-8.0 8.0.27-0ubuntu0.20.04.1 failed to 
install/upgrade: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mysql-8.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957013

Title:
  package mysql-server-8.0 8.0.27-0ubuntu0.20.04.1 failed to
  install/upgrade: installed mysql-server-8.0 package post-installation
  script subprocess returned error exit status 1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1302462] Re: network icon disappeared in xubuntu

2022-01-09 Thread Detemple Jean-Luc

Do the following :

sudo mousepad /etc/NetworkManager/NetworkManager.conf

and change :

[ifupdown]
managed=true


The default value is false, but it seems that if when the system starts the 
network is not yet ready the applet will not be displayed

if you set the value to true, it solves the problem.

PS : depending on your distribution the file may be called nm-system-
settings.conf instead of NetworkManager.conf

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302462

Title:
  network icon disappeared in xubuntu

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling

2021-12-15 Thread Jean

Good. I woke up the laptop after leaving it hooked to the docking and in
sleep the whole night, no issues.

I consider it resolved. Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944409

Title:
  Systemd uses CPU after wakeup due to power_supply BAT0 (battery)
  continued polling

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling

2021-12-14 Thread Jean

After first reboot with BIOS 1.12.2 all seems fine, the update seems
even to have made the process of hooking up the docking station and
activating the external monitors faster.

After first sleep and wakeup, no battery pinging that I can see with
udevadm monitor, not even at a slow pace (but the battery is more than
full).

Should I retry during battery recharge?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944409

Title:
  Systemd uses CPU after wakeup due to power_supply BAT0 (battery)
  continued polling

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling

2021-12-14 Thread Jean

#7 output was already attached there, just grepped for brevity. The
first lines where confusing me though, I've now upgraded the system BIOS
from 1.6.1 to 1.12.2. 1.13 seems available on the official site, I'll
report back ASAP on the results of the upgrade.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944409

Title:
  Systemd uses CPU after wakeup due to power_supply BAT0 (battery)
  continued polling

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1815278] Re: LyX restores the same cursor position wherever it was placed next time(s)

2021-12-13 Thread Jean-Marc Lasgouttes

Do you have more than 100 files remembered in session file? We
supposedly have fixed this in 2.3.4, if this is the bug I have in mind.

Are other parameters of session (e.g. window size), correctly
remembered?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815278

Title:
  LyX restores the same cursor position wherever it was placed next
  time(s)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling

2021-12-13 Thread Jean

I don't have any BIOS update available; as I said, my laptop (Dell
Latitude 7520) is fully updated.

$ sudo dmidecode -s bios-version
1.6.1

$ fwupdmgr get-updates | grep "Current version" -B2
Devices with no available firmware updates: 
 • UEFI Device Firmware
 • UEFI Device Firmware
 • UEFI dbx
 • VMM3332 inside Dell WD15/TB16/TB18 wired Dock
│ │   Device ID:  71b677ca0f1bc2c5b804fa1d59e52064ce589293
│ │   Summary:NVM Express Solid State Drive
│ │   Current version:21112012
--
└─System Firmware:
  │   Device ID:  5ecfc78eb81da0c1a2ab9baa1510f0c269ea1b9b
  │   Current version:1.6.1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944409

Title:
  Systemd uses CPU after wakeup due to power_supply BAT0 (battery)
  continued polling

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling

2021-12-12 Thread Jean

No, no workaround. I still have to do the restart at every reboot with
the docking station attached.

My system is fully updated up to yesterday:

$ uname -a
Linux CLIFMI085 5.13.0-1021-oem #25-Ubuntu SMP Thu Dec 2 18:03:51 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944409

Title:
  Systemd uses CPU after wakeup due to power_supply BAT0 (battery)
  continued polling

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870189] Re: initramfs does not get loaded

2021-12-08 Thread Éric St-Jean

** Changed in: cloud-images
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870189

Title:
  initramfs does not get loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1953249] Re: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing

2021-12-05 Thread Jean-Pierre van Riel

Per coincidence, I worked on this same bug today, as I'm hoping to try
make use of the amdpro legacy OpenCL drivers, which will need amdgpu as
a base.

The issue is Ubuntu is providing newer kernel HWE stacks with amdgpu
driver modules, but failing to keep related Linux firmware packages up
to date and in lockstep. E.g. 20.04.3 LTS is based on kernel 5.11 from
hirsute (21.04), but the linux-firmware collection is left outdated on
1.187.20 that came with kernel 5.4?

https://packages.ubuntu.com/hirsute-updates/linux-firmware shows v
1.197.3, so I'd expect a HWE stack with 20.04.3 to also provide the same
level of firmware updates for kernel 5.11.

> I use UEFI and the module wasn't signed

Perhaps installing the official deb/repo instead of upstream has a good
shot at the firmware that gets added into initramfs being signed
properly (one would hope!). I manged the following workaround, but my
case is still legacy BIOS.

curl -OL
http://archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.197.3_all.deb
sudo dpkg -i linux-firmware_1.197.3_all.deb

Extra hint: maybe download the deb from your closest mirror because this
package is almost 200MB large.

P.S. While most firmware is hopefully decoupled and backward compatible
to use with older kernel modules/drivers, one never knows if a bug might
show up by using very new firmware with much older modules, since you
stray into a untested path between the firmware and the kernel modules.
Hence I tried to match the Ubuntu release, kernel versions, and tested-
at-the-time firmware more closely than just jumping to latest upstream
firmware versions.

Its similar but a kinda upside version of the older proprietary graphics
driver blob hell that plagued Linux over the previous decade. Firmware
is the other way round where the in-tree admgpu driver needs the
firmware to provide a stable interface. Can't recall if Linux ever
solved the lack of a stable in-kernel/versioned ABI between drivers and
binary driver blobs. It's why AMD FGLRX proprietary drivers blobs were
always hell, and AMD failed to keep up with ABI changes on the kernel
and often didn't work with newer kernels, hence amdgpu became the new
middle layer/foundation to bridge this ABI gap and add create a
stable/presumably versioned ABI for AMD that the kernel developers never
bothered to provide. Now AMD-pro software and extended driver blobs can
rely on the opensource amdgpu parts to be less of a moving target as ABI
changes on the kernel core will need to update/include required changes
to amdgpu because amdgpu is now in-tree and should be tested in lockstep
with other kernel changes.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953249

Title:
UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing

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

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952999] Re: Wayland blocks the microphone of the webcam

Yes, it works perfectly with Xorg.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952999

Title:
  Wayland blocks the microphone of the webcam

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952999] [NEW] Wayland blocks the microphone of the webcam

Public bug reported:

Jammy daily

In the wayland session the microphone of the webcam is no available.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libwayland-bin 1.19.0-2build1
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec  2 07:45:44 2021
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Comet Lake UHD Graphics [8086:9bca] (rev 04) (prog-if 00 
[VGA controller])
   Subsystem: Intel Corporation Device [8086:2081]
InstallationDate: Installed on 2020-05-31 (549 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
MachineType: Intel(R) Client Systems NUC10i7FNH
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_nt06gx@/vmlinuz-5.13.0-20-generic 
root=ZFS=rpool/ROOT/ubuntu_nt06gx ro snd-intel-dspcfg.dsp_driver=1
SourcePackage: wayland
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2019
dmi.bios.release: 5.16
dmi.bios.vendor: Intel Corp.
dmi.bios.version: FNCML357.0032.2019.1021.1624
dmi.board.asset.tag: Default string
dmi.board.name: NUC10i7FNB
dmi.board.vendor: Intel Corporation
dmi.board.version: K61360-302
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 3.4
dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:br5.16:efr3.4:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:skuBXNUC10i7FNH:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
dmi.product.family: FN
dmi.product.name: NUC10i7FNH
dmi.product.sku: BXNUC10i7FNH
dmi.product.version: K61081-302
dmi.sys.vendor: Intel(R) Client Systems
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug jammy reproducible rls-jj-incoming single-occurrence 
ubuntu wayland-session

** Tags added: rls-jj-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952999

Title:
  Wayland blocks the microphone of the webcam

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952457] Re: choosing Ubuntu on xorg fails to launch X, launches Wayland

There is no crash and this is on hardware.

** Tags added: rls-jj-incoming

** Attachment added: "journal.txt.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1952457/+attachment/5544826/+files/journal.txt.gz

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952457

Title:
  choosing Ubuntu on xorg fails to launch X, launches Wayland

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952930] Re: Xorg session doesn't stick

** Attachment added: "journal.txt.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1952930/+attachment/5544680/+files/journal.txt.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952930

Title:
  Xorg session doesn't stick

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952930] [NEW] Xorg session doesn't stick

Public bug reported:

Jammy daily.

*Test Case*
1. Boot to GDM
2. Select an Xorg Session
3. Login
4. Verify that Xorg is running 
5. Reboot the machine
6. Check that Xorg session is still selected
7. Login
8. Verify that Xorg is running

*Actual result*
Wayland is running despite Xorg was preselected.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-session 40.1.1-3ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  1 16:28:37 2021
InstallationDate: Installed on 2020-05-31 (549 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
PackageArchitecture: all
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy rls-jj-incoming wayland-session

** Tags added: rls-jj-incomping

** Tags removed: rls-jj-incomping
** Tags added: rls-jj-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952930

Title:
  Xorg session doesn't stick

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1580596] Re: Xenial & bionic vagrant box disk size is too small

2021-11-16 Thread Éric St-Jean

** Changed in: cloud-images
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580596

Title:
  Xenial & bionic vagrant box disk size is too small

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1580596/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context

2021-11-16 Thread Jean-Baptiste Lallement

Verification

Mesa 21.0.3-0ubuntu0.3~20.04.4 has been tested on 2 systems and it fixes
the issue. Marking as verification-done.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950174

Title:
  [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context

** Changed in: mesa (Ubuntu Focal)
   Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950174

Title:
  [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context

** Description changed:

  [Description]
  This is a request to backport this fix from mesa 21.1 to focal-updates which 
is affecting users of WSL:
  
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
  
  This cached stale pointer is causing various chromium applications
  (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is
  enabled in WSLg. We’re getting incredibly unlucky because a glx drawable
  is being freed and reallocated with exactly the same heap pointers
  during a resize, which is causing Mesa to think the new drawable is
  already fully initialized when binded to the context, but it is not true
  and only because the new drawable is matching the old stale pointer for
  the previously freed drawable… and as a result the context remain
  invalid and the app is unable to present.
  
  With the push of WDDMv3 drivers which expose vGPU in WSL, the number of
  users hitting this issue is increasing.
  
  [Test Case]
  On Windows 11 with WSLg and Ubuntu 20.04
  
  1. Verify that hardware acceleration is enable either with glxinfo -B or in 
edge with edge://gpu
  2. Install and launch chrome, edge or vscode
  3. Resize the windows repeatedly
  
  Verification:
  The app must not crash or hang.
+ 
+ [What could go wrong]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950174

Title:
  [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context

** Description changed:

  [Description]
  This is a request to backport this fix from mesa 21.1 to focal-updates which 
is affecting users of WSL:
  
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
  
  This cached stale pointer is causing various chromium applications
  (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is
  enabled in WSLg. We’re getting incredibly unlucky because a glx drawable
  is being freed and reallocated with exactly the same heap pointers
  during a resize, which is causing Mesa to think the new drawable is
  already fully initialized when binded to the context, but it is not true
  and only because the new drawable is matching the old stale pointer for
  the previously freed drawable… and as a result the context remain
  invalid and the app is unable to present.
  
  With the push of WDDMv3 drivers which expose vGPU in WSL, the number of
  users hitting this issue is increasing.
  
  [Test Case]
+ On Windows 11 with WSLg and Ubuntu 20.04
+ 
  1. Verify that hardware acceleration is enable either with glxinfo -B or in 
edge with edge://gpu
  2. Install and launch chrome, edge or vscode
  3. Resize the windows repeatedly
  
  Verification:
  The app must not crash or hang.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950174

Title:
  [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context