[Desktop-packages] [Bug 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 Status in firefox package in Ubuntu: New Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2083538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2083568] Re: full system freezes and needs to be hard rebooted
** Package changed: ubuntu-release-upgrader (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2083568 Title: full system freezes and needs to be hard rebooted Status in mesa package in Ubuntu: New Bug description: Not related to a specific package but started to happend after updating to 24.04.01. Some other issues of note are: - full system freeze requiring reboot - black screen with x curser on start up - bottom toolbar occasionally is frozen - firefox lags and need to restart - windows freeze when using split window function Ubuntu 24.04.1 LTS ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.23 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 16:07:56 2024 InstallationDate: Installed on 2021-08-19 (1140 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.init.d.apport: 2024-07-22T07:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2083568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2083538] Re: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0
To the best of my knowledge the issue started happening when the kernel was upgraded. That being said, the Firefox process that seemingly causes stalls is a snap so it is using its own mesa and not the host one, and I can't speak to the snap's mesa version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2083538 Title: amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 / Fence fallback timer expired on ring sdma0 Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite crashy and laggy. I have attached the previous boot log which shows a lot of errors. It does not seem to like firefox. Behavior visible is that it hangs, then tries resets, fails to reset and then the screen is unusable so I sysrq reboot it. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-8-generic 6.11.0-8.8 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 2 19:06:47 2024 InstallationDate: Installed on 2022-11-26 (676 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2083068] Re: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH >
** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2083068 Title: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > Status in glib2.0 package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Won't Fix Status in glib2.0 source package in Noble: New Status in ubuntu-release-upgrader source package in Noble: New Bug description: When trying to upgrade from Ubuntu 22.04.5 LTS to 24.04 LTS, I've got this error: ... "Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. The package 'update-manager' is marked for removal but it is in the removal deny list. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. " Update-manager version is 1:22.04.21. All software were updated before upgrade process. Third party repos disabled. How can I upgrade without a fresh install? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.20 ProcVersionSignature: Ubuntu 6.8.0-45.45~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: GNOME Date: Fri Sep 27 20:54:38 2024 InstallationDate: Installed on 2019-07-12 (1904 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-09-27 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-09-27 20:51:16 Requested-By: razvi (1000) End-Date: 2024-09-27 20:51:17 VarLogDistupgradeApttermlog: Log started: 2024-09-27 20:51:16 Log ended: 2024-09-27 20:51:17 VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2083068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2083068] Re: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH >
For oracular is the solution architecture-properties? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2083068 Title: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > Status in glib2.0 package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Won't Fix Status in glib2.0 source package in Noble: New Status in ubuntu-release-upgrader source package in Noble: New Bug description: When trying to upgrade from Ubuntu 22.04.5 LTS to 24.04 LTS, I've got this error: ... "Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. The package 'update-manager' is marked for removal but it is in the removal deny list. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. " Update-manager version is 1:22.04.21. All software were updated before upgrade process. Third party repos disabled. How can I upgrade without a fresh install? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.20 ProcVersionSignature: Ubuntu 6.8.0-45.45~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: GNOME Date: Fri Sep 27 20:54:38 2024 InstallationDate: Installed on 2019-07-12 (1904 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-09-27 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-09-27 20:51:16 Requested-By: razvi (1000) End-Date: 2024-09-27 20:51:17 VarLogDistupgradeApttermlog: Log started: 2024-09-27 20:51:16 Log ended: 2024-09-27 20:51:17 VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2083068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2083068] Re: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH >
Tracking Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > here. Which happens due to Depends: python3 | qemu-user | qemu-user-static in libglib2.0-dev:i386 (thanks helmut). i.e. it says python3 needs to be the same architecture, or you need qemu-user to execute bits. For reasons of lazyness I'd propose changing this to: Depends: python3:amd64 [i386] | python3 | qemu-user | qemu-user-static This ensures we do not enter the broken python3:i386 code path. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Triaged => Won't Fix ** Changed in: glib2.0 (Ubuntu) Status: New => Triaged ** Also affects: glib2.0 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2083068 Title: Broken libglib2.0-dev:i386 Depends on python3:i386 < none | 3.12.3-0ubuntu2 @un uH > Status in glib2.0 package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Won't Fix Status in glib2.0 source package in Noble: New Status in ubuntu-release-upgrader source package in Noble: New Bug description: When trying to upgrade from Ubuntu 22.04.5 LTS to 24.04 LTS, I've got this error: ... "Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. The package 'update-manager' is marked for removal but it is in the removal deny list. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. " Update-manager version is 1:22.04.21. All software were updated before upgrade process. Third party repos disabled. How can I upgrade without a fresh install? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.20 ProcVersionSignature: Ubuntu 6.8.0-45.45~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: GNOME Date: Fri Sep 27 20:54:38 2024 InstallationDate: Installed on 2019-07-12 (1904 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-09-27 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-09-27 20:51:16 Requested-By: razvi (1000) End-Date: 2024-09-27 20:51:17 VarLogDistupgradeApttermlog: Log started: 2024-09-27 20:51:16 Log ended: 2024-09-27 20:51:17 VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2083068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2082162] Re: after updating , brightness is not working
Brightness is managed by gnome-settings-daemon. This report seems similar to bug 2081294 which was reported for oracular and fixed in 47.1. I haven't checked if noble also is affected, but either way we need more information. My suggestion would simply be to run ubuntu-bug 2082162 to attach the data. ** Package changed: gnome-shell (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2082162 Title: after updating , brightness is not working Status in gnome-settings-daemon package in Ubuntu: Incomplete Status in update-manager package in Ubuntu: Invalid Bug description: i updated my laptop after finishing the update , the brightness is not working brightness of screen is very high and i am not able to down the screen brightness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2082162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2081294] Re: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
The analysis below is for 47~rc1, 47.1 fixes the issue by not doing the broken
code path on Linux systems.
I believe this is related to the mutter displayconfig:
We receive this property change:
signal time=1727173020.361584 sender=:1.34 -> destination=(null destination)
serial=11943 path=/org/gnome/Mutter/DisplayConfig;
interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
string "org.gnome.Mutter.DisplayConfig"
array [
dict entry(
string "Backlight"
variant struct {
uint32 7
array [
array [
dict entry(
string "connector"
variantstring "eDP-1"
)
dict entry(
string "active"
variantboolean true
)
]
]
}
)
]
array [
]
This is missing value/min/max, hence the update_mutter_backlight() code does
not enter:
if (g_variant_lookup (monitor, "value", "i",
&backlight->brightness_val)) {
g_variant_lookup (monitor, "min", "i",
&backlight->brightness_min);
g_variant_lookup (monitor, "max", "i",
&backlight->brightness_max);
have_backlight = TRUE;
}
So we set those values to -1:
if (!have_backlight) {
backlight->brightness_val = -1;
backlight->brightness_min = -1;
backlight->brightness_max = -1;
}
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2081294
Title:
gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
Status in GNOME Settings Daemon:
New
Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Bug description:
The key shortcuts as well as slider controls in GNOME for setting the
brightness of the screen on a amdgpu_bl1 laptop stops working after a
sleep/resume cycle. The GNOME logs are the following after pressing
the brightness increase and decrease Fn keys on the keyboard:
12:46:37 (sd-bright): amdgpu_bl1: Failed to write brightness to device:
Invalid argument
12:46:37 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max >
min' failed
12:46:36 (sd-bright): amdgpu_bl1: Failed to write brightness to device:
Invalid argument
12:46:36 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max >
min' failed
12:46:36 (sd-bright): amdgpu_bl1: Failed to write brightness to device:
Invalid argument
12:46:36 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max >
min' failed
12:46:35 (sd-bright): amdgpu_bl1: Failed to write brightness to device:
Invalid argument
12:46:35 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max >
min' failed
12:46:34 (sd-bright): amdgpu_bl1: Failed to write brightness to device:
Invalid argument
12:46:34 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max >
min' failed
Setting the backlight manually using the sysfs interface or the gsd-
backlight-helper program still works:
$ sudo strace /usr/libexec/gsd-backlight-helper
/sys/class/backlight/amdgpu_bl1 15
...
openat(AT_FDCWD, "/sys/class/backlight/amdgpu_bl1/brightness", O_WRONLY) = 4
write(4, "15", 2) = 2
close(4)= 0
This is why I am filing this bug against gnome-settings-daemon and not
the kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/2081294/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2081294] Re: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
I did first see this with kernel 6.11 though, it may be possible that the kernel temporarily returns -1 in those sysfs files -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2081294 Title: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed Status in GNOME Settings Daemon: New Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: The key shortcuts as well as slider controls in GNOME for setting the brightness of the screen on a amdgpu_bl1 laptop stops working after a sleep/resume cycle. The GNOME logs are the following after pressing the brightness increase and decrease Fn keys on the keyboard: 12:46:37 (sd-bright): amdgpu_bl1: Failed to write brightness to device: Invalid argument 12:46:37 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed 12:46:36 (sd-bright): amdgpu_bl1: Failed to write brightness to device: Invalid argument 12:46:36 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed 12:46:36 (sd-bright): amdgpu_bl1: Failed to write brightness to device: Invalid argument 12:46:36 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed 12:46:35 (sd-bright): amdgpu_bl1: Failed to write brightness to device: Invalid argument 12:46:35 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed 12:46:34 (sd-bright): amdgpu_bl1: Failed to write brightness to device: Invalid argument 12:46:34 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed Setting the backlight manually using the sysfs interface or the gsd- backlight-helper program still works: $ sudo strace /usr/libexec/gsd-backlight-helper /sys/class/backlight/amdgpu_bl1 15 ... openat(AT_FDCWD, "/sys/class/backlight/amdgpu_bl1/brightness", O_WRONLY) = 4 write(4, "15", 2) = 2 close(4)= 0 This is why I am filing this bug against gnome-settings-daemon and not the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/2081294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2081294] Re: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
Notably after a resume the backlight control should still be max 255,
e.g. here it is
root@jak-t14-g3:/sys/class/backlight/amdgpu_bl1# grep . * 2>/dev/null
actual_brightness:15
bl_power:0
brightness:15
max_brightness:255
scale:unknown
type:raw
Basically yes it passes -1:
(gdb)
#0 gsd_power_backlight_abs_to_percentage (min=-1, max=-1, value=-1) at
../plugins/power/gpm-common.c:54
__func__ = "gsd_power_backlight_abs_to_percentage"
#1 0x60bb8f841733 in gsd_backlight_set_brightness_val_async
(backlight=0x60bbaeda21d0 [GsdBacklight], value=,
callback=, user_data=, cancellable=0x0)
at ../plugins/power/gsd-backlight.c:480
task_data =
error = 0x0
task = 0x60bbaeda6200 [GTask]
monitor =
percent =
__func__ = { }
** Tags added: rls-oo-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2081294
Title:
gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
Status in GNOME Settings Daemon:
New
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Bug description:
The key shortcuts as well as slider controls in GNOME for setting the
brightness of the screen on a amdgpu_bl1 laptop stops working after a
sleep/resume cycle. The GNOME logs are the following after pressing
the brightness increase and decrease Fn keys on the keyboard:
12:46:37 (sd-bright): amdgpu_bl1: Failed to write brightness to device:
Invalid argument
12:46:37 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max >
min' failed
12:46:36 (sd-bright): amdgpu_bl1: Failed to write brightness to device:
Invalid argument
12:46:36 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max >
min' failed
12:46:36 (sd-bright): amdgpu_bl1: Failed to write brightness to device:
Invalid argument
12:46:36 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max >
min' failed
12:46:35 (sd-bright): amdgpu_bl1: Failed to write brightness to device:
Invalid argument
12:46:35 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max >
min' failed
12:46:34 (sd-bright): amdgpu_bl1: Failed to write brightness to device:
Invalid argument
12:46:34 gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max >
min' failed
Setting the backlight manually using the sysfs interface or the gsd-
backlight-helper program still works:
$ sudo strace /usr/libexec/gsd-backlight-helper
/sys/class/backlight/amdgpu_bl1 15
...
openat(AT_FDCWD, "/sys/class/backlight/amdgpu_bl1/brightness", O_WRONLY) = 4
write(4, "15", 2) = 2
close(4)= 0
This is why I am filing this bug against gnome-settings-daemon and not
the kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/2081294/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2079843] Re: gdm3 fails after release upgrade, have to use lightdm
Reassigning as the upgrade looks good. Consider checking what's up with your SATA controller it goes down and resumes at limited speed a lot: [ 995.233156] ata5: SATA link down (SStatus 1 SControl 310) [ 995.243104] ata5: limiting SATA link speed to 1.5 Gbps [ 997.473147] ata5: SATA link down (SStatus 1 SControl 310) [ 997.476944] ata5: limiting SATA link speed to 1.5 Gbps ** Package changed: ubuntu-release-upgrader (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2079843 Title: gdm3 fails after release upgrade, have to use lightdm Status in gdm3 package in Ubuntu: New Bug description: I upgraded from 22.04 to 24.04 The gdm3 desktop does not come up. I tried uninstalling gdm3 and reinstalling, which did not change the problem. I have installed lightdm as an alternative. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.22 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 6 09:08:33 2024 InstallationDate: Installed on 2023-09-24 (349 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to noble on 2024-09-02 (4 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.init.d.apport: 2024-07-22T08:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2079843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2079819] [NEW] xwayland repeats keypresses, ignores modifier
Public bug reported: I switch into Mattermost with Windows+3 key combination, this causes an endless stream of 3 to be written into the mattermost field until I press another key (similarly for any other number key, I did not try non-numbers) If we look at the keyboard input device with https://github.com/DIGImend/evdev-dump we can see that the key is not stuck, all the input events are correct: /dev/input/event4 1725622057.447632 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622057.447632 EV_KEY KEY_LEFTMETA 0x0002 ^ press windows key /dev/input/event4 1725622057.447632 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.477343 EV_MSC MSC_SCAN 0x0004 /dev/input/event4 1725622057.477343 EV_KEY KEY_3 0x0001 ^ press key 3 /dev/input/event4 1725622057.477343 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.627896 EV_MSC MSC_SCAN 0x0004 /dev/input/event4 1725622057.627896 EV_KEY KEY_3 0x ^ release key 3 /dev/input/event4 1725622057.627896 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.997495 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622057.997495 EV_KEY KEY_LEFTMETA 0x ^ release windows key (now it starts endlessly dumping 3 into mattermost) /dev/input/event4 1725622057.997495 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622059.869769 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622059.869769 EV_KEY KEY_LEFTMETA 0x0001 ^ press windows key again /dev/input/event4 1725622059.869769 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622059.919605 EV_MSC MSC_SCAN 0x0009 /dev/input/event4 1725622059.919605 EV_KEY KEY_8 0x0001 ^ press 8 to switch to the terminal window This only affects Xwayland, native Wayland clients behave correctly. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xwayland 2:24.1.2-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Sep 6 13:26:18 2024 InstallationDate: Installed on 2022-11-26 (650 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular wayland-session ** Description changed: I switch into Mattermost with Windows+3 key combination, this causes an endless stream of 3 to be written into the mattermost field until I - press another key. + press another key (similarly for any other number key, I did not try + non-numbers) If we look at the keyboard input device with https://github.com/DIGImend/evdev-dump we can see that the key is not stuck, all the input events are correct: /dev/input/event4 1725622057.447632 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622057.447632 EV_KEY KEY_LEFTMETA 0x0002 ^ press windows key /dev/input/event4 1725622057.447632 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.477343 EV_MSC MSC_SCAN 0x0004 /dev/input/event4 1725622057.477343 EV_KEY KEY_3 0x0001 ^ press key 3 /dev/input/event4 1725622057.477343 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.627896 EV_MSC MSC_SCAN 0x0004 /dev/input/event4 1725622057.627896 EV_KEY KEY_3 0x ^ release key 3 /dev/input/event4 1725622057.627896 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622057.997495 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622057.997495 EV_KEY KEY_LEFTMETA 0x ^ release windows key (now it starts endlessly dumping 3 into mattermost) /dev/input/event4 1725622057.997495 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622059.869769 EV_MSC MSC_SCAN 0x00DB /dev/input/event4 1725622059.869769 EV_KEY KEY_LEFTMETA 0x0001 ^ press windows key again /dev/input/event4 1725622059.869769 EV_SYN SYN_REPORT 0x /dev/input/event4 1725622059.919605 EV_MSC MSC_SCAN 0x0009 /dev/input/event4 1725622059.919605 EV_KEY KEY_8 0x0001 ^ press 8 to switch to the terminal window - This only affects Xwayland, native Wayland clients behave correctly. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xwayland 2:24.1.2-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Sep 6 13:26:18 2024 InstallationDate: Installed on 2022-11-26 (650 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in
[Desktop-packages] [Bug 2078826] Re: Ubuntu budgie: pulseaudio-module-bluetooth fight
Possibly this can be solved by adding Conflicts: pulseaudio-module- bluetooth to the ubuntu-budgie-desktop-meta package or something. This is similar to bug 2078639 ** Summary changed: - Cannot upgrade budgie from 22.04 to 24.04 + Ubuntu budgie: pulseaudio-module-bluetooth fight ** Also affects: ubuntu-budgie-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2078826 Title: Ubuntu budgie: pulseaudio-module-bluetooth fight Status in pipewire package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Following on screen instruction I used ppa-purge to remove the only ppa package I had, then I remove many package manual installed, but every time I got same error: Broken packages after upgrade: ubuntu- budgie-desktop ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 5.15.0-119.129-generic 5.15.160 Uname: Linux 5.15.0-119-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: Budgie:GNOME Date: Tue Sep 3 16:30:52 2024 InstallationDate: Installed on 2018-02-25 (2382 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-09-03 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-09-03 16:28:46 Requested-By: giorgio (1000) End-Date: 2024-09-03 16:28:46 VarLogDistupgradeApttermlog: Log started: 2024-09-03 16:28:46 Log ended: 2024-09-03 16:28:46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2078826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2073128] Re: Missing compiler flags
FWIW I seem to have added a bunch of $(LDFLAGS) to lines with $(call gb_ExternalProject_get_link_flags,...) - those are unnecessary and upstream likely should complain about those. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2073128 Title: Missing compiler flags Status in libreoffice package in Ubuntu: Fix Committed Bug description: While evaluating libreoffice for the -fno-omit-frame-pointer option presence we identified the following files as having missing flags: libreoffice-core: /usr/lib/libreoffice/program/libstaroffice-0.0-lo.so.0 - All compilations units. libreoffice-draw: /usr/lib/libreoffice/program/libwpftdrawlo.so Various files with relative paths ending in .cpp as - ZMFDocument.cpp - BMIHeader.cpp - BMIParser.cpp - "BMITypes.cpp" - "ZBRHeader.cpp" ⁻ "ZBRParser.cpp" - "ZMF4Header.cpp" - "ZMF4Parser.cpp" It's worth noting that there are some files that do have all the flags; these are specified using absolute file paths and their paths end in .cxx instead of .cpp, such as "/usr/src/libreoffice-4:24.2.4-0ubuntu0.24.04.1/writerperfect/source/draw/CDRImportFilter.cxx" Further investigation is needed why this is failing for these compilation units. Note that this also downgrades some security features: .cxx files are compiled with "GNU C++20 13.2.0 -mno-omit-leaf-frame-pointer -mtune=generic -march=x86-64 -g -O2 -std=c++20 -fvisibility=hidden -finput- charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility-inlines- hidden -fPIC -fno-omit-frame-pointer -fstack-protector-strong -fcf- protection=full -fexceptions -fno-enforce-eh-specs -fasynchronous- unwind-tables -fstack-protector-strong -fstack-clash-protection" .cpp files with "GNU C++20 13.2.0 -mtune=generic -march=x86-64 -ggdb2 -O2 -std=c++20 -finput-charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility- inlines-hidden -fvisibility=hidden -fPIC -fasynchronous-unwind-tables -fstack-protector-strong -fstack-clash-protection -fcf-protection" So -fcf-protection=full is downgraded to just strong -fcf-protection Note that this does not include preprocessor flags, only compilation flags. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2073128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2073128] Re: Missing compiler flags
To add, the dump for noble main is available in
https://magenta.jak-linux.org/ubuntu-archive/noble-main.json
and https://magenta.jak-linux.org/ubuntu-archive/noble-main-
report.src.txt is the report of that. For libreoffice it was:
Source: libreoffice
Total: 68
Good: 66
Bad: 1
libreoffice-core:/usr/lib/libreoffice/program/libstaroffice-0.0-lo.so.0
Missing -fno-omit-frame-pointer
Partial: 1
libreoffice-draw:/usr/lib/libreoffice/program/libwpftdrawlo.so Missing
-fno-omit-frame-pointer (2 / 3)
Different toolchain: 1
libreoffice-core:/usr/lib/libreoffice/program/libskialo.so Compiled by LLVM:
{'Ubuntu clang version 18.1.3 (1)'} (1 / 1)
Unknown: 0
(Note that we deduplicated common strings, hence it shows 2/3 in the partial
case but it was more than 3 units affected).
(Skia is now validated too, oracular's clang dumps compiler flags into
DW_AT_producer too)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2073128
Title:
Missing compiler flags
Status in libreoffice package in Ubuntu:
Fix Committed
Bug description:
While evaluating libreoffice for the -fno-omit-frame-pointer option
presence we identified the following files as having missing flags:
libreoffice-core:
/usr/lib/libreoffice/program/libstaroffice-0.0-lo.so.0
- All compilations units.
libreoffice-draw:
/usr/lib/libreoffice/program/libwpftdrawlo.so
Various files with relative paths ending in .cpp as
- ZMFDocument.cpp
- BMIHeader.cpp
- BMIParser.cpp
- "BMITypes.cpp"
- "ZBRHeader.cpp"
⁻ "ZBRParser.cpp"
- "ZMF4Header.cpp"
- "ZMF4Parser.cpp"
It's worth noting that there are some files that do have all the
flags; these are specified using absolute file paths and their paths
end in .cxx instead of .cpp, such as
"/usr/src/libreoffice-4:24.2.4-0ubuntu0.24.04.1/writerperfect/source/draw/CDRImportFilter.cxx"
Further investigation is needed why this is failing for these
compilation units. Note that this also downgrades some security
features:
.cxx files are compiled with
"GNU C++20 13.2.0 -mno-omit-leaf-frame-pointer -mtune=generic
-march=x86-64 -g -O2 -std=c++20 -fvisibility=hidden -finput-
charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility-inlines-
hidden -fPIC -fno-omit-frame-pointer -fstack-protector-strong -fcf-
protection=full -fexceptions -fno-enforce-eh-specs -fasynchronous-
unwind-tables -fstack-protector-strong -fstack-clash-protection"
.cpp files with
"GNU C++20 13.2.0 -mtune=generic -march=x86-64 -ggdb2 -O2 -std=c++20
-finput-charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility-
inlines-hidden -fvisibility=hidden -fPIC -fasynchronous-unwind-tables
-fstack-protector-strong -fstack-clash-protection -fcf-protection"
So -fcf-protection=full is downgraded to just strong -fcf-protection
Note that this does not include preprocessor flags, only compilation flags.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2073128/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2073128] Re: Missing compiler flags
We have extracted the DW_AT_producer field from the DWARF debug info section, looking for -fno-omit-frame-pointer as part of the 24.04 validation of frame pointer enablement. I have provided a convenient script here that extracts those using python3-pyelftools: https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c There is a separate script to analyse its output, it still needs cleaning up. Particularly note that this only analyses CFLAGS/CXXFLAGS correctness as only compilation units (.o files) have that field; so linker flags and preprocessor flags are not validated (luckily that was enough for us). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2073128 Title: Missing compiler flags Status in libreoffice package in Ubuntu: Fix Committed Bug description: While evaluating libreoffice for the -fno-omit-frame-pointer option presence we identified the following files as having missing flags: libreoffice-core: /usr/lib/libreoffice/program/libstaroffice-0.0-lo.so.0 - All compilations units. libreoffice-draw: /usr/lib/libreoffice/program/libwpftdrawlo.so Various files with relative paths ending in .cpp as - ZMFDocument.cpp - BMIHeader.cpp - BMIParser.cpp - "BMITypes.cpp" - "ZBRHeader.cpp" ⁻ "ZBRParser.cpp" - "ZMF4Header.cpp" - "ZMF4Parser.cpp" It's worth noting that there are some files that do have all the flags; these are specified using absolute file paths and their paths end in .cxx instead of .cpp, such as "/usr/src/libreoffice-4:24.2.4-0ubuntu0.24.04.1/writerperfect/source/draw/CDRImportFilter.cxx" Further investigation is needed why this is failing for these compilation units. Note that this also downgrades some security features: .cxx files are compiled with "GNU C++20 13.2.0 -mno-omit-leaf-frame-pointer -mtune=generic -march=x86-64 -g -O2 -std=c++20 -fvisibility=hidden -finput- charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility-inlines- hidden -fPIC -fno-omit-frame-pointer -fstack-protector-strong -fcf- protection=full -fexceptions -fno-enforce-eh-specs -fasynchronous- unwind-tables -fstack-protector-strong -fstack-clash-protection" .cpp files with "GNU C++20 13.2.0 -mtune=generic -march=x86-64 -ggdb2 -O2 -std=c++20 -finput-charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility- inlines-hidden -fvisibility=hidden -fPIC -fasynchronous-unwind-tables -fstack-protector-strong -fstack-clash-protection -fcf-protection" So -fcf-protection=full is downgraded to just strong -fcf-protection Note that this does not include preprocessor flags, only compilation flags. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2073128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2073128] Re: Missing compiler flags
** Changed in: libreoffice (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2073128 Title: Missing compiler flags Status in libreoffice package in Ubuntu: Fix Committed Bug description: While evaluating libreoffice for the -fno-omit-frame-pointer option presence we identified the following files as having missing flags: libreoffice-core: /usr/lib/libreoffice/program/libstaroffice-0.0-lo.so.0 - All compilations units. libreoffice-draw: /usr/lib/libreoffice/program/libwpftdrawlo.so Various files with relative paths ending in .cpp as - ZMFDocument.cpp - BMIHeader.cpp - BMIParser.cpp - "BMITypes.cpp" - "ZBRHeader.cpp" ⁻ "ZBRParser.cpp" - "ZMF4Header.cpp" - "ZMF4Parser.cpp" It's worth noting that there are some files that do have all the flags; these are specified using absolute file paths and their paths end in .cxx instead of .cpp, such as "/usr/src/libreoffice-4:24.2.4-0ubuntu0.24.04.1/writerperfect/source/draw/CDRImportFilter.cxx" Further investigation is needed why this is failing for these compilation units. Note that this also downgrades some security features: .cxx files are compiled with "GNU C++20 13.2.0 -mno-omit-leaf-frame-pointer -mtune=generic -march=x86-64 -g -O2 -std=c++20 -fvisibility=hidden -finput- charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility-inlines- hidden -fPIC -fno-omit-frame-pointer -fstack-protector-strong -fcf- protection=full -fexceptions -fno-enforce-eh-specs -fasynchronous- unwind-tables -fstack-protector-strong -fstack-clash-protection" .cpp files with "GNU C++20 13.2.0 -mtune=generic -march=x86-64 -ggdb2 -O2 -std=c++20 -finput-charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility- inlines-hidden -fvisibility=hidden -fPIC -fasynchronous-unwind-tables -fstack-protector-strong -fstack-clash-protection -fcf-protection" So -fcf-protection=full is downgraded to just strong -fcf-protection Note that this does not include preprocessor flags, only compilation flags. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2073128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2073128] Re: Missing compiler flags
Initial patch, currently test compiling, I hope I have enough space. ** Patch added: "external-flags.patch" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2073128/+attachment/5812818/+files/external-flags.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2073128 Title: Missing compiler flags Status in libreoffice package in Ubuntu: New Bug description: While evaluating libreoffice for the -fno-omit-frame-pointer option presence we identified the following files as having missing flags: libreoffice-core: /usr/lib/libreoffice/program/libstaroffice-0.0-lo.so.0 - All compilations units. libreoffice-draw: /usr/lib/libreoffice/program/libwpftdrawlo.so Various files with relative paths ending in .cpp as - ZMFDocument.cpp - BMIHeader.cpp - BMIParser.cpp - "BMITypes.cpp" - "ZBRHeader.cpp" ⁻ "ZBRParser.cpp" - "ZMF4Header.cpp" - "ZMF4Parser.cpp" It's worth noting that there are some files that do have all the flags; these are specified using absolute file paths and their paths end in .cxx instead of .cpp, such as "/usr/src/libreoffice-4:24.2.4-0ubuntu0.24.04.1/writerperfect/source/draw/CDRImportFilter.cxx" Further investigation is needed why this is failing for these compilation units. Note that this also downgrades some security features: .cxx files are compiled with "GNU C++20 13.2.0 -mno-omit-leaf-frame-pointer -mtune=generic -march=x86-64 -g -O2 -std=c++20 -fvisibility=hidden -finput- charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility-inlines- hidden -fPIC -fno-omit-frame-pointer -fstack-protector-strong -fcf- protection=full -fexceptions -fno-enforce-eh-specs -fasynchronous- unwind-tables -fstack-protector-strong -fstack-clash-protection" .cpp files with "GNU C++20 13.2.0 -mtune=generic -march=x86-64 -ggdb2 -O2 -std=c++20 -finput-charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility- inlines-hidden -fvisibility=hidden -fPIC -fasynchronous-unwind-tables -fstack-protector-strong -fstack-clash-protection -fcf-protection" So -fcf-protection=full is downgraded to just strong -fcf-protection Note that this does not include preprocessor flags, only compilation flags. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2073128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078721] Re: nautilus crashed with SIGSEGV
backtrace of another crash that manifests basically the same way but later, in a different directory I guess as I stopped typing in the search. ** Attachment added: "gdb-nautilus.txt" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2078721/+attachment/5812744/+files/gdb-nautilus.txt ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2078721 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: New Bug description: This crash happened while trying to attach monitors.xml in bug 2078060, using the file portal I believe and searching in there ProblemType: Crash DistroRelease: Ubuntu 24.10 Package: nautilus 1:47~beta.1-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Sep 2 18:41:28 2024 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-11-26 (646 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x5922257b1ac9:mov(%rax),%rbx PC (0x5922257b1ac9) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rbx" ok SegvReason: reading unknown VMA Signal: 11 SignalName: SIGSEGV SourcePackage: nautilus StacktraceTop: ?? () ?? () ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libffi.so.8 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sudo separator: usr_lib_nautilus: file-roller 44.3-1 nautilus-extension-gnome-terminal 3.52.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2078721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078723] Re: gnome-control-center crashed with SIGSEGV in g_signal_emit_valist()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2078723 Title: gnome-control-center crashed with SIGSEGV in g_signal_emit_valist() Status in gnome-control-center package in Ubuntu: New Bug description: While analysing bug 2078060 after toggling off fractional scaling and the shell crashing (bug 2078722), following a new login, gnome- control-center now crashes reliably when selecting built-in display. ProblemType: Crash DistroRelease: Ubuntu 24.10 Package: gnome-control-center 1:47~beta-2ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Sep 2 18:43:40 2024 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-11-26 (646 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) ProcCmdline: /usr/bin/gnome-control-center SegvAnalysis: Segfault happened at: 0x5e684488469e:mov(%rax),%rax PC (0x5e684488469e) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SignalName: SIGSEGV SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2078723/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078060] Re: gnome-control-center 47~beta-1ubuntu2 does not accept fractional scales
Attaching monitors.xml and trying to debug this lead to 3 crashes: https://bugs.launchpad.net/bugs/2078721 https://bugs.launchpad.net/bugs/2078722 https://bugs.launchpad.net/bugs/2078723 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2078060 Title: gnome-control-center 47~beta-1ubuntu2 does not accept fractional scales Status in gnome-control-center package in Ubuntu: New Bug description: Fractional scale support seems broken, it says the configuration cannot be applied due to "hardware limitations". If you already have configured fractional scaling; any changes to the output essentially can't be saved. e.g. you can't switch to external-only (with fractionally scaled external display) from the settings app; you can however switch using the function key. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-control-center 1:47~beta-2ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Aug 28 15:43:37 2024 InstallationDate: Installed on 2022-11-26 (641 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2078060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078060] Re: gnome-control-center 47~beta-1ubuntu2 does not accept fractional scales
Current monitors.xml attached ** Attachment added: "monitors.xml" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2078060/+attachment/5812408/+files/monitors.xml -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2078060 Title: gnome-control-center 47~beta-1ubuntu2 does not accept fractional scales Status in gnome-control-center package in Ubuntu: New Bug description: Fractional scale support seems broken, it says the configuration cannot be applied due to "hardware limitations". If you already have configured fractional scaling; any changes to the output essentially can't be saved. e.g. you can't switch to external-only (with fractionally scaled external display) from the settings app; you can however switch using the function key. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-control-center 1:47~beta-2ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Aug 28 15:43:37 2024 InstallationDate: Installed on 2022-11-26 (641 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2078060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078676] Re: wifi not remembering login password
** Package changed: ubuntu-release-upgrader (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2078676 Title: wifi not remembering login password Status in network-manager package in Ubuntu: New Bug description: wifi login not recalling password used. asks for password after sleep or idle time - not storing password entered or else not recalling the stored password entered for any user. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.22 ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12 Uname: Linux 6.8.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE Date: Mon Sep 2 04:23:44 2024 InstallationDate: Installed on 2024-06-05 (89 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2078676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078642] Re: Ubuntu upgrade 22 to 24 failed.
The dependencies of gnome-settings-daemon are: Depends: libspa-0.2-bluetooth | pulseaudio-module-bluetooth, pipewire-audio | pulseaudio, Recommends: pipewire-audio Because pulseaudio and pulseaudio-module-bluetooth are installed, APT reorders those to the front, and this later on causes conflicts. I'm not sure if this was intentional. There are other dependency solutions here, if you run APT itself, it will install pipewire without an audio component. I don't think it makes sense to quirk this in u-r-u, it may make sense to drop the pulseaudio alternatives or add Depends: on pipewire-audio, libspa-0.2-bluetooth to the desktop meta packages that should pull it in. ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-budgie-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2078642 Title: Ubuntu upgrade 22 to 24 failed. Status in gnome-settings-daemon package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: "ubuntu-bug ubuntu-release-upgrader-core" the updater failed to collect system informations I don't know and understand more ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 5.15.0-119.129-generic 5.15.160 Uname: Linux 5.15.0-119-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: Budgie:GNOME Date: Sun Sep 1 22:35:42 2024 InstallationDate: Installed on 2020-07-27 (1497 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-09-01 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2078642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2065932] Re: Only adds the weak key for PPAs dual-signed with both weak and strong keys
Dual signing started back then but it finished in July and the default key exposed was switched to the newest for August. ** Changed in: software-properties (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2065932 Title: Only adds the weak key for PPAs dual-signed with both weak and strong keys Status in software-properties package in Ubuntu: Invalid Bug description: After running ‘add-apt-repository ppa:git-core/ppa’ on Ubuntu 24.04, ‘apt update’ gives this warning: W: https://ppa.launchpadcontent.net/git- core/ppa/ubuntu/dists/noble/InRelease: Signature by key E1DD270288B4E6030699E45FA1715D88E1DF1F24 uses weak algorithm (rsa1024) But this PPA is dual-signed by two keys, only one of which is weak. add-apt-repository has chosen to install the rsa1024 key in sources.list.d. It should choose the rsa4096 key instead. $ curl 'https://ppa.launchpadcontent.net/git-core/ppa/ubuntu/dists/noble/InRelease' | gpgv … gpg: Signature made Thu 16 May 2024 05:22:18 AM PDT gpg:using RSA key F911AB184317630C59970973E363C90F8F1B6217 gpg: Good signature from "Launchpad PPA for Ubuntu Git Maintainers" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: F911 AB18 4317 630C 5997 0973 E363 C90F 8F1B 6217 gpg: Signature made Thu 16 May 2024 05:22:18 AM PDT gpg:using RSA key E1DD270288B4E6030699E45FA1715D88E1DF1F24 gpg: Good signature from "Launchpad PPA for Ubuntu Git Maintainers" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E1DD 2702 88B4 E603 0699 E45F A171 5D88 E1DF 1F24 $ gpg --list-keys F911AB184317630C59970973E363C90F8F1B6217 E1DD270288B4E6030699E45FA1715D88E1DF1F24 pub rsa1024 2009-01-22 [SC] E1DD270288B4E6030699E45FA1715D88E1DF1F24 uid [ unknown] Launchpad PPA for Ubuntu Git Maintainers pub rsa4096 2024-04-24 [SC] F911AB184317630C59970973E363C90F8F1B6217 uid [ unknown] Launchpad PPA for Ubuntu Git Maintainers Context: https://discourse.ubuntu.com/t/new-requirements-for-apt- repository-signing-in-24-04/42854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2065932/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078443] Re: Upgrade from 22.04 to 24.04.1 failed - firefox package
It seems we failed to install libglib2.0-0t64 and only removed libglib2.0. We had the bug multiple times before, neither snapd nor the transitional packages depend on libglib2.0-0(t64) despite needing them for the desktop hooks, but I do not recall what the outcome of that was and why it is resurfacing now ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Triaged ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2078443 Title: Upgrade from 22.04 to 24.04.1 failed - firefox package Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Triaged Bug description: Trying to upgrade my updated 22.04 to 24.04 using do-release-upgrade -d Upgrade failed Errors were encountered while processing: /var/cache/apt/archives/firefox_1%3a1snap1-0ubuntu5_amd64.deb ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/firefox.0.crash' /usr/bin/gdbus: error while loading shared libraries: libgio-2.0.so.0: cannot open shared object file: No such file or directory /usr/bin/gdbus: error while loading shared libraries: libgio-2.0.so.0: cannot open shared object file: No such file or directory /usr/bin/gdbus: error while loading shared libraries: libgio-2.0.so.0: cannot open shared object file: No such file or directory Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Description:Ubuntu 22.04.4 LTS Release:22.04 firefox: Installed: 129.0.2+build1-0ubuntu0.22.04.1~mt1 Candidate: 1:1snap1-0ubuntu5 Version table: 1:1snap1-0ubuntu5 500 500 http://fr.archive.ubuntu.com/ubuntu noble/main amd64 Packages *** 129.0.2+build1-0ubuntu0.22.04.1~mt1 100 100 /var/lib/dpkg/status I don't use firefox snap package as my home directory is in /nethome/ and not in /home/ (is there a way to fix this ?) I had to remove the firefox snap package and install firefox using dpkg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2078443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013545] Re: /usr/sbin/apt-add-repository will not function with IPv6 proxies called by address
** Package changed: software-properties (Ubuntu) => python-httplib2
(Ubuntu)
** Changed in: python-httplib2 (Ubuntu)
Status: New => Fix Released
** Also affects: python-httplib2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: python-httplib2 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/2013545
Title:
/usr/sbin/apt-add-repository will not function with IPv6 proxies
called by address
Status in python-httplib2 package in Ubuntu:
Fix Released
Status in python-httplib2 source package in Focal:
New
Status in python-httplib2 source package in Jammy:
New
Bug description:
It appears that if one has an HTTP or HTTPS proxy called out
specifically by IPv6 address rather than hostname, it will fail.
Placing an entry in /etc/hosts, or the proxy into DNS (and calling by
hostname) will function.
failure steps:
1) set proxy environment variables
export http_proxy="http://[2001:db8:f00::2]:3128/";
export https_proxy="http://[2001:db8:f00::2]:3128/";
2) Attempt to add repository (in this case, a PPA):
apt-add-repository ppa:ansible/ansible
3) Enjoy the resulting stack trace:
Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 347, in main
shortcut = handler(source, **shortcut_params)
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line
40, in shortcut_handler
return handler(shortcut, **kwargs)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 82,
in __init__
if self.lpppa.publish_debug_symbols:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 120,
in lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 107,
in lpteam
self._lpteam = self.lp.people(self.teamname)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98,
in lp
self._lp = login_func("%s.%s" % (self.__module__,
self.__class__.__name__),
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 494,
in login_anonymously
return cls(
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 230,
in __init__
super(Launchpad, self).__init__(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line
472, in __init__
self._wadl = self._browser.get_wadl_application(self._root_uri)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
447, in get_wadl_application
response, content = self._request(url, media_type=wadl_type)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
389, in _request
response, content = self._request_and_retry(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
359, in _request_and_retry
response, content = self._connection.request(
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1578, in
request
conn = self.connections[conn_key] = connection_type(
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1095, in
__init__
self.proxy_info = proxy_info("https")
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 926, in
proxy_info_from_environment
return proxy_info_from_url(url, method, noproxy=None)
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 950, in
proxy_info_from_url
port = int(port)
ValueError: invalid literal for int() with base 10: 'db8:f00::2]:3128'
Ubuntu Release:
# lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Package version:
# apt-cache policy software-properties-common
software-properties-common:
Installed: 0.99.22.6
Candidate: 0.99.22.6
Version table:
*** 0.99.22.6 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
0.99.22 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-httplib2/+bug/2013545/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2077940] Re: setuptools v72 removed the test command
This is a weird thing, new dh-python seemingly just removed running the test instead of switching to python -m unittest discover which would have been arguably the right fix? ** Also affects: dh-python (Ubuntu) Importance: Undecided Status: New ** No longer affects: dh-python (Ubuntu) ** Tags removed: rls-oo-incoming ** Tags added: foundations-todo ** Changed in: software-properties (Ubuntu) Milestone: None => ubuntu-24.10-beta ** Also affects: software-properties (Ubuntu Oracular) Importance: High Status: Confirmed ** Changed in: software-properties (Ubuntu Oracular) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2077940 Title: setuptools v72 removed the test command Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Oracular: Triaged Bug description: the autopkg tests fail with setuptools v72: v72.0.0 === Deprecations and Removals - - The test command has been removed. Users relying on 'setup.py test' will need to migrate to another test runner or pin setuptools before this version. (#931) [...] 121s autopkgtest [16:15:43]: test run-tests: [--- 121s MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER) 121s glx: failed to create drisw screen 121s 121s (setup.py:4590): dbind-WARNING **: 16:15:43.530: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files 121s ERROR: Python module Queue not found 121s ERROR: Python module urllib2 not found 122s ERROR: Python module Queue not found 122s ERROR: Python module ConfigParser not found 122s /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:268: UserWarning: Unknown distribution option: 'test_suite' 122s warnings.warn(msg) 122s usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] 122sor: setup.py --help [cmd1 cmd2 ...] 122sor: setup.py --help-commands 122sor: setup.py cmd --help 122s 122s error: invalid command 'test' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2077940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078061] [NEW] Internal screen touch sensor remains active when only external display is enabled
Public bug reported: I connected the ThinkPad T14 G3 AMD to an external screen with the lid open, turned off the internal screen, and to my surprise when my cat walked over the screen she moved the windows on the external screen. 🙀 Now this may be useful and I am not sure it is a bug, I'll let other people decide. You just don't see where you tap on the screen with the internal one not showing anything, but maybe there are valid use cases. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-shell 47~beta-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Aug 28 15:53:55 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-26 (641 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) RelatedPackageVersions: mutter-common 47~beta-3ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular rls-oo-incoming third-party-packages wayland-session ** Tags added: rls-oo-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2078061 Title: Internal screen touch sensor remains active when only external display is enabled Status in gnome-shell package in Ubuntu: New Bug description: I connected the ThinkPad T14 G3 AMD to an external screen with the lid open, turned off the internal screen, and to my surprise when my cat walked over the screen she moved the windows on the external screen. 🙀 Now this may be useful and I am not sure it is a bug, I'll let other people decide. You just don't see where you tap on the screen with the internal one not showing anything, but maybe there are valid use cases. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-shell 47~beta-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Aug 28 15:53:55 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-26 (641 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) RelatedPackageVersions: mutter-common 47~beta-3ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2078061/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078060] Re: gnome-control-center 47~beta-1ubuntu2 does not accept fractional scales
** Tags added: rls-oo-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2078060 Title: gnome-control-center 47~beta-1ubuntu2 does not accept fractional scales Status in gnome-control-center package in Ubuntu: New Bug description: Fractional scale support seems broken, it says the configuration cannot be applied due to "hardware limitations". If you already have configured fractional scaling; any changes to the output essentially can't be saved. e.g. you can't switch to external-only (with fractionally scaled external display) from the settings app; you can however switch using the function key. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-control-center 1:47~beta-2ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Aug 28 15:43:37 2024 InstallationDate: Installed on 2022-11-26 (641 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2078060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078060] [NEW] gnome-control-center 47~beta-1ubuntu2 does not accept fractional scales
Public bug reported: Fractional scale support seems broken, it says the configuration cannot be applied due to "hardware limitations". If you already have configured fractional scaling; any changes to the output essentially can't be saved. e.g. you can't switch to external-only (with fractionally scaled external display) from the settings app; you can however switch using the function key. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-control-center 1:47~beta-2ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Aug 28 15:43:37 2024 InstallationDate: Installed on 2022-11-26 (641 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2078060 Title: gnome-control-center 47~beta-1ubuntu2 does not accept fractional scales Status in gnome-control-center package in Ubuntu: New Bug description: Fractional scale support seems broken, it says the configuration cannot be applied due to "hardware limitations". If you already have configured fractional scaling; any changes to the output essentially can't be saved. e.g. you can't switch to external-only (with fractionally scaled external display) from the settings app; you can however switch using the function key. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-control-center 1:47~beta-2ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.30.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Aug 28 15:43:37 2024 InstallationDate: Installed on 2022-11-26 (641 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2078060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2073128] Re: Missing compiler flags
I'd wager this is the issue where it's not forwarding flags to the external build system: gb_ExternalProject_get_build_flags = $(call gb_LinkTarget__get_debugflags,ExternalProject_$(1)) Notably, gb_ExternalProject_get_link_flags = $(LDFLAGS) $(USE_LD) $(call gb_LinkTarget__get_debugldflags,ExternalProject_$(1)) passes LDFLAGS through. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2073128 Title: Missing compiler flags Status in libreoffice package in Ubuntu: New Bug description: While evaluating libreoffice for the -fno-omit-frame-pointer option presence we identified the following files as having missing flags: libreoffice-core: /usr/lib/libreoffice/program/libstaroffice-0.0-lo.so.0 - All compilations units. libreoffice-draw: /usr/lib/libreoffice/program/libwpftdrawlo.so Various files with relative paths ending in .cpp as - ZMFDocument.cpp - BMIHeader.cpp - BMIParser.cpp - "BMITypes.cpp" - "ZBRHeader.cpp" ⁻ "ZBRParser.cpp" - "ZMF4Header.cpp" - "ZMF4Parser.cpp" It's worth noting that there are some files that do have all the flags; these are specified using absolute file paths and their paths end in .cxx instead of .cpp, such as "/usr/src/libreoffice-4:24.2.4-0ubuntu0.24.04.1/writerperfect/source/draw/CDRImportFilter.cxx" Further investigation is needed why this is failing for these compilation units. Note that this also downgrades some security features: .cxx files are compiled with "GNU C++20 13.2.0 -mno-omit-leaf-frame-pointer -mtune=generic -march=x86-64 -g -O2 -std=c++20 -fvisibility=hidden -finput- charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility-inlines- hidden -fPIC -fno-omit-frame-pointer -fstack-protector-strong -fcf- protection=full -fexceptions -fno-enforce-eh-specs -fasynchronous- unwind-tables -fstack-protector-strong -fstack-clash-protection" .cpp files with "GNU C++20 13.2.0 -mtune=generic -march=x86-64 -ggdb2 -O2 -std=c++20 -finput-charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility- inlines-hidden -fvisibility=hidden -fPIC -fasynchronous-unwind-tables -fstack-protector-strong -fstack-clash-protection -fcf-protection" So -fcf-protection=full is downgraded to just strong -fcf-protection Note that this does not include preprocessor flags, only compilation flags. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2073128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2073128] Re: Missing compiler flags
Rico, any suggestion where to go from here? It seems all vendored libraries are compiled without the right compiler flags but I don't want to waste hours digging deep into that convoluted build system and I hope you can point me in the right direction. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2073128 Title: Missing compiler flags Status in libreoffice package in Ubuntu: New Bug description: While evaluating libreoffice for the -fno-omit-frame-pointer option presence we identified the following files as having missing flags: libreoffice-core: /usr/lib/libreoffice/program/libstaroffice-0.0-lo.so.0 - All compilations units. libreoffice-draw: /usr/lib/libreoffice/program/libwpftdrawlo.so Various files with relative paths ending in .cpp as - ZMFDocument.cpp - BMIHeader.cpp - BMIParser.cpp - "BMITypes.cpp" - "ZBRHeader.cpp" ⁻ "ZBRParser.cpp" - "ZMF4Header.cpp" - "ZMF4Parser.cpp" It's worth noting that there are some files that do have all the flags; these are specified using absolute file paths and their paths end in .cxx instead of .cpp, such as "/usr/src/libreoffice-4:24.2.4-0ubuntu0.24.04.1/writerperfect/source/draw/CDRImportFilter.cxx" Further investigation is needed why this is failing for these compilation units. Note that this also downgrades some security features: .cxx files are compiled with "GNU C++20 13.2.0 -mno-omit-leaf-frame-pointer -mtune=generic -march=x86-64 -g -O2 -std=c++20 -fvisibility=hidden -finput- charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility-inlines- hidden -fPIC -fno-omit-frame-pointer -fstack-protector-strong -fcf- protection=full -fexceptions -fno-enforce-eh-specs -fasynchronous- unwind-tables -fstack-protector-strong -fstack-clash-protection" .cpp files with "GNU C++20 13.2.0 -mtune=generic -march=x86-64 -ggdb2 -O2 -std=c++20 -finput-charset=UTF-8 -fmessage-length=0 -fno-common -fvisibility- inlines-hidden -fvisibility=hidden -fPIC -fasynchronous-unwind-tables -fstack-protector-strong -fstack-clash-protection -fcf-protection" So -fcf-protection=full is downgraded to just strong -fcf-protection Note that this does not include preprocessor flags, only compilation flags. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2073128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2077162] Re: [FFe/SRU] add-apt-repository --refresh-keys
** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Oracular) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2077162 Title: [FFe/SRU] add-apt-repository --refresh-keys Status in software-properties package in Ubuntu: New Status in software-properties source package in Focal: New Status in software-properties source package in Jammy: New Status in software-properties source package in Noble: New Status in software-properties source package in Oracular: New Bug description: [Impact] We want to provide an easy tool to allow users to refresh signing keys. This feature works for both deb822 sources and classic sources. [Test plan] For all releases: 1. Add a weak PPA, ensure its key is refreshed. 2. Add a weak private PPA and ensure that it does not fail the process, then retry with --login, ensure we only see one login request. 3. Ensure non-PPA repositories are notified about as not being refreshable 4. Ensure key files not refreshable via PPA mechanism are notified For 24.04: A. Add a weak PPA as a .list (23.10), ensure its key is refreshed. B. Add a superflous key for a deb822 source with Signed-By and observe key file deletion. [Where problems could occur] The new feature could not work in all cases. It is luckily self contained in one (too) large function The launchpad login caching could possibly cause some problems, there may be bugs there, but our test plan checks for both non-login and login cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2077162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2077162] [NEW] [FFe/SRU] add-apt-repository --refresh-keys
Public bug reported: [Impact] We want to provide an easy tool to allow users to refresh signing keys. This feature works for deb822 sources, classic sources are TBD. [Test plan] We have multiple test cases: 1. Add a weak PPA, ensure its key is refreshed. 2. Add a weak private PPA and ensure that it does not fail the process, then retry with --login 3. Add a second private PPA and ensure that we only see a single login request with --login [Where problems could occur] The new feature could not work in all cases. The launchpad login caching could possibly cause some problems, there may be bugs there, but our test plan checks for both non-login and login cases. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2077162 Title: [FFe/SRU] add-apt-repository --refresh-keys Status in software-properties package in Ubuntu: New Bug description: [Impact] We want to provide an easy tool to allow users to refresh signing keys. This feature works for deb822 sources, classic sources are TBD. [Test plan] We have multiple test cases: 1. Add a weak PPA, ensure its key is refreshed. 2. Add a weak private PPA and ensure that it does not fail the process, then retry with --login 3. Add a second private PPA and ensure that we only see a single login request with --login [Where problems could occur] The new feature could not work in all cases. The launchpad login caching could possibly cause some problems, there may be bugs there, but our test plan checks for both non-login and login cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2077162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061708] Re: Yubikey stopped working after noble upgrade
I don't recommend running with pcscd, it's much more stable to run with
direct access, but I do not know why it doesn't seem to work for you, it
certainly does for me.
It failing with pcscd is nice, it not telling us why and how to fix it
is bad UX though.
** Changed in: gnupg2 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/2061708
Title:
Yubikey stopped working after noble upgrade
Status in Arch Linux on Launchpad:
Fix Released
Status in gnupg2 package in Ubuntu:
Triaged
Status in pcsc-lite package in Ubuntu:
Invalid
Bug description:
In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
since upgrading to Noble I get the following trying to access it.
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
If I run this as root it works:
$ sudo gpg --card-status
Reader ...: 1050:0407:X:0
Application ID ...: D27600012401000609082616
Application type .: OpenPGP
Version ..: 2.1
Manufacturer .: Yubico
Serial number :
Name of cardholder: [not set]
Language prefs ...: [not set]
Salutation ...:
URL of public key : [not set]
Login data ...: [not set]
Signature PIN : not forced
Key attributes ...: rsa4096 rsa4096 rsa2048
Max. PIN lengths .: 127 127 127
PIN retry counter : 10 0 10
Signature counter : 1172
UIF setting ..: Sign=off Decrypt=off Auth=off
Signature key :
created :
Encryption key:
created :
Authentication key: [none]
General key info..: [none]
If I manually run pcscd.service then it stops working both as root and
a user.
$ sudo pkill -9 scdaemon
$ sudo systemctl start pcscd.service
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
$ sudo gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
It might be worth mentioning I'm accessing the machine over SSH, so I
also did experiment with a polkit rule like this:
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_card" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
polkit.addRule(function(action, subject) {
if (action.id == "org.debian.pcsc-lite.access_pcsc" &&
subject.isInGroup("sudo")) {
return polkit.Result.YES;
}
});
Added into /etc/polkit-1/rules.d/99-pcscd.rules and then reloading
polkit.service in case this was a polkit issue, but this didn't do
anything.
Versions in noble:
pcscd: 2.0.3-1build1
libpcslite1: 2.0.3-1build1
gnupg: 2.4.4-2ubuntu17
scdaemon: 2.4.4-2ubuntu17
To manage notifications about this bug go to:
https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822
Yeah sorry folks this was a bit awkward, to avoid respinning other images we temporarily spun out software-properties-qt into its own package (0.99.48.1) and fixed it there, and hence there was no bug closure or anything. This will fold back into the main package in a zero-day SRU in 0.99.49. ** Also affects: software-properties-qt (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties-qt (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: [SRU] Software Sources is not compatible with deb822 Status in software-properties package in Ubuntu: Confirmed Status in software-properties-qt package in Ubuntu: Fix Released Status in software-properties source package in Noble: Confirmed Status in software-properties-qt source package in Noble: Fix Released Bug description: [ Impact ] Ubuntu 24.04 now uses deb822 to represent software sources for deb packages, instead of /etc/apt/sources.list. The complete rationale for this change can be found here: https://discourse.ubuntu.com/t/spec- apt-deb822-sources-by-default/29333 software-properties has two graphical frontends for editing these software sources, one is GTK-based and the other is Qt-based. When the underlying change to deb822 sources was made, the GTK-based frontend and the DBus backend interface gained support. The original bug report shown below informed us of the lack of deb822 support in the Qt frontend, which results in a broken, non-functional interface when attempting to view or edit most values on the first two tabs. The fix for this is to implement a Qt dialog for deb822 sources that somewhat matches the existing GTK interface. [ Test Plan ] Install software-properties-qt 0.99.48 or earlier. Reproducing the bug: 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. 2. Observe that all four checkboxes on the Ubuntu Software tab (main, universe, restricted, and multiverse) are unchecked. 3. Move to the Other Software tab and observe that there are no items in the list. Upgrade to software-properties-qt 0.99.49. Intended functionality: 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. 2. Observe that one or more checkboxes on the Ubuntu Software tab (representing main, universe, restricted, or multiverse) are checked. Toggle one or more of the checkboxes. 3. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. 4. Switch to the Other Software tab, there should be one item in the list. 5. Select that item, then click Edit at the bottom of the dialog. Make a modification to every field on the screen, or a combination of fields you would like to test. All fields should work. 6. Click the OK button at the bottom of the dialog to confirm the changes, then click Edit for that item again. The changes you made should be reflected (meaning, the changes were saved.) 7. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. [ Where problems could occur ] This is well-tested code. That being said, the following small edge cases exist: - If you create a very large amount of rows, it infinitely expands the dialog without a scroll wheel. This is the same functionality as the GTK frontend. - Error validation is not performed on the deb822 lines, they are simply written to the ubuntu.sources file. This is good as a starting point, but also relies on the appropriate update notifier handling these errors. This is the same functionality as the GTK frontend. In a future update, this functionality could be broken by one or more of the following underlying changes: - Changes to the software-properties backend which are only implemented for the GTK frontend. - Changes to the location or formatting of the ubuntu.sources file. - Regressions in the Python bindings for Qt 5, which are rare but possible. - Regressions in Python itself. [ Other Info ] Ubuntu Studio's live ISO and installed system are affected by this. Only Lubuntu's installed system is affected by this. [ Original Report ] Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Used command sudo do-release-upgrade -d Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architec
[Desktop-packages] [Bug 2062979] Re: unable to create ubuntu-noble image due to dictionaries-common config failure
I'm unsubscribing as I only did a no-change rebuild. I'd generally advise against using LC_ALL=C in any setting however, it's generally a bad idea and you should use LC_ALL=C.UTF-8 instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aspell in Ubuntu. https://bugs.launchpad.net/bugs/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure Status in aspell package in Ubuntu: New Status in dictionaries-common package in Ubuntu: New Bug description: this is running with LC_ALL=C the following are output in terminal when configuring dictionaries- common Setting up dictionaries-common (1.29.7) ... Processing triggers for dictionaries-common (1.29.7) ... aspell-autobuildhash: processing: en [en-common]. Error: /dev/null:1: The key "/usr/bin/aspell" is unknown. Undefined subroutine &main::subst called at /usr/sbin/aspell-autobuildhash line 54. dpkg: error processing package dictionaries-common (--configure): installed dictionaries-common package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: dictionaries-common this worked without issues when I last built images of ubuntu-noble in late February 2024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2060038] [NEW] splix version 2.0.0+svn315-7fakesync1ubuntu0.22.04.1 in jammy is higher than versions in mantic and noble
Public bug reported: This package cannot be upgraded, we're going to need a mantic SRU and an ubuntu1 for noble. ** Affects: splix (Ubuntu) Importance: High Assignee: Till Kamppeter (till-kamppeter) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to splix in Ubuntu. https://bugs.launchpad.net/bugs/2060038 Title: splix version 2.0.0+svn315-7fakesync1ubuntu0.22.04.1 in jammy is higher than versions in mantic and noble Status in splix package in Ubuntu: New Bug description: This package cannot be upgraded, we're going to need a mantic SRU and an ubuntu1 for noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/splix/+bug/2060038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
I'm agreeing with desktop in following Fedora to bump to 1048576, the precedence makes this safe, and this I consider this a bug fix for crashing software and not a feature request. ** Changed in: procps (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: procps (Ubuntu) Status: Triaged => In Progress ** Changed in: procps (Ubuntu) Status: In Progress => Fix Committed ** No longer affects: ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gamemode in Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in gamemode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in procps package in Ubuntu: Fix Committed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
Subscribing Canonical desktop team to get their input. Basically the ask is to ship this file: https://src.fedoraproject.org/rpms/systemd/blob/f39/f/10-map-count.conf I believe if we do it should be shipped in procps; or possibly, gamemode should set that option? ** Also affects: procps (Ubuntu) Importance: Undecided Status: New ** Also affects: gamemode (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gamemode in Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in Ubuntu: Confirmed Status in gamemode package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in procps package in Ubuntu: New Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
** Tags removed: rls-nn-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054716 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I was working on recreating bug 2054319 and did so by modifying my /etc/apt/sources.list file from jammy to noble and installing polkit and all its dependencies. bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic linux-headers-6.5.0-14-generic linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic linux-modules-extra-6.2.0-36-generic linux-modules-extra-6.5.0-14-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1 locales systemd systemd-dev systemd-oomd systemd-resolved systemd-sysv systemd-timesyncd udev Suggested packages: glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container systemd-homed systemd-userdbd systemd-boot libqrencode4 libtss2-rc0 Recommended packages: libnss-nis libnss-nisplus The following NEW packages will be installed: libduktape207 libsystemd-shared systemd-dev systemd-resolved The following packages will be upgraded: gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 libzstd1 locales pkexec policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev 26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded. Need to get 34.9 MB of archives. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Feb 22 08:46:48 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-02 (112 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885646] Re: RM ring FTBFS
** Tags removed: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1885646 Title: RM ring FTBFS Status in nettle package in Ubuntu: Incomplete Status in ring package in Ubuntu: Fix Released Status in ring package in Debian: Fix Released Bug description: Please remove ring 20190215.1.f152c98~ds1-1build4 groovy-proposed ring 20190215.1.f152c98~ds1-1build2 groovy-release FTBFS, RC-buggy, removed from testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1885646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
Deferring tracking to the other bugs ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid ** Changed in: policykit-1 (Ubuntu) Status: New => Invalid ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid ** Tags removed: rls-nn-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054319 Title: System installed from jammy point release iso cannot upgrade to noble Status in gnome-shell package in Ubuntu: Invalid Status in policykit-1 package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: We have different crashes being encountered. In our auto-upgrade- testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though. When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash 600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 14:34:19.370597600 +:/var/crash/polkitd.0.crash Date: Mon Feb 19 14:53:39 2024 InstallationDate: Installed on 2024-02-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
** No longer affects: tracker-miners (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054319 Title: System installed from jammy point release iso cannot upgrade to noble Status in gnome-shell package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: We have different crashes being encountered. In our auto-upgrade- testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though. When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash 600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 14:34:19.370597600 +:/var/crash/polkitd.0.crash Date: Mon Feb 19 14:53:39 2024 InstallationDate: Installed on 2024-02-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble
So the script here fails to run snap info firefox It was pointed out it managed to upgrade the chromium snap before it, so not sure what's going on, this seems like a job for the snapd team to investigate. ** Package changed: ubuntu-release-upgrader (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade fails consistently at the `Installing the firefox snap` step. This was first detected on Jenkins [1], then reproduced locally with `auto-upgrade-testing`, then finally by manually running a `do- release-upgrade -d` in a VM. [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade- list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull (Jenkins full log attached) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.17 ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Fri Nov 17 18:24:22 2023 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045455] Re: add-apt-repository crashed with --- in _request()
Nevermind, a non-existent or private PPA has been tried to add and software-properties should properly surface the error to you. ** Changed in: software-properties (Ubuntu) Status: Incomplete => Triaged ** Tags removed: rls-nn-incoming ** Tags added: foundations-todo ** Also affects: software-properties (Ubuntu Noble) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2045455 Title: add-apt-repository crashed with --- in _request() Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Noble: Triaged Bug description: Error encountered during first boot after installing ubuntu-unity- desktop on Live Server 24.04 Daily Build. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.40 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Nov 30 02:20:48 2023 ExecutablePath: /usr/bin/add-apt-repository InstallationDate: Installed on 2023-11-30 (2 days ago) InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily amd64 (20231129) InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=linux Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y'] PythonDetails: N/A SourcePackage: software-properties Title: add-apt-repository crashed with --- in _request() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2045455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2050033] Re: gettext: msgfmt --java2 does not support Java 21
Unsubscribing ubuntu sponsors as already subscribed to the merge -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/2050033 Title: gettext: msgfmt --java2 does not support Java 21 Status in gettext package in Ubuntu: New Status in gettext package in Debian: New Bug description: When building 'ssl-utils-clojure' package with Java 21 as default, the build fails with the following trace: -- Applying task i18n to [make] Running 'make i18n' make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- Running make in the build chroot produces the following error: --- msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo locales/eo.po msgfmt: Java compiler not found, try installing gcj or set $JAVAC msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC make: *** [dev-resources/Makefile.i18n:94: resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1 --- It appears that gettext package does not support Java 21. Note: gettext 0.22.4 refactors Java support. This delta can be safely dropped after a new upstream release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049222] Re: dracut: dracut module 'plymouth' will not be installed, because command 'plymouth-set-default-theme' could not be found!
OK _some_ more work is needed ** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Description changed: + (exploratory dracut analysis) + Installing dracut and using hostonly=yes (https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2049221) to get a working image, I get a password prompt on the terminal instead of in plymouth, apparently plymouth is not installed into the initrd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2049222 Title: dracut: dracut module 'plymouth' will not be installed, because command 'plymouth-set-default-theme' could not be found! Status in dracut package in Ubuntu: New Status in plymouth package in Ubuntu: New Bug description: (exploratory dracut analysis) Installing dracut and using hostonly=yes (https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2049221) to get a working image, I get a password prompt on the terminal instead of in plymouth, apparently plymouth is not installed into the initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2049222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
Waiting for 6.5.13 to actually build but on 6.6.0-14 from proposed now
which is based on 6.6.3 which probably has all the fancy patches too
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2045899
Title:
More amdgpu crashes: pagefaults, ring timeouts and parser bugs
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
New
Bug description:
I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level
but the GUI doesn't actually recover and I also can switch tty with
the keyboard.
I have attached the two crashes from yesterday, they look slightly
different but may be the same cause:
LastDmesg.txt contains the journalctl -k -b of the last failed boot,
OlderDmesg.txt contains the same for the crash before that.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Dec 7 13:09:42 2023
InstallationDate: Installed on 2022-11-26 (376 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2023
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET71W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CF004PGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.28
dmi.modalias:
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21CF004PGE
dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
I saw similar messages in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032386 but that
only caused hangs and not block the entire desktop (and Firefox is good
now so I don't know)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2045899
Title:
More amdgpu crashes: pagefaults, ring timeouts and parser bugs
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
New
Bug description:
I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level
but the GUI doesn't actually recover and I also can switch tty with
the keyboard.
I have attached the two crashes from yesterday, they look slightly
different but may be the same cause:
LastDmesg.txt contains the journalctl -k -b of the last failed boot,
OlderDmesg.txt contains the same for the crash before that.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Dec 7 13:09:42 2023
InstallationDate: Installed on 2022-11-26 (376 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2023
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET71W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CF004PGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.28
dmi.modalias:
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21CF004PGE
dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
These ones I don't remember seeing before:
[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2045899
Title:
More amdgpu crashes: pagefaults, ring timeouts and parser bugs
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
New
Bug description:
I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level
but the GUI doesn't actually recover and I also can switch tty with
the keyboard.
I have attached the two crashes from yesterday, they look slightly
different but may be the same cause:
LastDmesg.txt contains the journalctl -k -b of the last failed boot,
OlderDmesg.txt contains the same for the crash before that.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Dec 7 13:09:42 2023
InstallationDate: Installed on 2022-11-26 (376 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2023
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET71W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CF004PGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.28
dmi.modalias:
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21CF004PGE
dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs
** Attachment added: "OlderDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+attachment/5727266/+files/OlderDmesg.txt
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2045899
Title:
More amdgpu crashes: pagefaults, ring timeouts and parser bugs
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
New
Bug description:
I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level
but the GUI doesn't actually recover and I also can switch tty with
the keyboard.
I have attached the two crashes from yesterday, they look slightly
different but may be the same cause:
LastDmesg.txt contains the journalctl -k -b of the last failed boot,
OlderDmesg.txt contains the same for the crash before that.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Dec 7 13:09:42 2023
InstallationDate: Installed on 2022-11-26 (376 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2023
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET71W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CF004PGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.28
dmi.modalias:
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21CF004PGE
dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033949] Re: Does not work with Ubuntu sources in deb822 format
Setting the mantic tasks to Won't Fix as the changes to python-apt to enable deb822 ubuntu.sources were larger than anticipated. ** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu) Status: In Progress => Fix Committed ** Changed in: python-apt (Ubuntu) Status: New => Fix Committed ** Changed in: software-properties (Ubuntu Mantic) Status: In Progress => Won't Fix ** Changed in: python-apt (Ubuntu Mantic) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2033949 Title: Does not work with Ubuntu sources in deb822 format Status in python-apt package in Ubuntu: Fix Committed Status in software-properties package in Ubuntu: Fix Committed Status in python-apt source package in Mantic: Won't Fix Status in software-properties source package in Mantic: Won't Fix Bug description: On my Mantic I have sources in new deb822 format. Starting software-properties-gtk seems my server is Main server, but from /etc/apt/sources.list.d/ubuntu.sources I see server from Italy and I software-properties-gtk seems unable to change. corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list.d/ubuntu.sources Types: deb URIs: http://it.archive.ubuntu.com/ubuntu Suites: mantic mantic-updates mantic-backports Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://it.archive.ubuntu.com/ubuntu Suites: mantic-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg corrado@corrado-n16-mm-0901:~$ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-gtk 0.99.39 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 2 10:33:12 2023 InstallationDate: Installed on 2023-09-01 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2033949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041831] Re: /usr/bin/update-manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup
I believe this seems like a pygobject issue for desktop to investigate, probably a type declared wrong somewhere? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2041831 Title: /usr/bin/update- manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup Status in pygobject package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:23.10.1, the problem page at https://errors.ubuntu.com/problem/dff72cd5c27c916b2d887a56311ba08ef15b0dff contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2041831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041831] Re: /usr/bin/update-manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup
** Also affects: pygobject (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/2041831 Title: /usr/bin/update- manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup Status in pygobject package in Ubuntu: New Status in update-manager package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:23.10.1, the problem page at https://errors.ubuntu.com/problem/dff72cd5c27c916b2d887a56311ba08ef15b0dff contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2041831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037004] Re: warnings in terminal with software-properties-gtk
This is from ubuntu-drivers-common:
UbuntuDrivers/detect.py
452:out = subprocess.check_output(['udevadm', 'hwdb', '--test=' +
alias],
455:logging.debug('_get_db_name(%s, %s): udevadm hwdb failed: %s',
syspath, alias, str(e))
** Package changed: software-properties (Ubuntu) => ubuntu-drivers-common
(Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2037004
Title:
warnings in terminal with software-properties-gtk
Status in ubuntu-drivers-common package in Ubuntu:
New
Bug description:
When running software-properties-gtk and switching to the "Additional
Drivers" tab I saw the following warnings in my terminal:
$ software-properties-gtk
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
...
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: software-properties-gtk 0.99.39
ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
Uname: Linux 6.5.0-4-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 21 11:49:24 2023
InstallationDate: Installed on 2018-08-10 (1868 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: software-properties
UpgradeStatus: Upgraded to mantic on 2023-09-06 (15 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2037004/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007702] Re: [SRU] Deb version numbering is misleading
2:1snap1-0ubuntu1.22.04.1 is a non-native version number but of course there is no upstream version, it would be a lot better to do this correctly as a native package, like 2:1snap0ubuntu1.22.04.1 ** Description changed: - For Ubuntu >= Focal the transitional debs are frozen at the version - number 1:85... + [Impact] + For Ubuntu >= Focal the transitional debs are frozen at the version number 1:85... This might make one think[1][2] that it will install a critically outdated Chromium while it does not, because it installs the snap. [Test plan] Install the package and confirm the version change with e.g. - dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1' + dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1' [Regression potential] If the version were incorrectly constructed the deb build could fail. [1] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591 [2] https://askubuntu.com/q/1420925 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2007702 Title: [SRU] Deb version numbering is misleading Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: New Status in chromium-browser source package in Jammy: New Status in chromium-browser source package in Lunar: New Status in chromium-browser source package in Mantic: New Bug description: [Impact] For Ubuntu >= Focal the transitional debs are frozen at the version number 1:85... This might make one think[1][2] that it will install a critically outdated Chromium while it does not, because it installs the snap. [Test plan] Install the package and confirm the version change with e.g. dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1' [Regression potential] If the version were incorrectly constructed the deb build could fail. [1] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591 [2] https://askubuntu.com/q/1420925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2030947] Re: gnome-shell spams journal with `g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed` when 'Zoom' a11y feature en
Kir, this is the Ubuntu bug tracker, not the Fedora one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2030947 Title: gnome-shell spams journal with `g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed` when 'Zoom' a11y feature enabled Status in gjs package in Ubuntu: New Bug description: gnome-shell logs gnome-shell[4537]: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed multiple times per second for weeks now. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 44.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Aug 10 10:38:23 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-26 (256 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) RelatedPackageVersions: mutter-common 44.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2030947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041845] Re: Notifies about some ancient downgrades on every boot
Hmm that shows the result of the last offline update, not anything queued; and pkcon offline-get-prepared shows prepared ones. Were you running kinetic during the development cycle? There was a short period where offline updates where unintentionally enabled in gnome- software, bug 1992498. I don't know how else you would have triggered that. ** No longer affects: gnome-software (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2041845 Title: Notifies about some ancient downgrades on every boot Status in packagekit package in Ubuntu: Incomplete Bug description: Preparing for upgrade from 22.04 to 23.04 some packages were downgraded (or just marked as such?) and now update-notifier reminds me about them on every boot, this makes me likely to miss important upgrades available, because I tend now to dismiss it without looking. google-chrome-stable was upgraded many times since then, but I still get notifications about that 113.0... version. Btw, it says about downgrade from the current version! It's update-notifier/lunar,now 3.192.64 amd64 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: update-notifier 3.192.64 ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 14:47:30 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2016-11-26 (2529 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: update-notifier UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago) upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 new release available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2041845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041845] Re: Notifies about some ancient downgrades on every boot
The messages in the screenshot seem to be from gnome-software which is a third party software in universe and not part of the Ubuntu user experience. It's not clear why it would show downgrades to packages no longer in the cache. gnome-software uses PackageKit so you may want to see if pkcon get-updates shows the same issue. ** Package changed: update-notifier (Ubuntu) => gnome-software (Ubuntu) ** Also affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Changed in: packagekit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2041845 Title: Notifies about some ancient downgrades on every boot Status in gnome-software package in Ubuntu: Incomplete Status in packagekit package in Ubuntu: Incomplete Bug description: Preparing for upgrade from 22.04 to 23.04 some packages were downgraded (or just marked as such?) and now update-notifier reminds me about them on every boot, this makes me likely to miss important upgrades available, because I tend now to dismiss it without looking. google-chrome-stable was upgraded many times since then, but I still get notifications about that 113.0... version. Btw, it says about downgrade from the current version! It's update-notifier/lunar,now 3.192.64 amd64 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: update-notifier 3.192.64 ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 14:47:30 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2016-11-26 (2529 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: update-notifier UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago) upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 new release available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2041845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040481] Re: Cannot install Jammy server on machine using pppoe connection to access internet
Seed ppp for inclusion in live-server pool so manual install is possible offline. ** Project changed: subiquity => ubuntu-meta (Ubuntu) ** Also affects: ubuntu-meta (Ubuntu Noble) Importance: Undecided Status: New ** Tags removed: rls-nn-incoming ** Tags added: foundations-todo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2040481 Title: Cannot install Jammy server on machine using pppoe connection to access internet Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: I've noticed that the Ubuntu Jammy live server installer iso does not contain the ppp package, so this makes it impossible to install ubuntu on a device which uses pppoe to access the internet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2040481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
It does seem we already have bug 1990189 fgor the 1a86:7523 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: Fix Released Status in brltty source package in Jammy: Fix Released Status in brltty package in Debian: Confirmed Bug description: * Impact The brltty udev rules are claiming generic devices IDs which makes some other devices like Arduino cards not able to interact with the serial port anymore * Test Case Try to use an Arduino over a cp210x or FTDI serial port, it should be able to talk to the computer - upgrades from focal/impish to the SRU version should have no question and no /etc/udev/rules.d/86-brltty-usbgeneric.rules generated - upgrades from brltty 6.4-4ubuntu2 1. if a device matching the IDs 0403:6001 / 10C4:EA60 / 10C4:EA80 is connectect at the time of the upgrade it should prompt with the debconf question 1.a if the answer is yes, /etc/udev/rules.d/86-brltty-usbgeneric.rules should be generated 1.b if the answer is no, /etc/udev/rules.d/86-brltty-usbgeneric.rules not installed 2. if no matching device is connected there should be no debconf question nor /etc/udev/rules.d/86-brltty-usbgeneric.rules generated - installing brltty when it was not installed no question and no config generated * Regression potential If the debconf logic is wrong users could be prompted with the question when not needed or not prompted when they should. If the udev rules was incorrect or wrongly installed it could lead to have brltty not starting when it should --- Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
Triaging this as high matching bug 1958224. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1990189 Title: brlttty claiming CH341 usbtty device blocking access Status in brltty package in Ubuntu: Fix Released Status in brltty source package in Jammy: Triaged Bug description: While this problem seems to have been fixed for FTDI and CP210 based devices CH340/CH341 based (and possibly other USB serial adapters) are unusable except by brltty. Workaround: disable brltty sudo systemctl stop brltty-udev.service sudo systemctl mask brltty-udev.service sudo systemctl stop brltty.service sudo systemctl disable brltty.service [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using xhci_hcd [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63 [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0 [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input24 [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [139100.786136] ch341 1-2.1.2:1.0: device disconnected [143917.740171] usb 1-2.1.2: USB disconnect, device number 17 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" ProblemType: BugDistroRelease: Ubuntu 22.04 Package: brltty 6.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 19 12:01:21 2022 InstallationDate: Installed on 2022-08-23 (27 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
This needs a followup SRU for the 1a86:7523 following the change in mantic, but it may be best to track this in a new bug report? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: Fix Released Status in brltty source package in Jammy: Fix Released Status in brltty package in Debian: Confirmed Bug description: * Impact The brltty udev rules are claiming generic devices IDs which makes some other devices like Arduino cards not able to interact with the serial port anymore * Test Case Try to use an Arduino over a cp210x or FTDI serial port, it should be able to talk to the computer - upgrades from focal/impish to the SRU version should have no question and no /etc/udev/rules.d/86-brltty-usbgeneric.rules generated - upgrades from brltty 6.4-4ubuntu2 1. if a device matching the IDs 0403:6001 / 10C4:EA60 / 10C4:EA80 is connectect at the time of the upgrade it should prompt with the debconf question 1.a if the answer is yes, /etc/udev/rules.d/86-brltty-usbgeneric.rules should be generated 1.b if the answer is no, /etc/udev/rules.d/86-brltty-usbgeneric.rules not installed 2. if no matching device is connected there should be no debconf question nor /etc/udev/rules.d/86-brltty-usbgeneric.rules generated - installing brltty when it was not installed no question and no config generated * Regression potential If the debconf logic is wrong users could be prompted with the question when not needed or not prompted when they should. If the udev rules was incorrect or wrongly installed it could lead to have brltty not starting when it should --- Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
This has been fixed in mantic, and the following needs to be cherry-
picked to 22.04:
# Device: 1A86:7523
+# Generic Identifier
+# Vendor: Jiangsu QinHeng, Ltd.
+# Product: CH341 USB Bridge Controller
# Baum [NLS eReader Zoomax (20 cells)]
-ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm",
GOTO="brltty_usb_run"
+ENV{PRODUCT}=="1a86/7523/*", ATTRS{idVendor}=="1a40",
ATTRS{idProduct}=="0101", ENV{BRLTTY_BRAILLE_DRIVER}="bm", GOTO="brltty_usb_run"
This bug is similar to bug 1958224.
** Changed in: brltty (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: brltty (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags added: rls-jj-incoming
** Changed in: brltty (Ubuntu)
Importance: Low => High
** Changed in: brltty (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: brltty (Ubuntu Jammy)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1990189
Title:
brlttty claiming CH341 usbtty device blocking access
Status in brltty package in Ubuntu:
Fix Released
Status in brltty source package in Jammy:
Triaged
Bug description:
While this problem seems to have been fixed for FTDI and CP210 based
devices CH340/CH341 based (and possibly other USB serial adapters) are
unusable except by brltty.
Workaround: disable brltty
sudo systemctl stop brltty-udev.service
sudo systemctl mask brltty-udev.service
sudo systemctl stop brltty.service
sudo systemctl disable brltty.service
[139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using
xhci_hcd
[139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86,
idProduct=7523, bcdDevice= 2.63
[139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2,
SerialNumber=0
[139099.370782] usb 1-2.1.2: Product: USB2.0-Serial
[139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected
[139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0
[139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as
/devices/virtual/input/input24
[139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while
'brltty' sets config #1
[139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected
from ttyUSB0
[139100.786136] ch341 1-2.1.2:1.0: device disconnected
[143917.740171] usb 1-2.1.2: USB disconnect, device number 17
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"
ProblemType: BugDistroRelease: Ubuntu 22.04
Package: brltty 6.4-4ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Mon Sep 19 12:01:21 2022
InstallationDate: Installed on 2022-08-23 (27 days ago)
InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bashSourcePackage: brltty
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998111] Re: Quectel EM05-G not being unlocked
Yes, correct, I no longer see the issue in mantic. ** Changed in: modemmanager (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1998111 Title: Quectel EM05-G not being unlocked Status in modemmanager package in Ubuntu: Fix Released Bug description: Despite support being in fcc-unlock.d Bus 001 Device 003: ID 2c7c:030a Quectel Wireless Solutions Co., Ltd. Quectel EM05-G the modem remains locked and enabling it fails: jak@jak-t14-g3:~:master$ mmcli -m any -e error: couldn't enable the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Retry: Invalid transition' Doing something like # modprobe -r cdc_mbim # modprobe cdc_mbim # mbimcli --device-open-proxy --device="/dev/wwan0mbim0" --quectel-set-radio-state=on # systemctl RestartModemManager # mmcli -m any -e makes it work. Peculiar it seems that the mbim-proxy process that ModemManager started is hanging and causing the mbimcli command to time out (if I just run it manually). Further investigation warranted, tips welcome. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: modemmanager 1.20.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Nov 28 13:54:07 2022 InstallationDate: Installed on 2022-11-26 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1998111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862764] Re: add-apt-repository should use signed-by
This has been fixed a couple of months ago for PPAs and I think other shortcuts; they now use deb822 .sources files with Signed-By parameter. ** Changed in: software-properties (Ubuntu) Status: Confirmed => Fix Released ** Changed in: python-apt (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1862764 Title: add-apt-repository should use signed-by Status in python-apt package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Fix Released Status in software-properties package in Debian: New Bug description: add-apt-repository should use signed-by apt sources.list syntax supports limiting which keys are used to sign a given repo. It would be nice for add-apt-repository to import the key somewhere else but trusted.gpg.d and then specify path to it, using the "signed- by" field. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 12:01:49 2020 InstallationDate: Installed on 2016-01-26 (1477 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2019-01-15 (391 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-01-10T16:24:15.968394 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1862764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
** Changed in: apport (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037228] Re: Firefox doesn't work after 23.10 upgrade
Submitter says snapped firefox is installed but snapped firefox binary isn't found, probably needs more triaging ** Package changed: ubuntu-release-upgrader (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037228 Title: Firefox doesn't work after 23.10 upgrade Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Firefox doesn’t work after upgrading from 23.04 to 23.10 beta. The Firefox icon disappeared from my sidebar during the upgrade process. 'snap list' shows firefox stable is installed, trying to run the command firefox says: Command '/usr/bin/firefox' requires the firefox snap to be installed. Please install it with: snap install firefox $ lsb_release -rd No LSB modules are available. Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu3 Candidate: 1:1snap1-0ubuntu3 Version table: *** 1:1snap1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037228] Re: Firefox doesn't work after 23.10 upgrade
What does ls -l /snap/bin/firefox tell you? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037228 Title: Firefox doesn't work after 23.10 upgrade Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Firefox doesn’t work after upgrading from 23.04 to 23.10 beta. The Firefox icon disappeared from my sidebar during the upgrade process. 'snap list' shows firefox stable is installed, trying to run the command firefox says: Command '/usr/bin/firefox' requires the firefox snap to be installed. Please install it with: snap install firefox $ lsb_release -rd No LSB modules are available. Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu3 Candidate: 1:1snap1-0ubuntu3 Version table: *** 1:1snap1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037425] Re: ubuntu-server pulls in ZFS userspace
** Tags removed: rls-mm-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2037425 Title: ubuntu-server pulls in ZFS userspace Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Bug description: ubuntu-server in Mantic pulls in zfs userspace packages and systemd services are automatically enabled, which means zfs kernel modules are automatically loaded at boot, for everybody. On Raspberry Pi, this results in +5MB of additional memory consumption which is not acceptable, especially not on 512MB devices. Culprit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033949] Re: Does not work with sources in deb822 format
For 23.10, we will support deb822 sources for third party sources, especially PPAs, but due to complex interactions did not fully manage to create a decent experience for ubuntu.sources so far.. So in my local git branches: The bits I got working correctly still ended up splitting paragraphs into multiple ones and not merging them back again, so if you enabled a component and disabled it again, you suddenly had two paragraphs. There's missing bits still were it writes to sources.list if you edit ubuntu.sources, actually generates duplicate entries and then stops working. ** Changed in: software-properties (Ubuntu Mantic) Status: Fix Released => In Progress ** Summary changed: - Does not work with sources in deb822 format + Does not work with Ubuntu sources in deb822 format -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2033949 Title: Does not work with Ubuntu sources in deb822 format Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Mantic: In Progress Bug description: On my Mantic I have sources in new deb822 format. Starting software-properties-gtk seems my server is Main server, but from /etc/apt/sources.list.d/ubuntu.sources I see server from Italy and I software-properties-gtk seems unable to change. corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list.d/ubuntu.sources Types: deb URIs: http://it.archive.ubuntu.com/ubuntu Suites: mantic mantic-updates mantic-backports Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://it.archive.ubuntu.com/ubuntu Suites: mantic-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg corrado@corrado-n16-mm-0901:~$ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-gtk 0.99.39 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 2 10:33:12 2023 InstallationDate: Installed on 2023-09-01 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2033949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
** Tags removed: rls-mm-incoming ** Tags added: foundations-todo ** Also affects: software-properties (Ubuntu Mantic) Importance: Undecided Status: Confirmed ** Also affects: ppa-purge (Ubuntu Mantic) Importance: High Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Triaged Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: Triaged Status in software-properties source package in Mantic: Confirmed Bug description: Test Case - From Ubuntu 23.10: sudo apt install hello sudo add-apt-repository ppa:jbicha/temp sudo apt upgrade apt policy hello sudo ppa-purge ppa:jbicha/temp apt policy hello reveals that the PPA version of hello is still installed Also /etc/apt/sources.list.d/jbicha-ubuntu-temp-mantic.sources is still present and active What Should Happen -- ppa-purge should disable the PPA and reinstall any PPA packages with the version apt currently sees. Background -- add-apt-repository creates deb822 sources lists, starting in Ubuntu 23.10 https://discourse.ubuntu.com/t/spec-apt-deb822-sources-by- default/29333 Other Info -- add-apt-repository has a --remove option But it does not do the reinstall part which is important Honestly, that feature is so important, I suggest that add-apt-repository take over the functionality of ppa-purge so that we always get the ppa-purge behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033440] Re: ubuntu-desktop: unnecessary hard "Depends: pipewire-audio"
** Changed in: ubuntu-meta (Ubuntu Lunar) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2033440 Title: ubuntu-desktop: unnecessary hard "Depends: pipewire-audio" Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Lunar: Won't Fix Status in ubuntu-meta source package in Mantic: New Bug description: Recommend demoting pipewire-audio from Depends: to Recommends:. Reason: While it's not ideal, the Ubuntu Desktop can still function on the pulseaudio backend rather than using the direct pipewire-alsa backend which conflicts with the pulseaudio package. This would help people who wish to have a more traditional JACK setup that is bridged to pulseaudio. Right now, this setup is incompatible. Original description: I have installed successfully the standard Ubuntu 23.04 (on a 500 GB external USB drive). Immediately after the installation, I have also installed with apt the "ubuntustudio-installer" package. In the dialog provided by the ubuntustudio-installer, I have selected the following metapackages: - linux-lowlatency - ubuntustudio-lowlatency-settings - ubuntustudio-performance-tweaks - ubuntustudio-audio - ubuntu-pulseaudio-config and pressed "Modify installed Package Selection" After a while a "qaptbatch" dialog has appeared with title "Commit Error" and message "An error occurred while applying changes" So the installation has failed. Then I have tried to manually install each metapackage in the list above with apt and every package was installed successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2033440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2030951] Re: geoclue service prevented from working by apparmor profile
FWIW, I disabled the AppArmor profile and clients still don't connect or rather geoclue times out, don't know what's going on but probably separate bug. Even deleted my modem devices and masked modemmanger, thinking it may be talking to that and hanging there -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2030951 Title: geoclue service prevented from working by apparmor profile Status in geoclue-2.0 package in Ubuntu: Triaged Bug description: The geoclue service doesn't start anymore in mantic, failing with (geoclue:8550): Geoclue-CRITICAL **: 10:56:36.151: Failed to acquire name 'org.freedesktop.GeoClue2' on system bus or lost it. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: geoclue-2.0 2.7.0-3 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Aug 10 10:57:41 2023 InstallationDate: Installed on 2022-11-26 (256 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: geoclue-2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/2030951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2030951] Re: geoclue.service fails to start
Oh that's possible but for me it's denying geoclue from accessing my LTE modem for GPS data, I don't have a test to check if it can provide other data. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2030951 Title: geoclue.service fails to start Status in geoclue-2.0 package in Ubuntu: Triaged Bug description: The geoclue service doesn't start anymore in mantic, failing with (geoclue:8550): Geoclue-CRITICAL **: 10:56:36.151: Failed to acquire name 'org.freedesktop.GeoClue2' on system bus or lost it. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: geoclue-2.0 2.7.0-3 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Aug 10 10:57:41 2023 InstallationDate: Installed on 2022-11-26 (256 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: geoclue-2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/2030951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
ppa-purge is a pretty dangerous script to run due to the downgrade functionality that we should be discouraging use of. It can create systems that look like they have supported components only but had everything messed up by downgrading from some PPA. If the PPA added packages not available in other sources, removing them is fine. But if downgrades are involved it should come with reasonably strong warnings. Generally speaking people should probably reinstall from scratch if they added a PPA that replaced important system packages. ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Triaged Status in software-properties package in Ubuntu: New Bug description: Test Case - From Ubuntu 23.10: sudo apt install hello sudo add-apt-repository ppa:jbicha/temp sudo apt upgrade apt policy hello sudo ppa-purge ppa:jbicha/temp apt policy hello reveals that the PPA version of hello is still installed Also /etc/apt/sources.list.d/jbicha-ubuntu-temp-mantic.sources is still present and active What Should Happen -- ppa-purge should disable the PPA and reinstall any PPA packages with the version apt currently sees. Background -- add-apt-repository creates deb822 sources lists, starting in Ubuntu 23.10 https://discourse.ubuntu.com/t/spec-apt-deb822-sources-by- default/29333 Other Info -- add-apt-repository has a --remove option But it does not do the reinstall part which is important Honestly, that feature is so important, I suggest that add-apt-repository take over the functionality of ppa-purge so that we always get the ppa-purge behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2030951] Re: geoclue.service fails to start
Starts here afaict, gps blocked by apparmor though. What do you see, seb? ● geoclue.service - Location Lookup Service Loaded: loaded (/lib/systemd/system/geoclue.service; static) Active: active (running) since Wed 2023-09-20 18:53:28 CEST; 35s ago Main PID: 1594438 (geoclue) Tasks: 4 (limit: 37482) Memory: 2.4M CPU: 153ms CGroup: /system.slice/geoclue.service └─1594438 /usr/libexec/geoclue Sep 20 18:53:28 jak-t14-g3 systemd[1]: Starting geoclue.service - Location Lookup Service... Sep 20 18:53:28 jak-t14-g3 systemd[1]: Started geoclue.service - Location Lookup Service. Sep 20 18:53:28 jak-t14-g3 geoclue[1594438]: Failed to set GPS refresh rate: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.2613" (uid=123 pid=1594438 comm="/usr/libexec/geoclue" label="/usr/libexec/geoclue (enforce)") interface="org.freedesktop.ModemManager1.Modem.Location" member="SetGpsRefreshRate" error name="(unset)" requested_reply="0" destination=":1.17" (uid=0 pid=2021 comm="/usr/sbin/ModemManager" label="unconfined") -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2030951 Title: geoclue.service fails to start Status in geoclue-2.0 package in Ubuntu: Triaged Bug description: The geoclue service doesn't start anymore in mantic, failing with (geoclue:8550): Geoclue-CRITICAL **: 10:56:36.151: Failed to acquire name 'org.freedesktop.GeoClue2' on system bus or lost it. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: geoclue-2.0 2.7.0-3 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Aug 10 10:57:41 2023 InstallationDate: Installed on 2022-11-26 (256 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: geoclue-2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/2030951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990952] Re: gnome-control-center crashed with SIGABRT in g_assertion_message_expr()
I have the same crash, it seems the message is missing it is: Sep 08 15:47:30 jak-t14-g3 gnome-bluetooth-panel.desktop[309717]: ** Sep 08 15:47:30 jak-t14-g3 gnome-bluetooth-panel.desktop[309717]: Gvc:ERROR:../subprojects/gvc/gvc-mixer-card.c:208:_pa_context_set_card_profile_by_index_cb: assertion failed: (card->priv->target_profile) Sep 08 15:47:30 jak-t14-g3 gnome-bluetooth-panel.desktop[309717]: Bail out! Gvc:ERROR:../subprojects/gvc/gvc-mixer-card.c:208:_pa_context_set_card_profile_by_index_cb: assertion failed: (card->priv->target_profile) ** Summary changed: - gnome-control-center crashed with SIGABRT in g_assertion_message_expr() + gnome-control-center crashed with SIGABRT: Gvc:ERROR:../subprojects/gvc/gvc-mixer-card.c:208:_pa_context_set_card_profile_by_index_cb: assertion failed: (card->priv->target_profile) ** Information type changed from Private to Public ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1990952/+attachment/5619413/+files/CoreDump.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1990952 Title: gnome-control-center crashed with SIGABRT: Gvc:ERROR:../subprojects/gvc/gvc-mixer- card.c:208:_pa_context_set_card_profile_by_index_cb: assertion failed: (card->priv->target_profile) Status in gnome-control-center package in Ubuntu: Confirmed Bug description: dont know what it is just reporting ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 15:42:48 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-09-26 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920) ProcCmdline: gnome-control-center ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-16.1.so Title: gnome-control-center crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1990952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2029148] Re: cups snap - can't add printer
I think this is still Fix Released, the cups deb is back in main, hplip has been force demoted to make everything sort of work (well no hp drivers but that's tracked elsewhere). ** Changed in: ubuntu-meta (Ubuntu) Status: In Progress => Fix Released ** Tags removed: rls-mm-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2029148 Title: cups snap - can't add printer Status in gnome-control-center package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: With cups as snap I can't add a printer. gnome-control-center printer 20:27:44.5824cc-window[13155]: WARNING: Could not find settings panel "printer" smbXcli_negprot_smb1_done: No compatible protocol selected by server. smbXcli_negprot_smb1_done: No compatible protocol selected by server. 20:27:50.3557cc-printers-panel[13155]: WARNING: Install system-config-printer which provides DBus method "GroupPhysicalDevices" to group duplicates in device list. 20:27:54.5122cc-printers-panel[13155]: WARNING: Install system-config-printer which provides DBus method "GroupPhysicalDevices" to group duplicates in device list. 20:27:54.6242cc-printers-panel[13155]: WARNING: Install system-config-printer which provides DBus method "GroupPhysicalDevices" to group duplicates in device list. 20:27:55.2845cc-printers-panel[13155]: WARNING: Install system-config-printer which provides DBus method "GroupPhysicalDevices" to group duplicates in device list. 20:27:57.9338cc-printers-panel[13155]: WARNING: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.fedoraproject.Config.Printing was not provided by any .service files 20:27:57.9348cc-printers-panel[13155]: WARNING: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files 20:27:57.9358cc-printers-panel[13155]: WARNING: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.fedoraproject.Config.Printing was not provided by any .service files 20:27:57.9358cc-printers-panel[13155]: WARNING: Installation of the new printer failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2029148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028054] Re: [MIR] python-rlpycairo
** Tags added: foundations-todo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2028054 Title: [MIR] python-rlpycairo Status in hplip package in Ubuntu: New Status in python-reportlab package in Ubuntu: Incomplete Status in python-rlpycairo package in Ubuntu: Incomplete Bug description: python-rlpycairo is a new dependency of python-reportlab (currently owned by Foundations). The only consumer of python-reportlab is hplip (owned by Desktop), apparently it needs it for scanning: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=651240 $ reverse-depends src:python-reportlab -c main -r mantic Reverse-Depends === * hplip (for python3-reportlab) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x src:hplip -> src:python-reportlab -> src:python-rlpycairo -> src:freetype-py & src:ttf-bitstream-vera So from the above, it sounds like this new dependency is actually needed (after the reportlab package dropped its renderpm extension). It should be discussed between Foundations and Desktop who's owning those dependencies and doing the MIRs for python-rlpycairo, freetype- py and ttf-bitstream-vera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2028054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033129] Re: hplip is in universe and was dropped from Recommends
This depends on bug 2028054 ** Tags removed: rls-mm-incoming ** Changed in: hplip (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2033129 Title: hplip is in universe and was dropped from Recommends Status in hplip package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Triaged Bug description: When preparing the upload of ubuntu-meta 1.516 I wasn't enough attentive. Only afterwards I noticed that the update script had caused hplip to be removed from the meta packages, even if it is still here: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/tree/desktop-common#n69 I don't know how to properly correct this. Please help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2033129/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build
Removing rls-mm-incoming, as this seems to be done. ** Tags removed: rls-mm-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Committed Bug description: Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in mantic-proposed. See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3 When I downgrade glib in my sbuild environment, everything works as expected: $ apt install libglib2.0-0=2.76.3-1ubuntu1 libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1 libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1 The build also works fine in Debian unstable, which is using glib2.0 2.74.6-2. Netplan is using plenty of GLib's keyfile functions (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to producing a different output with this newer release (some strange line breaks injected in the middle of a keyfile). Example keyfile from the test_wifis.test_wifi_wowlan test, that should be generated by Netplan and the way it fails: Expected output: ``` [connection] id=netplan-wl0-homenet type=wifi interface-name=wl0 [wifi] wake-on-wlan=330 ssid=homenet mode=infrastructure [ipv4] method=link-local [ipv6] method=ignore ``` Failure: ``` E AssertionError: '[con[88 chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n' E [connection] E id=netplan-wl0-homenet E type=wifi E interface-name=wl0 E E [wifi] E wake-on-wlan=330 E - E ssid=homenet E mode=infrastructure E + E [ipv4] E method=link-local E E [ipv6] E method=ignore ``` To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2026826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026637] Re: [mantic] many useful apps are marked for auto removal
Generally the way to do this in Debian at least would be something like 1. move the removed dependencies/recommends to a ubuntu-desktop-legacy metapackage/seed 2. recommend that so it is installed 3. one cycle later, drop the recommends (or move it to suggests to keep it installed on upgrades*) (*) In Ubuntu, ubuntu-release-upgrader removes Suggests Adding the recommends for a month to transition devel users using apt, and then removing it again and make u-r-u install it could make sense. On the other hand we also kind of strive to have upgraded users have the same experience (which is why we removed suggested-only packages in the first place), so weigh the benefits. One thing to note is APT's metapackage handling: 1. apt remove metapackage keeps dependencies automatically installed 2. apt install foo where foo conflicts with metapackage causes metapackage to be removed and the manual bit to transition to the dependencies. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2026637 Title: [mantic] many useful apps are marked for auto removal Status in ubuntu-meta package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Triaged Bug description: Today update want remove a lot of apps. This happens on two systems installed from ISO dated 2023-06-07 and 2023-05-21 corrado@corrado-n03-mm-0607:~$ sudo apt update && sudo apt upgrade [sudo] password for corrado: Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease Hit:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu mantic-backports InRelease Hit:4 http://archive.ubuntu.com/ubuntu mantic-security InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: aisleriot baobab branding-ubuntu cheese cheese-common file-roller gir1.2-rb-3.0 gnome-mahjongg gnome-mines gnome-sudoku gnome-video-effects gstreamer1.0-clutter-3.0 guile-3.0-libs libavahi-ui-gtk3-0 libcairomm-1.16-1 libcdr-0.1-1 libchamplain-0.12-0 libchamplain-gtk-0.12-0 libcheese-gtk25 libcheese8 libclutter-gst-3.0-0 libdmapsharing-4.0-3 libevent-2.1-7 libfreehand-0.1-1 libfreerdp-client2-2 libglibmm-2.68-1 libgnome-games-support-1-3 libgnome-games-support-common libgpod-common libgpod4 libgtkmm-4.0-0 libgupnp-igd-1.0-4 libixml10 liblc3-0 libminiupnpc17 libmspub-0.1-1 libmujs2 libnatpmp1 libpagemaker-0.0-0 libpangomm-2.48-1 libqqwing2v5 libreoffice-calc libreoffice-draw libreoffice-gnome libreoffice-gtk3 libreoffice-impress librhythmbox-core10 libsdl-image1.2 libsdl1.2debian libsgutils2-1.46-2 libsigc++-3.0-0 libupnp13 libvisio-0.1-1 lp-solve media-player-info python3-mako python3-renderpm python3-reportlab-accel remmina remmina-common remmina-plugin-rdp remmina-plugin-secret remmina-plugin-vnc rhythmbox rhythmbox-data rhythmbox-plugin-alternative-toolbar rhythmbox-plugins shotwell shotwell-common simple-scan transmission-common transmission-gtk Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. corrado@corrado-n03-mm-0607: ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop 1.505 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 9 08:53:45 2023 InstallationDate: Installed on 2023-06-07 (31 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230607) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2026637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
There seem to be an unrelated change in the debdiff that are not
mentioned in the changelog or in the bug, the _is_runtimepm_supported()
rework to use apt_pkg.DepCache rather than the high-level apt API.
So I am unsubscribing ubuntu-sponsors as that needs more information.
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Status: Confirmed => Invalid
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Incomplete
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995650] Re: Trivial: Unclosed tag in distro.py
While I cherry-picked the fix, as this only affects Debian, I'm going to
mark the bug as Won't Fix.
** Changed in: software-properties (Ubuntu)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1995650
Title:
Trivial: Unclosed tag in distro.py
Status in software-properties package in Ubuntu:
Won't Fix
Bug description:
Hi, distro.py, line: 37 starts with a tag but does not close it.
The code is here:
return(_("To improve the user experiece of Debian please take "
"part in the popularity contest. If you do so the list of "
"installed software and how often it was used will be "
"collected and sent anonymously to the Debian project.\n\n"
"The results are used to optimise the layout of the "
"installation CDs."))
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1995650/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891270] Re: Iranian calendar shows in Azerbaijani language
Queued for 23.10 in https://git.launchpad.net/ubiquity/commit/?id=6ad715e6ae9dda99a9349924cc464528a759af17 For a stable release update to 22.04, feel free to follow the procedure at https://wiki.ubuntu.com/StableReleaseUpdates to add the metadata to the bug such that it can be reproduced and resubscribe ubuntu-sponsors when that's done, I think the patch is trivial to adapt from the commit that it doesn't need a new debdiff. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1891270 Title: Iranian calendar shows in Azerbaijani language Status in gnome-calendar package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Committed Bug description: I already installed Ubuntu 20.04.1 LTS and set location on Iran during installation. After finishing installation successfully, I open the calendar by clicking at the top of the screen (where the clock is shown), I see the calendar with Azerbaijani names for month and weekdays. Such as "آقوست" for August and "جومعه آخشامی" for Thursday. But it should show in Iranian names such as "اوت" for August and "پنجشنبه" for Thursday. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969901] Re: network-manager fails to renew ipv6 address
Ubuntu 18.04 has reached it's end of standard support, hence marking
won't fix.
** Changed in: network-manager (Ubuntu Bionic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1969901
Title:
network-manager fails to renew ipv6 address
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
Won't Fix
Bug description:
[Impact]
* This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
used.
* Network manager might kill dhclient(6) and fail to start it again
causing the IPv6 address to be lost on a network that uses mixed
IPv4/IPV6.
The network status will still be seen as online in gnome since ipv4
is still active.
The user then have to manually remove the dhcpv6 lease files and
restart ipv6 connection/restart network manager to regain IPv6
connectivity.
* This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
is based on 1.10.6):
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f
* Upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=783391
[Test Plan]
The test requires three computers
* one computer runing isc dhcpd server (with network configured static)
* one computer running patched network manager
* one computer running vanilla ubuntu
The idea is to execute on an isolated network and trigger the error by
changing
ip range handed out by the dhcp-server to force a nack response back to the
clients.
Expected result
* patched network keeps dhclient6 alive
* vanilla network manager will fail to keep dhclient6 alive
in network manager logs dhcp6 will expire and not be restarted
ON THE SERVER
# Disable app-armor, as it has rules restricting dhcpd
aa-teardown
# install isc dhcpserver
isc-dhcp-server
# configure network static
sudo nmcli connection modify "${CONNECTION_NAME}" \
ipv4.method "manual" \
ipv4.addresses "192.168.1.1/24" \
ipv4.gateway "192.168.1.254" \
ipv4.dns "192.168.1.1" \
ipv6.method "manual" \
ipv6.addresses "2001:db8:0:1::1/64" \
ipv6.gateway "2001:db8:0:1::ffbb" \
ipv6.dns "2001:db8:0:1::1/64"
mkdir -p tmp
touch tmp/dhcpd4_a.leases
touch tmp/dhcpd4_b.leases
touch tmp/dhcpd6_a.leases
touch tmp/dhcpd6_b.leases
Then it is time to execute dhcpd
-f - run in foreground
-d - print errors to stderr instead of syslog
# Start in separate terminals
dhcpd -f -d -4 -cf dhcp_v4_a.conf -lf tmp/dhcpd4_a.leases enp0s31f6
dhcpd -f -d -6 -cf dhcp_v6_a.conf -lf tmp/dhcpd6_a.leases enp0s31f6
Press ctrl-C to kill servers, then restart with the b configurations
dhcpd -f -d -4 -cf dhcp_v4_b.conf -lf tmp/dhcpd4_b.leases enp0s31f6
dhcpd -f -d -6 -cf dhcp_v6_b.conf -lf tmp/dhcpd6_b.leases enp0s31f6
Then leases to expire (check for clients that kills dhclient)
Press ctrl-C to kill servers, then restart with the a configurations
ON THE CLIENTS
Setup:
Configure ipv6 network in settings to use dhcp (using the gui)
Test:
check that dhcp clients are still running:
ps aux|grep dhclient
Expected in output
one client for dhcpv4
one client for dhcpv6
Also check network manager status :
journalctl -u NetworkManager.service
journalctl -u NetworkManager.service|grep dhcp6 # to only view dhclient6
journalctl -u NetworkManager.service|grep dhcp4 # to only view dhclient4
if dhclient is not running:
stop network in gui
remove lease files (/var/lib/NetworkManager/dhclient*.lease). Only remove the
lease for the client not running.
start network in gui
if dhclients are running:
wait additional ten minutes, repeat from beginning of test
[Where problems could occur]
* The change is in the dchp lease expiration handling so verify that
there is no regression in dhcp renewals on different type of
configuration include IPv6
[Other Info]
* We have tested this patch on a couple of clients where we have seen this
this problem. If this patch is feasible to include in Ubuntu 18.04 we
could request more users to test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921398] Re: No dns resolution after closing a vpn/sstp connection
This is fixed in kinetic/lunar/mantic, I have not checked older releases. If you want to provide an update for an older stable release, please provide debdiffs against that version and follow the process in https://wiki.ubuntu.com/StableReleaseUpdates ** Changed in: ppp (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/1921398 Title: No dns resolution after closing a vpn/sstp connection Status in ppp package in Ubuntu: Fix Released Bug description: The fix for the following issue closes it for nm-pptp-service-* connections, however; it is still a problem for users using network- manager-sstp. You use network-manager-sstp, connect to your VPN server. Then disconnect and you now can't lookup any hostnames. Original problem #1778946 No dns resolution after closing a vpn/pptp connection This is still a problem for sstp users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1921398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
ubuntu-sponsors was still subscribed and a task open for gdm3/focal.
AFAICT, the issue was somehow resolved in ubuntu-drivers in focal and
there's nothing to actually sponsor.
If sponsorship is still needed, please provide more details and
resubscribe ubuntu-sponsors.
** Changed in: gdm3 (Ubuntu Focal)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia driver probe
Status in OEM Priority Project:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Incomplete
Status in ubuntu-drivers-common source package in Focal:
Fix Released
Status in gdm3 source package in Impish:
Won't Fix
Status in ubuntu-drivers-common source package in Impish:
Fix Released
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
This doesn't appear worth shipping a patch for downstream either, so I am going to unsubscribe Ubuntu Sponsors and mark it Won't fix. ** Changed in: hplip (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: hplip (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in hplip package in Ubuntu: Won't Fix Status in hplip source package in Bionic: Won't Fix Status in hplip source package in Focal: Won't Fix Status in hplip source package in Hirsute: Won't Fix Status in hplip source package in Impish: Won't Fix Status in hplip source package in Jammy: Won't Fix Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
Unsubscribing ubuntu-sponsors as the bug has been inactive for months now and it's not clear what, if anything, still needs sponsoring. Please add a comment and resubscribe if sponsorship is still required. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: Confirmed Status in xserver-xorg-video-nouveau source package in Jammy: Confirmed Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2021937] [NEW] preinst writes to /root
Public bug reported: As part of my sandboxed APT I noticed that the package failed to install as it was trying to write to /root. /root is a user directory, not a system one, which may not even exist because the administrator changed it to like /home/root, for example, and we definitely should not be writing system files in user directories. Preparing to unpack .../16-network-manager_1.42.4-1ubuntu4_amd64.deb ... mkdir: cannot create directory ‘/root/NetworkManager.bak’: Read-only file system cp: cannot create directory '/root/NetworkManager.bak/system-connections_1.42.4-1ubuntu2': No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-x9x0Qo/16-network-manager_1.42.4-1ubuntu4_amd64.deb (--unpack): new network-manager package pre-installation script subprocess returned error exit status 1 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2021937 Title: preinst writes to /root Status in network-manager package in Ubuntu: New Bug description: As part of my sandboxed APT I noticed that the package failed to install as it was trying to write to /root. /root is a user directory, not a system one, which may not even exist because the administrator changed it to like /home/root, for example, and we definitely should not be writing system files in user directories. Preparing to unpack .../16-network-manager_1.42.4-1ubuntu4_amd64.deb ... mkdir: cannot create directory ‘/root/NetworkManager.bak’: Read-only file system cp: cannot create directory '/root/NetworkManager.bak/system-connections_1.42.4-1ubuntu2': No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-x9x0Qo/16-network-manager_1.42.4-1ubuntu4_amd64.deb (--unpack): new network-manager package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2021937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007743] Re: intramfs Failed: ZSTD-compressed data
The grub update has been submitted for signing now https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2013361 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2007743 Title: intramfs Failed: ZSTD-compressed data Status in grub2-unsigned package in Ubuntu: Triaged Bug description: The current updates of Ubuntu 22.04.2 LTS results on boot (black screen) the message "not enough memory, press any key" and after comes any others "error messages" too and then Ubuntu starts! Maybe this Bug results from the current AMD Kernel Updates on "modern" Prozessors or Update for the Grub or something - i'don't know - there are many System-Updates yesterday and all comes over Ubuntu Store as package # lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 # dpkg -l | grep init ii busybox-initramfs 1:1.30.1-7ubuntu3 amd64Standalone shell setup for initramfs ii gnome-initial-setup42.0.1-1ubuntu2.3 amd64Initial GNOME system setup helper ii init 1.62 amd64metapackage ensuring an init system is installed ii init-system-helpers1.62 all helper tools for all init systems ii initramfs-tools0.140ubuntu13.1 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu13.1 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu13.1 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.6.1-1ubuntu1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.10-4 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu4 all Linux Standard Base init script functionality ii ncurses-base 6.3-2 all basic terminal type definitions ii sysvinit-utils 3.01-1ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu4 amd64X server initialisation tool # dpkg -l | grep zfs -> brings no information here # zfs list -> zfs is not installed here if you need more system-infos to solve this Bug, please let me know! The first error means "Not Enough Memory, Please press any key" - you can press any key (but you don't need) and it comes the "intramfs Failed: ZSTD-compressed data ..." and then the Ubuntu Login screen comes up. Please be patient with me, I'm new to Ubuntu and Launchpad and don't know much about it yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007743] Re: intramfs Failed: ZSTD-compressed data
An updated grub is available for testing in 22.10 (and other versions once everything has been published and builds retriggered) in the PPA: ppa:ubuntu-uefi-team/ubuntu/ppa This is not trusted by the default Ubuntu key! To test, you need to import the PPA signing key https://ppa.launchpadcontent.net/ubuntu-uefi- team/ppa/ubuntu/dists/kinetic/main/uefi/grub2-amd64/current/control/uefi.crt You can convert it to DER format by running openssl x509 -in uefi.crt -out uefi.der -outform der and then importing it into the MOK using mokutil --import uefi.der Please make sure to only update grub-efi-amd64-signed and related packages from the PPA and not newer shims or similar changes, and remove the PPA immediately after, then remove the key after a new update has been published in the main archive. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2007743 Title: intramfs Failed: ZSTD-compressed data Status in grub2-unsigned package in Ubuntu: Triaged Bug description: The current updates of Ubuntu 22.04.2 LTS results on boot (black screen) the message "not enough memory, press any key" and after comes any others "error messages" too and then Ubuntu starts! Maybe this Bug results from the current AMD Kernel Updates on "modern" Prozessors or Update for the Grub or something - i'don't know - there are many System-Updates yesterday and all comes over Ubuntu Store as package # lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 # dpkg -l | grep init ii busybox-initramfs 1:1.30.1-7ubuntu3 amd64Standalone shell setup for initramfs ii gnome-initial-setup42.0.1-1ubuntu2.3 amd64Initial GNOME system setup helper ii init 1.62 amd64metapackage ensuring an init system is installed ii init-system-helpers1.62 all helper tools for all init systems ii initramfs-tools0.140ubuntu13.1 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu13.1 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu13.1 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.6.1-1ubuntu1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.10-4 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu4 all Linux Standard Base init script functionality ii ncurses-base 6.3-2 all basic terminal type definitions ii sysvinit-utils 3.01-1ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu4 amd64X server initialisation tool # dpkg -l | grep zfs -> brings no information here # zfs list -> zfs is not installed here if you need more system-infos to solve this Bug, please let me know! The first error means "Not Enough Memory, Please press any key" - you can press any key (but you don't need) and it comes the "intramfs Failed: ZSTD-compressed data ..." and then the Ubuntu Login screen comes up. Please be patient with me, I'm new to Ubuntu and Launchpad and don't know much about it yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
Is desktop working on this / going to? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps Status in glib2.0 package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. I was unable to reproduce the issue on Debian Testing but there may have been differences in how snap was configured there. I'm filing this bug since ideally we would not be diverging from upstream here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2007743] Re: intramfs Failed: ZSTD-compressed data
Regressions have been reported from the additional fixes in another distribution so I am hesitating a bit and I'm still waiting to hear back about which path to take for fixing a bug on bionic (missing efibootmgr). So I pivoted to apt work in the meantime while these threads get more clear. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2007743 Title: intramfs Failed: ZSTD-compressed data Status in grub2-unsigned package in Ubuntu: Triaged Bug description: The current updates of Ubuntu 22.04.2 LTS results on boot (black screen) the message "not enough memory, press any key" and after comes any others "error messages" too and then Ubuntu starts! Maybe this Bug results from the current AMD Kernel Updates on "modern" Prozessors or Update for the Grub or something - i'don't know - there are many System-Updates yesterday and all comes over Ubuntu Store as package # lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 # dpkg -l | grep init ii busybox-initramfs 1:1.30.1-7ubuntu3 amd64Standalone shell setup for initramfs ii gnome-initial-setup42.0.1-1ubuntu2.3 amd64Initial GNOME system setup helper ii init 1.62 amd64metapackage ensuring an init system is installed ii init-system-helpers1.62 all helper tools for all init systems ii initramfs-tools0.140ubuntu13.1 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu13.1 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu13.1 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.6.1-1ubuntu1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.10-4 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu4 all Linux Standard Base init script functionality ii ncurses-base 6.3-2 all basic terminal type definitions ii sysvinit-utils 3.01-1ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu4 amd64X server initialisation tool # dpkg -l | grep zfs -> brings no information here # zfs list -> zfs is not installed here if you need more system-infos to solve this Bug, please let me know! The first error means "Not Enough Memory, Please press any key" - you can press any key (but you don't need) and it comes the "intramfs Failed: ZSTD-compressed data ..." and then the Ubuntu Login screen comes up. Please be patient with me, I'm new to Ubuntu and Launchpad and don't know much about it yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965094] Re: "Additional Drivers" application crashes on startup
*** This bug is a duplicate of bug 1964880 *** https://bugs.launchpad.net/bugs/1964880 It's actually the exact same backtrace in that bug as here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1965094 Title: "Additional Drivers" application crashes on startup Status in software-properties package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Click on "Show applications" in the dock * Click on "Additional Drivers" Expected: It is possible to see and install additional drivers Actual: Application "software-properties-gtk" crashes Background: I installed 22.04 daily build from scratch on my new Samsung laptop just a few days ago and I have almost no custom settings. Output from screenfetch: ./+o+- [...] y- -yy+ OS: Ubuntu 22.04 jammy ://+//-yyo Kernel: x86_64 Linux 5.15.0-22-generic .++ .:/++/-.+sss/` Uptime: 1d 9h 37m .:++o: //:--:/- Packages: 1810 o:+o+:++.`..```.-/oo+/ Shell: bash 5.1.16 .:+o:+o/. `+sssoo+/Resolution: 3840x1080 .++/+:+oo+o:` /sssooo. DE: GNOME 41.4 /+++//+:`oo+o /::--:. WM: Mutter \+/+o+++`o++o ++. WM Theme: Adwaita .++.o+++oo+:` /dddhhh. GTK Theme: Yaru-dark [GTK2/3] .+.o+oo:. `odd+Icon Theme: Yaru \+.++o+o``-.:ohdh+ Font: Ubuntu 11 `:o+++ `oyo++os: Disk: 21G / 1,2T (2%) .o:`.syhhh/.oo++o` CPU: 11th Gen Intel Core i7-1165G7 @ 8x 4,7GHz [40.0°C] /osyyo++ooo+++/ GPU: Iris Xe Graphics ` +oo+++o\: RAM: 2627MiB / 15725MiB `oo++. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 08:34:57 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-14 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4 Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4'] PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964823] Re: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
*** This bug is a duplicate of bug 1964880 *** https://bugs.launchpad.net/bugs/1964880 ** This bug is no longer a duplicate of bug 1965094 "Additional Drivers" application crashes on startup ** This bug has been marked a duplicate of bug 1964880 software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1964823 Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' Status in software-properties package in Ubuntu: New Bug description: The following packages will be upgraded: linux-firmware 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/238 MB of archives. After this operation, 24,9 MB of additional disk space will be used. Do you want to continue? [Y/n] Y (Reading database ... 212684 files and directories currently installed.) Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) root@Proton:~# ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 14 21:48:26 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4 Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1964823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
