[Touch-packages] [Bug 1863733] Re: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later
The MP was approved and I uploaded but it seems Lukasz did the same upload already. => https://launchpad.net/ubuntu/+source/bubblewrap/0.4.0-1ubuntu3 I now marked the MP as rejected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1863733 Title: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later Status in bubblewrap package in Ubuntu: New Status in libcap2 package in Ubuntu: New Status in bubblewrap package in Debian: Unknown Bug description: The bubblewrap upstream-as-root test started failing after libcap2 1:2.31-1 got synced from Debian. The same failure can be seen with 1:2.32-1. I have reproduced the issue locally on focal - when using the focal-proposed version, the aforementioned test fails, where with the release version (1:2.27-1) it passes. It seems to fail here already: bwrap --bind / / --tmpfs /tmp --as-pid-1 --cap-drop CAP_KILL --cap-drop CAP_FOWNER --unshare-pid capsh --print assert_not_file_has_content caps.test '^Current: =.*cap_kill' It looks like the requested caps did not get dropped, as the logs show that both cap_kill and cap_fowner are still there. This is only for the upstream-as-root test, i.e. executing tests/test-run.sh as root. This might be an issue with bubblewrap, but seeing that it all works fine with the release version, it all feels weird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1863733/+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 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: - In all our LXC containers running Bionic Beaver, installing systemd - 237-3ubuntu10.39 results in losing network configuration. + In all our LXC containers running Bionic Beaver, Eoan Ermine or Focal + Fossa, installing the latest systemd package results in losing network + configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. An example is provided, followed by a complete procedure to reproduce the issue. Affected container distributions Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo systemd 240-6ubuntu5.8: OK, not affected Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Example steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB]
[Touch-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation
Since disco these messages are no longer visible. Hence closing this ticket. ** Changed in: console-setup (Ubuntu) Status: Expired => Fix Released ** Changed in: ubuntu-z-systems Status: Won't Fix => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1704929 Title: Repeating "can't open /dev/ttyX: No such device or address" messages during installation Status in Ubuntu on IBM z Systems: Fix Released Status in console-setup package in Ubuntu: Fix Released Bug description: [Impact] console-setup continuously tries to open /dev/tty[1-6] on s390x, when such consoles do not exist on s390x. This can be seen on boot in the output from the initramfs, and during the installer. [Cause] It seems to me that the postinst of the console-setup is incorrect for s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR, z/VM, KVM) [Solution] I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it to... "guess". Usually it should be slcp, but that depends on which consoles are configured/activated in the given KVM. [Testcase] On boot, scroll all the messages and makesure there are no error messages about inability to open /dev/tty* [Original Bug Report] During the installation (z/VM guest and KVM virtual machine) of Ubuntu Server 16.04.1 (and 16.04.2) repeating messages of the form: " Select and install software ... 10% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 20% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 30%... 40% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 50% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 60% can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 90% The system is going down NOW Sent SIGTERM to all processes Sent SIGKILL to all processes Requesting system reboot 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 00 Storage cleared - system reset. 00 zIPL .. " They start to occur when the software gets installed: "Select and install software ... 10% can't open /dev/tty4: No such device or address" And only stop with the final system reboot at the end of the installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+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 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem
Do understand people can get busy, and being grumpy won't help anyone. -- 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/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860806/+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 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc3/ Particularly to test this commit: commit d5ad7a6a7f3c87b278d7e4973b65682be4e588dd Author: Jeff Kirsher Date: Sat Jan 4 23:29:22 2020 -0800 e1000e: Revert "e1000e: Make watchdog use delayed work" This reverts commit 59653e6497d16f7ac1d9db088f3959f57ee8c3db. This is due to this commit causing driver crashes and connections to reset unexpectedly. Signed-off-by: Jeff Kirsher Tested-by: Aaron Brown -- 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/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860806/+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 1864423] Re: Failed test 'default log is not used' with new procps 3.3.16-1
** Changed in: procps (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1864423 Title: Failed test 'default log is not used' with new procps 3.3.16-1 Status in postgresql-common package in Ubuntu: Fix Released Status in procps package in Ubuntu: Invalid Bug description: Since the new procps upload procps | 2:3.3.16-1ubuntu1 | focal-proposed | source, amd64, arm64, armhf, i386, ppc64el, s390x the tests of postgresql-common fail. The issues are: autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - results - - - - - - - - - - run-testsuiteFAIL non-zero exit status 2 autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - stderr - - - - - - - - - - # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 143. # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 154. # Looks like you failed 2 tests of 144. It was retried a few times by different people now and reproduced so we can assume it is a real issues for now. I was running two VMs to compare: $ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --test-name=run-testsuite --apt-pocket=proposed=src:procps --shell postgresql-common_211.dsc -- qemu --qemu-options='-cpu host' --ram-size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img (and the other one without --apt-pocket=proposed=src:procps) The issue reproduced locally in only the one with the new procps. In Debian the latest similar run is https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-common/4279031/log.gz https://ci.debian.net/data/packages/testing/amd64/p/postgresql-common/4279031.log But that is pre-3.3.16 and I wasn't able to find their result with the same combination. Lets mark this bug update-excuse and check if we can find anything in these VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+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 992194] Re: BOM symbols in ru_RU.aff affect some package installation
** Tags added: precise trusty xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hunspell-ru in Ubuntu. https://bugs.launchpad.net/bugs/992194 Title: BOM symbols in ru_RU.aff affect some package installation Status in hunspell-ru package in Ubuntu: Confirmed Status in postgresql-common package in Ubuntu: New Bug description: BOM symbols (http://en.wikipedia.org/wiki/Byte_order_mark) in ru_RU.aff affect some package installation. 1) Ubuntu 12.04 amd64 release 2) hunspell-ru 20120101-1 from postgresql 9.1 installation log: Building PostgreSQL dictionaries from installed myspell/hunspell packages... en_au en_gb en_us en_za ERROR: no ecoding defined in /usr/share/hunspell/ru_RU.aff, ignoring When BOM removed from ru_RU.aff, encoding (UTF8) is recognized and installation processed without errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-ru/+bug/992194/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
1. Added to /etc/X11/Xwrapper.config : needs_root_rights = yes (as instructed in bug 1716857. 2. Open terminal, input "sudo apt install nvidia-driver-390". 3. After installation complete, input "systemctl reboot" to reboot. 4. Screen went blank on reboot, cursor blinking at around the top left corner. 5. Pressed Alt Ctrl F2 to bring up tty2, then input "sudo apt-get remove --purge nvidia-*" to remove nvidia driver. 6. After removal complete, input "systemctl reboot" to reboot. 7. Reboot OK. System OK with Nouveau driver. 8. Ran journalctl to generate attached Summary: bug 1716857 didn't help. ** Attachment added: "boot-1.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331457/+files/boot-1.txt -- 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
to add, after step 4: 4a. i waited a little longer and noticed a jagged dialogue window popped up (attached). i tried to input my password, but neither mouse nor keyboard was functional. i waited again, and later proceeded to resume at step 5. ** Attachment added: "dialogue box.jpeg" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331458/+files/dialogue%20box.jpeg -- 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1864781/+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 1854621] Re: ubuntu 20.04 daily boots with no background, selecting other background has warped picture
booted today's daily on dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550 or system in main report, no background on boot? i rebooted & same. Changing wallpapers works for some, but creates a visual mess for others ** Attachment added: "just changed wallpaper; expected blue for sky is at bottom underneath mess, no mountains.." https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+attachment/5331456/+files/Screenshot%20from%202020-02-27%2004-54-33.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1854621 Title: ubuntu 20.04 daily boots with no background, selecting other background has warped picture Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu 20.04 daily - verified (check disc for defects) prior to boot. dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550) On booting, the 20.04 daily has no background when desktop is loaded? (ie. top panel is there, dock on left side on black screen) When changing background (to any already installed), they are warped when selected and made the bacground as if corrupted (but small image where selection is made looks valid). This issue may relate to video card [radeon] ubuntu@ubuntu:~$ sudo lshw -C video *-display:0 description: VGA compatible controller product: RV516 [Radeon X1300/X1550 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e ioport:dc00(size=256) memory:c-d *-display:1 UNCLAIMED description: Display controller product: RV516 [Radeon X1300/X1550 Series] (Secondary) vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0.1 bus info: pci@:01:00.1 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress bus_master cap_list configuration: latency=0 resources: memory:fe9f-fe9f ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.440 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CasperVersion: 1.432 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 1 11:58:33 2019 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+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 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem
** This bug is no longer a duplicate of bug 1576953 8086:153a e1000e driver failed with error -3 -- 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/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860806/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
I wonder if this is a distant relation to bug 1716857... Can you try this?; https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-418/+bug/1716857/comments/26 ** No longer affects: linux (Ubuntu) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete ** Also affects: systemd (Ubuntu) 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1864781/+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 1864813] Re: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c
Yes, I think I have chance to access the HW and provide details soon. -- 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/1864813 Title: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+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 1864813] Re: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c
OK, I don't think that's explained in the bug description so could you write it there? -- 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/1864813 Title: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+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 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
** Changed in: ibus (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in ibus: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change intentionally requires a change to apparmor to add a unix rule for communicating with the new ibus address. This is in xenial- proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to ensure that the apparmor abstraction is updated and policy recompiled before ibus is restarted. This was omitted from the initial im-config upload which resulted in bug #1588197. Test cases ensuring this is working properly are included above under 'Extended t
[Touch-packages] [Bug 1864839] Re: Background solid color causes noise
*** This bug is a duplicate of bug 1855757 *** https://bugs.launchpad.net/bugs/1855757 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1855757, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1855757 [nvidia] Background image corrupted after standby -- 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/1864839 Title: Background solid color causes noise Status in xorg package in Ubuntu: New Bug description: Setting background to Solid color (Black) causes noise to appear on background (instead of black). This regularly happens on resume from sleep. See also https://www.reddit.com/r/Ubuntu/comments/8ezq2q/strange_graphics_bug_ubuntu_1710_background/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 07:09:26 2020 DistUpgraded: 2018-09-03 16:17:03,502 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-76-generic, x86_64: installed nvidia, 390.116, 4.15.0-88-generic, x86_64: installed virtualbox, 5.2.34, 4.15.0-76-generic, x86_64: installed virtualbox, 5.2.34, 4.15.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6593] InstallationDate: Installed on 2017-10-27 (852 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: MSI MS-7A62 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-09-03 (540 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: Z270 GAMING M3 (MS-7A62) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd07/10/2017:svnMSI:pnMS-7A62:pvr1.0:rvnMSI:rnZ270GAMINGM3(MS-7A62):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A62 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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/xorg/+bug/1864839/+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 1864917] Re: Screen artifacts after hibernate
*** This bug is a duplicate of bug 1855757 *** https://bugs.launchpad.net/bugs/1855757 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1855757, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1855757 [nvidia] Background image corrupted after standby -- 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/1864917 Title: Screen artifacts after hibernate Status in xorg package in Ubuntu: New Bug description: After waking up from hibernate mode, screen has broken. There are screen artifacts instead of main screen ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 20:53:26 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-02-17 (8 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ECS H61H2-M12 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=4e5f8156-c16b-4d91-94b4-54f3fd0efccd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-M12 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd10/27/2011:svnECS:pnH61H2-M12:pvr1.0:rvnECS:rnH61H2-M12:rvr1.0:cvnECS:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: H61H2-M12 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: ECS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864917/+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 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
@Jamie: The code, which changes the abstract socket path from 'unix:tmpdir=/tmp/ibus' to 'unix:tmpdir=$XDG_CACHE_HOME/ibus', was uploaded to focal via ibus 1.5.21-5ubuntu1 (unix-socket-path.patch). Mentioned it on bug #1856738 too. Closing the ibus (ubuntu) task on this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in ibus: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: In Progress Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change intentionally requires a change to apparmor to add a unix rule for communicating with the new ibus address. This is in xenial- proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to ensure that the apparmor abstraction is updated and policy rec
[Touch-packages] [Bug 1856738] Re: access always denied when using @{HOME} tunable in peer_addr for abstract socket
@Jamie: The code, which changes the abstract socket path from 'unix:tmpdir=/tmp/ibus' to 'unix:tmpdir=$XDG_CACHE_HOME/ibus', was uploaded to focal via ibus 1.5.21-5ubuntu1 (unix-socket-path.patch). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1856738 Title: access always denied when using @{HOME} tunable in peer_addr for abstract socket Status in AppArmor: Triaged Status in apparmor package in Ubuntu: Triaged Bug description: With this profile: #include profile test { #include # Parses but always denied unix (connect, receive, send) type=stream peer=(addr="@@{HOME}/.cache/ibus/dbus-*"), # parses and allows access # unix (connect, receive, send) #type=stream #peer=(addr="@/home/*/.cache/ibus/dbus-*"), } In one terminal I start a server: $ ./abstract-server stream /home/jamie/.cache/ibus/dbus-foo Then in another terminal do: $ sudo apparmor_parser -r /tmp/apparmor.profile && aa-exec -p test -- ./abstract-client stream /home/jamie/.cache/ibus/dbus-foo hi connect() failed With the following denial (and no output from the server terminal): apparmor="DENIED" operation="connect" profile="test" pid=3665 comm="abstract-client" family="unix" sock_type="stream" protocol=0 requested_mask="send receive connect" denied_mask="send connect" addr=none peer_addr="@/home/jamie/.cache/ibus/dbus-fo" peer="unconfined" Commenting out the @{HOME} rule and uncommenting the /home/* rule, it works: $ sudo apparmor_parser -r /tmp/apparmor.profile && aa-exec -p test -- ./abstract-client stream /home/jamie/.cache/ibus/dbus-foo hi MESSAGE FROM SERVER: received message number 1 (with the server displaying 'MESSAGE FROM CLIENT: hi') Attached is the server and client code. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1856738/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@hui.wang, I confirm that now everything works as expected, thanks for your outstanding work. Just to be understand a bit more the release cycle, what is the plan to integrate all the things we did in this thread into the 18.04 standard repository ? Is already planned or for now it's better to just stick with the proposed repository ? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1864274] Re: crunchy pixels
Yes, that mesa bug looks about right. Here's a photo I snapped of firefox's address bar. I hit 'a', which brought up history entries in a drop-down list. When I deleted the 'a', the history list is removed, and these pixels were momentarily visible during the repainting. The static view of firefox is normal enough. The pixeljunk only happens on some screen changes, but not all. Thanks ** Attachment added: "IMG_20200226_154451.jpg" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1864274/+attachment/5331419/+files/IMG_20200226_154451.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1864274 Title: crunchy pixels Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: Hello, after upgrading firefox (and many other packages) on focal today, I've got some video artifacts in firefox. When typing in text boxes and text fields, the new character is drawn very slowly, pixel-by-pixel, and isn't complete until the cursor has moved on. When larger portions of the screen are updated, it looks a lot like the entire window is being run through a video codec or you can see parts of the video memory from other processes. (But it looks more deliberate and predictable than either of these descriptions.) So far Firefox is the only application I've found that is affected. urxvt, libreoffice, xfontsel, glxgears all seem to work as expected. I did get cairo package update today, but the changelog is just: pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium * No-change rebuild with fixed binutils on arm64. -- Matthias Klose Sat, 08 Feb 2020 11:15:23 + And an xorg update: xorg (1:7.7+19ubuntu14) focal; urgency=medium * No-change rebuild with fixed binutils on arm64. -- Matthias Klose Sat, 08 Feb 2020 11:21:28 + So I don't believe these are involved. 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 73.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sarnold3296 F pulseaudio /dev/snd/controlC0: sarnold3296 F pulseaudio BuildID: 20200217142647 Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,0012 HDA:8086280b,80860101,0010' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 Channel: Unavailable Date: Sat Feb 22 05:41:10 2020 ForcedLayersAccel: False IncompatibleExtensions: Pentadactyl - pentadac...@dactyl.googlecode.com English (GB) Language Pack - langpack-en...@firefox.mozilla.org English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} IpRoute: default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100 10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1 192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:737 PrefSources: prefs.js ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use) RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago) dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET69W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_T
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@Paolo, The kernel you installed is too old, we integrated Intel's kernel patch to switch to use snd-hda-codec-hdmi instead of soc/codecs/hdac_hdmi.c. Please update your kernel to Ubuntu-5.3.0-40.32 then redo the test. And please don't install Ubuntu-5.3.0-41.33, there is some regression in the -41 kernel. And all these issues will be addressed in the -42 kernel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1864824] Re: BlueZ 5.53 release
This bug was fixed in the package bluez - 5.53-0ubuntu1 --- bluez (5.53-0ubuntu1) focal; urgency=medium * New upstream release 5.53 (LP: #1864824) - Fix issue with handling unregistration for advertisment. - Fix issue with A2DP and handling recovering process. - Fix issue with udpating input device information. - Add support for loading blocked keys. -- Daniel van Vugt Wed, 26 Feb 2020 17:57:54 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1864824 Title: BlueZ 5.53 release Status in bluez package in Ubuntu: Fix Released Bug description: Release BlueZ 5.53 to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1864824/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
the synaptics driver is unmaintained upstream, so I'd suggest anyone suffering from this to uninstall it and verify that -libinput is installed ** Package changed: xorg (Ubuntu) => xserver-xorg-input-synaptics (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/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1574667/+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 645404] Re: Support Private PPAs
gave up on the MR corresponding to this bug. moved devel work into https://code.launchpad.net/~ubuntu-support-team/software-properties/+git/software-properties daily builds at: https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/add-apt-repository if anyone is interested in this please feel free to test with that ppa and let me know if it works and/or if there are any issues. ** Changed in: software-properties (Ubuntu Eoan) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: software-properties (Ubuntu Disco) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: software-properties (Ubuntu Cosmic) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: software-properties (Ubuntu Bionic) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: software-properties (Ubuntu) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: software-properties (Ubuntu Eoan) Status: In Progress => Confirmed ** Changed in: software-properties (Ubuntu Disco) Status: In Progress => Confirmed ** Changed in: software-properties (Ubuntu Cosmic) Status: In Progress => Won't Fix ** Changed in: software-properties (Ubuntu Disco) Status: Confirmed => Won't Fix ** Changed in: software-properties (Ubuntu Bionic) Status: In Progress => Confirmed ** Changed in: software-properties (Ubuntu) Status: In Progress => Confirmed ** Also affects: software-properties (Ubuntu Focal) Importance: Medium Status: Confirmed -- 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/645404 Title: Support Private PPAs Status in software-properties package in Ubuntu: Confirmed Status in software-properties source package in Bionic: Confirmed Status in software-properties source package in Cosmic: Won't Fix Status in software-properties source package in Disco: Won't Fix Status in software-properties source package in Eoan: Confirmed Status in software-properties source package in Focal: Confirmed Bug description: Software properties add-apt-repository currently does not support adding private PPAs. software-properties should connect to the API and observe that it gets permission denied trying to read the ppa. Then it can reconnect to the API asking for authentication, which will open a browser window where you can do the openid ritual. Then using that token it ought to be possible for it to get the password etc. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+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 1864708] Re: Mount unit fails but systemctl status shows success
> I don't know why, but this doesn't result in the "Mountpoint not empty" error (or any error/warning for that matter). I thought systemd should be able to figure out the order of nested mounts, not sure why it's not working here. because systemd doesn't mount zfs mounts; zfs is a "magical" filesystem that mounts itself because it's just so smart and special. All zfs mounts are performed by 'zfs-mount.service' and systemd only creates corresponding mount units after zfs performs the mounts (i.e. the systemd mount units for zfs mounts only indicate the mount state, they don't actually perform the mounting). ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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/1864708 Title: Mount unit fails but systemctl status shows success Status in systemd package in Ubuntu: Invalid Bug description: I have this mount unit # cat /etc/systemd/system/srv-cctvstore.mount [Unit] Description=Drive for CCTVstore [Mount] What=/dev/disk/by-id/ata-ST2000NM0011_Z1P21NQ7-part1 Where=/srv/cctvstore Type=ext4 Options=defaults [Install] WantedBy=multi-user.target On boot systemd thinks it is mounted: $ systemctl status srv-cctvstore.mount ● srv-cctvstore.mount - Drive for CCTVstore Loaded: loaded (/etc/systemd/system/srv-cctvstore.mount; enabled; vendor preset: enabled) Active: active (mounted) since Tue 2020-02-25 22:37:16 SAST; 48s ago Where: /srv/cctvstore What: /dev/sda1 Process: 1294 ExecMount=/bin/mount /dev/disk/by-id/ata-ST2000NM0011_Z1P21NQ7-part1 /srv/cctvstore -t ext4 -o defaults (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/srv-cctvstore.mount Feb 25 22:37:16 kluis systemd[1]: Mounting Drive for CCTVstore... Feb 25 22:37:16 kluis systemd[1]: Mounted Drive for CCTVstore. and the mount command seems to agree $ mount | grep cctv /dev/sda1 on /srv/cctvstore type ext4 (rw,relatime) but the mountpoint is empty: $ ls -al /srv/cctvstore/ total 1 drwxr-xr-x 2 root root 2 Dec 7 22:51 . drwxr-xr-x 4 root root 4 Dec 7 22:51 .. and umount thinks it is not mounted: $ sudo umount /srv/cctvstore [sudo] password for johann: umount: /srv/cctvstore: not mounted. journalctl doesn't report any funnies: $ journalctl -u srv-cctvstore.mount -- Logs begin at Tue 2020-02-25 22:37:16 SAST, end at Tue 2020-02-25 22:41:43 SAST. -- Feb 25 22:37:16 kluis systemd[1]: Mounting Drive for CCTVstore... Feb 25 22:37:16 kluis systemd[1]: Mounted Drive for CCTVstore. but mounting by hand works: $ sudo mount /dev/sda1 /srv/cctvstore johann@kluis:~$ ls -al /srv/cctvstore total 3157 drwxrwxrwx 7 root root 4096 Dec 9 22:27 . drwxr-xr-x 4 root root 4 Dec 7 22:51 .. drwxr-xr-x 14 165569 1655694096 Dec 10 23:10 events drwxr-xr-x 2 165569 1655694096 Dec 7 22:59 images drwxr-xr-x 2 165569 1655694096 Dec 7 23:01 logs drwx-- 2 root root 16384 Dec 7 22:47 lost+found drwxrwxr-x 2 165569 165569 3194880 Feb 25 22:25 mlevents I am unsure where to go next, any help appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 Date: Tue Feb 25 22:27:59 2020 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-5.3.0-40-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: E3C232D2I dmi.board.vendor: ASRockRack 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.:bvrP2.50:bd03/07/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnE3C232D2I:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2020-01-0
[Touch-packages] [Bug 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
Fair enough, I will contact the web site maintainer. However, regarding this: >You can override this via command-line, a system config file, or a local >config file + environment variable pointing to it. > >On Ubuntu 20.04 LTS: > >man SSL_CTX_get_security_level.3ssl 1) I searched high, low, and sideways, and couldn't find any documentation of how to override this via a config file or environment variable. Regarding command line, I imagine that is going to be different for each program, and I did manage to figure out how to do it for curl, but it took a huge amount of educated effort that the vast majority of users are not going to be able to figure out. 2) I don't know what deb the man pages for the OpenSSL API are in, but whichever one it is, it's not in the package install set that most people get. That man page is not available on my system, for example. -- 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/1864689 Title: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox Status in openssl package in Ubuntu: New Bug description: openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to connect to. Reproduce with: `curl -v https://www.toodledo.com/' or: `openssl s_client -connect www.toodledo.com:443` or: `python3 -c 'import requests; requests.get("https://www.toodledo.com/";)'` or: `wget https://www.toodledo.com/` These worked in Ubuntu 19.10 and don't work in 20.04. I've tried all sorts of things to debug this further and I've just run into walls. I hope someone who understands more about this stuff will be able to figure it out. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssl 1.1.1d-2ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 25 13:01:22 2020 InstallationDate: Installed on 2019-08-16 (192 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: openssl UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+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 1864708] Re: Mount unit fails but systemctl status shows success
So I spent a bunch more time on this tonight, and you can close this, it's not a systemd bug. Basically the problem was an ordering issue between this mount unit and a zfs mount unit responsible for providing /srv. What was happening was the /srv/cctvstore was getting mounted first and then /srv was getting mounted on top, obscuring the /srv/cctvstore mount underneath. I don't know why, but this doesn't result in the "Mountpoint not empty" error (or any error/warning for that matter). I thought systemd should be able to figure out the order of nested mounts, not sure why it's not working here. Apologies for wasting your time, and thanks for looking into this. If anyone runs into this in the future, this is what my mount unit ended up looking like: [Unit] Description=Drive for CCTVstore After=zfs.target Requires=srv.mount [Mount] What=/dev/disk/by-id/ata-ST2000NM0011_Z1P21NQ7-part1 Where=/srv/cctvstore Type=ext4 Options=defaults [Install] WantedBy=lxd.service - $ systemctl list-units -t mount UNIT LOAD ACTIVE SUB DESCRIPTION -.mount loaded active mounted Root Mount dev-hugepages.mount loaded active mounted Huge Pages File System dev-mqueue.mount loaded active mounted POSIX Message Queue File System home-johann.mount loaded active mounted /home/johann home.mount loaded active mounted /home proc-sys-fs-binfmt_misc.mount loaded active mounted Arbitrary Executable File Formats File System run-user-1000.mount loaded active mounted /run/user/1000 srv-cctvstore.mount loaded active mounted Drive for CCTVstore srv.mount loaded active mounted /srv sys-fs-fuse-connections.mount loaded active mounted FUSE Control File System sys-kernel-config.mount loaded active mounted Kernel Configuration File System sys-kernel-debug.mount loaded active mounted Kernel Debug File System var-cache.mount loaded active mounted /var/cache var-games.mount loaded active mounted /var/games var-lib-lxcfs.mount loaded active mounted /var/lib/lxcfs var-lib-lxd-devices-storj-disk.aadisable.sys\x2dmodule\x2dapparmor\x2dparameters\x2denabled.mount loaded active mounted /var/lib/lxd/devices/storj/disk.aadisable.sys-module-apparmor-parameters-enabled var-lib-lxd-devices-zm-disk.disk.srv\x2dcctvstore.mount loaded active mounted /var/lib/lxd/devices/zm/disk.disk.srv-cctvstore var-lib-lxd-devlxd.mount loaded active mounted /var/lib/lxd/devlxd var-lib-lxd-shmounts.mount loaded active mount
[Touch-packages] [Bug 1864917] [NEW] Screen artifacts after hibernate
Public bug reported: After waking up from hibernate mode, screen has broken. There are screen artifacts instead of main screen ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 20:53:26 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-02-17 (8 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ECS H61H2-M12 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=4e5f8156-c16b-4d91-94b4-54f3fd0efccd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-M12 dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd10/27/2011:svnECS:pnH61H2-M12:pvr1.0:rvnECS:rnH61H2-M12:rvr1.0:cvnECS:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: H61H2-M12 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: ECS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption eoan ubuntu ** Attachment added: "Screenshot from 2020-02-26 21-00-01.png" https://bugs.launchpad.net/bugs/1864917/+attachment/5331380/+files/Screenshot%20from%202020-02-26%2021-00-01.png -- 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/1864917 Title: Screen artifacts after hibernate Status in xorg package in Ubuntu: New Bug description: After waking up from hibernate mode, screen has broken. There are screen artifacts instead of main screen ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other c
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
I found some more interesting logs, while switching the hdmi1-3 output: Feb 26 20:35:00 spark-carbon-cto kernel: [17745.742041] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=206059 end=206060) time 138 us, min 1431, max 1439, scanline start 1428, end 1440 Feb 26 20:35:01 spark-carbon-cto slack.desktop[26636]: [02/26/20, 20:35:01:025] info: [DND] (T025L5BAC) Checking for changes in DND status for the following members: U02Q8NN0E,U025P7R5R,U03KJ3DUQ,U02Q7NP19,U03HD1F72,U025P3QLV,U03BQJS0V,U025P6YRF,UNF2WRT7H,U632EB0SF,U03BQM6CV,U288F67HS,UKFNC48SX,U3N5QH4P3,U0D78EXC4,U03V5EH0K Feb 26 20:35:01 spark-carbon-cto slack.desktop[26636]: [02/26/20, 20:35:01:026] info: [DND] (T025L5BAC) Will check for changes in DND status again in 5 minutes Feb 26 20:35:01 spark-carbon-cto CRON[2554]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Feb 26 20:35:01 spark-carbon-cto kernel: [17746.899506] wlp0s20f3: Limiting TX power to 20 (23 - 3) dBm as advertised by 90:35:6e:e2:d6:3c Feb 26 20:35:05 spark-carbon-cto kernel: [17750.175668] wlp0s20f3: Limiting TX power to 17 (23 - 6) dBm as advertised by 90:35:6e:e2:d6:3c Feb 26 20:35:15 spark-carbon-cto pulseaudio[2923]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Feb 26 20:35:15 spark-carbon-cto pulseaudio[2923]: [pulseaudio] alsa-ucm.c: Failed to enable ucm device HDMI1 Feb 26 20:35:15 spark-carbon-cto pulseaudio[2923]: [pulseaudio] source.c: Default and alternate sample rates are the same. Feb 26 20:35:15 spark-carbon-cto rtkit-daemon[1436]: Supervising 1 threads of 1 processes of 1 users. Feb 26 20:35:15 spark-carbon-cto rtkit-daemon[1436]: Successfully made thread 2562 of process 2923 (n/a) owned by '1002' RT at priority 5. Feb 26 20:35:15 spark-carbon-cto rtkit-daemon[1436]: Supervising 2 threads of 1 processes of 1 users. Feb 26 20:35:15 spark-carbon-cto pulseaudio[2923]: [pulseaudio] source.c: Default and alternate sample rates are the same. Feb 26 20:35:15 spark-carbon-cto rtkit-daemon[1436]: Supervising 2 threads of 1 processes of 1 users. Feb 26 20:35:15 spark-carbon-cto rtkit-daemon[1436]: Successfully made thread 2564 of process 2923 (n/a) owned by '1002' RT at priority 5. Feb 26 20:35:15 spark-carbon-cto rtkit-daemon[1436]: Supervising 3 threads of 1 processes of 1 users. Feb 26 20:35:15 spark-carbon-cto gsd-media-keys[3115]: Unable to get default source Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] alsa-ucm.c: Failed to enable ucm device HDMI2 Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] source.c: Default and alternate sample rates are the same. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 1 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Successfully made thread 2565 of process 2923 (n/a) owned by '1002' RT at priority 5. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 2 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] source.c: Default and alternate sample rates are the same. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 2 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Successfully made thread 2566 of process 2923 (n/a) owned by '1002' RT at priority 5. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 3 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto gsd-media-keys[3115]: Unable to get default source Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] alsa-ucm.c: Failed to enable ucm device HDMI1 Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] source.c: Default and alternate sample rates are the same. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 1 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Successfully made thread 2567 of process 2923 (n/a) owned by '1002' RT at priority 5. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 2 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] source.c: Default and alternate sample rates are the same. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 2 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Successfully made thread 2568 of process 2923 (n/a) owned by '1002' RT at priority 5. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 3 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto gsd-media-keys[3115]: Unable to get default source Feb 26 20:35:18 spark-carbon-cto pulseaudio[2923
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
The previous comment missed the attachment. ** Attachment added: "pactl-list" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5331364/+files/pactl-list -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
** Attachment added: "alsa-info after attaching an hdmi tv" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5331363/+files/alsa-info.txt.VGDIH3ZkNA -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
pactl list after attaching an hdmi tv -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
And this one is the only hdmi-related thing i can found on dmesg: "[17231.810042] HDMI HDA Codec ehdaudio0D2: hdac_hdmi_present_sense: disconnect for pin:port 5:0" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Just for the sake of clarity, this is what i see from gnome audio settings. ** Attachment added: "Screenshot from 2020-02-26 20-31-47.png" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5331365/+files/Screenshot%20from%202020-02-26%2020-31-47.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1863414] Re: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" o
** Tags added: champagne -- 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/1863414 Title: Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used" on simple APT usage Status in python3-defaults package in Ubuntu: Confirmed Status in python3.8 package in Ubuntu: Won't Fix Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Run regular APT task such as `sudo apt dist-upgrade` 3. Wait it to finish Expected results: * APT runs without any warnings and/or errors Actual results: * APT runs with many python-related warnings like >``` >/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported >in binary mode, the default buffer size will be used > self.stdin = io.open(p2cwrite, 'wb', bufsize) > >``` Full output below: ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: ruby-json ruby-pg ruby-sequel ruby-sequel-pg Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: kdevelop55-libs libxentoolcore1 ubuntu-mate-wallpapers-focal The following packages will be upgraded: atril atril-common debootstrap dmeventd dmsetup dnsmasq-base engrampa engrampa-common fwupd fwupd-signed gir1.2-atrildocument-1.5.0 gir1.2-atrilview-1.5.0 gir1.2-freedesktop gir1.2-glib-2.0 gir1.2-pluma-1.0 initramfs-tools initramfs-tools-bin initramfs-tools-core iproute2 isc-dhcp-client isc-dhcp-common jekyll k3b k3b-data k3b-i18n kdevelop kdevelop-data libatrildocument-dev libatrildocument3 libatrilview-dev libatrilview3 libdevmapper-event1.02.1 libdevmapper1.02.1 libdistro-info-perl libfwupd2 libfwupdplugin1 libgirepository-1.0-1 libk3b7 libk3b7-extracodecs liblvm2cmd2.03 libmate-sensors-applet-plugin-dev libmate-sensors-applet-plugin0 libmate-slab0 libmate-window-settings-dev libmate-window-settings1 libmatedict-dev libmatedict6 libmysqlclient21 libmysqlclient21:i386 libvirt-clients libvirt-daemon libvirt-daemon-driver-qemu libvirt-daemon-driver-storage-rbd libvirt-daemon-system libvirt-daemon-system-systemd libvirt0 libxenstore3.0 libxmlgraphics-commons-java lvm2 mate-applets mate-applets-common mate-common mate-control-center mate-control-center-common mate-core mate-desktop-environment mate-desktop-environment-core mate-desktop-environment-extra mate-desktop-environment-extras mate-dock-applet mate-media mate-media-common mate-netbook mate-netbook-common mate-notification-daemon mate-notification-daemon-common mate-power-manager mate-power-manager-common mate-screensaver mate-screensaver-common mate-sensors-applet mate-sensors-applet-common mate-sensors-applet-nvidia mate-system-monitor mate-system-monitor-common mate-terminal mate-terminal-common mate-user-share mate-user-share-common mate-utils mate-utils-common maxima maxima-doc maxima-share mozo nano pluma pluma-common pluma-dev pluma-doc plymouth-theme-ubuntu-mate-logo plymouth-theme-ubuntu-mate-text python-caja-common python3-caja python3-distro-info python3-macaroonbakery qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils ubuntu-mate-artwork ubuntu-mate-default-settings ubuntu-mate-icon-themes ubuntu-mate-lightdm-theme ubuntu-mate-live-settings ubuntu-mate-themes ubuntu-mate-wallpapers ubuntu-mate-wallpapers-artful ubuntu-mate-wallpapers-bionic ubuntu-mate-wallpapers-common ubuntu-mate-wallpapers-complete ubuntu-mate-wallpapers-cosmic ubuntu-mate-wallpapers-disco ubuntu-mate-wallpapers-eoan ubuntu-mate-wallpapers-legacy ubuntu-mate-wallpapers-photos ubuntu-mate-wallpapers-utopic ubuntu-mate-wallpapers-vivid ubuntu-mate-wallpapers-wily ubuntu-mate-wallpapers-xenial ubuntu-mate-wallpapers-yakkety ubuntu-mate-wallpapers-zesty umbrello 136 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 215 MB of archives. After this operation, 12,8 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu focal/universe amd64 mate-common all 1.24.0-1ubuntu1 [17,0 kB] ... Get:139 http://archive.ubuntu.com/ubuntu focal/universe amd64 mate-dock-applet amd64 20.04.0-0ubuntu1 [91,8 kB] Fetched 215 MB in 4min 4s (882 kB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 961594 files and directories cur
[Touch-packages] [Bug 887079] Re: Software Sources shows codenames not version numbers
** Merge proposal unlinked: https://code.launchpad.net/~osomon/software-properties/+git/software-properties/+merge/379346 -- 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/887079 Title: Software Sources shows codenames not version numbers Status in software-properties package in Ubuntu: In Progress Bug description: In the updates tab software-properties shows codenames such as 'oneiric-updates' and 'oneiric-proposed'. As I understand it we shouldn't really show the codename to the user. It also seems somewhat redundant, it's not like that screen would ever have anything other than $current_release-* in it. I can see why the 3rd party sources might display codenames as users may (for whatever reason) want to add the source for an older (or newer) release on a 3rd party site to get an app. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: software-properties-gtk 0.81.10 Uname: Linux 3.1.0-999-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Nov 7 11:20:31 2011 PackageArchitecture: all ProcEnviron: PATH=(custom, user) SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/887079/+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 992194] Re: BOM symbols in ru_RU.aff affect some package installation
** Also affects: postgresql-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hunspell-ru in Ubuntu. https://bugs.launchpad.net/bugs/992194 Title: BOM symbols in ru_RU.aff affect some package installation Status in hunspell-ru package in Ubuntu: Confirmed Status in postgresql-common package in Ubuntu: New Bug description: BOM symbols (http://en.wikipedia.org/wiki/Byte_order_mark) in ru_RU.aff affect some package installation. 1) Ubuntu 12.04 amd64 release 2) hunspell-ru 20120101-1 from postgresql 9.1 installation log: Building PostgreSQL dictionaries from installed myspell/hunspell packages... en_au en_gb en_us en_za ERROR: no ecoding defined in /usr/share/hunspell/ru_RU.aff, ignoring When BOM removed from ru_RU.aff, encoding (UTF8) is recognized and installation processed without errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-ru/+bug/992194/+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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
Sponsored by dgadomski. Unsubscribing sts-sponsor team. Thanks for your contribution Seyeong. Thanks for the sponsoring Dariusz. - Eric -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: In Progress Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]:
[Touch-packages] [Bug 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem
*** This bug is a duplicate of bug 1576953 *** https://bugs.launchpad.net/bugs/1576953 Bug 1576953 I have latest BIOS for Optiplex 7010 which is A29. This does not help. Furthermore, looking at bug 1576953 I can clearly see a response to questions being asked. This worthless site is no more that an content mill closed to the general public as every time I have presented any questions I get absolutely NO RESPONSE. So now I go from 19.04 to 18.04 as per worthless Paul White recommendation and have since then been talking to myself and the worthless Ubuntu Bot to which at this point my only hope is that people will read my comments and realize that only the chosen few will get any response from this worthless web site. -- 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/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860806/+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 1861705] Re: The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information.
*** This bug is a duplicate of bug 1861631 *** https://bugs.launchpad.net/bugs/1861631 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- 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/1861705 Title: The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information. Status in apt package in Ubuntu: Confirmed Bug description: ~$ sudo apt update && sudo apt upgrade && sudo apt dist-upgrade OK:1 http://security.ubuntu.com/ubuntu focal-security InRelease OK:2 http://archive.canonical.com/ubuntu focal InRelease OK:3 http://de.archive.ubuntu.com/ubuntu focal InRelease OK:4 http://de.archive.ubuntu.com/ubuntu focal-updates InRelease OK:5 http://de.archive.ubuntu.com/ubuntu focal-backports InRelease The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 1.9.8 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Mon Feb 3 17:48:43 2020 InstallationDate: Installed on 2020-01-16 (17 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to focal on 2020-01-21 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1861705/+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 1863733] Re: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/bubblewrap/+git/bubblewrap/+merge/379880 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1863733 Title: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later Status in bubblewrap package in Ubuntu: New Status in libcap2 package in Ubuntu: New Status in bubblewrap package in Debian: Unknown Bug description: The bubblewrap upstream-as-root test started failing after libcap2 1:2.31-1 got synced from Debian. The same failure can be seen with 1:2.32-1. I have reproduced the issue locally on focal - when using the focal-proposed version, the aforementioned test fails, where with the release version (1:2.27-1) it passes. It seems to fail here already: bwrap --bind / / --tmpfs /tmp --as-pid-1 --cap-drop CAP_KILL --cap-drop CAP_FOWNER --unshare-pid capsh --print assert_not_file_has_content caps.test '^Current: =.*cap_kill' It looks like the requested caps did not get dropped, as the logs show that both cap_kill and cap_fowner are still there. This is only for the upstream-as-root test, i.e. executing tests/test-run.sh as root. This might be an issue with bubblewrap, but seeing that it all works fine with the release version, it all feels weird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1863733/+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 1864623] Re: apt-get attempts to download Packages.xz which is not InRelease and does not exist
OK, apparently the repository Packages.bz2 had not updated, but Packages.gz and Packages had. It seems to have been fixed now. -- 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/1864623 Title: apt-get attempts to download Packages.xz which is not InRelease and does not exist Status in apt package in Ubuntu: Invalid Bug description: When trying to install the latest virtualbox-6.0 from virtualbox.org, we got a failure: Err:1 http://download.virtualbox.org/virtualbox/debian xenial/contrib amd64 virtualbox-6.0 amd64 6.0.16-135674~Ubuntu~xenial 404 Not Found E: Failed to fetch http://download.virtualbox.org/virtualbox/debian/pool/contrib/v/virtualbox-6.0/virtualbox-6.0_6.0.16-135674~Ubuntu~xenial_amd64.deb 404 Not Found We expected that this was a case of `apt-get update` not having been run before `apt-get install`, but turns out it's a bit more interesting: apt-get update fetched the following files: ubuntu@ubuntu:~$ apt-get --print-uris update |grep virtualbox 'http://download.virtualbox.org/virtualbox/debian/dists/xenial/InRelease' download.virtualbox.org_virtualbox_debian_dists_xenial_InRelease 0 'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/binary-amd64/Packages.xz' download.virtualbox.org_virtualbox_debian_dists_xenial_contrib_binary-amd64_Packages 0 'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/binary-all/Packages.xz' download.virtualbox.org_virtualbox_debian_dists_xenial_contrib_binary-all_Packages 0 'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/i18n/Translation-en.xz' download.virtualbox.org_virtualbox_debian_dists_xenial_contrib_i18n_Translation-en 0 http://download.virtualbox.org/virtualbox/debian/dists/xenial/InRelease returns 200 and lists a bunch of Packages lists. However, it does *not* list contrib/binary-amd64/Packages.xz, only: - contrib/binary-amd64/Packages - contrib/binary-amd64/Packages.gz - contrib/binary-amd64/Packages.bz2 For some reason, apt still attempts to download the .xz files, and does not even report an error for them! Trying to download the file locally, I get a 404, but with an HTML error page as the content: $ curl -v 'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/binary-amd64/Packages.xz' | head -n 20 % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 2.22.40.42... * TCP_NODELAY set * Connected to download.virtualbox.org (2.22.40.42) port 80 (#0) > GET /virtualbox/debian/dists/xenial/contrib/binary-amd64/Packages.xz HTTP/1.1 > Host: download.virtualbox.org > User-Agent: curl/7.58.0 > Accept: */* > 0 00 00 0 0 0 --:--:-- 0:00:02 --:--:-- 0< HTTP/1.1 404 Not Found < Accept-Ranges: bytes < Content-Type: text/html < ETag: "477d9862374177c810b0b7d73b4f1e53:1531792454.541174" < Last-Modified: Wed, 31 Aug 2011 20:28:54 GMT < Server: AkamaiNetStorage < Content-Length: 7073 < Date: Tue, 25 Feb 2020 09:08:16 GMT < Connection: keep-alive < { [7073 bytes data] 100 7 Error Page 404 http://download.oracle.com/index.html"; /> I think it's a bug that: a) apt tries to download Packages files not listed in InRelease b) apt does not report errors on 404 it gets when downloading them It is of course possible that apt get a *different* InRelease and a *different* response when trying to download the .xz files, but that seems unlikely. If you want to, I can try to confirm the actual network traffic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1864623/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
Thanks Juan! #32 fixed the issue for me. ASUS VivoBook S14 (S430F) running Ubuntu 18.04.4 LTS. This issue was driving me crazy, it was impossible (and quite dangerous) trying to work while fighting the pointer. -- 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/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1864836] Re: package language-pack-gnome-fr 1:18.04+20180712 failed to install/upgrade: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.mo'
** Description changed: ubuntu 18.04 checking in software center error and abortion ProblemType: Package DistroRelease: Ubuntu 18.04 Package: language-pack-gnome-fr 1:18.04+20180712 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Feb 26 12:02:15 2020 DuplicateSignature: - package:language-pack-gnome-fr:1:18.04+20180712 - Replacing files in old package language-pack-fr-base (1:18.04+20180712) ... - dpkg: error processing archive /tmp/apt-dpkg-install-uFbaQU/09-language-pack-fr_1%3a18.04+20200123_all.deb (--unpack): - unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/JabberBot.mo' before installing new version: Input/output error + package:language-pack-gnome-fr:1:18.04+20180712 + Replacing files in old package language-pack-fr-base (1:18.04+20180712) ... + dpkg: error processing archive /tmp/apt-dpkg-install-uFbaQU/09-language-pack-fr_1%3a18.04+20200123_all.deb (--unpack): + unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/JabberBot.mo' before installing new version: Input/output error ErrorMessage: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: - dpkg 1.19.0.5ubuntu2.3 - apt 1.6.12 + dpkg 1.19.0.5ubuntu2.3 + apt 1.6.12 SourcePackage: language-pack-gnome-fr Title: package language-pack-gnome-fr 1:18.04+20180712 failed to install/upgrade: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-fr in Ubuntu. https://bugs.launchpad.net/bugs/1864836 Title: package language-pack-gnome-fr 1:18.04+20180712 failed to install/upgrade: unable to make backup link of './usr/share/locale- langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error Status in language-pack-gnome-fr package in Ubuntu: New Bug description: ubuntu 18.04 checking in software center error and abortion ProblemType: Package DistroRelease: Ubuntu 18.04 Package: language-pack-gnome-fr 1:18.04+20180712 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Feb 26 12:02:15 2020 DuplicateSignature: package:language-pack-gnome-fr:1:18.04+20180712 Replacing files in old package language-pack-fr-base (1:18.04+20180712) ... dpkg: error processing archive /tmp/apt-dpkg-install-uFbaQU/09-language-pack-fr_1%3a18.04+20200123_all.deb (--unpack): unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/JabberBot.mo' before installing new version: Input/output error ErrorMessage: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: language-pack-gnome-fr Title: package language-pack-gnome-fr 1:18.04+20180712 failed to install/upgrade: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-fr/+bug/1864836/+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 1251228] Re: unattended-upgrade doesn't upgrade packages pinned to version
This bug was fixed in the package unattended-upgrades - 1.18 --- unattended-upgrades (1.18) experimental; urgency=medium [ louib ] * Update blacklist translations * Fix syntax in template conf files [ Balint Reczey ] * Keep mypy 0.761 happy * test: Create empty dirs to save kept packages list to them * Log explanation about kept back packages (LP: #1850964) (Closes: #945837, #903875) * Use GitHub Actions for CI instead of Travis. Run tests in Ubuntu Focal release because older releases don't have the needed python-apt version. * debian/tests/common-functions: Use backported python-apt from a PPA on Eoan * debian/tests: Skip upgrade-between-snapshots test. Python-apt's version is sid is too low for unattended-upgrades to work. * Use apt_pkg.Hashes instead of deprecated apt_pkg.md5sum() * autopkgtest: Skip upgrate-all-security in sid because buster can't be tested * Make allowed_origins, blacklist and whitelist attributes of UnattendedUpgradesCache * Make strict_whitelist attribute of UnattendedUpgradesCache * Apply pinning to disable not allowed origins and honor blacklist/whitelist. This makes candidate adjustments obsolete, since apt's resolver would pick candidates only from allowed origins by itself unless local pinning configuration overrides that. * Rely fully on pinning to disable allowed origins and stop adjusting candidates. * Drop Unattended-Upgrade::Allow-downgrade since now pinning is honored and downgrades are allowed for package versions with priority >= 1000. (Closes: #905877, #919046, #768087, #946491) (LP: #1251228, #1434115) * Don't ignore allowed origin when the package's priority is < 100. This used to be the way of honoring the priority, but now this special case prevents the package from showing up as a package kept back. * Assume frontend locking to be supported. Python3-apt (>= 1.9.6~) is required which supports the frontend locking API -- Balint Reczey Tue, 25 Feb 2020 19:28:13 +0100 ** Changed in: unattended-upgrades (Ubuntu) Status: New => Fix Released -- 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/1251228 Title: unattended-upgrade doesn't upgrade packages pinned to version Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: We wish to keep puppet and puppet-common pinned to the 2.7 versions. We achive this with the following /etc/apt/preferences.d/00-puppet.pref: Package: puppet puppet-common Pin: version 2.7* Pin-Priority: 501 This has the desired effect: puppet: Installed: 2.7.21-1puppetlabs1 Candidate: 2.7.23-1puppetlabs1 Package pin: 2.7.23-1puppetlabs1 Version table: 3.3.2-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 3.3.1-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 3.3.0-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 3.2.4-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 3.2.3-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 3.2.2-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 3.2.1-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 3.1.1-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 3.1.0-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 3.0.2-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 3.0.1-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 3.0.0-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 2.7.23-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 2.7.22-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages *** 2.7.21-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 100 /var/lib/dpkg/status 2.7.20-2puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 2.7.20-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 2.7.19-1puppetlabs2 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 2.7.19-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 2.7.18-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages 2.7.17-1puppetlabs1 501 500 http://apt.puppetlabs.com/ precise/main amd64 Packages
[Touch-packages] [Bug 1434115] Re: apparently broken dependency resolution
This bug was fixed in the package unattended-upgrades - 1.18 --- unattended-upgrades (1.18) experimental; urgency=medium [ louib ] * Update blacklist translations * Fix syntax in template conf files [ Balint Reczey ] * Keep mypy 0.761 happy * test: Create empty dirs to save kept packages list to them * Log explanation about kept back packages (LP: #1850964) (Closes: #945837, #903875) * Use GitHub Actions for CI instead of Travis. Run tests in Ubuntu Focal release because older releases don't have the needed python-apt version. * debian/tests/common-functions: Use backported python-apt from a PPA on Eoan * debian/tests: Skip upgrade-between-snapshots test. Python-apt's version is sid is too low for unattended-upgrades to work. * Use apt_pkg.Hashes instead of deprecated apt_pkg.md5sum() * autopkgtest: Skip upgrate-all-security in sid because buster can't be tested * Make allowed_origins, blacklist and whitelist attributes of UnattendedUpgradesCache * Make strict_whitelist attribute of UnattendedUpgradesCache * Apply pinning to disable not allowed origins and honor blacklist/whitelist. This makes candidate adjustments obsolete, since apt's resolver would pick candidates only from allowed origins by itself unless local pinning configuration overrides that. * Rely fully on pinning to disable allowed origins and stop adjusting candidates. * Drop Unattended-Upgrade::Allow-downgrade since now pinning is honored and downgrades are allowed for package versions with priority >= 1000. (Closes: #905877, #919046, #768087, #946491) (LP: #1251228, #1434115) * Don't ignore allowed origin when the package's priority is < 100. This used to be the way of honoring the priority, but now this special case prevents the package from showing up as a package kept back. * Assume frontend locking to be supported. Python3-apt (>= 1.9.6~) is required which supports the frontend locking API -- Balint Reczey Tue, 25 Feb 2020 19:28:13 +0100 ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Fix Released -- 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/1434115 Title: apparently broken dependency resolution Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: It looks as though unattended upgrades' dependency resolution is a little broken when there are multiple alternatives and when the dependency is currently satisfied by a package other than the first alternative. In this case, package php5 was upgraded. php5 depends: $ dpkg -s php5|grep Depends Depends: libapache2-mod-php5 (>= 5.5.9+dfsg-1ubuntu4.7) | libapache2-mod-php5filter (>= 5.5.9+dfsg-1ubuntu4.7) | php5-cgi (>= 5.5.9+dfsg-1ubuntu4.7) | php5-fpm (>= 5.5.9+dfsg-1ubuntu4.7), php5-common (>= 5.5.9+dfsg-1ubuntu4.7) I use php5-fpm, and specifically do not want libapache2-mod-php5 installed (not least because it breaks my FPM config). After manually purging libapache2-mod-php5: $ dpkg -l $(dpkg -s php5|grep Depends|perl -npe 's/Depends://; s/[,|]/\n/g'|cut -f 2 -d\ )|grep ^[a-z] un libapache2-mod-php5 (no description available) un libapache2-mod-php5filter (no description available) un php5-cgi (no description available) ii php5-common 5.5.9+dfsg-1ubuntu4.7 amd64Common files for packages built from the php5 source ii php5-fpm5.5.9+dfsg-1ubuntu4.7 amd64server-side, HTML-embedded scripting language (FPM-CGI binary) note that: • php5-fpm is installed and therefore that dependency of php5 was already satisfied • php5-cgi and libapache2-mod-php5filter are alternative dependencies along with libapache2-mod-php5, yet neither got installed in the way that libapache2-mod-php5 did. For completeness' sake, here's an excerpt of the unattended upgrade log (full log attached) showing that it was this morning's upgrade run that installed libapache2-mod-php5: Selecting previously unselected package libapache2-mod-php5. Preparing to unpack .../libapache2-mod-php5_5.5.9+dfsg-1ubuntu4.7_amd64.deb ... Unpacking libapache2-mod-php5 (5.5.9+dfsg-1ubuntu4.7) ... Preparing to unpack .../php5_5.5.9+dfsg-1ubuntu4.7_all.deb ... Unpacking php5 (5.5.9+dfsg-1ubuntu4.7) over (5.5.9+dfsg-1ubuntu4.6) ... Other requested information: $ lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.82.1ubuntu2.1 Candidate
[Touch-packages] [Bug 1850964] Re: Always explain why packages are held back in logs even without debugging enabled
This bug was fixed in the package unattended-upgrades - 1.18 --- unattended-upgrades (1.18) experimental; urgency=medium [ louib ] * Update blacklist translations * Fix syntax in template conf files [ Balint Reczey ] * Keep mypy 0.761 happy * test: Create empty dirs to save kept packages list to them * Log explanation about kept back packages (LP: #1850964) (Closes: #945837, #903875) * Use GitHub Actions for CI instead of Travis. Run tests in Ubuntu Focal release because older releases don't have the needed python-apt version. * debian/tests/common-functions: Use backported python-apt from a PPA on Eoan * debian/tests: Skip upgrade-between-snapshots test. Python-apt's version is sid is too low for unattended-upgrades to work. * Use apt_pkg.Hashes instead of deprecated apt_pkg.md5sum() * autopkgtest: Skip upgrate-all-security in sid because buster can't be tested * Make allowed_origins, blacklist and whitelist attributes of UnattendedUpgradesCache * Make strict_whitelist attribute of UnattendedUpgradesCache * Apply pinning to disable not allowed origins and honor blacklist/whitelist. This makes candidate adjustments obsolete, since apt's resolver would pick candidates only from allowed origins by itself unless local pinning configuration overrides that. * Rely fully on pinning to disable allowed origins and stop adjusting candidates. * Drop Unattended-Upgrade::Allow-downgrade since now pinning is honored and downgrades are allowed for package versions with priority >= 1000. (Closes: #905877, #919046, #768087, #946491) (LP: #1251228, #1434115) * Don't ignore allowed origin when the package's priority is < 100. This used to be the way of honoring the priority, but now this special case prevents the package from showing up as a package kept back. * Assume frontend locking to be supported. Python3-apt (>= 1.9.6~) is required which supports the frontend locking API -- Balint Reczey Tue, 25 Feb 2020 19:28:13 +0100 ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Fix Released -- 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/1850964 Title: Always explain why packages are held back in logs even without debugging enabled Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades package in Debian: New Bug description: [Impact] * Unattended-upgrades' log does not contain information about why held packages are kept back unless debugging is enabled. Users should be explained why packages are kept back to let them easily resolve the issues keeping the packages from being upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1850964/+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 1864839] Re: Background solid color causes noise
** Package changed: ubuntu => xorg (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/1864839 Title: Background solid color causes noise Status in xorg package in Ubuntu: New Bug description: Setting background to Solid color (Black) causes noise to appear on background (instead of black). This regularly happens on resume from sleep. See also https://www.reddit.com/r/Ubuntu/comments/8ezq2q/strange_graphics_bug_ubuntu_1710_background/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 07:09:26 2020 DistUpgraded: 2018-09-03 16:17:03,502 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-76-generic, x86_64: installed nvidia, 390.116, 4.15.0-88-generic, x86_64: installed virtualbox, 5.2.34, 4.15.0-76-generic, x86_64: installed virtualbox, 5.2.34, 4.15.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6593] InstallationDate: Installed on 2017-10-27 (852 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: MSI MS-7A62 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-09-03 (540 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: Z270 GAMING M3 (MS-7A62) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd07/10/2017:svnMSI:pnMS-7A62:pvr1.0:rvnMSI:rnZ270GAMINGM3(MS-7A62):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A62 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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/xorg/+bug/1864839/+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 1864839] [NEW] Background solid color causes noise
You have been subscribed to a public bug: Setting background to Solid color (Black) causes noise to appear on background (instead of black). This regularly happens on resume from sleep. See also https://www.reddit.com/r/Ubuntu/comments/8ezq2q/strange_graphics_bug_ubuntu_1710_background/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 07:09:26 2020 DistUpgraded: 2018-09-03 16:17:03,502 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-76-generic, x86_64: installed nvidia, 390.116, 4.15.0-88-generic, x86_64: installed virtualbox, 5.2.34, 4.15.0-76-generic, x86_64: installed virtualbox, 5.2.34, 4.15.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6593] InstallationDate: Installed on 2017-10-27 (852 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: MSI MS-7A62 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-09-03 (540 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.30 dmi.board.asset.tag: Default string dmi.board.name: Z270 GAMING M3 (MS-7A62) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.30:bd07/10/2017:svnMSI:pnMS-7A62:pvr1.0:rvnMSI:rnZ270GAMINGM3(MS-7A62):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A62 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 -- Background solid color causes noise https://bugs.launchpad.net/bugs/1864839 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1864708] Re: Mount unit fails but systemctl status shows success
can you attach/paste the output from these commands (after booting, before manually mounting): $ journalctl -b --no-pager $ systemctl list-units -t mount $ mount $ cat /etc/fstab ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1864708 Title: Mount unit fails but systemctl status shows success Status in systemd package in Ubuntu: Incomplete Bug description: I have this mount unit # cat /etc/systemd/system/srv-cctvstore.mount [Unit] Description=Drive for CCTVstore [Mount] What=/dev/disk/by-id/ata-ST2000NM0011_Z1P21NQ7-part1 Where=/srv/cctvstore Type=ext4 Options=defaults [Install] WantedBy=multi-user.target On boot systemd thinks it is mounted: $ systemctl status srv-cctvstore.mount ● srv-cctvstore.mount - Drive for CCTVstore Loaded: loaded (/etc/systemd/system/srv-cctvstore.mount; enabled; vendor preset: enabled) Active: active (mounted) since Tue 2020-02-25 22:37:16 SAST; 48s ago Where: /srv/cctvstore What: /dev/sda1 Process: 1294 ExecMount=/bin/mount /dev/disk/by-id/ata-ST2000NM0011_Z1P21NQ7-part1 /srv/cctvstore -t ext4 -o defaults (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/srv-cctvstore.mount Feb 25 22:37:16 kluis systemd[1]: Mounting Drive for CCTVstore... Feb 25 22:37:16 kluis systemd[1]: Mounted Drive for CCTVstore. and the mount command seems to agree $ mount | grep cctv /dev/sda1 on /srv/cctvstore type ext4 (rw,relatime) but the mountpoint is empty: $ ls -al /srv/cctvstore/ total 1 drwxr-xr-x 2 root root 2 Dec 7 22:51 . drwxr-xr-x 4 root root 4 Dec 7 22:51 .. and umount thinks it is not mounted: $ sudo umount /srv/cctvstore [sudo] password for johann: umount: /srv/cctvstore: not mounted. journalctl doesn't report any funnies: $ journalctl -u srv-cctvstore.mount -- Logs begin at Tue 2020-02-25 22:37:16 SAST, end at Tue 2020-02-25 22:41:43 SAST. -- Feb 25 22:37:16 kluis systemd[1]: Mounting Drive for CCTVstore... Feb 25 22:37:16 kluis systemd[1]: Mounted Drive for CCTVstore. but mounting by hand works: $ sudo mount /dev/sda1 /srv/cctvstore johann@kluis:~$ ls -al /srv/cctvstore total 3157 drwxrwxrwx 7 root root 4096 Dec 9 22:27 . drwxr-xr-x 4 root root 4 Dec 7 22:51 .. drwxr-xr-x 14 165569 1655694096 Dec 10 23:10 events drwxr-xr-x 2 165569 1655694096 Dec 7 22:59 images drwxr-xr-x 2 165569 1655694096 Dec 7 23:01 logs drwx-- 2 root root 16384 Dec 7 22:47 lost+found drwxrwxr-x 2 165569 165569 3194880 Feb 25 22:25 mlevents I am unsure where to go next, any help appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 Date: Tue Feb 25 22:27:59 2020 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-5.3.0-40-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: E3C232D2I dmi.board.vendor: ASRockRack 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.:bvrP2.50:bd03/07/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnE3C232D2I:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2020-01-08T12:29:15.304369 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1864708/+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 1863873] Re: Systemd fails to configure bridged network in LXC container
Possible workaround: switch back to ifupdown and don't use netplan sudo apt-get update sudo apt-get install ifupdown cat << EOF > /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet manual EOF systemctl stop systemd-networkd.socket systemd-networkd \ networkd-dispatcher systemd-networkd-wait-online systemctl disable systemd-networkd.socket systemd-networkd \ networkd-dispatcher systemd-networkd-wait-online sudo apt-get purge netplan.io -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. An example is provided, followed by a complete procedure to reproduce the issue. Affected container distributions Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo systemd 240-6ubuntu5.8: OK, not affected Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Example steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Sug
[Touch-packages] [Bug 1285444] Re: Login Successful, Desktop Never Loads
I'm Not 100% sure it's the same issue but there are many similarities to the original issue. My issue only happens after after I try to wake the laptop from sleep. What I've been encountering: 1. Boot computer, boot proceeds normally, can log-in, all is good. 2. Suspend laptop 3. On wake, just see the pink "Ubuntu 19.10" background. Cursor works and can be moved around, can click on upper right tool bar menu (with battery/wifi/etc) but nothing else seems to work if I click on items. Looks like wifi connection is successful. 4. Switching TTY with ctrl+alt+F1 works andthen a normal login screen appears where I can successfully log in. 5. Sometimes (but not always) I'm prompted for password saying, "Authentication required to refresh system repositories". I'm happy to open up a new bug if that makes more sense and these issues are unrelated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1285444 Title: Login Successful, Desktop Never Loads Status in at-spi2-core package in Ubuntu: Triaged Bug description: Here is what I encounter 1. Boot computer, boot proceeds normally 2. Reach standard Ubuntu login screen, nothing seems to be amiss 3. Enter user name and password 4. Login disappears, just see the pink "Ubuntu 14.04" background The desktop never loads, not even after ~30 minutes. The launcher never appears, and the Desktop background never changes to the user- configured background. Other features: * Cursor works fine, it can be moved around the screen * No error messages pop up * ALT+F1 etc. can be used to switch to different TTYs; all files on the system appear to be intact * Print screen button works (I will upload a screen shot when I get a chance to copy it onto a USB drive) * Hitting power button pops up a window prompting the user to decide whether to shut down * CTRL+ALT+DELETE prompts the user to log out * Desktop does not load on any user accounts, including the guest account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
After attaching to a TV, please upload dmesg, alsa-info.txt (run alsa- info to generate ala-info.txt) and the log of "pactl list". thx. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Hello @hui.wang, it seems that HDMI audio output is not working as expected, i can see the HDMI[1-3] devices (why 3 ?) but trying to using, when attached to a TV for example, what i get is just a new "dummy output" device. How should i debug this ? Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1862157] Re: dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles
Changing the behavior in Ubuntu only would only break plenty of scripts automation and expectations. I (personally) agree to Simon who also is "the upstream" on this that it is a security feature and people can still (if preferred) just not set it. I have read the answer twice but don't really (sorry) see the pain point which is made harder by this. Feel free to convince Simon and I guess Ubuntu is happy to follow on this whatever upstream decides to do. ** Changed in: dnsmasq (Ubuntu) Status: New => Confirmed ** Changed in: dnsmasq (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1862157 Title: dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles Status in dnsmasq package in Ubuntu: Confirmed Bug description: dnsmasq does in all cases prepend "tftp_root" to tftp-files. tftp-root=/data/tftp dhcp-boot=grub/i386-pc/core.0 now have some config files for different subnets: dhcp-boot=net:172-18-1,grub/i386-pc/core.0,172.18.1.1 dhcp-boot=net:172-18-8,pxelinux.0,172.18.8.1 dhcp-boot=net:172-18-7,/var/lib/tftpboot/pxelinux.0,spacewalk-ber.bfs.de Now booting clients within subnet 172.18.1.0/24 will boot grub with: /data/tftp/grub/i386-pc/core.0 Booting clients within subnet 172.18.2.0/24 will boot pxelinux.0 with: /data/tftp/pxelinux.0 And in subnet 172.18.7.0/24 clients will boot with: /data/tftp/var/lib/tftpboot/pxelinux.0 and return a "File not found" error. I'd expected: 172.18.1: grub/i386-pc/core.0 (file found within /data/tftp -- without exposing path) 172.18.2: pxelinux.0(file found within /data/tftp -- without exposing path) 172.18.3: /pxelinux.0 (file found within /) 172.18.7: /var/lib/tftpboot/pxelinux.0 (file found within /var/lib/tftpboot/pxelinux.0) or even better: some way to set tftp-root for every subnet-config and having only relative paths to access files regardless of giving absolute or relative paths. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dnsmasq 2.79-1 ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18 Uname: Linux 4.15.0-87-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Thu Feb 6 11:43:07 2020 InstallationDate: Installed on 2014-01-31 (2197 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: Upgraded to bionic on 2018-11-23 (439 days ago) mtime.conffile..etc.default.dnsmasq: 2014-02-19T17:19:28.429595 mtime.conffile..etc.dnsmasq.conf: 2016-08-17T12:18:41.225353 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1862157/+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 1849261] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-02-26 08:06 EDT--- IBM Bugzilla status-> closed, Fix Released by Canonical -- 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/1849261 Title: Update systemd for ubuntu 18.04 with fix for interaction between OnFailure= and Restart= Status in Ubuntu on IBM z Systems: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Fix Released Status in systemd source package in Eoan: Fix Released Bug description: [impact] services configured with both OnFailure= and Restart= directives will both start the failure service(s), as well as restarting itself. The documentation (and later versions) indicate that OnFailure= services will only be started once the service actually does stop (due to failure) once its restart limit has been exceeded. [test case] create service files as: ubuntu@lp1849261-b:/etc/systemd/system$ cat test.service [Unit] OnFailure=failure.service [Service] ExecStart=/bin/sh -c '/bin/sleep 10; /bin/false' Restart=always ubuntu@lp1849261-b:/etc/systemd/system$ cat failure.service [Service] ExecStart=/bin/true perform daemon-reload, and then start test service: ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl daemon-reload ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl start test wait for a while for the test service to exit - at least 10 seconds, as that's what we configured in the service, although I have waited longer in this example. Then check the journal for both test and failure services: ubuntu@lp1849261-b:/etc/systemd/system$ journalctl -b -u test -- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Fri 2019-12-13 01:18:34 UTC. -- Dec 13 01:17:43 lp1849261-b systemd[1]: Started test.service. Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 1. Dec 13 01:17:53 lp1849261-b systemd[1]: Stopped test.service. Dec 13 01:17:53 lp1849261-b systemd[1]: Started test.service. Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 2. Dec 13 01:18:04 lp1849261-b systemd[1]: Stopped test.service. Dec 13 01:18:04 lp1849261-b systemd[1]: Started test.service. Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 3. Dec 13 01:18:14 lp1849261-b systemd[1]: Stopped test.service. Dec 13 01:18:14 lp1849261-b systemd[1]: Started test.service. Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 4. Dec 13 01:18:24 lp1849261-b systemd[1]: Stopped test.service. Dec 13 01:18:24 lp1849261-b systemd[1]: Started test.service. Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'. Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies. Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart. Dec 13 01:18:34
[Touch-packages] [Bug 1846208] Re: [MIR] abootimg (dependency of initramfs-tools-ubuntu-core)
** Changed in: abootimg (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to abootimg in Ubuntu. https://bugs.launchpad.net/bugs/1846208 Title: [MIR] abootimg (dependency of initramfs-tools-ubuntu-core) Status in abootimg package in Ubuntu: Won't Fix Bug description: needs a MIR (or removal of the dependency): abootimg (dependency of initramfs-tools-ubuntu-core) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/abootimg/+bug/1846208/+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 1607845] Re: List of versioned kernels is not right for Ubuntu
Marking invalid for u-u since apt is fixed and now u-u autopkgtest passes. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Invalid -- 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/1607845 Title: List of versioned kernels is not right for Ubuntu Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Bug description: The following command outputs the list: $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages' linux-image linux-headers linux-image-extra linux-signed-image kfreebsd-image kfreebsd-headers gnumach-image .*-modules .*-kernel linux-backports-modules-.* linux-tools but the list does not 'contain linux-.*-tools' and 'linux-goldfish- headers', which are versioned kernel packages as well, if I have understood correctly. On the other hand are these values appropriate for Ubuntu? kfreebsd-image kfreebsd-headers gnumach-image .*-modules .*-kernel Same thing for Ubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jul 29 18:55:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-21 (250 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1607845/+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 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
I am on Focal Fossa, I just installed drm-tip kernel. Let's see how it goes :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1862865 Title: i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0 Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in mesa source package in Focal: Invalid Bug description: Hi, Every now and again, my session locks up with the following logged: | i915 :00:02.0: Resetting rcs0 for hang on rcs0 Most of the time, it recovers on it's own but sometimes locks up completely requring a reboot. When that happens this is logged: | Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 [i915]) | Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting chip for hang on rcs0 | Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001} | Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in chrome[5568968fd000+6abe000] | Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in chrome[55ac6372a000+6abe000] | Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01 80 bd 7f ff | Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 | Feb 2 10:38:15 dharkan kernel: [71070.591932]
[Touch-packages] [Bug 1864836] Re: package language-pack-gnome-fr 1:18.04+20180712 failed to install/upgrade: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.mo'
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-fr in Ubuntu. https://bugs.launchpad.net/bugs/1864836 Title: package language-pack-gnome-fr 1:18.04+20180712 failed to install/upgrade: unable to make backup link of './usr/share/locale- langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error Status in language-pack-gnome-fr package in Ubuntu: New Bug description: ubuntu 18.04 checking in software center error and abortion ProblemType: Package DistroRelease: Ubuntu 18.04 Package: language-pack-gnome-fr 1:18.04+20180712 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Feb 26 12:02:15 2020 DuplicateSignature: package:language-pack-gnome-fr:1:18.04+20180712 Replacing files in old package language-pack-fr-base (1:18.04+20180712) ... dpkg: error processing archive /tmp/apt-dpkg-install-uFbaQU/09-language-pack-fr_1%3a18.04+20200123_all.deb (--unpack): unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/JabberBot.mo' before installing new version: Input/output error ErrorMessage: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: language-pack-gnome-fr Title: package language-pack-gnome-fr 1:18.04+20180712 failed to install/upgrade: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-fr/+bug/1864836/+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 1863733] Re: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later
Test build in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3943/+packages works against the older libcap2 => https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ci-train-ppa-service-3943/focal/amd64/b/bubblewrap/20200226_102201_2465e@/log.gz I'm now setting up tests with the following combinations: - new libpcap2 - old bubblewrap (expect fail) - new libpcap2 - new bubblewrap (expected to work) - old libpcap2 - new bubblewrap (expected to work) Unfortunately all of the above passed, so the fix might be harder to confirm than expected :-/ Note this is masked on s390x and will need a bump there to the new version: $ grep -Hrn bubble ubuntu-release:22:force-badtest bubblewrap/0.4.0-1ubuntu1/s390x The upload with the bubblewrap fix can be reviewed at: https://code.launchpad.net/~paelzer/ubuntu/+source/bubblewrap/+git/bubblewrap/+merge/379880 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1863733 Title: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later Status in bubblewrap package in Ubuntu: New Status in libcap2 package in Ubuntu: New Status in bubblewrap package in Debian: Unknown Bug description: The bubblewrap upstream-as-root test started failing after libcap2 1:2.31-1 got synced from Debian. The same failure can be seen with 1:2.32-1. I have reproduced the issue locally on focal - when using the focal-proposed version, the aforementioned test fails, where with the release version (1:2.27-1) it passes. It seems to fail here already: bwrap --bind / / --tmpfs /tmp --as-pid-1 --cap-drop CAP_KILL --cap-drop CAP_FOWNER --unshare-pid capsh --print assert_not_file_has_content caps.test '^Current: =.*cap_kill' It looks like the requested caps did not get dropped, as the logs show that both cap_kill and cap_fowner are still there. This is only for the upstream-as-root test, i.e. executing tests/test-run.sh as root. This might be an issue with bubblewrap, but seeing that it all works fine with the release version, it all feels weird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1863733/+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 1864836] [NEW] package language-pack-gnome-fr 1:18.04+20180712 failed to install/upgrade: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.m
Public bug reported: ubuntu 18.04 checking in software center error and abortion ProblemType: Package DistroRelease: Ubuntu 18.04 Package: language-pack-gnome-fr 1:18.04+20180712 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Feb 26 12:02:15 2020 DuplicateSignature: package:language-pack-gnome-fr:1:18.04+20180712 Replacing files in old package language-pack-fr-base (1:18.04+20180712) ... dpkg: error processing archive /tmp/apt-dpkg-install-uFbaQU/09-language-pack-fr_1%3a18.04+20200123_all.deb (--unpack): unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/JabberBot.mo' before installing new version: Input/output error ErrorMessage: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: language-pack-gnome-fr Title: package language-pack-gnome-fr 1:18.04+20180712 failed to install/upgrade: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: language-pack-gnome-fr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-fr in Ubuntu. https://bugs.launchpad.net/bugs/1864836 Title: package language-pack-gnome-fr 1:18.04+20180712 failed to install/upgrade: unable to make backup link of './usr/share/locale- langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error Status in language-pack-gnome-fr package in Ubuntu: New Bug description: ubuntu 18.04 checking in software center error and abortion ProblemType: Package DistroRelease: Ubuntu 18.04 Package: language-pack-gnome-fr 1:18.04+20180712 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Feb 26 12:02:15 2020 DuplicateSignature: package:language-pack-gnome-fr:1:18.04+20180712 Replacing files in old package language-pack-fr-base (1:18.04+20180712) ... dpkg: error processing archive /tmp/apt-dpkg-install-uFbaQU/09-language-pack-fr_1%3a18.04+20200123_all.deb (--unpack): unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/JabberBot.mo' before installing new version: Input/output error ErrorMessage: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: language-pack-gnome-fr Title: package language-pack-gnome-fr 1:18.04+20180712 failed to install/upgrade: unable to make backup link of './usr/share/locale-langpack/fr/LC_MESSAGES/ModemManager.mo' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-fr/+bug/1864836/+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 1864824] Re: BlueZ 5.53 release
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed ** Changed in: bluez (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1864824 Title: BlueZ 5.53 release Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.53 to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1864824/+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 1864813] Re: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c
In bionic, the dummy output disappears in certain case and never show up again in certain cases. I do like to know which is the *corrected* behaviors so I know which one we should work on. Agree that it’s not a major bug IMHO. -- 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/1864813 Title: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+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 1864824] Re: BlueZ 5.53 release
** Attachment added: "bluez_5.53-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1864824/+attachment/5331193/+files/bluez_5.53-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1864824 Title: BlueZ 5.53 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.53 to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1864824/+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 1864824] Re: BlueZ 5.53 release
** Attachment added: "bluez_5.53.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1864824/+attachment/5331192/+files/bluez_5.53.orig.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1864824 Title: BlueZ 5.53 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.53 to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1864824/+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 1864824] [NEW] BlueZ 5.53 release
Public bug reported: Release BlueZ 5.53 to focal. ** Affects: bluez (Ubuntu) Importance: Undecided Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: champagne focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1864824 Title: BlueZ 5.53 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.53 to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1864824/+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 1668944] Re: The _apt user ignores group membership.
Nowadays our HTTPS implementation works a few layers deeper than what I talked about three years ago, so we could similar to our auth.conf work now open all certificate (others also?) files as root before dropping rights. As that would be best implemented by someone who actually uses these features in practice for easier testing: Any takers? -- 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/1668944 Title: The _apt user ignores group membership. Status in apt package in Ubuntu: Invalid Bug description: Actually I had the same problem described in http://askubuntu.com/questions/773955/apt-get-ssl-client-certificate-not-working-on-16-04-error-while-reading-file I want to use client certificates with apt. But I don't want to make them world readable in order to make apt working. So I created a group 'ssl-cert' and changed the group ownership of the ssl cert files to match this group. I also added the _apt user to the ssl-cert group. Then I tried to open these files as user '_apt' in bash (su -s /bin/bash _apt) which works well. But if I run: "apt-get -o "Debug::Acquire::https=true" update" I still get the following error: * error reading ca cert file /etc/certs/mycert/ca.pem (Error while reading file.) * Closing connection 26 So my guess is that apt somehow ignores the ssl-cert membership. Possible workarounds: - make ssl client cert world readable - change owner ssl client cert to _apt - change main group of _apt user from 'nogroup' to 'ssl-cert' - set APT::Sandbox::User "root"; in apt.conf.d Neither of them is pretty. Maybe this is a wanted behavior, then just suggest how to fix the issue in nice way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1668944/+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 1863733] Re: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later
FYI - I'm taking a look if the proposed change on the issue would help us to unblock the new libcap2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1863733 Title: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later Status in bubblewrap package in Ubuntu: New Status in libcap2 package in Ubuntu: New Status in bubblewrap package in Debian: Unknown Bug description: The bubblewrap upstream-as-root test started failing after libcap2 1:2.31-1 got synced from Debian. The same failure can be seen with 1:2.32-1. I have reproduced the issue locally on focal - when using the focal-proposed version, the aforementioned test fails, where with the release version (1:2.27-1) it passes. It seems to fail here already: bwrap --bind / / --tmpfs /tmp --as-pid-1 --cap-drop CAP_KILL --cap-drop CAP_FOWNER --unshare-pid capsh --print assert_not_file_has_content caps.test '^Current: =.*cap_kill' It looks like the requested caps did not get dropped, as the logs show that both cap_kill and cap_fowner are still there. This is only for the upstream-as-root test, i.e. executing tests/test-run.sh as root. This might be an issue with bubblewrap, but seeing that it all works fine with the release version, it all feels weird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1863733/+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 1864623] Re: apt-get attempts to download Packages.xz which is not InRelease and does not exist
The cake is a lie. --print-uris does *NOT* print the URIs an "apt update" is bound to use. It can't because it doesn't download any file and it would need to download at least the (current) InRelease file to answer that. So what it does is print the URIs it would download IF everything would exist and be advertised in the (In)Release file. The option is from a time the answer was a lot easier to answer (a long time ago), but nowadays apt supports too many optional features which are handled at runtime to make accurate predictions (especially) about the future. So, your problem is elsewhere. Please check what "update" says. What a following install command says and verify that the deb file it wants to download actually exists. "~Ubuntu" in the version seems kinda strange… usually its lowercase. Either is fine, but consistency is key: apt as most tools in Linux is case-sensitive. Anyway, with the current set of information we can only make very wild guesses. ** Changed in: apt (Ubuntu) Status: New => Invalid -- 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/1864623 Title: apt-get attempts to download Packages.xz which is not InRelease and does not exist Status in apt package in Ubuntu: Invalid Bug description: When trying to install the latest virtualbox-6.0 from virtualbox.org, we got a failure: Err:1 http://download.virtualbox.org/virtualbox/debian xenial/contrib amd64 virtualbox-6.0 amd64 6.0.16-135674~Ubuntu~xenial 404 Not Found E: Failed to fetch http://download.virtualbox.org/virtualbox/debian/pool/contrib/v/virtualbox-6.0/virtualbox-6.0_6.0.16-135674~Ubuntu~xenial_amd64.deb 404 Not Found We expected that this was a case of `apt-get update` not having been run before `apt-get install`, but turns out it's a bit more interesting: apt-get update fetched the following files: ubuntu@ubuntu:~$ apt-get --print-uris update |grep virtualbox 'http://download.virtualbox.org/virtualbox/debian/dists/xenial/InRelease' download.virtualbox.org_virtualbox_debian_dists_xenial_InRelease 0 'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/binary-amd64/Packages.xz' download.virtualbox.org_virtualbox_debian_dists_xenial_contrib_binary-amd64_Packages 0 'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/binary-all/Packages.xz' download.virtualbox.org_virtualbox_debian_dists_xenial_contrib_binary-all_Packages 0 'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/i18n/Translation-en.xz' download.virtualbox.org_virtualbox_debian_dists_xenial_contrib_i18n_Translation-en 0 http://download.virtualbox.org/virtualbox/debian/dists/xenial/InRelease returns 200 and lists a bunch of Packages lists. However, it does *not* list contrib/binary-amd64/Packages.xz, only: - contrib/binary-amd64/Packages - contrib/binary-amd64/Packages.gz - contrib/binary-amd64/Packages.bz2 For some reason, apt still attempts to download the .xz files, and does not even report an error for them! Trying to download the file locally, I get a 404, but with an HTML error page as the content: $ curl -v 'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/binary-amd64/Packages.xz' | head -n 20 % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 2.22.40.42... * TCP_NODELAY set * Connected to download.virtualbox.org (2.22.40.42) port 80 (#0) > GET /virtualbox/debian/dists/xenial/contrib/binary-amd64/Packages.xz HTTP/1.1 > Host: download.virtualbox.org > User-Agent: curl/7.58.0 > Accept: */* > 0 00 00 0 0 0 --:--:-- 0:00:02 --:--:-- 0< HTTP/1.1 404 Not Found < Accept-Ranges: bytes < Content-Type: text/html < ETag: "477d9862374177c810b0b7d73b4f1e53:1531792454.541174" < Last-Modified: Wed, 31 Aug 2011 20:28:54 GMT < Server: AkamaiNetStorage < Content-Length: 7073 < Date: Tue, 25 Feb 2020 09:08:16 GMT < Connection: keep-alive < { [7073 bytes data] 100 7 Error Page 404 http://download.oracle.com/index.html"; /> I think it's a bug that: a) apt tries to download Packages files not listed in InRelease b) apt does not report errors on 404 it gets when downloading them It is of course possible that apt get a *different* InRelease and a *different* response when trying to download the .xz files, but that seems unlikely. If you want to, I can try to confirm the actual network traffic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1864623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1864813] Re: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c
Sounds kind of correct. Why is this a bug? ** Tags added: focal ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1864813 Title: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+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 1864813] [NEW] As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c
Public bug reported: There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 ** Affects: oem-priority Importance: Medium Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Medium ** Description changed: - There will be an dummy output if + There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. - Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 -- 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/1864813 Title: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+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 1863873] Re: Systemd fails to configure bridged network in LXC container
I can confirm this behavior after update to systemd 237-3ubuntu10.39 on privileged and unprivileged containers. We classify this bug as critical because in the next monthly update cycle via ansible orchestration we would expect failing all Bionic LXC containers. The only workaround seems to manually define a static network configuration in /etc/netplan/10-lxc.yaml via lxc-attach. But this is not an acceptable solution for 180 servers we run. Some our Plesk servers already failed completely due to automatic upgrades Plesk triggered daily. Websites were down for hours until we figured out the reason. I would appreciate that someone solves this problem due to urgency. Thank you in advance. -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. An example is provided, followed by a complete procedure to reproduce the issue. Affected container distributions Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo systemd 240-6ubuntu5.8: OK, not affected Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Example steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389: