[Desktop-packages] [Bug 1933589] [NEW] lightdm login window cannot come up
Public bug reported: After upgrading the package to the latest, lightdm login windows does not appear. I can see just a blank black display with a mouse cursor, nothing else. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gsettings-desktop-schemas 40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-23.24-generic 5.11.22 Uname: Linux 5.11.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 25 06:32:52 2021 InstallationDate: Installed on 2020-12-31 (175 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: gsettings-desktop-schemas UpgradeStatus: Upgraded to impish on 2021-01-02 (173 days ago) ** Affects: gsettings-desktop-schemas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1933589 Title: lightdm login window cannot come up Status in gsettings-desktop-schemas package in Ubuntu: New Bug description: After upgrading the package to the latest, lightdm login windows does not appear. I can see just a blank black display with a mouse cursor, nothing else. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gsettings-desktop-schemas 40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-23.24-generic 5.11.22 Uname: Linux 5.11.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 25 06:32:52 2021 InstallationDate: Installed on 2020-12-31 (175 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: gsettings-desktop-schemas UpgradeStatus: Upgraded to impish on 2021-01-02 (173 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1933589/+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 1933452] Re: secondary portrait monitor is not portrait during boot
This is somewhat related to bug 1873164. In both cases they are landscape displays that just don't yet know which way is up. Since we don't have access to the user monitor config (or know which user) during boot, it's not possible to find out that way. It is however sometimes possible to read from the monitor over i2s bus which way it is rotated. I've never seen that implemented in real software though. ** Package changed: xorg (Ubuntu) => plymouth (Ubuntu) ** Summary changed: - secondary portrait monitor is not portrait during boot + Portrait monitor is not portrait during boot ** Changed in: plymouth (Ubuntu) Importance: Undecided => Low ** Changed in: plymouth (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933452 Title: Portrait monitor is not portrait during boot Status in plymouth package in Ubuntu: Triaged Bug description: I'm using Ubuntu 20.04 in my laptop. with that i'm using a secondary monitor which is portrait. these 2 works fine but in the boot menu, secondary monitor's screen is wrong. it's not portrait. please fix this issue. Thank you. Regards, Shehan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 24 15:49:32 2021 DistUpgraded: 2020-10-11 07:43:44,586 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-53-generic, x86_64: installed nvidia, 390.138, 5.4.0-54-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-53-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-54-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:098a] Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940M] [1025:098c] InstallationDate: Installed on 2019-06-23 (731 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Aspire E5-573G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=2151ff19-8bcb-4ed7-aded-0cfb4745ec95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-10-11 (256 days ago) dmi.bios.date: 03/17/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd03/17/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-573G dmi.product.sku: Aspire E5-573G_098A_1_07 dmi.product.version: V3.72 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1933452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~
[Desktop-packages] [Bug 1933570] Re: package python3-uno 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: installed python3-uno package post-installation script subprocess returned error exit statu
** Tags removed: need-duplicate-check -- 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/1933570 Title: package python3-uno 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: installed python3-uno package post-installation script subprocess returned error exit status 1 Status in libreoffice package in Ubuntu: New Bug description: Removed Libre Office to use Open Office. All was going well until I tried to install the latest update for ubuntu base. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3-uno 1:6.4.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: libreoffice-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 24 18:33:12 2021 ErrorMessage: installed python3-uno package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-09 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: libreoffice Title: package python3-uno 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: installed python3-uno 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/libreoffice/+bug/1933570/+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 1933570] [NEW] package python3-uno 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: installed python3-uno package post-installation script subprocess returned error exit sta
Public bug reported: Removed Libre Office to use Open Office. All was going well until I tried to install the latest update for ubuntu base. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3-uno 1:6.4.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: libreoffice-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 24 18:33:12 2021 ErrorMessage: installed python3-uno package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-09 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: libreoffice Title: package python3-uno 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: installed python3-uno package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1933570 Title: package python3-uno 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: installed python3-uno package post-installation script subprocess returned error exit status 1 Status in libreoffice package in Ubuntu: New Bug description: Removed Libre Office to use Open Office. All was going well until I tried to install the latest update for ubuntu base. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3-uno 1:6.4.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: libreoffice-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 24 18:33:12 2021 ErrorMessage: installed python3-uno package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-09 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: libreoffice Title: package python3-uno 1:6.4.7-0ubuntu0.20.04.1 failed to install/upgrade: installed python3-uno 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/libreoffice/+bug/1933570/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Changed in: bluez (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: bluez (Ubuntu Hirsute) Status: In Progress => Fix Committed -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released ** Also affects: bluez (Ubuntu Impish) Importance: High Status: Fix Released ** Changed in: bluez (Ubuntu Focal) Assignee: (unassigned) => Anch (anch) ** Changed in: bluez (Ubuntu Hirsute) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: bluez (Ubuntu Impish) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu Focal) Assignee: Anch (anch) => Andy Chi (andch) ** Description changed: [Impact] - * On/off of Bluetooth in gnome-control-center will not work properly. - - * Devices are not refreshed in the list anymore. - - * The passed struct will depend on the length of the submitted read() and the -kernel version. + On/off of Bluetooth in gnome-control-center will not work properly in + kernels 5.11 (approximately) onward. Devices are not refreshed in the + list anymore. [Test Plan] - * Open gnome-control-center and select Bluetooth - - * turn off Bluetooth via UI - - * turn on Bluetooth via UI + 1. Open gnome-control-center and select Bluetooth + 2. Turn off Bluetooth via UI + 3. Turn on Bluetooth via UI + + Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] - * If user install newer kernel such as 5.13, they may have this issue. + Since the fix involves the 'rfkill' logic it has the potential to affect + any Bluetooth or Wifi on/off setting. - * Tested on Intel AX201 and Intel 6235 with kernel version - 5.13.0-1003-oem. + [Other info] - * Upstream bug in gnome-bluetooth -https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 + Upstream bug in gnome-bluetooth: + https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 - * Discussion in linux-bluetooth -https://marc.info/?t=16200475893&r=1&w=2 + Discussion in linux-bluetooth: + https://marc.info/?t=16200475893&r=1&w=2 ** Changed in: bluez (Ubuntu Focal) Importance: Undecided => High ** Changed in: bluez (Ubuntu Hirsute) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
I swapped my environment (gnome-fallback, chromium-browser, evolution, libreoffice, gnome-terminal) for a vanilla env of ctwm, xterm and firefox. After 4 days the memory usage stayed at 0.6%. Confirm that it is not a bug in xorg but in one of the other apps, as suggested by Daniel. So I need to check all other apps to see which one is causing the memory use and report it to the offending one. I've changed the status of this bug report to invalid. Thanks Daniel! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in libreoffice package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1930641/+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 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
** Changed in: xorg-server (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in libreoffice package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1930641/+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 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image
** Changed in: ubiquity (Ubuntu) Assignee: (unassigned) => jean fourie (jeanjpfmainten2) -- 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/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image Status in OEM Priority Project: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubiquity source package in Groovy: Won't Fix Status in ubuntu-drivers-common source package in Groovy: Won't Fix Bug description: I've installed the focal-desktop-amd64.iso image with SHA-256 sum b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook 15 G7 laptop (CID 202009-28216). There are multiple issues: * The graphical desktop isn't launched. The screen remains black except for a cursor blinking erratically in the top left corner of the screen. If I hammer Control+Alt+F[12345] for a while, the graphical desktop starts eventually. * The screen resolution is 3840x2160 but there is no scaling, so everything is tiny. * The touchpad does not work. * WLAN does not work. * Ethernet does not work. I tried two dongles (a USB A as well as a USB C dongle). * No sound. $ cat /proc/version_signature Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914374/+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 1907886] Re: avinfo is missing
This bug was fixed in the package bluez - 5.59-0ubuntu1 --- bluez (5.59-0ubuntu1) impish; urgency=medium * New upstream release 5.59 (LP: #1933078): - Fix issue with string to UUID-32 conversion. - Fix issue with connect request if SDP search failed. - Fix issue with accepting invalid AVDTP capabilities. - Fix issue with unregister handling of AVRCP player. * Add new build-dep 'python3-docutils' required for rst2man. * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833). - Requires new build-dep 'libjson-c-dev'. * Cleanups from upstream debian: - Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'. - Lots of benign formatting changes in debian/control to shrink the diff. * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022). * Add binary 'avinfo' to 'bluez' (LP: #1907886). * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth on/off toggle issues with newer kernel versions (LP: #1926062). -- Daniel van Vugt Mon, 21 Jun 2021 17:02:38 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1907886 Title: avinfo is missing Status in bluez package in Ubuntu: Fix Released Bug description: The "avinfo" command line tools available in bluez/tools (https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools) is not available in the package. The package bluez-tools (https://packages.ubuntu.com/groovy/bluez- tools) seems to map another project external to bluez (https://github.com/khvzak/bluez-tools) and not the "tools" folder of bluez. "avinfo" is used for example in order to check which codecs are supported by a headphone set (see https://github.com/EHfive /pulseaudio-modules-bt/issues/31#issuecomment-462717049). Maybe have "bluez-tools" map the "tools" folder of bluez, and move the other project to another package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1907886/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
This bug was fixed in the package bluez - 5.59-0ubuntu1 --- bluez (5.59-0ubuntu1) impish; urgency=medium * New upstream release 5.59 (LP: #1933078): - Fix issue with string to UUID-32 conversion. - Fix issue with connect request if SDP search failed. - Fix issue with accepting invalid AVDTP capabilities. - Fix issue with unregister handling of AVRCP player. * Add new build-dep 'python3-docutils' required for rst2man. * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833). - Requires new build-dep 'libjson-c-dev'. * Cleanups from upstream debian: - Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'. - Lots of benign formatting changes in debian/control to shrink the diff. * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022). * Add binary 'avinfo' to 'bluez' (LP: #1907886). * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth on/off toggle issues with newer kernel versions (LP: #1926062). -- Daniel van Vugt Mon, 21 Jun 2021 17:02:38 +0800 ** Changed in: bluez (Ubuntu Impish) Status: Fix Committed => 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions --
[Desktop-packages] [Bug 1929833] Re: bluez: meshctl missing
This bug was fixed in the package bluez - 5.59-0ubuntu1 --- bluez (5.59-0ubuntu1) impish; urgency=medium * New upstream release 5.59 (LP: #1933078): - Fix issue with string to UUID-32 conversion. - Fix issue with connect request if SDP search failed. - Fix issue with accepting invalid AVDTP capabilities. - Fix issue with unregister handling of AVRCP player. * Add new build-dep 'python3-docutils' required for rst2man. * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833). - Requires new build-dep 'libjson-c-dev'. * Cleanups from upstream debian: - Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'. - Lots of benign formatting changes in debian/control to shrink the diff. * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022). * Add binary 'avinfo' to 'bluez' (LP: #1907886). * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth on/off toggle issues with newer kernel versions (LP: #1926062). -- Daniel van Vugt Mon, 21 Jun 2021 17:02:38 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1929833 Title: bluez: meshctl missing Status in bluez package in Ubuntu: Fix Released Status in bluez package in Debian: Fix Released Bug description: bluez has added a new tool for BT mesh handling. Debian has a new binary package: https://packages.debian.org/bullseye /bluez-meshd Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+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 1932022] Re: Can you add the btvirt executable to bluez-tests?
This bug was fixed in the package bluez - 5.59-0ubuntu1 --- bluez (5.59-0ubuntu1) impish; urgency=medium * New upstream release 5.59 (LP: #1933078): - Fix issue with string to UUID-32 conversion. - Fix issue with connect request if SDP search failed. - Fix issue with accepting invalid AVDTP capabilities. - Fix issue with unregister handling of AVRCP player. * Add new build-dep 'python3-docutils' required for rst2man. * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833). - Requires new build-dep 'libjson-c-dev'. * Cleanups from upstream debian: - Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'. - Lots of benign formatting changes in debian/control to shrink the diff. * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022). * Add binary 'avinfo' to 'bluez' (LP: #1907886). * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth on/off toggle issues with newer kernel versions (LP: #1926062). -- Daniel van Vugt Mon, 21 Jun 2021 17:02:38 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1932022 Title: Can you add the btvirt executable to bluez-tests? Status in bluez package in Ubuntu: Fix Released Bug description: See the Debian package: https://packages.debian.org/buster/i386/bluez- test-tools/filelist The Ubuntu package contains the same tools, except for btvirt. Would it be possible to add this? The buildlog shows that the btvirt executable is already built, but just not put into the *.deb package. Additions to be done to debian/bluez-tests.install: emulator/b1ee usr/bin emulator/btvirt usr/bin emulator/hfp usr/bin Having the btvirt tool available will make testing on CI systems a lot easier. References: https://github.com/hadess/bluez/blob/master/Makefile.tools#L76-L82 https://answers.launchpad.net/ubuntu/+source/bluez/+question/697542 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1932022/+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 1933078] Re: BlueZ 5.59 release
This bug was fixed in the package bluez - 5.59-0ubuntu1 --- bluez (5.59-0ubuntu1) impish; urgency=medium * New upstream release 5.59 (LP: #1933078): - Fix issue with string to UUID-32 conversion. - Fix issue with connect request if SDP search failed. - Fix issue with accepting invalid AVDTP capabilities. - Fix issue with unregister handling of AVRCP player. * Add new build-dep 'python3-docutils' required for rst2man. * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833). - Requires new build-dep 'libjson-c-dev'. * Cleanups from upstream debian: - Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'. - Lots of benign formatting changes in debian/control to shrink the diff. * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022). * Add binary 'avinfo' to 'bluez' (LP: #1907886). * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth on/off toggle issues with newer kernel versions (LP: #1926062). -- Daniel van Vugt Mon, 21 Jun 2021 17:02:38 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+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 1933361] Re: Audio Problem, soundcard not detected
you installed 20.04 on your machine, but the kernel version in your log is 5.11.0-generic, how did you install the 5.11 kernel under 20.04, I remember it is 5.8 kernel under 20.04 if you run update. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1933361 Title: Audio Problem, soundcard not detected Status in alsa-driver package in Ubuntu: New Bug description: Hi, After last patch in Ubuntu 20.04.2 LTS, I have lost my audio. I have got an Asus monitor with speakers inside the monitor. The sound come to the monitor from the HDMI cable. My GPU is an GTX 1080 Ti. I have got a KVM Switch in which is connected my monitor, Keyboard and Mouse. Before the last update of Ubuntu, all worked well. When I go to settings in Ubuntu, I couldn't watch any audio device check the image attached. Regards. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 17:30:22 2021 InstallationDate: Installed on 2021-01-14 (159 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933361/+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 1743247] Re: B2 Python APIs are missing
I'm on 21.04 but I had success resolving this by installing python3-b2sdk with apt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1743247 Title: B2 Python APIs are missing Status in Duplicity: Invalid Status in duplicity package in Ubuntu: Confirmed Bug description: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 which works fine on 16.04, which makes me think this regression was in 0.7.15 or 0.7.16. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1743247/+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 1933540] Re: duplicity falsely reports B2 python SDK not installed, fails backup to B2
Even easier fix - instead of installing b2sdk via pip, installing python3-b2sdk via apt seems to have resolved this issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1933540 Title: duplicity falsely reports B2 python SDK not installed, fails backup to B2 Status in Duplicity: New Status in duplicity package in Ubuntu: Invalid Bug description: Description: Ubuntu 21.04 Release: 21.04 duplicity: Installed: 0.8.17-1build1 Candidate: 0.8.17-1build1 Version table: *** 0.8.17-1build1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: duplicity successfully backs up to B2 when I run `duplicity ~ b2://@` What happened instead: duplicity immediately fails with the error "BackendException: B2 backend requires B2 Python SDK (pip install b2sdk)". duplicity was working fine for me backing up my local machine to BackBlaze B2, when I was running 20.10. After upgrading to 21.04, now I get this problem. Both b2 and b2sdk are installed by pip and pip3, with and without sudo. I do use pyenv to manage different Python versions but pyenv global is set to system when I use pip to try to troubleshoot this, so this should not be interfering ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: duplicity 0.8.17-1build1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Jun 24 12:28:50 2021 InstallationDate: Installed on 2020-11-20 (215 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: Upgraded to hirsute on 2021-06-15 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1933540/+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 1743247] Re: B2 Python APIs are missing
Two options for now: - upgrade to the _latest_ (dev) version of duplicity, - revert to b2sdk==1.7.0 until duplicity 0.8.20 is released To revert do: _sudo pip install -U b2sdk==1.7.0_ There are multiple options for latest: - Latest snap builds - “sudo snap install duplicity —classic —edge" - Latest pip3 builds - “sudo pip3 install --pre duplicity" - Latest duplicity PPA - https://code.launchpad.net/\~duplicity-team/+archive/ubuntu/duplicity-develop-git Note 1: UNINSTALL duplicity first if it was installed from a different source.. This is due to divergent install locations, especially between repository installs and the other forms. Note 2: Launchpad PPAs contain builds for Bionic 18.04, Eoan 19.10, Focal 20.04, Hirsute 20.10 and Impish 21.04. Note 3: Xenial 16.04 works with Snap and Pip installs, but cannot be built under Launchpad PPAs at the moment. ** Changed in: duplicity Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1743247 Title: B2 Python APIs are missing Status in Duplicity: Invalid Status in duplicity package in Ubuntu: Confirmed Bug description: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 which works fine on 16.04, which makes me think this regression was in 0.7.15 or 0.7.16. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1743247/+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 1933540] Re: duplicity falsely reports B2 python SDK not installed, fails backup to B2
** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1933540 Title: duplicity falsely reports B2 python SDK not installed, fails backup to B2 Status in Duplicity: New Status in duplicity package in Ubuntu: Invalid Bug description: Description: Ubuntu 21.04 Release: 21.04 duplicity: Installed: 0.8.17-1build1 Candidate: 0.8.17-1build1 Version table: *** 0.8.17-1build1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: duplicity successfully backs up to B2 when I run `duplicity ~ b2://@` What happened instead: duplicity immediately fails with the error "BackendException: B2 backend requires B2 Python SDK (pip install b2sdk)". duplicity was working fine for me backing up my local machine to BackBlaze B2, when I was running 20.10. After upgrading to 21.04, now I get this problem. Both b2 and b2sdk are installed by pip and pip3, with and without sudo. I do use pyenv to manage different Python versions but pyenv global is set to system when I use pip to try to troubleshoot this, so this should not be interfering ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: duplicity 0.8.17-1build1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Jun 24 12:28:50 2021 InstallationDate: Installed on 2020-11-20 (215 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: Upgraded to hirsute on 2021-06-15 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1933540/+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 1933540] Re: duplicity falsely reports B2 python SDK not installed, fails backup to B2
Potentially a duplicate of https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1743247 but I'm not ready to mark it as duplicate myself since I'm on a different release as that reporter -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1933540 Title: duplicity falsely reports B2 python SDK not installed, fails backup to B2 Status in Duplicity: New Status in duplicity package in Ubuntu: Invalid Bug description: Description: Ubuntu 21.04 Release: 21.04 duplicity: Installed: 0.8.17-1build1 Candidate: 0.8.17-1build1 Version table: *** 0.8.17-1build1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: duplicity successfully backs up to B2 when I run `duplicity ~ b2://@` What happened instead: duplicity immediately fails with the error "BackendException: B2 backend requires B2 Python SDK (pip install b2sdk)". duplicity was working fine for me backing up my local machine to BackBlaze B2, when I was running 20.10. After upgrading to 21.04, now I get this problem. Both b2 and b2sdk are installed by pip and pip3, with and without sudo. I do use pyenv to manage different Python versions but pyenv global is set to system when I use pip to try to troubleshoot this, so this should not be interfering ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: duplicity 0.8.17-1build1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Jun 24 12:28:50 2021 InstallationDate: Installed on 2020-11-20 (215 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: Upgraded to hirsute on 2021-06-15 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1933540/+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 1933540] Re: duplicity falsely reports B2 python SDK not installed, fails backup to B2
Two options for now: - upgrade to the _latest_ (dev) version of duplicity, - revert to b2sdk==1.7.0 until duplicity 0.8.20 is released To revert do: _sudo pip install -U b2sdk==1.7.0_ There are multiple options for latest: - Latest snap builds - “sudo snap install duplicity —classic —edge" - Latest pip3 builds - “sudo pip3 install --pre duplicity" - Latest duplicity PPA - https://code.launchpad.net/\~duplicity-team/+archive/ubuntu/duplicity-develop-git Note 1: UNINSTALL duplicity first if it was installed from a different source.. This is due to divergent install locations, especially between repository installs and the other forms. Note 2: Launchpad PPAs contain builds for Bionic 18.04, Eoan 19.10, Focal 20.04, Hirsute 20.10 and Impish 21.04. Note 3: Xenial 16.04 works with Snap and Pip installs, but cannot be built under Launchpad PPAs at the moment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1933540 Title: duplicity falsely reports B2 python SDK not installed, fails backup to B2 Status in Duplicity: New Status in duplicity package in Ubuntu: Invalid Bug description: Description: Ubuntu 21.04 Release: 21.04 duplicity: Installed: 0.8.17-1build1 Candidate: 0.8.17-1build1 Version table: *** 0.8.17-1build1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: duplicity successfully backs up to B2 when I run `duplicity ~ b2://@` What happened instead: duplicity immediately fails with the error "BackendException: B2 backend requires B2 Python SDK (pip install b2sdk)". duplicity was working fine for me backing up my local machine to BackBlaze B2, when I was running 20.10. After upgrading to 21.04, now I get this problem. Both b2 and b2sdk are installed by pip and pip3, with and without sudo. I do use pyenv to manage different Python versions but pyenv global is set to system when I use pip to try to troubleshoot this, so this should not be interfering ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: duplicity 0.8.17-1build1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Jun 24 12:28:50 2021 InstallationDate: Installed on 2020-11-20 (215 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: Upgraded to hirsute on 2021-06-15 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1933540/+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 1933540] [NEW] duplicity falsely reports B2 python SDK not installed, fails backup to B2
Public bug reported: Description:Ubuntu 21.04 Release:21.04 duplicity: Installed: 0.8.17-1build1 Candidate: 0.8.17-1build1 Version table: *** 0.8.17-1build1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: duplicity successfully backs up to B2 when I run `duplicity ~ b2://@` What happened instead: duplicity immediately fails with the error "BackendException: B2 backend requires B2 Python SDK (pip install b2sdk)". duplicity was working fine for me backing up my local machine to BackBlaze B2, when I was running 20.10. After upgrading to 21.04, now I get this problem. Both b2 and b2sdk are installed by pip and pip3, with and without sudo. I do use pyenv to manage different Python versions but pyenv global is set to system when I use pip to try to troubleshoot this, so this should not be interfering ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: duplicity 0.8.17-1build1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Jun 24 12:28:50 2021 InstallationDate: Installed on 2020-11-20 (215 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: Upgraded to hirsute on 2021-06-15 (8 days ago) ** Affects: duplicity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1933540 Title: duplicity falsely reports B2 python SDK not installed, fails backup to B2 Status in duplicity package in Ubuntu: New Bug description: Description: Ubuntu 21.04 Release: 21.04 duplicity: Installed: 0.8.17-1build1 Candidate: 0.8.17-1build1 Version table: *** 0.8.17-1build1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: duplicity successfully backs up to B2 when I run `duplicity ~ b2://@` What happened instead: duplicity immediately fails with the error "BackendException: B2 backend requires B2 Python SDK (pip install b2sdk)". duplicity was working fine for me backing up my local machine to BackBlaze B2, when I was running 20.10. After upgrading to 21.04, now I get this problem. Both b2 and b2sdk are installed by pip and pip3, with and without sudo. I do use pyenv to manage different Python versions but pyenv global is set to system when I use pip to try to troubleshoot this, so this should not be interfering ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: duplicity 0.8.17-1build1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Jun 24 12:28:50 2021 InstallationDate: Installed on 2020-11-20 (215 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: Upgraded to hirsute on 2021-06-15 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1933540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793124]
For what it's worth, Excel has the same issue but Microsoft is working on a fix: https://excel.uservoice.com/forums/304921/suggestions/9769824 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1793124 Title: [upstream] Scrolling on Calc leaves content invisible if cell is higher than screen Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I sometimes receive Calc documents where the content of an individual cell is split on so many lines that it fills up the whole screen and more. I can easily see the top part of these cells but scrolling to the bottom does not seem to work. Whether I try dragging the scrollbar or moving the screen with my laptop’s touchpad, Calc seems to skip the bottom part of the cell and jump directly to the following cell. See the attached screenshots of a document which has numbers 1 to 50 so that numbers 4 to 40 occupy one single cell (A4). In the first screenshot I see the top part of that cell (4 to 23) and in the next I have scrolled down the screen as little as possible, and now I see cell A5 (number 41) on the top. Everything in between is visually inaccessible whatever I try. Description: Ubuntu 18.04.1 LTS Release: 18.04 Installed: 1:6.0.3-0ubuntu1 Candidate: 1:6.0.3-0ubuntu1 Version table: *** 1:6.0.3-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-calc 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 18 11:16:17 2018 InstallationDate: Installed on 2017-02-13 (582 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933361] Re: Audio Problem, soundcard not detected
Why do I need to install nothing when an Ubuntu Update is installed? It has no sense. The Ubuntu Update must have all the things that the update need. I have installed this: sudo apt install linux-generic and this: sudo apt install linux-generic-hwe-20.04 but it doesn't work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1933361 Title: Audio Problem, soundcard not detected Status in alsa-driver package in Ubuntu: New Bug description: Hi, After last patch in Ubuntu 20.04.2 LTS, I have lost my audio. I have got an Asus monitor with speakers inside the monitor. The sound come to the monitor from the HDMI cable. My GPU is an GTX 1080 Ti. I have got a KVM Switch in which is connected my monitor, Keyboard and Mouse. Before the last update of Ubuntu, all worked well. When I go to settings in Ubuntu, I couldn't watch any audio device check the image attached. Regards. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 17:30:22 2021 InstallationDate: Installed on 2021-01-14 (159 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933361/+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 1933537] [NEW] add-apt-repository should store PGP keys in /usr/share/keyrings because /etc/apt/trusted.gpg.d is deprecated for third party repos
Public bug reported: PPAs are third party repositories. for security reasons, PGP keys for these must not be placed in /etc/apt/trusted.gpg.d, according to this document: https://wiki.debian.org/DebianRepository/UseThirdParty they should instead be saved to /usr/share/keyrings and the generated .list file for the repo added should refer to its particular key by using a [signed-by=/usr/share/keyrings/...] argument. this ensures that the downloaded PGP key will only be used to verify a particular repository and is not globally available to verify package lists of all configured repositories (as are all keys found in /etc/apt/trusted.gpg.d). please fix add-apt-repository accordingly. Ubuntu 20.04.2 LTS software-properties-common 0.98.9.5 ** 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/1933537 Title: add-apt-repository should store PGP keys in /usr/share/keyrings because /etc/apt/trusted.gpg.d is deprecated for third party repos Status in software-properties package in Ubuntu: New Bug description: PPAs are third party repositories. for security reasons, PGP keys for these must not be placed in /etc/apt/trusted.gpg.d, according to this document: https://wiki.debian.org/DebianRepository/UseThirdParty they should instead be saved to /usr/share/keyrings and the generated .list file for the repo added should refer to its particular key by using a [signed-by=/usr/share/keyrings/...] argument. this ensures that the downloaded PGP key will only be used to verify a particular repository and is not globally available to verify package lists of all configured repositories (as are all keys found in /etc/apt/trusted.gpg.d). please fix add-apt-repository accordingly. Ubuntu 20.04.2 LTS software-properties-common 0.98.9.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1933537/+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 1933536] [NEW] jsc CLI crashes upon start
Public bug reported: epx@zypred:~$ jsc Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libjavascriptcoregtk-4.0-bin 2.32.0-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 24 15:37:44 2021 InstallationDate: Installed on 2021-04-13 (72 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1933536 Title: jsc CLI crashes upon start Status in webkit2gtk package in Ubuntu: New Bug description: epx@zypred:~$ jsc Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libjavascriptcoregtk-4.0-bin 2.32.0-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 24 15:37:44 2021 InstallationDate: Installed on 2021-04-13 (72 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1933536/+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 1931272] Re: [SRU] libreoffice 7.1.4 for hirsute
** Changed in: libreoffice (Ubuntu) Status: In Progress => 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/1931272 Title: [SRU] libreoffice 7.1.4 for hirsute Status in libreoffice package in Ubuntu: Fix Committed Status in libreoffice source package in Hirsute: Fix Committed Bug description: [Impact] * LibreOffice 7.1.4 is in its forth bugfix release of the 7.1 line: https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.4_release * Version 7.1.3 is currently released in hirsute. For a list of fixed bugs compared to 7.1.3 see the list of bugs fixed in the release candidates of 7.1.4 (that's a total of 79 bugs): https://wiki.documentfoundation.org/Releases/7.1.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.1.4/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_71/1220/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/amd64/libr/libreoffice/20210607_174726_685e9@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/arm64/libr/libreoffice/20210608_013339_0abc1@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/armhf/libr/libreoffice/20210607_175937_445f4@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/ppc64el/libr/libreoffice/20210607_221555_8f69a@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/s390x/libr/libreoffice/20210609_131734_bd6bf@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 79 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1931272/+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 1931514] Re: The NVIDIA X server Settings is blank when under Intel mode
I have integrated, modified, and uploaded the changes to this PPA: https://launchpad.net/~albertomilone/+archive/ubuntu/u-d-c-release Please give it a try and see if it solves the problem. If it does, I will proceed with the SRU. -- 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/1931514 Title: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Changed in: bluez Status: Unknown => 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+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 1933506] [NEW] ubuntu 20.04 no show cursor in 1 of 3 monitors
Public bug reported: Install Ubuntu 20.04, I have 3 monitors but I can not make the mouse work on the monitor 1, stays stuck on the center monitor and does not pass the cursor. If I use the option on the title bar and press "Move to the screen on the left this works without problem" However, it could not access the window that I sent to that screen. That is to say everything works but the mouse does not pass, and attempting by removing the stickers with "Retouch Editor" but it does not work, also try changing the dock and monitor but the problem with the monitor 1 persists. ** Affects: gpm (Ubuntu) Importance: Undecided Status: New ** Tags: 3monitor ** Attachment added: "simplescreenrecorder-2021-06-24_08.24.17.mkv" https://bugs.launchpad.net/bugs/1933506/+attachment/5506733/+files/simplescreenrecorder-2021-06-24_08.24.17.mkv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1933506 Title: ubuntu 20.04 no show cursor in 1 of 3 monitors Status in gpm package in Ubuntu: New Bug description: Install Ubuntu 20.04, I have 3 monitors but I can not make the mouse work on the monitor 1, stays stuck on the center monitor and does not pass the cursor. If I use the option on the title bar and press "Move to the screen on the left this works without problem" However, it could not access the window that I sent to that screen. That is to say everything works but the mouse does not pass, and attempting by removing the stickers with "Retouch Editor" but it does not work, also try changing the dock and monitor but the problem with the monitor 1 persists. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1933506/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Status in evolution-data-server source package in Hirsute: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1933452] Re: secondary portrait monitor is not portrait during boot
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933452 Title: secondary portrait monitor is not portrait during boot Status in xorg package in Ubuntu: New Bug description: I'm using Ubuntu 20.04 in my laptop. with that i'm using a secondary monitor which is portrait. these 2 works fine but in the boot menu, secondary monitor's screen is wrong. it's not portrait. please fix this issue. Thank you. Regards, Shehan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 24 15:49:32 2021 DistUpgraded: 2020-10-11 07:43:44,586 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-53-generic, x86_64: installed nvidia, 390.138, 5.4.0-54-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-53-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-54-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:098a] Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940M] [1025:098c] InstallationDate: Installed on 2019-06-23 (731 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Aspire E5-573G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=2151ff19-8bcb-4ed7-aded-0cfb4745ec95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-10-11 (256 days ago) dmi.bios.date: 03/17/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd03/17/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-573G dmi.product.sku: Aspire E5-573G_098A_1_07 dmi.product.version: V3.72 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1933452/+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 1933452] [NEW] secondary portrait monitor is not portrait during boot
You have been subscribed to a public bug: I'm using Ubuntu 20.04 in my laptop. with that i'm using a secondary monitor which is portrait. these 2 works fine but in the boot menu, secondary monitor's screen is wrong. it's not portrait. please fix this issue. Thank you. Regards, Shehan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 24 15:49:32 2021 DistUpgraded: 2020-10-11 07:43:44,586 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-53-generic, x86_64: installed nvidia, 390.138, 5.4.0-54-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-53-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-54-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:098a] Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940M] [1025:098c] InstallationDate: Installed on 2019-06-23 (731 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Aspire E5-573G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=2151ff19-8bcb-4ed7-aded-0cfb4745ec95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-10-11 (256 days ago) dmi.bios.date: 03/17/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd03/17/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-573G dmi.product.sku: Aspire E5-573G_098A_1_07 dmi.product.version: V3.72 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- secondary portrait monitor is not portrait during boot https://bugs.launchpad.net/bugs/1933452 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
> Declaring "Fix Committed" when a fix exists in an upstream tributary before anything has reached proposed is a procedure requested by seb128 and we now follow on the desktop team. I'm not sure what you mean by "upstream tributary", but if the fix exists in the main Ubuntu packaging branch used by the desktop team (ie. Vcs-Git in debian/control points to it) then that makes sense, as it was in this case. If you mean it's just fixed upstream somewhere, then that doesn't make sense - Launchpad's bug tracker expects to have a separate task to track upstream status if you want that. However, from an SRU perspective, I would expect an upload to the development release *before* an SRU is uploaded. Sometimes we make concessions (eg. during a development release freeze), but I don't think a sponsorship delay qualifies. The sponsor should be able to sponsor to the development release first, so there's no reason not to do it. I see it's there now, but please could you adjust your processes to make sure that in the normal case, this happens? This would save me reviewing the SRU twice. -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Unknown Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893&r=1&w=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Pos
[Desktop-packages] [Bug 1933445] [NEW] Thunderbird crashes on startup
Public bug reported: After normal system upgrade thunderbird (1.78) start results in a window: We're Sorry Thunderbird had a problem and crashed. ... Removing current user profile ~/.thunderbird does not solve the problem. Starting on console gives: [calBackendLoader] Using Thunderbird's libical backend console.debug: "Successfully loaded OpenPGP library librnp.so version 0.14+git20210121.7c8492b4.MZLA from /usr/lib/thunderbird/librnp.so" console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0 unprotected)" console.debug: "Successfully loaded optional OpenPGP library libgpgme.so.11 from system's standard library locations" console.debug: "gpgme version: 1.14.0-unknown" Unable to SHM memory segment ExceptionHandler::GenerateDump cloned child 6098 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.11.0+build1-0ubuntu0.21.04.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BuildID: 20210528153351 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 24 11:01:38 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes InstallationDate: Installed on 2021-04-25 (60 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=78.11.0/20210528153351 SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages wayland-session ** Summary changed: - Thunderbird crahes on startup + Thunderbird crashes on startup -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1933445 Title: Thunderbird crashes on startup Status in thunderbird package in Ubuntu: New Bug description: After normal system upgrade thunderbird (1.78) start results in a window: We're Sorry Thunderbird had a problem and crashed. ... Removing current user profile ~/.thunderbird does not solve the problem. Starting on console gives: [calBackendLoader] Using Thunderbird's libical backend console.debug: "Successfully loaded OpenPGP library librnp.so version 0.14+git20210121.7c8492b4.MZLA from /usr/lib/thunderbird/librnp.so" console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0 unprotected)" console.debug: "Successfully loaded optional OpenPGP library libgpgme.so.11 from system's standard library locations" console.debug: "gpgme version: 1.14.0-unknown" Unable to SHM memory segment ExceptionHandler::GenerateDump cloned child 6098 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.11.0+build1-0ubuntu0.21.04.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BuildID: 20210528153351 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 24 11:01:38 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes InstallationDate: Installed on 2021-04-25 (60 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=78.11.0/20210528153351 SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1933445/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages M
[Desktop-packages] [Bug 1892573] Re: syslog gdm-x-session "your system is too slow" as desktop GUI slows down and eventually stops
*** This bug is a duplicate of bug 1870597 *** https://bugs.launchpad.net/bugs/1870597 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892573 Title: syslog gdm-x-session "your system is too slow" as desktop GUI slows down and eventually stops Status in mutter package in Ubuntu: Confirmed Bug description: After ~72 hours, my Gnome desktop will be very slow. In syslog I noticed that I get a bunch of these messages as the system slows down: /usr/lib/gdm3/gdm-x-session[13460]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-30ms), your system is too slow ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.4-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 22 18:02:23 2020 InstallationDate: Installed on 2020-02-23 (181 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892573/+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 1923845] Re: Please compress packages with zstd by default
** Changed in: debian-el (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
Fix Released
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in hello package in Ubuntu:
Fix Released
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
Fix Released
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
Fix Released
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Status in debian-el package in Debian:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
insighttoolkit4 - skip, ...orig-data.tar.xz
j
