[Touch-packages] [Bug 1869304] [NEW] Video Card Intel Not being used
Public bug reported: Laptop was draining battery too fast, checked for Video Card Updates, Intel is not being used. Tried Xorg, it says fault packages are being held. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 11:07:15 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:078b] Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1028:078b] InstallationDate: Installed on 2020-03-23 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a05 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15-3567 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=7a4ba4e2-af26-42b5-b4bf-852d8f4e530b ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.0 dmi.board.name: 0765NJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.0:bd05/10/2019:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0765NJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078B dmi.sys.vendor: Dell Inc. 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.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1869304 Title: Video Card Intel Not being used Status in xorg package in Ubuntu: New Bug description: Laptop was draining battery too fast, checked for Video Card Updates, Intel is not being used. Tried Xorg, it says fault packages are being held. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 11:07:15 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:078b] Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1028:078b] InstallationDate: Installed on 2020-03-23 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a05 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15-3567 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=7a4ba4e2-af26-42b5-b4bf-852d8f4e530b ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.0 dmi.board.name: 0765NJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
** Summary changed: - [PATCH] Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity + Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity ** Changed in: console-setup (Ubuntu) Importance: Undecided => Medium -- 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/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: Confirmed Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+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 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
** Changed in: wpa (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Triaged Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+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 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
This is the debdiff for eoan (19.10), please help put it into the queue. thx. ** Patch added: "alsa-lib_1.1.9-0ubuntu1.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+attachment/5341981/+files/alsa-lib_1.1.9-0ubuntu1.3.debdiff -- 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/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in HWE Next: New Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Eoan: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: This SRU is not backported from upstream of alsa-lib and this SRU is not going to be submitted to upstream. That is because the latest alsa-lib already supports ucm2, and with ucm2 all machines could share one ucm, so latest alsa-lib does not have this problem. This problem is only specific to the alsa-lib in Bionic and Eoan. [Impact] On some Lenovo notebooks, UCM files are not loaded and mic can't be used. [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] After applying this patch, install the testing alsa-lib on Lenovo X1C7 and Dell vostro 5390, which are all machines with the DMIC connected to PCH. After system bootup, check the /usr/share/alsa/ucm/ for the presence of LENOVO-BIOSID-xxx directories. Lenovo X1C7 should load the N2H/*.conf and verify the audio functionalities. The Dell machine should still load the ucm by cardname, and it should work as good as before. [Regression Potential] low, just add some new UCMs and let Lenovo machine find the UCM by bios_version if it fails by cardlongname. I've already tested the change on Lenovo and Dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868210/+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 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
This is the debdiff for bionic (18.04), please help put it into the queue. thx. ** Patch added: "alsa-lib_1.1.3-5ubuntu0.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1868210/+attachment/5341982/+files/alsa-lib_1.1.3-5ubuntu0.5.debdiff -- 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/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in HWE Next: New Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Eoan: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: This SRU is not backported from upstream of alsa-lib and this SRU is not going to be submitted to upstream. That is because the latest alsa-lib already supports ucm2, and with ucm2 all machines could share one ucm, so latest alsa-lib does not have this problem. This problem is only specific to the alsa-lib in Bionic and Eoan. [Impact] On some Lenovo notebooks, UCM files are not loaded and mic can't be used. [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] After applying this patch, install the testing alsa-lib on Lenovo X1C7 and Dell vostro 5390, which are all machines with the DMIC connected to PCH. After system bootup, check the /usr/share/alsa/ucm/ for the presence of LENOVO-BIOSID-xxx directories. Lenovo X1C7 should load the N2H/*.conf and verify the audio functionalities. The Dell machine should still load the ucm by cardname, and it should work as good as before. [Regression Potential] low, just add some new UCMs and let Lenovo machine find the UCM by bios_version if it fails by cardlongname. I've already tested the change on Lenovo and Dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868210/+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 1860947] Re: package libqt4-sql:amd64 4:4.8.7+dfsg-7ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a r
[Expired for qt4-x11 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qt4-x11 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1860947 Title: package libqt4-sql:amd64 4:4.8.7+dfsg-7ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in qt4-x11 package in Ubuntu: Expired Bug description: na ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libqt4-sql:amd64 4:4.8.7+dfsg-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 26 19:41:03 2020 DuplicateSignature: package:libqt4-sql:amd64:4:4.8.7+dfsg-7ubuntu3 Preparing to unpack .../03-libqtcore4_4%3a4.8.7+dfsg-7ubuntu1_amd64.deb ... Log started: 2020-01-26 19:41:03 dpkg: error processing package libqt4-sql:amd64 (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2019-05-05 (266 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: qt4-x11 Title: package libqt4-sql:amd64 4:4.8.7+dfsg-7ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1860947/+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 1814938] Re: drm.edid_firmware fails to load firmware where crypsetup-initramfs is installed
** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1814938 Title: drm.edid_firmware fails to load firmware where crypsetup-initramfs is installed Status in initramfs-tools package in Ubuntu: Confirmed Bug description: My HP LP2475W monitor reports incorrect EDID info resulting in bad image quality. It can be fixed with a customized edid file, and adding drm.edid_firmware kernel boot parameter. But in Ubuntu 18.04.1 and Ubuntu 18.10, if crypsetup-initramfs package is installed, it fails to load the firmware file. Detailed bug report: Following this istructions (https://blog.tingping.se/2018/12/01 /amdgpu-fullrgb.html), I created a modified edid.bin file in /lib/firmware/edid/edid.bin and passed drm.edid_firmware=edid/edid.bin to the kernel at boot. In my daily Ubuntu 18.04.1 dmesg report this error and I could not solve it. [1.173897] platform HDMI-A-1: Direct firmware load for edid/edid.bin failed with error -2 So I tried in a fresh Ubuntu 18.10 and it worked nicely, no error and nice crisp display image. But when I began to install the software I need for daily use it ceased to work and began to show the same message as in my work Ubuntu 18.04.1. After some test it seems that the problem occurs after I install cryptsetup: -- dmesg | grep edid [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1 [3.792846] [drm] Got external EDID base block and 1 extension from "edid/edid.bin" for connector "HDMI-A-1" -- I purged cryptsetup but the problem persisted, so I removed too cryptsetup-initramfs and the the problem disapeared and the edid file is loaded again, improving the display quality: -- dmesg | grep edid [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1 [3.717878] [drm] Got external EDID base block and 1 extension from "edid/edid.bin" for connector "HDMI-A-1" --- This question in AskUbuntu suggest that there are more people with this probem (https://askubuntu.com/questions/1113195/how-to-output- full-range-rgb-in-ubuntu-18-04-1) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-14-generic 4.18.0-14.15 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 2007 F pulseaudio /dev/snd/pcmC0D1p: david 2007 F...m pulseaudio /dev/snd/controlC1: david 2007 F pulseaudio Date: Wed Feb 6 18:37:39 2019 InstallationDate: Installed on 2019-02-06 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-14-generic N/A linux-backports-modules-4.18.0-14-generic N/A linux-firmware 1.175.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U1n dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z68X-UD3H-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Touch-packages] [Bug 1814938] [NEW] drm.edid_firmware fails to load firmware where crypsetup-initramfs is installed
You have been subscribed to a public bug: My HP LP2475W monitor reports incorrect EDID info resulting in bad image quality. It can be fixed with a customized edid file, and adding drm.edid_firmware kernel boot parameter. But in Ubuntu 18.04.1 and Ubuntu 18.10, if crypsetup-initramfs package is installed, it fails to load the firmware file. Detailed bug report: Following this istructions (https://blog.tingping.se/2018/12/01/amdgpu- fullrgb.html), I created a modified edid.bin file in /lib/firmware/edid/edid.bin and passed drm.edid_firmware=edid/edid.bin to the kernel at boot. In my daily Ubuntu 18.04.1 dmesg report this error and I could not solve it. [1.173897] platform HDMI-A-1: Direct firmware load for edid/edid.bin failed with error -2 So I tried in a fresh Ubuntu 18.10 and it worked nicely, no error and nice crisp display image. But when I began to install the software I need for daily use it ceased to work and began to show the same message as in my work Ubuntu 18.04.1. After some test it seems that the problem occurs after I install cryptsetup: -- dmesg | grep edid [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1 [3.792846] [drm] Got external EDID base block and 1 extension from "edid/edid.bin" for connector "HDMI-A-1" -- I purged cryptsetup but the problem persisted, so I removed too cryptsetup-initramfs and the the problem disapeared and the edid file is loaded again, improving the display quality: -- dmesg | grep edid [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1 [3.717878] [drm] Got external EDID base block and 1 extension from "edid/edid.bin" for connector "HDMI-A-1" --- This question in AskUbuntu suggest that there are more people with this probem (https://askubuntu.com/questions/1113195/how-to-output-full- range-rgb-in-ubuntu-18-04-1) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-14-generic 4.18.0-14.15 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 2007 F pulseaudio /dev/snd/pcmC0D1p: david 2007 F...m pulseaudio /dev/snd/controlC1: david 2007 F pulseaudio Date: Wed Feb 6 18:37:39 2019 InstallationDate: Installed on 2019-02-06 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=dfb5fdf3-b93b-4abf-99fd-d5a7ec4e66df ro drm.edid_firmware=edid/edid.bin quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-14-generic N/A linux-backports-modules-4.18.0-14-generic N/A linux-firmware 1.175.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U1n dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z68X-UD3H-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU1n:bd07/11/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3H-B3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: Confirmed ** Tags:
[Touch-packages] [Bug 1869267] [NEW] /etc/login.defs contains a non-ASCII character
Public bug reported: 1) OS: Ubuntu 16.04.6 LTS 2) Package: login 1:4.2-3.1ubuntu5.4 amd64 from xenial-updates/main 3) After installing this package, I expect /etc/login.defs to contain only ASCII characters. 4) Instead, /etc/login.defs contains an Acute Accent (Unicode U+00B4) on line 221 in a comment: === Quote From File === # If set to yes, userdel will remove the user´s group if it contains no === End Quote === This causes a problem in SaltStack: https://github.com/saltstack/salt/issues/55695 SaltStack does recognize that they should do a better job at loading this file and is planning on fixing its problem. But I still question this: Should we expect /etc/login.defs to contain ASCII characters only? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: login 1:4.2-3.1ubuntu5.4 ProcVersionSignature: Ubuntu 4.4.0-1101.112-aws 4.4.208 Uname: Linux 4.4.0-1101-aws x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Mar 26 17:46:26 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1869267 Title: /etc/login.defs contains a non-ASCII character Status in shadow package in Ubuntu: New Bug description: 1) OS: Ubuntu 16.04.6 LTS 2) Package: login 1:4.2-3.1ubuntu5.4 amd64 from xenial-updates/main 3) After installing this package, I expect /etc/login.defs to contain only ASCII characters. 4) Instead, /etc/login.defs contains an Acute Accent (Unicode U+00B4) on line 221 in a comment: === Quote From File === # If set to yes, userdel will remove the user´s group if it contains no === End Quote === This causes a problem in SaltStack: https://github.com/saltstack/salt/issues/55695 SaltStack does recognize that they should do a better job at loading this file and is planning on fixing its problem. But I still question this: Should we expect /etc/login.defs to contain ASCII characters only? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: login 1:4.2-3.1ubuntu5.4 ProcVersionSignature: Ubuntu 4.4.0-1101.112-aws 4.4.208 Uname: Linux 4.4.0-1101-aws x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Mar 26 17:46:26 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1869267/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Same insue here with a Dell G3 laptop. Microphone, nor any input device its recognized -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
The fix provided by chris-18 worked for me, same issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 1869078] Re: dhclient then ath10k firmware crashes
It seems to have disappeared when I updated dhclient to 4.4.2
** Changed in: isc-dhcp (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1869078
Title:
dhclient then ath10k firmware crashes
Status in isc-dhcp package in Ubuntu:
Fix Released
Bug description:
I had to restart so not sure if automatically generated debug-info is
relevant.
In my journalctl I get this error:
Mar 25 21:17:10 dhclient[29542]: For info, please visit
https://www.isc.org/software/dhcp/
Mar 25 21:17:10 dhclient[29542]:
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 45:
numeric minute expected.
Mar 25 21:17:10 dhclient[29542]: rebind 3 2020/03/25 18:lease
Mar 25 21:17:10 dhclient[29542]: ^
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 45:
semicolon expected.
Mar 25 21:17:10 dhclient[29542]: rebind 3 2020/03/25 18:lease {
Mar 25 21:17:10 dhclient[29542]: ^
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 79:
expecting numeric value.
Mar 25 21:17:10 dhclient[29542]: option routers 192.168.0lease
Mar 25 21:17:10 dhclient[29542]: ^
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 142:
unterminated lease declaration.
...
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: firmware crashed! (guid
9bfed658-d8c1-48ad-9172-538c9219d4df)
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: qca6174 hw3.2 target
0x0503 chip_id 0x00340aff sub 1a56:1535
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1
tracing 1 dfs 0 testmode 0
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: firmware ver
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32
29eb8ca1
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A
crc32 4ac0889b
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: htt-ver 3.60 wmi-op 4
htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: failed to get memcpy hi
address for firmware address 4: -16
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: failed to read firmware
dump area: -16
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: Copy Engine register dump:
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [00]: 0x00034400 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [01]: 0x00034800 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [02]: 0x00034c00 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [03]: 0x00035000 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [04]: 0x00035400 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [05]: 0x00035800 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [06]: 0x00035c00 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [07]: 0x00036000 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to receive control
response completion, polling..
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x0001 at 0x00034430: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
read32 at 0x0003: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x001e at 0x00034430: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x0001 at 0x00034830: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x0001 at 0x00035430: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
read32 at 0x00035444: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x001e at 0x00035430: -110
Mar 25 21:17:12 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x001e at 0x00034830: -110
Mar 25 21:17:13 kernel: ath10k_pci :3a:00.0: ctl_resp never came in
(-110)
Mar 25 21:17:13 kernel: ath10k_pci :3a:00.0: failed to connect to HTC:
-110
Full debug log attached.
My system froze. I was watching a move and the video stopped, audio
skipped. Hence why there are alsa complaints in the debug.
The ath10k firmware crashed and I couldn't reload.
Ubuntu 18.04.4 LTS
Linux albert-XPS-13-9360 5.5.0-050500-generic #202001262030 SMP Mon
Jan 27 01:33:36 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
*-network
Re: [Touch-packages] [Bug 1868706] Re: Snapd postinst script hangs
Pawel, this is great debugging, thank you. Agree it's an edge case. Mark -- 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/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+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 1868409] Re: gnome-{calculator, logs, characters} snaps not removed after the equivalent APT packages are installed on 20.04, and gnome-software APT package not replaced by snap-
The desktop team is currently working on changes to update-manager which
would replace snaps with deb packages and this would help people who
installed or upgraded to the development release of Ubuntu early.
https://code.launchpad.net/~marcustomlinson/update-manager/update-
manager/+merge/380060
However, that would not help you out as you are using apt directly.
--
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/1868409
Title:
gnome-{calculator,logs,characters} snaps not removed after the
equivalent APT packages are installed on 20.04, and gnome-software APT
package not replaced by snap-store
Status in gnome-calculator package in Ubuntu:
New
Status in ubuntu-meta package in Ubuntu:
Confirmed
Bug description:
I'm trialing the development release of Ubuntu 20.04, installed in
December and kept up-to-date by regularly running apt full-upgrade.
I understand from [1] that 20.04 will ship
gnome-{calculator,logs,characters} as APT packages rather than snap
apps, and gnome-software as a snap app (called snap-store) rather than
an APT package.
Following an apt full-upgrade in late February, I now have:
* both the snap and the APT versions of gnome-{calculator,logs,characters}
* still only the APT version of gnome-software, no snap-store
Is this normal? A user in the #ubuntu+1 IRC channel reports that a
fresh install of the development release:
* only features the APT versions of gnome-{calculator,logs,characters}
* features the snap-store (but also the APT version of gnome-software)
Are users of older installs of the development release supposed to
manually uninstall the snap versions of
gnome-{calculator,logs,characters} and manually install the snap-
store?
[1] https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-
remove-for-snap-snap-store/14542
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1868409/+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 1868927] Re: FFe: Sync shared-mime-info 1.15-1 (main) from Debian unstable (main)
I wasn't sure whether the updated build dependences require an FFe or not. But yes, the changes are mostly bug fixes and improvements. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1868927 Title: FFe: Sync shared-mime-info 1.15-1 (main) from Debian unstable (main) Status in shared-mime-info package in Ubuntu: New Bug description: Please sync shared-mime-info 1.15-1 (main) from Debian unstable (main) NEWS: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/blob/master/NEWS shared-mime-info 1.15 (2019-30-10) * Add Kindle 8 eBook format * Fix some HTML files being detected as XML shared-mime-info 1.14 (2019-20-09) * Add mime-type for QCOW images * Fix matching SVG files in some circumstances (again) shared-mime-info 1.13.1 (2019-11-09) * Fix matching SVG files in some circumstances shared-mime-info 1.13 (2019-11-09) * Add code of conduct document * Use itstool and gettext to generate translations * Add content-tree type for OSTree USB repositories * Add match for MPEG-4 v1 videos * Adjust a lot of user readable mime-type descriptions * Fix WOFF/WOFF2 mime-types * Prefer text/html to XHTML for *.html files * Better magic for text/html files * Fix SVG magic for files embedded in HTML * Add *.sgd as a glob for Mega Drive ROMs Specification: - Mention that sub-class-of can be aliases Tools: - Enable Large File Support in update-mime-database Test suite: - Make test suite failures fatal - Add test for duplicate mime-types - Fix WarpScript test - Generate the specification in the CI, to avoid it becoming syntactically invalid shared-mime-info 1.12 (2019-17-01) * Fix build from tarball shared-mime-info 1.11 (2019-17-01) * Add mime-type for reStructuredText * Add mime-type for Groovy scripting language * Add mime-type for Gradle build tool * Add mime-type for Maven * Add mime-type for WarpScript source code * Add mime-type for zstd and tar.zst archives * Change the preferred suffix for image/jpeg from .jpeg to .jpg * Assign *.html to XHTML pages * Better detection for *.key files (Apple Keynote vs. GPG keys) * Give weight to one of the appimage patterns Tools: - Link to GitLab for contributions and bug reports - Loads of memory and file descriptor leak fixes Spec: - Clarify the availability of C character escape support Explanation of FeatureFreeze exception: New mime-type's and improvements to the existing ones useful for the life of the new LTS. The current version 1.10 has not been updated since September 2018. Changelog entries since current focal version 1.10-1: shared-mime-info (1.15-1) unstable; urgency=medium * New upstream release. Closes: #954669. * Update watch file for gitlab.freedesktop.org. * Update build-dependencies. * Remove ancient patches changing the magic database. Those should be reported upstream if they're still present. * Switch to debhelper-compat and bump compat to 12. * Don't hardcode full command path in postinst. -- Emilio Pozuelo Monfort Tue, 24 Mar 2020 16:58:21 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1868927/+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 1868720] Re: backport time64 syscalls whitelist
Focal may be affected after all then -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Bionic: Triaged Status in libseccomp source package in Disco: Won't Fix Status in libseccomp source package in Eoan: Triaged Status in libseccomp source package in Focal: Fix Released Bug description: A number of new *time64 syscalls are introduced in newer kernel series (>=5.1.x): 403: clock_gettime64 404: clock_settime64 405: clock_adjtime64 406: clock_getres_time64 407: clock_nanosleep_time64 408: timer_gettime64 409: timer_settime64 410: timerfd_gettime64 411: timerfd_settime64 412: utimensat_time64 413: pselect6_time64 414: ppoll_time64 In particular utimensat_time64 is now used inside glibc>=2.31 In turn ubuntu with has trouble running docker images of newer distros. This problem affects libseccomp<2.4.2, ie bionic (lts), and eoan, but not focal. See a similar report at Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1770154 A solution could be to backport the related changes from 2.4.2 similarly to what happened for the statx whitelisting (https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+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 1868409] Re: gnome-{calculator, logs, characters} snaps not removed after the equivalent APT packages are installed on 20.04, and gnome-software APT package not replaced by snap-
** Also affects: gnome-calculator (Ubuntu)
Importance: Undecided
Status: New
--
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/1868409
Title:
gnome-{calculator,logs,characters} snaps not removed after the
equivalent APT packages are installed on 20.04, and gnome-software APT
package not replaced by snap-store
Status in gnome-calculator package in Ubuntu:
New
Status in ubuntu-meta package in Ubuntu:
Confirmed
Bug description:
I'm trialing the development release of Ubuntu 20.04, installed in
December and kept up-to-date by regularly running apt full-upgrade.
I understand from [1] that 20.04 will ship
gnome-{calculator,logs,characters} as APT packages rather than snap
apps, and gnome-software as a snap app (called snap-store) rather than
an APT package.
Following an apt full-upgrade in late February, I now have:
* both the snap and the APT versions of gnome-{calculator,logs,characters}
* still only the APT version of gnome-software, no snap-store
Is this normal? A user in the #ubuntu+1 IRC channel reports that a
fresh install of the development release:
* only features the APT versions of gnome-{calculator,logs,characters}
* features the snap-store (but also the APT version of gnome-software)
Are users of older installs of the development release supposed to
manually uninstall the snap versions of
gnome-{calculator,logs,characters} and manually install the snap-
store?
[1] https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-
remove-for-snap-snap-store/14542
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1868409/+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 1868720] Re: backport time64 syscalls whitelist
turns ou we may also need this fix in docker: https://github.com/moby/moby/pull/40739 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Bionic: Triaged Status in libseccomp source package in Disco: Won't Fix Status in libseccomp source package in Eoan: Triaged Status in libseccomp source package in Focal: Fix Released Bug description: A number of new *time64 syscalls are introduced in newer kernel series (>=5.1.x): 403: clock_gettime64 404: clock_settime64 405: clock_adjtime64 406: clock_getres_time64 407: clock_nanosleep_time64 408: timer_gettime64 409: timer_settime64 410: timerfd_gettime64 411: timerfd_settime64 412: utimensat_time64 413: pselect6_time64 414: ppoll_time64 In particular utimensat_time64 is now used inside glibc>=2.31 In turn ubuntu with has trouble running docker images of newer distros. This problem affects libseccomp<2.4.2, ie bionic (lts), and eoan, but not focal. See a similar report at Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1770154 A solution could be to backport the related changes from 2.4.2 similarly to what happened for the statx whitelisting (https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+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 1869117] Re: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)
** Also affects: python-pip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1869117 Title: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal) Status in python-pip package in Ubuntu: Confirmed Status in python2.7 package in Ubuntu: Invalid Bug description: apt-get install python-pip fails in Ubuntu 20.04: The following packages have unmet dependencies: python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be installed Recommends: python-all-dev (>= 2.6) but it is not going to be installed Recommends: python-wheel but it is not going to be installed E: Unable to correct problems, you have held broken packages. The python-pip package needs to be updated to accept newer versions of python-pip-whl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1869117/+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 1869117] Re: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-pip (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1869117 Title: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal) Status in python-pip package in Ubuntu: Confirmed Status in python2.7 package in Ubuntu: Invalid Bug description: apt-get install python-pip fails in Ubuntu 20.04: The following packages have unmet dependencies: python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be installed Recommends: python-all-dev (>= 2.6) but it is not going to be installed Recommends: python-wheel but it is not going to be installed E: Unable to correct problems, you have held broken packages. The python-pip package needs to be updated to accept newer versions of python-pip-whl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1869117/+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 1868927] Re: FFe: Sync shared-mime-info 1.15-1 (main) from Debian unstable (main)
You subscribed the release team so I'm going to let them comment but the changes look like mostly bugfixes, unsure there is a new feature/things required a ffe there? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1868927 Title: FFe: Sync shared-mime-info 1.15-1 (main) from Debian unstable (main) Status in shared-mime-info package in Ubuntu: New Bug description: Please sync shared-mime-info 1.15-1 (main) from Debian unstable (main) NEWS: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/blob/master/NEWS shared-mime-info 1.15 (2019-30-10) * Add Kindle 8 eBook format * Fix some HTML files being detected as XML shared-mime-info 1.14 (2019-20-09) * Add mime-type for QCOW images * Fix matching SVG files in some circumstances (again) shared-mime-info 1.13.1 (2019-11-09) * Fix matching SVG files in some circumstances shared-mime-info 1.13 (2019-11-09) * Add code of conduct document * Use itstool and gettext to generate translations * Add content-tree type for OSTree USB repositories * Add match for MPEG-4 v1 videos * Adjust a lot of user readable mime-type descriptions * Fix WOFF/WOFF2 mime-types * Prefer text/html to XHTML for *.html files * Better magic for text/html files * Fix SVG magic for files embedded in HTML * Add *.sgd as a glob for Mega Drive ROMs Specification: - Mention that sub-class-of can be aliases Tools: - Enable Large File Support in update-mime-database Test suite: - Make test suite failures fatal - Add test for duplicate mime-types - Fix WarpScript test - Generate the specification in the CI, to avoid it becoming syntactically invalid shared-mime-info 1.12 (2019-17-01) * Fix build from tarball shared-mime-info 1.11 (2019-17-01) * Add mime-type for reStructuredText * Add mime-type for Groovy scripting language * Add mime-type for Gradle build tool * Add mime-type for Maven * Add mime-type for WarpScript source code * Add mime-type for zstd and tar.zst archives * Change the preferred suffix for image/jpeg from .jpeg to .jpg * Assign *.html to XHTML pages * Better detection for *.key files (Apple Keynote vs. GPG keys) * Give weight to one of the appimage patterns Tools: - Link to GitLab for contributions and bug reports - Loads of memory and file descriptor leak fixes Spec: - Clarify the availability of C character escape support Explanation of FeatureFreeze exception: New mime-type's and improvements to the existing ones useful for the life of the new LTS. The current version 1.10 has not been updated since September 2018. Changelog entries since current focal version 1.10-1: shared-mime-info (1.15-1) unstable; urgency=medium * New upstream release. Closes: #954669. * Update watch file for gitlab.freedesktop.org. * Update build-dependencies. * Remove ancient patches changing the magic database. Those should be reported upstream if they're still present. * Switch to debhelper-compat and bump compat to 12. * Don't hardcode full command path in postinst. -- Emilio Pozuelo Monfort Tue, 24 Mar 2020 16:58:21 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1868927/+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 1868706] Re: Snapd postinst script hangs
Ok, reproduced with focal and broken seeds from an older image, symptoms are exactly the same (including ps/pstree output). The problem is caused by blocking on snapd.seeded.service (which waits for seeding to complete, but it's never going to complete with broken seeds). Given that this is an edge case (we don't expect images with broken seeds) and focal images have been fixed already, I'm lowering the priority. We will discuss what to do to handle this gracefully. ** Changed in: snapd Importance: Critical => High -- 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/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+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 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
I just tried to reproduce this problem, but couldn't. Installed the ubuntu 20.04 daily built image on my Lenovo X1 Carbon 7th sudo apt dist-upgrade reboot and check the pulesaudio version, it is 1:13.99.1-1ubuntu1 Paring a bluetooth headset (Sony WL-1000X), it connected successfully check the gnome-sound-setting: the output device is Headset - WL-1000X the configuration is High Fidelity Playback (A2DP Sink) Click test Front left and Front right, the sound output to my BT headset choose speaker - Cannon point-LP High Definition...(internal speaker), click test front left and front right,the sound output to internal speaker. Disconnect the BT headset plug a usb audio bar (one headphone and one microphone) the output device is automatically changed to USB Speaker - Audio Adapter (Unitek Y-247A) click the test front left and front right, the sound output to usb headphone manually select internal speaker from gnome-control-center, click front left and front right, the sound output to internal speaker. So looks like everything worked as expected. Didn't reproduce the problem. Also added my testing result to pulseaudio/issues/832. -- 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/1866194 Title: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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 1868706] Re: Snapd postinst script hangs
@Mark does 'snap changes' (and then 'snap change ' if you see any failed changes) reveal antyhing interesing? Some of the older focal images had broken seeds that would never succeed, potentially causing other issues. -- 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/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+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 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/508522 Title: Add automatic switching to HSP/HFP from A2DP when a mic is needed Status in PulseAudio: New Status in chromium-browser package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1869117] Re: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)
the python2.7 has nothing to do with python-pip ** Changed in: python2.7 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1869117 Title: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal) Status in python2.7 package in Ubuntu: Invalid Bug description: apt-get install python-pip fails in Ubuntu 20.04: The following packages have unmet dependencies: python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be installed Recommends: python-all-dev (>= 2.6) but it is not going to be installed Recommends: python-wheel but it is not going to be installed E: Unable to correct problems, you have held broken packages. The python-pip package needs to be updated to accept newer versions of python-pip-whl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1869117/+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 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
How to inform upstream (where) ? -- 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/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: New Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+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 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
ok. please notice that https://launchpad.net/~oibaf/+archive/ubuntu /graphics-drivers is working fine -- 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/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: New Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+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 1868706] Re: Snapd postinst script hangs
@sabdfl How was dpkg started? As root systemctl should not ask for password. @stolowski The snapd version seems to be a git snapshot, not one from the archive. Marking as invalid for dpkg and systemd because nothing shows that there would be any issue with their behaviour. Please reopen the bug against one of them if the root cause seem to be in them. ** Changed in: systemd (Ubuntu) Status: Confirmed => 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/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+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 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
sure, it's there https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398 ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues #398 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398 ** Description changed: + Also created bug on upstream : + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398 + + This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: - default via 192.168.101.1 dev eno1 proto static metric 100 - 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 - 169.254.0.0/16 dev eno1 scope link metric 1000 - 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 + default via 192.168.101.1 dev eno1 proto static metric 100 + 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 + 169.254.0.0/16 dev eno1 scope link metric 1000 + 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: - Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device - - X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory + Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device + + X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: - NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME - netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection + NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME + netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.22.10 connected starting full enabled disabled disabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.22.10 connected starting full enabled disabled disabled enabled enabled -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu.
[Touch-packages] [Bug 1868706] Re: Snapd postinst script hangs
** Changed in: dpkg (Ubuntu) Status: Confirmed => 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/1868706 Title: Snapd postinst script hangs Status in snapd: Triaged Status in dpkg package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: On a machine which has been tracking upgrades for a while, I am unable to install new versions of snapd. The install process stalls indefinitely. Processes running suggest this is a hang in the postinst: ~$ ps ax | grep dpkg 2388 pts/1Ss+0:00 /usr/bin/dpkg --status-fd 25 --configure --pending 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2875 pts/2S+ 0:00 grep --color=auto dpkg ~$ pstree 2388 dpkg───snapd.postinst───systemctl───systemd-tty-ask ~$ ps ax | grep snapd 732 ?Ssl0:00 /usr/lib/snapd/snapd 2389 pts/1S+ 0:00 /bin/sh /var/lib/dpkg/info/snapd.postinst configure 2.43.3+git1.8109f8 2452 pts/1S+ 0:00 /bin/systemctl start snapd.autoimport.service snapd.core-fixup.service snapd.recovery-chooser-trigger.service snapd.seeded.service snapd.service snapd.snap-repair.timer snapd.socket snapd.system-shutdown.service 2880 pts/2S+ 0:00 grep --color=auto snapd To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1868706/+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 1857046] Re: lxc 3.0.4-0ubuntu2 ADT test failure with linux 5.5.0-2.3
No, but might have been an allocation error which we fixed in the meantime. The error can only come from: ENOMEM The kernel could not allocate a free page to copy filenames or data into. That's the only reason mount() can fail with ENOMEM from just glancing at the manpage. I'll take another close look at the codepath now, to make sure that there's not an obvious bug in there but otherwise I'd close and see if this happens again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1857046 Title: lxc 3.0.4-0ubuntu2 ADT test failure with linux 5.5.0-2.3 Status in lxc package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/amd64/l/lxc/20191218_145013_76e0c@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/arm64/l/lxc/20191218_165648_a3f34@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/ppc64el/l/lxc/20191218_151902_0998c@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/s390x/l/lxc/20191218_152251_9101b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1857046/+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 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
let upstream know that the fix is needed in 20.0.x.. that way focal will get it (and bionic too, when mesa is backported for 18.04.5) -- 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/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: New Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+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 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
@Alex, could you upstream it to https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/ -- 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/1868915 Title: [focal] nm-online -s --timeout=10 timeout every time Status in MAAS: New Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Bug description: This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: default via 192.168.101.1 dev eno1 proto static metric 100 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected starting full enabled disabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1868915/+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 1869127] Re: after upgrade uuidgen crashes, complaining about version of libuuid.1
No problem, glad that you figured it you! I'm closing the bug as invalid now ** Changed in: util-linux (Ubuntu) Importance: Undecided => Low ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1869127 Title: after upgrade uuidgen crashes, complaining about version of libuuid.1 Status in util-linux package in Ubuntu: Invalid Bug description: I execute uuidgen and get: $ uuidgen uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by uuidgen I tried: steven@steven-ge40:~$ sudo apt-get clean steven@steven-ge40:~$ sudo apt-get install --reinstall libuuid1 Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded. Need to get 41.6 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 libuuid1 amd64 2.34-0.1ubuntu2.4 [20.3 kB] Get:2 http://archive.ubuntu.com/ubuntu eoan-updates/main i386 libuuid1 i386 2.34-0.1ubuntu2.4 [21.3 kB] Fetched 41.6 kB in 1s (42.1 kB/s) (Reading database ... 605009 files and directories currently installed.) Preparing to unpack .../libuuid1_2.34-0.1ubuntu2.4_amd64.deb ... Unpacking libuuid1:amd64 (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2.4) ... Preparing to unpack .../libuuid1_2.34-0.1ubuntu2.4_i386.deb ... Unpacking libuuid1:i386 (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2.4) ... Setting up libuuid1:amd64 (2.34-0.1ubuntu2.4) ... Setting up libuuid1:i386 (2.34-0.1ubuntu2.4) ... Processing triggers for libc-bin (2.30-0ubuntu2.1) ... steven@steven-ge40:~$ uuidgen uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by uuidgen) But that did not help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: uuid-runtime 2.34-0.1ubuntu2.4 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 26 13:27:34 2020 InstallationDate: Installed on 2015-03-30 (1822 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150319) SourcePackage: util-linux UpgradeStatus: Upgraded to eoan on 2019-10-31 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1869127/+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 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
I've just try Focal fossa with new 20.0.2-1ubuntu1 Same problem, half screen picture for VAAPI - bob -- 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/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: New Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+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 1869117] Re: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python2.7 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1869117 Title: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal) Status in python2.7 package in Ubuntu: Confirmed Bug description: apt-get install python-pip fails in Ubuntu 20.04: The following packages have unmet dependencies: python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be installed Recommends: python-all-dev (>= 2.6) but it is not going to be installed Recommends: python-wheel but it is not going to be installed E: Unable to correct problems, you have held broken packages. The python-pip package needs to be updated to accept newer versions of python-pip-whl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1869117/+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 1410558] Re: ps doesn't support "thcount" format specifier on Xenial
This bug was fixed in the package procps - 2:3.3.10-4ubuntu2.5 --- procps (2:3.3.10-4ubuntu2.5) xenial; urgency=medium * d/p/lp1410558-fix-thcount.patch: - fix 'thcount' format specifier (LP: #1410558) -- Heitor Alves de Siqueira Fri, 07 Feb 2020 14:06:26 + ** Changed in: procps (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1410558 Title: ps doesn't support "thcount" format specifier on Xenial Status in procps package in Ubuntu: Fix Released Status in procps source package in Xenial: Fix Released Bug description: [Impact] ps -o thcount prints out an error (error: unknown user-defined format specifier "thcount") [Description] The Xenial version of procps has a bug in the thcount format specifier. ps doesn't recognize it, and complains about an unknown user-defined format. This is due to the format specifier table in ps/output.c, which is queried with a binary search. Since the "thcount" entry appears out of order in Xenial, it can't be looked up and the program fails with the "unknown user-defined format specifier" error. This has been fixed upstream by the commit below: - Fix for Bug:1174313 (3a52dfa34027) $ git describe --contains 3a52dfa34027 v3.3.12~58^2 $ rmadison procps procps | 2:3.3.10-4ubuntu2 | xenial | source, ... procps | 2:3.3.10-4ubuntu2.4 | xenial-security | source, ... procps | 2:3.3.10-4ubuntu2.4 | xenial-updates | source, ... < procps | 2:3.3.12-3ubuntu1 | bionic | source, ... procps | 2:3.3.12-3ubuntu1.1 | bionic-security | source, ... procps | 2:3.3.12-3ubuntu1.2 | bionic-updates | source, ... Releases starting with Bionic already have this fix, so it's only needed for Xenial. [Test case] 1. Boot up a Xenial environment with e.g. an lxd container: # lxc launch images:ubuntu/xenial xenial 2. Execute ps with the '-o thcount' options: # lxc exec xenial -- ps -o thcount error: unknown user-defined format specifier "thcount" Usage: ps [options] Try 'ps --help ' or 'ps --help ' for additional help text. For more details see ps(1). [Regression Potential] The fix just fixes the order of two entries in the format specifier array, so the regression potential is very low. Furthermore, the patch has been present and tested in up-to-date versions of procps since Bionic. Any new regressions introduced in Xenial will be checked with autopkgtest. [Original Description] In Ubuntu 12.04.5 LTS (procps 1:3.2.8-11ubuntu6.3), the following worked fine: $ export PS_FORMAT=thcount $ ps THCNT 1 1 In Ubuntu 14.04.1 LTS (procps 1:3.3.9-1ubuntu2), it does not work anymore: $ export PS_FORMAT=thcount $ ps warning: $PS_FORMAT ignored. (unknown user-defined format specifier "thcount") PID TTY TIME CMD 6593 pts/100:00:00 ps 16633 pts/100:00:00 bash Other PS_FORMAT specifiers still work fine (I have tried many, but not all). In real-life usage, a more complex PS_FORMAT would of course be used, such as PS_FORMAT=pid,s,thcount,nice,euser,egroup,etime,cputime,%mem,rssize:6,size:7,vsize:7,command Workaround: use nlwp instead of thcount (they are alias to the same data, and nlwp works fine in both versions). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1410558/+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 1410558] Update Released
The verification of the Stable Release Update for procps has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1410558 Title: ps doesn't support "thcount" format specifier on Xenial Status in procps package in Ubuntu: Fix Released Status in procps source package in Xenial: Fix Released Bug description: [Impact] ps -o thcount prints out an error (error: unknown user-defined format specifier "thcount") [Description] The Xenial version of procps has a bug in the thcount format specifier. ps doesn't recognize it, and complains about an unknown user-defined format. This is due to the format specifier table in ps/output.c, which is queried with a binary search. Since the "thcount" entry appears out of order in Xenial, it can't be looked up and the program fails with the "unknown user-defined format specifier" error. This has been fixed upstream by the commit below: - Fix for Bug:1174313 (3a52dfa34027) $ git describe --contains 3a52dfa34027 v3.3.12~58^2 $ rmadison procps procps | 2:3.3.10-4ubuntu2 | xenial | source, ... procps | 2:3.3.10-4ubuntu2.4 | xenial-security | source, ... procps | 2:3.3.10-4ubuntu2.4 | xenial-updates | source, ... < procps | 2:3.3.12-3ubuntu1 | bionic | source, ... procps | 2:3.3.12-3ubuntu1.1 | bionic-security | source, ... procps | 2:3.3.12-3ubuntu1.2 | bionic-updates | source, ... Releases starting with Bionic already have this fix, so it's only needed for Xenial. [Test case] 1. Boot up a Xenial environment with e.g. an lxd container: # lxc launch images:ubuntu/xenial xenial 2. Execute ps with the '-o thcount' options: # lxc exec xenial -- ps -o thcount error: unknown user-defined format specifier "thcount" Usage: ps [options] Try 'ps --help ' or 'ps --help ' for additional help text. For more details see ps(1). [Regression Potential] The fix just fixes the order of two entries in the format specifier array, so the regression potential is very low. Furthermore, the patch has been present and tested in up-to-date versions of procps since Bionic. Any new regressions introduced in Xenial will be checked with autopkgtest. [Original Description] In Ubuntu 12.04.5 LTS (procps 1:3.2.8-11ubuntu6.3), the following worked fine: $ export PS_FORMAT=thcount $ ps THCNT 1 1 In Ubuntu 14.04.1 LTS (procps 1:3.3.9-1ubuntu2), it does not work anymore: $ export PS_FORMAT=thcount $ ps warning: $PS_FORMAT ignored. (unknown user-defined format specifier "thcount") PID TTY TIME CMD 6593 pts/100:00:00 ps 16633 pts/100:00:00 bash Other PS_FORMAT specifiers still work fine (I have tried many, but not all). In real-life usage, a more complex PS_FORMAT would of course be used, such as PS_FORMAT=pid,s,thcount,nice,euser,egroup,etime,cputime,%mem,rssize:6,size:7,vsize:7,command Workaround: use nlwp instead of thcount (they are alias to the same data, and nlwp works fine in both versions). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1410558/+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 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug
This bug was fixed in the package apport - 2.20.11-0ubuntu8.7 --- apport (2.20.11-0ubuntu8.7) eoan; urgency=medium * apport/ui.py: Always allow users to use ubuntu-bug or apport-collect regardless of the Problem Reporting setting as they are manually invoked and not automatically generated like a crash report. (LP: #1814611) -- Brian Murray Wed, 18 Mar 2020 15:21:14 -0700 ** Changed in: apport (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: Fix Released Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Regression Potential The fix is just setting the value of a variable to True instead of checking to see if whoopsie is enabled so there really isn't any. However, it could cause a regression if there's a typo in the line being changed. Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1814611] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: Fix Released Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Regression Potential The fix is just setting the value of a variable to True instead of checking to see if whoopsie is enabled so there really isn't any. However, it could cause a regression if there's a typo in the line being changed. Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1869127] Re: after upgrade uuidgen crashes, complaining about version of libuuid.1
Argh. For some reason which I can NOT explain. my libuuid.so.1 symlink was not pointing to libuuid.so.1.3.0 but to a file called libuuid.so.1.3.0.original And i just found libblkid is similarly redirected. I remade the symlinks (and deleted those bogus files) and it all works now. Sorry for the false report. But thank you for the help, it made it obvious what the problem was. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1869127 Title: after upgrade uuidgen crashes, complaining about version of libuuid.1 Status in util-linux package in Ubuntu: New Bug description: I execute uuidgen and get: $ uuidgen uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by uuidgen I tried: steven@steven-ge40:~$ sudo apt-get clean steven@steven-ge40:~$ sudo apt-get install --reinstall libuuid1 Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded. Need to get 41.6 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 libuuid1 amd64 2.34-0.1ubuntu2.4 [20.3 kB] Get:2 http://archive.ubuntu.com/ubuntu eoan-updates/main i386 libuuid1 i386 2.34-0.1ubuntu2.4 [21.3 kB] Fetched 41.6 kB in 1s (42.1 kB/s) (Reading database ... 605009 files and directories currently installed.) Preparing to unpack .../libuuid1_2.34-0.1ubuntu2.4_amd64.deb ... Unpacking libuuid1:amd64 (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2.4) ... Preparing to unpack .../libuuid1_2.34-0.1ubuntu2.4_i386.deb ... Unpacking libuuid1:i386 (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2.4) ... Setting up libuuid1:amd64 (2.34-0.1ubuntu2.4) ... Setting up libuuid1:i386 (2.34-0.1ubuntu2.4) ... Processing triggers for libc-bin (2.30-0ubuntu2.1) ... steven@steven-ge40:~$ uuidgen uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by uuidgen) But that did not help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: uuid-runtime 2.34-0.1ubuntu2.4 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 26 13:27:34 2020 InstallationDate: Installed on 2015-03-30 (1822 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150319) SourcePackage: util-linux UpgradeStatus: Upgraded to eoan on 2019-10-31 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1869127/+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 1794523] Re: lxc-net.service is not properly ordered with network-online.target
Hello. Only the Requires= will make it fail, no Wants= A weaker version of Requires=. Units listed in this option will be started if the configuring unit is. However, if the listed units fail to start or cannot be added to the transaction, this has no impact on the validity of the transaction as a whole. This is the recommended way to hook start-up of one unit to the start-up of another unit. https://manpages.ubuntu.com/manpages/bionic/en/man5/systemd.unit.5.html Regards. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1794523 Title: lxc-net.service is not properly ordered with network-online.target Status in lxc package in Ubuntu: Incomplete Bug description: I made several tests and I figure out that the lxc-net.service is missing a Wants= directive to be properly ordered against network- online.target. As I understand the systemd.unit manpage, to be properly ordered a unit must define a Requires=/Wants= in addition to an After=/Before=. Regards. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1794523/+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 1869127] Re: after upgrade uuidgen crashes, complaining about version of libuuid.1
Thank you for your bug report, unsure what's going on there what is the output of $ md5sum /lib/x86_64-linux-gnu/libuuid.so.1 I just tried on a new 19.10 instance $ dpkg -l | grep uuid ii libuuid1:amd64 2.34-0.1ubuntu2.4 amd64 Universally Unique ID library ii uuid-runtime 2.34-0.1ubuntu2.4 amd64 runtime components for the Universally Unique ID library $ md5sum /lib/x86_64-linux-gnu/libuuid.so.1 d4cdde44bff22d9720e488b0f55a0d8b /lib/x86_64-linux-gnu/libuuid.so.1 $ nm -D /lib/x86_64-linux-gnu/libuuid.so.1 | grep UUID_ A UUID_1.0 A UUID_2.20 A UUID_2.31 $ uuidgen 51c34b6d-ecd4-48dd-b7c4-f7477606824a $ ldd -v `which uuidgen` ... Version information: /usr/bin/uuidgen: libc.so.6 (GLIBC_2.3.4) => /lib/x86_64-linux-gnu/libc.so.6 libc.so.6 (GLIBC_2.4) => /lib/x86_64-linux-gnu/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6 libuuid.so.1 (UUID_2.31) => /lib/x86_64-linux-gnu/libuuid.so.1 libuuid.so.1 (UUID_1.0) => /lib/x86_64-linux-gnu/libuuid.so.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1869127 Title: after upgrade uuidgen crashes, complaining about version of libuuid.1 Status in util-linux package in Ubuntu: New Bug description: I execute uuidgen and get: $ uuidgen uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by uuidgen I tried: steven@steven-ge40:~$ sudo apt-get clean steven@steven-ge40:~$ sudo apt-get install --reinstall libuuid1 Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded. Need to get 41.6 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 libuuid1 amd64 2.34-0.1ubuntu2.4 [20.3 kB] Get:2 http://archive.ubuntu.com/ubuntu eoan-updates/main i386 libuuid1 i386 2.34-0.1ubuntu2.4 [21.3 kB] Fetched 41.6 kB in 1s (42.1 kB/s) (Reading database ... 605009 files and directories currently installed.) Preparing to unpack .../libuuid1_2.34-0.1ubuntu2.4_amd64.deb ... Unpacking libuuid1:amd64 (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2.4) ... Preparing to unpack .../libuuid1_2.34-0.1ubuntu2.4_i386.deb ... Unpacking libuuid1:i386 (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2.4) ... Setting up libuuid1:amd64 (2.34-0.1ubuntu2.4) ... Setting up libuuid1:i386 (2.34-0.1ubuntu2.4) ... Processing triggers for libc-bin (2.30-0ubuntu2.1) ... steven@steven-ge40:~$ uuidgen uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by uuidgen) But that did not help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: uuid-runtime 2.34-0.1ubuntu2.4 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 26 13:27:34 2020 InstallationDate: Installed on 2015-03-30 (1822 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150319) SourcePackage: util-linux UpgradeStatus: Upgraded to eoan on 2019-10-31 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1869127/+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 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
** Attachment added: "dmesg.log" https://bugs.launchpad.net/oem-priority/+bug/1868915/+attachment/5341768/+files/dmesg.log -- 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/1868915 Title: [focal] nm-online -s --timeout=10 timeout every time Status in MAAS: New Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Bug description: This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: default via 192.168.101.1 dev eno1 proto static metric 100 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected starting full enabled disabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1868915/+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 1825000] Re: Add ability for mirrors to distinguish interactive and non-interactive apt runs
Probably ! What is it going to be for interactive uses though ? -- 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/1825000 Title: Add ability for mirrors to distinguish interactive and non-interactive apt runs Status in apt package in Ubuntu: In Progress Status in apt source package in Eoan: Triaged Bug description: As part of a larger scale plan to manage traffic to the main archive servers it would be useful if apt could provide a facility for us to identify interactive vs. non-interactive traffic on the server side, ideally via a header of some kind. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825000/+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 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
** Tags added: rls-ff-incomong ** Tags removed: rls-ff-incomong ** Tags added: rls-ff-incoming -- 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/1866194 Title: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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 1869127] Re: after upgrade uuidgen crashes, complaining about version of libuuid.1
steven@steven-ge40:~$ ldd -v `which uuidgen` /usr/bin/uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by /usr/bin/uuidgen) linux-vdso.so.1 (0x7ffdf0ce4000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f6f9a079000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f6f99e88000) /lib64/ld-linux-x86-64.so.2 (0x7f6f9a2c7000) Version information: /usr/bin/uuidgen: libc.so.6 (GLIBC_2.3.4) => /lib/x86_64-linux-gnu/libc.so.6 libc.so.6 (GLIBC_2.4) => /lib/x86_64-linux-gnu/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6 libuuid.so.1 (UUID_2.31) => not found libuuid.so.1 (UUID_1.0) => /lib/x86_64-linux-gnu/libuuid.so.1 /lib/x86_64-linux-gnu/libuuid.so.1: ld-linux-x86-64.so.2 (GLIBC_2.3) => /lib64/ld-linux-x86-64.so.2 libc.so.6 (GLIBC_2.3) => /lib/x86_64-linux-gnu/libc.so.6 libc.so.6 (GLIBC_2.3.4) => /lib/x86_64-linux-gnu/libc.so.6 libc.so.6 (GLIBC_2.4) => /lib/x86_64-linux-gnu/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6 /lib/x86_64-linux-gnu/libc.so.6: ld-linux-x86-64.so.2 (GLIBC_2.3) => /lib64/ld-linux-x86-64.so.2 ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1869127 Title: after upgrade uuidgen crashes, complaining about version of libuuid.1 Status in util-linux package in Ubuntu: New Bug description: I execute uuidgen and get: $ uuidgen uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by uuidgen I tried: steven@steven-ge40:~$ sudo apt-get clean steven@steven-ge40:~$ sudo apt-get install --reinstall libuuid1 Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded. Need to get 41.6 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 libuuid1 amd64 2.34-0.1ubuntu2.4 [20.3 kB] Get:2 http://archive.ubuntu.com/ubuntu eoan-updates/main i386 libuuid1 i386 2.34-0.1ubuntu2.4 [21.3 kB] Fetched 41.6 kB in 1s (42.1 kB/s) (Reading database ... 605009 files and directories currently installed.) Preparing to unpack .../libuuid1_2.34-0.1ubuntu2.4_amd64.deb ... Unpacking libuuid1:amd64 (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2.4) ... Preparing to unpack .../libuuid1_2.34-0.1ubuntu2.4_i386.deb ... Unpacking libuuid1:i386 (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2.4) ... Setting up libuuid1:amd64 (2.34-0.1ubuntu2.4) ... Setting up libuuid1:i386 (2.34-0.1ubuntu2.4) ... Processing triggers for libc-bin (2.30-0ubuntu2.1) ... steven@steven-ge40:~$ uuidgen uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by uuidgen) But that did not help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: uuid-runtime 2.34-0.1ubuntu2.4 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 26 13:27:34 2020 InstallationDate: Installed on 2015-03-30 (1822 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150319) SourcePackage: util-linux UpgradeStatus: Upgraded to eoan on 2019-10-31 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1869127/+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 1869127] [NEW] after upgrade uuidgen crashes, complaining about version of libuuid.1
Public bug reported: I execute uuidgen and get: $ uuidgen uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by uuidgen I tried: steven@steven-ge40:~$ sudo apt-get clean steven@steven-ge40:~$ sudo apt-get install --reinstall libuuid1 Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded. Need to get 41.6 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 libuuid1 amd64 2.34-0.1ubuntu2.4 [20.3 kB] Get:2 http://archive.ubuntu.com/ubuntu eoan-updates/main i386 libuuid1 i386 2.34-0.1ubuntu2.4 [21.3 kB] Fetched 41.6 kB in 1s (42.1 kB/s) (Reading database ... 605009 files and directories currently installed.) Preparing to unpack .../libuuid1_2.34-0.1ubuntu2.4_amd64.deb ... Unpacking libuuid1:amd64 (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2.4) ... Preparing to unpack .../libuuid1_2.34-0.1ubuntu2.4_i386.deb ... Unpacking libuuid1:i386 (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2.4) ... Setting up libuuid1:amd64 (2.34-0.1ubuntu2.4) ... Setting up libuuid1:i386 (2.34-0.1ubuntu2.4) ... Processing triggers for libc-bin (2.30-0ubuntu2.1) ... steven@steven-ge40:~$ uuidgen uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by uuidgen) But that did not help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: uuid-runtime 2.34-0.1ubuntu2.4 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 26 13:27:34 2020 InstallationDate: Installed on 2015-03-30 (1822 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150319) SourcePackage: util-linux UpgradeStatus: Upgraded to eoan on 2019-10-31 (146 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1869127 Title: after upgrade uuidgen crashes, complaining about version of libuuid.1 Status in util-linux package in Ubuntu: New Bug description: I execute uuidgen and get: $ uuidgen uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by uuidgen I tried: steven@steven-ge40:~$ sudo apt-get clean steven@steven-ge40:~$ sudo apt-get install --reinstall libuuid1 Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded. Need to get 41.6 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 libuuid1 amd64 2.34-0.1ubuntu2.4 [20.3 kB] Get:2 http://archive.ubuntu.com/ubuntu eoan-updates/main i386 libuuid1 i386 2.34-0.1ubuntu2.4 [21.3 kB] Fetched 41.6 kB in 1s (42.1 kB/s) (Reading database ... 605009 files and directories currently installed.) Preparing to unpack .../libuuid1_2.34-0.1ubuntu2.4_amd64.deb ... Unpacking libuuid1:amd64 (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2.4) ... Preparing to unpack .../libuuid1_2.34-0.1ubuntu2.4_i386.deb ... Unpacking libuuid1:i386 (2.34-0.1ubuntu2.4) over (2.34-0.1ubuntu2.4) ... Setting up libuuid1:amd64 (2.34-0.1ubuntu2.4) ... Setting up libuuid1:i386 (2.34-0.1ubuntu2.4) ... Processing triggers for libc-bin (2.30-0ubuntu2.1) ... steven@steven-ge40:~$ uuidgen uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found (required by uuidgen) But that did not help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: uuid-runtime 2.34-0.1ubuntu2.4 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 26 13:27:34 2020 InstallationDate: Installed on 2015-03-30 (1822 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150319) SourcePackage: util-linux UpgradeStatus: Upgraded to eoan on 2019-10-31 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1869127/+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 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
It seems this issue only happens to machine which eth port be renamed as eno1. It can not be reproduced on another machine which eth port be renamed to enp2s0. -- 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/1868915 Title: [focal] nm-online -s --timeout=10 timeout every time Status in MAAS: New Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Bug description: This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: default via 192.168.101.1 dev eno1 proto static metric 100 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected starting full enabled disabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1868915/+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 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
** No longer affects: pulseaudio (Ubuntu) ** No longer affects: systemd (Ubuntu) ** No longer affects: udev (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: In Progress Status in libmtp package in Debian: Unknown Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+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
