[Touch-packages] [Bug 1563110]
Cannabidiol (CBD) has been as of late shrouded in the media, and you may have even considered it to be an include sponsor to your post-exercise smoothie or morning espresso. What precisely is CBD? For what reason is it out of nowhere so famous? https://cforcbd.com/products/cbd-oil/ -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Fix Released Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1766503] Re: ibus-* randomly use high CPU
Actually I have seen this a couple of times in the past week or so. I'll reconfirm if and when it happens again. ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in The Ubuntu Power Consumption Project: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 1766503] Re: ibus-* randomly use high CPU
One comment. This situation does NOT happen, when I use Atom to edit. It is happening only with Xed Editor. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in The Ubuntu Power Consumption Project: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 1766503] Re: ibus-* randomly use high CPU
I can confirm. My system is: adasiek@mint-desktop:~$ lsb_release -a No LSB modules are available. Distributor ID: LinuxMint Description:Linux Mint 19.3 Tricia Release:19.3 Codename: tricia adasiek@mint-desktop:~$ uname -a Linux mint-desktop 5.0.0-32-generic #34~18.04.2-Ubuntu SMP Thu Oct 10 10:36:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I have quite good machine: processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 94 model name : Intel(R) Core(TM) i7-6770HQ CPU @ 2.60GHz stepping: 3 microcode : 0xd6 cpu MHz : 1191.362 cache size : 6144 KB physical id : 0 siblings: 8 core id : 3 cpu cores : 4 and ibus daemon is running randomly about 100% cpu. Keeping htop opened in terminal helps. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in The Ubuntu Power Consumption Project: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Additional observations. MAAS is being used to deploy the system and configure the bond interface and settings. MAAS allows you to specify which is the primary interface, with the other being the backup, for the active-backup bonding mode. However, it does not appear to be working -it's not passing along a primary primitive, for instance, in the netplan yaml or otherwise resulting in this being honored (still need to confirm). MAAS allows you to enter a mac address for the bond interface, but if not supplied, by default it will use the mac address of the "primary" interface, as configured. MAAS then populates the /etc/netplan/50-cloud-init.yaml, including a macaddr= line with the default. netplan then passes that along to systemd-networkd. The bonding kernel, however, will use as the active interface whichever interface is first attached to the bond (i.e., which completes getting attached to the bond interface first) in the absence of a primary= directive. The bonding kernel will, however, use the mac addr supplied as an override. So let's say the active interface was configured in MAAS to be f0, and it's mac is used to be the mac address of the bond, but f1 (the second port of the NIC) actually gets attached first to the bond and is used as the active interface by the bond. We have a situation where f0 = backup, f1 = active, and bond0 is using the mac of f0. While this should work, there is a potential for problems depending on the circumstances. It's likely this has nothing to do with our current issue, but here for completeness. Will see if we can test/confirm. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Changed in: curtin (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: curtin (Ubuntu Focal) Assignee: (unassigned) => Ryan Harper (raharper) -- 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/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: In Progress Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: In Progress Status in util-linux source package in Focal: New Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
That is because the ucm is not loaded successfully. please change cset "name='Headset Mic Boost Volume' 1" to cset "name='Mic Boost Volume' 2" in the all LENOVO_*/LENOVO_*.conf; then reboot. If it doesn't work, please upload log of "pactl list cards", maybe your machine has a specific dmi string that those 4 folders doesn't match the cardlongname of your machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
** Attachment added: "Screenshot from 2020-02-13 00-50-52.png" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5327774/+files/Screenshot%20from%202020-02-13%2000-50-52.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
It seems that adding "load-module module-alsa-source device=hw:0,7" to "/etc/pulse/default.pa" i have the mic recognized and working, see the attachment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report
I personally noticed this with a crash file with the following
permissions:
-rw-r- 1 bdmurray whoopsie 194K Feb 7 15:22 _usr_bin_seeded-in-
ubuntu.1000.crash
whoopsie-upload-all, which runs as root, is unable to append to the
crash file due to /proc/sys/fs/protected_regular being set to 1.
Changing that file to 0 allows whoopsie-upload-all to run. Here's a
simple test case, thanks Steve!
# echo 0 > /proc/sys/fs/protected_regular
# python3 -c "foo = open('/var/crash/_usr_bin_reportbug.1000.crash', 'ab')"
# echo 1 > /proc/sys/fs/protected_regular
# python3 -c "foo = open('/var/crash/_usr_bin_reportbug.1000.crash', 'ab')"
Traceback (most recent call last):
File "", line 1, in
PermissionError: [Errno 13] Permission denied:
'/var/crash/_usr_bin_reportbug.1000.crash'
--
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/1848064
Title:
/usr/share/apport/whoopsie-upload-
all:PermissionError:/usr/share/apport/whoopsie-upload-
all@168:collect_info:process_report
Status in apport package in Ubuntu:
Confirmed
Status in apport source package in Eoan:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
apport. This problem was most recently seen with package version
2.20.11-0ubuntu8, the problem page at
https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1848064/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: gerbera (Ubuntu) Status: New => In Progress -- 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/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: New Status in hoel package in Ubuntu: New Status in jabberd2 package in Ubuntu: New Status in kannel package in Ubuntu: New Status in libgda5 package in Ubuntu: New Status in libodb-mysql package in Ubuntu: New Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: gearmand (Ubuntu) Status: New => In Progress -- 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/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: New Status in gnokii package in Ubuntu: New Status in hoel package in Ubuntu: New Status in jabberd2 package in Ubuntu: New Status in kannel package in Ubuntu: New Status in libgda5 package in Ubuntu: New Status in libodb-mysql package in Ubuntu: New Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: argus-clients (Ubuntu) Status: New => In Progress ** Changed in: asterisk (Ubuntu) Status: New => In Progress ** Changed in: gambas3 (Ubuntu) Status: New => In Progress ** Changed in: clickhouse (Ubuntu) Status: New => In Progress ** Changed in: cppdb (Ubuntu) Status: New => In Progress ** Changed in: dballe (Ubuntu) Status: New => In Progress -- 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/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: New Status in gerbera package in Ubuntu: New Status in gnokii package in Ubuntu: New Status in hoel package in Ubuntu: New Status in jabberd2 package in Ubuntu: New Status in kannel package in Ubuntu: New Status in libgda5 package in Ubuntu: New Status in libodb-mysql package in Ubuntu: New Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1861472] Re: upgrade from fresh bionic to focal needlessly prompts user
** Changed in: openssh (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1861472 Title: upgrade from fresh bionic to focal needlessly prompts user Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: New Bug description: Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts for how to handle a change to /etc/ssh/sshd_config To reproduce the issue: lxc launch ubuntu:18.04 u18 lxc exec u18 -- bash # within container do-release-upgrade -d # select restart services when prompted Eventually you'll be prompted to accept changes to /etc/ssh/sshd_config or not because of "local changes". Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.1p1-5 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 03:37:55 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1861472/+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 1862846] Re: Crash and failure installing focal
** Changed in: util-linux (Debian) Status: Unknown => New -- 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/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Triaged Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Triaged Status in util-linux source package in Focal: New Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
On a machine Lenovo Thinkpad X1 Carbon 7th, running Bionic, verification failed. What i did: 1) Enabled Proposed repository 2) Installed libasound2: ``` > dpkg -l | grep libasound2 ii libasound2:amd64 1.1.3-5ubuntu0.3 amd64shared library for ALSA applications ii libasound2-data1.1.3-5ubuntu0.3 all Configuration files and profiles for ALSA drivers ii libasound2-plugins:amd64 1.1.1-1ubuntu1 amd64ALSA library additional plugins ``` 3) Upgraded linux-firmware to "1.173.15" 4) Installed "linux-oem-osp1" - "5.0.0-1038-oem-osp1" 5) Verified that all the UCM files are there: ``` ucm ├── apq8064-tabla-snd-card ├── broadwell-rt286 ├── chtrt5645 ├── DAISY-I2S ├── DB410c ├── Dell-WD15-Dock ├── GoogleNyan ├── HDAudio-Lenovo-DualCodecs ├── LENOVO-20QE000VMC-ThinkPadX1Carbon7th-20QE000VMC ├── LENOVO-20QESITR05-ThinkPadX1Carbon7th-20QESITR05 ├── LENOVO-20UB0SIT17-ThinkPadX1YogaGen5-20UB0SIT17 ├── LENOVO-MFG_IN_GO-ThinkPad-MFG_IN_GO ├── Manta-I2S ├── Manta-SPDIF ├── msm8974-taiko-mtp-snd-card ├── PandaBoard ├── PandaBoardES ├── PAZ00 ├── SDP4430 ├── skylake-rt286 ├── sof-skl_hda_card ├── tegraalc5632 ├── tegra-rt5640 ├── Tuna └── VEYRON-I2S ``` 6) Blacklisted "snd_soc_skl" and "snd_hda_intel" on "/etc/modprobe.d/blacklist.conf" 7) Verified that SOF firmware has been loaded correctly: ``` dmesg | grep sof | grep -iv microsoft [3.558639] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.558647] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.558800] sof-audio-pci :00:1f.3: use msi interrupt mode [3.567161] sof-audio-pci :00:1f.3: Linked as a consumer to :00:02.0 [3.567247] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.607451] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.607454] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.641575] sof-audio-pci :00:1f.3: unexpected ipc interrupt raised! [3.641577] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [3.723585] sof-audio-pci :00:1f.3: Firmware info: version 1:1:0-0f736 [3.723587] sof-audio-pci :00:1f.3: Firmware: ABI 3:7:0 Kernel ABI 3:6:0 [3.723588] sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel [3.723793] sof-audio-pci :00:1f.3: firmware boot complete [3.969365] sof-audio-pci :00:1f.3: Topology: ABI 3:7:0 Kernel ABI 3:6:0 [3.969366] sof-audio-pci :00:1f.3: warn: topology ABI is more recent than kernel [3.969369] sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp3 Tx not handled [3.970268] sof-audio-pci :00:1f.3: warning: widget type 0 name codec0_in not handled [3.970269] sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp2 Tx not handled [3.970986] sof-audio-pci :00:1f.3: warning: widget type 0 name codec1_in not handled [3.970989] sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp1 Tx not handled [3.971741] sof-audio-pci :00:1f.3: warning: widget type 1 name codec0_out not handled [3.971743] sof-audio-pci :00:1f.3: warning: widget type 7 name Analog CPU Playback not handled [3.972525] sof-audio-pci :00:1f.3: warning: widget type 1 name codec1_out not handled [3.972527] sof-audio-pci :00:1f.3: warning: widget type 7 name Digital CPU Playback not handled [3.972529] sof-audio-pci :00:1f.3: warning: widget type 0 name codec2_in not handled [3.972531] sof-audio-pci :00:1f.3: warning: widget type 7 name Alt Analog CPU Playback not handled [3.972532] sof-audio-pci :00:1f.3: warning: widget type 1 name codec2_out not handled [3.972534] sof-audio-pci :00:1f.3: warning: widget type 0 name Analog CPU Capture not handled [3.973342] sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp1_out not handled [3.973343] sof-audio-pci :00:1f.3: warning: widget type 0 name Digital CPU Capture not handled [3.974153] sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp2_out not handled [3.974155] sof-audio-pci :00:1f.3: warning: widget type 0 name Alt Analog CPU Capture not handled [3.974930] sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp3_out not handled [3.981916] sof-audio-pci :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [4.058562] input: sof-skl_hda_card Mic as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input16 [4.058597] input: sof-skl_hda_card Headphone as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input17 [4.058638] input: sof-skl_hda_card HDMI/DP,pcm=3 as
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Following my last comment, this is what i see from gnome audio settings. ** Attachment added: "Screenshot from 2020-02-12 23-28-30.png" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5327771/+files/Screenshot%20from%202020-02-12%2023-28-30.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863027] Re: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1863027 Title: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 Status in rsyslog package in Ubuntu: New Bug description: This error occurred in system update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: rsyslog 8.2001.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Wed Feb 12 19:18:14 2020 DuplicateSignature: package:rsyslog:8.2001.0-1ubuntu1 Installing new version of config file /etc/logcheck/ignore.d.server/rsyslog ... O usuário 'syslog' já é um membro de 'adm'. dpkg: error processing package rsyslog (--configure): installed rsyslog package post-installation script subprocess returned error exit status 10 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-02-01 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Python3Details: /usr/bin/python3.7, Python 3.7.6, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.9 SourcePackage: rsyslog Title: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1863027/+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 1863027] [NEW] package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10
Public bug reported: This error occurred in system update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: rsyslog 8.2001.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Wed Feb 12 19:18:14 2020 DuplicateSignature: package:rsyslog:8.2001.0-1ubuntu1 Installing new version of config file /etc/logcheck/ignore.d.server/rsyslog ... O usuário 'syslog' já é um membro de 'adm'. dpkg: error processing package rsyslog (--configure): installed rsyslog package post-installation script subprocess returned error exit status 10 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-02-01 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Python3Details: /usr/bin/python3.7, Python 3.7.6, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.9 SourcePackage: rsyslog Title: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1863027 Title: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 Status in rsyslog package in Ubuntu: New Bug description: This error occurred in system update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: rsyslog 8.2001.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Wed Feb 12 19:18:14 2020 DuplicateSignature: package:rsyslog:8.2001.0-1ubuntu1 Installing new version of config file /etc/logcheck/ignore.d.server/rsyslog ... O usuário 'syslog' já é um membro de 'adm'. dpkg: error processing package rsyslog (--configure): installed rsyslog package post-installation script subprocess returned error exit status 10 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-02-01 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Python3Details: /usr/bin/python3.7, Python 3.7.6, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.9 SourcePackage: rsyslog Title: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1863027/+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 1863026] [NEW] Remove my_bool typedef workaround
Public bug reported: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-removal ** Affects: argus-clients (Ubuntu) Importance: Undecided Status: New ** Affects: asterisk (Ubuntu) Importance: Undecided Status: New ** Affects: clickhouse (Ubuntu) Importance: Undecided Status: New ** Affects: cppdb (Ubuntu) Importance: Undecided Status: New ** Affects: dballe (Ubuntu) Importance: Undecided Status: New ** Affects: gambas3 (Ubuntu) Importance: Undecided Status: New ** Affects: gearmand (Ubuntu) Importance: Undecided Status: New ** Affects: gerbera (Ubuntu) Importance: Undecided Status: New ** Affects: gnokii (Ubuntu) Importance: Undecided Status: New ** Affects: hoel (Ubuntu) Importance: Undecided Status: New ** Affects: jabberd2 (Ubuntu) Importance: Undecided Status: New ** Affects: kannel (Ubuntu) Importance: Undecided Status: New ** Affects: libgda5 (Ubuntu) Importance: Undecided Status: New ** Affects: libodb-mysql (Ubuntu) Importance: Undecided Status: New ** Affects: lyricue (Ubuntu) Importance: Undecided Status: New ** Affects: motion (Ubuntu) Importance: Undecided Status: New ** Affects: mysql-8.0 (Ubuntu) Importance: High Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: mysql-ocaml (Ubuntu) Importance: Undecided Status: New ** Affects: mysqltcl (Ubuntu) Importance: Undecided Status: New ** Affects: opendnssec (Ubuntu) Importance: Undecided Status: New ** Affects: opensmtpd-extras (Ubuntu) Importance: Undecided Status: New ** Affects: orthanc-mysql (Ubuntu) Importance: Undecided Status: New ** Affects: pike8.0 (Ubuntu) Importance: Undecided Status: New ** Affects: pvpgn (Ubuntu) Importance: Undecided Status: New ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New ** Affects: redland (Ubuntu) Importance: Undecided Status: New ** Affects: tango (Ubuntu) Importance: Undecided Status: New ** Affects: tntdb (Ubuntu) Importance: Undecided Status: New ** Affects: voms-mysql-plugin (Ubuntu) Importance: Undecided Status: New ** Affects: vtk7 (Ubuntu) Importance: Undecided Status: New ** Affects: w1retap (Ubuntu) Importance: Undecided Status: New ** Affects: zoneminder (Ubuntu) Importance: Undecided Status: New ** Tags: server-next ** Description changed: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. + + PPA with test builds: + https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-removal ** Also affects: jabberd2 (Ubuntu) Importance: Undecided Status: New ** Also affects: dballe (Ubuntu) Importance: Undecided Status: New ** Also affects: cppdb (Ubuntu) Importance: Undecided Status: New ** Also affects: clickhouse (Ubuntu) Importance: Undecided Status: New ** Also affects: asterisk (Ubuntu) Importance: Undecided Status: New ** Also affects: argus-clients (Ubuntu) Importance: Undecided Status: New ** Also affects: mysql-ocaml (Ubuntu) Importance: Undecided Status: New ** Also affects: motion (Ubuntu) Importance: Undecided Status: New ** Also affects: lyricue (Ubuntu) Importance: Undecided Status: New ** Also affects: mysqltcl (Ubuntu) Importance: Undecided Status: New ** Also affects: pvpgn (Ubuntu) Importance: Undecided Status: New ** Also
[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes
@voldemark can you test with the systemd for Xenial and/or Bionic from this ppa to make sure it's working for you: https://launchpad.net/~ddstreet/+archive/ubuntu/systemd -- 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/1839290 Title: systemd doesn't restart a service after crashes Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: Fix Released Bug description: [impact] when a service configured to restart crashes, under certain configurations, that service is not correctly restarted. [test case] see comment 8 [regression potential] this changes the job mode of manager-triggered restarts to 'replace' any existing queued job(s), instead of failing if there are queued job(s). thus any regressions would occur when a service fails, that is configured to restart on failure. [scope] This is needed only for Xenial and Bionic. this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51 which is included already in Eoan. [other info] original description: --- Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1839290/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
This bug was fixed in the package rsyslog - 8.2001.0-1ubuntu1 --- rsyslog (8.2001.0-1ubuntu1) focal; urgency=medium [ Christian Ehrhardt ] * Merge with Debian unstable (LP: #1862762). Remaining changes: - debian/00rsyslog.conf Install tmpfiles.d snippet to ensure that the syslog group can write into /var/log/. - debian/50-default.conf: set of default rules for syslog + debian/50-default.conf: separated default rules + d/rsyslog.install: install default rules + d/rsyslog.postrm: clear default rules on purge + d/rsyslog.postrm: remove conf file in postrm on purge. manage with ucf + d/rsyslog.postinst: Adapt script to use ucf for Ubuntu's config files + debian/control: Add Depends for ucf - debian/rsyslog.conf: + enable $RepeatedMsgReduction to avoid bloating the syslog file. + enable $KLogPermitNonKernelFacility for non-kernel klog messages + Run as rsyslog:rsyslog, set $FileOwner to syslog + Remove rules moved to 50-default.conf - Add disabled by default AppArmor profile, debian/usr.sbin.rsyslogd + d/rsyslog.install: install apparmor rule + d/rules: use dh_apparmor to install profile before rsyslog is started + d/control: suggests apparmor (>= 2.3) + d/contrl: Build-Depends on dh-apparmor + debian/rsyslog.dirs: install /etc/apparmor.d/force-complain, /etc/apparmor.d/disable and /etc/apparmor.d/local + d/usr.sbin.rsyslogd apparmor profile for rsyslogd + debian/rsyslog.preinst: disable profile on clean installs. - d/rules: Fix LDFLAGS to avoid segfault on receipt of first message - Drop mmnormalize module, which depends on liblognorm from universe. + d/rules: drop --enable-mmnormalize + d/control: drop build dependency on liblognorm-dev - run as user syslog + d/rsyslog.postinst: fix ownership of /var/spool/rsyslog. + d/rsyslog.postinst: Create syslog user and add it to adm group + d/rsyslog.postinst: Adapt privileges for /var/log + debian/control: Add Depends for adduser - debian/dmesg.service: provide /var/log/dmesg.log as non log-rotated log for boot-time kernel messages. - debian/clean: Delete some files left over by the test suite * Dropped Changes: - d/control: drop rsyslog-mongodb package from suggests [ This part was forgotten to be droped in 8.32.0-1ubuntu1 ] - d/rules: Build with --disable-silent-rules to get useful build logs. [ was a no-op as verbose is the default ] - d/rsyslog.postinst: Clean up temporary syslog.service symlink [ Formerly missing in Changelog, now gone in Debian as well ] [ Simon Deziel ] * d/usr.sbin.rsyslogd: apparmor: fix typo in rule for (LP: #1827253). rsyslog (8.2001.0-1) unstable; urgency=medium * New upstream version 8.2001.0 * Set PYTHON=/usr/bin/python3 in debian/rules * Cherry-pick upstream patches which fix a couple of imfile issues * Add missing test files rsyslog (8.1911.0-1) unstable; urgency=medium * New upstream version 8.1911.0 * Follow DEP-14 naming * Rebase patches * Bump Standards-Version to 4.4.1 rsyslog (8.1910.0-2) unstable; urgency=medium * Fix file handle leak in omfile (Closes: #935300) rsyslog (8.1910.0-1) unstable; urgency=medium * New upstream version 8.1910.0 - Support cross-platform build for mysql/mariadb (Closes: #932068) - Fix heap overflow in pmaixforwardedfrom module (CVE-2019-17041, Closes: #942067) - Fix heap overflow in pmcisconames module (CVE-2019-17042, Closes: #942065) * Use Python3 for running the test suite (Closes: #938417) * Enable imfile tests rsyslog (8.1908.0-1) unstable; urgency=medium * New upstream version 8.1908.0 rsyslog (8.1907.0-2) unstable; urgency=medium * Enable OpenSSL network stream driver. Split the driver into a separate package named rsyslog-openssl and update the Suggests accordingly to make it the preferred TLS driver. (Closes: #930816) rsyslog (8.1907.0-1) unstable; urgency=medium * New upstream version 8.1907.0 * Rebase patches rsyslog (8.1905.0-4) unstable; urgency=medium * Stop installing /etc/default/rsyslog and remove it on upgrades * Upload to unstable rsyslog (8.1905.0-3) experimental; urgency=medium * Fix leading double space in rsyslog startup messages (Closes: #907755) * Update URL in logcheck rule to use https instead of http (Closes: #927771) rsyslog (8.1905.0-2) experimental; urgency=medium * Bump Build-Depends on librelp to (>= 1.4.0) for relpEngineSetTLSLibByName() * Add Build-Depends on logrotate and net-tools. Those are required by the test suite: logrotate is used in the imfile-logrotate* tests and ifconfig in sndrcv_tls_anon_ipv6. rsyslog (8.1905.0-1) experimental; urgency=medium * New upstream version 8.1905.0 rsyslog (8.1904.0-1) experimental; urgency=medium * New upstream version 8.1904.0 * Rebase patches rsyslog
[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes
@voldemark, very sorry it seems when I made comment 7 I must have missed your comment 6, so I was unclear on why this was marked as affecting Disco. I've reproduced and will queue the patch for Bionic. ** Changed in: systemd (Ubuntu Disco) Status: Incomplete => Fix Released ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Xenial) Status: Incomplete => In Progress ** Changed in: systemd (Ubuntu Bionic) Status: Incomplete => In Progress ** Description changed: + [impact] + + when a service configured to restart crashes, under certain + configurations, that service is not correctly restarted. + + [test case] + + see comment 8 + + [regression potential] + + this changes the job mode of manager-triggered restarts to 'replace' any + existing queued job(s), instead of failing if there are queued job(s). + thus any regressions would occur when a service fails, that is + configured to restart on failure. + + [scope] + + This is needed only for Xenial and Bionic. + + this is fixed with commit 1e0a54e72b73df7ee26e45e29ddda44c1dece919 which + is included already in Eoan. + + [other info] + + original description: + --- + + Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. ** Description changed: [impact] when a service configured to restart crashes, under certain configurations, that service is not correctly restarted. [test case] see comment 8 [regression potential] this changes the job mode of manager-triggered restarts to 'replace' any existing queued job(s), instead of failing if there are queued job(s). thus any regressions would occur when a service fails, that is configured to restart on failure. [scope] This is needed only for Xenial and Bionic. - this is fixed with commit 1e0a54e72b73df7ee26e45e29ddda44c1dece919 which + this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51 which is included already in Eoan. [other info] original description: --- - Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. -- 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/1839290 Title: systemd doesn't restart a service after crashes Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: Fix Released Bug description: [impact] when a service configured to restart crashes, under certain configurations, that service is not correctly restarted. [test case] see comment 8 [regression potential] this changes the job mode of manager-triggered restarts to 'replace' any existing queued job(s), instead of failing if there are queued job(s). thus any regressions would occur when a service fails, that is configured to restart on failure. [scope] This is needed only for Xenial and Bionic. this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51 which is included already in Eoan. [other info] original description: --- Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd
[Touch-packages] [Bug 1862762] Re: Merge 8.2001.0-1 from Debian
This bug was fixed in the package rsyslog - 8.2001.0-1ubuntu1 --- rsyslog (8.2001.0-1ubuntu1) focal; urgency=medium [ Christian Ehrhardt ] * Merge with Debian unstable (LP: #1862762). Remaining changes: - debian/00rsyslog.conf Install tmpfiles.d snippet to ensure that the syslog group can write into /var/log/. - debian/50-default.conf: set of default rules for syslog + debian/50-default.conf: separated default rules + d/rsyslog.install: install default rules + d/rsyslog.postrm: clear default rules on purge + d/rsyslog.postrm: remove conf file in postrm on purge. manage with ucf + d/rsyslog.postinst: Adapt script to use ucf for Ubuntu's config files + debian/control: Add Depends for ucf - debian/rsyslog.conf: + enable $RepeatedMsgReduction to avoid bloating the syslog file. + enable $KLogPermitNonKernelFacility for non-kernel klog messages + Run as rsyslog:rsyslog, set $FileOwner to syslog + Remove rules moved to 50-default.conf - Add disabled by default AppArmor profile, debian/usr.sbin.rsyslogd + d/rsyslog.install: install apparmor rule + d/rules: use dh_apparmor to install profile before rsyslog is started + d/control: suggests apparmor (>= 2.3) + d/contrl: Build-Depends on dh-apparmor + debian/rsyslog.dirs: install /etc/apparmor.d/force-complain, /etc/apparmor.d/disable and /etc/apparmor.d/local + d/usr.sbin.rsyslogd apparmor profile for rsyslogd + debian/rsyslog.preinst: disable profile on clean installs. - d/rules: Fix LDFLAGS to avoid segfault on receipt of first message - Drop mmnormalize module, which depends on liblognorm from universe. + d/rules: drop --enable-mmnormalize + d/control: drop build dependency on liblognorm-dev - run as user syslog + d/rsyslog.postinst: fix ownership of /var/spool/rsyslog. + d/rsyslog.postinst: Create syslog user and add it to adm group + d/rsyslog.postinst: Adapt privileges for /var/log + debian/control: Add Depends for adduser - debian/dmesg.service: provide /var/log/dmesg.log as non log-rotated log for boot-time kernel messages. - debian/clean: Delete some files left over by the test suite * Dropped Changes: - d/control: drop rsyslog-mongodb package from suggests [ This part was forgotten to be droped in 8.32.0-1ubuntu1 ] - d/rules: Build with --disable-silent-rules to get useful build logs. [ was a no-op as verbose is the default ] - d/rsyslog.postinst: Clean up temporary syslog.service symlink [ Formerly missing in Changelog, now gone in Debian as well ] [ Simon Deziel ] * d/usr.sbin.rsyslogd: apparmor: fix typo in rule for (LP: #1827253). rsyslog (8.2001.0-1) unstable; urgency=medium * New upstream version 8.2001.0 * Set PYTHON=/usr/bin/python3 in debian/rules * Cherry-pick upstream patches which fix a couple of imfile issues * Add missing test files rsyslog (8.1911.0-1) unstable; urgency=medium * New upstream version 8.1911.0 * Follow DEP-14 naming * Rebase patches * Bump Standards-Version to 4.4.1 rsyslog (8.1910.0-2) unstable; urgency=medium * Fix file handle leak in omfile (Closes: #935300) rsyslog (8.1910.0-1) unstable; urgency=medium * New upstream version 8.1910.0 - Support cross-platform build for mysql/mariadb (Closes: #932068) - Fix heap overflow in pmaixforwardedfrom module (CVE-2019-17041, Closes: #942067) - Fix heap overflow in pmcisconames module (CVE-2019-17042, Closes: #942065) * Use Python3 for running the test suite (Closes: #938417) * Enable imfile tests rsyslog (8.1908.0-1) unstable; urgency=medium * New upstream version 8.1908.0 rsyslog (8.1907.0-2) unstable; urgency=medium * Enable OpenSSL network stream driver. Split the driver into a separate package named rsyslog-openssl and update the Suggests accordingly to make it the preferred TLS driver. (Closes: #930816) rsyslog (8.1907.0-1) unstable; urgency=medium * New upstream version 8.1907.0 * Rebase patches rsyslog (8.1905.0-4) unstable; urgency=medium * Stop installing /etc/default/rsyslog and remove it on upgrades * Upload to unstable rsyslog (8.1905.0-3) experimental; urgency=medium * Fix leading double space in rsyslog startup messages (Closes: #907755) * Update URL in logcheck rule to use https instead of http (Closes: #927771) rsyslog (8.1905.0-2) experimental; urgency=medium * Bump Build-Depends on librelp to (>= 1.4.0) for relpEngineSetTLSLibByName() * Add Build-Depends on logrotate and net-tools. Those are required by the test suite: logrotate is used in the imfile-logrotate* tests and ifconfig in sndrcv_tls_anon_ipv6. rsyslog (8.1905.0-1) experimental; urgency=medium * New upstream version 8.1905.0 rsyslog (8.1904.0-1) experimental; urgency=medium * New upstream version 8.1904.0 * Rebase patches rsyslog
[Touch-packages] [Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)
For others with similar problems, I'm keeping my findings up to date here: https://www.tartley.com/dina-as-otf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1861340 Title: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development) Status in Pango: Fix Released Status in pango1.0 package in Ubuntu: Triaged Bug description: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here: http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7 I have always installed it using a script: # install dina sudo mkdir -p /usr/share/fonts/Dina cd /usr/share/fonts/Dina sudo unzip ~/Downloads/Dina.zip # enable bitmap fonts sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf # rebuild the cache fc-cache -f -v # Set as default mono font gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8" This has always worked in the past, through many versions of Ubuntu, including 19.10. I installed Focal today, using `sudo do-release-upgrade -d`. Now the above script does not make Dina visible in font selectors such as that produced by the Tweaks / Fonts / [Monospace Text] button. Terminals that were previously configured to use that font now display the "box of hex digits" characters (what are they called?) gnome-font-viewer does not list any of the installed bitmap fonts. While trying to find a fix, I tried a few changes to the above script, which did not help: * Unzip to "$HOME/.fonts" instead * Trying other symlinks in the fonts config.d: ( cd /etc/fonts/conf.d sudo rm -f 70-no-bitmaps.conf sudo ln -sf ../conf.avail/70-yes-bitmaps.conf ) (tried with both 'yes-bitmaps' and 'force-bitmaps') * fc-cache -r # "really" force cache re-creation To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1861340/+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 1862846] Re: Crash and failure installing focal
** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/379024 -- 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/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Triaged Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Triaged Status in util-linux source package in Focal: New Status in util-linux package in Debian: Unknown Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+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 1862987] Re: qtbase5-private-dev does not install private headers for QtWayland
Upon further inspection I think qtwayland-opensource-src is the package this bug should be filed against. ** Package changed: qtbase-opensource-src (Ubuntu) => qtwayland- opensource-src (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1862987 Title: qtbase5-private-dev does not install private headers for QtWayland Status in qtwayland-opensource-src package in Ubuntu: New Bug description: Trying to build QGNOMEPlatform (https://github.com/FedoraQt/QGnomePlatform/releases) fails with the following error message: Project ERROR: Unknown module(s) in QT: waylandclient-private Running `dpkg -L qtbase5-private-dev | grep -i wayland` shows nothing, running `apt-file search /usr/include/x86_64-linux- gnu/qt5/QtWaylandClient/5.12.5/QtWaylandClient/private` also returns nothing. I also tried installing qtbase5-private-dev in a Debian container and they have the same issue so it may be worth notifying them if you fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwayland-opensource-src/+bug/1862987/+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 718693] Re: Can't type EURO symbol with AltGr+E using main lithuanian (lt) keymap
Current situation about this issue is described and fixed in bug #1863001 ** Changed in: baltix Status: New => Triaged ** Changed in: baltix Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/718693 Title: Can't type EURO symbol with AltGr+E using main lithuanian (lt) keymap Status in xkeyboard-config package in Ubuntu: New Status in Baltix: In Progress Bug description: Binary package hint: xkeyboard-config Main lithuanian layout has no EURO symbol. Main lithuanian layout should have EURO symbol on key "e" (alt gr + e), like other layouts "Lithuanian US", "Lithuanian IBM", "Lihuanian Standard" has it on key "e". Windows OS it is also on key "e". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/718693/+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 1861472] Re: upgrade from fresh bionic to focal needlessly prompts user
** Bug watch added: Debian Bug tracker #951220 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951220 ** Also affects: openssh (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951220 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1861472 Title: upgrade from fresh bionic to focal needlessly prompts user Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: Unknown Bug description: Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts for how to handle a change to /etc/ssh/sshd_config To reproduce the issue: lxc launch ubuntu:18.04 u18 lxc exec u18 -- bash # within container do-release-upgrade -d # select restart services when prompted Eventually you'll be prompted to accept changes to /etc/ssh/sshd_config or not because of "local changes". Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.1p1-5 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 03:37:55 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1861472/+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 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
** Summary changed: - Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration + Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity -- 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: New 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 will attach 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 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration
When user chooses Lithuanian keyboard layout then XKB variables in /etc/default/keyboard should set to: XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" I'm attaching screenshot of English US (intl with altGR) keyboard layoyut, this layout is most usefull for Lithuanians, because it contains Euro (€) and other symbols, often used in Lithuania. ** Attachment added: "Screenshot of English US (intl with altGR) keyboard layoyut" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+attachment/5327742/+files/US%28altGR%20intl%29%20keyboard%20layoyut.png -- 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: New 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 will attach 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 1863001] [NEW] Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration
Public bug reported: 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 will attach a patch to debian/keyboard-configuration.config file which fixes this issue ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- 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 Status in console-setup package in Ubuntu: New 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 will attach 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 1860762] Re: Upgrade with zfs-on-root failures
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- 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/1860762 Title: Upgrade with zfs-on-root failures Status in initramfs-tools package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I followed rlaager's howto for installing Ubuntu 18.04 LTS with ZFS root (but used disco). I've also set up sanoid to perform periodic snapshots of bpool (which stores /boot). The upgrade from disco to eoan didn't go well: [.. trimmed to fit in the comment box; more context in attachment ..] /ubuntu@autosnap_2020-01-24_04:00:05_frequently Found initrd image: initrd.img-5.3.0-29-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:00:05_frequently Found linux image: vmlinuz-5.0.0-39-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently Found initrd image: initrd.img-5.0.0-39-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently Found linux image: vmlinuz-5.0.0-40-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently Found initrd image: initrd.img-5.0.0-40-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently Found linux image: vmlinuz-5.3.0-29-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently Found initrd image: initrd.img-5.3.0-29-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently Adding boot menu entry for EFI firmware configuration done Processing triggers for dbus (1.12.14-1ubuntu2) ... Processing triggers for initramfs-tools (0.133ubuntu10) ... update-initramfs: Generating /boot/initrd.img-5.3.0-29-generic cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu cryptsetup: WARNING: Couldn't determine root device Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.3.0-29-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for shim-signed (1.39+15+1533136590.3beb971-0ubuntu1) ... Nothing to do. Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg-1build1) ... Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Setting up initramfs-tools (0.133ubuntu10) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.133ubuntu10) ... update-initramfs: Generating /boot/initrd.img-5.3.0-29-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/initramfs-tools.0.crash' cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu cryptsetup: WARNING: Couldn't determine root device Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.3.0-29-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.0.0-40.44-generic 5.0.21 Uname: Linux 5.0.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Fri Jan 24 06:02:32 2020 PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2020-01-24 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage
[Touch-packages] [Bug 1860762] Re: Upgrade with zfs-on-root failures
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1860762 Title: Upgrade with zfs-on-root failures Status in initramfs-tools package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I followed rlaager's howto for installing Ubuntu 18.04 LTS with ZFS root (but used disco). I've also set up sanoid to perform periodic snapshots of bpool (which stores /boot). The upgrade from disco to eoan didn't go well: [.. trimmed to fit in the comment box; more context in attachment ..] /ubuntu@autosnap_2020-01-24_04:00:05_frequently Found initrd image: initrd.img-5.3.0-29-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:00:05_frequently Found linux image: vmlinuz-5.0.0-39-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently Found initrd image: initrd.img-5.0.0-39-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently Found linux image: vmlinuz-5.0.0-40-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently Found initrd image: initrd.img-5.0.0-40-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently Found linux image: vmlinuz-5.3.0-29-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently Found initrd image: initrd.img-5.3.0-29-generic in rpool/ROOT/ubuntu@autosnap_2020-01-24_04:15:05_frequently Adding boot menu entry for EFI firmware configuration done Processing triggers for dbus (1.12.14-1ubuntu2) ... Processing triggers for initramfs-tools (0.133ubuntu10) ... update-initramfs: Generating /boot/initrd.img-5.3.0-29-generic cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu cryptsetup: WARNING: Couldn't determine root device Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.3.0-29-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for shim-signed (1.39+15+1533136590.3beb971-0ubuntu1) ... Nothing to do. Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg-1build1) ... Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Setting up initramfs-tools (0.133ubuntu10) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.133ubuntu10) ... update-initramfs: Generating /boot/initrd.img-5.3.0-29-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/initramfs-tools.0.crash' cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu cryptsetup: WARNING: Couldn't determine root device Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.3.0-29-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.0.0-40.44-generic 5.0.21 Uname: Linux 5.0.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Fri Jan 24 06:02:32 2020 PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2020-01-24 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Bug watch added: Debian Bug tracker #951217 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951217 ** Also affects: util-linux (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951217 Importance: Unknown Status: Unknown -- 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/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Triaged Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Triaged Status in util-linux source package in Focal: New Status in util-linux package in Debian: Unknown Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+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 1862987] [NEW] qtbase5-private-dev does not install private headers for QtWayland
Public bug reported: Trying to build QGNOMEPlatform (https://github.com/FedoraQt/QGnomePlatform/releases) fails with the following error message: Project ERROR: Unknown module(s) in QT: waylandclient-private Running `dpkg -L qtbase5-private-dev | grep -i wayland` shows nothing, running `apt-file search /usr/include/x86_64-linux- gnu/qt5/QtWaylandClient/5.12.5/QtWaylandClient/private` also returns nothing. I also tried installing qtbase5-private-dev in a Debian container and they have the same issue so it may be worth notifying them if you fix this. ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1862987 Title: qtbase5-private-dev does not install private headers for QtWayland Status in qtbase-opensource-src package in Ubuntu: New Bug description: Trying to build QGNOMEPlatform (https://github.com/FedoraQt/QGnomePlatform/releases) fails with the following error message: Project ERROR: Unknown module(s) in QT: waylandclient-private Running `dpkg -L qtbase5-private-dev | grep -i wayland` shows nothing, running `apt-file search /usr/include/x86_64-linux- gnu/qt5/QtWaylandClient/5.12.5/QtWaylandClient/private` also returns nothing. I also tried installing qtbase5-private-dev in a Debian container and they have the same issue so it may be worth notifying them if you fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1862987/+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 1862928] Re: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)
Thanks Steve!! Package is back to archive, moving on with what needed this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1862928 Title: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh) Status in python-crypto package in Ubuntu: Invalid Bug description: If you try: (c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be installed Depends: libgmp10:amd64 but it is not going to be installed python3-samba : Depends: python3-crypto but it is not installable You won't be able to install python3-crypto. With a simple rebuild problem goes away. NOTE: This is needed to fix: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316 (Where I'm getting back winbind to samba on i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928/+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 1862928] Re: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)
Does not need a rebuild (which wouldn't have worked anyway), it only needed the i386 binaries resuscitated which is now done. ** Changed in: python-crypto (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1862928 Title: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh) Status in python-crypto package in Ubuntu: Invalid Bug description: If you try: (c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be installed Depends: libgmp10:amd64 but it is not going to be installed python3-samba : Depends: python3-crypto but it is not installable You won't be able to install python3-crypto. With a simple rebuild problem goes away. NOTE: This is needed to fix: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316 (Where I'm getting back winbind to samba on i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928/+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 1862770] Re: MySQL autopkgtest regressed in Focal release pocket
*** This bug is a duplicate of bug 1862364 *** https://bugs.launchpad.net/bugs/1862364 ** This bug has been marked a duplicate of bug 1862364 mysql-8.0 FTBFS (focal) because of hardcoded date in test -- 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/1862770 Title: MySQL autopkgtest regressed in Focal release pocket Status in mysql-8.0 package in Ubuntu: New Status in shadow package in Ubuntu: New Bug description: http://autopkgtest.ubuntu.com/packages/m/mysql-8.0/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/m/mysql-8.0/20200211_122839_60bab@/log.gz ... 63%] main.events_1 [ fail ] Test ended at 2020-02-11 12:06:00 CURRENT_TEST: main.events_1 mysqltest: At line 69: Query 'ALTER EVENT event_starts_test ON SCHEDULE AT '2020-02-02 20:00:02'' failed. ERROR 1589 (HY000): Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future. The result from queries just before the failure was: drop event if exists event1; Warnings: Note 1305Event event1 does not exist create event event1 on schedule every 15 minute starts now() ends date_add(now(), interval 5 hour) DO begin end; alter event event1 rename to event2 enable; alter event event2 disable; alter event event2 enable; alter event event2 on completion not preserve; alter event event2 on schedule every 1 year on completion preserve rename to event3 comment "new comment" do begin select 1; end__ alter event event3 rename to event2; drop event event2; create event event2 on schedule every 2 second starts now() ends date_add(now(), interval 5 hour) comment "some" DO begin end; drop event event2; CREATE EVENT event_starts_test ON SCHEDULE EVERY 10 SECOND COMMENT "" DO SELECT 1; SELECT interval_field, interval_value, event_definition FROM information_schema.events WHERE event_name='event_starts_test'; INTERVAL_FIELDINTERVAL_VALUE EVENT_DEFINITION SECOND10 SELECT 1 SELECT execute_at IS NULL, starts IS NULL, ends IS NULL, event_comment FROM information_schema.events WHERE event_schema='events_test' AND event_name='event_starts_test'; execute_at IS NULLstarts IS NULL ends IS NULLEVENT_COMMENT 1 0 1 safe_process[25029]: Child process: 25030, exit: 1 - the logfile can be found in '/tmp/tmp.YL1y5O4jCj/var/log/main.events_1/events_1.log' ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862770/+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 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines
** Description changed: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. + + Test packages for the supported releases are available from the + following PPA: + + https://launchpad.net/~waveform/+archive/ubuntu/python-apt + + Built from the source which can be found in the following branches: + + https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git + /python-apt/+ref/sru-dupe-ppa-xenial + + https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git + /python-apt/+ref/sru-dupe-ppa-bionic + + https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git + /python-apt/+ref/sru-dupe-ppa-eoan Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented "deb-src" line * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated * sudo add-apt-repository ppa:waveform/python-apt * sudo apt upgrade # update python-apt to fixed version * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note there has been no further duplication of the commented "deb-src" line Regression Potential Minimal; test cases have been added to cover the duplication case, and to cover the enabling of sources (which was not covered by existing tests, but was part of the code altered to fix the duplication case), and insertion of sources at a position (again, not covered by existing tests but modified as part of the fix). The test case has been used successfully on all targeted releases (xenial, bionic, and eoan). Original Description Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1311056 Title: [SRU] apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: New Status in python-apt source package in Bionic: New Status in python-apt source package in Eoan: New Bug description: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. Test packages for the supported releases are available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/python-apt Built from the source which can be found in the following branches: https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-xenial https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-bionic https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-eoan Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented
[Touch-packages] [Bug 1332114] Re: Please update mawk to latest upstream release
Version 1.3.4.20200120-1 was updated in Debian and migrated to testing on January 31th. Please sync that version to Focal, the current version in the archive is from 2012!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mawk in Ubuntu. https://bugs.launchpad.net/bugs/1332114 Title: Please update mawk to latest upstream release Status in mawk package in Ubuntu: Triaged Status in mawk package in Debian: Fix Released Bug description: mawk in Ubuntu is 18 years old and very buggy (see https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=mawk and https://bugs.launchpad.net/ubuntu/+source/mawk , also bugs in other products, like bug #1331381) :( Almost all bugs, reported in Ubuntu and Debian are fixed in 1.3.4- upstream releases, see http://invisible-island.net/mawk/CHANGES.html Please update mawk to latest upstream release - all the other major distributions (Fedora/Redhat, Suse, even FreeBSD) have switched to mawk 1.3.4-2014. Five years since the bug asking to upload new mawk in Debian didn't change anything, so, I'm reporting bug in Ubuntu - sticking to 1.3.3 is now causing headeach to lots of people rather than saving from regressions, see for example bug #1005077 :( Please, update mawk package before major Ubuntu 16.04 LTS release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1332114/+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 1841654] Re: Consider replacing mawk with gawk in main
With mawk 1.3.4.20200120-1 being uploaded to Debian testing now I
suggest to mark this bug here as invalid and just sync the new mawk
version to Focal. There is a separate bug for just updating mawk
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1332114 Let's follow
up there...
** Changed in: mawk (Ubuntu)
Status: Confirmed => Opinion
** Changed in: ubuntu-mate-meta (Ubuntu)
Status: Confirmed => Opinion
** Changed in: ubuntu-meta (Ubuntu)
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/1841654
Title:
Consider replacing mawk with gawk in main
Status in mawk package in Ubuntu:
Opinion
Status in ubuntu-mate-meta package in Ubuntu:
Opinion
Status in ubuntu-meta package in Ubuntu:
Opinion
Bug description:
For POSIX compatibility reasons Ubuntu ships with mawk ("Mike's awk" =
mawk) in main. There is an awk-symlink to mawk, thus mawk is the
official awk implementation in Ubuntu.
== Reasons against keeping mawk ==
*The mawk package is synced from debian and it is heavily
undermaintained: Debian (and thus Ubuntu) still ships version
1.3.3-17, the same version at least since oldoldstable:
https://packages.debian.org/search?searchon=names=mawk
*maintainer Thomas E. Dickey (https://invisible-island.net/mawk/)
called officially out that Debian "neglected" mawk in 2014 ("As noted,
mawk has been neglected by some packagers (see for example this
http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=mawk)". And
Debian (and Ubuntu) still ship the same version five years later
*Most other distributions ship mawk at least in its last official
incarnation 1.3.4 in their repositories. Dickey lists AIX, Fedora,
FinkPorts (Mac OS X), FreeBSD port, Gentoo, HPUX, MacPorts (Mac OS X),
NetBSD pkgsrc/lang, OpenCSW (Solaris). That version is from 2014 but
updated snapshots are released in regular intervals. The current
snapshot is from February 2019: https://github.com/ThomasDickey/mawk-
snapshots/blob/ab13a164013940e90c0b1ad36a039feae06a0b65/CHANGES
*A planned rewrite mawk2 was planned by original author Mike Brennan
in 2016 but obviously came to nothing:
https://github.com/ploxiln/mawk-2/commits/master
*Thus mawk sits in Ubuntu main in a version published upstream in 2009
and celebrates its 10th anniversary of negligence. In a state that
Debian was called out for 5 years ago.
*This year it is 10 years unmaintained and largely untouched. At the
end of the next LTS-support-cycle we can celebrate 15 years of not
supporting it.
*awk is included in Linux for POSIX standard compliance. Mawk is known
to be fast and small but it is the implementation that is farthest
from being POSIX compliant, missing things like named character
classes like [[:space:]] within its EREs.
== Reasons for gawk as a replacement ==
*It is the official GNU awk implementation and known to work well with
the rest of the GNU userland.
*It is actively maintained with the last version 5.01 shipping in
June, 2019 (even if Ubuntu will obviously still ship 4.2 for Eoan).
*It is mostly compliant with the POSIX standard.
*Most other distributions ship it as the standard POSIX
implementation, with a awk symlink. So it had security reviews already
by Red Hat and others.
== Possible problems with switching to gawk in time for Ubuntu 20.4 ==
- It might need to be MIRed by the Ubuntu security team and a review
might take some time. So I filed this bug early with Eoan not yet out
of the door.
- It is much larger than mawk, the Ubuntu package is 1600 kB in size,
while mawk is only about 190KB. Thus some might want to split out some
basic functionality to save size. Like what is vim-tiny to vim. To
start gawk in --traditional or --posix mode and disable the extensions
at compile time might be a good start to reduce the size. See:
https://www.gnu.org/software/gawk/manual/html_node/Additional-
Configuration-Options.html#Additional-Configuration-Options
=
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: mawk 1.3.3-17ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 27 20:12:11 2019
Dependencies:
gcc-9-base 9.1.0-2ubuntu2~19.04
libc6 2.29-0ubuntu2
libgcc1 1:9.1.0-2ubuntu2~19.04
libidn2-0 2.0.5-1
libunistring2 0.9.10-1ubuntu2
InstallationDate: Installed on 2018-02-23 (550 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
ProcEnviron:
LANGUAGE=de_AT:de
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_AT.UTF-8
SHELL=/bin/bash
SourcePackage: mawk
[Touch-packages] [Bug 1732962] Re: apport uses sys.argv instead of named arguments
** Changed in: apport (Ubuntu Trusty)
Status: New => Fix Committed
** Changed in: apport (Ubuntu Trusty)
Status: Fix Committed => Won't Fix
--
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/1732962
Title:
apport uses sys.argv instead of named arguments
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Trusty:
Won't Fix
Status in apport source package in Xenial:
New
Status in apport source package in Bionic:
New
Status in apport source package in Cosmic:
Won't Fix
Status in apport source package in Disco:
Fix Released
Bug description:
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with
some security updates where we were trying to support a new version of
apport on a host system and one inside a container. Here's something
of an example:
347 # Normal startup
348 if len(sys.argv) not in (5, 6):
349 try:
350 print('Usage: %s [global pid]' % sys.argv[0])
351 print('The core dump is read from stdin.')
We could not maintain backwards compatibility because "global pid" is
an optional argument and "dump mode" was a new argument. So if there
were five arguments its possible the last one was "dump mode" (no
global pid) or "global pid" (no support for dump mode).
Its possible to use strings in /proc/sys/kernel/core_pattern so we
could use those and have apport accept named arguments e.g:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d
--global-pid=%P
['/home/bdmurray/source-trees/apport/artful/data/apport', '--
pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-
pid=5870']
Tyler said "that's probably a nice cleanup to make no matter what
because the magic arg ordering is dangerous".
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1732962/+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 1862969] [NEW] On SystemReboot wifi failed to connect on tplink wifi adapter
Public bug reported: I'm using Ubuntu 19.10 64bit for my PC. For network/wifi I'm using TP- Link wifi adapter. My network works only when I do a fresh start (That is completely shutdown and start). But network connection fails to connect to my wifi on REBOOT(on system software updates , etc..). After reboot: 1. I can see my mobile device(wifi service providing) name in the list at WIFI SETTINGS -> VISIBLE NETWORKS. 2. BUT IT FAILS TO CONNECT. It tries many times and finally says , CANT CONNECT. I searched GOOGLE, UBUNTU FORMS, but I failed to find the solution. As per now solution: After reboot , I have to shutdown pc again and do a boot. To make wifi connect. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1862969 Title: On SystemReboot wifi failed to connect on tplink wifi adapter Status in network-manager package in Ubuntu: New Bug description: I'm using Ubuntu 19.10 64bit for my PC. For network/wifi I'm using TP- Link wifi adapter. My network works only when I do a fresh start (That is completely shutdown and start). But network connection fails to connect to my wifi on REBOOT(on system software updates , etc..). After reboot: 1. I can see my mobile device(wifi service providing) name in the list at WIFI SETTINGS -> VISIBLE NETWORKS. 2. BUT IT FAILS TO CONNECT. It tries many times and finally says , CANT CONNECT. I searched GOOGLE, UBUNTU FORMS, but I failed to find the solution. As per now solution: After reboot , I have to shutdown pc again and do a boot. To make wifi connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1862969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 645404] Re: Support Private PPAs
To be usable under sudo, the changes for this also require bug 1862948 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/645404 Title: Support Private PPAs Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: In Progress Status in software-properties source package in Cosmic: In Progress Status in software-properties source package in Disco: In Progress Status in software-properties source package in Eoan: In Progress Bug description: Software properties add-apt-repository currently does not support adding private PPAs. software-properties should connect to the API and observe that it gets permission denied trying to read the ppa. Then it can reconnect to the API asking for authentication, which will open a browser window where you can do the openid ritual. Then using that token it ought to be possible for it to get the password etc. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
This look like a similar issue: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 A test package (including the above fix) is available on my PPA: sudo add-apt-repository ppa:slashd/lp1794478 sudo apt-get update Please let me know the outcome. - Eric ** Bug watch added: Red Hat Bugzilla #1575944 https://bugzilla.redhat.com/show_bug.cgi?id=1575944 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+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 1862846] Re: Crash and failure installing focal
@Alberto > I thought the installer would work similarly to what the desktop installer > does with btrfs, where it creates subvolumes for / and /home in the root > partition (as @ and @home). > > On my desktop, when I upgrade I just move @ out of the way (by renaming it) > and the installer creates a new one. > This is kinda nice as you can easily keep/revert to the old rootfs by > just changing which subvol is mounted at boot. Subiquity/curtin does not have support for btrfs subvolumes. -- 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/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Triaged Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Triaged Status in util-linux source package in Focal: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+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 1862846] Re: Crash and failure installing focal
@Lee Thanks for tracking down the util-linux bug. Since this is broken in 2.34 (eoan/focal); I'm thinking we should use sysfs to find the parent via device name walking; Given a kname (nvme0n1p1) of the target partition # look up sysfs path from kname % realpath /sys/class/block/nvme0n1p1 /sys/devices/pci:00/:00:02.0/:05:00.0/nvme/nvme0/nvme0n1/nvme0n1p1 # check if it's a partition % ls -al /sys/devices/pci:00/:00:02.0/:05:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/partition -r--r--r-- 1 root root 4096 Feb 12 08:08 /sys/devices/pci:00/:00:02.0/:05:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/partition # extract parent device path % dirname /sys/devices/pci:00/:00:02.0/:05:00.0/nvme/nvme0/nvme0n1/nvme0n1p1 /sys/devices/pci:00/:00:02.0/:05:00.0/nvme/nvme0/nvme0n1 # extract parent device major/minor % cat /sys/devices/pci:00/:00:02.0/:05:00.0/nvme/nvme0/nvme0n1/dev 259:0 # udev symlinks/dev/block/$MAJOR:$MINOR % ls -al /dev/block/259:0 lrwxrwxrwx 1 root root 10 Jan 18 00:16 /dev/block/259:0 -> ../nvme0n1 % realpath /dev/block/259:0 /dev/nvme0n1 -- 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/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Triaged Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Triaged Status in util-linux source package in Focal: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+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 1862846] Re: Crash and failure installing focal
** Also affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-ff-incoming ** Also affects: util-linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Focal) Importance: High Status: Triaged ** Also affects: util-linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu Eoan) 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/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Triaged Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Triaged Status in util-linux source package in Focal: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+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 1862949] [NEW] vim-runtime does not also install vim
Public bug reported: Installing vim-runtime for the vimtutor does not also install vim. Running vimtutor then opens vi and presents the user with the default empty page with no knowledge of how to exit vi. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: vim-runtime 2:8.1.0875-5ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 13:51:54 2020 InstallationDate: Installed on 2020-01-24 (19 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim (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 vim in Ubuntu. https://bugs.launchpad.net/bugs/1862949 Title: vim-runtime does not also install vim Status in vim package in Ubuntu: New Bug description: Installing vim-runtime for the vimtutor does not also install vim. Running vimtutor then opens vi and presents the user with the default empty page with no knowledge of how to exit vi. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: vim-runtime 2:8.1.0875-5ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 13:51:54 2020 InstallationDate: Installed on 2020-01-24 (19 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1862949/+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 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
Terrence Houlahan's fix also works for me on 18.04 Many thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq package in Debian: New Bug description: [Impact] dnsmasq will fail to respond on network devices that weren't up when its service started, thus not binding as expected. [Test Case] TBD [Regression Potential] The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] Straightforward packaging fix to the service to make it delay startup until after the network is online. https://bugs.debian.org/cgi- bin/bugreport.cgi?att=1;bug=774970;filename=774970-network- online.debdiff;msg=22 [Discussion] [Original Report] My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+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 1862928] Re: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)
09:43 you see that python3-crypto has per-arch deb files 09:43 I added a comment in the case and subscribed steve 09:43 while your conter-xample of ansi just has one called ..._all.deb 09:43 — rafaeldtinoco checks 09:43 AFAICS python3-crypto contains no arch dependent files 09:44 so it could be Architecture:all, rebuilt and then it should work 09:44 but as I said this is always confusing having an expert like vorlon comment on it sounds the right path forward before we'd do anything wrong 09:46 cpaelzer: dh $@ --with=python2,python3 --buildsystem=pybuild 09:46 ? 09:46 and I could remove python2 from rules also 09:46 together with the rebuild 09:47 and change Architecture: all 09:47 sure, but I thought we only remove those python2 that are blocking anything 09:47 we only want to demote to universe or did it change and we want to drop things entriely? 09:48 anyway - agreed, it feels almost always right to drop py2 - just sometimes you might cause more work than you solve 09:48 think of other dependencies on that and the chain that you need to resolve then for example 09:52 yep, i think that is the last one 09:52 as I rebuilt it locally and was able to re-enable all needed samba pkgs 09:53 your rebuilt gave you an :i386 package 09:53 yep 09:53 I'd expect that an :all package is even more generic 09:53 which the :all might do 09:53 I see no need this needs to be per-arch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1862928 Title: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh) Status in python-crypto package in Ubuntu: In Progress Bug description: If you try: (c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be installed Depends: libgmp10:amd64 but it is not going to be installed python3-samba : Depends: python3-crypto but it is not installable You won't be able to install python3-crypto. With a simple rebuild problem goes away. NOTE: This is needed to fix: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316 (Where I'm getting back winbind to samba on i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928/+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 1025418] Re: Using ProxyCommand w/a non-existant host results in infinite spawns.
> It should, therefore, be pushed upstream. Sure. Upstream can make a final determination, and Ubuntu will inherit their decision. Thank you for doing that. > ...it would be welcome if Ubuntu were to request a fix as well. Ubuntu is a community project and that community includes you. If you've made a request upstream, I don't think it's appropriate for anyone else to be joining in unless they have new and useful information to add. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1025418 Title: Using ProxyCommand w/a non-existant host results in infinite spawns. Status in openssh package in Ubuntu: Invalid Bug description: Version: OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012 Package: openssh-client Today we discovered a possible bug in the OpenSSH-Client package (openssh) that happens when you enable ProxyCommand with a non- existant hostname. This bug is easily replicated with the default example in /etc/ssh/ssh_config. If one uncomments that line and then for example tries to push via Git SSH you end up with SSH spawning over and over and over again as seein the attached screenshot. I have flagged this as a security bug (but ultimately it's up to ya'll if it is) because any user can do this and take down any server quite easily by adding add a bad ProxyCommand to their ~/.ssh/config. I was able to take out one of my personal servers (which happens to be a pretty big server) within a few minutes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1025418/+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 1862928] Re: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)
FYI The ones working seem to be those building as: Architecture: all While the ones you report as failing are: Architecture: any -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1862928 Title: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh) Status in python-crypto package in Ubuntu: In Progress Bug description: If you try: (c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be installed Depends: libgmp10:amd64 but it is not going to be installed python3-samba : Depends: python3-crypto but it is not installable You won't be able to install python3-crypto. With a simple rebuild problem goes away. NOTE: This is needed to fix: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316 (Where I'm getting back winbind to samba on i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928/+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 1862928] Re: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)
Steve, Looks like python3-crypto package is not in the i386 archive. Judging by: https://launchpad.net/ubuntu/+source/python-crypto https://launchpad.net/ubuntu/+source/python-crypto/+publishinghistory https://launchpad.net/ubuntu/+source/python-crypto/2.6.1-11ubuntu2 https://launchpad.net/ubuntu/+source/python-crypto/2.6.1-11ubuntu2/+build/17949247 And based on other similar tests (python3-pam also failing in i386 only environment, but some other python3-XXX packages having i386 binary packages available) I would say we need the i386 binary package python3-crypto back in archive to satisfy the needs for: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316 (MERGE: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/samba/+git/samba/+merge/378664) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1862928 Title: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh) Status in python-crypto package in Ubuntu: In Progress Bug description: If you try: (c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be installed Depends: libgmp10:amd64 but it is not going to be installed python3-samba : Depends: python3-crypto but it is not installable You won't be able to install python3-crypto. With a simple rebuild problem goes away. NOTE: This is needed to fix: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316 (Where I'm getting back winbind to samba on i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928/+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 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Same here on Linux CH-W-7269416 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Device 04:5D:4B:99:46:9C (public) Name: WH-1000XM2 Alias: WH-1000XM2 Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (-deca-fade-deca-deafdecacaff) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Vendor specific (7b265b0e-2232-4d45-bef4-bb8ae62f813d) UUID: Vendor specific (96cc203e-5068-46ad-b32d-e316f5e069ba) UUID: Vendor specific (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b) Modalias: usb:v054Cp0C67d0105 -- 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/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 1025418] Re: Using ProxyCommand w/a non-existant host results in infinite spawns.
I'm sorry to revive this old topic. I'm astonished that after 8 years, it hasn't been fixed. I would like to push this up once more. The reason is any user interaction that is not by designed suppose to happen, should be considered a user experience bug and fixed. Crafting a fork bomb by design is out of the scope of this context. One is a malicious conscious creation of a piece of code, while a user misconfiguration is not. It is easily preventable by creating a hardcoded automatic implicit exclusion of the gateway. It is not normal that a user could create a recursive infinite loop with a piece of configuration like this. We are responsible to protect the user in such a case. The issue is not limited to Ubuntu, but to all systems that embedded OpenSSH. It should, therefore, be pushed upstream. I have sent an email to the OpenSSH developer mailing list and it would be welcome if Ubuntu were to request a fix as well. I will do the same request at RedHat. Thank you for your cooperation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1025418 Title: Using ProxyCommand w/a non-existant host results in infinite spawns. Status in openssh package in Ubuntu: Invalid Bug description: Version: OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012 Package: openssh-client Today we discovered a possible bug in the OpenSSH-Client package (openssh) that happens when you enable ProxyCommand with a non- existant hostname. This bug is easily replicated with the default example in /etc/ssh/ssh_config. If one uncomments that line and then for example tries to push via Git SSH you end up with SSH spawning over and over and over again as seein the attached screenshot. I have flagged this as a security bug (but ultimately it's up to ya'll if it is) because any user can do this and take down any server quite easily by adding add a bad ProxyCommand to their ~/.ssh/config. I was able to take out one of my personal servers (which happens to be a pretty big server) within a few minutes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1025418/+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 1862928] Re: python-crypto needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)
Yep, I had those as well, thought it was my dev environmnet. But, if you say yours install fine there is no need for a rebuild.. weird.. I'll re- check here, thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1862928 Title: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh) Status in python-crypto package in Ubuntu: In Progress Bug description: If you try: (c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be installed Depends: libgmp10:amd64 but it is not going to be installed python3-samba : Depends: python3-crypto but it is not installable You won't be able to install python3-crypto. With a simple rebuild problem goes away. NOTE: This is needed to fix: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316 (Where I'm getting back winbind to samba on i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928/+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 1862928] Re: python-crypto needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)
I think this relates to having i386 in amd64 installed OSes only currently. Since I'm using a i386 only container, it can't figure out the correct python dependency (asking for amd64). If I build python3-crypto in an i386 container dependencies are correctly figured out. ** Summary changed: - python-crypto needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh) + python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1862928 Title: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh) Status in python-crypto package in Ubuntu: In Progress Bug description: If you try: (c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be installed Depends: libgmp10:amd64 but it is not going to be installed python3-samba : Depends: python3-crypto but it is not installable You won't be able to install python3-crypto. With a simple rebuild problem goes away. NOTE: This is needed to fix: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316 (Where I'm getting back winbind to samba on i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928/+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 1862928] Re: python-crypto needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)
Ah okay, perhaps your environment is amd64 ? I'm testing this in an i386 environmnet (LXD container) only. Still getting: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1862928 Title: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh) Status in python-crypto package in Ubuntu: In Progress Bug description: If you try: (c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be installed Depends: libgmp10:amd64 but it is not going to be installed python3-samba : Depends: python3-crypto but it is not installable You won't be able to install python3-crypto. With a simple rebuild problem goes away. NOTE: This is needed to fix: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316 (Where I'm getting back winbind to samba on i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928/+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 1862264] Re: Browsing smb share is painfully slow
Looks like gio is part of glib, not gvfs, so changed the package accordingly. Also made clear in the title that gio vs mount is part of the issue. ** Package changed: gvfs (Ubuntu) => glib2.0 (Ubuntu) ** Summary changed: - Browsing smb share is painfully slow + Browsing smb share is painfully slow when mounted via "gio" (compared with "mount") -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1862264 Title: Browsing smb share is painfully slow when mounted via "gio" (compared with "mount") Status in glib2.0 package in Ubuntu: New Bug description: Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020). TEST #1: To establish a baseline/expected behavior, we first mount an SMB share via mount.cifs and time an ls command: $ sudo mount -t cifs -o username=pablo //myserver.example.com/share ~/mnt/share $ cd ~/mnt/share/some/dir $ time ls ... approx 320 files ... real 0m1,080s user 0m0,008s sys 0m0,005s $ sudo umount ~/mnt/share TEST #2 Now we do the same via gio mount: $ gio mount smb://myserver.example.com/share cd /run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir $ time ls ... same 320 files ... real 0m28,999s user 0m0,013s sys 0m0,032s Enumeration of files is about 29 times slower when mounted via gio mount than via mount -t cifs. TEST #3 Now for the real weird: while using the gio-mounted folder, we now time ls IN COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...): $ time ls | wc 321 3239804 real 0m0,546s user 0m0,006s sys 0m0,004s Note that this is almost TWICE AS FAST than the "fast" mount of test #1 and about 53 times faster than "slow" test #2 ! The expectation is that Tests 1 and 2 should have similar timings, not differing by a factor of 30 or so. More disturbing, there is no good reason why tests 2 and 3 differ by an even bigger factor of 53: They use the same underlying infrastructure which test 3 proves is adequately fast. And yet, we get this slow down in test 2. As a final note, these benchmarks are a distilled version of the original real-life motivating scenario where a Java-based program would simply take tens of minutes to display the same list of 320 files when mounted via gio mount and a second or so when mounted via mount -t cifs. The same timing difference is of course visible in any file manager. Hope this helps PS: several old/ancient bug reports exist for a similar issue and I deliberately copied the title from one of them (#259771) PS2: may or may not be relevant: The remote server is a VM running Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu stock SSTP). PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM) $ gio mount smb://nas.example.com/share2 $ cd /run/user/1000/gvfs/smb- share\:server\=nas.example.com\,share\=share2/another/path $ time ls ... 528 subdirs approximately ... real 0m45,075s user 0m0,013s sys 0m0,058s $ time ls | wc 5281631 10893 real 0m0,911s user 0m0,003s sys 0m0,005s Factor is about 50. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1862264/+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 1862264] [NEW] Browsing smb share is painfully slow
You have been subscribed to a public bug: Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020). TEST #1: To establish a baseline/expected behavior, we first mount an SMB share via mount.cifs and time an ls command: $ sudo mount -t cifs -o username=pablo //myserver.example.com/share ~/mnt/share $ cd ~/mnt/share/some/dir $ time ls ... approx 320 files ... real0m1,080s user0m0,008s sys 0m0,005s $ sudo umount ~/mnt/share TEST #2 Now we do the same via gio mount: $ gio mount smb://myserver.example.com/share cd /run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir $ time ls ... same 320 files ... real0m28,999s user0m0,013s sys 0m0,032s Enumeration of files is about 29 times slower when mounted via gio mount than via mount -t cifs. TEST #3 Now for the real weird: while using the gio-mounted folder, we now time ls IN COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...): $ time ls | wc 321 3239804 real0m0,546s user0m0,006s sys 0m0,004s Note that this is almost TWICE AS FAST than the "fast" mount of test #1 and about 53 times faster than "slow" test #2 ! The expectation is that Tests 1 and 2 should have similar timings, not differing by a factor of 30 or so. More disturbing, there is no good reason why tests 2 and 3 differ by an even bigger factor of 53: They use the same underlying infrastructure which test 3 proves is adequately fast. And yet, we get this slow down in test 2. As a final note, these benchmarks are a distilled version of the original real-life motivating scenario where a Java-based program would simply take tens of minutes to display the same list of 320 files when mounted via gio mount and a second or so when mounted via mount -t cifs. The same timing difference is of course visible in any file manager. Hope this helps PS: several old/ancient bug reports exist for a similar issue and I deliberately copied the title from one of them (#259771) PS2: may or may not be relevant: The remote server is a VM running Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu stock SSTP). PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM) $ gio mount smb://nas.example.com/share2 $ cd /run/user/1000/gvfs/smb- share\:server\=nas.example.com\,share\=share2/another/path $ time ls ... 528 subdirs approximately ... real0m45,075s user0m0,013s sys 0m0,058s $ time ls | wc 5281631 10893 real0m0,911s user0m0,003s sys 0m0,005s Factor is about 50. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Browsing smb share is painfully slow https://bugs.launchpad.net/bugs/1862264 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862928] Re: python-crypto needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)
mine installs on 20.04 devel but with other warnings: /usr/lib/python3/dist-packages/Crypto/Random/Fortuna/FortunaGenerator.py:28: Syn taxWarning: "is" with a literal. Did you mean "=="? if sys.version_info[0] is 2 and sys.version_info[1] is 1: /usr/lib/python3/dist-packages/Crypto/Random/Fortuna/FortunaGenerator.py:28: Syn taxWarning: "is" with a literal. Did you mean "=="? if sys.version_info[0] is 2 and sys.version_info[1] is 1: /usr/lib/python3/dist-packages/Crypto/SelfTest/Random/test_random.py:107: Syntax Warning: "is" with a literal. Did you mean "=="? if sys.version_info[0] is 3: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1862928 Title: python-crypto needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh) Status in python-crypto package in Ubuntu: In Progress Bug description: If you try: (c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be installed Depends: libgmp10:amd64 but it is not going to be installed python3-samba : Depends: python3-crypto but it is not installable You won't be able to install python3-crypto. With a simple rebuild problem goes away. NOTE: This is needed to fix: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316 (Where I'm getting back winbind to samba on i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928/+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 1862928] [NEW] python-crypto needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)
Public bug reported: If you try: (c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be installed Depends: libgmp10:amd64 but it is not going to be installed python3-samba : Depends: python3-crypto but it is not installable You won't be able to install python3-crypto. With a simple rebuild problem goes away. NOTE: This is needed to fix: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316 (Where I'm getting back winbind to samba on i386) ** Affects: python-crypto (Ubuntu) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: In Progress ** Changed in: python-crypto (Ubuntu) Status: New => In Progress ** Changed in: python-crypto (Ubuntu) Importance: Undecided => Medium ** Changed in: python-crypto (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1862928 Title: python-crypto needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh) Status in python-crypto package in Ubuntu: In Progress Bug description: If you try: (c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be installed Depends: libgmp10:amd64 but it is not going to be installed python3-samba : Depends: python3-crypto but it is not installable You won't be able to install python3-crypto. With a simple rebuild problem goes away. NOTE: This is needed to fix: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1861316 (Where I'm getting back winbind to samba on i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928/+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 1862925] [NEW] libtool-doc gives dpkg error on install
Public bug reported: Ubuntu 20.04 development branch with kernel 5.4.0-12-generic system up to date @ 12/2/2020 Installing libtool-doc gives a dpkg error on install: lotuspsychje @ RooTBoX: ~ $ sudo apt install libtool-doc Package lists are read ... Ready Tree of requirements is being built The status information is read ... Ready The following NEW packages will be installed: libtool doc 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 0 B / 232 kB of archives must be retrieved. After this operation, an additional 1,072 kB of disk space will be used. (Database is being read ... 247912 files and folders currently installed .) Unpacking ... / libtool-doc_2.4.6-12_all.deb is being prepared ... Unpacking libtool-doc (2.4.6-12) ... dpkg: Error processing archive /var/cache/apt/archives/libtool-doc_2.4.6-1 2_all.deb (--unpack): attempt to overwrite '/ usr / share / doc / libtool / AUTHORS', whatever in package t libtool 2.4.6-12 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors found while processing: /var/cache/apt/archives/libtool-doc_2.4.6-12_all.deb E: Sub-process / usr / bin / dpkg returned an error code (1) ** Affects: libtool (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtool in Ubuntu. https://bugs.launchpad.net/bugs/1862925 Title: libtool-doc gives dpkg error on install Status in libtool package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 development branch with kernel 5.4.0-12-generic system up to date @ 12/2/2020 Installing libtool-doc gives a dpkg error on install: lotuspsychje @ RooTBoX: ~ $ sudo apt install libtool-doc Package lists are read ... Ready Tree of requirements is being built The status information is read ... Ready The following NEW packages will be installed: libtool doc 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 0 B / 232 kB of archives must be retrieved. After this operation, an additional 1,072 kB of disk space will be used. (Database is being read ... 247912 files and folders currently installed .) Unpacking ... / libtool-doc_2.4.6-12_all.deb is being prepared ... Unpacking libtool-doc (2.4.6-12) ... dpkg: Error processing archive /var/cache/apt/archives/libtool-doc_2.4.6-1 2_all.deb (--unpack): attempt to overwrite '/ usr / share / doc / libtool / AUTHORS', whatever in package t libtool 2.4.6-12 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors found while processing: /var/cache/apt/archives/libtool-doc_2.4.6-12_all.deb E: Sub-process / usr / bin / dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1862925/+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 1862925] Re: libtool-doc gives dpkg error on install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libtool (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtool in Ubuntu. https://bugs.launchpad.net/bugs/1862925 Title: libtool-doc gives dpkg error on install Status in libtool package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 development branch with kernel 5.4.0-12-generic system up to date @ 12/2/2020 Installing libtool-doc gives a dpkg error on install: lotuspsychje @ RooTBoX: ~ $ sudo apt install libtool-doc Package lists are read ... Ready Tree of requirements is being built The status information is read ... Ready The following NEW packages will be installed: libtool doc 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 0 B / 232 kB of archives must be retrieved. After this operation, an additional 1,072 kB of disk space will be used. (Database is being read ... 247912 files and folders currently installed .) Unpacking ... / libtool-doc_2.4.6-12_all.deb is being prepared ... Unpacking libtool-doc (2.4.6-12) ... dpkg: Error processing archive /var/cache/apt/archives/libtool-doc_2.4.6-1 2_all.deb (--unpack): attempt to overwrite '/ usr / share / doc / libtool / AUTHORS', whatever in package t libtool 2.4.6-12 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors found while processing: /var/cache/apt/archives/libtool-doc_2.4.6-12_all.deb E: Sub-process / usr / bin / dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1862925/+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 1266492] Re: ld:i386 crashes with -static -fPIE -pie
closing task for trusty
** Changed in: evolution-data-server (Ubuntu Trusty)
Status: Triaged => Invalid
** Changed in: binutils (Ubuntu Trusty)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1266492
Title:
ld:i386 crashes with -static -fPIE -pie
Status in GLibC:
Incomplete
Status in binutils package in Ubuntu:
Confirmed
Status in eglibc package in Ubuntu:
Fix Released
Status in evolution-data-server package in Ubuntu:
Fix Released
Status in xorg-server package in Ubuntu:
Fix Released
Status in binutils source package in Trusty:
Invalid
Status in eglibc source package in Trusty:
Fix Released
Status in evolution-data-server source package in Trusty:
Invalid
Status in xorg-server source package in Trusty:
Fix Released
Status in eglibc package in Debian:
Fix Released
Bug description:
Making a simple file conftest.c with the following contents:
int main() { return 0; }
And then compiling it on i386 with gcc -fPIE -pie -static conftest.c
returns:
*** Error in `/usr/bin/ld': corrupted double-linked list: 0x08dddb38
***
This breaks compilation xorg-server on i386. I believe that -static
-fPIE -pie is probably invalid, and it fails on amd64 too.
$ gcc -fPIE -pie -static conftest.c
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.8/crtbeginT.o: relocation
R_X86_64_32 against `__TMC_END__' can not be used when making a shared object;
recompile with -fPIC
/usr/lib/gcc/x86_64-linux-gnu/4.8/crtbeginT.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
But autoconf hangs on the corrupted double-linked list, which times
out the xorg-server build.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1266492/+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 1862453] Re: static ip netplan does not apply on boot
Please enable networkd debug with: $ sudo systemctl edit systemd-networkd which will open an editor, put this in and save it: [Service] Environment=SYSTEMD_LOG_LEVEL=debug then reboot, and attach the entire journal, e.g. with: $ journalctl -b --no-pager -- 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/1862453 Title: static ip netplan does not apply on boot Status in systemd package in Ubuntu: Incomplete Bug description: I was advised to report a bug when I posted the following thread... https://askubuntu.com/questions/1208145/netplan-apply-required-after-reboot After a reboot, I must manually run "sudo netplan apply" to set the static IP described in 50-cloud-init.yaml. Journalctl repeatedly reports: Feb 04 20:10:52 lei systemd-networkd[935]: Failed to connect to bus: Permission denied during boot. Once booted, I can manually run "netplan apply" and everything configures normally. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.38 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sat Feb 8 08:54:00 2020 InstallationDate: Installed on 2019-12-28 (42 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=cb6893b3-aa11-452c-8b50-cf43b1ddaee3 ro maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: Z97 Anniversary dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd03/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Anniversary:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862453/+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 1839290] Re: systemd doesn't restart a service after crashes
Here is a minimal example, courtesy of bl33pbl0p from the github issue. I've double-checked it and it is valid test case for this issue: $ systemctl cat foo # /etc/systemd/system/foo.service [Unit] PartOf=bar.service [Service] ExecStart=/bin/sleep infinity RestartSec=0s Restart=always $ systemctl cat bar # /etc/systemd/system/bar.service [Unit] BindsTo=foo.service #Same with or without After=, the window is very small to make a difference. After=foo.service [Service] ExecStart=/bin/sleep infinity $ sudo systemctl status foo bar ● foo.service Loaded: loaded (/etc/systemd/system/foo.service; static; vendor preset: enabled) Active: active (running) since Wed 2020-02-12 11:38:30 MSK; 36s ago Main PID: 1614 (sleep) Tasks: 1 Memory: 172.0K CPU: 1ms CGroup: /system.slice/foo.service └─1614 /bin/sleep infinity Feb 12 11:38:30 pono-mac systemd[1]: Started foo.service. ● bar.service Loaded: loaded (/etc/systemd/system/bar.service; static; vendor preset: enabled) Active: active (running) since Wed 2020-02-12 11:38:30 MSK; 36s ago Main PID: 1625 (sleep) Tasks: 1 Memory: 188.0K CPU: 972us CGroup: /system.slice/bar.service └─1625 /bin/sleep infinity Feb 12 11:38:30 pono-mac systemd[1]: Started bar.service. $ sudo kill -6 1614 $ sudo systemctl status foo bar ● foo.service Loaded: loaded (/etc/systemd/system/foo.service; static; vendor preset: enabled) Active: failed (Result: resources) since Wed 2020-02-12 11:39:24 MSK; 2s ago Process: 1614 ExecStart=/bin/sleep infinity (code=killed, signal=ABRT) Main PID: 1614 (code=killed, signal=ABRT) Feb 12 11:39:24 pono-mac systemd[1]: foo.service: Unit entered failed state. Feb 12 11:39:24 pono-mac systemd[1]: foo.service: Failed with result 'signal'. Feb 12 11:39:24 pono-mac systemd[1]: foo.service: Service has no hold-off time, scheduling restart. Feb 12 11:39:24 pono-mac systemd[1]: foo.service: Failed to schedule restart job: Transaction is destructive. Feb 12 11:39:24 pono-mac systemd[1]: foo.service: Unit entered failed state. Feb 12 11:39:24 pono-mac systemd[1]: foo.service: Failed with result 'resources'. ● bar.service Loaded: loaded (/etc/systemd/system/bar.service; static; vendor preset: enabled) Active: inactive (dead) since Wed 2020-02-12 11:39:24 MSK; 2s ago Process: 1625 ExecStart=/bin/sleep infinity (code=killed, signal=TERM) Main PID: 1625 (code=killed, signal=TERM) Feb 12 11:38:30 pono-mac systemd[1]: Started bar.service. Feb 12 11:39:24 pono-mac systemd[1]: Stopping bar.service... Feb 12 11:39:24 pono-mac systemd[1]: Stopped bar.service. -- 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/1839290 Title: systemd doesn't restart a service after crashes Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Incomplete Status in systemd source package in Bionic: Incomplete Status in systemd source package in Disco: Incomplete Bug description: Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1839290/+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 1862913] [NEW] ubuntu-bug failing silently if Settings > Privacy > Problem Reporting disabled
Public bug reported: On a system running Ubuntu 19.10 (upgraded over several versions) if Settings > Privacy > Problem Reporting is disabled then running ubuntu-bug collects the data and asks if it should send it. On clicking Send it silently terminates and does nothing. An appropriate response would either be to send the data anyway, since the user has been explicitly asked, or to fail with a message explaining why. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportLog: ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: called for pid 2865, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: executable: /usr/lib/tracker/tracker-miner-fs (command line "/usr/lib/tracker/tracker-miner-fs") ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: debug: session gdbus call: (true,) ERROR: apport (pid 3384) Mon Feb 10 14:41:31 2020: wrote report /var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 09:03:53 2020 InstallationDate: Installed on 2014-10-21 (1939 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago) ** Affects: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1862913 Title: ubuntu-bug failing silently if Settings > Privacy > Problem Reporting disabled Status in apport package in Ubuntu: New Bug description: On a system running Ubuntu 19.10 (upgraded over several versions) if Settings > Privacy > Problem Reporting is disabled then running ubuntu-bug collects the data and asks if it should send it. On clicking Send it silently terminates and does nothing. An appropriate response would either be to send the data anyway, since the user has been explicitly asked, or to fail with a message explaining why. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportLog: ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: called for pid 2865, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: executable: /usr/lib/tracker/tracker-miner-fs (command line "/usr/lib/tracker/tracker-miner-fs") ERROR: apport (pid 3384) Mon Feb 10 14:41:30 2020: debug: session gdbus call: (true,) ERROR: apport (pid 3384) Mon Feb 10 14:41:31 2020: wrote report /var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 09:03:53 2020 InstallationDate: Installed on 2014-10-21 (1939 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1862913/+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
