[Touch-packages] [Bug 1834333] Re: Scaling problem with Qt apps
This may be relate to bug 1824753 ** Package changed: gnome-control-center (Ubuntu) => qtbase-opensource- src (Ubuntu) ** Changed in: qtbase-opensource-src (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1834333 Title: Scaling problem with Qt apps Status in qtbase-opensource-src package in Ubuntu: New Bug description: Hi I have problem with scaling for Qt apps. when i open Kolourpaint scaling is too small i have Ubuntu 18.04 and install from snap and apt i first report to bugs.kde.org and they tell me to report here https://bugs.kde.org/show_bug.cgi?id=407668 Kolourpaint its not only app with problem , anydesk , filezilla , pylon viewer , dukto , stacer , vmware horizon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1834333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834333] [NEW] Scaling problem with Qt apps
You have been subscribed to a public bug: Hi I have problem with scaling for Qt apps. when i open Kolourpaint scaling is too small i have Ubuntu 18.04 and install from snap and apt i first report to bugs.kde.org and they tell me to report here https://bugs.kde.org/show_bug.cgi?id=407668 Kolourpaint its not only app with problem , anydesk , filezilla , pylon viewer , dukto , stacer , vmware horizon ** Affects: qtbase-opensource-src (Ubuntu) Importance: Low Status: New ** Tags: hidpi qt scaling -- Scaling problem with Qt apps https://bugs.launchpad.net/bugs/1834333 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833527] Re: in gnome settings audio section does not see any sound card
Thanks Daniel, I have reported another bug with the same issue this time with alsa running. https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1815526 solution is exactly the same -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1833527 Title: in gnome settings audio section does not see any sound card Status in pulseaudio package in Ubuntu: Incomplete Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 12:28:49 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827879] Re: Killer Wireless 1525 firmware crashes on suspend
Please run `sudo modprobe -r btusb` before suspend and see if it helps. -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1834400] Re: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed
** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1834400 Title: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed Status in HPLIP: New Status in cups package in Ubuntu: New Bug description: I attempted to print a file on a network printer which was set up via HPLIP. The PC reports that the print job has started and completed on the network printer, but in fact the network printer has not printed anything. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1834400/+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 1834400] [NEW] pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed
Public bug reported: I attempted to print a file on a network printer which was set up via HPLIP. The PC reports that the print job has started and completed on the network printer, but in fact the network printer has not printed anything. ** Affects: hplip Importance: Undecided Status: New ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Attachment added: "troubleshoot.txt" https://bugs.launchpad.net/bugs/1834400/+attachment/5273695/+files/troubleshoot.txt ** Also affects: hplip Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1834400 Title: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed Status in HPLIP: New Status in cups package in Ubuntu: New Bug description: I attempted to print a file on a network printer which was set up via HPLIP. The PC reports that the print job has started and completed on the network printer, but in fact the network printer has not printed anything. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1834400/+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 1834400] Re: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed
** Attachment added: "troubleshoot-logs.txt" https://bugs.launchpad.net/hplip/+bug/1834400/+attachment/5273697/+files/troubleshoot-logs.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1834400 Title: pc reports that HP OfficeJet Pro 8715 printed file, but nothing has printed Status in HPLIP: New Status in cups package in Ubuntu: New Bug description: I attempted to print a file on a network printer which was set up via HPLIP. The PC reports that the print job has started and completed on the network printer, but in fact the network printer has not printed anything. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1834400/+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 1834375] Re: Gaia.com videos unsupported
** Package changed: xorg (Ubuntu) => firefox (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/1834375 Title: Gaia.com videos unsupported Status in firefox package in Ubuntu: New Bug description: Firefox could not play videos on Gaia.com. The error message blamed the browser. So I downloaded and installed the browser Opera, with the same results and message. Both browsers would play Youtube videos. Please enable Gaia.com videos. Thanks. I downloaded the latest Ubuntu release today. 18.04...something ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 26 17:57:24 2019 DistUpgraded: 2019-06-26 11:14:51,559 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] InstallationDate: Installed on 2019-06-25 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=dfa2862a-4da8-414d-9f41-cecde30f67c6 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-06-26 (0 days ago) dmi.bios.date: 06/23/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G2 v02.02 dmi.board.name: 3048h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G2v02.02:bd06/23/2011:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jun 26 10:11:57 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1834375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
By the way, judging by http://autopkgtest.ubuntu.com/running#pkg- systemd-upstream, it seems Ubuntu CI keeps running the tests for PR 12618, which was merged about a month ago. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE | | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 | | updated | 2019-05-16T07:00:42Z | | user_id | 8524250971084851b3792a68fbc398dd
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
Anyway, as I said in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831296/comments/3, I don't think Ubuntu CI in its current form is suitable for CI so I'll just turn it off as soon as it starts failing again. I'm afraid I don't have time for keeping an eye on it and reporting whatever comes up there on bugs.launchpad.net. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE | | tenant_id| afaef86b96dd4828a1ed5ee395ea1421 | | updated | 2019-05-16T07:00:42Z
[Touch-packages] [Bug 1829829] Re: Ubuntu CI has been flaky for a week
I turned on bionic-amd64 and bionic-i386 yesterday. VMs no longer fail to boot but apparently something else was broken on bionic-i386 while it was off: https://github.com/systemd/systemd/issues/12891. In https://github.com/systemd/systemd/pull/12861#issuecomment-506025351 both bionic-amd64 and bionic-s390x failed due to something weird I don't quite understand. It would be great if someone who is interested in keeping it afloat could chime in there to help to debug that. ** Bug watch added: github.com/systemd/systemd/issues #12891 https://github.com/systemd/systemd/issues/12891 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829829 Title: Ubuntu CI has been flaky for a week Status in systemd package in Ubuntu: Confirmed Bug description: It was originally reported in https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days ago. To judge from the logs VMs can't be rebooted there: ``` Ubuntu 18.04.2 LTS autopkgtest ttyS0 autopkgtest login: --- --- nova show 91e76a78-d05c-412a-b383-55a26010ae69 (adt-bionic-amd64-systemd-upstream-20190516-051604) -- +--++ | Property | Value | +--++ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-SRV-ATTR:host | euler | | OS-EXT-SRV-ATTR:hypervisor_hostname | euler.lcy01.scalingstack | | OS-EXT-SRV-ATTR:instance_name| instance-003d216a | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2019-05-16T07:00:42.00 | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | config_drive | | | created | 2019-05-16T07:00:33Z | | flavor | autopkgtest (f878e70e-9991-46e0-ba02-8ea159a71656) | | hostId | 1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd | | id | 91e76a78-d05c-412a-b383-55a26010ae69 | | image| adt/ubuntu-bionic-amd64-server-20190516.img (d00bf12c-467e-433f-a4f5-15720f13bff1) | | key_name | testbed-juju-prod-ues-proposed-migration-machine-11 | | metadata | {} | | name | adt-bionic-amd64-systemd-upstream-20190516-051604 | | net_ues_proposed_migration network | 10.42.40.13 | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | security_groups | autopkgtest@lcy01-27.secgroup | | status | ACTIVE
[Touch-packages] [Bug 1834264] Re: PCI/internal sound card not detected
According to the #17 and you said "it was workig fine until today", it looks like this is a hardware issue. Probably the hardware of audio was broken. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834128] Re: Multiple sshd services cannot be executed
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like the actual bug you're reporting is: > When this happens, other sshd services will fault since the privileged separation directory is no longer there. Please could you provide exact steps to reproduce your "will fault" prediction? Once done, please change the bug status back to New. I'd appreciate the usual "steps to reproduce/expected behaviour/actual behaviour" clearly laid out please. As this is an unusual end-user configuration, I'm marking Importance: Low based on our definitions at https://wiki.ubuntu.com/Bugs/Importance. Please note that this means that after you do reply and assuming that we do agree that the actual behaviour is a bug, I expect that a bug report to Debian will be required but no further action will take place in Ubuntu, save for the possibility of patches to stable releases if a fix does land in the development release via Debian and the patch meets our stable update requirements. I expect that if the fix is to sshd@.service then a local workaround will be trivially possible by overriding that service definition. ** Changed in: openssh (Ubuntu) Status: New => Incomplete ** Changed in: openssh (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1834128 Title: Multiple sshd services cannot be executed Status in openssh package in Ubuntu: Incomplete Bug description: OpenSSH 7.6p1 Ubuntu 18.04.2 (LTS) (Bionic) See also Ticket #1831765, #1690485, and #1832110 regarding the path of the privilege separation directory (aka: /run/sshd). The current Debian installer sets the RuntimeDirectory=sshd (i.e. /run/sshd) in sshd.service (i.e. /lib/systemd/system/sshd.service) and sshd@.service (i.e. /lib/systemd/system/sshd@.service). This is not the best means of implementing this service. The problem is that the systemd deletes the RuntimeDirectory resource as soon as the service is stopped. When this happens, other sshd services will fault since the privileged separation directory is no longer there. We need to modify the configuration as follows: 1) Create /usr/lib/tmpfiles.d/sshd.conf that defines the /run/sshd directory with root:root as the owner and the protection of 0755. 2) Change the assignment of the RuntimeDirectory in sshd.service to something other than sshd (i.e. /run/sshd). 3) Change the assignment of the RuntimeDirectory in sshd@.service to something other than sshd (i.e. /run/sshd). Both OpenSSH and Ubuntu have declined to provision a means of adjusting the Privilege Separation directory. Since both teams do not want to address this, we need to have a means of implementing multiple instance sshd invocation using systemd and avoiding using the RuntimeDirectory assignment of /run/sshd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1834128/+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 1834129] Re: Presence of sshd_config mandatory
Hi Luke, thanks for reporting this issue. Unfortunately, I am not able to reproduce it. Ubuntu 18.04.2 ships openssh-server 1:7.6p1-4ubuntu0.3, not 7.9. Is the version typo'd in the report or are you running a self-installed version of openssh perhaps? In any case, I attempted reproduction on both 18.04 (bionic) and 19.10 (eoan) in lxc, but was not able to reproduce a fault. If you could, please provide an exact set of commands to reproduce, and the error message you encountered. Please also verify you're running the stock distro version of openssh when doing - reproducing in a clean vanilla lxc instance or a fresh installation of ubuntu would be helpful. $ lxc launch ubuntu:18.04/amd64 lp1834129 $ lxc exec lp1834129 bash # apt-get update [...] # ps aux | grep sshd root 685 0.0 0.0 72296 5660 ?Ss 22:31 0:00 /usr/sbin/sshd -D root 687 0.0 0.0 14856 1008 ?S+ 22:31 0:00 grep --color=auto sshd # service sshd stop # ps aux | grep sshd root 718 0.0 0.0 14856 1116 ?S+ 22:31 0:00 grep --color=auto sshd # ls -l /run/ssh* ls: cannot access '/run/ssh*': No such file or directory # touch my_sshd_config # sshd -f ./my_sshd_config sshd re-exec requires execution with an absolute path # /usr/sbin/sshd -f ./my_sshd_config Missing privilege separation directory: /run/sshd # mkdir /run/sshd # /usr/sbin/sshd -f ./my_sshd_config # ps aux | grep sshd root 725 0.0 0.0 72296 3344 ?Ss 22:31 0:00 /usr/sbin/sshd -f ./my_sshd_config root 727 0.0 0.0 14856 1040 ?S+ 22:31 0:00 grep --color=auto sshd # kill 725 # !ps ps aux | grep sshd root 729 0.0 0.0 14856 1004 ?S+ 22:32 0:00 grep --color=auto sshd # mv /etc/ssh/sshd_config /tmp/ # /usr/sbin/sshd -f ./my_sshd_config # !ps ps aux | grep sshd root 732 0.0 0.0 72296 3200 ?Ss 22:32 0:00 /usr/sbin/sshd -f ./my_sshd_config root 734 0.0 0.0 14856 1156 ?S+ 22:32 0:00 grep --color=auto sshd # ls -l /etc/ssh/sshd_* ls: cannot access '/etc/ssh/sshd_*': No such file or directory # passwd ubuntu Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully # su ubuntu To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. $ ssh localhost ubuntu@localhost's password: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. $ logout Connection to localhost closed. $ . /etc/lsb-release && echo ${DISTRIB_DESCRIPTION} Ubuntu 18.04.2 LTS $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 $ apt-cache policy openssh-server | grep Installed Installed: 1:7.6p1-4ubuntu0.3 ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1834129 Title: Presence of sshd_config mandatory Status in openssh package in Ubuntu: Incomplete Bug description: OpenSSH 7.9p1 Ubuntu 18..04.2 (LTS) If a sshd daemon is started with a "-f my_sshd_config" command-line specification the sshd process still requires the existence of the sshd_config. The bug is somewhere in one of the forked processes started when an external client attempts a connection. Since the sshd_config file does not exists, an external client connection cannot be started. Solution: If I "touch /etc/ssh/sshd_config" then the lock-up issue goes away and I am successfully able to login. Bug: If the sshd configuration file is specified in the command line execution of the daeomon, then this should be the only file that should be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1834129/+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 1118446] Re: NetworkManager[14155]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
I want to know which versifon fixed the bug. I installed network-manager 0.9.8.8-0ubuntu7.3 but still occurs this issue. -- 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/1118446 Title: NetworkManager[14155]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted Status in network-manager package in Ubuntu: Fix Released Bug description: I see the following messages in /var/log/syslog: NetworkManager[14155]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted When it goes down, I have to bounce network-manager to resolve it. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.7.995+git201301311547.17123fc-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Thu Feb 7 08:59:00 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-01-26 (12 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IpRoute: default via 10.0.1.1 dev wlan0 proto static 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.11 metric 9 169.254.0.0/16 dev wlan0 scope link metric 1000 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-01-26 (11 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Ubuntuac3b296c-3250-4464-8ee0-ebd6e5d8e9ca 802-11-wireless 1360249035 Thu 07 Feb 2013 08:57:15 AM CSTyes no /org/freedesktop/NetworkManager/Settings/2 Palms 2e5ef890-c77c-466e-92ee-d9dcb777cf12 802-11-wireless 1359750784 Fri 01 Feb 2013 02:33:04 PM CSTyes no /org/freedesktop/NetworkManager/Settings/1 MIA-WiFi ea25a58d-9cb8-48a8-843a-2dc3231a1e17 802-11-wireless 1359754973 Fri 01 Feb 2013 03:42:53 PM CSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.995 connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1118446/+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 1834375] [NEW] Gaia.com videos unsupported
Public bug reported: Firefox could not play videos on Gaia.com. The error message blamed the browser. So I downloaded and installed the browser Opera, with the same results and message. Both browsers would play Youtube videos. Please enable Gaia.com videos. Thanks. I downloaded the latest Ubuntu release today. 18.04...something ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 26 17:57:24 2019 DistUpgraded: 2019-06-26 11:14:51,559 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] InstallationDate: Installed on 2019-06-25 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=dfa2862a-4da8-414d-9f41-cecde30f67c6 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-06-26 (0 days ago) dmi.bios.date: 06/23/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G2 v02.02 dmi.board.name: 3048h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G2v02.02:bd06/23/2011:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jun 26 10:11:57 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1834375 Title: Gaia.com videos unsupported Status in xorg package in Ubuntu: New Bug description: Firefox could not play videos on Gaia.com. The error message blamed the browser. So I downloaded and installed the browser Opera, with the same results and message. Both browsers would play Youtube videos. Please enable Gaia.com videos. Thanks. I downloaded the latest Ubuntu release today. 18.04...something ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 26 17:57:24 2019 DistUpgraded: 2019-06-26 11:14:51,559 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics Controller [103c:3048] InstallationDate: Installed on 2019-06-25 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=dfa2862a-4da8-414d-9f41-cecde30f67c6 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-06-26 (0 days ago) dmi.bios.date: 06/23/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G2 v02.02 dmi.board.name: 3048h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
@mvo @xnox ok, so if I run unfixed systemd and fixed snapd and unfixed initramfs-tools /usr/local/... patch are missing when booting with initramfs: ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo systemd-run --pty --wait /usr/bin/env | grep PATH Running as unit: run-u69.service Press ^] three times within 1s to disconnect TTY. PATH=/sbin:/usr/sbin:/bin:/usr/bin:/snap/bin Finished with result: success Main processes terminated with: code=exited/status=0 Service runtime: 8ms ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l systemd 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 systemd237-3ubuntu10.23 amd64system and service manager ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l snapd 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 snapd 2.37.1+18.04 amd64Daemon and tooling that enable snap packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
@mvo thanks for the test! Nor @xnox or I could reproduce the problem of missing /usr/local/bin and /usr/local/sbin when booting with initramfs. I tried even downgrading snapd to 2.37.1+18.04 and systemd to 237-3ubuntu10.10 with no luck. I seems it is safe to go ahead with the snapd fix, too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834264] Re: PCI/internal sound card not detected
Bluetooth does not work. And after updating the kernel, virtualbox no longer works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1834264 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I don't have any sound. I have followed some online instructions that have not worked. Please help me. My laptop was working just fine until today. I opened it up and there was no sound. If you need further information from me, please provide instructions on how to obtain it. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 25 18:29:31 2019 InstallationDate: Installed on 2019-02-18 (127 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8364 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd02/23/2018:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc0xx dmi.product.sku: 1KU13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-06-25T18:04:58.293034 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827879] Re: Killer Wireless 1525 firmware crashes on suspend
Yes, nothing changed as far as i know, so the issue remains -- 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/1827879 Title: Killer Wireless 1525 firmware crashes on suspend Status in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Problem: Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware) System: Ubuntu 19.04 Kernel 5.0.0-13-generic Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1) Wireless info: description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 20 serial: 40:b8:9a:ca:2b:99 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:f680-f69f My attempts: 1. Tried other kernels: 5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114 2. Tried several distro's based on ubuntu -> all have the same issue 3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest) 4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11 5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly Of course i want to be able to use the 1525, so please help me solve the issue. Happy to perform additional debugging if required. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 1527 F pulseaudio /dev/snd/controlC0: sander 1527 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600 MachineType: Alienware Alienware 17 R2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.16.0-0ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/31/2017 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: Alienware 17 R2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.family: Alienware 17 R2 dmi.product.name: Alienware 17 R2 dmi.product.sku: Alienware 15 dmi.product.version: A08 dmi.sys.vendor: Alienware nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1827879/+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 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in Release Notes for Ubuntu: New Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: In Progress Status in sudo source package in Bionic: In Progress Status in sudo source package in Cosmic: In Progress Status in sudo source package in Disco: In Progress Status in sudo source package in Eoan: Fix Released Bug description: [impact] sudo does not set HOME to the target user's HOME [test case] ddstreet@thorin:~$ sudo printenv | grep HOME HOME=/home/ddstreet [regression potential] this is a significant behavior change. As mentioned in comment 11 (and later, and other bugs duped to this, and the mailing list discussion, etc) users of Ubuntu so far have been used to running sudo with their own HOME set, not root's HOME. Therefore, it's inappropriate to change this behavior for existing releases; this should be changed starting in Eoan, and only the sudo and sudoers man pages changed in previous releases to indicate the actual behavior of sudo in those releases. [other info] Shortly after upstream changed the behavior, the patch to keep HOME as the calling (instead of target) user was added in bug 760140. For quick reference to anyone coming to this bug, the pre-19.10 behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home or, run sudo with the -H param. -- original description: -- I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1556302/+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 1513528] Re: /usr/bin/software-properties-gtk:KeyError:__getitem__:__getitem__:show_drivers:set_driver_action_status:__getitem__
The following bug is more recent, affects disco and eoan, and contains a similar Traceback to the one here. https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1820863 Additionally, this errors bucket looks to be the same issue. https://errors.ubuntu.com/problem/4e534b50ef855b7cd8166e7c5bb73303dd62fd9f -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1513528 Title: /usr/bin/software-properties- gtk:KeyError:__getitem__:__getitem__:show_drivers:set_driver_action_status:__getitem__ Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with version 0.96.13.1, the problem page at https://errors.ubuntu.com/problem/9de02a9f290237dd5c83e9cc73db340a544b362d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1513528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
** Also affects: gstreamer-editing-services1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-python1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: New Status in gst-omx package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gst-plugins-good1.0 package in Ubuntu: New Status in gst-plugins-ugly1.0 package in Ubuntu: New Status in gst-python1.0 package in Ubuntu: New Status in gst-rtsp-server1.0 package in Ubuntu: New Status in gstreamer-editing-services1.0 package in Ubuntu: New Status in gstreamer-vaapi package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay: keep buffer pool around when flushing/seeking - rtpssrcdemux: Forward serialized events to all pads - qmlglsink: Handle OPENGL header guard changes - qtdemux: fix track language code parsing; ignore corrupted CTTS box - qtmux: Correctly set tkhd width/height to the display size - splitmuxsink: various timecode meta handling fixes - splitmuxsink: make work with audio-only encoders as muxers, e.g. wavenc - v4l2sink: fix pool-less allocation query handling - v4l2dec/enc: fix use after free when handling events - vpx: Fix build against libvpx 1.8 - webmmux: allow resolutions above 4096 gst-plugins-ugly - sid: Fix cross-compilation by using AC_TRY_LINK instead of AC_TRY_RUN - x264: Only enable dynamic loading code for x264 before v253 gst-plugins-bad - assrender: fix disappearing subtitles when seeking back in time -
[Touch-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
There is currently 1.14.4 that in bionic-proposed that needs to be verified first -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: New Status in gst-omx package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gst-plugins-good1.0 package in Ubuntu: New Status in gst-plugins-ugly1.0 package in Ubuntu: New Status in gst-python1.0 package in Ubuntu: New Status in gst-rtsp-server1.0 package in Ubuntu: New Status in gstreamer-editing-services1.0 package in Ubuntu: New Status in gstreamer-vaapi package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay: keep buffer pool around when flushing/seeking - rtpssrcdemux: Forward serialized events to all pads - qmlglsink: Handle OPENGL header guard changes - qtdemux: fix track language code parsing; ignore corrupted CTTS box - qtmux: Correctly set tkhd width/height to the display size - splitmuxsink: various timecode meta handling fixes - splitmuxsink: make work with audio-only encoders as muxers, e.g. wavenc - v4l2sink: fix pool-less allocation query handling - v4l2dec/enc: fix use after free when handling events - vpx: Fix build against libvpx 1.8 - webmmux: allow resolutions above 4096 gst-plugins-ugly - sid: Fix cross-compilation by using AC_TRY_LINK instead of AC_TRY_RUN - x264: Only enable dynamic loading code for x264 before v253 gst-plugins-bad - assrender: fix disappearing subtitles when seeking back in time - decklinkvideosink: fix segfault when audiosink is closed before videosink - decklinkvideosrc: r
[Touch-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
** Also affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-ugly1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-libav1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-rtsp-server1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gstreamer-vaapi (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-omx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: New Status in gst-omx package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gst-plugins-good1.0 package in Ubuntu: New Status in gst-plugins-ugly1.0 package in Ubuntu: New Status in gst-python1.0 package in Ubuntu: New Status in gst-rtsp-server1.0 package in Ubuntu: New Status in gstreamer-editing-services1.0 package in Ubuntu: New Status in gstreamer-vaapi package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay: keep buffer pool around when flushing/seeking - rtpssrcdemux: Forward serialized events to all pads - qmlglsink: Handle OPENGL header guard changes - qtdemux: fix track language code parsing; ignore corrupted CTTS box - qtmux: Correctly set tkhd width/height to the display size - splitmuxsink: various timecode meta handling fixes - splitmuxs
[Touch-packages] [Bug 1733733] Re: portable apps crash while installing package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado
*** This bug is a duplicate of bug 1509043 *** https://bugs.launchpad.net/bugs/1509043 ** This bug has been marked a duplicate of bug 1509043 package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1733733 Title: portable apps crash while installing package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post- installation instalado retornou estado de saída de erro 128 Status in gconf package in Ubuntu: New Bug description: I installed orbital apps then it crashed, i changed to unity environment then tried to install again. I'm in need for portable apps for ubuntu. Description: Ubuntu 17.10 Release: 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: gconf2-common 3.2.6-4ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Tue Nov 21 21:44:08 2017 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 128 InstallationDate: Installed on 2017-09-05 (77 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: gconf Title: package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 128 UpgradeStatus: Upgraded to artful on 2017-11-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1733733/+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 1645384] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de
*** This bug is a duplicate of bug 1509043 *** https://bugs.launchpad.net/bugs/1509043 ** This bug has been marked a duplicate of bug 1509043 package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1645384 Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 128 Status in gconf package in Ubuntu: Confirmed Bug description: el problema se genero cuando intentaba descargar unos programas, no se completo la descarga y la tuve que reiniciar y posterior al reinicio aparecio el mensaje de error. ProblemType: Package DistroRelease: elementary 0.4 Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 28 09:10:05 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 128 InstallationDate: Installed on 2016-11-26 (1 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1645384/+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 1698612] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett
*** This bug is a duplicate of bug 1509043 *** https://bugs.launchpad.net/bugs/1509043 ** This bug has been marked a duplicate of bug 1509043 package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1698612 Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett Status in gconf package in Ubuntu: New Bug description: this problem comes up after aech booting ProblemType: Package DistroRelease: elementary 0.4.1 Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue May 23 18:21:04 2017 ErrorMessage: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett InstallationDate: Installed on 2017-05-22 (26 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698612/+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 1711472] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie
*** This bug is a duplicate of bug 1509043 *** https://bugs.launchpad.net/bugs/1509043 ** This bug has been marked a duplicate of bug 1509043 package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1711472 Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 128 Status in gconf package in Ubuntu: New Bug description: Hello, i want you say what this problem isn't today. I had this problem with ubuntu16.10 And today i have this problem with this new system based on ubuntu. I wish what you resolved this problem. Jo ProblemType: Package DistroRelease: elementary 0.4.1 Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Thu Aug 17 23:53:18 2017 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 128 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1711472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
I've verified these as best as I can. I installed 1.14.4 and played a load of different filetypes: - mp3 - ogg - flac - opus - mp4 (H.264) with different codecs, e.g. mpg123, libav, ... and different players - epiphany, totem, rhythmbox. I didn't find any regressions. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: In Progress Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833039] Re: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1
apt-get update && apt-get install -y --no-install-recommends --allow-downgrades \ libssl1.1=1.1.0g-2ubuntu4.3 openssl=1.1.0g-2ubuntu4.3 \ Temporary fix this issue particularly painful in production -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833039 Title: 18.04/Apache2: rejecting client initiated renegotiation due to openssl 1.1.1 Status in apache2 package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Confirmed Bug description: I am using Apache2 with client certificate authentication. Since recently (last week) and without any configuration changes, the following errors occur frequently: AH02042: rejecting client initiated renegotiation Client connections are very slow and sometimes it takes more than a minute until a weg page can be opened in the browser. Before installation of the latest security fixes last week, this error did not occur. Could it be related to https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689? System information: Description:Ubuntu 18.04.2 LTS Release:18.04 apache2: Installiert: 2.4.29-1ubuntu4.6 Installationskandidat: 2.4.29-1ubuntu4.6 Versionstabelle: *** 2.4.29-1ubuntu4.6 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.29-1ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages openssl: Installiert: 1.1.1-1ubuntu2.1~18.04.2 Installationskandidat: 1.1.1-1ubuntu2.1~18.04.2 Versionstabelle: *** 1.1.1-1ubuntu2.1~18.04.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.0g-2ubuntu4.3 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.1.0g-2ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834318] Re: Warning from Google about Ubuntu
I believe it is a bug, because ubuntu would need to comply with updating the plugin in order for it to continue to function. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1834318 Title: Warning from Google about Ubuntu Status in gnome-online-accounts package in Ubuntu: Invalid Bug description: I'm not sure if it is a correct place to report this problem. I use Ubuntu 18.04. Yesterday I've got an email from Google warning that "Ubuntu" will lose access to my Google account if it will not comply with new Google policy requirement. Screenshot attached and here's the full text of the email: Hi, Although you don’t need to do anything, we wanted to let you know that the following apps may no longer be able to access some data in your Google account, including your Gmail content. If these apps are unable to meet the deadline to comply with our updated data policy requirements, they'll lose access to your account from 15 July 2019. Ubuntu We are making this change as part of ongoing efforts to make sure that your data is protected and private. You can always view, manage and remove apps to which you’ve given access to your account by visiting your Google account. Thanks, The Google Accounts team To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1834318/+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 1829077] Re: disco 19.04 doesn't shutdown on an Asrock 970 Extreme 4
** Package changed: systemd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829077 Title: disco 19.04 doesn't shutdown on an Asrock 970 Extreme 4 Status in linux package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 19.04 GNOME 64 bits. When I choose "Power Off", it closes the session screen but then it displays the red dots who scroll under Ubuntu logo and it never stop completely. I can listen the hard disk containing my home directory which stops (the system is on a SSD). Each time, I have to switch off the computer. I can start it again without any problem. The command "sudo shutdown now" give the same result. This computer had not this problem with the previous version of Ubuntu. Proc : AMD Fx 8320 Motherboard : Asrock 970 Extreme 4 graphic card : Radeon 6850 Ram : 8Go Ubuntu 19.04 is the only OS on the SSD system drive /home is on a second hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Changed in: systemd (Debian) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Released Status in linux source package in Disco: New Status in systemd source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Status in systemd package in Debian: Confirmed Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775457] Re: /usr/bin/pip3:ImportError:/usr/bin/pip3@9
** Tags added: id-5d127347b179250b9b79f461 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1775457 Title: /usr/bin/pip3:ImportError:/usr/bin/pip3@9 Status in apport package in Ubuntu: New Status in python-pip package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding python-pip. This problem was most recently seen with package version 9.0.1-2.3~ubuntu1, the problem page at https://errors.ubuntu.com/problem/4e26eab10247fe3383fb8c84ca8a0d8eb21abc83 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775457/+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 1813581] Re: gpgme1.0 ftbfs in 18.04 LTS
** Tags added: id-5d126ca59ddb0c88fa166051 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1813581 Title: gpgme1.0 ftbfs in 18.04 LTS Status in gpgme1.0 package in Ubuntu: Won't Fix Status in gpgme1.0 source package in Bionic: Confirmed Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html gpgme1.0 ftbfs. * Start testing of TofuInfoTest * Config: Using QtTest library 5.9.5, Qt 5.9.5 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0) PASS : TofuInfoTest::initTestCase() PASS : TofuInfoTest::testTofuNull() PASS : TofuInfoTest::testTofuInfo() PASS : TofuInfoTest::testTofuSignCount() PASS : TofuInfoTest::testTofuKeyList() PASS : TofuInfoTest::testTofuPolicy() FAIL! : TofuInfoTest::testTofuConflict() 'sig.validity() == Signature::Marginal' returned FALSE. () Loc: [t-tofuinfo.cpp(458)] PASS : TofuInfoTest::cleanupTestCase() Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 2386ms * Finished testing of TofuInfoTest * FAIL: t-tofuinfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1813581/+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 1834321] Re: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 ... I downloaded the python 3.7 source code
we don't support installing the python3.7 packages in 16.04 LTS. This has nothing to do with any packaging. ** Changed in: python3-defaults (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1834321 Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 ... I downloaded the python 3.7 source code and compiled & installed it. I did this with serveral libraries which belong to ffmpeg & gstreamer. My system crached for two totally. I am not sure about the first one resion but for second time, I was going to uninstall python 3.5 (system default python3) because I had already compiled and installed python 3.7. The ubuntu package manager uninstalled a huge chunk of other packages like Qt5 package & etc. After uinstalling packages my system went to unstable graphical situation. I think something went wrong with the main graphical libraries and maybe graphical drivers. After a system restart I had system boot problem and only I could access command line. My network-manager service also stoped and I couldn't access internet so reinstall or fixing packages were not possible for me. I had to reinstall whole the system. Status in python3-defaults package in Ubuntu: Invalid Bug description: I downloaded the python 3.7 source code and compiled & installed it. I did this with several libraries which belong to ffmpeg & gstreamer. My system crashed for two totally. I am not sure about the first one reason but for second time, I was going to uninstall python 3.5 (system default python3) because I had already compiled and installed python 3.7. The Ubuntu package manager uninstalled a huge chunk of other packages like Qt5 package & etc. After uninstalling packages my system went to unstable graphical situation. I think something went wrong with the main graphical libraries and maybe graphical drivers. After a system restart I had system boot problem and only I could access command line. My network-manager service also stopped and I couldn't access internet so reinstall or fixing packages were not possible for me. I had to reinstall whole the system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-151.178-generic 4.4.179 Uname: Linux 4.4.0-151-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Jun 25 13:16:57 2019 DuplicateSignature: package:python3:3.5.1-3 Removing python3 (3.5.1-3) ... /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: py3clean: not found dpkg: error processing package python3 (--purge): subprocess installed pre-removal script returned error exit status 127 ErrorMessage: subprocess installed pre-removal script returned error exit status 127 InstallationDate: Installed on 2019-06-24 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1834321/+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 1829077] Re: disco 19.04 doesn't shutdown on an Asrock 970 Extreme 4
YES ! It works ! I reached to start with kernel 5.2 (I had a problem with Grub because of 2 versions of Ubuntu installed on 2 partitions, and it booted not with the right Grub). So, when I boot with kernel 5.2, the computer stop normally and completely like before. Thanks ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1829077 Title: disco 19.04 doesn't shutdown on an Asrock 970 Extreme 4 Status in systemd package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 19.04 GNOME 64 bits. When I choose "Power Off", it closes the session screen but then it displays the red dots who scroll under Ubuntu logo and it never stop completely. I can listen the hard disk containing my home directory which stops (the system is on a SSD). Each time, I have to switch off the computer. I can start it again without any problem. The command "sudo shutdown now" give the same result. This computer had not this problem with the previous version of Ubuntu. Proc : AMD Fx 8320 Motherboard : Asrock 970 Extreme 4 graphic card : Radeon 6850 Ram : 8Go Ubuntu 19.04 is the only OS on the SSD system drive /home is on a second hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829077/+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 1756595] Re: disk space info inadvertently provides all installed snaps
This bug was fixed in the package apt - 1.9.1 --- apt (1.9.1) experimental; urgency=medium * RFC1123StrToTime: Accept const std::string& as first argument * Fix pkg-config-test autopkgtest -- Julian Andres Klode Thu, 20 Jun 2019 17:53:14 +0200 ** Changed in: apt (Ubuntu Eoan) Status: Fix Committed => Fix Released -- 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/1756595 Title: disk space info inadvertently provides all installed snaps Status in apport package in Ubuntu: Invalid Status in apt package in Ubuntu: Fix Released Status in apport source package in Bionic: Invalid Status in apt source package in Bionic: Triaged Status in apport source package in Disco: New Status in apt source package in Disco: Triaged Status in apport source package in Eoan: Invalid Status in apt source package in Eoan: Fix Released Bug description: When apport is reporting a crash, it includes the output of the "df" utility, to list the free disk space information per mount point. That output nowadays will inadvertently include all snaps that the user may have installed, including their revision numbers. Here is a simple df output: andreas@nsn7:~$ df Filesystem 1K-blocksUsed Available Use% Mounted on udev 8119680 0 8119680 0% /dev tmpfs 16301561828 1628328 1% /run nsn7/ROOT/ubuntu433084288 2500608 430583680 1% / tmpfs 8150776 1 8131888 1% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs 8150776 0 8150776 0% /sys/fs/cgroup nsn7/var/log430763136 179456 430583680 1% /var/log nsn7/var/tmp430583808 128 430583680 1% /var/tmp /dev/sda2 1032088 160336871752 16% /boot /dev/sda1 5232482720520528 1% /boot/efi nsn7/home 430651264 67584 430583680 1% /home nsn7/var/cache 430653312 69632 430583680 1% /var/cache nsn7/var/mail 430583808 128 430583680 1% /var/mail nsn7/var/spool 430583808 128 430583680 1% /var/spool tmpfs 1630152 16 1630136 1% /run/user/120 tmpfs 100 0 100 0% /var/lib/lxd/shmounts tmpfs 100 0 100 0% /var/lib/lxd/devlxd tmpfs 1630152 36 1630116 1% /run/user/1000 nsn7/lxd/containers/squid-ds216 431444096 860416 430583680 1% /var/lib/lxd/storage-pools/default/containers/squid-ds216 /dev/loop0 83712 83712 0 100% /snap/core/4206 /dev/loop1 102144 102144 0 100% /snap/git-ubuntu/402 You can see I have the core snap at revision 4206, and git-ubuntu at revision 402. There are already many bug reports in launchpad where one can see this information. Granted, the user can review it, refuse to send this data, etc. This bug is about the unexpectedness of having that information in the disk space data. If the user sees a prompt like "Would you like to include disk free space information in your report?", or "Would you like to include the output of the df(1) command in your report?", that doesn't immediately translate to "Would you like to include disk free space information and a list of all installed snaps and their revision numbers in your report?". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1756595/+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 1834321] [NEW] package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 ... I downloaded the python 3.7 source co
Public bug reported: I downloaded the python 3.7 source code and compiled & installed it. I did this with several libraries which belong to ffmpeg & gstreamer. My system crashed for two totally. I am not sure about the first one reason but for second time, I was going to uninstall python 3.5 (system default python3) because I had already compiled and installed python 3.7. The Ubuntu package manager uninstalled a huge chunk of other packages like Qt5 package & etc. After uninstalling packages my system went to unstable graphical situation. I think something went wrong with the main graphical libraries and maybe graphical drivers. After a system restart I had system boot problem and only I could access command line. My network-manager service also stopped and I couldn't access internet so reinstall or fixing packages were not possible for me. I had to reinstall whole the system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-151.178-generic 4.4.179 Uname: Linux 4.4.0-151-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Jun 25 13:16:57 2019 DuplicateSignature: package:python3:3.5.1-3 Removing python3 (3.5.1-3) ... /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: py3clean: not found dpkg: error processing package python3 (--purge): subprocess installed pre-removal script returned error exit status 127 ErrorMessage: subprocess installed pre-removal script returned error exit status 127 InstallationDate: Installed on 2019-06-24 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1834321 Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 ... I downloaded the python 3.7 source code and compiled & installed it. I did this with serveral libraries which belong to ffmpeg & gstreamer. My system crached for two totally. I am not sure about the first one resion but for second time, I was going to uninstall python 3.5 (system default python3) because I had already compiled and installed python 3.7. The ubuntu package manager uninstalled a huge chunk of other packages like Qt5 package & etc. After uinstalling packages my system went to unstable graphical situation. I think something went wrong with the main graphical libraries and maybe graphical drivers. After a system restart I had system boot problem and only I could access command line. My network-manager service also stoped and I couldn't access internet so reinstall or fixing packages were not possible for me. I had to reinstall whole the system. Status in python3-defaults package in Ubuntu: New Bug description: I downloaded the python 3.7 source code and compiled & installed it. I did this with several libraries which belong to ffmpeg & gstreamer. My system crashed for two totally. I am not sure about the first one reason but for second time, I was going to uninstall python 3.5 (system default python3) because I had already compiled and installed python 3.7. The Ubuntu package manager uninstalled a huge chunk of other packages like Qt5 package & etc. After uninstalling packages my system went to unstable graphical situation. I think something went wrong with the main graphical libraries and maybe graphical drivers. After a system restart I had system boot problem and only I could access command line. My network-manager service also stopped and I couldn't access internet so reinstall or fixing packages were not possible for me. I had to reinstall whole the system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-151.178-generic 4.4.179 Uname: Linux 4.4.0-151-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Jun 25 13:16:57 2019 DuplicateSignature: package:python3:3.5.1-3 Removing python3 (3.5.1-3) ... /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: py3clean: not found dpkg: error processing package python3 (--purge): subprocess installed pre-removal script returned error exit status 127 ErrorMessage: subprocess installed pre-removal script returned error exit status 127 InstallationDate: Installed on 2019-06-24
[Touch-packages] [Bug 1834321] Re: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 ... I downloaded the python 3.7 source code
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1834321 Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 ... I downloaded the python 3.7 source code and compiled & installed it. I did this with serveral libraries which belong to ffmpeg & gstreamer. My system crached for two totally. I am not sure about the first one resion but for second time, I was going to uninstall python 3.5 (system default python3) because I had already compiled and installed python 3.7. The ubuntu package manager uninstalled a huge chunk of other packages like Qt5 package & etc. After uinstalling packages my system went to unstable graphical situation. I think something went wrong with the main graphical libraries and maybe graphical drivers. After a system restart I had system boot problem and only I could access command line. My network-manager service also stoped and I couldn't access internet so reinstall or fixing packages were not possible for me. I had to reinstall whole the system. Status in python3-defaults package in Ubuntu: New Bug description: I downloaded the python 3.7 source code and compiled & installed it. I did this with several libraries which belong to ffmpeg & gstreamer. My system crashed for two totally. I am not sure about the first one reason but for second time, I was going to uninstall python 3.5 (system default python3) because I had already compiled and installed python 3.7. The Ubuntu package manager uninstalled a huge chunk of other packages like Qt5 package & etc. After uninstalling packages my system went to unstable graphical situation. I think something went wrong with the main graphical libraries and maybe graphical drivers. After a system restart I had system boot problem and only I could access command line. My network-manager service also stopped and I couldn't access internet so reinstall or fixing packages were not possible for me. I had to reinstall whole the system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-151.178-generic 4.4.179 Uname: Linux 4.4.0-151-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Jun 25 13:16:57 2019 DuplicateSignature: package:python3:3.5.1-3 Removing python3 (3.5.1-3) ... /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: py3clean: not found dpkg: error processing package python3 (--purge): subprocess installed pre-removal script returned error exit status 127 ErrorMessage: subprocess installed pre-removal script returned error exit status 127 InstallationDate: Installed on 2019-06-24 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1834321/+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 1834318] Re: Warning from Google about Ubuntu
So to report this as a bug, I need to wait until Ubuntu stops working with Google account? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1834318 Title: Warning from Google about Ubuntu Status in gnome-online-accounts package in Ubuntu: Invalid Bug description: I'm not sure if it is a correct place to report this problem. I use Ubuntu 18.04. Yesterday I've got an email from Google warning that "Ubuntu" will lose access to my Google account if it will not comply with new Google policy requirement. Screenshot attached and here's the full text of the email: Hi, Although you don’t need to do anything, we wanted to let you know that the following apps may no longer be able to access some data in your Google account, including your Gmail content. If these apps are unable to meet the deadline to comply with our updated data policy requirements, they'll lose access to your account from 15 July 2019. Ubuntu We are making this change as part of ongoing efforts to make sure that your data is protected and private. You can always view, manage and remove apps to which you’ve given access to your account by visiting your Google account. Thanks, The Google Accounts team To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1834318/+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 1834318] Re: Warning from Google about Ubuntu
This is not an ubuntu bug, but a warning from google updating data policy ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1834318 Title: Warning from Google about Ubuntu Status in gnome-online-accounts package in Ubuntu: Invalid Bug description: I'm not sure if it is a correct place to report this problem. I use Ubuntu 18.04. Yesterday I've got an email from Google warning that "Ubuntu" will lose access to my Google account if it will not comply with new Google policy requirement. Screenshot attached and here's the full text of the email: Hi, Although you don’t need to do anything, we wanted to let you know that the following apps may no longer be able to access some data in your Google account, including your Gmail content. If these apps are unable to meet the deadline to comply with our updated data policy requirements, they'll lose access to your account from 15 July 2019. Ubuntu We are making this change as part of ongoing efforts to make sure that your data is protected and private. You can always view, manage and remove apps to which you’ve given access to your account by visiting your Google account. Thanks, The Google Accounts team To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1834318/+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 1834318] [NEW] Warning from Google about Ubuntu
Public bug reported: I'm not sure if it is a correct place to report this problem. I use Ubuntu 18.04. Yesterday I've got an email from Google warning that "Ubuntu" will lose access to my Google account if it will not comply with new Google policy requirement. Screenshot attached and here's the full text of the email: Hi, Although you don’t need to do anything, we wanted to let you know that the following apps may no longer be able to access some data in your Google account, including your Gmail content. If these apps are unable to meet the deadline to comply with our updated data policy requirements, they'll lose access to your account from 15 July 2019. Ubuntu We are making this change as part of ongoing efforts to make sure that your data is protected and private. You can always view, manage and remove apps to which you’ve given access to your account by visiting your Google account. Thanks, The Google Accounts team ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: Invalid ** Attachment added: "google-ubuntu.png" https://bugs.launchpad.net/bugs/1834318/+attachment/5273452/+files/google-ubuntu.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1834318 Title: Warning from Google about Ubuntu Status in gnome-online-accounts package in Ubuntu: Invalid Bug description: I'm not sure if it is a correct place to report this problem. I use Ubuntu 18.04. Yesterday I've got an email from Google warning that "Ubuntu" will lose access to my Google account if it will not comply with new Google policy requirement. Screenshot attached and here's the full text of the email: Hi, Although you don’t need to do anything, we wanted to let you know that the following apps may no longer be able to access some data in your Google account, including your Gmail content. If these apps are unable to meet the deadline to comply with our updated data policy requirements, they'll lose access to your account from 15 July 2019. Ubuntu We are making this change as part of ongoing efforts to make sure that your data is protected and private. You can always view, manage and remove apps to which you’ve given access to your account by visiting your Google account. Thanks, The Google Accounts team To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1834318/+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 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se
** Description changed: + [Impact] + https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 + + This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: + https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=pulseaudio&period=month + + [Test Case] + + No manual test case known. We just wait and watch errors.ubuntu.com to + see where the most crashes are. + + [Regression Potential] + + Low. The fix is already in PulseAudio 12 so has been used in Ubuntu + 18.10 and later for a year so far. --- Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE 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.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Description changed: [Impact] https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=pulseaudio&period=month [Test Case] No manual test case known. We just wait and watch errors.ubuntu.com to see where the most crashes are. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. - --- + [Original Report] Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.
[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
** Description changed: + [Impact] + https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669 + + This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: + https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=pulseaudio&period=month + + [Test Case] + + No manual test case known. We just wait and watch errors.ubuntu.com to + see where the most crashes are. + + [Regression Potential] + + Low. The fix is already in PulseAudio 12 so has been used in Ubuntu + 18.10 and later for a year so far. --- Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux-gnu/libasound.so.2 ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC ** Description changed: [Impact] https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=pulseaudio&period=month [Test Case] No manual test case known. We just wait and watch errors.ubuntu.com to see where the most crashes are. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. - --- + [Original Report] Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevice
[Touch-packages] [Bug 1599646] Re: E-mail report contains repeated "Reading database ... NN%" lines
This fix only works in english localization. Still getting these lines in german with 1.1ubuntu1.18.04.11 on bionic LTS: ... Paketinstallationsprotokoll: Log started: 2019-06-26 06:08:33 (Lese Datenbank ... (Lese Datenbank ... 5% (Lese Datenbank ... 10% (Lese Datenbank ... 15% ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1599646 Title: E-mail report contains repeated "Reading database ... NN%" lines Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Status in apt package in Debian: New Bug description: [Impact] * Unattended-upgrades sends the following repeating dpkg progress lines with almost no informational value in the email report: ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 60486 files and directories currently installed.) ... * This makes the report email too verbose and makes harder to spot real problems. [Test Case] * Run package autopkgtest and observe no such lines in the echoed email in upgrade-all-security and upgrade-between-snapshots tests. [Regression Potential] * The fix filters dpkg's output only and in the worst case other lines could be missing or u-u could crash. Since the applied hard- coded regex pattern is fairly simple and we observed no crashes in the tests those regressions are unlikey to occur. [Originial Bug Text] This concerns unattended-upgrades 0.90 in Xenial. Here is an excerpt from an e-mail report sent out by u-u after the upgrade process is completed: Package installation log: Log started: 2016-07-06 17:24:21 Preconfiguring packages ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 314949 files and directories currently installed.) Preparing to unpack .../tzdata_2016f-0ubuntu0.16.04_all.deb ... Unpacking tzdata (2016f-0ubuntu0.16.04) over (2016d-0ubuntu0.16.04) ... Preparing to unpack .../libgimp2.0_2.8.16-1ubuntu1.1_i386.deb ... All but the last "Reading database ..." line should be elided from the message. As a matter of fact, those lines do not appear in messages mailed out from current Trusty systems (u-u version 0.82.1ubuntu2.4), so this appears to be a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1599646/+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 1814355] Re: snapd remove /usr/local/bin from the PATH for all systemd unit (bionic SRU regression)
** Description changed: [Impact] - * Initramfs exports PATH to init, which is different than the expected + * Initramfs exports PATH to init, which is different than the expected stock / compiled one, which results in slightly different runtime behaviour of init, if it has environment generators as well. - [Test Case] - * Disable snapd env generator & disable initrd-less boot (if enabled) -sudo chmod -x /usr/lib/systemd/system-environment-generators/snapd-env-generator -set empty GRUB_FORCE_PARTUUID= and update-grub - - * Reboot cosmic system with an initramfs -$ journalctl -b -k | grep initramfs -(verify that initramfs was unpacked) + * Disable snapd env generator & disable initrd-less boot (if enabled) + sudo chmod -x /usr/lib/systemd/system-environment-generators/snapd-env-generator + set empty GRUB_FORCE_PARTUUID= and update-grub - * Check the path used by systemd, ie.: -systemd-run /usr/bin/env -journalctl -b -e | grep PATH + * Reboot cosmic system with an initramfs + $ journalctl -b -k | grep initramfs + (verify that initramfs was unpacked) -It should contain /usr/local + * Check the path used by systemd, ie.: + systemd-run /usr/bin/env + journalctl -b -e | grep PATH - * Upgrade initramfs-tools & reboot + It should contain /usr/local -The path should remain the same and it should contain /usr/local + * Enable any env generator for example & reboot: +/usr/lib/systemd/system-environment-generators/xnox.sh +#!/bin/sh +echo XNOX=ROCKS - * Enable snapd env generator and reboot again + * Verify path used by systemd - * Verify path used by systemd + It should still contain /usr/local -It should still contain /usr/local & /snap/bin + Repeat again with the new initramfs-tools. + [Regression Potential] - * We are hardcoding, the same path, yet again, in one more place. - However, we are setting it to a well-known value as it was pre + * We are hardcoding, the same path, yet again, in one more place. However, we are setting it to a well-known value (see https://wiki.ubuntu.com/PATH + ) as it is universally expected and regressed when booted (a) with initrd AND (b) with broken path exported by initrd AND (c) with an env-generator. [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance === Big regression in 2.37.1+18.04 compare to version 2.34.2 all these paths /usr/local/sbin & /usr/local/bin are not anymore in the path of all systemd process . So we can not start a daemon that use /usr/local/bin reinstalling package 2.34.2 fix the problem in 2.34.2 : ~# strings /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin in 2.37.1+18.04 : ~# strings /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH PATH=/sbin:/usr/sbin:/bin:/usr/bin:/snap/bin -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1814355 Title: snapd remove /usr/local/bin from the PATH for all systemd unit (bionic SRU regression) Status in initramfs-tools package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in snapd source package in Bionic: Fix Released Status in systemd source package in Bionic: New Status in initramfs-tools source package in Cosmic: New Status in snapd source package in Cosmic: New Status in systemd source package in Cosmic: New Bug description: [Impact] * Initramfs exports PATH to init, which is different than the expected stock / compiled one, which results in slightly different runtime behaviour of init, if it has environment generators as well. [Test Case] * Disable snapd env generator & disable initrd-less boot (if enabled) sudo chmod -x /usr/lib/systemd/system-environment-generators/snapd-env-generator set empty GRUB_FORCE_PARTUUID= and update-grub * Reboot cosmic system with an initramfs $ journalctl -b -k | grep initramfs (verify that initramfs was unpacked) * Check the path used by systemd, ie.: systemd-run /usr/bin/env journalctl -b -e | grep PATH It should contain /usr/local * Enable any env generator for example & reboot: /usr/lib/systemd/system-environment-generators/xnox.sh #!/bin/sh echo XNOX=ROCKS * Verify path used by systemd
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
The PR to re-enable the generator: https://github.com/snapcore/snapd/pull/7031 and updates the test. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
When we disabled the generator in snapd we added a regression test (tests/main/snap-system-env): https://github.com/snapcore/snapd/pull/6470/files With the current systemd (not the one in -proposed) I get: ``` grep error: pattern not found, got: LANG=C.UTF-8 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/snap/bin ``` which is expected and shows that the generator is broken. When running the same regression test with the systemd in -proposed I get no error so the update looks fine (as far as our test case goes). I heard some concerns from xnox about systems with initrd that need to be explored too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814355] Re: snapd remove /usr/local/bin from the PATH for all systemd unit (bionic SRU regression)
** Description changed: + [Impact] + + * Initramfs exports PATH to init, which is different than the expected + stock / compiled one, which results in slightly different runtime + behaviour of init, if it has environment generators as well. + + + [Test Case] + + * Disable snapd env generator & disable initrd-less boot (if enabled) +sudo chmod -x /usr/lib/systemd/system-environment-generators/snapd-env-generator +set empty GRUB_FORCE_PARTUUID= and update-grub + + * Reboot cosmic system with an initramfs +$ journalctl -b -k | grep initramfs +(verify that initramfs was unpacked) + + * Check the path used by systemd, ie.: +systemd-run /usr/bin/env +journalctl -b -e | grep PATH + +It should contain /usr/local + + * Upgrade initramfs-tools & reboot + +The path should remain the same and it should contain /usr/local + + * Enable snapd env generator and reboot again + + * Verify path used by systemd + +It should still contain /usr/local & /snap/bin + + [Regression Potential] + + * We are hardcoding, the same path, yet again, in one more place. + However, we are setting it to a well-known value as it was pre + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + + === + Big regression in 2.37.1+18.04 compare to version 2.34.2 all these paths /usr/local/sbin & /usr/local/bin are not anymore in the path of all systemd process . So we can not start a daemon that use /usr/local/bin - reinstalling package 2.34.2 fix the problem in 2.34.2 : - + ~# strings /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin in 2.37.1+18.04 : ~# strings /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH PATH=/sbin:/usr/sbin:/bin:/usr/bin:/snap/bin -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1814355 Title: snapd remove /usr/local/bin from the PATH for all systemd unit (bionic SRU regression) Status in initramfs-tools package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in snapd source package in Bionic: Fix Released Status in systemd source package in Bionic: New Status in initramfs-tools source package in Cosmic: New Status in snapd source package in Cosmic: New Status in systemd source package in Cosmic: New Bug description: [Impact] * Initramfs exports PATH to init, which is different than the expected stock / compiled one, which results in slightly different runtime behaviour of init, if it has environment generators as well. [Test Case] * Disable snapd env generator & disable initrd-less boot (if enabled) sudo chmod -x /usr/lib/systemd/system-environment-generators/snapd-env-generator set empty GRUB_FORCE_PARTUUID= and update-grub * Reboot cosmic system with an initramfs $ journalctl -b -k | grep initramfs (verify that initramfs was unpacked) * Check the path used by systemd, ie.: systemd-run /usr/bin/env journalctl -b -e | grep PATH It should contain /usr/local * Upgrade initramfs-tools & reboot The path should remain the same and it should contain /usr/local * Enable snapd env generator and reboot again * Verify path used by systemd It should still contain /usr/local & /snap/bin [Regression Potential] * We are hardcoding, the same path, yet again, in one more place. However, we are setting it to a well-known value as it was pre [Other Info] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance === Big regression in 2.37.1+18.04 compare to version 2.34.2 all these paths /usr/local/sbin & /usr/local/bin are not anymore in the path of all systemd process . So we can not start a daemon that use /usr/local/bin reinstalling package 2.34.2 fix the problem in 2.34.2 : ~# strings /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin in 2.37.1+18.04 : ~# strings /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH PATH=/sbin:/usr/sbin:/bin:/usr/bin:/snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814355/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-pack
[Touch-packages] [Bug 1814355] Re: snapd remove /usr/local/bin from the PATH for all systemd unit (bionic SRU regression)
** Also affects: initramfs-tools (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1814355 Title: snapd remove /usr/local/bin from the PATH for all systemd unit (bionic SRU regression) Status in initramfs-tools package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in snapd source package in Bionic: Fix Released Status in systemd source package in Bionic: New Status in initramfs-tools source package in Cosmic: New Status in snapd source package in Cosmic: New Status in systemd source package in Cosmic: New Bug description: Big regression in 2.37.1+18.04 compare to version 2.34.2 all these paths /usr/local/sbin & /usr/local/bin are not anymore in the path of all systemd process . So we can not start a daemon that use /usr/local/bin reinstalling package 2.34.2 fix the problem in 2.34.2 : ~# strings /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin in 2.37.1+18.04 : ~# strings /proc/$(pidof /lib/systemd/systemd-resolved)/environ | grep PATH PATH=/sbin:/usr/sbin:/bin:/usr/bin:/snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814355/+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 1834293] Re: screen
Are you saying the display gets screenshotted without you asking? ** Package changed: xorg (Ubuntu) => gnome-shell (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/1834293 Title: screen Status in gnome-shell package in Ubuntu: New Bug description: the system begins to make the operation capture the screen without opening any program or keyboard command. sometimes it happens without to and I have to restart the system and the use becomes unfeasible. Sometimes the problem stops and comes back with everything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 04:26:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated Graphics Controller [1019:995b] Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated Graphics Controller [1019:995b] MachineType: Semp Toshiba IS 1414 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fbbaea76-1d2d-4b24-850f-cb5685d71e24 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: MTVNCRB01.86C..X.00 dmi.board.name: IS 1414 dmi.board.vendor: Semp Toshiba dmi.board.version: CRB dmi.chassis.type: 10 dmi.chassis.vendor: Semp Toshiba dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrMTVNCRB01.86C..X.00:bd05/07/2010:svnSempToshiba:pnIS1414:pvr20ga&ICH9MChipset:rvnSempToshiba:rnIS1414:rvrCRB:cvnSempToshiba:ct10:cvr: dmi.product.name: IS 1414 dmi.product.version: 20ga & ICH9M Chipset dmi.sys.vendor: Semp Toshiba version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
The added Breaks: will ensure that the fixes are applied together. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
@xnox we were investigating this in parallel :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
The snapd and systemd fixes triggered LP: #1814355 together and I'm now investigating if the initiramfs fix for that 'regression' should be backported to Bionic, too. In that case I'll add a new Breaks: to the systemd upload. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832337] Re: Require password when starting usb-creator
IIUC, when anyone who plugs a removable USB stick in a PC it is mounted in /media// and, as long as the FS in the device does not support privileges attributes (e.g. FAT32), anyone is granted the rights to overwrite anything (but partitions ?) in the device. So I don't see why anyone would be bored with authentication for this task. Let me know if I forget something. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1832337 Title: Require password when starting usb-creator Status in policykit-desktop-privileges package in Ubuntu: Fix Released Status in usb-creator package in Ubuntu: Fix Released Bug description: Because usb-creator performs privileged actions, it should require authentication prior to starting. policykit-desktop-privileges should be modified so that usb-creator requires password authentication prior to starting. While it was a deliberate design decision to allow usb-creator to perform mounting and writing without authentication (see https://bugs.launchpad.net/ubuntu/+source/policykit-desktop- privileges/+bug/1568149), this decision should be revisited. Allowing the use of usb-creator without authentication presents an unnecessary security risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1832337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
In effect, I'm saying that we need to (a) fix systemd as per this bug report (b) fix initramfs-tools (c) only then enable snapd env generator -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791691] Re: PATH broken in systemd units
** Also affects: initramfs-tools (Ubuntu) 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/1791691 Title: PATH broken in systemd units Status in cloud-images: Confirmed Status in initramfs-tools package in Ubuntu: New Status in snapd package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: New Status in snapd source package in Bionic: In Progress Status in initramfs-tools source package in Cosmic: New Status in snapd source package in Cosmic: Fix Released Bug description: systemd units have broken PATH in recent cloud images. The PATH set for them is PATH=:/snap/bin. Previously value is PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin # cat /etc/cloud/build.info build_name: server serial: 20180906 Booted in lxc that fails like: # lxc launch ubuntu-daily:cosmic c3 # lxc exec c3 cat /run/cloud-init/result.json { "v1": { "datasource": null, "errors": [ "Unexpected error while running command.\nCommand: ['netplan', 'generate']\nExit code: -\nReason: [Errno 2] No such file or directory: b'netplan': b'netplan'\nStdout: -\nStderr: -", "Unexpected error while running command.\nCommand: ['netplan', 'generate']\nExit code: -\nReason: [Errno 2] No such file or directory: b'netplan': b'netplan'\nStdout: -\nStderr: -", "('ssh-authkey-fingerprints', KeyError('getpwnam(): name not found: ubuntu',))" ] } } Related bugs: * bug 1771382: ds-identify: does not have expected PATH. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1791691/+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 1752830] Re: Permanent framerate drop
** Package changed: xorg (Ubuntu) => compiz (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/1752830 Title: Permanent framerate drop Status in compiz package in Ubuntu: New Bug description: After some time of use, the desktop framerate drops to about 15 fps permanently, requiring a system restart to get back to normal. The top command does not indicate any increase in cpu or memory use. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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: Fri Mar 2 03:14:13 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: EcryptfsInUse: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:030d] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:030d] InstallationDate: Installed on 2017-08-15 (199 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer Aspire 4332 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=082fac05-7749-4a84-9734-774ee7b03b1a ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.10 dmi.board.name: HM41 dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.10:bd03/29/2010:svnAcer:pnAspire4332:pvr0100:rvnAcer:rnHM41:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 4332 dmi.product.version: 0100 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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 Mar 1 23:56:15 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1752830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
We have codepaths with and without initrd, which results in different environment that systemd starts up with. In bionic, initramfs-tools sets PATH to PATH=/sbin:/usr/sbin:/bin:/usr/bin In later releases, initramfs-tools sets PATH to PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin And systemd can come up without initrd (lxd) in which case PATH is not set at all, and internally systemd uses the built-in compiled PATH. The snapd environment generator has been fixed to handle the case of empty or unset PATH. But it only appends the snapd path, meaning that it doesn't inject /usr/local into the PATH. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1513528] Re: /usr/bin/software-properties-gtk:KeyError:__getitem__:__getitem__:show_drivers:set_driver_action_status:__getitem__
** Changed in: software-properties (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1513528 Title: /usr/bin/software-properties- gtk:KeyError:__getitem__:__getitem__:show_drivers:set_driver_action_status:__getitem__ Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with version 0.96.13.1, the problem page at https://errors.ubuntu.com/problem/9de02a9f290237dd5c83e9cc73db340a544b362d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1513528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
The autopkgtest failures seem to be unrelated. I re-triggered flaky tests and I'm updating the hints where needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834293] [NEW] screen
Public bug reported: the system begins to make the operation capture the screen without opening any program or keyboard command. sometimes it happens without to and I have to restart the system and the use becomes unfeasible. Sometimes the problem stops and comes back with everything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 04:26:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated Graphics Controller [1019:995b] Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated Graphics Controller [1019:995b] MachineType: Semp Toshiba IS 1414 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fbbaea76-1d2d-4b24-850f-cb5685d71e24 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: MTVNCRB01.86C..X.00 dmi.board.name: IS 1414 dmi.board.vendor: Semp Toshiba dmi.board.version: CRB dmi.chassis.type: 10 dmi.chassis.vendor: Semp Toshiba dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrMTVNCRB01.86C..X.00:bd05/07/2010:svnSempToshiba:pnIS1414:pvr20ga&ICH9MChipset:rvnSempToshiba:rnIS1414:rvrCRB:cvnSempToshiba:ct10:cvr: dmi.product.name: IS 1414 dmi.product.version: 20ga & ICH9M Chipset dmi.sys.vendor: Semp Toshiba version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1834293 Title: screen Status in xorg package in Ubuntu: New Bug description: the system begins to make the operation capture the screen without opening any program or keyboard command. sometimes it happens without to and I have to restart the system and the use becomes unfeasible. Sometimes the problem stops and comes back with everything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 04:26:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated Graphics Controller [1019:995b] Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated Graphics Controller [1019:995b] MachineType: Semp Toshiba IS 1414 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fbbaea76-1d2d-4b24-850f-cb5685d71e24 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: MTVNCRB01.86C..X.00 dmi.board.name: IS 1414 dmi.board.vendor: Semp Toshiba dmi.board.version: CRB dmi.chassis.type: 10 dmi.chassis.vendor: Semp Toshiba dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrMTVNCRB01.86C..X.00:bd05/07/2010:svnSempToshiba:pnIS1414:pvr20ga&ICH9MChipset:rvnSempToshiba:rnIS1414:rvrCRB:cvnSempToshiba:ct10:cvr: dmi.product.name: IS 1414 dmi.product.version: 20ga & ICH9M Chipset dmi.sys.vendor: Semp Toshiba version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
Verified 237-3ubuntu10.24 on Bionic: root@bb:~# systemd-run /usr/bin/env Running as unit: run-r14e6d7c0430841c59697a5c84ded2a88.service root@bb:~# dpkg -l systemd | cat 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 systemd237-3ubuntu10.23 amd64system and service manager root@bb:~# systemd-run /usr/bin/env Running as unit: run-r512450e1e4134a86bc6c65eb4b68d9c3.service root@bb:~# journalctl -e | grep PATH Jun 26 06:54:12 bb env[2830]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Jun 26 06:54:38 bb env[2835]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin root@bb:~# sed -i 's/-backports/-proposed/' /etc/apt/sources.list root@bb:~# apt update -qq 16 packages can be upgraded. Run 'apt list --upgradable' to see them. root@bb:~# apt install -y -qq systemd ... root@bb:~# ls -alh /usr/lib/systemd/system-environment-generators/snapd-env-generator -rw-r--r-- 1 root root 44K Jun 5 06:41 /usr/lib/systemd/system-environment-generators/snapd-env-generator root@bb:~# chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator root@bb:~# reboot Session terminated, terminating shell...rbalint@yogi:~$ lxc shell bb mesg: ttyname failed: No such device root@bb:~# dpkg -l systemd | cat 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 systemd237-3ubuntu10.24 amd64system and service manager root@bb:~# journalctl -e | grep PATH Jun 26 06:54:12 bb env[2830]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Jun 26 06:54:38 bb env[2835]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin root@bb:~# systemd-run /usr/bin/env Running as unit: run-r5a67017348664e9face4a9f084dfcde7.service root@bb:~# journalctl -e | grep PATH Jun 26 06:54:12 bb env[2830]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Jun 26 06:54:38 bb env[2835]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Jun 26 06:59:20 bb env[311]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-pa