[Touch-packages] [Bug 1311889] Re: App launcher icons don't respond
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1311889 Title: App launcher icons don't respond Status in Ubuntu: Incomplete Bug description: Left click on an app icon in the launcher bar works fine on first use. After closing the app, it is impossible to open the app again by left click. The only way to open the same app is to right click and select the open option from the menu. Software updater would not launch after notifying me by being highlighted that updates were available. It was necessary to use apt-get in terminal to update. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 23 22:27:47 2014 DistUpgraded: 2014-04-22 20:30:06,232 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516/M62-S [Mobility Radeon X1350] [1002:7196] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30d7] InstallationDate: Installed on 2013-08-21 (245 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) MachineType: Hewlett-Packard HP Compaq 6820s ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=0f70fc5d-bedc-4a3f-b7f8-707f56830f71 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-22 (1 days ago) dmi.bios.date: 04/14/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MDD Ver. F.0A dmi.board.name: 30D7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 83.13 dmi.chassis.asset.tag: CNU8313FRT dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MDDVer.F.0A:bd04/14/2008:svnHewlett-Packard:pnHPCompaq6820s:pvrF.0A:rvnHewlett-Packard:rn30D7:rvrKBCVersion83.13:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6820s dmi.product.version: F.0A dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 23 21:02:54 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1311889/+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 1338715] Re: Snapping windows get enabled automatically sometimes
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1338715 Title: Snapping windows get enabled automatically sometimes Status in Ubuntu: Incomplete Bug description: Every once in a while, the windows edges get sticky. In combination with Wobbly Windows, this gives an annoying behavior. The setting for snappy windows in compiz is off (stays of), and sticky edges in system settings/display are off and stay off. I resolve the issue by fooling around with these settings and by switching wobbly windows off and on again. But the edges should not get sticky by themselves, should they? It may be related to Google Chrome. I noticed strange behavior of Chrome when this happened just a minute ago, like the Chrome window flickering and turning on and off. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-31.55-generic 3.13.11.4 Uname: Linux 3.13.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 7 20:25:24 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1370] InstallationDate: Installed on 2014-04-21 (77 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-31-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CROSSHAIR V FORMULA-Z dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd11/15/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVFORMULA-Z:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Jul 6 15:18:56 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputEee PC WMI hotkeys KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: nouveau To manage notifications about this bug go to:
[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution
From cloud-init point of view the solution now implemented make sense: to run it before the apt-daily-upgrade. However, I wanted to add that there are other use cases as well such as SSM documents being executed on instances. These can be executed in batch at any time and may also require installation of packages and thus interfere with these unattended upgrades. The execution of documents is not linked directly to cloud-init and may be ran after the instances has been booted, so this falls in the other category of having some kind queuing system or at least a centralized way to obtain a lock to be able to use apt. At the moment there are dozens of different possibilities how to get a mutex to be able to execute apt, but somehow we couldn't find a bullet proof way that works *every time*. So maybe this does not really fit into this ticket, but to address that this is only a partial fix to a bigger problem. -- 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/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution Status in APT: Fix Released Status in cloud-init: Fix Released Status in apt package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Yakkety: Won't Fix Status in cloud-init source package in Zesty: Fix Released Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] A cloud-config that contains packages to install (see below) or 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a result of contention with the apt-daily.service that updates that information. Cloud-config showing the problem is just like: $ cat my.yaml #cloud-config packages: ['hello'] [Test Case] lxc-proposed-snapshot is https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot It publishes an image to lxd with proposed enabled and cloud-init upgraded. a.) launch an instance with proposed version of cloud-init and some user-data. This is platform independent. The test case demonstrates lxd. $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ "package_upgrade: true" > config.yaml $ release=xenial $ ref=proposed-$release $ ./lxc-proposed-snapshot --proposed --publish $release $ref; b.) start the instance $ name=$release-1693361 $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) $ sleep 1 $ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log # watch this boot. c.) Look for evidence of systemd failure journalctl -o short-precise | grep -i break journalctl -o short-precise | grep -i order [Regression Potential] Regression chance here is low. Its possible that ordering loops could occur. When that does happen, journalctl will mention it. Unfortunately in such cases systemd somewhat randomly picks a service to kil so behavior is somewhat undefined. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11121fe4 === End SRU Template === apt-daily is now a systemd service rather than being invoked by cron.daily. If one builds a custom AMI it is possible that the apt- daily.timer will fire during boot. This can fire at the same time cloud-init is running and if cloud-init loses the race the invocation of apt (e.g. use of "packages:" in the config) will fail. There is a lot of discussion online about this change to apt-daily (e.g. unattended upgrades happening during business hours, delaying boot, etc.) and discussion of potential systemd changes regarding timers firing during boot (c.f. https://github.com/systemd/systemd/issues/5659). While it would be better to solve this in apt itself, I suggest that cloud-init be defensive when calling apt and implement some retry mechanism. Various instances of people running into this issue: https://github.com/chef/bento/issues/609 https://clusterhq.atlassian.net/browse/FLOC-4486 https://github.com/boxcutter/ubuntu/issues/73 https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1693361/+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 1952918] Re: Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed
Ok, removing fluidsynth from jammy-proposed for now, please be sure to re-introduce it once the other transitions make it through. I checked the rdeps of libfluidsynth3 from -proposed though, and it seems we have two packages in jammy-proposed that have been rebuilt to now depend on libfluidsynth3 instead of libfluidsynth2. I'm leaving them there as-is, but it's good to know that those are already involved with the SONAME bump: * mpd * minuet $ remove-package -s jammy-proposed -m "Temporarily dropping from -proposed to let other transitions finish first. To be reintroduced (LP: #1952918)" fluidsynth Removing packages from jammy-proposed: fluidsynth 2.2.4-2 in jammy fluidsynth 2.2.4-2 in jammy amd64 fluidsynth 2.2.4-2 in jammy arm64 fluidsynth 2.2.4-2 in jammy armhf fluidsynth 2.2.4-2 in jammy i386 fluidsynth 2.2.4-2 in jammy ppc64el fluidsynth 2.2.4-2 in jammy riscv64 fluidsynth 2.2.4-2 in jammy s390x libfluidsynth-dev 2.2.4-2 in jammy amd64 libfluidsynth-dev 2.2.4-2 in jammy arm64 libfluidsynth-dev 2.2.4-2 in jammy armhf libfluidsynth-dev 2.2.4-2 in jammy i386 libfluidsynth-dev 2.2.4-2 in jammy ppc64el libfluidsynth-dev 2.2.4-2 in jammy riscv64 libfluidsynth-dev 2.2.4-2 in jammy s390x libfluidsynth3 2.2.4-2 in jammy amd64 libfluidsynth3 2.2.4-2 in jammy arm64 libfluidsynth3 2.2.4-2 in jammy armhf libfluidsynth3 2.2.4-2 in jammy i386 libfluidsynth3 2.2.4-2 in jammy ppc64el libfluidsynth3 2.2.4-2 in jammy riscv64 libfluidsynth3 2.2.4-2 in jammy s390x Comment: Temporarily dropping from -proposed to let other transitions finish first. To be reintroduced (LP: #1952918) Remove [y|N]? y 1 package successfully removed. ** Changed in: fluidsynth (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/1952918 Title: Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed Status in fluidsynth package in Ubuntu: Fix Released Bug description: fluidsynth 2.2.4-2 (currently in jammy-proposed) has a SONAME bump: libfluidsynth2 -> libfluidsynth3 which is a fairly large transition: $ reverse-depends -b -l src:fluidsynth | wc -l 30 This list of reverse-dependencies has exactly one package in common with other two currently ongoing transitions: $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l src:libidn) vlc $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l src:liburing) mpd These other two transitions are almost done, hopefully just requiring couple of minor uploads (merging a new Debian revision of ghostscript and uploading a new Ubuntu revision of exim4 to resolve a components- mismatch). I think it it would be better to finish these other two transitions first, without fluidsynth, and then sync fluidsynth again, to be handled separately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1952918/+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 1952918] Re: Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed
Let me try looking into that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/1952918 Title: Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed Status in fluidsynth package in Ubuntu: New Bug description: fluidsynth 2.2.4-2 (currently in jammy-proposed) has a SONAME bump: libfluidsynth2 -> libfluidsynth3 which is a fairly large transition: $ reverse-depends -b -l src:fluidsynth | wc -l 30 This list of reverse-dependencies has exactly one package in common with other two currently ongoing transitions: $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l src:libidn) vlc $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l src:liburing) mpd These other two transitions are almost done, hopefully just requiring couple of minor uploads (merging a new Debian revision of ghostscript and uploading a new Ubuntu revision of exim4 to resolve a components- mismatch). I think it it would be better to finish these other two transitions first, without fluidsynth, and then sync fluidsynth again, to be handled separately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1952918/+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 1640736] Re: dell dock system is freezing while docking
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1640736 Title: dell dock system is freezing while docking Status in Ubuntu: Incomplete Bug description: I Can't find any solution to solve this headache. :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Nov 10 15:30:36 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.36, 4.2.0-42-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06dc] InstallationDate: Installed on 2016-11-09 (1 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Dell Inc. Latitude E7470 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-42-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 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 xserver.bootTime: Thu Nov 10 15:28:33 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1168 vendor LGD xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1640736/+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 1953337] Re: Backport needed for 18.04 and 20.04 LTS (CVE-2021-42378)
It's "low" because I don't believe our use of busybox runs untrusted awk scripts. There are test packages available in the security team PPA here: https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/+packages They will probably be released this week. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1953337 Title: Backport needed for 18.04 and 20.04 LTS (CVE-2021-42378) Status in busybox package in Ubuntu: New Bug description: Dear community, Qualys reports a finding on our Ubuntu 18.04 and Ubuntu 20.04 instances because of CVE-2021-42378. I can see that there is already a fix for Ubuntu 22.04. When will the fix be released for the LTS versions 18.04 and 20.04? I can see the finding is monitored at https://ubuntu.com/security/CVE-2021-42378, but the CVSS3 scoring is 7.2, so I think the rating "high" would be better. Or is there any reason why "low" is ok? Thanks in advance. Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1953337/+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 1913979] Re: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink
I see this behaviour also when /etc is still on the rootfs, but fstab has a "ro" for rootfs. on Ubuntu 18.04 LTS and 20.04 LTS (arm versions for odroids, but not unlikely generally), I get a # nmcli con add type ethernet ifname eth0 con-name X "Error: Failed to add 'X' connection: failure adding connection: settings plugin does not support adding connections" Changing fstab to rw and rebooting removes the error; added or modified connections, including static ip addresses, Wifi connections etc, will persist and work as expected when rebooting later with ro for rootfs in fstab. for me, any fix would ideally enable functionality after a simple # mount -o remount,rw /dev/mmcblk0p2 / instead of having to change fstab and reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1913979 Title: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink Status in network-manager package in Ubuntu: New Bug description: If the /etc/NetworkManager/system-connections directory is a cross- filesystem symlink, activating connections will fail with the unrelated messages: * "failed to create file ...: Read-only file system" (TRACE level) * "failure adding connection: settings plugin does not support adding connections" (DEBUG level and above) * no error message (Gnome UI) I suspect moving the systems-connections directory onto a separate filesystem is not supported because network manager tries to atomically move a connection temp file into place and fails, but this is really hard to figure out since the error messages are completely unrelated. Versions: Ubuntu 20.10 network-manager 1.26.2-1ubuntu1 network-manager-gnome 1.18.0-1ubuntu2 How to reproduce: sudo mv /etc/NetworkManager/system-connections /some/other/mountpoint/system-connections sudo ln -s /some/other/mountpoint/system-connections /etc/NetworkManager/system-connections Then: * select any wifi network via the Gnome UI, or * connect to a wifi network via nmcli, or * connect to a wifi network via nmtui Symptoms: * "failed to create file ...: Read-only file system" (TRACE level, journalctl) * "failure adding connection: settings plugin does not support adding connections" (DEBUG level and above, journalctl and nmtui/nmcli output) * no error message (Gnome UI) Relevant sample logs: Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4038] active-connection[0x56274f6f0a60]: creating Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4039] active-connection[0x56274f6f0a60]: set device "wlp61s0" [0x56274f883f00] Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4039] device[d62304f9da70d783] (wlp61s0): add_pending_action (1): 'activation-5' Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4040] active-connection[0x56274f6f0a60]: constructed (NMActRequest, version-id 5, type managed) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4040] auth: call[37]: CheckAuthorization(org.freedesktop.NetworkManager.network-control), subject=unix-process[pid=1369566, uid=0, start=18908113] (succeeding for root) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4041] auth: call[37]: completed: authorized=1, challenge=0 (simulated) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4041] auth: call[38]: CheckAuthorization(org.freedesktop.NetworkManager.settings.modify.system), subject=unix-process[pid=1369566, uid=0, start=18908113] (succeeding for root) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4042] auth: call[38]: completed: authorized=1, challenge=0 (simulated) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4042] settings: add-connection: failed to add a4e6f563-eb2a-41ff-bc23-986ee3438ed9/'mywifi_2G': settings plugin does not support adding connections Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4061] keyfile: commit: a4e6f563-eb2a-41ff-bc23-986ee3438ed9 (mywifi_2G) failed to add: error writing to file '/etc/NetworkManager/system-connections/mywifi_2G.nmconnection': failed to create file /etc/NetworkManager/system-connections/mywifi_2G.nmconnection.ZE5DY0: Read-only file system Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4062] settings: add-connection: failed to add a4e6f563-eb2a-41ff-bc23-986ee3438ed9/'mywifi_2G': error writing to file '/etc/NetworkManager/system-connections/mywifi_2G.nmconnection': failed to create file /etc/NetworkManager/system-connections/mywifi_2G.nmconnection.ZE5DY0: Read-only file system Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4062] active-connection[0x56274f6f0a60]: Failed to activate '(null)': failure adding connection: settings plugin does not support adding
[Touch-packages] [Bug 1639347] Re: Please check about these issues
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1639347 Title: Please check about these issues Status in Ubuntu: Incomplete Bug description: I don't know, but don't you receive informatios by the program Diagnose?? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Nov 4 21:41:04 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C79 [GeForce 9300] [10de:0864] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C79 [GeForce 9300] [103c:2a7c] InstallationDate: Installed on 2016-08-24 (72 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Compaq-Presario NQ918AA-ABZ CQ5023IT ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-46-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug=1 quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.04 dmi.board.name: Newark dmi.board.vendor: FOXCONN dmi.board.version: HP P/N dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd01/16/2009:svnCompaq-Presario:pnNQ918AA-ABZCQ5023IT:pvr:rvnFOXCONN:rnNewark:rvrHPP/N:cvnHewlett-Packard:ct3:cvr: dmi.product.name: NQ918AA-ABZ CQ5023IT dmi.sys.vendor: Compaq-Presario version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Nov 4 21:15:37 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1639347/+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 1953337] Re: Backport needed for 18.04 and 20.04 LTS (CVE-2021-42378)
Thank you very much! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1953337 Title: Backport needed for 18.04 and 20.04 LTS (CVE-2021-42378) Status in busybox package in Ubuntu: New Bug description: Dear community, Qualys reports a finding on our Ubuntu 18.04 and Ubuntu 20.04 instances because of CVE-2021-42378. I can see that there is already a fix for Ubuntu 22.04. When will the fix be released for the LTS versions 18.04 and 20.04? I can see the finding is monitored at https://ubuntu.com/security/CVE-2021-42378, but the CVSS3 scoring is 7.2, so I think the rating "high" would be better. Or is there any reason why "low" is ok? Thanks in advance. Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1953337/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
Closing as invalid, since I can't repro anymore and I can't explain why. ** Changed in: modemmanager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: Invalid Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1953337] [NEW] Backport needed for 18.04 and 20.04 LTS (CVE-2021-42378)
*** This bug is a security vulnerability *** Public security bug reported: Dear community, Qualys reports a finding on our Ubuntu 18.04 and Ubuntu 20.04 instances because of CVE-2021-42378. I can see that there is already a fix for Ubuntu 22.04. When will the fix be released for the LTS versions 18.04 and 20.04? I can see the finding is monitored at https://ubuntu.com/security/CVE-2021-42378, but the CVSS3 scoring is 7.2, so I think the rating "high" would be better. Or is there any reason why "low" is ok? Thanks in advance. Best regards. ** Affects: busybox (Ubuntu) Importance: Undecided Status: New ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-42378 ** Information type changed from Private Security to Public Security ** Information type changed from Public Security to Private Security ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1953337 Title: Backport needed for 18.04 and 20.04 LTS (CVE-2021-42378) Status in busybox package in Ubuntu: New Bug description: Dear community, Qualys reports a finding on our Ubuntu 18.04 and Ubuntu 20.04 instances because of CVE-2021-42378. I can see that there is already a fix for Ubuntu 22.04. When will the fix be released for the LTS versions 18.04 and 20.04? I can see the finding is monitored at https://ubuntu.com/security/CVE-2021-42378, but the CVSS3 scoring is 7.2, so I think the rating "high" would be better. Or is there any reason why "low" is ok? Thanks in advance. Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1953337/+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 1952477] Re: unable to compile gtk+3.0-3.24.30 on 21.10
Thank you for your bug report, which cmd do you use to start the build? ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1952477 Title: unable to compile gtk+3.0-3.24.30 on 21.10 Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Have Ubuntu 21.10 installed 2. Enable source code repositories 3. Get updates, get source to compile sudo apt-get update sudo apt-get build-dep apt-get source -b gtk+3.0 Expected results: * compiled successful Actual results: * not compiled, shows errors: PASS: test-settings make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite/tools' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite/tools' make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make check-local make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[3]: *** [Makefile:547: check-recursive] Error 1 make[3]: Target 'check' not remade because of errors. make[3]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' Making check in examples make[3]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples' Making check in bp make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/bp' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/bp' Making check in application1 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application1' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application1' Making check in application2 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' Making check in application3 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' Making check in application4 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' Making check in application5 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' Making check in application6 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' Making check in application7 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory
[Touch-packages] [Bug 1952477] Re: unable to compile gtk+3.0-3.24.30 on 21.10
** Description changed: Steps to reproduce: 1. Have Ubuntu 21.10 installed 2. Enable source code repositories 3. Get updates, get source to compile - - - sudo apt-get update - sudo apt-get build-dep - apt-get source -b gtk+3.0 + + sudo apt-get update + sudo apt-get build-dep gtk+3.0 + apt-get source -b gtk+3.0 Expected results: * compiled successful Actual results: * not compiled, shows errors: PASS: test-settings make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite/tools' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite/tools' make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make check-local make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[3]: *** [Makefile:547: check-recursive] Error 1 make[3]: Target 'check' not remade because of errors. make[3]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' Making check in examples make[3]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples' Making check in bp make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/bp' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/bp' Making check in application1 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application1' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application1' Making check in application2 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' Making check in application3 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' Making check in application4 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' Making check in application5 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' Making check in application6 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' Making check in application7 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' Making check in application8 make[4]: Entering directory
[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution
Since 20.04, apt can wait for a lock. The apt(8) command automatically waits for a lock for 120 seconds (non- interactive) or infinitely. The apt-get(8) command can be configured to wait as well by passing the -o DPkg::Lock::Timeout=, where may also be -1 for infinite. This avoids any races you'd get by doing the lock yourself and then invoking apt. -- 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/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution Status in APT: Fix Released Status in cloud-init: Fix Released Status in apt package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Yakkety: Won't Fix Status in cloud-init source package in Zesty: Fix Released Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] A cloud-config that contains packages to install (see below) or 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a result of contention with the apt-daily.service that updates that information. Cloud-config showing the problem is just like: $ cat my.yaml #cloud-config packages: ['hello'] [Test Case] lxc-proposed-snapshot is https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot It publishes an image to lxd with proposed enabled and cloud-init upgraded. a.) launch an instance with proposed version of cloud-init and some user-data. This is platform independent. The test case demonstrates lxd. $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ "package_upgrade: true" > config.yaml $ release=xenial $ ref=proposed-$release $ ./lxc-proposed-snapshot --proposed --publish $release $ref; b.) start the instance $ name=$release-1693361 $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) $ sleep 1 $ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log # watch this boot. c.) Look for evidence of systemd failure journalctl -o short-precise | grep -i break journalctl -o short-precise | grep -i order [Regression Potential] Regression chance here is low. Its possible that ordering loops could occur. When that does happen, journalctl will mention it. Unfortunately in such cases systemd somewhat randomly picks a service to kil so behavior is somewhat undefined. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11121fe4 === End SRU Template === apt-daily is now a systemd service rather than being invoked by cron.daily. If one builds a custom AMI it is possible that the apt- daily.timer will fire during boot. This can fire at the same time cloud-init is running and if cloud-init loses the race the invocation of apt (e.g. use of "packages:" in the config) will fail. There is a lot of discussion online about this change to apt-daily (e.g. unattended upgrades happening during business hours, delaying boot, etc.) and discussion of potential systemd changes regarding timers firing during boot (c.f. https://github.com/systemd/systemd/issues/5659). While it would be better to solve this in apt itself, I suggest that cloud-init be defensive when calling apt and implement some retry mechanism. Various instances of people running into this issue: https://github.com/chef/bento/issues/609 https://clusterhq.atlassian.net/browse/FLOC-4486 https://github.com/boxcutter/ubuntu/issues/73 https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1693361/+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 1952918] Re: Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed
since all packages are now rebuild against liburing2 that need to be, without the fluidsynth dependency, I've re-copied fluidsynth to jammy- proposed now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/1952918 Title: Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed Status in fluidsynth package in Ubuntu: Fix Released Bug description: fluidsynth 2.2.4-2 (currently in jammy-proposed) has a SONAME bump: libfluidsynth2 -> libfluidsynth3 which is a fairly large transition: $ reverse-depends -b -l src:fluidsynth | wc -l 30 This list of reverse-dependencies has exactly one package in common with other two currently ongoing transitions: $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l src:libidn) vlc $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l src:liburing) mpd These other two transitions are almost done, hopefully just requiring couple of minor uploads (merging a new Debian revision of ghostscript and uploading a new Ubuntu revision of exim4 to resolve a components- mismatch). I think it it would be better to finish these other two transitions first, without fluidsynth, and then sync fluidsynth again, to be handled separately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1952918/+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 1913979] Re: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1913979 Title: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink Status in network-manager package in Ubuntu: Confirmed Bug description: If the /etc/NetworkManager/system-connections directory is a cross- filesystem symlink, activating connections will fail with the unrelated messages: * "failed to create file ...: Read-only file system" (TRACE level) * "failure adding connection: settings plugin does not support adding connections" (DEBUG level and above) * no error message (Gnome UI) I suspect moving the systems-connections directory onto a separate filesystem is not supported because network manager tries to atomically move a connection temp file into place and fails, but this is really hard to figure out since the error messages are completely unrelated. Versions: Ubuntu 20.10 network-manager 1.26.2-1ubuntu1 network-manager-gnome 1.18.0-1ubuntu2 How to reproduce: sudo mv /etc/NetworkManager/system-connections /some/other/mountpoint/system-connections sudo ln -s /some/other/mountpoint/system-connections /etc/NetworkManager/system-connections Then: * select any wifi network via the Gnome UI, or * connect to a wifi network via nmcli, or * connect to a wifi network via nmtui Symptoms: * "failed to create file ...: Read-only file system" (TRACE level, journalctl) * "failure adding connection: settings plugin does not support adding connections" (DEBUG level and above, journalctl and nmtui/nmcli output) * no error message (Gnome UI) Relevant sample logs: Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4038] active-connection[0x56274f6f0a60]: creating Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4039] active-connection[0x56274f6f0a60]: set device "wlp61s0" [0x56274f883f00] Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4039] device[d62304f9da70d783] (wlp61s0): add_pending_action (1): 'activation-5' Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4040] active-connection[0x56274f6f0a60]: constructed (NMActRequest, version-id 5, type managed) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4040] auth: call[37]: CheckAuthorization(org.freedesktop.NetworkManager.network-control), subject=unix-process[pid=1369566, uid=0, start=18908113] (succeeding for root) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4041] auth: call[37]: completed: authorized=1, challenge=0 (simulated) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4041] auth: call[38]: CheckAuthorization(org.freedesktop.NetworkManager.settings.modify.system), subject=unix-process[pid=1369566, uid=0, start=18908113] (succeeding for root) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4042] auth: call[38]: completed: authorized=1, challenge=0 (simulated) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4042] settings: add-connection: failed to add a4e6f563-eb2a-41ff-bc23-986ee3438ed9/'mywifi_2G': settings plugin does not support adding connections Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4061] keyfile: commit: a4e6f563-eb2a-41ff-bc23-986ee3438ed9 (mywifi_2G) failed to add: error writing to file '/etc/NetworkManager/system-connections/mywifi_2G.nmconnection': failed to create file /etc/NetworkManager/system-connections/mywifi_2G.nmconnection.ZE5DY0: Read-only file system Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4062] settings: add-connection: failed to add a4e6f563-eb2a-41ff-bc23-986ee3438ed9/'mywifi_2G': error writing to file '/etc/NetworkManager/system-connections/mywifi_2G.nmconnection': failed to create file /etc/NetworkManager/system-connections/mywifi_2G.nmconnection.ZE5DY0: Read-only file system Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4062] active-connection[0x56274f6f0a60]: Failed to activate '(null)': failure adding connection: settings plugin does not support adding connections Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4062] active-connection[0x56274f6f0a60]: set state deactivated (was unknown) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4063] active-connection[0x56274f6f0a60]: check-master-ready: not signalling (state deactivated, no master) Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4063] device[d62304f9da70d783] (wlp61s0): remove_pending_action (0): 'activation-5' Feb 01 20:56:04 laptop NetworkManager[1368510]: [1612230964.4066] audit: socket created Feb 01 20:56:04 laptop
[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution
Not sure if this helps, but we recently added behavior to wait for an apt lock when doing apt commands. This will be included in our next release: https://github.com/canonical/cloud-init/pull/1034 If there are still remaining issues, please open a new bug rather than commenting here. This bug won't be re-opened. -- 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/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution Status in APT: Fix Released Status in cloud-init: Fix Released Status in apt package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Yakkety: Won't Fix Status in cloud-init source package in Zesty: Fix Released Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] A cloud-config that contains packages to install (see below) or 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a result of contention with the apt-daily.service that updates that information. Cloud-config showing the problem is just like: $ cat my.yaml #cloud-config packages: ['hello'] [Test Case] lxc-proposed-snapshot is https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot It publishes an image to lxd with proposed enabled and cloud-init upgraded. a.) launch an instance with proposed version of cloud-init and some user-data. This is platform independent. The test case demonstrates lxd. $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ "package_upgrade: true" > config.yaml $ release=xenial $ ref=proposed-$release $ ./lxc-proposed-snapshot --proposed --publish $release $ref; b.) start the instance $ name=$release-1693361 $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) $ sleep 1 $ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log # watch this boot. c.) Look for evidence of systemd failure journalctl -o short-precise | grep -i break journalctl -o short-precise | grep -i order [Regression Potential] Regression chance here is low. Its possible that ordering loops could occur. When that does happen, journalctl will mention it. Unfortunately in such cases systemd somewhat randomly picks a service to kil so behavior is somewhat undefined. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11121fe4 === End SRU Template === apt-daily is now a systemd service rather than being invoked by cron.daily. If one builds a custom AMI it is possible that the apt- daily.timer will fire during boot. This can fire at the same time cloud-init is running and if cloud-init loses the race the invocation of apt (e.g. use of "packages:" in the config) will fail. There is a lot of discussion online about this change to apt-daily (e.g. unattended upgrades happening during business hours, delaying boot, etc.) and discussion of potential systemd changes regarding timers firing during boot (c.f. https://github.com/systemd/systemd/issues/5659). While it would be better to solve this in apt itself, I suggest that cloud-init be defensive when calling apt and implement some retry mechanism. Various instances of people running into this issue: https://github.com/chef/bento/issues/609 https://clusterhq.atlassian.net/browse/FLOC-4486 https://github.com/boxcutter/ubuntu/issues/73 https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1693361/+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 1952477] Re: unable to compile gtk+3.0-3.24.30 on 21.10
Trying in a fresh pbuilder environment using dpkg-buildpackage the build finish without error, could you share details on which tests are failing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1952477 Title: unable to compile gtk+3.0-3.24.30 on 21.10 Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Have Ubuntu 21.10 installed 2. Enable source code repositories 3. Get updates, get source to compile sudo apt-get update sudo apt-get build-dep apt-get source -b gtk+3.0 Expected results: * compiled successful Actual results: * not compiled, shows errors: PASS: test-settings make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite/tools' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite/tools' make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make check-local make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[3]: *** [Makefile:547: check-recursive] Error 1 make[3]: Target 'check' not remade because of errors. make[3]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' Making check in examples make[3]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples' Making check in bp make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/bp' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/bp' Making check in application1 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application1' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application1' Making check in application2 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' Making check in application3 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' Making check in application4 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' Making check in application5 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' Making check in application6 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' Making check in application7 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' make[5]: Nothing to be
[Touch-packages] [Bug 1952477] Re: unable to compile gtk+3.0-3.24.30 on 21.10
sudo apt-get update sudo apt-get build-dep apt-get source -b gtk+3.0 fails, what else do you need? ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1952477 Title: unable to compile gtk+3.0-3.24.30 on 21.10 Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 21.10 installed 2. Enable source code repositories 3. Get updates, get source to compile sudo apt-get update sudo apt-get build-dep apt-get source -b gtk+3.0 Expected results: * compiled successful Actual results: * not compiled, shows errors: PASS: test-settings make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite/tools' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite/tools' make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make check-local make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[3]: *** [Makefile:547: check-recursive] Error 1 make[3]: Target 'check' not remade because of errors. make[3]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' Making check in examples make[3]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples' Making check in bp make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/bp' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/bp' Making check in application1 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application1' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application1' Making check in application2 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' Making check in application3 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' Making check in application4 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' Making check in application5 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' Making check in application6 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' Making check in application7 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7'
[Touch-packages] [Bug 1950193] Re: libqt5svg5 affected by CVE-2021-38593
Thank you picking this up Dmitry and sorry for not replying earlier. Anything I can do now to help this arrive in 20.04? -- 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/1950193 Title: libqt5svg5 affected by CVE-2021-38593 Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593: https://nvd.nist.gov/vuln/detail/CVE-2021-38593 Trying to open the attached svg file will block one core at 100% and occupy much memory. Depending on the configuration, it might even run out of memory and crash. This is fixed upstream by: https://codereview.qt-project.org/c/qt/qtbase/+/377942 The original issue is public since July 29th. If I'm allowed to upload further files, I'll send a simple test program. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libqt5svg5 5.12.8-0ubuntu1 ProcVersionSignature: Ubuntu 5.14.0-1005.5-oem 5.14.9 Uname: Linux 5.14.0-1005-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 8 20:24:34 2021 InstallationDate: Installed on 2012-07-06 (3411 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: qtsvg-opensource-src UpgradeStatus: Upgraded to focal on 2020-10-03 (400 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1953394] [NEW] Last installed drivers don't work
Public bug reported: I install last updates from Ubuntu update, and after installation I can't log in to Ubuntu, I see black screen and after that there is a redirect to the form of authorization ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Mon Dec 6 22:43:22 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22a4] InstallationDate: Installed on 2021-11-30 (6 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20TRS1KL00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 11/08/2021 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET43W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TRS1KL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN30ET43W(1.26):bd11/08/2021:br1.26:efr1.16:svnLENOVO:pn20TRS1KL00:pvrThinkPadP15vGen1:skuLENOVO_MT_20TR_BU_Think_FM_ThinkPadP15vGen1:rvnLENOVO:rn20TRS1KL00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P15v Gen 1 dmi.product.name: 20TRS1KL00 dmi.product.sku: LENOVO_MT_20TR_BU_Think_FM_ThinkPad P15v Gen 1 dmi.product.version: ThinkPad P15v Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-11-30T14:17:13.277812 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1953394 Title: Last installed drivers don't work Status in xorg package in Ubuntu: New Bug description: I install last updates from Ubuntu update, and after installation I can't log in to Ubuntu, I see black screen and after that there is a redirect to the form of authorization ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Mon Dec 6 22:43:22 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22a4] InstallationDate: Installed on 2021-11-30 (6 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20TRS1KL00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 11/08/2021 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET43W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TRS1KL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset
[Touch-packages] [Bug 1952477] Re: unable to compile gtk+3.0-3.24.30 on 21.10
Can't Ctrl+Shift+A and copy the whole terminal output because of bug 1922276. It is unacceptable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1952477 Title: unable to compile gtk+3.0-3.24.30 on 21.10 Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 21.10 installed 2. Enable source code repositories 3. Get updates, get source to compile sudo apt-get update sudo apt-get build-dep gtk+3.0 apt-get source -b gtk+3.0 Expected results: * compiled successful Actual results: * not compiled, shows errors: PASS: test-settings make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite/tools' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite/tools' make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make check-local make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' make[3]: *** [Makefile:547: check-recursive] Error 1 make[3]: Target 'check' not remade because of errors. make[3]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/testsuite' Making check in examples make[3]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples' Making check in bp make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/bp' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/bp' Making check in application1 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application1' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application1' Making check in application2 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application2' Making check in application3 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application3' Making check in application4 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application4' Making check in application5 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application5' Making check in application6 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' make[4]: Leaving directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application6' Making check in application7 make[4]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' /usr/bin/glib-compile-schemas . No schema files found: doing nothing. make check-am make[5]: Entering directory '/home/i/gtk+3.0-3.24.30/debian/build/deb/examples/application7' make[5]: Nothing to be done for 'check-am'. make[5]: Leaving directory
[Touch-packages] [Bug 1953394] Re: Last installed drivers don't work
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- 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/1953394 Title: Last installed drivers don't work Status in xorg package in Ubuntu: New Bug description: I install last updates from Ubuntu update, and after installation I can't log in to Ubuntu, I see black screen and after that there is a redirect to the form of authorization ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Mon Dec 6 22:43:22 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22a4] InstallationDate: Installed on 2021-11-30 (6 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20TRS1KL00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 11/08/2021 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET43W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TRS1KL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN30ET43W(1.26):bd11/08/2021:br1.26:efr1.16:svnLENOVO:pn20TRS1KL00:pvrThinkPadP15vGen1:skuLENOVO_MT_20TR_BU_Think_FM_ThinkPadP15vGen1:rvnLENOVO:rn20TRS1KL00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P15v Gen 1 dmi.product.name: 20TRS1KL00 dmi.product.sku: LENOVO_MT_20TR_BU_Think_FM_ThinkPad P15v Gen 1 dmi.product.version: ThinkPad P15v Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-11-30T14:17:13.277812 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1953394/+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 1952107] Please test proposed package
Hello Yeshayohu, or anyone else affected, Accepted evolution-data-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evolution-data- server/3.36.5-0ubuntu2 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, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Committed Status in evolution-data-server source package in Impish: Fix Committed Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1952107] Re: Google Contacts API Deprecated
Hello Yeshayohu, or anyone else affected, Accepted evolution into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evolution/3.36.5-0ubuntu2 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, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: evolution (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal ** Changed in: evolution-data-server (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Unknown Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Focal: Fix Committed Status in evolution-data-server source package in Focal: Fix Committed Status in evolution source package in Impish: Fix Committed Status in evolution-data-server source package in Impish: Fix Committed Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume
find a lenovo machine which has legacy hda audio desgin, install 21.10 and run dist-upgrade, enable the -proposed channel in the /etc/apt/sources.list and run sudo apt-get update, then run sudo apt install pulseaudio, the puseaudio 1:15.0+dfsg1-1ubuntu2.2 is installed. reboot, plug a hdmi monitor, manually select it to be active output, keep the hdmi monotor plugged and reboot, after reboot checking the active output device, it is still the hdmi audio, then run suspend and resume, check the active output device, it is still hdmi audio. Verification done on impish. ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1951667 Title: [SRU] pulseaudio: restore hdmi audio be active output after resume Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Hirsute: Won't Fix Status in pulseaudio source package in Impish: Fix Committed Status in pulseaudio source package in Jammy: Fix Released Bug description: [Impact] On the machines with legacy HDA audio driver, when users plug a hdmi/dp monitor, the active output device is still speaker, need users to manually select the hdmi, then the hdmi audio will be the users' preference, once it is plugged, it should become the active output automatically. But with the current PA, after reboot and suspend/resume, the hdmi can't change to be active output automatically anymore. [Fix] Backport an upstream fix, this will fix the issue of "preferred ports being cleaned by a mistake" [Test] On a machine with legacy HDA audio driver, install the patched pulseaudio, then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi audio to be active, with the hdmi monitor plugged and reboot, suspend and resume, check what is the active output, it is still the hdmi audio. [Where problems could occur] This patch is in the card-restore.c, if it could introduce regression, it will be on the default active input/output devices, for example, users select a input or output device to be active, after reboot, if those devices are available, they should be active, but they could be replaced by other devices if a regression is introduced. But this possibility is very low since we tested the patch on a couple of desktop and laptop machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951667/+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 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume
This bug was fixed in the package pulseaudio - 1:15.0+dfsg1-1ubuntu6 --- pulseaudio (1:15.0+dfsg1-1ubuntu6) jammy; urgency=medium * debian/control: build-depends on doxygen -- Sebastien Bacher Wed, 24 Nov 2021 10:10:01 +0100 ** Changed in: pulseaudio (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1951667 Title: [SRU] pulseaudio: restore hdmi audio be active output after resume Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Hirsute: Won't Fix Status in pulseaudio source package in Impish: Fix Committed Status in pulseaudio source package in Jammy: Fix Released Bug description: [Impact] On the machines with legacy HDA audio driver, when users plug a hdmi/dp monitor, the active output device is still speaker, need users to manually select the hdmi, then the hdmi audio will be the users' preference, once it is plugged, it should become the active output automatically. But with the current PA, after reboot and suspend/resume, the hdmi can't change to be active output automatically anymore. [Fix] Backport an upstream fix, this will fix the issue of "preferred ports being cleaned by a mistake" [Test] On a machine with legacy HDA audio driver, install the patched pulseaudio, then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi audio to be active, with the hdmi monitor plugged and reboot, suspend and resume, check what is the active output, it is still the hdmi audio. [Where problems could occur] This patch is in the card-restore.c, if it could introduce regression, it will be on the default active input/output devices, for example, users select a input or output device to be active, after reboot, if those devices are available, they should be active, but they could be replaced by other devices if a regression is introduced. But this possibility is very low since we tested the patch on a couple of desktop and laptop machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951667/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
Regression test results: (1) Test passed with Lenovo T14s (Tiger-2) on Hirsute: * The version of the packages tested: ModemManager: 1.16.6-2~21.04.1 (2) Test passed with Lenovo X13 AMD (Servel-AMD-1) on Focal: * The version of the packages tested: ModemManager: 1.16.6-2~20.04.1 The detail testing procedure and result is provided as the attached file : "RegressionTestReportFor-proposedPackages-1946096.pdf" ** Attachment added: "RegressionTestReportFor-proposedPackages-1946096.pdf" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5545834/+files/RegressionTestReportFor-proposedPackages-1946096.pdf.pdf ** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Focal: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the modem is working 4. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 5. Using the firmware upgrading application to upgrade the modem’s firmware 6. Verify if the modem’s firmware upgrading is successful 7. Reboot 8. Verify if the upgraded modem firmware is still working --- Regression test --- Verify if one USB modem are still working with these patches for PCIe modems. [Where problems could occur] The requested update has 2 parts: 1. Informative 1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually 2. Changes are specific to Foxconn and Quectel modems 2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) In current Ubuntu's certification records for modem: * No other modem uses WWAN subsystem in kernel 5.13 * Modem's FW update is not supported via ModemManager ( < v1.18 ) There is no certificated modems can do the firmware upgrading flow for the regression test. This update should not affect existing modems. The problem would be limited to these two mentioned modems. Each carrier mapping .conf file is for a specific modem. ModemManager will load one of the carrier mapping conf files via the modem manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.) We cannot verify if the carrier mapping is correct. This relies on the manufacturer to provide the correct mapping. The carrier mapping .conf files is verified by modem’s manufacture according to the tested SIM card published by different countries. Modem manufacturer confirmed that the content in the .conf file is absolutely correct. [Other Info] The firmware and the upgrading utilities can be downloaded from the
[Touch-packages] [Bug 1946213] Re: strongswan: Fail to build against OpenSSL 3.0
This bug was fixed in the package openssl - 3.0.0-1ubuntu1 --- openssl (3.0.0-1ubuntu1) jammy; urgency=medium * Manual merge of version 3.0.0-1 from Debian experimental, remaining changes: - Replace duplicate files in the doc directory with symlinks. - debian/libssl1.1.postinst: + Display a system restart required notification on libssl1.1 upgrade on servers, unless needrestart is available. + Use a different priority for libssl1.1/restart-services depending on whether a desktop, or server dist-upgrade is being performed. + Skip services restart & reboot notification if needrestart is in-use. + Bump version check to to 1.1.1. + Import libraries/restart-without-asking template as used by above. - Revert "Enable system default config to enforce TLS1.2 as a minimum" & "Increase default security level from 1 to 2". - Reword the NEWS entry, as applicable on Ubuntu. - Set OPENSSL_TLS_SECURITY_LEVEL=2 as compiled-in minimum security level. Change meaning of SECURITY_LEVEL=2 to prohibit TLS versions below 1.2 and update documentation. Previous default of 1, can be set by calling SSL_CTX_set_security_level(), SSL_set_security_level() or using ':@SECLEVEL=1' CipherString value in openssl.cfg. - Add support for building with noudeb build profile. * d/p/Don-t-create-an-ECX-key-with-short-keys.patch: Backported from upstream to fix a regression with short keys (LP: #1946213) * d/p/Add-null-digest-implementation-to-the-default-provid.patch: Backported from upstream to fix a compatibility issue with 1.1.1l * Manually call dh_installdirs to fix build failure * Drop some Ubuntu patches merged upstream + The s390x series (00xx) has been applied upstream + The lp-1927161 Intel CET series has been applied upstream + CVE-2021-3449 has been fixed upstream + CVE-2021-3450 doesn't apply to 3.0 branch * Refresh and adapt the remaining patches openssl (3.0.0-1) experimental; urgency=medium * Import 3.0.0. * Add avr32, patch by Vineet Gupta (Closes: #989442). openssl (3.0.0~~beta2-1) experimental; urgency=medium * Import 3.0.0-beta2. openssl (3.0.0~~beta1-1) experimental; urgency=medium * Import 3.0.0-beta1. * Use HARNESS_VERBOSE again (otherwise the test suite might killed since no progress is visible). openssl (3.0.0~~alpha16-1) experimental; urgency=medium * Import 3.0.0-alpha16. * Use VERBOSE_FAILURE to log only failures in the build log. openssl (3.0.0~~alpha15-1) experimental; urgency=medium * Import 3.0.0-alpha15. openssl (3.0.0~~alpha13-2) experimental; urgency=medium * Add a proposed patch from upstream to skip negativ errno number in the testsuite to pass the testsute on hurd. * Always link against libatomic. openssl (3.0.0~~alpha13-1) experimental; urgency=medium * Import 3.0.0-alpha13. * Move configuration.h to architecture specific include folder. Patch from Antonio Terceiro (Closes: #98). * Enable LFS. Thanks to Dan Nicholson for debugging (Closes: #923479). * drop `lsof', the testsuite is not using it anymore. * Enable ktls. openssl (3.0.0~~alpha4-1) experimental; urgency=medium * Import 3.0.0-alpha4. * Add `lsof' which is needed by the test suite. * Add ossl-modules to libcrypto's udeb. openssl (3.0.0~~alpha3-1) experimental; urgency=medium * Import 3.0.0-alpha3 * Install the .so files only in the -dev package (Closes: #962548). openssl (3.0.0~~alpha1-1) experimental; urgency=medium * Import 3.0.0-alpha1 (Closes: #934836). -- Simon Chopin Mon, 20 Sep 2021 18:09:50 +0200 ** Changed in: openssl (Ubuntu) Status: Invalid => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3449 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3450 -- 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/1946213 Title: strongswan: Fail to build against OpenSSL 3.0 Status in OpenSSL: Fix Released Status in strongSwan: New Status in openssl package in Ubuntu: Fix Released Status in strongswan package in Ubuntu: Fix Released Bug description: Hello, As part of a rebuild against OpenSSL3, this package failed to build on one or several architectures. You can find the details of the rebuild at https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html or for the amd64 failed build, directly at https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22099394/+files/buildlog_ubuntu- impish-amd64.strongswan_5.9.1-1ubuntu3.0~ssl3ppa1.1_BUILDING.txt.gz We're planning to transition to OpenSSL 3.0 for the 22.04 release, and consider this issue as blocking for this transition. You can find general migration informations at
[Touch-packages] [Bug 1951943] Re: Engine crashes when loading the configuration more than once
What is the plan for fixing this in Jammy (which has a version lower than the version in impish-proposed)? -- 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/1951943 Title: Engine crashes when loading the configuration more than once Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Bionic: Fix Committed Status in openssl source package in Focal: Fix Committed Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: Fix Committed Status in openssl source package in Jammy: Confirmed Bug description: [Impact] * Engine crashes when loading the configuration more than once * Upstream started to avoid loading engines twice by using dynamic ids to track the loaded engines correctly * OpenSSL 3 https://github.com/openssl/openssl/commit/81c11349c2a0e945aa3dfc6bd81c957363dd2011 (bugfix) https://github.com/openssl/openssl/commit/38e2957249c90317a26a080c7e7eb186dd5b6598 (test case) * OpenSSL 1.1.1 backports: https://github.com/openssl/openssl/commit/9b06ebb1edfddffea083ba36090af7eb7cad207b (bugfix) https://github.com/openssl/openssl/pull/17083 (test case) [Test Plan] * https://github.com/openssl/openssl/issues/17023 lists multiple ways how one can trigger the issue at hand, but also test case implements this issue too by explicitly attempting to load an engine multiple times and checking that it is operational. The test a is run during the build as part of the upstream regression test suite, for the shared library build (as static build does not support engines), so you'll see one pass and one skip in the log. [Where problems could occur] * Separately we have started to fix userspace packages that needlessly load configuration files multiple times, which used to trigger this issue. The codepaths changed are with engine use, how they are loaded/unloaded/used. It is possible that this fix will make some engines to start working and be used resulting in new behaviour. But also exposing bugs in the engines that previously were installed & configured but not actually used. [Other Info] * Previous bug reports about this issues are: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518 https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951943/+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 1953394] Re: Last installed drivers don't work
Thanks for the bug report. Please attach a video of the problem so we can better understand what kind of problem you are experiencing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1953394 Title: Last installed drivers don't work Status in Ubuntu: Incomplete Bug description: I install last updates from Ubuntu update, and after installation I can't log in to Ubuntu, I see black screen and after that there is a redirect to the form of authorization ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Mon Dec 6 22:43:22 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22a4] InstallationDate: Installed on 2021-11-30 (6 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 20TRS1KL00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 11/08/2021 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET43W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TRS1KL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN30ET43W(1.26):bd11/08/2021:br1.26:efr1.16:svnLENOVO:pn20TRS1KL00:pvrThinkPadP15vGen1:skuLENOVO_MT_20TR_BU_Think_FM_ThinkPadP15vGen1:rvnLENOVO:rn20TRS1KL00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P15v Gen 1 dmi.product.name: 20TRS1KL00 dmi.product.sku: LENOVO_MT_20TR_BU_Think_FM_ThinkPad P15v Gen 1 dmi.product.version: ThinkPad P15v Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-11-30T14:17:13.277812 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1953394/+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 1953297] Re: unmkinitramfs does not work on arm64
Sorry false alarm. The initrd I use to test is from arm64 live ISO and it is compressed by zstd which not installed. With zstd installed unmkinitramfs works fine too. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/1953297 Title: unmkinitramfs does not work on arm64 Status in initramfs-tools package in Ubuntu: Invalid Bug description: unmkinitramfs in initramfs-tools-core works fine on amd64 but same command fails on arm64 On amd64: $ unmkinitramfs initrd temp $ ls temp early early2 main On arm64: $ unmkinitramfs initrd temp cpio: premature end of archive $ ls temp $ The tested unmkinitramfs is 0.136ubuntu6.6 in focal-update archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1953297/+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 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd
** Also affects: initramfs-tools (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: initramfs-tools (Ubuntu Impish) Importance: Undecided Status: New -- 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/1950214 Title: raspi 64 bit Impish image fails update-initramfs with OOM on zstd Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools source package in Impish: New Status in initramfs-tools source package in Jammy: Confirmed Bug description: When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish image and nothing new installed to it, update-initramfs fails like so: Setting up linux-firmware (1.201.1) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 A simple workaround for now is to switch to the old lz4 default: $ sudo apt install lz4 $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' /etc/initramfs-tools/initramfs.conf Original Workaround === Adding a swap file to the setup allowed 'apt -f install' to run successfully. How the device was setup 1) xzcat | dd the sdcard with the impish 64 bit server image 2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, link getty@ttyGS0.service ) as suggested in https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console 3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest of the 16GB flash, e2fsck, resize2fs 4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html 5) boot, connect to wireless, ssh in 6) apt update && apt upgrade 7) observe above issue ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.201.1 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 19:47 seq crw-rw 1 root audio 116, 33 Nov 8 19:47 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-1009-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Mon Nov 8 21:00:59 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20211013 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PackageArchitecture: all PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash modules-load=dwc2,g_serial Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 bcm2835_codec vc_sm_cma Title: package linux-firmware 1.201.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950214/+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 1953301] Re: Segfault on AArch64 caused by OpenSSL affecting numerous packages
** Information type changed from Private Security to Public Security -- 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/1953301 Title: Segfault on AArch64 caused by OpenSSL affecting numerous packages Status in openssl package in Ubuntu: New Bug description: OpenSSL causes crashes when reaching to some URLs on AArch64 platform, affecting Ubuntu, but not Fedora for instance. Initially reported in https://mediasoup.discourse.group/t/mediasoup- worker-default-make-failed/3647/12, more details and reproductions in https://github.com/mesonbuild/meson/issues/9690 Affects curl, wget, python and probably everything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1953301/+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 1953428] [NEW] /etc/PackageKit/Vendor.conf specifies invalid CodecUrl
Public bug reported: CodecUrl in /etc/PackageKit/Vendor.conf on Impish at least currently has: http://shop.canonical.com/index.php?cPath=19=f1e370ea7563ed5e654c10450364ff24 shop.canonical.com does not have a DNS record and has been dead for a long time so this should be removed. ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1953428 Title: /etc/PackageKit/Vendor.conf specifies invalid CodecUrl Status in packagekit package in Ubuntu: New Bug description: CodecUrl in /etc/PackageKit/Vendor.conf on Impish at least currently has: http://shop.canonical.com/index.php?cPath=19=f1e370ea7563ed5e654c10450364ff24 shop.canonical.com does not have a DNS record and has been dead for a long time so this should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1953428/+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 1953301] Re: Segfault on AArch64 caused by OpenSSL affecting numerous packages
FWIW I can't reproduce this on a RPi 4 running the aarch64/arm64 Ubuntu 20.04 LTS image: ubuntu@rpi4:~$ wget https://wrapdb.mesonbuild.com/v2/libuv_1.42.0-1/get_patch --2021-12-07 05:50:01-- https://wrapdb.mesonbuild.com/v2/libuv_1.42.0-1/get_patch Resolving wrapdb.mesonbuild.com (wrapdb.mesonbuild.com)... 138.201.247.118 Connecting to wrapdb.mesonbuild.com (wrapdb.mesonbuild.com)|138.201.247.118|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://github.com/mesonbuild/wrapdb/releases/download/libuv_1.42.0-1/libuv_1.42.0-1_patch.zip [following] --2021-12-07 05:50:03-- https://github.com/mesonbuild/wrapdb/releases/download/libuv_1.42.0-1/libuv_1.42.0-1_patch.zip Resolving github.com (github.com)... 13.236.229.21 Connecting to github.com (github.com)|13.236.229.21|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://objects.githubusercontent.com/github-production-release-asset-2e65be/236250352/46c49bec-514b-4411-afe8-46ac8cb2e82f?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAIWNJYAX4CSVEH53A%2F20211207%2Fus-east-1%2Fs3%2Faws4_request=20211207T054758Z=300=504c83b4d0c3567dc2f509362714a5b5709951655612c5665ca7d3e1f09050c5=host_id=0_id=0_id=236250352=attachment%3B%20filename%3Dlibuv_1.42.0-1_patch.zip=application%2Foctet-stream [following] --2021-12-07 05:50:03-- https://objects.githubusercontent.com/github-production-release-asset-2e65be/236250352/46c49bec-514b-4411-afe8-46ac8cb2e82f?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAIWNJYAX4CSVEH53A%2F20211207%2Fus-east-1%2Fs3%2Faws4_request=20211207T054758Z=300=504c83b4d0c3567dc2f509362714a5b5709951655612c5665ca7d3e1f09050c5=host_id=0_id=0_id=236250352=attachment%3B%20filename%3Dlibuv_1.42.0-1_patch.zip=application%2Foctet-stream Resolving objects.githubusercontent.com (objects.githubusercontent.com)... 185.199.110.133, 185.199.108.133, 185.199.109.133, ... Connecting to objects.githubusercontent.com (objects.githubusercontent.com)|185.199.110.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 5146 (5.0K) [application/octet-stream] Saving to: ‘get_patch’ get_patch 100%[=>] 5.03K --.-KB/sin 0.009s 2021-12-07 05:50:04 (590 KB/s) - ‘get_patch’ saved [5146/5146] ubuntu@rpi4:~$ dpkg -l openssl Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=-- ii openssl1.1.1f-1ubuntu2.9 arm64Secure Sockets Layer toolkit - cryptographic utility ubuntu@rpi4:~$ uname -a Linux rpi4 5.4.0-1047-raspi #52-Ubuntu SMP PREEMPT Wed Nov 24 08:16:38 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Can you please provide more details on what hardware platform is being used in your case and what Ubuntu version / openssl version is in use? The meson github issue appears to mention Ubuntu 20.04 but some more details would be useful. ** Changed in: openssl (Ubuntu) Status: New => Incomplete -- 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/1953301 Title: Segfault on AArch64 caused by OpenSSL affecting numerous packages Status in openssl package in Ubuntu: Incomplete Bug description: OpenSSL causes crashes when reaching to some URLs on AArch64 platform, affecting Ubuntu, but not Fedora for instance. Initially reported in https://mediasoup.discourse.group/t/mediasoup- worker-default-make-failed/3647/12, more details and reproductions in https://github.com/mesonbuild/meson/issues/9690 Affects curl, wget, python and probably everything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1953301/+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 1946209] Re: evolution-alarm-notify crashed with signal 5 in _XEventsQueued()
[Expired for evolution-data-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evolution-data-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1946209 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() Status in evolution-data-server package in Ubuntu: Expired Bug description: Crashes when going to system setting / Graphic tablet / manually register a tablet / select Multi-device tablet pen sensor => crash ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: evolution-data-server 3.40.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: KDE Date: Wed Oct 6 10:32:24 2021 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify Signal: 5 SourcePackage: evolution-data-server StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to impish on 2021-10-03 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo uinput separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1946209/+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 1953301] Re: Segfault on AArch64 caused by OpenSSL affecting numerous packages
Not sure why it doesn't reproduce on RPi 4, but I guess as described on GitHub, might be because of assembly instructions that work on RPi 4 and not in some virtualized environments (both binfmt and Docker under macOS M1 are virtualization technologies). This is on my x86-64 Linux system: nazar-pc@nazar-pc:~> docker run --rm -it -u root --platform linux/arm64 ubuntu:20.04 root@6fbdb0317cd7:/# apt-get update Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages [11.1 MB] Get:6 http://ports.ubuntu.com/ubuntu-ports focal/restricted arm64 Packages [1317 B] Get:7 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages [139 kB] Get:8 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages [1234 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe arm64 Packages [1036 kB] Get:10 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 Packages [9055 B] Get:11 http://ports.ubuntu.com/ubuntu-ports focal-updates/restricted arm64 Packages [3529 B] Get:12 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages [1244 kB] Get:13 http://ports.ubuntu.com/ubuntu-ports focal-backports/universe arm64 Packages [21.6 kB] Get:14 http://ports.ubuntu.com/ubuntu-ports focal-backports/main arm64 Packages [50.0 kB] Get:15 http://ports.ubuntu.com/ubuntu-ports focal-security/restricted arm64 Packages [3291 B] Get:16 http://ports.ubuntu.com/ubuntu-ports focal-security/main arm64 Packages [871 kB] Get:17 http://ports.ubuntu.com/ubuntu-ports focal-security/multiverse arm64 Packages [3242 B] Get:18 http://ports.ubuntu.com/ubuntu-ports focal-security/universe arm64 Packages [759 kB] Fetched 17.1 MB in 6s (3070 kB/s) Reading package lists... Done root@6fbdb0317cd7:/# apt-get install -y --no-install-recommends ca-certificates curl Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libasn1-8-heimdal libbrotli1 libcurl4 libgssapi-krb5-2 libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal libk5crypto3 libkeyutils1 libkrb5-26-heimdal libkrb5-3 libkrb5support0 libldap-2.4-2 libldap-common libnghttp2-14 libpsl5 libroken18-heimdal librtmp1 libsasl2-2 libsasl2-modules-db libsqlite3-0 libssh-4 libssl1.1 libwind0-heimdal openssl Suggested packages: krb5-doc krb5-user Recommended packages: krb5-locales publicsuffix libsasl2-modules The following NEW packages will be installed: ca-certificates curl libasn1-8-heimdal libbrotli1 libcurl4 libgssapi-krb5-2 libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal libk5crypto3 libkeyutils1 libkrb5-26-heimdal libkrb5-3 libkrb5support0 libldap-2.4-2 libldap-common libnghttp2-14 libpsl5 libroken18-heimdal librtmp1 libsasl2-2 libsasl2-modules-db libsqlite3-0 libssh-4 libssl1.1 libwind0-heimdal openssl 0 upgraded, 29 newly installed, 0 to remove and 0 not upgraded. Need to get 4891 kB of archives. After this operation, 15.1 MB of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 libssl1.1 arm64 1.1.1f-1ubuntu2.9 [1157 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 openssl arm64 1.1.1f-1ubuntu2.9 [599 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 ca-certificates all 20210119~20.04.2 [145 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 libsqlite3-0 arm64 3.31.1-4ubuntu0.2 [507 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 libkrb5support0 arm64 1.17-6ubuntu4.1 [30.4 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 libk5crypto3 arm64 1.17-6ubuntu4.1 [80.4 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 libkeyutils1 arm64 1.6-6ubuntu1 [10.1 kB] Get:8 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 libkrb5-3 arm64 1.17-6ubuntu4.1 [312 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 libgssapi-krb5-2 arm64 1.17-6ubuntu4.1 [113 kB] Get:10 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 libpsl5 arm64 0.21.0-1ubuntu1 [51.3 kB] Get:11 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 libbrotli1 arm64 1.0.7-6ubuntu0.1 [257 kB] Get:12 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 libroken18-heimdal arm64 7.7.0+dfsg-1ubuntu1 [39.4 kB] Get:13 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 libasn1-8-heimdal arm64 7.7.0+dfsg-1ubuntu1 [150 kB] Get:14 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 libheimbase1-heimdal arm64
