[Touch-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
So this "fix" seems to cause Kernels released with zesty (and newer) keep the monitor always ON. No blanking, and no power down either. Before this fix, a clean install of Ubuntu server would signal the monitor to sleep/standby after a short while. Now the default behavior is to leave the monitor always on, wasting power. While blanking itself should be negligible to power savings and monitor longevity, sleep states are still an important feature. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834554] Re: [nvidia] Screen displays dynamic corruptions
If the location and shape of the problem never changes then one possible explanation would be small areas of failing RAM on the graphics card. It might also be a software bug of course. ** Summary changed: - Screen displays dynamic corruptions + [nvidia] Screen displays dynamic corruptions ** Tags added: nvidia ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-340 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1834554 Title: [nvidia] Screen displays dynamic corruptions Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Regularly the screen displays corruptions that change depending on disk i/o, keyboard/mouse and other system activity. The screen corruptions do not appear on each session and can be removed by selecting an alternative resolution and then changing back (or reverting without accepting the change). The location of the corruptions is stereotypical and always has the same shape characteristics. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Jun 28 12:14:17 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 4.18.0-15-generic, x86_64: installed nvidia-340, 340.107, 4.18.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT200b [GeForce GTX 275] [10de:05e6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology GT200b [GeForce GTX 275] [10b0:0801] Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 470/480/570/580] [1458:22fc] InstallationDate: Installed on 2019-06-25 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-24-generic root=UUID=b92b7098-365d-445a-b980-7fe3bc3b73da ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0504 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0504:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to:
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
In the meantime, I brought arm64 back almost as soon as
https://salsa.debian.org/systemd-team/systemd/merge_requests/34 was
merged. It looks promising except that the "upstream" test is flaky
there as well. It'd be great to turn it off on Ubuntu CI.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1829829
Title:
Ubuntu CI has been flaky for a week
Status in systemd package in Ubuntu:
Confirmed
Bug description:
It was originally reported in
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days
ago. To judge from the logs VMs can't be rebooted there:
```
Ubuntu 18.04.2 LTS autopkgtest ttyS0
autopkgtest login:
---
--- nova show 91e76a78-d05c-412a-b383-55a26010ae69
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
+--++
| Property | Value
|
+--++
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | euler
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack
|
| OS-EXT-SRV-ATTR:instance_name| instance-003d216a
|
| OS-EXT-STS:power_state | 1
|
| OS-EXT-STS:task_state| -
|
| OS-EXT-STS:vm_state | active
|
| OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive |
|
| created | 2019-05-16T07:00:33Z
|
| flavor | autopkgtest
(f878e70e-9991-46e0-ba02-8ea159a71656) |
| hostId |
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
|
| id | 91e76a78-d05c-412a-b383-55a26010ae69
|
| image|
adt/ubuntu-bionic-amd64-server-20190516.img
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
| key_name |
testbed-juju-prod-ues-proposed-migration-machine-11
|
| metadata | {}
|
| name |
adt-bionic-amd64-systemd-upstream-20190516-051604
|
| net_ues_proposed_migration network | 10.42.40.13
|
| os-extended-volumes:volumes_attached | []
|
| progress | 0
|
| security_groups | autopkgtest@lcy01-27.secgroup
|
| status | ACTIVE
|
| tenant_id| afaef86b96dd4828a1ed5ee395ea1421
|
| updated | 2019-05-16T07:00:42Z
|
| user_id |
[Touch-packages] [Bug 1834554] [NEW] Screen displays dynamic corruptions
Public bug reported: Regularly the screen displays corruptions that change depending on disk i/o, keyboard/mouse and other system activity. The screen corruptions do not appear on each session and can be removed by selecting an alternative resolution and then changing back (or reverting without accepting the change). The location of the corruptions is stereotypical and always has the same shape characteristics. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Jun 28 12:14:17 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 4.18.0-15-generic, x86_64: installed nvidia-340, 340.107, 4.18.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT200b [GeForce GTX 275] [10de:05e6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology GT200b [GeForce GTX 275] [10b0:0801] Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 470/480/570/580] [1458:22fc] InstallationDate: Installed on 2019-06-25 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-24-generic root=UUID=b92b7098-365d-445a-b980-7fe3bc3b73da ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0504 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0504:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1834554 Title: Screen displays dynamic corruptions Status in xorg package in Ubuntu: New Bug description: Regularly the screen displays corruptions that change depending on disk i/o, keyboard/mouse and other system activity. The screen corruptions do not appear on each session and can be removed by selecting an alternative resolution and then changing back (or reverting without accepting the change). The location of the corruptions is stereotypical and always has the same shape characteristics. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic
[Touch-packages] [Bug 1834554] Re: Screen displays dynamic corruptions
Screen shots of the corruption do not work as the screen shot tool appears to overwrite the corruption. Video capture does work. ** Attachment added: "Video capture of screen corruption" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834554/+attachment/5273854/+files/screen-speckles.ogv -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1834554 Title: Screen displays dynamic corruptions Status in xorg package in Ubuntu: New Bug description: Regularly the screen displays corruptions that change depending on disk i/o, keyboard/mouse and other system activity. The screen corruptions do not appear on each session and can be removed by selecting an alternative resolution and then changing back (or reverting without accepting the change). The location of the corruptions is stereotypical and always has the same shape characteristics. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Jun 28 12:14:17 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 4.18.0-15-generic, x86_64: installed nvidia-340, 340.107, 4.18.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT200b [GeForce GTX 275] [10de:05e6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology GT200b [GeForce GTX 275] [10b0:0801] Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 470/480/570/580] [1458:22fc] InstallationDate: Installed on 2019-06-25 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-24-generic root=UUID=b92b7098-365d-445a-b980-7fe3bc3b73da ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0504 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0504:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Thanks for working on this and preparing the debdiffs. Has the debian package changed from interest to interest-noawait? Is there a bug in debian regarding this issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly
** Tags added: bionic ** Also affects: bzip2 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1834494 Title: latest bzip2 reports crc errors incorrectly Status in bzip2 package in Ubuntu: Confirmed Status in bzip2 source package in Bionic: New Bug description: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Changed in: systemd (Debian) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: Fix Committed Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Released Status in linux source package in Disco: New Status in systemd source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Status in systemd package in Debian: Fix Committed Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810346] Re: VLC interface not displayed correctly
I also tested 18.04 again with another setup, still dual screen on a samsung TV, the vlc GUI is exageratly zoomed but still correctly visible and usable, not sure if they want it to be zoomed like that. ** Attachment added: "IdUAJtp.png" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+attachment/5273828/+files/IdUAJtp.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1810346 Title: VLC interface not displayed correctly Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: I use vlc on a Dell E-5530 laptop seated on its docking station. The laptop display cover is closed, the output is sent on an external LG TV with 1920x1080. This system has been working flawlessly for many years, resp. under late 14.04 and 16.04. After recently upgrading to 18.04, I noticed VLC wouldn't display correctly - see attachment. This only occurs on the external display ; if I open the cover and use the internal display, there is no problem - except I cannot work on the internal display. regards, J.-Luc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vlc-bin 3.0.4-1ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 23:38:36 2019 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2018-12-19 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
This is confusing, I'm seeing the timeout with a TLSv1.2 connection, and the commit pointed out in comment #9 mentions TLSv1.3. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833039 Title: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1 Status in apache2 package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Confirmed Bug description: I am using Apache2 with client certificate authentication. Since recently (last week) and without any configuration changes, the following errors occur frequently: AH02042: rejecting client initiated renegotiation Client connections are very slow and sometimes it takes more than a minute until a weg page can be opened in the browser. Before installation of the latest security fixes last week, this error did not occur. Could it be related to https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689? System information: Description:Ubuntu 18.04.2 LTS Release:18.04 apache2: Installiert: 2.4.29-1ubuntu4.6 Installationskandidat: 2.4.29-1ubuntu4.6 Versionstabelle: *** 2.4.29-1ubuntu4.6 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.29-1ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages openssl: Installiert: 1.1.1-1ubuntu2.1~18.04.2 Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2 Versionstabelle: *** 1.1.1-1ubuntu2.1~18.04.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.0g-2ubuntu4.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.1.0g-2ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
I can try some or all of the patches mentioned in https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689/comments/2 That bug might be a duplicate, btw. (or this one) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833039 Title: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1 Status in apache2 package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Confirmed Bug description: I am using Apache2 with client certificate authentication. Since recently (last week) and without any configuration changes, the following errors occur frequently: AH02042: rejecting client initiated renegotiation Client connections are very slow and sometimes it takes more than a minute until a weg page can be opened in the browser. Before installation of the latest security fixes last week, this error did not occur. Could it be related to https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689? System information: Description:Ubuntu 18.04.2 LTS Release:18.04 apache2: Installiert: 2.4.29-1ubuntu4.6 Installationskandidat: 2.4.29-1ubuntu4.6 Versionstabelle: *** 2.4.29-1ubuntu4.6 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.29-1ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages openssl: Installiert: 1.1.1-1ubuntu2.1~18.04.2 Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2 Versionstabelle: *** 1.1.1-1ubuntu2.1~18.04.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.0g-2ubuntu4.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.1.0g-2ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
Same thing. Another, or an additional, fix is needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833039 Title: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1 Status in apache2 package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Confirmed Bug description: I am using Apache2 with client certificate authentication. Since recently (last week) and without any configuration changes, the following errors occur frequently: AH02042: rejecting client initiated renegotiation Client connections are very slow and sometimes it takes more than a minute until a weg page can be opened in the browser. Before installation of the latest security fixes last week, this error did not occur. Could it be related to https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689? System information: Description:Ubuntu 18.04.2 LTS Release:18.04 apache2: Installiert: 2.4.29-1ubuntu4.6 Installationskandidat: 2.4.29-1ubuntu4.6 Versionstabelle: *** 2.4.29-1ubuntu4.6 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.29-1ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages openssl: Installiert: 1.1.1-1ubuntu2.1~18.04.2 Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2 Versionstabelle: *** 1.1.1-1ubuntu2.1~18.04.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.0g-2ubuntu4.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.1.0g-2ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly
Hi, Thanks for report this issue. I added a comment in commit fix that caused this regression in upstream project: https://gitlab.com/federicomenaquintero/bzip2/commit/74de1e2e6ffc9d51ef9824db71a8ffee5962cdbc Soon they update there with some notes we can look for a fix. For now, as you already did, please try downgrade to the previous version. Also, if possible, could you please test it using upstream version? We apologize for the inconvenience. ** Changed in: bzip2 (Ubuntu) Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1834494 Title: latest bzip2 reports crc errors incorrectly Status in bzip2 package in Ubuntu: Confirmed Bug description: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810346] Re: VLC interface not displayed correctly
I just checked and the bug is still there on 19.04. ** Attachment added: "Screenshot from 2019-06-27 20-05-31.png" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+attachment/5273821/+files/Screenshot%20from%202019-06-27%2020-05-31.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1810346 Title: VLC interface not displayed correctly Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: I use vlc on a Dell E-5530 laptop seated on its docking station. The laptop display cover is closed, the output is sent on an external LG TV with 1920x1080. This system has been working flawlessly for many years, resp. under late 14.04 and 16.04. After recently upgrading to 18.04, I noticed VLC wouldn't display correctly - see attachment. This only occurs on the external display ; if I open the cover and use the internal display, there is no problem - except I cannot work on the internal display. regards, J.-Luc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vlc-bin 3.0.4-1ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 23:38:36 2019 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2018-12-19 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"
** Changed in: software-properties (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1834226 Title: update-notifier doesn't respect "automatically check for updates: Never" Status in software-properties package in Ubuntu: New Bug description: This has been a long-standing problem with various ubuntu installations, and I'm sensing some reticence in doing anything about it. This attitude also seems to be purposeful to try to cajole updates on people who make bad choices due to confusion/fud/paranoia. apt install fails due to: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? A great deal of networking is taking place despite setting automatic upgrades to "never". Cycling this doesn't seem to do anything. This action is hostile to programmers and the setting should be respected. Wisdom on threads is to let it update until it's out of updates, and then it supposedly respects the "never" flag, but the experience I'm having is much more non-deterministic. have been using 19.04 for weeks now and still get the background notifier using data and getting in the way of aptitude package installations. I prefer manual update && upgrade once my code is ready to push. Is there another way around this or are people just living with it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1834226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
I can reproduce this with stock bionic (plus updates applied). ==> /var/log/apache2/error.log <== [Thu Jun 27 19:37:43.049064 2019] [ssl:error] [pid 3084:tid 140343919978240] [client 10.0.100.1:45036] AH02261: Re-negotiation handshake failed It's a bit complicated to setup, as usual with SSL certificates, but doable. Let me try the ppa now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833039 Title: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1 Status in apache2 package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Confirmed Bug description: I am using Apache2 with client certificate authentication. Since recently (last week) and without any configuration changes, the following errors occur frequently: AH02042: rejecting client initiated renegotiation Client connections are very slow and sometimes it takes more than a minute until a weg page can be opened in the browser. Before installation of the latest security fixes last week, this error did not occur. Could it be related to https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689? System information: Description:Ubuntu 18.04.2 LTS Release:18.04 apache2: Installiert: 2.4.29-1ubuntu4.6 Installationskandidat: 2.4.29-1ubuntu4.6 Versionstabelle: *** 2.4.29-1ubuntu4.6 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.29-1ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages openssl: Installiert: 1.1.1-1ubuntu2.1~18.04.2 Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2 Versionstabelle: *** 1.1.1-1ubuntu2.1~18.04.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.0g-2ubuntu4.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.1.0g-2ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1834494 Title: latest bzip2 reports crc errors incorrectly Status in bzip2 package in Ubuntu: Confirmed Bug description: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell
Sorry for the late answer. In my case, the sound was the correct one, but it was played twice at the same time, causing some unpleasant saturation. Furthermore, if I changed the sound in the Gnome control panel, than I would have two different sounds playing at the same time (the newly configure Gnome sound, plus the old one, played by module-x11-bell). That being said, I have not tried it on a fresh disco install. Mine was installed a year ago, and upgraded to disco... It took me that much time to investigate the problem and report it ;-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827842 Title: pulseaudio should not load module-x11-bell in gnome-shell Status in pulseaudio package in Ubuntu: Triaged Bug description: The package `pulseaudio` installs a startup script in `/etc/xdg/autostart/pulseaudio.desktop`, which itself runs `/usr/bin/start-pulseaudio-x11`, which loads a number of x11 related modules in `pulseaudio`. One of these modules is `module-x11-bell`, which makes `pulseaudio` play a sound each time a system bell is emitted (usually by terminal applications, such as bash or vim). This is redundant with gnome-shell, which is also able to handle the system bell (through the gsetting key `org.gnome.desktop.sound event-sounds`). The gnome system bell is directly configurable by the user (Settings > Sound), so it should be preferred over pulseaudio's own system bell. I suggest to patch the `/usr/bin/start-pulseaudio-x11`, to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome Shell (e.g. if GNOME_SHELL_SESSION_MODE is set). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828663] Re: policykit failures due to internal user id mismatch
** Changed in: policykit-1 Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1828663 Title: policykit failures due to internal user id mismatch Status in PolicyKit: New Status in lubuntu-meta package in Ubuntu: Invalid Status in lxqt-policykit package in Ubuntu: Invalid Status in policykit-1 package in Ubuntu: Confirmed Status in polkit-qt-1 package in Ubuntu: New Bug description: After adding a second user to the sudo group any authentication in the QT applications menu fails, till I manually remove the second user from the sudo group by issuing deluser chiara sudo in terminal window. Lubuntu 19.04 (fresh install, in italian) 1)open the preferences/LXQt settins/user and groups menu from the application menu 2)add new user, before saving add it to sudo group; save (password asked for user currently logged on, as expected - then new user password asked, user created -all ok) 3)restart system 4) log in as newly created user; open the same interface preferences/LXQt settins/user and groups; try changing the full name field (properties of your own user): logged user password asked (and... why? User two is changing himself) 5)popup showed: "Error executing command as another user: Not authorized" & user unchanged. 6)if you exit session, reenter with the first user, also him is now unable to use interface ti change users via interface 7)using terminal, delete second user from sudo group 8)restart system 9)athenticated interface working again. It happened me both at home on a phisical laptop and on a virtual machine at office, where I could do it all twice. By the way, also plasma-discover tells me I haven't the right to update/install when I have two sudoers (tried at home to remove second sudoer to fix it, and it worked) So it seems that the authentication mechanism of the QT graphical interface fails when there are more then one sudoer on the system - but only for applications started from the application menu. Launching the same application via terminal (sudo plasma-discovery) works. commands issued by the interface (which lead to "unauthorized" error: --change user pkexec --disable-internal-agent lxqt-admin-user-helper usermod -c marco marcop --plasma-discover polkit-agent-helper-1 marcop To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1828663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly
Bug is also present with other Nvidia Jetson packages. https://devtalk.nvidia.com/default/topic/1056381/jetson-agx-xavier/jetpack-4-2-xavier-install-failed/post/5355851/?offset=4#5355865 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1834494 Title: latest bzip2 reports crc errors incorrectly Status in bzip2 package in Ubuntu: Confirmed Bug description: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bzip2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1834494 Title: latest bzip2 reports crc errors incorrectly Status in bzip2 package in Ubuntu: Confirmed Bug description: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825470] Re: systemd-networkd: Deconfigures bridge after last attached interface disconnects (ie: LXC)
** Changed in: systemd (Ubuntu Disco) Status: New => Incomplete ** Changed in: systemd (Ubuntu Bionic) Status: New => Incomplete ** Changed in: systemd (Ubuntu Cosmic) Status: New => Incomplete ** Changed in: systemd (Ubuntu Eoan) Importance: Medium => Undecided -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825470 Title: systemd-networkd: Deconfigures bridge after last attached interface disconnects (ie: LXC) Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Bionic: Incomplete Status in systemd source package in Cosmic: Incomplete Status in systemd source package in Disco: Incomplete Status in systemd source package in Eoan: Incomplete Bug description: Ubuntu 18.04 Bionic Beaver An issue was reported to systemd-networkd on GitHub - https://github.com/systemd/systemd/issues/11650 - and all the thorough details are there. Using anonymous bridges (ie: not attached to physical NICs) is problematic with systemd-networkd as they get deconfigured as soon as the last attached device disconnects (ie: a LXC container). Static IP configuration must be done again manually. The root cause is that systemd-networkd assumes that every network interface have a carrier signal. There's no notion of carrier signal on anonymous bridges, a case not properly handled by systemd-networkd. The systemd dev team provided a patch to address the issue and it would be nice to be integrated on the Ubuntu package. The PR is here : https://github.com/systemd/systemd/commit/93b4dab57e2e13bd804cbee999241be65a443e2e To get the proper fix, you'll need to combine 2 patches : - The one from the PR above - Another patch [1] which fixes a segfault introduced by the PR. [1] https://github.com/systemd/systemd/pull/11741/commits/a294af6810df3c18909a96b556deadba0e2ab0a9 On my test environment, I rebuild the Ubuntu package with the 2 patches above from "237-3ubuntu10.17" to "237-3ubuntu10.20" and made thorough tests without hiting a single issue so I think we can assume that these 2 patches are safe to use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828892] Autopkgtest regression report (systemd/229-4ubuntu21.22)
All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1828892 Title: systemctl - alias service reports inactive while aliased is active Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] 'systemctl is-active' command reports an alias service as inactive even though the aliased service is active. Currently the 'systemctl is-active' command does not load units to minimise its effect on the system (i.e. that a monitoring command does not itself alter the state of the system). However, this behaviour leads to inconsistencies when services are aliased. [Test case] - Test case 1 - libvirtd alias service : libvirtd aliased service : libvirt-bin /etc/systemd/system$ ls -la libvirtd.service lrwxrwxrwx 1 root root 39 May 13 20:49 libvirtd.service -> /lib/systemd/system/libvirt-bin.service $ systemctl is-active libvirtd inactive $ systemctl is-active libvirt-bin active - Test case 2 - sshd alias service : sshd aliased service : ssh /ect/systemd/system$ ls -la sshd.service lrwxrwxrwx 1 root root 31 Mar 19 19:44 sshd.service -> /lib/systemd/system/ssh.service $ systemctl is-active sshd inactive $ systemctl is-active ssh active [Regression Potential] This fix may result into systemctl reporting inconsistent information concerning the status of a service. [Other] Upstream issue : https://github.com/systemd/systemd/issues/7875 Upstream fix : https://github.com/systemd/systemd/pull/7997 Xenial is affected, fix exists on Bionic onward. $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.21 Candidate: 229-4ubuntu21.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830477] Autopkgtest regression report (systemd/229-4ubuntu21.22)
All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1830477 Title: systemd-fsckd, cmdline-upstart-boot tests fail on xenial s390x Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [impact] these tests require, and modify, grub. That fails on s390x on xenial because it does not use grub. [test case] run the autopkgtests for xenial on s390x [regression potential] low; only skipping test cases on s390x. [other info] in bionic and later, systemd-fsckd has support for zipl (s390x bootloader) and cmdline-upstart-boot is removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Autopkgtest regression report (systemd/229-4ubuntu21.22)
All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Committed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814373] Autopkgtest regression report (systemd/229-4ubuntu21.22)
All autopkgtests for the newly accepted systemd (229-4ubuntu21.22) for xenial have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: Fix Committed Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Released Status in linux source package in Disco: New Status in systemd source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Status in systemd package in Debian: Confirmed Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"
In the updates tab, I keep all three boxes checked under "Install updates from:", because I like to manually run `sudo apt-get update && sudo apt-get upgrade` whenever I have a good stable release of software and feel like stomaching a raft of system changes. In past versions of ubuntu going back 'Dapper Drake', I'd change the setting for "automatically check for updates" and it was generally good about respecting this setting from my recollection. I'm not sure which release changed this but it's for sure worse, the updater tries to run in the background, and I've noticed it's easy to repeat as I've installed 19.04 on various machines. I've got laptops and desktops alike with 19.04 installed, and they all have this problem. I tried letting it actually do the updates, but that didn't work so I generally cancel it. This non-deterministic behavior is nonsensical. When update-notifier runs, check this flag and quit if it's set to 'Never'. There's really nothing else to debug, is there? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1834226 Title: update-notifier doesn't respect "automatically check for updates: Never" Status in software-properties package in Ubuntu: Incomplete Bug description: This has been a long-standing problem with various ubuntu installations, and I'm sensing some reticence in doing anything about it. This attitude also seems to be purposeful to try to cajole updates on people who make bad choices due to confusion/fud/paranoia. apt install fails due to: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? A great deal of networking is taking place despite setting automatic upgrades to "never". Cycling this doesn't seem to do anything. This action is hostile to programmers and the setting should be respected. Wisdom on threads is to let it update until it's out of updates, and then it supposedly respects the "never" flag, but the experience I'm having is much more non-deterministic. have been using 19.04 for weeks now and still get the background notifier using data and getting in the way of aptitude package installations. I prefer manual update && upgrade once my code is ready to push. Is there another way around this or are people just living with it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1834226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1220013] Re: python-apt can SIGSEGV when encountering Packages stanzas with no Description field (was: update-apt-xapian-index crashed with SIGSEGV in File())
Hello. It is still unclear whether this is still an issue in apt-xapian-index or the underlying python apt bindings. I am marking this as Incomplete for apt-xapian-index as this is still marked as affecting it and has been since 2015, and the Trusty that was affected is End of Life. Please verify if this remains an issue or not. ** Changed in: apt-xapian-index (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1220013 Title: python-apt can SIGSEGV when encountering Packages stanzas with no Description field (was: update-apt-xapian-index crashed with SIGSEGV in File()) Status in apt package in Ubuntu: Fix Released Status in apt-xapian-index package in Ubuntu: Incomplete Status in python-apt package in Ubuntu: Triaged Bug description: Errors Bucket: http://errors.ubuntu.com/bug/1220013 There are 600+ reports of this on errors.ubuntu.com. Something wrong ProblemType: CrashDistroRelease: Ubuntu 13.10 Package: apt-xapian-index 0.45ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic i686 ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Tue Sep 3 01:23:23 2013 ExecutablePath: /usr/sbin/update-apt-xapian-index InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --quiet ProcEnviron: TERM=linux PATH=(custom, no user) SHELL=/bin/sh SegvAnalysis: Segfault happened at: 0xb6c9e020:imul $0x3c,(%eax),%ebp PC (0xb6c9e020) ok source "$0x3c" ok destination "(%eax)" (0xd7ac1000) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11SourcePackage: apt-xapian-index StacktraceTop: ?? () from /usr/lib/python2.7/dist-packages/apt_pkg.so ?? () PyObject_GetAttr () PyEval_EvalFrameEx () ?? () Title: update-apt-xapian-index crashed with SIGSEGV in PyObject_GetAttr() UpgradeStatus: Upgraded to saucy on 2013-08-16 (17 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1220013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817559] Re: update-notifier ignores software-properties's settings
** Summary changed: - update-notifier ignores update-manager's settings + update-notifier ignores software-properties's settings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1817559 Title: update-notifier ignores software-properties's settings Status in software-properties package in Ubuntu: Triaged Bug description: > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 > 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy update-manager update-manager: Installed: 1:16.04.15 Candidate: 1:16.04.15 Version table: *** 1:16.04.15 500 500 https://mirror.one.com/ubuntu xenial-updates/main amd64 Packages 500 https://mirror.one.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 1:16.04.12 500 500 https://mirror.one.com/ubuntu xenial-security/main amd64 Packages 500 https://mirror.one.com/ubuntu xenial-security/main i386 Packages 1:16.04.3 500 500 https://mirror.one.com/ubuntu xenial/main amd64 Packages 500 https://mirror.one.com/ubuntu xenial/main i386 Packages Steps to reproduce: - Run `update-manager' manually, via `update-manager' from a terminal for example - Press "Settings..." button - Configure the following settings to hide all update-manager's pop-ups respectively: Automatically check for updates: Never When there are security updates: When there are other updates: Display every two weeks Notify me of a new Ubuntu version: Never - Close settings - Exit `update-manager' Expected behaviour: - update-manager won't be checking any updates at all - but even if there are some "other updates" then it must be displayed not more often than "every two weeks" Actual behaviour: - update-manager checks for updates from time to time by itself - update-manager shows notifications *all* *the* *time*: every single day and much more times per day than even twice - update-manager keeps to show notifications even if it has been seen & closed manually (just because there wasn't time for maintenance window currently, for example) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: update-manager 1:16.04.15 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 25 16:32:29 2019 GsettingsChanges: b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'365' b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'window-width' b'303' b'com.ubuntu.update-manager' b'launch-time' b'int64 1551101458' InstallationDate: Installed on 2016-07-19 (951 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"
** Changed in: software-properties (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1834226 Title: update-notifier doesn't respect "automatically check for updates: Never" Status in software-properties package in Ubuntu: Incomplete Bug description: This has been a long-standing problem with various ubuntu installations, and I'm sensing some reticence in doing anything about it. This attitude also seems to be purposeful to try to cajole updates on people who make bad choices due to confusion/fud/paranoia. apt install fails due to: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? A great deal of networking is taking place despite setting automatic upgrades to "never". Cycling this doesn't seem to do anything. This action is hostile to programmers and the setting should be respected. Wisdom on threads is to let it update until it's out of updates, and then it supposedly respects the "never" flag, but the experience I'm having is much more non-deterministic. have been using 19.04 for weeks now and still get the background notifier using data and getting in the way of aptitude package installations. I prefer manual update && upgrade once my code is ready to push. Is there another way around this or are people just living with it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1834226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832882] Re: libcurl-gnutls segfaults spotify client
** Changed in: curl (Ubuntu) Status: Confirmed => Fix Released ** Tags removed: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832882 Title: libcurl-gnutls segfaults spotify client Status in curl package in Ubuntu: Fix Released Status in curl source package in Disco: Confirmed Bug description: The latest release of Spotify client segfaults in libcurl-gnutls as can be read in this thread on spotify support forum: https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479 According to one participant the work-around is to install debian packages libgnutls30_3.6.8-1_amd64.deb and libcurl3-gnutls_7.64.0-3_amd64.deb Ubuntu 19.04 version of the packages: libgnutls30 3.6.5-2ubuntu1.1 libcurl3-gnutls 7.64.0-2ubuntu1.1 As the bug can be resolved by installing debian packages, I assume Ubuntu's version of the packages is at fault and should be upgraded to match debian's level as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
Good to know! Thank you!
Would it also be possible to mark the "upstream" test
(https://salsa.debian.org/systemd-
team/systemd/blob/master/debian/tests/control#L113) "flaky" or turn it
off altogether? We run it on CentOS and Arch anyway so it should be
safe. On Ubuntu CI it's particularly flaky and I don't think it makes
much sense to keep running it there until some stuff like timeouts isn't
adjusted to VMs on the Ubuntu CI infrastructure. I think at this point
it would make sense to make sure that Ubuntu-specific tests are in good
shape.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1829829
Title:
Ubuntu CI has been flaky for a week
Status in systemd package in Ubuntu:
Confirmed
Bug description:
It was originally reported in
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days
ago. To judge from the logs VMs can't be rebooted there:
```
Ubuntu 18.04.2 LTS autopkgtest ttyS0
autopkgtest login:
---
--- nova show 91e76a78-d05c-412a-b383-55a26010ae69
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
+--++
| Property | Value
|
+--++
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | euler
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack
|
| OS-EXT-SRV-ATTR:instance_name| instance-003d216a
|
| OS-EXT-STS:power_state | 1
|
| OS-EXT-STS:task_state| -
|
| OS-EXT-STS:vm_state | active
|
| OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive |
|
| created | 2019-05-16T07:00:33Z
|
| flavor | autopkgtest
(f878e70e-9991-46e0-ba02-8ea159a71656) |
| hostId |
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
|
| id | 91e76a78-d05c-412a-b383-55a26010ae69
|
| image|
adt/ubuntu-bionic-amd64-server-20190516.img
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
| key_name |
testbed-juju-prod-ues-proposed-migration-machine-11
|
| metadata | {}
|
| name |
adt-bionic-amd64-systemd-upstream-20190516-051604
|
| net_ues_proposed_migration network | 10.42.40.13
|
| os-extended-volumes:volumes_attached | []
|
| progress | 0
|
| security_groups | autopkgtest@lcy01-27.secgroup
|
| status | ACTIVE
|
|
[Touch-packages] [Bug 1833758] Re: lvm2: vgcfgbackup in postinst takes several minutes
I tested this on an virtual machine running Eoan and did not notice vgcfgbackup taking as much time as it doesn in an schroot. bdmurray@clean-eoan-amd64:~$ sudo time vgcfgbackup 0.00user 0.00system 0:00.02elapsed 37%CPU (0avgtext+0avgdata 10848maxresident)k 3584inputs+0outputs (0major+1411minor)pagefaults 0swaps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1833758 Title: lvm2: vgcfgbackup in postinst takes several minutes Status in lvm2 package in Ubuntu: New Bug description: The postinst for lvm2 includes a call to vgcfgbackup; in the version included in eoan 2.03.02-2ubuntu4 (and 2.03.02-2ubuntu3 before it), this command takes several minutes to run when invoked in an schroot as happens when a building a package with sbuild that ends up pulling lvm2 as part of its build dependency chain. An example package with lvm2 in its build depends is rsnapshot, but this behavior was seen with a build of glibc. Some notes: - this behavior is NOT seen with the version of lvm2 in disco. - this happens in bionic with a 4.15 kernel and disco with a 5.0 kernel (different hosts, so different sets of block devices) - this happens regardless of whether the host is currently using logical volumes or not Here's the time difference between running the disco version and the eoan version: (disco-amd64)root@HOSTNAME:~# time vgcfgbackup WARNING: Failed to connect to lvmetad. Falling back to device scanning. real0m0.204s user0m0.014s sys 0m0.010s (eoan-amd64)root@HOSTNAME:~# time vgcfgbackup WARNING: Device /dev/sda not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde2 not initialized in udev database even after waiting 1000 microseconds. real4m11.405s user0m0.470s sys 0m0.576s /proc/mounts in the schroot: (eoan-amd64)root@HOSTNAME:~# cat /proc/mounts eoan-amd64 / overlay rw,relatime,lowerdir=/var/lib/schroot/union/underlay/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34,upperdir=/srv/devel/schroot-overlays/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34/upper,workdir=/srv/devel/schroot-overlays/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34/work 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,nosuid,relatime,size=10197712k,nr_inodes=2549428,mode=755 0 0 devpts /dev/pts
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
I've tried it and its not working for me. Do you need some log or something I can try? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833039 Title: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1 Status in apache2 package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Confirmed Bug description: I am using Apache2 with client certificate authentication. Since recently (last week) and without any configuration changes, the following errors occur frequently: AH02042: rejecting client initiated renegotiation Client connections are very slow and sometimes it takes more than a minute until a weg page can be opened in the browser. Before installation of the latest security fixes last week, this error did not occur. Could it be related to https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689? System information: Description:Ubuntu 18.04.2 LTS Release:18.04 apache2: Installiert: 2.4.29-1ubuntu4.6 Installationskandidat: 2.4.29-1ubuntu4.6 Versionstabelle: *** 2.4.29-1ubuntu4.6 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.29-1ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages openssl: Installiert: 1.1.1-1ubuntu2.1~18.04.2 Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2 Versionstabelle: *** 1.1.1-1ubuntu2.1~18.04.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.0g-2ubuntu4.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.1.0g-2ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment
Lubuntu is suffering what seems to be a related failure although I tracked that down to what I thought was a different upstream bug report. In Lubuntu's case the lxqt-policykit-agent suffers a SIGSEGV as a side- affect (I think) of polkit failing to authorise. It was originally discovered when, using the GUI, an additional user was added with 'sudo' membership. This broke the subsequent ability of the new user to make any user account changes via the GUI because they'd get an authentication challenge and then failure. That failure seems to exercise a rarely followed code path that causes the SIGSEGV, and is likely unrelated to the underlying policykit issue. That new 'sudo' member is also prevented from using privileged tools like "gparted". bug #1828663 "policykit failures due to internal user id mismatch" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Triaged Status in policykit-1 package in Ubuntu: Triaged Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828663] Re: policykit failures due to internal user id mismatch
Possibly related to Bug #1821415 "pkexec fails in a non-graphical environment" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1828663 Title: policykit failures due to internal user id mismatch Status in PolicyKit: Unknown Status in lubuntu-meta package in Ubuntu: Invalid Status in lxqt-policykit package in Ubuntu: Invalid Status in policykit-1 package in Ubuntu: Confirmed Status in polkit-qt-1 package in Ubuntu: New Bug description: After adding a second user to the sudo group any authentication in the QT applications menu fails, till I manually remove the second user from the sudo group by issuing deluser chiara sudo in terminal window. Lubuntu 19.04 (fresh install, in italian) 1)open the preferences/LXQt settins/user and groups menu from the application menu 2)add new user, before saving add it to sudo group; save (password asked for user currently logged on, as expected - then new user password asked, user created -all ok) 3)restart system 4) log in as newly created user; open the same interface preferences/LXQt settins/user and groups; try changing the full name field (properties of your own user): logged user password asked (and... why? User two is changing himself) 5)popup showed: "Error executing command as another user: Not authorized" & user unchanged. 6)if you exit session, reenter with the first user, also him is now unable to use interface ti change users via interface 7)using terminal, delete second user from sudo group 8)restart system 9)athenticated interface working again. It happened me both at home on a phisical laptop and on a virtual machine at office, where I could do it all twice. By the way, also plasma-discover tells me I haven't the right to update/install when I have two sudoers (tried at home to remove second sudoer to fix it, and it worked) So it seems that the authentication mechanism of the QT graphical interface fails when there are more then one sudoer on the system - but only for applications started from the application menu. Launching the same application via terminal (sudo plasma-discovery) works. commands issued by the interface (which lead to "unauthorized" error: --change user pkexec --disable-internal-agent lxqt-admin-user-helper usermod -c marco marcop --plasma-discover polkit-agent-helper-1 marcop To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1828663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828663] Re: policykit failures due to internal user id mismatch
Using gparted (which requires root access to the block storage devices) "test" user fails whilst original "lubuntu" user is successful: # In "lubuntu" user's GUI terminal emulator: lubuntu@lubuntu:~$ gparted localuser:root being added to access control list == libparted : 3.2 == localuser:root being removed from access control list # In "test" user's GUI terminal emulator: test@lubuntu:~$ gparted localuser:root being added to access control list Error executing command as another user: Not authorized This incident has been reported. localuser:root being removed from access control list -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1828663 Title: policykit failures due to internal user id mismatch Status in PolicyKit: Unknown Status in lubuntu-meta package in Ubuntu: Invalid Status in lxqt-policykit package in Ubuntu: Invalid Status in policykit-1 package in Ubuntu: Confirmed Status in polkit-qt-1 package in Ubuntu: New Bug description: After adding a second user to the sudo group any authentication in the QT applications menu fails, till I manually remove the second user from the sudo group by issuing deluser chiara sudo in terminal window. Lubuntu 19.04 (fresh install, in italian) 1)open the preferences/LXQt settins/user and groups menu from the application menu 2)add new user, before saving add it to sudo group; save (password asked for user currently logged on, as expected - then new user password asked, user created -all ok) 3)restart system 4) log in as newly created user; open the same interface preferences/LXQt settins/user and groups; try changing the full name field (properties of your own user): logged user password asked (and... why? User two is changing himself) 5)popup showed: "Error executing command as another user: Not authorized" & user unchanged. 6)if you exit session, reenter with the first user, also him is now unable to use interface ti change users via interface 7)using terminal, delete second user from sudo group 8)restart system 9)athenticated interface working again. It happened me both at home on a phisical laptop and on a virtual machine at office, where I could do it all twice. By the way, also plasma-discover tells me I haven't the right to update/install when I have two sudoers (tried at home to remove second sudoer to fix it, and it worked) So it seems that the authentication mechanism of the QT graphical interface fails when there are more then one sudoer on the system - but only for applications started from the application menu. Launching the same application via terminal (sudo plasma-discovery) works. commands issued by the interface (which lead to "unauthorized" error: --change user pkexec --disable-internal-agent lxqt-admin-user-helper usermod -c marco marcop --plasma-discover polkit-agent-helper-1 marcop To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1828663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
> I think it would be better to somehow address
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824864.
> arm64 has been off since December 2018 due to that issue.
yep, the ubuntu bionic kernel will be patched to increase the arm64 log buffer
size:
https://lists.ubuntu.com/archives/kernel-team/2019-June/101613.html
however the kernel release cycle is long, so that won't happen until end of
July (earliest):
https://lists.ubuntu.com/archives/kernel-sru-announce/2019-June/000151.html
but, the test case in debian-experimental has a mr that should stop CI failing
once merged:
https://salsa.debian.org/systemd-team/systemd/merge_requests/34
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1829829
Title:
Ubuntu CI has been flaky for a week
Status in systemd package in Ubuntu:
Confirmed
Bug description:
It was originally reported in
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days
ago. To judge from the logs VMs can't be rebooted there:
```
Ubuntu 18.04.2 LTS autopkgtest ttyS0
autopkgtest login:
---
--- nova show 91e76a78-d05c-412a-b383-55a26010ae69
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
+--++
| Property | Value
|
+--++
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | euler
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack
|
| OS-EXT-SRV-ATTR:instance_name| instance-003d216a
|
| OS-EXT-STS:power_state | 1
|
| OS-EXT-STS:task_state| -
|
| OS-EXT-STS:vm_state | active
|
| OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive |
|
| created | 2019-05-16T07:00:33Z
|
| flavor | autopkgtest
(f878e70e-9991-46e0-ba02-8ea159a71656) |
| hostId |
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
|
| id | 91e76a78-d05c-412a-b383-55a26010ae69
|
| image|
adt/ubuntu-bionic-amd64-server-20190516.img
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
| key_name |
testbed-juju-prod-ues-proposed-migration-machine-11
|
| metadata | {}
|
| name |
adt-bionic-amd64-systemd-upstream-20190516-051604
|
| net_ues_proposed_migration network | 10.42.40.13
|
| os-extended-volumes:volumes_attached | []
|
| progress | 0
|
| security_groups | autopkgtest@lcy01-27.secgroup
|
| status
[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"
Also, final question, did you turn off "Download and install automatically" for security updates? If you only turn of "Automatically check for updates", then we won't automatically check for updates, but if you ran apt update, the next day-ish all updates will be downloaded automatically (it should be only security updates, but it also downloads non-security ones). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1834226 Title: update-notifier doesn't respect "automatically check for updates: Never" Status in software-properties package in Ubuntu: New Bug description: This has been a long-standing problem with various ubuntu installations, and I'm sensing some reticence in doing anything about it. This attitude also seems to be purposeful to try to cajole updates on people who make bad choices due to confusion/fud/paranoia. apt install fails due to: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? A great deal of networking is taking place despite setting automatic upgrades to "never". Cycling this doesn't seem to do anything. This action is hostile to programmers and the setting should be respected. Wisdom on threads is to let it update until it's out of updates, and then it supposedly respects the "never" flag, but the experience I'm having is much more non-deterministic. have been using 19.04 for weeks now and still get the background notifier using data and getting in the way of aptitude package installations. I prefer manual update && upgrade once my code is ready to push. Is there another way around this or are people just living with it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1834226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834226] Re: update-notifier doesn't respect "automatically check for updates: Never"
Also, is this a desktop machine / does it have PackageKit installed, and if so, which frontends for packagekit? ** Package changed: update-notifier (Ubuntu) => software-properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1834226 Title: update-notifier doesn't respect "automatically check for updates: Never" Status in software-properties package in Ubuntu: New Bug description: This has been a long-standing problem with various ubuntu installations, and I'm sensing some reticence in doing anything about it. This attitude also seems to be purposeful to try to cajole updates on people who make bad choices due to confusion/fud/paranoia. apt install fails due to: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? A great deal of networking is taking place despite setting automatic upgrades to "never". Cycling this doesn't seem to do anything. This action is hostile to programmers and the setting should be respected. Wisdom on threads is to let it update until it's out of updates, and then it supposedly respects the "never" flag, but the experience I'm having is much more non-deterministic. have been using 19.04 for weeks now and still get the background notifier using data and getting in the way of aptitude package installations. I prefer manual update && upgrade once my code is ready to push. Is there another way around this or are people just living with it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1834226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
Hello Dan, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.22 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Committed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
Hello Dimitri, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.22 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Xenial) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: Fix Committed Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Released Status in linux source package in Disco: New Status in systemd source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Status in systemd package in Debian: Confirmed Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828663] Re: lubuntu 19.04 QT interfaces not properly working where more then one sudoer configured
I've found that there appears to be a fundamental bug in policykit and have added the upstream bug report covering it, which has been around for several years but the developers don't seem able to come up with a fix for. Tests done using the Lubuntu 19.10 Live ISO (June 24th 2019 build) where an additional user "test" is created with the same supplementary group memberships as the "lubuntu" user. Both have passwords set so that these tests can be done over SSH as well as at the console, or in the GUI. The fact that "pkexec" itself is broken proves that lxqt nor the qt- policykit code is at fault here. test@lubuntu:~$ groups test adm cdrom sudo dip plugdev lpadmin $ sudo ls -l /root/ [sudo] password for test: total 0 -rw-r--r-- 1 root root 0 Jun 26 23:35 file test@lubuntu:~$ pkexec ls -l /root/ AUTHENTICATING FOR org.freedesktop.policykit.exec === Authentication is needed to run `/usr/bin/ls' as the super user Multiple identities can be used for authentication: 1. Lubuntu2,,, (lubuntu) 2. Test3,,, (test) Choose identity to authenticate as (1-2): 2 Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie lubuntu@lubuntu:~$ groups lubuntu adm cdrom sudo dip plugdev lpadmin sambashare lubuntu@lubuntu:~$ sudo ls -l /root/ total 0 -rw-r--r-- 1 root root 0 Jun 26 23:35 grep lubuntu@lubuntu:~$ pkexec ls -l /root/ Error executing command as another user: Not authorized This incident has been reported. ** Summary changed: - lubuntu 19.04 QT interfaces not properly working where more then one sudoer configured + policykit failures due to internal user id mismatch ** Changed in: lubuntu-meta (Ubuntu) Status: In Progress => Invalid ** Changed in: lxqt-policykit (Ubuntu) Status: Confirmed => Invalid ** Changed in: policykit-1 (Ubuntu) Status: New => Confirmed ** Changed in: lubuntu-meta (Ubuntu) Assignee: TJ (tj) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1828663 Title: policykit failures due to internal user id mismatch Status in PolicyKit: Unknown Status in lubuntu-meta package in Ubuntu: Invalid Status in lxqt-policykit package in Ubuntu: Invalid Status in policykit-1 package in Ubuntu: Confirmed Status in polkit-qt-1 package in Ubuntu: New Bug description: After adding a second user to the sudo group any authentication in the QT applications menu fails, till I manually remove the second user from the sudo group by issuing deluser chiara sudo in terminal window. Lubuntu 19.04 (fresh install, in italian) 1)open the preferences/LXQt settins/user and groups menu from the application menu 2)add new user, before saving add it to sudo group; save (password asked for user currently logged on, as expected - then new user password asked, user created -all ok) 3)restart system 4) log in as newly created user; open the same interface preferences/LXQt settins/user and groups; try changing the full name field (properties of your own user): logged user password asked (and... why? User two is changing himself) 5)popup showed: "Error executing command as another user: Not authorized" & user unchanged. 6)if you exit session, reenter with the first user, also him is now unable to use interface ti change users via interface 7)using terminal, delete second user from sudo group 8)restart system 9)athenticated interface working again. It happened me both at home on a phisical laptop and on a virtual machine at office, where I could do it all twice. By the way, also plasma-discover tells me I haven't the right to update/install when I have two sudoers (tried at home to remove second sudoer to fix it, and it worked) So it seems that the authentication mechanism of the QT graphical interface fails when there are more then one sudoer on the system - but only for applications started from the application menu. Launching the same application via terminal (sudo plasma-discovery) works. commands issued by the interface (which lead to "unauthorized" error: --change user pkexec --disable-internal-agent lxqt-admin-user-helper usermod -c marco marcop --plasma-discover polkit-agent-helper-1 marcop To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1828663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
Thanks for the reports and comments. I setup a PPA with patch pointed out by xnox in comment #7 on bionic's apache2 source package: https://launchpad.net/~legovini/+archive/ubuntu/apache2-lp1833039 It would be great to have some feedback on the effectiveness of the patch. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833039 Title: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1 Status in apache2 package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Confirmed Bug description: I am using Apache2 with client certificate authentication. Since recently (last week) and without any configuration changes, the following errors occur frequently: AH02042: rejecting client initiated renegotiation Client connections are very slow and sometimes it takes more than a minute until a weg page can be opened in the browser. Before installation of the latest security fixes last week, this error did not occur. Could it be related to https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689? System information: Description:Ubuntu 18.04.2 LTS Release:18.04 apache2: Installiert: 2.4.29-1ubuntu4.6 Installationskandidat: 2.4.29-1ubuntu4.6 Versionstabelle: *** 2.4.29-1ubuntu4.6 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.29-1ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages openssl: Installiert: 1.1.1-1ubuntu2.1~18.04.2 Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2 Versionstabelle: *** 1.1.1-1ubuntu2.1~18.04.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.0g-2ubuntu4.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.1.0g-2ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828892] Re: systemctl - alias service reports inactive while aliased is active
Hello Ioanna, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.22 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1828892 Title: systemctl - alias service reports inactive while aliased is active Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] 'systemctl is-active' command reports an alias service as inactive even though the aliased service is active. Currently the 'systemctl is-active' command does not load units to minimise its effect on the system (i.e. that a monitoring command does not itself alter the state of the system). However, this behaviour leads to inconsistencies when services are aliased. [Test case] - Test case 1 - libvirtd alias service : libvirtd aliased service : libvirt-bin /etc/systemd/system$ ls -la libvirtd.service lrwxrwxrwx 1 root root 39 May 13 20:49 libvirtd.service -> /lib/systemd/system/libvirt-bin.service $ systemctl is-active libvirtd inactive $ systemctl is-active libvirt-bin active - Test case 2 - sshd alias service : sshd aliased service : ssh /ect/systemd/system$ ls -la sshd.service lrwxrwxrwx 1 root root 31 Mar 19 19:44 sshd.service -> /lib/systemd/system/ssh.service $ systemctl is-active sshd inactive $ systemctl is-active ssh active [Regression Potential] This fix may result into systemctl reporting inconsistent information concerning the status of a service. [Other] Upstream issue : https://github.com/systemd/systemd/issues/7875 Upstream fix : https://github.com/systemd/systemd/pull/7997 Xenial is affected, fix exists on Bionic onward. $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.21 Candidate: 229-4ubuntu21.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830477] Re: systemd-fsckd, cmdline-upstart-boot tests fail on xenial s390x
Hello Dan, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.22 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1830477 Title: systemd-fsckd, cmdline-upstart-boot tests fail on xenial s390x Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [impact] these tests require, and modify, grub. That fails on s390x on xenial because it does not use grub. [test case] run the autopkgtests for xenial on s390x [regression potential] low; only skipping test cases on s390x. [other info] in bionic and later, systemd-fsckd has support for zipl (s390x bootloader) and cmdline-upstart-boot is removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834226] [NEW] update-notifier doesn't respect "automatically check for updates: Never"
You have been subscribed to a public bug: This has been a long-standing problem with various ubuntu installations, and I'm sensing some reticence in doing anything about it. This attitude also seems to be purposeful to try to cajole updates on people who make bad choices due to confusion/fud/paranoia. apt install fails due to: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? A great deal of networking is taking place despite setting automatic upgrades to "never". Cycling this doesn't seem to do anything. This action is hostile to programmers and the setting should be respected. Wisdom on threads is to let it update until it's out of updates, and then it supposedly respects the "never" flag, but the experience I'm having is much more non-deterministic. have been using 19.04 for weeks now and still get the background notifier using data and getting in the way of aptitude package installations. I prefer manual update && upgrade once my code is ready to push. Is there another way around this or are people just living with it? ** Affects: software-properties (Ubuntu) Importance: High Status: New ** Tags: bot-comment rls-ee-incoming -- update-notifier doesn't respect "automatically check for updates: Never" https://bugs.launchpad.net/bugs/1834226 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828663] Re: lubuntu 19.04 QT interfaces not properly working where more then one sudoer configured
** Also affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/polkit/polkit/issues #39 https://gitlab.freedesktop.org/polkit/polkit/issues/39 ** Also affects: policykit-1 via https://gitlab.freedesktop.org/polkit/polkit/issues/39 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1828663 Title: policykit failures due to internal user id mismatch Status in PolicyKit: Unknown Status in lubuntu-meta package in Ubuntu: Invalid Status in lxqt-policykit package in Ubuntu: Invalid Status in policykit-1 package in Ubuntu: Confirmed Status in polkit-qt-1 package in Ubuntu: New Bug description: After adding a second user to the sudo group any authentication in the QT applications menu fails, till I manually remove the second user from the sudo group by issuing deluser chiara sudo in terminal window. Lubuntu 19.04 (fresh install, in italian) 1)open the preferences/LXQt settins/user and groups menu from the application menu 2)add new user, before saving add it to sudo group; save (password asked for user currently logged on, as expected - then new user password asked, user created -all ok) 3)restart system 4) log in as newly created user; open the same interface preferences/LXQt settins/user and groups; try changing the full name field (properties of your own user): logged user password asked (and... why? User two is changing himself) 5)popup showed: "Error executing command as another user: Not authorized" & user unchanged. 6)if you exit session, reenter with the first user, also him is now unable to use interface ti change users via interface 7)using terminal, delete second user from sudo group 8)restart system 9)athenticated interface working again. It happened me both at home on a phisical laptop and on a virtual machine at office, where I could do it all twice. By the way, also plasma-discover tells me I haven't the right to update/install when I have two sudoers (tried at home to remove second sudoer to fix it, and it worked) So it seems that the authentication mechanism of the QT graphical interface fails when there are more then one sudoer on the system - but only for applications started from the application menu. Launching the same application via terminal (sudo plasma-discovery) works. commands issued by the interface (which lead to "unauthorized" error: --change user pkexec --disable-internal-agent lxqt-admin-user-helper usermod -c marco marcop --plasma-discover polkit-agent-helper-1 marcop To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1828663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
I'm not working on this. I filled it as a place-holder for anyone who is willing to work on the update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: New Status in gst-omx package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gst-plugins-good1.0 package in Ubuntu: New Status in gst-plugins-ugly1.0 package in Ubuntu: New Status in gst-python1.0 package in Ubuntu: New Status in gst-rtsp-server1.0 package in Ubuntu: New Status in gstreamer-editing-services1.0 package in Ubuntu: New Status in gstreamer-vaapi package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay: keep buffer pool around when flushing/seeking - rtpssrcdemux: Forward serialized events to all pads - qmlglsink: Handle OPENGL header guard changes - qtdemux: fix track language code parsing; ignore corrupted CTTS box - qtmux: Correctly set tkhd width/height to the display size - splitmuxsink: various timecode meta handling fixes - splitmuxsink: make work with audio-only encoders as muxers, e.g. wavenc - v4l2sink: fix pool-less allocation query handling - v4l2dec/enc: fix use after free when handling events - vpx: Fix build against libvpx 1.8 - webmmux: allow resolutions above 4096 gst-plugins-ugly - sid: Fix cross-compilation by using AC_TRY_LINK instead of AC_TRY_RUN - x264: Only enable dynamic loading code for x264 before v253 gst-plugins-bad - assrender: fix disappearing subtitles when seeking back in time - decklinkvideosink: fix segfault when audiosink is closed before videosink -
[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly
Reference: http://changelogs.ubuntu.com/changelogs/pool/main/b/bzip2/bzip2_1.0.6-8.1ubuntu0.1/changelog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1834494 Title: latest bzip2 reports crc errors incorrectly Status in bzip2 package in Ubuntu: New Bug description: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly
Manually reverting to a previous version of /lib/x86_64-linux- gnu/libbz2.so.1.0.4 corrects the issue for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1834494 Title: latest bzip2 reports crc errors incorrectly Status in bzip2 package in Ubuntu: New Bug description: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
Amr Ibrahim, are you working on this -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: New Status in gst-omx package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gst-plugins-good1.0 package in Ubuntu: New Status in gst-plugins-ugly1.0 package in Ubuntu: New Status in gst-python1.0 package in Ubuntu: New Status in gst-rtsp-server1.0 package in Ubuntu: New Status in gstreamer-editing-services1.0 package in Ubuntu: New Status in gstreamer-vaapi package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay: keep buffer pool around when flushing/seeking - rtpssrcdemux: Forward serialized events to all pads - qmlglsink: Handle OPENGL header guard changes - qtdemux: fix track language code parsing; ignore corrupted CTTS box - qtmux: Correctly set tkhd width/height to the display size - splitmuxsink: various timecode meta handling fixes - splitmuxsink: make work with audio-only encoders as muxers, e.g. wavenc - v4l2sink: fix pool-less allocation query handling - v4l2dec/enc: fix use after free when handling events - vpx: Fix build against libvpx 1.8 - webmmux: allow resolutions above 4096 gst-plugins-ugly - sid: Fix cross-compilation by using AC_TRY_LINK instead of AC_TRY_RUN - x264: Only enable dynamic loading code for x264 before v253 gst-plugins-bad - assrender: fix disappearing subtitles when seeking back in time - decklinkvideosink: fix segfault when audiosink is closed before videosink - decklinkvideosrc: respect pixel format property even if mode is
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
> looks like this has been fixed already upstream
Yes. I merged the PR (created by @yuwata) fixing that this morning.
> looks like someone stopped that; it's only running tests for 12888,
12897, and 12899 currently.
In
https://github.com/systemd/systemd/issues/12891#issuecomment-506093934 I
asked Iain Lane to stop that, which I think explains why it's not there
any more.
> I'll take a look at those failures.
Those failures most likely have something to do with that PR and
probably should be fixed upstream. I think it would be better to somehow
address https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824864.
arm64 has been off since December 2018 due to that issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1829829
Title:
Ubuntu CI has been flaky for a week
Status in systemd package in Ubuntu:
Confirmed
Bug description:
It was originally reported in
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days
ago. To judge from the logs VMs can't be rebooted there:
```
Ubuntu 18.04.2 LTS autopkgtest ttyS0
autopkgtest login:
---
--- nova show 91e76a78-d05c-412a-b383-55a26010ae69
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
+--++
| Property | Value
|
+--++
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | euler
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack
|
| OS-EXT-SRV-ATTR:instance_name| instance-003d216a
|
| OS-EXT-STS:power_state | 1
|
| OS-EXT-STS:task_state| -
|
| OS-EXT-STS:vm_state | active
|
| OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive |
|
| created | 2019-05-16T07:00:33Z
|
| flavor | autopkgtest
(f878e70e-9991-46e0-ba02-8ea159a71656) |
| hostId |
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
|
| id | 91e76a78-d05c-412a-b383-55a26010ae69
|
| image|
adt/ubuntu-bionic-amd64-server-20190516.img
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
| key_name |
testbed-juju-prod-ues-proposed-migration-machine-11
|
| metadata | {}
|
| name |
adt-bionic-amd64-systemd-upstream-20190516-051604
|
| net_ues_proposed_migration network | 10.42.40.13
|
| os-extended-volumes:volumes_attached | []
|
| progress | 0
|
| security_groups | autopkgtest@lcy01-27.secgroup
|
[Touch-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: New Status in gst-omx package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gst-plugins-good1.0 package in Ubuntu: New Status in gst-plugins-ugly1.0 package in Ubuntu: New Status in gst-python1.0 package in Ubuntu: New Status in gst-rtsp-server1.0 package in Ubuntu: New Status in gstreamer-editing-services1.0 package in Ubuntu: New Status in gstreamer-vaapi package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay: keep buffer pool around when flushing/seeking - rtpssrcdemux: Forward serialized events to all pads - qmlglsink: Handle OPENGL header guard changes - qtdemux: fix track language code parsing; ignore corrupted CTTS box - qtmux: Correctly set tkhd width/height to the display size - splitmuxsink: various timecode meta handling fixes - splitmuxsink: make work with audio-only encoders as muxers, e.g. wavenc - v4l2sink: fix pool-less allocation query handling - v4l2dec/enc: fix use after free when handling events - vpx: Fix build against libvpx 1.8 - webmmux: allow resolutions above 4096 gst-plugins-ugly - sid: Fix cross-compilation by using AC_TRY_LINK instead of AC_TRY_RUN - x264: Only enable dynamic loading code for x264 before v253 gst-plugins-bad - assrender: fix disappearing subtitles when seeking back in time - decklinkvideosink: fix segfault when audiosink is closed before videosink - decklinkvideosrc: respect pixel format property even if mode is set to auto - d3dvideosink:
[Touch-packages] [Bug 1834494] [NEW] latest bzip2 reports crc errors incorrectly
Public bug reported: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. ** Affects: bzip2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bzip2 in Ubuntu. https://bugs.launchpad.net/bugs/1834494 Title: latest bzip2 reports crc errors incorrectly Status in bzip2 package in Ubuntu: New Bug description: I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine and am now having problems with some .tbz2 archives. In particular, I can no longer extract this one: https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver- package-31-1-0 Downloading this and running: bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2 ...yields a CRC error. The previous version of bunzip2 does not report any errors with this archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/1834494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
> apparently something else was broken on bionic-i386 while it was off:
> https://github.com/systemd/systemd/issues/12891.
looks like this has been fixed already upstream
> In https://github.com/systemd/systemd/pull/12861#issuecomment-506025351 both
> bionic-amd64 and bionic-s390x failed due to something weird I don't quite
> understand.
> It would be great if someone who is interested in keeping it afloat could
> chime in
> there to help to debug that.
I'll take a look at those failures.
> it seems Ubuntu CI keeps running the tests for PR 12618
looks like someone stopped that; it's only running tests for 12888,
12897, and 12899 currently.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1829829
Title:
Ubuntu CI has been flaky for a week
Status in systemd package in Ubuntu:
Confirmed
Bug description:
It was originally reported in
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days
ago. To judge from the logs VMs can't be rebooted there:
```
Ubuntu 18.04.2 LTS autopkgtest ttyS0
autopkgtest login:
---
--- nova show 91e76a78-d05c-412a-b383-55a26010ae69
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
+--++
| Property | Value
|
+--++
| OS-DCF:diskConfig| MANUAL
|
| OS-EXT-AZ:availability_zone | nova
|
| OS-EXT-SRV-ATTR:host | euler
|
| OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack
|
| OS-EXT-SRV-ATTR:instance_name| instance-003d216a
|
| OS-EXT-STS:power_state | 1
|
| OS-EXT-STS:task_state| -
|
| OS-EXT-STS:vm_state | active
|
| OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00
|
| OS-SRV-USG:terminated_at | -
|
| accessIPv4 |
|
| accessIPv6 |
|
| config_drive |
|
| created | 2019-05-16T07:00:33Z
|
| flavor | autopkgtest
(f878e70e-9991-46e0-ba02-8ea159a71656) |
| hostId |
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
|
| id | 91e76a78-d05c-412a-b383-55a26010ae69
|
| image|
adt/ubuntu-bionic-amd64-server-20190516.img
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
| key_name |
testbed-juju-prod-ues-proposed-migration-machine-11
|
| metadata | {}
|
| name |
adt-bionic-amd64-systemd-upstream-20190516-051604
|
| net_ues_proposed_migration network | 10.42.40.13
|
| os-extended-volumes:volumes_attached | []
|
| progress | 0
|
| security_groups | autopkgtest@lcy01-27.secgroup
|
| status
[Touch-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
Yep, 1.14.4 has been released now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: New Status in gst-omx package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gst-plugins-good1.0 package in Ubuntu: New Status in gst-plugins-ugly1.0 package in Ubuntu: New Status in gst-python1.0 package in Ubuntu: New Status in gst-rtsp-server1.0 package in Ubuntu: New Status in gstreamer-editing-services1.0 package in Ubuntu: New Status in gstreamer-vaapi package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay: keep buffer pool around when flushing/seeking - rtpssrcdemux: Forward serialized events to all pads - qmlglsink: Handle OPENGL header guard changes - qtdemux: fix track language code parsing; ignore corrupted CTTS box - qtmux: Correctly set tkhd width/height to the display size - splitmuxsink: various timecode meta handling fixes - splitmuxsink: make work with audio-only encoders as muxers, e.g. wavenc - v4l2sink: fix pool-less allocation query handling - v4l2dec/enc: fix use after free when handling events - vpx: Fix build against libvpx 1.8 - webmmux: allow resolutions above 4096 gst-plugins-ugly - sid: Fix cross-compilation by using AC_TRY_LINK instead of AC_TRY_RUN - x264: Only enable dynamic loading code for x264 before v253 gst-plugins-bad - assrender: fix disappearing subtitles when seeking back in time - decklinkvideosink: fix segfault when audiosink is closed before videosink - decklinkvideosrc: respect pixel format property even if mode is
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Description changed: - When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. + [Impact] + + During system upgrades, triggers for gconf2 might activate too early, + while some of its dependencies aren't configured yet. This happens + several times in a loop and stops the upgrade in the end. + + The attached debdiffs fix this issue by changing interest to interest- + noawait in debian/gconf2.triggers file. The triggers will now activate + near the end of upgrade. + + In addition, the debdiff for Bionic also contains a fix for FTBFS (bug + 1834211). + + [Test Case] + + Triggers for gconf2 are usually activated on changes in + /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with + GNOME) is most suitable for reproducing the issue. To reproduce it, + install that edition, apply all updates, then try upgrading to the next + release. + + [Regression Potential] + + None, interest-noawait trigger is known to work well in other packages + (comment 31). + + [Other Info] + + Even if Cosmic goes EOL next month, the fix for it might be worth it for + release upgrades. + + [Original Description] + + When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: - dpkg 1.18.4ubuntu1 - apt 1.2.3 + dpkg 1.18.4ubuntu1 + apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) ** Summary changed: - package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed + [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** Tags added: bionic cosmic disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1834211] Re: [SRU] gconf FTBFS in Bionic
These fixes are also added to combined debdiff in bug 1551623. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1834211 Title: [SRU] gconf FTBFS in Bionic Status in gconf package in Ubuntu: New Bug description: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk- doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Fix for 18.04 + build fix (bug 1834211) this can go into bionic-proposed in one diff ** Attachment added: "Debdiff with the fix for Bionic + build fix (bug 1834211)" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273780/+files/gconf-debdiff-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834264] Re: PCI/internal sound card not detected
Now for some reason overnight, my sound settings no longer say "Dummy Output" It says "Headphones". However, the headphones don't work. If I open pavucontrol, it says Speakers (Unavailable) for the speakers option. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834264] Re: PCI/internal sound card not detected
I should also mention this has happened before, but I just reinstalled Ubuntu. I'm backing everything up to do that right now, but it was something I wanted to avoid due to the hassle. However, I'm seeing it is becoming a bigger hassle to try to fix it without a fresh install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
For 18.04, a build fix is required first (bug 1834211). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
The attachment "Debdiff with the fix for Disco" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Fix for 18.10 ** Attachment added: "Debdiff with the fix for Cosmic" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273779/+files/gconf-debdiff-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Fix for 19.04 ** Attachment added: "Debdiff with the fix for Disco" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273778/+files/gconf-debdiff-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824916] Re: Wallpaper corruption after waking from sleep
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Just change your driver from proprietary to open source noveau driver. I also had the same problem but it is solved. It is a problem of nvidia driver.Enjoy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1824916 Title: Wallpaper corruption after waking from sleep Status in xorg package in Ubuntu: Confirmed Bug description: I upgraded to Dingo today, and I'm having a new issue with waking from sleep on my Dell XPS 9560. When I wake my laptop, the wallpaper becomes corrupted (screenshot attached), and it doesn't go away until I restart. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 23:06:37 2019 DistUpgraded: 2019-04-15 19:46:05,884 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2018-10-28 (170 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic root=UUID=9f074e0b-7e2f-475a-9cae-48d43abd3345 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-15 (0 days ago) dmi.bios.date: 10/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/1824916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
This is similar to what happened in the past with: - dbus (https://bugs.debian.org/771989) - cracklib-runtime (https://bugs.debian.org/854554) - shared-mime-info (https://bugs.debian.org/864953) It can be fixed the same way as those. I'll post the debdiffs with the fixes later. ** Bug watch added: Debian Bug tracker #771989 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771989 ** Bug watch added: Debian Bug tracker #854554 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854554 ** Bug watch added: Debian Bug tracker #864953 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864953 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777010] Re: ip token set, results in: Invalid argument
This bug is over a year old now, so I checked if there are news in upcoming Ubuntu 19.10 (Eoan Ermine): ~# ip token list token :: dev eth0 ~# ip token set ::12 dev eth0 RTNETLINK answers: Invalid argument iproute2 Version: 4.18.0-1ubuntu3 Sadly, there are none. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1777010 Title: ip token set, results in: Invalid argument Status in iproute2 package in Ubuntu: Confirmed Bug description: Hi, I can't set any ipv6 token with ip command. It seems that it has a bug. Also it is not possible to set it with netplan (see bug #1737976) ~# ip token list token :: dev enp1s0 token :: dev enp2s0 token :: dev ovpn0 token :: dev br0 ~# ip token set ::2a:2a:2a:2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::beef dev br0 RTNETLINK answers: Invalid argument It seems, that this Bug is really old?! https://bbs.archlinux.org/viewtopic.php?id=202757 This is really fatal, because I cant set a static ip. My prefix get mixed from my provider every x days. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 15 01:26:04 2018 InstallationDate: Installed on 2018-06-12 (2 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1777010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
This bug was fixed in the package gst-plugins-base1.0 - 1.14.4-1ubuntu1.1~ubuntu18.04.1 --- gst-plugins-base1.0 (1.14.4-1ubuntu1.1~ubuntu18.04.1) bionic; urgency=medium * No-change backport to bionic (LP: #1829366) gst-plugins-base1.0 (1.14.4-1ubuntu1.1) cosmic-security; urgency=medium * SECURITY UPDATE: heap overflow in RTSP parser - debian/patches/CVE-2019-9928.patch: limit length in gst-libs/gst/rtsp/gstrtspconnection.c. - CVE-2019-9928 gst-plugins-base1.0 (1.14.4-1ubuntu1) cosmic; urgency=medium * Merge from Debian unstable. Remaining changes: + debian/rules: Build for GLES only on arm. We build OpenGL support, which conflicts with Qt's OpenGL support - used in gst-good - if built for a different implementation. This fixes an FTBFS of gst-plugins-good1.0 due to conflicting typedefs being dragged in by gst and Qt. This might be a bug in mesa - if the headers are supposed to be includable simultaneously. See FDO #105328 for that. gst-plugins-base1.0 (1.14.4-1) unstable; urgency=medium * New upstream bugfix release gst-plugins-base1.0 (1.14.3-2) unstable; urgency=medium [ Hugh McMaster ] * debian/control.in: - Mark gir1.2-gst-plugins-base-1.0 Multi-Arch: same. [ Sebastian Dröge ] * Upload to unstable. gst-plugins-base1.0 (1.14.3-1) unstable; urgency=medium [ Hugh McMaster ] * gir1.2-gst-plugins-base-1.0: Install the typelibs into a multi-arch library directory (Closes: #907808). * debian/control.in: - Mark libgstreamer-plugins-base1.0-dev Multi-Arch: same (Closes: #862119). [ Sebastian Dröge ] * New upstream bugfix release. gst-plugins-base1.0 (1.14.2-1ubuntu1) cosmic; urgency=low * Merge from Debian unstable. Remaining changes: + debian/rules: Build for GLES only on arm. We build OpenGL support, which conflicts with Qt's OpenGL support - used in gst-good - if built for a different implementation. This fixes an FTBFS of gst-plugins-good1.0 due to conflicting typedefs being dragged in by gst and Qt. This might be a bug in mesa - if the headers are supposed to be includable simultaneously. See FDO #105328 for that. gst-plugins-base1.0 (1.14.2-1) unstable; urgency=medium * New upstream bugfix release gst-plugins-base1.0 (1.14.1-1ubuntu1) cosmic; urgency=medium * Merge with Debian (LP: #1772898). Remaining change: + debian/rules: Build for GLES only on arm. We build OpenGL support, which conflicts with Qt's OpenGL support - used in gst-good - if built for a different implementation. This fixes an FTBFS of gst-plugins-good1.0 due to conflicting typedefs being dragged in by gst and Qt. This might be a bug in mesa - if the headers are supposed to be includable simultaneously. See FDO #105328 for that. -- Iain Lane Thu, 16 May 2019 13:18:37 +0100 ** Changed in: gst-plugins-bad1.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Released Status in gst-plugins-bad1.0 source package in Bionic: Fix Released Status in gst-plugins-base1.0 source package in Bionic: Fix Released Status in gst-plugins-good1.0 source package in Bionic: Fix Released Status in gst-plugins-ugly1.0 source package in Bionic: Fix Released Status in gst-python1.0 source package in Bionic: Fix Released Status in gst-rtsp-server1.0 source package in Bionic: Fix Released Status in gstreamer-editing-services1.0 source package in Bionic: Fix Released Status in gstreamer-vaapi source package in Bionic: Fix Released Status in gstreamer1.0 source package in Bionic: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
This bug was fixed in the package gstreamer1.0 - 1.14.4-1~ubuntu18.04.1
---
gstreamer1.0 (1.14.4-1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1829366)
gstreamer1.0 (1.14.4-1) unstable; urgency=medium
* New upstream bugfix release
gstreamer1.0 (1.14.3-1) unstable; urgency=medium
[ Hugh McMaster ]
* gir1.2-gstreamer-1.0: Install the typelibs into a multi-arch library
directory (Closes: #904266).
* debian/control.in:
- Mark gir1.2-gstreamer-1.0 Multi-Arch: same.
- Remove a duplicate ${gir:Depends} variable from gir1.2-gstreamer-1.0.
- Mark libgstreamer1.0-dev Multi-Arch: same (Closes: #823307).
* debian/dh_gstscancodecs:
- Call gst-codec-info-1.0 from the package's libexecdir path.
* libgstreamer1.0-dev:
- Install the gst-codec-info-1.0 utility into the package's multi-arch
program executables directory (libexecdir).
[ Sebastian Dröge ]
* New upstream bugfix release.
gstreamer1.0 (1.14.2-2) unstable; urgency=medium
* debian/patches/0002-gstconfig.h.in-initial-RISC-V-support.patch:
+ Add support for RISC-V (Closes: #895711).
* debian/control.in:
+ Build-depend on libgmp-dev | libgmp3-dev (Closes: #862257).
gstreamer1.0 (1.14.2-1) unstable; urgency=medium
* New upstream bugfix release
gstreamer1.0 (1.14.1-1) unstable; urgency=medium
* New upstream bugfix release.
-- Iain Lane Thu, 16 May 2019 13:13:52 +0100
** Changed in: gstreamer1.0 (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1829366
Title:
[SRU] Bugfix release 1.14.4
Status in gst-libav1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
Fix Released
Status in gst-python1.0 package in Ubuntu:
Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
Fix Released
Status in gstreamer-vaapi package in Ubuntu:
Fix Released
Status in gstreamer1.0 package in Ubuntu:
Fix Released
Status in gst-libav1.0 source package in Bionic:
Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
Fix Released
Status in gst-python1.0 source package in Bionic:
Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
Fix Released
Status in gstreamer-vaapi source package in Bionic:
Fix Released
Status in gstreamer1.0 source package in Bionic:
Fix Released
Bug description:
[ Description ]
We should keep up with GStreamer's bugfix releases in the 1.14 series
that 18.04 shipped with.
[ QA and testing ]
Play a range of videos in Totem. Play a range of audio tracks in
Rhythmbox. Try to stream audio and/or video. Try to install a missing
codec.
In all cases, make sure that everything which worked before still
works.
[ Regression potential ]
If one of the fixes is bad then it might break video or audio
playback, or could crash any application that tries to use gstreamer.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
This bug was fixed in the package gst-python1.0 - 1.14.4-1~ubuntu18.04.1 --- gst-python1.0 (1.14.4-1~ubuntu18.04.1) bionic; urgency=medium * No-change backport to bionic (LP: #1829366) gst-python1.0 (1.14.4-1) unstable; urgency=medium * New upstream bugfix release gst-python1.0 (1.14.3-1) unstable; urgency=medium * New upstream bugfix release. gst-python1.0 (1.14.2-1) unstable; urgency=medium * New upstream bugfix release gst-python1.0 (1.14.1-1) unstable; urgency=medium * New upstream bugfix release -- Iain Lane Thu, 16 May 2019 13:42:44 +0100 ** Changed in: gst-plugins-ugly1.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Released Status in gst-plugins-bad1.0 source package in Bionic: Fix Released Status in gst-plugins-base1.0 source package in Bionic: Fix Released Status in gst-plugins-good1.0 source package in Bionic: Fix Released Status in gst-plugins-ugly1.0 source package in Bionic: Fix Released Status in gst-python1.0 source package in Bionic: Fix Released Status in gst-rtsp-server1.0 source package in Bionic: Fix Released Status in gstreamer-editing-services1.0 source package in Bionic: Fix Released Status in gstreamer-vaapi source package in Bionic: Fix Released Status in gstreamer1.0 source package in Bionic: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
This bug was fixed in the package gstreamer-vaapi - 1.14.4-1~ubuntu18.04.1 --- gstreamer-vaapi (1.14.4-1~ubuntu18.04.1) bionic; urgency=medium * No-change backport to bionic (LP: #1829366) gstreamer-vaapi (1.14.4-1) unstable; urgency=medium * New upstream bugfix release gstreamer-vaapi (1.14.3-1) unstable; urgency=medium * New upstream bugfix release. gstreamer-vaapi (1.14.2-1) unstable; urgency=medium * New upstream bugfix release gstreamer-vaapi (1.14.1-1) unstable; urgency=medium * New upstream bugfix release -- Iain Lane Thu, 16 May 2019 13:39:10 +0100 ** Changed in: gstreamer-vaapi (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: gstreamer-editing-services1.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Released Status in gst-plugins-bad1.0 source package in Bionic: Fix Released Status in gst-plugins-base1.0 source package in Bionic: Fix Released Status in gst-plugins-good1.0 source package in Bionic: Fix Released Status in gst-plugins-ugly1.0 source package in Bionic: Fix Released Status in gst-python1.0 source package in Bionic: Fix Released Status in gst-rtsp-server1.0 source package in Bionic: Fix Released Status in gstreamer-editing-services1.0 source package in Bionic: Fix Released Status in gstreamer-vaapi source package in Bionic: Fix Released Status in gstreamer1.0 source package in Bionic: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829366] Update Released
The verification of the Stable Release Update for gstreamer1.0 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Released Status in gst-plugins-bad1.0 source package in Bionic: Fix Released Status in gst-plugins-base1.0 source package in Bionic: Fix Released Status in gst-plugins-good1.0 source package in Bionic: Fix Released Status in gst-plugins-ugly1.0 source package in Bionic: Fix Released Status in gst-python1.0 source package in Bionic: Fix Released Status in gst-rtsp-server1.0 source package in Bionic: Fix Released Status in gstreamer-editing-services1.0 source package in Bionic: Fix Released Status in gstreamer-vaapi source package in Bionic: Fix Released Status in gstreamer1.0 source package in Bionic: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
This bug was fixed in the package gst-plugins-bad1.0 -
1.14.4-1ubuntu1~ubuntu18.04.1
---
gst-plugins-bad1.0 (1.14.4-1ubuntu1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1829366)
gst-plugins-bad1.0 (1.14.4-1ubuntu1) cosmic; urgency=medium
* Merge with Debian unstable; remaining changes:
+ Stop installing camerabin2 basecamerabin jpegformat - plugins which have
moved to -good.
+ Provide gstreamer-plugins-bad-1.0.pc with Requires on
gstreamer-plugins-good-1.0 - the package we've moved the referenced
library to. This maintains compatibility with upstream software and
other distributions.
+ debian/control{,.in}: Update Vcs-* for Ubuntu
* debian/gbp.conf: Set the debian-branch to ubuntu
gst-plugins-bad1.0 (1.14.4-1) unstable; urgency=medium
* New upstream bugfix release
gst-plugins-bad1.0 (1.14.3-1) unstable; urgency=medium
[ Hugh McMaster ]
* gir1.2-gst-plugins-bad-1.0: Install the typelibs into a multi-arch
library directory.
* debian/control.in:
- Mark gir1.2-gst-plugins-bad-1.0 Multi-Arch: same.
- Remove a duplicate ${gir:Depends} from gir1.2-gst-plugins-bad-1.0.
- Mark libgstreamer-plugins-bad1.0-dev Multi-Arch: same.
[ Sebastian Dröge ]
* New upstream bugfix release.
gst-plugins-bad1.0 (1.14.2-1ubuntu1) cosmic; urgency=low
* Merge from Debian unstable. Remaining changes:
+ Stop installing camerabin2 basecamerabin jpegformat - plugins which have
moved to -good.
+ Provide gstreamer-plugins-bad-1.0.pc with Requires on
gstreamer-plugins-good-1.0 - the package we've moved the referenced
library to. This maintains compatibility with upstream software and
other distributions.
+ debian/control{,.in}: Update Vcs-* for Ubuntu
gst-plugins-bad1.0 (1.14.2-1) unstable; urgency=medium
* New upstream bugfix release
gst-plugins-bad1.0 (1.14.1-1ubuntu2) cosmic; urgency=medium
* No-change rebuild for x265 soname change.
gst-plugins-bad1.0 (1.14.1-1ubuntu1) cosmic; urgency=medium
* Merge with Debian unstable (LP: #1772898); remaining changes:
+ Stop installing camerabin2 basecamerabin jpegformat - plugins which have
moved to -good.
+ Provide gstreamer-plugins-bad-1.0.pc with Requires on
gstreamer-plugins-good-1.0 - the package we've moved the referenced
library to. This maintains compatibility with upstream software and
other distributions.
+ debian/control{,.in}: Update Vcs-* for Ubuntu
-- Iain Lane Thu, 16 May 2019 13:19:09 +0100
** Changed in: gst-libav1.0 (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1829366
Title:
[SRU] Bugfix release 1.14.4
Status in gst-libav1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
Fix Released
Status in gst-python1.0 package in Ubuntu:
Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
Fix Released
Status in gstreamer-vaapi package in Ubuntu:
Fix Released
Status in gstreamer1.0 package in Ubuntu:
Fix Released
Status in gst-libav1.0 source package in Bionic:
Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
Fix Released
Status in gst-python1.0 source package in Bionic:
Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
Fix Released
Status in gstreamer-vaapi source package in Bionic:
Fix Released
Status in gstreamer1.0 source package in Bionic:
Fix Released
Bug description:
[ Description ]
We should keep up with GStreamer's bugfix releases in the 1.14 series
that 18.04 shipped with.
[ QA and testing ]
Play a range of videos in Totem. Play a range of audio tracks in
Rhythmbox. Try to stream audio and/or video. Try to install a missing
codec.
In all cases, make sure that everything which worked before still
works.
[ Regression potential ]
If one of the fixes is bad then it might break video or audio
playback, or could crash any application that tries to use gstreamer.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
This bug was fixed in the package gst-plugins-ugly1.0 - 1.14.4-1~ubuntu18.04.1 --- gst-plugins-ugly1.0 (1.14.4-1~ubuntu18.04.1) bionic; urgency=medium * No-change backport to bionic (LP: #1829366) gst-plugins-ugly1.0 (1.14.4-1) unstable; urgency=medium * New upstream bugfix release gst-plugins-ugly1.0 (1.14.3-1) unstable; urgency=medium * New upstream bugfix release. gst-plugins-ugly1.0 (1.14.2-1) unstable; urgency=medium * New upstream bugfix release gst-plugins-ugly1.0 (1.14.1-1) unstable; urgency=medium * New upstream bugfix release -- Iain Lane Thu, 16 May 2019 13:19:31 +0100 ** Changed in: gst-plugins-good1.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Bug watch added: bugzilla.gnome.org/ #796879 https://bugzilla.gnome.org/show_bug.cgi?id=796879 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Released Status in gst-plugins-bad1.0 source package in Bionic: Fix Released Status in gst-plugins-base1.0 source package in Bionic: Fix Released Status in gst-plugins-good1.0 source package in Bionic: Fix Released Status in gst-plugins-ugly1.0 source package in Bionic: Fix Released Status in gst-python1.0 source package in Bionic: Fix Released Status in gst-rtsp-server1.0 source package in Bionic: Fix Released Status in gstreamer-editing-services1.0 source package in Bionic: Fix Released Status in gstreamer-vaapi source package in Bionic: Fix Released Status in gstreamer1.0 source package in Bionic: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
This bug was fixed in the package gst-libav1.0 - 1.14.4-0ubuntu1~ubuntu18.04.1 --- gst-libav1.0 (1.14.4-0ubuntu1~ubuntu18.04.1) bionic; urgency=medium * New upstream bugfix release (LP: #1829366) -- Iain Lane Thu, 16 May 2019 13:23:37 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Released Status in gst-plugins-bad1.0 source package in Bionic: Fix Released Status in gst-plugins-base1.0 source package in Bionic: Fix Released Status in gst-plugins-good1.0 source package in Bionic: Fix Released Status in gst-plugins-ugly1.0 source package in Bionic: Fix Released Status in gst-python1.0 source package in Bionic: Fix Released Status in gst-rtsp-server1.0 source package in Bionic: Fix Released Status in gstreamer-editing-services1.0 source package in Bionic: Fix Released Status in gstreamer-vaapi source package in Bionic: Fix Released Status in gstreamer1.0 source package in Bionic: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
This bug was fixed in the package gst-plugins-good1.0 -
1.14.4-1ubuntu1~ubuntu18.04.1
---
gst-plugins-good1.0 (1.14.4-1ubuntu1~ubuntu18.04.1) bionic; urgency=medium
* No-change backport to bionic (LP: #1829366)
gst-plugins-good1.0 (1.14.4-1ubuntu1) cosmic; urgency=medium
* Merge from Debian unstable. Remaining changes:
+ Import plugins from -bad that are needed for main applications.
- jpegformat
- camerabin (+ basecamerabinsrc + photography)
+ Break and Replace -bad versions which contained these plugins.
+ Add a library package containing the shared library and a -dev package for
compiling against it. Add Breaks and Replaces against the plugins packages
which formerly contained files shipped here.
+ Add 'pluginsdir' variable to our added pcfile for compatibility with
some external software
+ debian/control{,.in}: Update Vcs-* for Ubuntu
gst-plugins-good1.0 (1.14.4-1) unstable; urgency=medium
* New upstream bugfix release
gst-plugins-good1.0 (1.14.3-1) unstable; urgency=medium
* New upstream bugfix release.
gst-plugins-good1.0 (1.14.2-1ubuntu3) cosmic; urgency=medium
* Add some information on previous patch about the new upstream issue:
https://bugzilla.gnome.org/show_bug.cgi?id=796879
gst-plugins-good1.0 (1.14.2-1ubuntu2) cosmic; urgency=medium
* debian/patches/b03df1abf828514b0966db058388bf974ed0cf4f.patch:
revert upstream b03df1abf828514b0966db058388bf974ed0cf4f making
the package FTBFS on arm* / Ubuntu
gst-plugins-good1.0 (1.14.2-1ubuntu1) cosmic; urgency=low
* Merge from Debian unstable. Remaining changes:
+ Import plugins from -bad that are needed for main applications.
- jpegformat
- camerabin (+ basecamerabinsrc + photography)
+ Break and Replace -bad versions which contained these plugins.
+ Add a library package containing the shared library and a -dev package for
compiling against it. Add Breaks and Replaces against the plugins packages
which formerly contained files shipped here.
+ Add 'pluginsdir' variable to our added pcfile for compatibility with
some external software
+ debian/control{,.in}: Update Vcs-* for Ubuntu
gst-plugins-good1.0 (1.14.2-1) unstable; urgency=medium
* New upstream bugfix release
gst-plugins-good1.0 (1.14.1-1ubuntu1) cosmic; urgency=medium
* Merge with Debian unstable (LP: #1772898); remaining changes:
+ Import plugins from -bad that are needed for main applications.
- jpegformat
- camerabin (+ basecamerabinsrc + photography)
+ Break and Replace -bad versions which contained these plugins.
+ Add a library package containing the shared library and a -dev package for
compiling against it. Add Breaks and Replaces against the plugins packages
which formerly contained files shipped here.
+ Add 'pluginsdir' variable to our added pcfile for compatibility with
some external software
+ debian/control{,.in}: Update Vcs-* for Ubuntu
* Revert 1.14.0-{2,3,4}. We've worked around this issue in -base instead, so
we don't need to disable Qt5 here.
-- Iain Lane Thu, 16 May 2019 13:18:09 +0100
** Changed in: gst-plugins-base1.0 (Ubuntu Bionic)
Status: In Progress => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9928
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1829366
Title:
[SRU] Bugfix release 1.14.4
Status in gst-libav1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
Fix Released
Status in gst-python1.0 package in Ubuntu:
Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
Fix Released
Status in gstreamer-vaapi package in Ubuntu:
Fix Released
Status in gstreamer1.0 package in Ubuntu:
Fix Released
Status in gst-libav1.0 source package in Bionic:
Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
Fix Released
Status in gst-python1.0 source package in Bionic:
Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
Fix Released
Status in gstreamer-vaapi source package in Bionic:
Fix Released
Status in gstreamer1.0 source package in Bionic:
Fix Released
Bug description:
[ Description ]
We should keep up with GStreamer's bugfix releases in
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
This bug was fixed in the package gstreamer-editing-services1.0 - 1.14.4-1~ubuntu18.04.1 --- gstreamer-editing-services1.0 (1.14.4-1~ubuntu18.04.1) bionic; urgency=medium * No-change backport to bionic (LP: #1829366) gstreamer-editing-services1.0 (1.14.4-1) unstable; urgency=medium * New upstream bugfix release gstreamer-editing-services1.0 (1.14.3-1) unstable; urgency=medium * New upstream bugfix release. * debian/control, debian/gir1.2-ges-1.0.install: + Various multi-arch fixes. gstreamer-editing-services1.0 (1.14.2-1) unstable; urgency=medium * New upstream bugfix release gstreamer-editing-services1.0 (1.14.1-1) unstable; urgency=medium * New upstream bugfix release -- Iain Lane Thu, 16 May 2019 13:43:34 +0100 ** Changed in: gst-rtsp-server1.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Released Status in gst-plugins-bad1.0 source package in Bionic: Fix Released Status in gst-plugins-base1.0 source package in Bionic: Fix Released Status in gst-plugins-good1.0 source package in Bionic: Fix Released Status in gst-plugins-ugly1.0 source package in Bionic: Fix Released Status in gst-python1.0 source package in Bionic: Fix Released Status in gst-rtsp-server1.0 source package in Bionic: Fix Released Status in gstreamer-editing-services1.0 source package in Bionic: Fix Released Status in gstreamer-vaapi source package in Bionic: Fix Released Status in gstreamer1.0 source package in Bionic: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
This bug was fixed in the package gst-rtsp-server1.0 - 1.14.4-1~ubuntu18.04.1 --- gst-rtsp-server1.0 (1.14.4-1~ubuntu18.04.1) bionic; urgency=medium * No-change backport to bionic (LP: #1829366) gst-rtsp-server1.0 (1.14.4-1) unstable; urgency=medium * New upstream bugfix release gst-rtsp-server1.0 (1.14.3-1) unstable; urgency=medium * New upstream bugfix release. * debian/control, debian/gir1.2-gst-rtsp-server-1.0.install: + Various multi-arch fixes. gst-rtsp-server1.0 (1.14.2-1) unstable; urgency=medium * New upstream bugfix release gst-rtsp-server1.0 (1.14.1-1) unstable; urgency=medium * New upstream bugfix release -- Iain Lane Thu, 16 May 2019 13:43:55 +0100 ** Changed in: gst-python1.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Released Status in gst-plugins-bad1.0 source package in Bionic: Fix Released Status in gst-plugins-base1.0 source package in Bionic: Fix Released Status in gst-plugins-good1.0 source package in Bionic: Fix Released Status in gst-plugins-ugly1.0 source package in Bionic: Fix Released Status in gst-python1.0 source package in Bionic: Fix Released Status in gst-rtsp-server1.0 source package in Bionic: Fix Released Status in gstreamer-editing-services1.0 source package in Bionic: Fix Released Status in gstreamer-vaapi source package in Bionic: Fix Released Status in gstreamer1.0 source package in Bionic: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Cosmic: Fix Released Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. In order to verify the fix, one needs to change MODULES option to dep on /etc/initramfs-tools/initramfs.conf, recreate initramfs and reboot, check the system has booted fine. That should not break on systems with non nvme disks or systems with non multipath nvme systems, and that should now work on multipath nvme systems. sed -i /MODULES=/s,=.*,=dep, /etc/initramfs-tools/initramfs.conf update-initramfs -u -k all reboot [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR:
[Touch-packages] [Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
** Changed in: fonts-noto-cjk (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in Poppler: New Status in fonts-noto-cjk package in Ubuntu: Fix Released Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: Fix Released Status in libreoffice-l10n source package in Xenial: Fix Released Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: New Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Released Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in fonts-noto-cjk source package in Cosmic: New Status in gnome-characters source package in Cosmic: New Status in gucharmap source package in Cosmic: New Status in icu source package in Cosmic: New Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Status in mozc source package in Cosmic: Fix Released Status in openjdk-8 source package in Cosmic: New Status in poppler-data source package in Cosmic: New Status in unicode-data source package in Cosmic: New Status in fonts-noto-cjk source package in Disco: New Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. == Typing / input methods == 1) Type in 'heisei' 2) Verify that the input method
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
** Branch linked: lp:~rbalint/britney/autopkgtest-bionic-hint -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833671] Re: bond interfaces stop working after restart of systemd-networkd
This bug also affects my company. Please integrate the fix soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833671 Title: bond interfaces stop working after restart of systemd-networkd Status in systemd package in Ubuntu: Confirmed Bug description: Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for interface eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 100 ms for interface eno1 and after that nothing until I stop systemd-networkd, delete the bond interface, and then start systemd-networkd again. On most machines the cycle seems to take a bit longer and the interfaces reach a hard down start before coming back and in that case there seems to be no problem. I think this is likely an instance of this upstream bug: https://github.com/systemd/systemd/issues/10118 which has a fix here: https://github.com/systemd/systemd/pull/10465 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
This bug was fixed in the package initramfs-tools - 0.131ubuntu15.2 --- initramfs-tools (0.131ubuntu15.2) cosmic; urgency=medium * Add modules for nvme path components on multipath nvme. LP: #1778844 -- Thadeu Lima de Souza Cascardo Tue, 16 Apr 2019 21:19:25 -0300 ** Changed in: initramfs-tools (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: Fix Committed Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Cosmic: Fix Released Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. In order to verify the fix, one needs to change MODULES option to dep on /etc/initramfs-tools/initramfs.conf, recreate initramfs and reboot, check the system has booted fine. That should not break on systems with non nvme disks or systems with non multipath nvme systems, and that should now work on multipath nvme systems. sed -i /MODULES=/s,=.*,=dep, /etc/initramfs-tools/initramfs.conf update-initramfs -u -k all reboot [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE)
[Touch-packages] [Bug 1832457] Re: [SRU] 2.60.4
This bug was fixed in the package glib2.0 - 2.60.4-0ubuntu0.19.04.1 --- glib2.0 (2.60.4-0ubuntu0.19.04.1) disco; urgency=medium * New upstream release (LP: #1832457) + Leak fixes to some `glib-genmarshal` generated code + Further fixes to the Happy Eyeballs (RFC 8305) implementation + File system permissions fix to clamp down permissions in a small time window when copying files (CVE-2019-12450) + build: Fix a typo in the test whether _NL_ABALTMON_n is supported + Critical in g_socket_client_async_connect_complete + Fix crash when displaying notifications on macOS (!786) + Fix documentation for `gdbus-tool wait` to use correct units + Fix typo in German translation + glib/date test fails + glib/gconstructor.h: Include stdlib.h for MSVC builds + GNetworkAddressAddressEnumerator unsafely modifies cache in GNetworkAddress + gnetworkaddress: Fix parallel enumerations interfering with eachother + gnetworkmonitornm: Fix network available detection + Fixes to improved network status detection with NetworkManager (#1788) + GResource generation test incompatible with stable LLVM on Linux + gschema.dtd: Add target attribute to alias + gsocketclient: Fix a leak in the connection code + Improve network status detection with NetworkManager + Leaks in gsocketclient.c connection code + test_month_names: assertion failed + tests: Update month name check for Greek locale + Update gdb pretty-printer for GHashTable + Various fixes to small key/value support in `GHashTable` + New GHashTable implementation confuses valgrind + more GHashTable fixes + GDB pretty-printer for GHashTable no longer works + ghash: Disable small-arrays under valgrind * CVE-2019-12450.patch: Drop, in this upstream release -- Iain Lane Wed, 12 Jun 2019 10:04:45 +0100 ** Changed in: glib2.0 (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832457 Title: [SRU] 2.60.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Disco: Fix Released Bug description: [ Description ] New stable release in the 2.60 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. [ Upstream NEWS ] Overview of changes in GLib 2.60.4 == * Fixes to improved network status detection with NetworkManager (#1788) * Leak fixes to some `glib-genmarshal` generated code (#1793) * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865) * File system permissions fix to clamp down permissions in a small time window when copying files (CVE-2019-12450, !876) * Bugs fixed: - #1755 Please revert #535 gmacros: Try to use the standard __func__ first in G_STRFUNC - #1788 GNetworkMonitor claims I am offline - #1792 glib-genmarshal generated valist marshal does not respect static scope for some types - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT type - #1795 Fix mingw32 CI on older branches - !865 gnetworkaddress: fix "happy eyeballs" logic - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60 Overview of changes in GLib 2.60.3 == * Various fixes to small key/value support in `GHashTable` (#1749, #1780) * Bugs fixed: - #1747 Critical in g_socket_client_async_connect_complete - #1749 New GHashTable implementation confuses valgrind - #1759 test_month_names: assertion failed - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in GNetworkAddress - #1774 Leaks in gsocketclient.c connection code - #1776 glib/date test fails - #1780 GDB pretty-printer for GHashTable no longer works - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master' - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to glib-2-60 - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to glib-2-60 - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n is supported” to glib-2-60 - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering with eachother" to glib-2-60 - !838 Backport !835 “Fix typo in German translation” to glib-2-60 - !841 Backport !839 “tests: Update month name check for Greek locale” to glib-2-60 - !844 Backport !840 “ghash: Disable small-arrays under
[Touch-packages] [Bug 1832457] Update Released
The verification of the Stable Release Update for glib2.0 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832457 Title: [SRU] 2.60.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Disco: Fix Released Bug description: [ Description ] New stable release in the 2.60 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. [ Upstream NEWS ] Overview of changes in GLib 2.60.4 == * Fixes to improved network status detection with NetworkManager (#1788) * Leak fixes to some `glib-genmarshal` generated code (#1793) * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865) * File system permissions fix to clamp down permissions in a small time window when copying files (CVE-2019-12450, !876) * Bugs fixed: - #1755 Please revert #535 gmacros: Try to use the standard __func__ first in G_STRFUNC - #1788 GNetworkMonitor claims I am offline - #1792 glib-genmarshal generated valist marshal does not respect static scope for some types - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT type - #1795 Fix mingw32 CI on older branches - !865 gnetworkaddress: fix "happy eyeballs" logic - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60 Overview of changes in GLib 2.60.3 == * Various fixes to small key/value support in `GHashTable` (#1749, #1780) * Bugs fixed: - #1747 Critical in g_socket_client_async_connect_complete - #1749 New GHashTable implementation confuses valgrind - #1759 test_month_names: assertion failed - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in GNetworkAddress - #1774 Leaks in gsocketclient.c connection code - #1776 glib/date test fails - #1780 GDB pretty-printer for GHashTable no longer works - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master' - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to glib-2-60 - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to glib-2-60 - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n is supported” to glib-2-60 - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering with eachother" to glib-2-60 - !838 Backport !835 “Fix typo in German translation” to glib-2-60 - !841 Backport !839 “tests: Update month name check for Greek locale” to glib-2-60 - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to glib-2-60 - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to glib-2-60 - !855 Backport !848 (more GHashTable fixes) to glib-2-60 - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60 * Translation updates: - German Overview of changes in GLib 2.60.2 == * Fix crash when displaying notifications on macOS (!786) * Improve network status detection with NetworkManager (!781) * Bugs fixed: - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds - !793 Backport !786: “cocoanotificationbackend: do not release readonly property” to glib-2-60 - !803 Backport !781 “gnetworkmonitornm: Fix network available detection” to glib-2-60 * Translation updates: - Catalan Overview of changes in GLib 2.60.1 == * Fix documentation for `gdbus-tool wait` to use correct units * Bugs fixed: - #1709 GResource generation test incompatible with stable LLVM on Linux - #1725 gosxappinfo.h is not installed on macOS - #1737 gdbus-tool wait command timeout argument incorrect unit reference - !711 socket: Fix annotation for flags in g_socket_receive_message - !722 Backport codegen: Fix use of uninitialised variable from !721 to glib-2-60 - !727 Backport !719 “Handle an UNKNOWN NetworkManager connectivity as NONE” to glib-2-60 - !729 Backport !728 “gsocket: Remove (type) annotation from flags arguments” to glib-2-60 - !758
[Touch-packages] [Bug 1833527] Re: in gnome settings audio section does not see any sound card
I just realised that removing chrome remote desktop config isn't enough. Like I mentioned on my PC i had the same issue. I had to remove .config/pulse too and restart to make it work -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1833527 Title: in gnome settings audio section does not see any sound card Status in pulseaudio package in Ubuntu: Incomplete Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 12:28:49 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834192] Re: apparmor mult_mount regression test fails in eoan
Fix committed upstream: https://gitlab.com/apparmor/apparmor/commit/7c7a4bc5311d983f2c4316252b830c52a5a0930b and backported to apparmor-2.13. We can work around this in qa-regression-testing or fix with an apparmor upload. ** Changed in: apparmor (Ubuntu) Assignee: Steve Beattie (sbeattie) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1834192 Title: apparmor mult_mount regression test fails in eoan Status in apparmor package in Ubuntu: Confirmed Bug description: In running adt testing on 5.2-based kernels for eoan, I'm seeing failures from the apparmor mult_mount regression test. Running the test case manually with -x yields: + dd if=/dev/zero of=/tmp/sdtest.2210-22387-i6UxxQ/image.ext3 bs=4096 count=20 + mkfs.ext2 -F -m 0 -N 10 /tmp/sdtest.2210-22387-i6UxxQ/image.ext3 ++ error_handler ++ fatalerror 'Unexpected shell error. Run with -x to debug' Running the following manually in a shell also fails in eoan with the 5.0 kernel copied forward from disco, while it passes in disco: $ uname -a Linux ee-apparmor 5.0.0-17-generic #18-Ubuntu SMP Tue Jun 4 15:34:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dd if=/dev/zero of=test.img bs=4096 count=20 20+0 records in 20+0 records out 81920 bytes (82 kB, 80 KiB) copied, 0.000406443 s, 202 MB/s $ mkfs.ext2 -F -m 0 -N 10 test.img mke2fs 1.45.2 (27-May-2019) test.img: Not enough space to build proposed filesystem while setting up superblock So this seems likely to be due to some change with mke2fs; not sure if this is a regression there or if the test was getting away with doing something invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1834192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834333] Re: Scaling problem with Qt apps
This may be relate to bug 1824753 ** Package changed: gnome-control-center (Ubuntu) => qtbase-opensource- src (Ubuntu) ** Changed in: qtbase-opensource-src (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1834333 Title: Scaling problem with Qt apps Status in qtbase-opensource-src package in Ubuntu: New Bug description: Hi I have problem with scaling for Qt apps. when i open Kolourpaint scaling is too small i have Ubuntu 18.04 and install from snap and apt i first report to bugs.kde.org and they tell me to report here https://bugs.kde.org/show_bug.cgi?id=407668 Kolourpaint its not only app with problem , anydesk , filezilla , pylon viewer , dukto , stacer , vmware horizon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1834333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834333] [NEW] Scaling problem with Qt apps
You have been subscribed to a public bug: Hi I have problem with scaling for Qt apps. when i open Kolourpaint scaling is too small i have Ubuntu 18.04 and install from snap and apt i first report to bugs.kde.org and they tell me to report here https://bugs.kde.org/show_bug.cgi?id=407668 Kolourpaint its not only app with problem , anydesk , filezilla , pylon viewer , dukto , stacer , vmware horizon ** Affects: qtbase-opensource-src (Ubuntu) Importance: Low Status: New ** Tags: hidpi qt scaling -- Scaling problem with Qt apps https://bugs.launchpad.net/bugs/1834333 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
