[Touch-packages] [Bug 1876962] Re: package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
[Expired for libxml2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libxml2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1876962 Title: package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxml2 package in Ubuntu: Expired Bug description: Fresh install of Ubuntu 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: python3-distupgrade:amd64: Install python3-update-manager:amd64: Install update-manager-core:amd64: Install update-manager:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 5 17:56:48 2020 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: libxml2 Title: package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1876962/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- 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/1852067 Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok. Status in linux package in Ubuntu: New Bug description: Steps to replicate the bug. 1. Start laptop with Ubuntu 18.04.3 LTS. Sound from built-in speakers works fine. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio 2. Connect headphones (wired, mini-jack connector). Sound from headphones works fine. No sound from built-in speakers (which is OK, obviously). Settings -> Sound -> Output shows one device: Headphones - Built-in Audio 3. Disconnect headphones from computer. No sound from built-in speakers. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, high volume) Changing volume, turning ON -> OFF -> ON, user logout->login doesn't help. Only full laptop restart helps. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 2115 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 12:26:58 2019 InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1672 F pulseaudio marcin 2115 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852067/+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 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
Which graphics does the HDMI connect to? Intel or Nvidia? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+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 1887016] Re: Openssh default config has two PasswordAuthentication params
I've made clean installation on my desktop from .iso downloaded from ubuntu.com (also re-checked on virtualbox). No additional packages or updates were installed. Ubuntu Desktop config is OK though. Maybe the problem is not in openssh package, but in some postinstall or cloudinit scripts, that change the config file after OS installation? -- 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/1887016 Title: Openssh default config has two PasswordAuthentication params Status in openssh package in Ubuntu: Incomplete Bug description: In Ubuntu server 20.04 the /etc/ssh/sshd_config file has an additional `PasswordAuthentication yes` string in the end. It can lead to security problems, because there's already one string `# PasswordAuthentication yes` in the beginning of the file. It is supposed to be uncommented if it's needed to change the default value. But if the user uncomments this string and set in to "no", it will be overriden by the last line of config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1887016/+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 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority
@sil2100 hello Lukasz, I just update the bug's description, would you please check if it is ok for you to proceed SRU. Thanks! ** Description changed: [Impact] * On the Dell machines with multi function audio jack, the headphone/headset can't output sound automatically, which is different from ubuntu 18.04. The headphone/headset should be able to output sound automatically after plugging in the audio jack. [Test Case] * On Tiger Lake platform -Reproduce step: + Reproduce step: 1. plug headphone/headset 2. open g-c-c sound to check Expect result: The output device should switch to headphone or headset, since headphone's priority is higher in ucm2 config. Actual result: The output device is still internal speaker. [Regression Potential] - * Low, just do a small change to store the ucm devices by their priority. - and upstream just merged this patch. + * The change insert the ucm device by its priority, the potential +regression is low, since if the change is not working properly, the +side effect is that the order of ucm devices are wrong, and it won't +switch to the correct output device as expect, but user can still +config it manually. [Other] * This bug originates from an OEM private bug #1875597, then ubuntu users reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 and the 1st issue of #1881659 have the same root cause as #1875597 * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, finally the audio jack is set to Mic2 mode, this make the audio jack can't output sound anymore. To fix it, let the audio jack set to Headset MIC mode by default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the device event to module-switch-on-port-available by the order of priority in the umc2. -- 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/1882161 Title: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] * On the Dell machines with multi function audio jack, the headphone/headset can't output sound automatically, which is different from ubuntu 18.04. The headphone/headset should be able to output sound automatically after plugging in the audio jack. [Test Case] * On Tiger Lake platform Reproduce step: 1. plug headphone/headset 2. open g-c-c sound to check Expect result: The output device should switch to headphone or headset, since headphone's priority is higher in ucm2 config. Actual result: The output device is still internal speaker. [Regression Potential] * The change insert the ucm device by its priority, the potential regression is low, since if the change is not working properly, the side effect is that the order of ucm devices are wrong, and it won't switch to the correct output device as expect, but user can still config it manually. [Other] * This bug originates from an OEM private bug #1875597, then ubuntu users reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 and the 1st issue of #1881659 have the same root cause as #1875597 * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, finally the audio jack is set to Mic2 mode, this make the audio jack can't output sound anymore. To fix it, let the audio jack set to Headset MIC mode by default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the device event to module-switch-on-port-available by the order of priority in the umc2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882161/+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 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority
** Description changed: - This bug originates from an OEM private bug #1875597, then ubuntu users - reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 - and the 1st issue of #1881659 have the same root cause as #1875597 + [Impact] - [Impact] - On the Dell machines with multi function audio jack, after installing the ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the headphone/headset can't output sound automatically after users plug in a headphone/headset. This is different from ubuntu 18.04, on the 18.04, the headphone/headset could output sound automatically after plugging in the audio jack. - - [Fix] - The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, finally the audio jack is set to Mic2 mode, this make the audio jack can't output sound anymore. To fix it, let the audio jack set to Headset MIC mode by default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the device event to module-switch-on-port-available by the order of priority in the umc2. + * On the Dell machines with multi function audio jack, the +headphone/headset can't output sound automatically, which is different +from ubuntu 18.04. The headphone/headset should be able to output +sound automatically after plugging in the audio jack. [Test Case] - applying the fix patch to pulseaudio, plug a headset/headphone to the multi function audio jack, play sound from headset/headphone, the sound could be heard from headset/headphone. - [Regression Risk] - Low, just do a small change to store the ucm devices by their priority. and upstream just merged this patch. + * Reproduce step: +1. plug headphone/headset +2. open g-c-c sound to check + +Expect result: The output device should switch to headphone or headset, + since headphone's priority is higher in ucm2 config. +Actual result: The output device is still internal speaker. + + [Regression Potential] + + * Low, just do a small change to store the ucm devices by their priority. +and upstream just merged this patch. + + [Other] + + * This bug originates from an OEM private bug #1875597, then ubuntu users +reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 +and the 1st issue of #1881659 have the same root cause as #1875597 + + * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and +Headset MIC, and the pulseaudio parse the input device Headset MIC +first then Mic2, finally the audio jack is set to Mic2 mode, this make +the audio jack can't output sound anymore. To fix it, let the audio +jack set to Headset MIC mode by default (Headset MIC has higher +priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the +device event to module-switch-on-port-available by the order of +priority in the umc2. ** Description changed: [Impact] - * On the Dell machines with multi function audio jack, the -headphone/headset can't output sound automatically, which is different -from ubuntu 18.04. The headphone/headset should be able to output -sound automatically after plugging in the audio jack. + * On the Dell machines with multi function audio jack, the + headphone/headset can't output sound automatically, which is different + from ubuntu 18.04. The headphone/headset should be able to output + sound automatically after plugging in the audio jack. [Test Case] - * Reproduce step: -1. plug headphone/headset -2. open g-c-c sound to check + * On Tiger Lake platform +Reproduce step: + 1. plug headphone/headset + 2. open g-c-c sound to check -Expect result: The output device should switch to headphone or headset, - since headphone's priority is higher in ucm2 config. -Actual result: The output device is still internal speaker. - + Expect result: The output device should switch to headphone or headset, + since headphone's priority is higher in ucm2 config. + Actual result: The output device is still internal speaker. + [Regression Potential] - * Low, just do a small change to store the ucm devices by their priority. -and upstream just merged this patch. + * Low, just do a small change to store the ucm devices by their priority. + and upstream just merged this patch. [Other] - * This bug originates from an OEM private bug #1875597, then ubuntu users -reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 -and the 1st issue of #1881659 have the same root cause as #1875597 + * This bug originates from an OEM private bug #1875597, then ubuntu users + reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 + and the 1st issue of #1881659 have the same root cause as
[Touch-packages] [Bug 1887016] Re: Openssh default config has two PasswordAuthentication params
Hello Rulon, can you please double-check where your openssh-server package came from? I don't have this "PasswordAuthentication yes" in any of my 20.04 systems, and a very quick look at the current package doesn't show this: $ apt-get download openssh-server Get:1 http://wopr.domain/ubuntu focal-updates/main amd64 openssh-server amd64 1:8.2p1-4ubuntu0.1 [377 kB] Fetched 377 kB in 0s (1,097 kB/s) $ mkdir openssh-server $ cd openssh-server $ ar x ../openssh-server_1%3a8.2p1-4ubuntu0.1_amd64.deb $ tar xf control.tar.xz $ tar xf data.tar.xz $ grep -r "PasswordAuthentication yes" usr/share/openssh/sshd_config:#PasswordAuthentication yes Of the versions of openssh that are on my local archive mirror, none of the sshd_config files had this line uncommented: $ rg "PasswordAuthentication yes" -g '**/sshd_config' openssh_5.9p1-5ubuntu1.10/sshd_config 64:#PasswordAuthentication yes openssh_7.2p2-4ubuntu2.9/sshd_config 72:#PasswordAuthentication yes openssh_7.2p2-4ubuntu2.10/sshd_config 72:#PasswordAuthentication yes openssh_6.6p1-2ubuntu1/sshd_config 73:#PasswordAuthentication yes openssh_5.9p1-5ubuntu1/sshd_config 64:#PasswordAuthentication yes openssh_8.0p1-4/sshd_config 56:#PasswordAuthentication yes openssh_8.0p1-6ubuntu0.1/sshd_config 56:#PasswordAuthentication yes openssh_6.6p1-2ubuntu2.13/sshd_config 73:#PasswordAuthentication yes openssh_7.7p1-4ubuntu0.3/sshd_config 56:#PasswordAuthentication yes openssh_7.7p1-4/sshd_config 56:#PasswordAuthentication yes openssh_8.2p1-4ubuntu0.1/sshd_config 58:#PasswordAuthentication yes openssh_7.6p1-4ubuntu0.3/sshd_config 56:#PasswordAuthentication yes openssh_7.6p1-4/sshd_config 56:#PasswordAuthentication yes openssh_7.2p2-4ubuntu2.8/sshd_config 72:#PasswordAuthentication yes openssh_8.3p1-1/sshd_config 58:#PasswordAuthentication yes openssh_8.1p1-5/sshd_config 56:#PasswordAuthentication yes openssh_7.6p1-4ubuntu0.4/sshd_config 56:#PasswordAuthentication yes openssh_7.9p1-10/sshd_config 56:#PasswordAuthentication yes openssh_7.2p2-4/sshd_config 72:#PasswordAuthentication yes openssh_8.0p1-4build1/sshd_config 56:#PasswordAuthentication yes openssh_8.0p1-6build1/sshd_config 56:#PasswordAuthentication yes openssh_8.2p1-4ubuntu1/sshd_config 58:#PasswordAuthentication yes openssh_8.1p1-1/sshd_config 56:#PasswordAuthentication yes openssh_8.2p1-4/sshd_config 58:#PasswordAuthentication yes How was this system installed? Was it customized by an ISP or cloud provider? Were any programs installed outside of the Ubuntu Archive that might have such a configuration change as part of an install script? Thanks ** Changed in: openssh (Ubuntu) Status: New => Incomplete ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1887016 Title: Openssh default config has two PasswordAuthentication params Status in openssh package in Ubuntu: Incomplete Bug description: In Ubuntu server 20.04 the /etc/ssh/sshd_config file has an additional `PasswordAuthentication yes` string in the end. It can lead to security problems, because there's already one string `# PasswordAuthentication yes` in the beginning of the file. It is supposed to be uncommented if it's needed to change the default value. But if the user uncomments this string and set in to "no", it will be overriden by the last line of config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1887016/+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 1659719] Re: ssh can't call a binary from a snap without the full path
** No longer affects: snapd (Ubuntu) ** No longer affects: snapd (Ubuntu Groovy) ** Also affects: pam (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: pam (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pam (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1659719 Title: ssh can't call a binary from a snap without the full path Status in Snappy: Fix Committed Status in livecd-rootfs package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Confirmed Status in pam package in Ubuntu: In Progress Status in livecd-rootfs source package in Xenial: New Status in openssh source package in Xenial: New Status in pam source package in Xenial: New Status in livecd-rootfs source package in Bionic: New Status in openssh source package in Bionic: New Status in pam source package in Bionic: New Status in livecd-rootfs source package in Focal: New Status in openssh source package in Focal: New Status in pam source package in Focal: New Status in livecd-rootfs source package in Groovy: Fix Released Status in openssh source package in Groovy: Confirmed Status in pam source package in Groovy: In Progress Bug description: ssh can't call a binary from a snap, it will only work using the full path. Let's say I have the hello snap installed in 192.168.122.24. Then: elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello elopio@192.168.122.24's password: bash: hello: command not found elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello elopio@192.168.122.24's password: Hello, world! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+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 1881982] Re: DoS vulnerability: cause resource exhaustion
Please use CVE-2020-11937 for this issue. Thanks. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-11937 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1881982 Title: DoS vulnerability: cause resource exhaustion Status in whoopsie package in Ubuntu: Confirmed Status in whoopsie source package in Xenial: Confirmed Status in whoopsie source package in Bionic: Confirmed Status in whoopsie source package in Eoan: Confirmed Status in whoopsie source package in Focal: Confirmed Status in whoopsie source package in Groovy: Confirmed Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. # Vulnerability description The parse_report() function in whoopsie.c allows attackers to cause a denial of service (memory leak) via a crafted file. Exploitation of this issue causes excessive memory consumption which results in the Linux kernel triggering OOM killer on arbitrary process. This results in the process being terminated by the OOM killer. # Details We have found a memory leak vulnerability during the parsing the crash file, when a collision occurs on GHashTable through g_hash_table_insert(). According to [1], if the key already exists in the GHashTable, its current value is replaced with the new value. If 'key_destory_func' and 'value_destroy_func' are supplied when creating the table, the old value and the passed key are freed using that function. Unfortunately, whoopsie does not handle the old value and the passed key when collision happens. If a crash file contains same repetitive key-value pairs, it leads to memory leak as much as the amount of repetition and results in denial-of-service. [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g -hash-table-insert # PoC (*Please check the below PoC: whoopsie_killer.py) 1) Generates a certain malformed crash file that contains same repetitive key-value pairs. 2) Trigger the whoopsie to read the generated crash file. 3) After then, the whoopsie process has been killed. # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch) We should use g_hash_table_new_full() with ‘key_destroy_func’ and ‘value_destroy_func’ functions instead of g_hash_table_new(). Otherwise, before g_hash_table_insert(), we should check the collision via g_hash_table_lookup_extended() and obtain pointer to the old value and remove it. Sincerely, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 1698604] Re: login will show unmasked password if user types too fast on a slow system
Just had this when updating Ubuntu via the terminal - first three characters of sudo password displayed on terminal (where the green blob is on the photo). ** Attachment added: "terminal-bug.jpg" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1698604/+attachment/5391151/+files/terminal-bug.jpg -- 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/1698604 Title: login will show unmasked password if user types too fast on a slow system Status in shadow package in Ubuntu: Confirmed Bug description: At the login, from the terminal, the user must login using his username and password. The program first displays " login:", then the user enters his username. Once the user has pressed "enter", he must enter his password. The user may type too quickly before "Password:" appears and thus what he types before "Password:" was displayed will appear on the screen. This occurs when the computer is slow when verifying the login username. Users that are used to fast computer will start typing right their password right after pressing "enter" and the characters will appear on the screen. The result would be something like this: Ubuntu 16.04.2 LTS computername tty2 computername login: myusername mypPassword: People who may look at my screen will see that my password starts with "myp". The other characters typed after that "Password:" was displayed are invisible. The solution would be to make every characters that are typed after the user has entered his password invisible. It could also be a good idea to give the user a sound cue (a PC speaker beep) when he enters a character in the case where he starts typing his password too fast. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1698604/+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 1698604] Re: login will show unmasked password if user types too fast on a slow system
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: shadow (Ubuntu) Status: New => Confirmed -- 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/1698604 Title: login will show unmasked password if user types too fast on a slow system Status in shadow package in Ubuntu: Confirmed Bug description: At the login, from the terminal, the user must login using his username and password. The program first displays " login:", then the user enters his username. Once the user has pressed "enter", he must enter his password. The user may type too quickly before "Password:" appears and thus what he types before "Password:" was displayed will appear on the screen. This occurs when the computer is slow when verifying the login username. Users that are used to fast computer will start typing right their password right after pressing "enter" and the characters will appear on the screen. The result would be something like this: Ubuntu 16.04.2 LTS computername tty2 computername login: myusername mypPassword: People who may look at my screen will see that my password starts with "myp". The other characters typed after that "Password:" was displayed are invisible. The solution would be to make every characters that are typed after the user has entered his password invisible. It could also be a good idea to give the user a sound cue (a PC speaker beep) when he enters a character in the case where he starts typing his password too fast. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1698604/+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 1820068] Re: specifying -O no-expr-simplify results in cache miss
** Changed in: apparmor Assignee: John Johansen (jjohansen) => Jaroslavas Karmazinas (cheops) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1820068 Title: specifying -O no-expr-simplify results in cache miss Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Disco: Fix Released Status in apparmor source package in Eoan: Fix Released Bug description: [Impact] * AppArmor 2.13 unconditionally invalidates its cache when parser options are specified. To decrease compile times for ARM systems, -O no-expr-simplify has been used in Ubuntu for click and snap policy for many years, but was temporarily disabled during the disco development release with the 2.13 upload so caching properly worked everywhere. Now that a simple upstream workaround is available (and already in eoan), we'd like to apply the upstream patch and re-enable -O no-expr-simplify. * A condition of the AppArmor 2.13 feature freeze exception was to fix this bug in SRU to re-enable -O no-expr-simplify. This will help compile times for all architectures with default and typical AppArmor policy (ie, a mixture of (distro) system and snap policy), but especially ARM systems with snaps where the improvement could be in terms of minutes saved. * Specifically, the upstream patch workaround to no longer unconditionally skip reading the cache when parser options are specified. It also re-enables an existing quilt patch to update /etc/apparmor/parser.conf to use no-expr-simplify. [Test Case] # setup $ mkdir -p /tmp/aa/cache /tmp/aa/profiles $ cp /etc/apparmor.d/sbin.dhclient /tmp/aa/profiles/ # no options, no cache, expect a miss and to write $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient # no options, cache, expect a hit $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache hit: /tmp/aa/cache/26b63962.0/sbin.dhclient # reset $ rm -rf /tmp/aa/cache/* # options, no cache, expect a miss and to write $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load -O no-expr-simplify --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient # options, cache, expect a hit $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load -O no-expr-simplify --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient # SHOULD BE A HIT Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient Same thing happens if omitting -O no-expr-simplify but add Optimize =no-expr-simplify to /etc/apparmor/parser.conf. [Regression Potential] The regression potential is considered low since the patch is simple and easily verifiable. If something went wrong, it would be around cache invalidation which the above test case will demonstrate it works correctly. # Original description With 2.13.2 and the most recent testsuite patches from the 2.13 branch, I find that the cache works correctly when no options are specified. Eg # setup $ mkdir -p /tmp/aa/cache /tmp/aa/profiles $ cp /etc/apparmor.d/sbin.dhclient /tmp/aa/profiles/ # no options, no cache, expect a miss and to write $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient # no options, cache, expect a hit $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache hit: /tmp/aa/cache/26b63962.0/sbin.dhclient # reset $ rm -rf /tmp/aa/cache/* # options, no cache, expect a miss and to write $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load -O no-expr-simplify --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient # options, cache, expect a hit $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load -O no-expr-simplify --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient # SHOULD BE A HIT Wrote cache: /tmp/aa/cach
[Touch-packages] [Bug 1887018] [NEW] Xorg crash when I was using Visual Studio code, throwing me back to the login screen
Public bug reported: Sometimes, when this happens, the computer goes to sleep too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Thu Jul 9 17:47:23 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-07-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=b7d02d55-0b33-48b4-8eb2-5217925c5f81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887018 Title: Xorg crash when I was using Visual Studio code, throwing me back to the login screen Status in xorg package in Ubuntu: New Bug description: Sometimes, when this happens, the computer goes to sleep too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Thu Jul 9 17:47:23 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-07-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=b7d02d55-0b33-48b4-8eb2-5217925c5f81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.com
[Touch-packages] [Bug 1884265] Re: [fips] Not fully initialized digest segfaulting some client applications
I added return checks to ntpq code and this appears to solve the problem. Is it ok to make this an SRU? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1884265 Title: [fips] Not fully initialized digest segfaulting some client applications Status in openssl package in Ubuntu: New Status in openssl source package in Bionic: New Bug description: In FIPS mode on Bionic MD5 is semi-disabled causing some applications to segfault. Test case: sudo apt install ntp ntpq -p Segmentation fault (core dumped) What happens there is ntpq wants to iterate all available digests (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this task. EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c. For FIPS mode it adds: EVP_add_digest(EVP_md5()); What happens later in ntpq is (list_md_fn function inside ntpq.c): ctx = EVP_MD_CTX_new(); EVP_DigestInit(ctx, EVP_get_digestbyname(name)); EVP_DigestFinal(ctx, digest, &digest_len); First digest it gets is MD5, but while running EVP_DigestInit for it, it gets to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex): #ifdef OPENSSL_FIPS if (FIPS_mode()) { if (!(type->flags & EVP_MD_FLAG_FIPS) && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) { EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS); return 0; } } #endif Due to type->flags for MD5 being 0 there's an error set (EVP_R_DISABLED_FOR_FIPS). After getting back to ntpq.c: ctx->engine and ctx->digest are not set (due to the mentioned error), hence inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c) OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE); causes a segfault (ctx->digest is NULL). So either MD5 shouldn't be added in FIPS mode or it should have the EVP_MD_FLAG_FIPS to be properly initialized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1884265/+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 1887010] [NEW] problème de démarrage ordinateur lenovo G50
Public bug reported: Bonjour, En marche, l'ordinateur avec ubuntu 18.04 fonctionne très bien. Il s'éteint facilement. Pour le re démarrer, l'écran reste noir très longtemps, parfois pendant une heure avant de retrouver le bureau et re fonctionner normalement. Le disque dur fonctionne normalement, la barette mémoire aussi que j'ai testé en la remplaçant par une neuve: le problème reste. Je ne comprends pas la cause de ce problème. Pouvez vous m'aider? Merci Hello, When running, the computer with ubuntu 18.04 works very well. It goes out easily. To restart it, the screen remains black for a very long time, sometimes for an hour before finding the office and re-operating normally. The hard drive works normally, the memory module also that I tested by replacing it with a new one: the problem remains. I do not understand the cause of this problem. Can you help me? Thank you (I do not understand English) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jul 9 21:48:34 2020 DistUpgraded: 2019-08-20 08:07:14,386 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:390c] Subsystem: Lenovo Radeon R5 M330 [17aa:390c] InstallationDate: Installed on 2019-08-14 (330 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 80E5 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic root=UUID=5732a78d-7e74-4071-9c56-b93ae51ffae3 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-08-20 (324 days ago) dmi.bios.date: 07/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN93WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.family: IDEAPAD dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jun 24 22:12:46 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887010 Title: problème de démarrage ordinateur lenovo G50 Status in xorg package in Ubuntu: New Bug description: Bonjour, En marche, l'ordinateur avec ubuntu 18.04 fonctionne très bien. Il s'éteint facilement. Pour le re démarrer, l'écran reste noir très longtemps, parfois pendant une heure avant de retrouver le bureau et re fonctionner normalement. Le disque dur fonctionne normalement, la barette mémoire aussi que j'ai testé en la remplaçant par une neuve: le problème reste. Je ne comprends pas la cause de ce problème. Pouvez vous m'aider? Merci Hello, When running, the computer with ubuntu 18.04 works very well. It goes out easily. To restart it, the screen remains black for a very long time, sometimes for an hour before finding the office and re-operating normally. The hard drive works normally, the memory module also that I tested by replacing it with a new one: the problem remains. I do not understand the cause of this problem. Can you help me? Thank you (I do not understand English) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubun
[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
Same result Kai-Heng. :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+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 1887001] [NEW] Mouse suddenly stopped working
Public bug reported: Mouse suddenly stopped working and didn't fix even after a reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 9 19:40:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:146a] InstallationDate: Installed on 2019-05-02 (434 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a3b4ba1a-5361-47c5-9d78-b04d395d28b8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 146A dmi.board.vendor: Hewlett-Packard dmi.board.version: 58.27 dmi.chassis.asset.tag: CNU0483ZXV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd10/21/2010:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr058B11242B1020100:rvnHewlett-Packard:rn146A:rvr58.27:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dm4 Notebook PC dmi.product.sku: XH124UA#ABA dmi.product.version: 058B11242B1020100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887001 Title: Mouse suddenly stopped working Status in xorg package in Ubuntu: New Bug description: Mouse suddenly stopped working and didn't fix even after a reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 9 19:40:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:146a] InstallationDate: Installed on 2019-05-02 (434 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a3b4ba1a-5361-47c5-9d78-b04d395d28b8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 146A dmi.board.vendor: Hewlett-Packard dmi.board.version: 58.27 dmi.chassis.asset.tag: CNU0483ZXV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd10/21/2010:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr058B11242B1020100:rvnHewlett-Packard:rn146A:rvr58.27:cvnHewlett-Packard:ct10:cvrChass
[Touch-packages] [Bug 1884265] Re: [fips] Not fully initialized digest segfaulting some client applications
Also, this is only applicable in bionic. Neither xenial nor focal experience this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1884265 Title: [fips] Not fully initialized digest segfaulting some client applications Status in openssl package in Ubuntu: New Status in openssl source package in Bionic: New Bug description: In FIPS mode on Bionic MD5 is semi-disabled causing some applications to segfault. Test case: sudo apt install ntp ntpq -p Segmentation fault (core dumped) What happens there is ntpq wants to iterate all available digests (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this task. EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c. For FIPS mode it adds: EVP_add_digest(EVP_md5()); What happens later in ntpq is (list_md_fn function inside ntpq.c): ctx = EVP_MD_CTX_new(); EVP_DigestInit(ctx, EVP_get_digestbyname(name)); EVP_DigestFinal(ctx, digest, &digest_len); First digest it gets is MD5, but while running EVP_DigestInit for it, it gets to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex): #ifdef OPENSSL_FIPS if (FIPS_mode()) { if (!(type->flags & EVP_MD_FLAG_FIPS) && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) { EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS); return 0; } } #endif Due to type->flags for MD5 being 0 there's an error set (EVP_R_DISABLED_FOR_FIPS). After getting back to ntpq.c: ctx->engine and ctx->digest are not set (due to the mentioned error), hence inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c) OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE); causes a segfault (ctx->digest is NULL). So either MD5 shouldn't be added in FIPS mode or it should have the EVP_MD_FLAG_FIPS to be properly initialized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1884265/+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 1884265] Re: [fips] Not fully initialized digest segfaulting some client applications
It seems 2 things are happening to generate this issue 1.fips-openssl in bionic has md5 and md5_sha1 in fips digest list with explicit purpose of accommodating PRF use only in fips mode. But you must pass the flag, EVP_MD_CTX_FLAG_NON_FIPS_ALLOW to successfully use them. 2. ntpq does not check return codes from EVP_ calls. It has, ctx = EVP_MD_CTX_new(); EVP_DigestInit(ctx, EVP_get_digestbyname(name)); EVP_DigestFinal(ctx, digest, &digest_len); EVP_MD_CTX_free(ctx); if (digest_len > (MAX_MAC_LEN - sizeof(keyid_t))) return; EVP_DigestInit() would have returned 0 in this case indicating a failure. Possible fixes: 1. in fips-libcrypto library remove md5 from fips digest list and keep md5_sha1 for PRF and mark as fips-allowed. Can still use md5 with EVP_MD_CTX_FLAG_NON_FIPS_ALLOW flag, but its just not in fips digest list. Note: this fix can be put in fips-update ppa for availability. But, it may be a while before it is re-certified. 2. ntpq should check its return codes and do appropriate thing on error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1884265 Title: [fips] Not fully initialized digest segfaulting some client applications Status in openssl package in Ubuntu: New Status in openssl source package in Bionic: New Bug description: In FIPS mode on Bionic MD5 is semi-disabled causing some applications to segfault. Test case: sudo apt install ntp ntpq -p Segmentation fault (core dumped) What happens there is ntpq wants to iterate all available digests (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this task. EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c. For FIPS mode it adds: EVP_add_digest(EVP_md5()); What happens later in ntpq is (list_md_fn function inside ntpq.c): ctx = EVP_MD_CTX_new(); EVP_DigestInit(ctx, EVP_get_digestbyname(name)); EVP_DigestFinal(ctx, digest, &digest_len); First digest it gets is MD5, but while running EVP_DigestInit for it, it gets to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex): #ifdef OPENSSL_FIPS if (FIPS_mode()) { if (!(type->flags & EVP_MD_FLAG_FIPS) && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) { EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS); return 0; } } #endif Due to type->flags for MD5 being 0 there's an error set (EVP_R_DISABLED_FOR_FIPS). After getting back to ntpq.c: ctx->engine and ctx->digest are not set (due to the mentioned error), hence inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c) OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE); causes a segfault (ctx->digest is NULL). So either MD5 shouldn't be added in FIPS mode or it should have the EVP_MD_FLAG_FIPS to be properly initialized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1884265/+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 1876219] Re: iris driver for old cpu
This bug disappears if I go back from intel x driver to standard modesetting driver. I didn't to that intenionally. I haven't been aware of that, but to get xbacklight working (to change screen brightness) I activated that. After removing that change in /etc/X11 mpv/celluloid works without this variable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1876219 Title: iris driver for old cpu Status in mesa package in Ubuntu: Confirmed Bug description: I am not completely sure where I should file the bug. I am using Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the default graphics driver, which results in crashes in multiple apps including guvcview and calibre. Setting MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but is it true that iris does not support older generations of Intel CPUs? If it is the case would it be possible to revert to i965 in those circumstances? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1876219/+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 1866365] Re: Missing /usr/lib/x86_64-linux-gnu/libfreetype.la file
** Changed in: freetype (Ubuntu) Importance: Undecided => Wishlist ** Changed in: freetype (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1866365 Title: Missing /usr/lib/x86_64-linux-gnu/libfreetype.la file Status in freetype package in Ubuntu: Invalid Bug description: This file disappeared from 19.10 dev package. Without the *.la file, libtool fails to configure libraries with GTK dependencies. My work around was to grab the file from 18.04 and change the metadata for the current library versions. That allowed me to successfully compile my package with GTK dependencies. Perhaps there is some libtool/autoconf magic that I do not understand here? Please do tell me how to address this this issue if I am misunderstanding the need for the *.la file. Thanks. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libfreetype6-dev 2.9.1-4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 10:18:10 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-12 (725 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: freetype UpgradeStatus: Upgraded to eoan on 2019-12-31 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1866365/+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 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
I've just encountered this issue myself, on a VM that started life as Ubuntu 16.04, do-release-upgrade to 18.04, then to 20.04, and now it fails to boot with a similar error: /lib/systemd/libsystemd- shared-245.so: undefined symbol: seccomp_api_get The only non-Ubuntu-standard stuff on this VM is some perl modules installed via CPAN, and none of those touch anything to do with Systemd, so I'm not sure why this is happening. I did see a post-install upgrade issue with the rkhunter package failing to find /usr/bin/egrep, but I ignored that issue and continued. I'm going to rollback, look for the lib involved, and see if I can remove it before retrying the do-release-upgrade -d to 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade Status in libseccomp package in Ubuntu: Incomplete Bug description: Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not possible. The error messages is: /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get [4.608900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 See also attached photograph of screen during boot. Upgrade followed steps from here: https://help.ubuntu.com/community/FocalUpgrades/Kubuntu With the excpetion that The -d flag was used for the do-release-upgrade: sudo do-release-upgrade -d -m desktop 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Prior to upgrade: Ubuntu 18.04.4 After upgrade (but never booted): Ubuntu (Kubuntu) 20.04 Note that Ubuntu had originally be installed, but kubuntu-desktop was recently installed to change to Kubuntu, but no booting problems were experienced before updating to 20.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Unknown -- Package version may have changed when upgrading to 20.04. 3) What you expected to happen Boot without kernel panic. 4) What happened instead Could not boot. Even selecting safe mode from grub could not boot. Had to restore system from backups. Will not attempt upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+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 1881972] Re: systemd-networkd crashes with invalid pointer
So far so good running the latest package for 10 hours. I'll let it run another day or two but previously I would have seen the issue by now. -- 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/1881972 Title: systemd-networkd crashes with invalid pointer Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: [impact] systemd-networkd double-free causes crash under some circumstances, such as adding/removing ip rules [test case] see original description [regression potential] this strdup's strings during addition of routing policy rules, so any regression would likely occur when adding/modifying/removing ip rules, possibly including networkd segfault or failure to add/remove/modify ip rules. [scope] this is needed for bionic. this is fixed by upstream commit eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in v240, so this is already included in Focal and later. I did not research what original commit introduced the problem, but the reporter indicates this did not happen for Xenial so it's unlikely this is a problem in Xenial or earlier. [original description] This is a serious regression with systemd-networkd that I ran in to while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm- ssd/ubuntu-bionic-18.04-amd64-server-20200131 with systemd-237-3ubuntu10.33 does NOT have the problem, but the next most recent AWS AMI ubuntu/images/hvm-ssd/ubuntu- bionic-18.04-amd64-server-20200311 with systemd-including 237-3ubuntu10.39 does. Also, a system booted from the (good) 20200131 AMI starts showing the problem after updating only systemd (to 237-3ubuntu10.41) and its direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly confident that a change to the systemd package between 237-3ubuntu10.33 and 237-3ubuntu10.39 introduced the problem and it is still present. On the NAT router I use three interfaces and have separate routing tables for admin and forwarded traffic. Things come up fine initially but every 30-60 minutes (DHCP lease renewal time?) one or more interfaces is reconfigured and most of the time systemd-networkd will crash and need to be restarted. Eventually the system becomes unreachable when the default crash loop backoff logic prevents the network service from being restarted at all. The log excerpt attached illustrates the crash loop. Also including the netplan and networkd config files below. # grep . /etc/netplan/* /etc/netplan/50-cloud-init.yaml:# This file is generated from information provided by the datasource. Changes /etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance reboot. To disable cloud-init's /etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a file /etc/netplan/50-cloud-init.yaml:# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: /etc/netplan/50-cloud-init.yaml:# network: {config: disabled} /etc/netplan/50-cloud-init.yaml:network: /etc/netplan/50-cloud-init.yaml:version: 2 /etc/netplan/50-cloud-init.yaml:ethernets: /etc/netplan/50-cloud-init.yaml:ens5: /etc/netplan/50-cloud-init.yaml:dhcp4: true /etc/netplan/50-cloud-init.yaml:match: /etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx /etc/netplan/50-cloud-init.yaml:set-name: ens5 /etc/netplan/99_config.yaml:network: /etc/netplan/99_config.yaml: version: 2 /etc/netplan/99_config.yaml: renderer: networkd /etc/netplan/99_config.yaml: ethernets: /etc/netplan/99_config.yaml:ens6: /etc/netplan/99_config.yaml: match: /etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy /etc/netplan/99_config.yaml: dhcp4: true /etc/netplan/99_config.yaml: dhcp4-overrides: /etc/netplan/99_config.yaml:use-routes: false /etc/netplan/99_config.yaml:ens7: /etc/netplan/99_config.yaml: match: /etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz /etc/netplan/99_config.yaml: mtu: 1500 /etc/netplan/99_config.yaml: dhcp4: true /etc/netplan/99_config.yaml: dhcp4-overrides: /etc/netplan/99_config.yaml:use-mtu: false /etc/netplan/99_config.yaml:use-routes: false # grep . /etc/networkd-dispatcher/*/* /etc/networkd-dispatcher/configured.d/nat:#!/bin/bash /etc/networkd-dispatcher/configured.d/nat:# Do additional configuration for the inside and outside interfaces /etc/networkd-dispatcher/configured.d/nat:# route table used for forwarded/routed/natted traffic /etc/networkd-dispatcher/configured.d/nat:FWD_TABLE=99 /etc/networkd-dispatcher/configured.d/nat:if [ "${IFACE}" = "ens6" ]; then /etc/networkd-dispatcher/configure
[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
same issue on hp pavillion au620tx # 17 works -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Status in Fedora: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority
The test case seems very vague sadly, could we get it a bit better clarified. What I mean is: what are the preliminary requirements for the test case to be valid? Does it have to be performed on specific hardware? What kind of hardware should it be? The regression potential field also doesn't say much about the regression potential, e.g. where possible regressions could be seen. I would appreciate if someone could update it with some regression analysis: what else can this break? Can different devices stop working by this? Which code paths are being touched by this change? Thanks! -- 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/1882161 Title: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Released Bug description: This bug originates from an OEM private bug #1875597, then ubuntu users reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 and the 1st issue of #1881659 have the same root cause as #1875597 [Impact] On the Dell machines with multi function audio jack, after installing the ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the headphone/headset can't output sound automatically after users plug in a headphone/headset. This is different from ubuntu 18.04, on the 18.04, the headphone/headset could output sound automatically after plugging in the audio jack. [Fix] The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, finally the audio jack is set to Mic2 mode, this make the audio jack can't output sound anymore. To fix it, let the audio jack set to Headset MIC mode by default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the device event to module-switch-on-port-available by the order of priority in the umc2. [Test Case] applying the fix patch to pulseaudio, plug a headset/headphone to the multi function audio jack, play sound from headset/headphone, the sound could be heard from headset/headphone. [Regression Risk] Low, just do a small change to store the ucm devices by their priority. and upstream just merged this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882161/+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 1861177] Re: seccomp_rule_add is very slow
As discussed on IRC, I have reviewed all the SRUs. They looked correct from my POV (although I guess I'd appreciate a second opinion from the security team). Since we want to include those in the -security pockets as well, I have uploaded all of them to a security-only Bileto PPA. I have confirmed via the build logs that only -security is enabled. The PPA can be found here: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4143/+packages Once the packages build correctly, I will bin-copy them to -proposed and remove the source uploads from the upload queues. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1861177 Title: seccomp_rule_add is very slow Status in snapd: Invalid Status in libseccomp package in Ubuntu: In Progress Status in libseccomp source package in Xenial: In Progress Status in libseccomp source package in Bionic: In Progress Status in libseccomp source package in Eoan: In Progress Status in libseccomp source package in Focal: In Progress Status in libseccomp source package in Groovy: In Progress Bug description: [IMPACT] There is a known and patched issue with version 2.4 of libseccomp where certain operations have a large performance regression. This is causing some packages that use libseccomp such as container orchestration systems to occasionally time out or otherwise fail under certain workloads. Please consider porting the patch into the various Ubuntu versions that have version 2.4 of libseccomp and into the backports. The performance patch from version 2.5 (yet to be released) applies cleanly on top of the 2.4 branch of libseccomp. For more information, and for a copy of the patch (which can also be cherry picked from the upstream libseccomp repos) see the similar Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913 Upstream issue : https://github.com/seccomp/libseccomp/issues/153 Upstream fix : https://github.com/seccomp/libseccomp/pull/180/ [Test Case] For this test case we use Docker on Ubuntu Groovy (20.10) : --> Current libseccomp version #dpkg -l | grep libseccomp ii libseccomp2:amd64 2.4.3-1ubuntu3 amd64high level interface to Linux seccomp filter ## pull ubuntu image # docker pull ubuntu ## create a container # docker run --name test_seccomp -it 74435f89ab78 /bin/bash ## run test case # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done ... MAX TIME : real 0m10,319s user 0m0,018s sys 0m0,033s --> Patched libseccomp version # dpkg -l | grep libseccomp ii libseccomp2:amd64 2.4.3-1ubuntu4 amd64high level interface to Linux seccomp filter # docker start test_seccomp ## run test case # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done ... MAX TIME : real 0m3,650s user 0m0,025s sys 0m0,028s [Regression Potential] The first of the 2 patches cleans up the code that adds rules to a single filter without changing the logic of the code. The second patch introduces the idea of shadow transactions. On a successful transaction commit the old transaction checkpoint is preserved and is brought up to date with the current filter. The next time a new transaction starts, it checks is the a shadow transaction exist and if so the shadow is used instead of creating a new checkpoint from scratch [1]. This is the patch that mitigates the performance regression. Any potential regression will involve the parts of the code that add rules to filters and/or the code that creates and checks the shadow transactions. [Other] Affected releases : Groovy, Focal, Eoan, Bionic, Xenial. [1] https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1861177/+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 1878507] Re: No HDMI audio in ubuntu 20.04
Can you please temporarily remove "~/.config/pulse/* " and attach `pactl list cards` here? Thanks! ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878507 Title: No HDMI audio in ubuntu 20.04 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sound settings does not offer hdmi audio in 20.04, but was there in 16 and 18 LTSs. New HDMI monitor is fine but no audio. Reboot to Ubuntu 16.04.1 LTS (16.04) {linux /boot/vmlinuz-4.4.0-24-generic} and all is well. ALSA Information Script v 0.4.65 ran giving result at: http://alsa-project.org/db/?f=84926788cff2eb5d8d305d6a896608514495ce2f Deleting ~/.config/pulse/* broke all the sound but ok again when restored ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 1715 F pulseaudio /dev/snd/controlC1: paul 1715 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 01:06:50 2020 HibernationDevice: RESUME=UUID=6ee76bfb-393c-47bf-807f-6d0d8929c120 InstallationDate: Installed on 2016-06-15 (1428 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=a0ad560d-ee6e-4f49-b40f-d239ecfcf167 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-06 (7 days ago) dmi.bios.date: 12/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0915 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785TD-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0915:bd12/22/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878507/+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 1363583] Re: usbmuxd is not compatible with libusbmuxd2 in ubuntu 14.10
Ubuntu 14.10 is EOL since July 2015. New versions of Ubuntu have new versions of usbmuxd and libusbmuxd ** Changed in: usbmuxd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/1363583 Title: usbmuxd is not compatible with libusbmuxd2 in ubuntu 14.10 Status in usbmuxd package in Ubuntu: Fix Released Bug description: In Ubuntu 14.10, the version of libusbmuxd2 is 1.0.9, but usbmuxd is still 1.0.8. usbmuxd 1.0.8 does not support the new commands used in libusbmuxd2 1.0.9 Any program which use libusbmuxd2 will simply crash. $ ideviceinfo ideviceinfo: plist.c:194: plist_copy_node: Assertion `data' failed. Aborted the debug output of usbmuxd: $ sudo usbmuxd -v -f -u [15:29:58.274][3] usbmuxd v1.0.8 starting up [15:29:58.274][4] Creating socket [15:29:58.274][4] Initializing USB [15:29:58.276][4] Found new device with v/p 05ac:129a at 2-7 [15:29:58.276][4] Found interface 1 with endpoints 04/85 for device 2-7 [15:29:58.277][4] Using wMaxPacketSize=512 for device 2-7 [15:29:58.277][3] Connecting to new device on location 0x20007 as ID 1 [15:29:58.277][4] 1 device detected [15:29:58.277][3] Initialization complete [15:29:58.278][3] Connected to v1.0 device 1 on location 0x20007 with serial number *** [15:30:07.646][4] New client on fd 14 [15:30:07.646][1] Unexpected command 'ListDevices' received! [15:30:07.646][4] Client 14 connection closed [15:30:07.646][4] Disconnecting client fd 14 [15:30:07.647][4] New client on fd 14 [15:30:07.747][4] Client 14 connection closed [15:30:07.747][4] Disconnecting client fd 14 [15:30:07.747][4] New client on fd 14 [15:30:07.754][4] New client on fd 15 [15:30:07.755][1] Unexpected command 'ReadPairRecord' received! [15:30:07.755][4] New client on fd 16 [15:30:07.755][1] Unexpected command 'ReadPairRecord' received! [15:30:07.757][4] Disconnecting client fd 14 [15:30:07.757][4] Client 15 connection closed [15:30:07.757][4] Disconnecting client fd 15 [15:30:07.757][4] Client 16 connection closed [15:30:07.757][4] Disconnecting client fd 16 I complied the latest source from https://github.com/libimobiledevice/usbmuxd, everything works. $ sudo usbmuxd -v -f -u [15:38:13.038][3] usbmuxd v1.0.9 starting up [15:38:13.038][4] Creating socket [15:38:13.038][4] Initializing USB [15:38:13.040][4] Found new device with v/p 05ac:129a at 2-7 [15:38:13.041][4] Found interface 1 with endpoints 04/85 for device 2-7 [15:38:13.042][4] Using wMaxPacketSize=512 for device 2-7 [15:38:13.042][3] Connecting to new device on location 0x20007 as ID 1 [15:38:13.042][4] 1 device detected [15:38:13.042][3] Initialization complete [15:38:13.042][3] Connected to v2.0 device 1 on location 0x20007 with serial number *** [15:38:13.042][4] preflight_worker_handle_device_add: Starting preflight on device ***... [15:38:13.043][4] New client on fd 16 [15:38:13.045][4] device_control_input: AppleUSBDeviceMux::handleConnectResult new session 0x8bc4a000 established 62078<-lo0->49706 62078<-usb->1 [15:38:13.050][4] New client on fd 18 [15:38:13.054][4] New client on fd 20 [15:38:13.184][4] preflight_worker_handle_device_add: StartSession success for device *** [15:38:13.184][4] preflight_worker_handle_device_add: Finished preflight on device *** [15:38:13.188][4] Disconnecting client fd 16 [15:38:13.189][4] device_control_input: void AppleUSBDeviceMux::handleMuxTCPInput(__mbuf*) received reset, closing 0x8bc4a000 [15:38:30.383][4] New client on fd 15 [15:38:30.383][4] New client on fd 16 [15:38:30.383][4] Client 15 connection closed [15:38:30.383][4] Disconnecting client fd 15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1363583/+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 1886128] Re: systemd-resolved does not resolve address due to udp payload size.
Thank you for the explanation, I have gathered dns.pcap file with the required option. ** Attachment added: "dns (1).pcap" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886128/+attachment/5391049/+files/dns%20%281%29.pcap -- 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/1886128 Title: systemd-resolved does not resolve address due to udp payload size. Status in systemd package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04.4 LTS Release: 18.04 systemd-resolve --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid We met an error: on an attempt to resolve address, the following issue appears: ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> mharder-formrec.cognitiveservices.azure.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;mharder-formrec.cognitiveservices.azure.com. IN A ;; Query time: 231 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Tue Apr 28 20:47:14 UTC 2020 ;; MSG SIZE rcvd: 72 Let me provide you important notes about the issue: 1) It's not reproducing on Ubuntu 16; 2) Bypassing systemd-resolve - everything works fine; 3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE Successful query: 113516:27:25.964386 10.1.0.4168.63.129.16 DNS 128 Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com OPT Domain Name System (query) Transaction ID: 0xc2d4 Flags: 0x0120 Standard query 0... = Response: Message is a query .000 0... = Opcode: Standard query (0) ..0. = Truncated: Message is not truncated ...1 = Recursion desired: Do query recursively .0.. = Z: reserved (0) ..1. = AD bit: Set ...0 = Non-authenticated data: Unacceptable Questions: 1 Answer RRs: 0 Authority RRs: 0 Additional RRs: 1 Queries mharder-formrec.cognitiveservices.azure.com: type A, class IN Additional records : type OPT Name: Type: OPT (41) UDP payload size: 4096 Higher bits in extended RCODE: 0x00 EDNS0 version: 0 Z: 0x 0... = DO bit: Cannot handle DNSSEC security RRs .000 = Reserved: 0x Data length: 12 Option: COOKIE Unsuccessful query: 112816:27:25.713886 10.1.0.4168.63.129.16 DNS 116 Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com OPT Domain Name System (query) Transaction ID: 0x198d Flags: 0x0100 Standard query 0... = Response: Message is a query .000 0... = Opcode: Standard query (0) ..0. = Truncated: Message is not truncated ...1 = Recursion desired: Do query recursively .0.. = Z: reserved (0) ...0 = Non-authenticated data: Unacceptable Questions: 1 Answer RRs: 0 Authority RRs: 0 Additional RRs: 1 Queries mharder-formrec.cognitiveservices.azure.com: type A, class IN Additional records : type OPT Name: Type: OPT (41) UDP payload size: 512 Higher bits in extended RCODE: 0x00 EDNS0 version: 0 Z: 0x 0... = DO bit: Cannot handle DNSSEC security RRs .000 = Reserved: 0x Data length: 0 Notable difference: Success: UDP payload size: 4096 Failure: UDP payload size: 512 And notable differences in the responses: Success: Flags: 0x8180 Standard query response, No error ..0. = Truncated: Message is not truncated Failure: Flags: 0x8380 Standard query response, No error ..1. = Truncated: Message is truncated Interestingly, systemd-resolved is setting the maximum payload size to 512 regardless of whether EDNS0 is configured and regardless of what is sent to it for the payload size. I tried to found a way to change UDP_PAYLOAD_SIZE,but it seems it is only possible to change it only with direct code modifications. To manage notifications about this bug g
[Touch-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor
Hello, I am having the same issues in my hp envy y013cl laptop.I tried the above steps but could not get the audio from speakers working.Please help me fix this issue.Will provide all the necessary logs. Aplay-l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CX8200 Analog [CX8200 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 -- 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/1852067 Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok. Status in alsa-driver package in Ubuntu: New Bug description: Steps to replicate the bug. 1. Start laptop with Ubuntu 18.04.3 LTS. Sound from built-in speakers works fine. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio 2. Connect headphones (wired, mini-jack connector). Sound from headphones works fine. No sound from built-in speakers (which is OK, obviously). Settings -> Sound -> Output shows one device: Headphones - Built-in Audio 3. Disconnect headphones from computer. No sound from built-in speakers. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, high volume) Changing volume, turning ON -> OFF -> ON, user logout->login doesn't help. Only full laptop restart helps. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 2115 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 12:26:58 2019 InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1672 F pulseaudio marcin 2115 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux
Kopanocore armhf is the only persistent red, but this test/package is known to be flaky on armhf. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1557157 Title: apparmor profile denied for saslauthd: /run/saslauthd/mux Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Trusty: Won't Fix Status in openldap source package in Xenial: Fix Committed Status in openldap source package in Bionic: Fix Committed Status in openldap source package in Eoan: Fix Committed Status in openldap source package in Focal: Fix Committed Status in openldap source package in Groovy: Fix Released Bug description: [Impact] When using openldap with sasl authentication, the slapd process will communicate with the saslauthd daemon via a socket in {,/var}/run/saslauthd/mux. Unfortunately, this will fail in every Ubuntu release from trusty onwards, because slapd's apparmor profile doesn't contain the necessary directive to allow it to read/write from/to the socket specified above. The fix is simple: just add the necessary directive to allow slapd to read/write from/to the saslauthd socket. [Test Case] One can reproduce the problem by doing: $ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy $ lxc shell openldap-bugbug1557157-groovy # apt install slapd sasl2-bin ldap-utils apparmor-utils (As the domain name, use "example.com"). # sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd # cat > /etc/ldap/sasl2/slapd.conf << __EOF__ mech_list: PLAIN pwcheck_method: saslauthd __EOF__ # adduser openldap sasl # aa-enforce /etc/apparmor.d/usr.sbin.slapd # systemctl restart slapd.service # systemctl restart saslauthd.service # passwd root (You can choose any password here. You will need to type it when running the next command.) # ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root -Y PLAIN The command will fail with something like: ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80) additional info: SASL(-1): generic failure: Password verification failed [Regression Potential] This is an extremely simple and well contained fix, so I don't envision any possible regressions after applying it. It is important noticing that, since the problem affects older Ubuntu releases, the openldap package will have to be rebuilt against possible newer versions of libraries and other depencencies, which, albeit unlikely, may cause issues. [Original Description] When using slapd with saslauthd the processes communicate via the {,/var}/run/saslauthd/mux socket (this is the default location for the saslauthd server from the sasl2-bin package in the /etc/default/saslauthd config), but the apparmor profile for usr.sbin.slapd does not allow access to this socket/file. Syslog message: apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd" name="/run/saslauthd/mux" pid=1880 4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0 Please add the following line to /etc/apparmor.d/usr.sbin.slapd: /{,var/}run/saslauthd/mux rw, Ubuntu version: Ubuntu 14.04.4 LTS slapd version: 2.4.31-1+nmu2ubu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+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 1866303] Re: slapd crash with pwdAccountLockedTime and stacked overlays
Kopanocore armhf is the only persistent red, but this test/package is known to be flaky on armhf. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1866303 Title: slapd crash with pwdAccountLockedTime and stacked overlays Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Committed Status in openldap source package in Bionic: Fix Committed Status in openldap source package in Disco: Won't Fix Status in openldap source package in Eoan: Fix Committed Status in openldap package in Debian: Fix Released Bug description: [Impact] In the configuration and conditions described below, slapd can crash: 1. ppolicy overlay configured with pwdLockout: TRUE 2. smbk5pwd overlay stacked after ppolicy 3. an account locked out via pwdAccountLockedTime 4. a client binding to the locked-out account and also requesting the ppolicy control [Test Case] * get the files from the bug: mkdir slapd-test-case; cd slapd-test-case wget -ct0 https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334194/+files/slapd.conf https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334195/+files/data.ldif https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334196/+files/samba.schema https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334197/+files/script * run the script: sudo apt update && sudo sh ./script * With the bug, the result is: ldap_bind: Invalid credentials (49) slapd dead * If when confirming the bug you don't see "slapd dead" like above, check manually, as slapd might have been in the process of shutting down when the script checked its status: "sudo systemctl status slapd" * With the fixed packages, you get a living slapd at the end (you can run the script again on the same system after updating the packages): sudo sh ./script ... slapd running ldap_bind: Invalid credentials (49) slapd running [Regression Potential] The fix is in the password policy overlay (not enabled by default), so any regressions would be around that area and could potentially impact authentication ("binding") to openldap. [Other Info] This was fixed in focal and "cooked" there for a long while, as suggested by the Debian maintainer. We haven't received further bug reports about this in focal+. [Original Description] Hello, Please merge openldap 2.4.49+dfsg-2 from Debian unstable to fix an issue in the ppolicy overlay that can crash slapd. Please also consider SRUing the patch after it has had some testing time. Upstream: https://openldap.org/its/?findid=9171 Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953150 The ingredients for the crash are: 1: ppolicy overlay configured with pwdLockout: TRUE 2. smbk5pwd overlay stacked after ppolicy 3. an account locked out via pwdAccountLockedTime 4. a client binding to the locked-out account and also requesting the ppolicy control The buggy code is not as specific as the above steps, so I suspect there are probably other configurations or steps that can trigger the same crash. I will attach my test script and data for reproducing the crash. Expected output (last lines): [ ok ] Starting OpenLDAP: slapd. slapd running ldap_bind: Invalid credentials (49) slapd running Actual output (last lines): [ ok ] Starting OpenLDAP: slapd. slapd running ldap_bind: Invalid credentials (49) slapd dead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+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 1849560] Re: Please revise the files installed in /etc/
I agree the generated keys doesn't belong to /etc, while I'm not so sure about the default configuration files, as there are options that once set can't be "undone" by a config file loaded later, e.g. the Port option. -- 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/1849560 Title: Please revise the files installed in /etc/ Status in openssh package in Ubuntu: Triaged Bug description: openssh-server and openssh-client install various files under /etc: /etc/ssh/* /etc/systemd/system/sshd.service Please see if these files can be moved elsewhere, in accordance with FHS: /etc should only contain files writable by the system administrator, and in Ubuntu Core 20 we should aim to have no writable files in /etc (as it will be included in images, avoid conflict resolution on upgrades). At a glance, it looks like /etc/systemd/system/sshd.service could be moved to /lib/systemd/system, and many of the files in /etc/ssh do have suitable locations elsewhere on the system, such as /var/lib/ for generated keys, /usr/share/ for default SSH configurations, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1849560/+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 1881982] Re: DoS vulnerability: cause resource exhaustion
** Also affects: whoopsie (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Groovy) Importance: Medium Assignee: Marc Deslauriers (mdeslaur) Status: Confirmed ** Also affects: whoopsie (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: whoopsie (Ubuntu Xenial) Status: New => Confirmed ** Changed in: whoopsie (Ubuntu Bionic) Status: New => Confirmed ** Changed in: whoopsie (Ubuntu Eoan) Status: New => Confirmed ** Changed in: whoopsie (Ubuntu Focal) Status: New => Confirmed ** Changed in: whoopsie (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: whoopsie (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: whoopsie (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: whoopsie (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: whoopsie (Ubuntu Xenial) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: whoopsie (Ubuntu Bionic) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: whoopsie (Ubuntu Eoan) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: whoopsie (Ubuntu Focal) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1881982 Title: DoS vulnerability: cause resource exhaustion Status in whoopsie package in Ubuntu: Confirmed Status in whoopsie source package in Xenial: Confirmed Status in whoopsie source package in Bionic: Confirmed Status in whoopsie source package in Eoan: Confirmed Status in whoopsie source package in Focal: Confirmed Status in whoopsie source package in Groovy: Confirmed Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. # Vulnerability description The parse_report() function in whoopsie.c allows attackers to cause a denial of service (memory leak) via a crafted file. Exploitation of this issue causes excessive memory consumption which results in the Linux kernel triggering OOM killer on arbitrary process. This results in the process being terminated by the OOM killer. # Details We have found a memory leak vulnerability during the parsing the crash file, when a collision occurs on GHashTable through g_hash_table_insert(). According to [1], if the key already exists in the GHashTable, its current value is replaced with the new value. If 'key_destory_func' and 'value_destroy_func' are supplied when creating the table, the old value and the passed key are freed using that function. Unfortunately, whoopsie does not handle the old value and the passed key when collision happens. If a crash file contains same repetitive key-value pairs, it leads to memory leak as much as the amount of repetition and results in denial-of-service. [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g -hash-table-insert # PoC (*Please check the below PoC: whoopsie_killer.py) 1) Generates a certain malformed crash file that contains same repetitive key-value pairs. 2) Trigger the whoopsie to read the generated crash file. 3) After then, the whoopsie process has been killed. # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch) We should use g_hash_table_new_full() with ‘key_destroy_func’ and ‘value_destroy_func’ functions instead of g_hash_table_new(). Otherwise, before g_hash_table_insert(), we should check the collision via g_hash_table_lookup_extended() and obtain pointer to the old value and remove it. Sincerely, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 1872560] Re: integer overflow in whoopsie 0.2.69
** Also affects: whoopsie (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Groovy) Importance: High Assignee: Marc Deslauriers (mdeslaur) Status: Confirmed ** Also affects: whoopsie (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: whoopsie (Ubuntu Xenial) Status: New => Confirmed ** Changed in: whoopsie (Ubuntu Bionic) Status: New => Confirmed ** Changed in: whoopsie (Ubuntu Eoan) Status: New => Confirmed ** Changed in: whoopsie (Ubuntu Focal) Status: New => Confirmed ** Changed in: whoopsie (Ubuntu Xenial) Importance: Undecided => High ** Changed in: whoopsie (Ubuntu Bionic) Importance: Undecided => High ** Changed in: whoopsie (Ubuntu Eoan) Importance: Undecided => High ** Changed in: whoopsie (Ubuntu Focal) Importance: Undecided => High ** Changed in: whoopsie (Ubuntu Xenial) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: whoopsie (Ubuntu Bionic) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: whoopsie (Ubuntu Eoan) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: whoopsie (Ubuntu Focal) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1872560 Title: integer overflow in whoopsie 0.2.69 Status in whoopsie package in Ubuntu: Confirmed Status in whoopsie source package in Xenial: Confirmed Status in whoopsie source package in Bionic: Confirmed Status in whoopsie source package in Eoan: Confirmed Status in whoopsie source package in Focal: Confirmed Status in whoopsie source package in Groovy: Confirmed Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. ## Vulnerability in whoopsie - whoopsie 0.2.69 and earlier have a heap-based buffer overflow vulnerability. - An attacker can cause a denial of service (memory corruption and application crash) via a crafted .crash file. ## Basic When a program has been crashed, Linux system tries to create a '.crash' file on '/var/crash/' directory with python script located in '/usr/share/apport/apport'. The file contains a series of system crash information including core dump, syslog, stack trace, memory map info, etc. After the creation of '.crash' file, whoopsie extracts the above information from the '.crash' file and encodes it into binary json (bson) format. Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error Report system. ## Vulnerability Unfortunately, we have found a heap-based buffer overflow vulnerability during the encoding, when whoopsie attempts to bsonify with crafted crash file. The data in '.crash' file is stored in key-value form and the whoopsie separately measures the length of 'key' and 'value' to allocate memory region during the encoding. A heap-based buffer overflow can occur when an integer overflow happens on a variable that contains length of 'key'. FYI, a issue to that raised by 'value' is well covered by performing exception handling. @[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663] const uint32_t len = strlen( name ) + 1; - Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value. - Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file. @[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627] b->data = bson_realloc( b->data, new_size ); - Unexpected small memory region is allocated due to above integer overflow. @[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680] bson_append( b, name, len ); - Memory corruption happens when unexpected small memory region is allocated. ## Attack Scenario 1) Create a fake.crash file - '.crash' file is composed of the following format: 'key : value'. - To cause the overflow attack, the size of 'key' should be in double amount of INT32_MAX. - The size of 'value' doesn’t matter, but not zero length. $ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash $ cat fake.crash AAA … AA : B 2) Trigger the whoopsie to read the fake.crash file - Just create 'fake.upload' file by touch command. - Or launch apport-gtk gui or apport-bug cli application. 3) Check out the result - After a while, the whoopsie has been killed by segmentation fault. Sincerely, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+
[Touch-packages] [Bug 1882180] Re: DoS vulnerability: fail to allocate
Looks like this is CVE-2020-15570 ** Changed in: whoopsie (Ubuntu Xenial) Assignee: Alex Murray (alexmurray) => Marc Deslauriers (mdeslaur) ** Changed in: whoopsie (Ubuntu Bionic) Assignee: Alex Murray (alexmurray) => Marc Deslauriers (mdeslaur) ** Changed in: whoopsie (Ubuntu Eoan) Assignee: Alex Murray (alexmurray) => Marc Deslauriers (mdeslaur) ** Changed in: whoopsie (Ubuntu Focal) Assignee: Alex Murray (alexmurray) => Marc Deslauriers (mdeslaur) ** Changed in: whoopsie (Ubuntu Groovy) Assignee: Alex Murray (alexmurray) => Marc Deslauriers (mdeslaur) ** Information type changed from Private Security to Public Security ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-15570 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1882180 Title: DoS vulnerability: fail to allocate Status in whoopsie package in Ubuntu: Confirmed Status in whoopsie source package in Xenial: Confirmed Status in whoopsie source package in Bionic: Confirmed Status in whoopsie source package in Eoan: Confirmed Status in whoopsie source package in Focal: Confirmed Status in whoopsie source package in Groovy: Confirmed Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. # Vulnerability description In whoopsie 0.2.69 and earlier, there is a denial of service vulnerability in the parse_report function. A crafted input, i.e., crash report located in '/var/crash/', will lead to a denial of service attack. During the parsing of the crash report, the data length is not checked. The value of data length can be directly controlled by an input file. In the parse_report() function, the g_malloc or g_realloc is called based on data length. If we set the value of data length close to the amount of system memory, it will cause the daemon process to terminate unexpectedly, hang the system, or trigger the OOM killer. # PoC Please check the below whoopsie_killer2.py Sincerely, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1882180/+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 1872560] Re: integer overflow in whoopsie 0.2.69
https://github.com/sungjungk/apport-vuln -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1872560 Title: integer overflow in whoopsie 0.2.69 Status in whoopsie package in Ubuntu: Confirmed Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. ## Vulnerability in whoopsie - whoopsie 0.2.69 and earlier have a heap-based buffer overflow vulnerability. - An attacker can cause a denial of service (memory corruption and application crash) via a crafted .crash file. ## Basic When a program has been crashed, Linux system tries to create a '.crash' file on '/var/crash/' directory with python script located in '/usr/share/apport/apport'. The file contains a series of system crash information including core dump, syslog, stack trace, memory map info, etc. After the creation of '.crash' file, whoopsie extracts the above information from the '.crash' file and encodes it into binary json (bson) format. Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error Report system. ## Vulnerability Unfortunately, we have found a heap-based buffer overflow vulnerability during the encoding, when whoopsie attempts to bsonify with crafted crash file. The data in '.crash' file is stored in key-value form and the whoopsie separately measures the length of 'key' and 'value' to allocate memory region during the encoding. A heap-based buffer overflow can occur when an integer overflow happens on a variable that contains length of 'key'. FYI, a issue to that raised by 'value' is well covered by performing exception handling. @[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663] const uint32_t len = strlen( name ) + 1; - Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value. - Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file. @[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627] b->data = bson_realloc( b->data, new_size ); - Unexpected small memory region is allocated due to above integer overflow. @[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680] bson_append( b, name, len ); - Memory corruption happens when unexpected small memory region is allocated. ## Attack Scenario 1) Create a fake.crash file - '.crash' file is composed of the following format: 'key : value'. - To cause the overflow attack, the size of 'key' should be in double amount of INT32_MAX. - The size of 'value' doesn’t matter, but not zero length. $ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash $ cat fake.crash AAA … AA : B 2) Trigger the whoopsie to read the fake.crash file - Just create 'fake.upload' file by touch command. - Or launch apport-gtk gui or apport-bug cli application. 3) Check out the result - After a while, the whoopsie has been killed by segmentation fault. Sincerely, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1882180] Re: DoS vulnerability: fail to allocate
https://github.com/sungjungk/whoopsie_killer2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1882180 Title: DoS vulnerability: fail to allocate Status in whoopsie package in Ubuntu: Confirmed Status in whoopsie source package in Xenial: Confirmed Status in whoopsie source package in Bionic: Confirmed Status in whoopsie source package in Eoan: Confirmed Status in whoopsie source package in Focal: Confirmed Status in whoopsie source package in Groovy: Confirmed Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. # Vulnerability description In whoopsie 0.2.69 and earlier, there is a denial of service vulnerability in the parse_report function. A crafted input, i.e., crash report located in '/var/crash/', will lead to a denial of service attack. During the parsing of the crash report, the data length is not checked. The value of data length can be directly controlled by an input file. In the parse_report() function, the g_malloc or g_realloc is called based on data length. If we set the value of data length close to the amount of system memory, it will cause the daemon process to terminate unexpectedly, hang the system, or trigger the OOM killer. # PoC Please check the below whoopsie_killer2.py Sincerely, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1882180/+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 1881982] Re: DoS vulnerability: cause resource exhaustion
https://github.com/sungjungk/whoopsie_killer -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1881982 Title: DoS vulnerability: cause resource exhaustion Status in whoopsie package in Ubuntu: Confirmed Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. # Vulnerability description The parse_report() function in whoopsie.c allows attackers to cause a denial of service (memory leak) via a crafted file. Exploitation of this issue causes excessive memory consumption which results in the Linux kernel triggering OOM killer on arbitrary process. This results in the process being terminated by the OOM killer. # Details We have found a memory leak vulnerability during the parsing the crash file, when a collision occurs on GHashTable through g_hash_table_insert(). According to [1], if the key already exists in the GHashTable, its current value is replaced with the new value. If 'key_destory_func' and 'value_destroy_func' are supplied when creating the table, the old value and the passed key are freed using that function. Unfortunately, whoopsie does not handle the old value and the passed key when collision happens. If a crash file contains same repetitive key-value pairs, it leads to memory leak as much as the amount of repetition and results in denial-of-service. [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g -hash-table-insert # PoC (*Please check the below PoC: whoopsie_killer.py) 1) Generates a certain malformed crash file that contains same repetitive key-value pairs. 2) Trigger the whoopsie to read the generated crash file. 3) After then, the whoopsie process has been killed. # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch) We should use g_hash_table_new_full() with ‘key_destroy_func’ and ‘value_destroy_func’ functions instead of g_hash_table_new(). Otherwise, before g_hash_table_insert(), we should check the collision via g_hash_table_lookup_extended() and obtain pointer to the old value and remove it. Sincerely, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 1872560] Re: integer overflow in whoopsie 0.2.69
** Changed in: whoopsie (Ubuntu) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: whoopsie (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1872560 Title: integer overflow in whoopsie 0.2.69 Status in whoopsie package in Ubuntu: Confirmed Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. ## Vulnerability in whoopsie - whoopsie 0.2.69 and earlier have a heap-based buffer overflow vulnerability. - An attacker can cause a denial of service (memory corruption and application crash) via a crafted .crash file. ## Basic When a program has been crashed, Linux system tries to create a '.crash' file on '/var/crash/' directory with python script located in '/usr/share/apport/apport'. The file contains a series of system crash information including core dump, syslog, stack trace, memory map info, etc. After the creation of '.crash' file, whoopsie extracts the above information from the '.crash' file and encodes it into binary json (bson) format. Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error Report system. ## Vulnerability Unfortunately, we have found a heap-based buffer overflow vulnerability during the encoding, when whoopsie attempts to bsonify with crafted crash file. The data in '.crash' file is stored in key-value form and the whoopsie separately measures the length of 'key' and 'value' to allocate memory region during the encoding. A heap-based buffer overflow can occur when an integer overflow happens on a variable that contains length of 'key'. FYI, a issue to that raised by 'value' is well covered by performing exception handling. @[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663] const uint32_t len = strlen( name ) + 1; - Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value. - Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file. @[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627] b->data = bson_realloc( b->data, new_size ); - Unexpected small memory region is allocated due to above integer overflow. @[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680] bson_append( b, name, len ); - Memory corruption happens when unexpected small memory region is allocated. ## Attack Scenario 1) Create a fake.crash file - '.crash' file is composed of the following format: 'key : value'. - To cause the overflow attack, the size of 'key' should be in double amount of INT32_MAX. - The size of 'value' doesn’t matter, but not zero length. $ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash $ cat fake.crash AAA … AA : B 2) Trigger the whoopsie to read the fake.crash file - Just create 'fake.upload' file by touch command. - Or launch apport-gtk gui or apport-bug cli application. 3) Check out the result - After a while, the whoopsie has been killed by segmentation fault. Sincerely, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1881982] Re: DoS vulnerability: cause resource exhaustion
** Changed in: whoopsie (Ubuntu) Assignee: Alex Murray (alexmurray) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1881982 Title: DoS vulnerability: cause resource exhaustion Status in whoopsie package in Ubuntu: Confirmed Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. # Vulnerability description The parse_report() function in whoopsie.c allows attackers to cause a denial of service (memory leak) via a crafted file. Exploitation of this issue causes excessive memory consumption which results in the Linux kernel triggering OOM killer on arbitrary process. This results in the process being terminated by the OOM killer. # Details We have found a memory leak vulnerability during the parsing the crash file, when a collision occurs on GHashTable through g_hash_table_insert(). According to [1], if the key already exists in the GHashTable, its current value is replaced with the new value. If 'key_destory_func' and 'value_destroy_func' are supplied when creating the table, the old value and the passed key are freed using that function. Unfortunately, whoopsie does not handle the old value and the passed key when collision happens. If a crash file contains same repetitive key-value pairs, it leads to memory leak as much as the amount of repetition and results in denial-of-service. [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g -hash-table-insert # PoC (*Please check the below PoC: whoopsie_killer.py) 1) Generates a certain malformed crash file that contains same repetitive key-value pairs. 2) Trigger the whoopsie to read the generated crash file. 3) After then, the whoopsie process has been killed. # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch) We should use g_hash_table_new_full() with ‘key_destroy_func’ and ‘value_destroy_func’ functions instead of g_hash_table_new(). Otherwise, before g_hash_table_insert(), we should check the collision via g_hash_table_lookup_extended() and obtain pointer to the old value and remove it. Sincerely, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 1866365] Re: Missing /usr/lib/x86_64-linux-gnu/libfreetype.la file
libfreetype.la has not been packaged in libfreetype-dev since release 2.8.1-2 in February 2018. In any case, you shouldn't need it to link against FreeType 2. Looking at your Dependencies list, you're only including shared libraries needed to run programs using FreeType, not linking against it. If this is no longer an issue, I'll close this bug as invalid. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1866365 Title: Missing /usr/lib/x86_64-linux-gnu/libfreetype.la file Status in freetype package in Ubuntu: New Bug description: This file disappeared from 19.10 dev package. Without the *.la file, libtool fails to configure libraries with GTK dependencies. My work around was to grab the file from 18.04 and change the metadata for the current library versions. That allowed me to successfully compile my package with GTK dependencies. Perhaps there is some libtool/autoconf magic that I do not understand here? Please do tell me how to address this this issue if I am misunderstanding the need for the *.la file. Thanks. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libfreetype6-dev 2.9.1-4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 10:18:10 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-12 (725 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: freetype UpgradeStatus: Upgraded to eoan on 2019-12-31 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1866365/+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 1613450] Re: Small fonts xenial
Fixed upstream in FreeType 2.8+. Closing. ** Changed in: freetype (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1613450 Title: Small fonts xenial Status in freetype package in Ubuntu: Fix Released Bug description: After upgrading from trusty (and from wily too) to xenial fonts have become smaller. The screenshot http://imgur.com/a/7TR9b User with the same problem https://askubuntu.com/questions/781430/font-or-windows-scaling-changed-between-15-10-and-16-04 See also: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1547196 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1613450/+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 1464056] Re: Some characters are invisible (libreoffice/freetype) - depends on font-rendering
I can't reproduce this. Are you still seeing this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1464056 Title: Some characters are invisible (libreoffice/freetype) - depends on font-rendering Status in freetype package in Ubuntu: Confirmed Bug description: Symptom: Certain characters are not reliably displayed in LibreOffice. Which character is visible depends on font size, font face, and even mouse-over. It looks as though about 40% of the letters have been randomly made white-on-white! (This is really weird to track down, and extremely annoying!) Debugging: * I note that this affects LO, but not export to PDF. It also shows up in Abiword. * The font needs to be about 18pt or higher to show this, eg Liberation Sans, 18pt. Font-face doesn't seem to matter. * Mouse-over the text, or even changing the window size alters which letters vanish. Test case (after hours of experimenting): * Font-rendering: smoothing = None -> triggers this bug. * Font-rendering: smoothing = Greyscale -> all is well. I attach some screenshots both ways, to make this clear, showing both LO and the control panel. Toggling from one setting to the other makes the bug appear/disappear immediately. I think the root cause is in libfreetype6, but it might be in Cairo, or elsewhere. I'm using Ubuntu Wily-64 (having upgraded today from Vivid which also had the same bug) I'm running this under Ubuntu-Mate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1464056/+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 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home
So one solution to this would be to run "vgck --updatemetadata" on each vg in postinst... would there be downside to that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home Status in Ubuntu on IBM z Systems: Confirmed Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no longer mounted. During boot the console shows Timed out waiting for device /dev/mapper/s5lp8--vg-home Please see the attached dist-upgrade logs and console output for more detail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+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 1886814] Re: posix_spawn usage in gnu make causes failures on s390x
> Is this a native s390x build, or something qemu-user? Thanks. That's a very good question. The failing autopkgtest, was run on an LPAR, which is running OpenStack Nova, which launched qemu-system kvm, v5.4 Ubuntu kernel, and then run make inside that. I will double check if those old builds of make & autopkgtest reproduced the issue just on an LPAR without qemu in between. I believe they did, but don't have the logs anymore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to make-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1886814 Title: posix_spawn usage in gnu make causes failures on s390x Status in Ubuntu on IBM z Systems: New Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in make-dfsg package in Ubuntu: New Bug description: posix_spawn usage in gnu make causes failures on s390x Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it started to use posix_spawn, instead of fork()/exec(). This has caused failure of an unrelated package flatpak-builder autopkgtests on s390x only, like so echo Building make: echo: Operation not permitted make: *** [Makefile:2: all] Error 127 Julian Klaude investigated this in-depth. His earlier research also indicated that this is a heisenbug, if one tries to print to stderr before printing to stdout, no issue occurs. We are configuring GNU make to be build with --disable-posix-spawn on s390x only. We passed these details to Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=964541 too. But I do wonder, if there is something different or incorrect about posix_spawn() implementation in either glibc, or linux kernel, on s390x. Or gnu-make's usage of posix_spawn(). As otherise, using posix_spawn() in gnu-make works on other architectures, and flatpak-builder autopkgtests pass too. It seems very weird that stdout does not appear to be functional, unless stderr was opened/written to, from gnu-make execution compiled with posix-spawn feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Changed in: linux-signed (Ubuntu Groovy) Assignee: Colin Ian King (colin-king) => (unassigned) -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 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: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1886809] Re: Pulse connect VPN exists because unwanted avahi network starts
This is a ubuntu desktop. A corporate laptop. > cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback > cat /etc/network/interfaces.d/* fish: No matches for wildcard “/etc/network/interfaces.d/*”. See `help expand`. cat /etc/network/interfaces.d/* ^ > cat /etc/netplan/* # Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager As you can see this is network-manager based settings. Pulsesecure is a sort of java browser based application. Since it is a proprietary application, I'm not sure how it runs internally, but it does some basic checkings into your system to allow the connection, and establishes it. It changes all routes to use the VPN as default. Any attempt to change is detect and it considers an attempt to tamper with system, which results in connection drop. That's where the avahi causes the problem. One extra info: I set the avahi to disable on /etc/default/avahi-daemon. > cat /etc/default/avahi-daemon # 1 = Try to detect unicast dns servers that serve .local and disable avahi in # that case, 0 = Don't try to detect .local unicast dns servers, can cause # troubles on misconfigured networks AVAHI_DAEMON_DETECT_LOCAL=0 So even a patch o top of avahi-autoipd that reads this parameter can be enough to avoid this unwanted route to pop up. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1886809 Title: Pulse connect VPN exists because unwanted avahi network starts Status in avahi package in Ubuntu: New Bug description: Pulse VPNs exists very often because avahi enforces network 192.250.0.0/0 over tun0 interface. The message error is: rmon.error Unauthorized new route to 169.254.0.0/0.0.0.0 has been added (conflicts with our route to 0.0.0.0), disconnecting (routemon.cpp:598) No matter the options to skip avahi on /etc/default/avahi-daemon, it always calls /etc/network/if-up.d/avahi-autoipd and raises this discovery network. A fix can be done patching /etc/network/if-up.d/avahi-autoipd to skip any tunnel interface. --- /etc/network/if-up.d/avahi-autoipd.dpkg-old 2020-07-08 13:25:41.834569800 +0200 +++ /etc/network/if-up.d/avahi-autoipd 2020-07-07 10:07:37.68581 +0200 @@ -11,6 +11,10 @@ [ -x /usr/sbin/avahi-autoipd ] || exit 0 +case "$IFACE" in + tun*) exit 0 ;; +esac + [ "$IFACE" != "lo" ] || exit 0 case "$ADDRFAM" in inet) ;; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1886809/+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 1882248] Re: plug headset won't proper reconfig ouput to it on machine with default output
This is the debdiff for pulseaudio bionic. And because the patch is already in the eoan, focal,..., only bionic need this patch. ** Patch added: "pulseaudio_11.1-1ubuntu7.10.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1882248/+attachment/5390950/+files/pulseaudio_11.1-1ubuntu7.10.debdiff ** Description changed: + This is for pulseaudio bionic: + + [Impact] + On a Dell machine without internal spk and internal mic, after freshly + install the bionic on it, the active profile is Off, after users plug a + headset to it and users select the headset from the pop-up dialogue, + users expect the profile changes to analog-stereo (headset is on it), + but the active_profile is still Off. + + [Fix] + Upstream already has a patch to fix it, cherrypiack that patch to bionic. + And that patch is already in the eoan, focal, ... + + [Test Case] + freshly install the bionic with this patch on that dell machine, + plug headset and select the headset from UI, the profile changes to + analog-stereo, and play some sound, we could hear it from the headset + + [Regression Risk] + Low, this patch is already in the upstream for a long time, and it is + already in the eoan and focal. + + + For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. - - - target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) + target machine does not have built-in speaker, and the monitor does not + have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. ** Summary changed: - plug headset won't proper reconfig ouput to it on machine with default output + [SRU] plug headset won't proper reconfig ouput to it on machine with default output -- 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/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in linux-oem source package in Bionic: Fix Committed Status in pulseaudio source package in Bionic: New Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing
[Touch-packages] [Bug 1882248] Re: plug headset won't proper reconfig ouput to it on machine with default output
** Changed in: pulseaudio (Ubuntu Bionic) Importance: Undecided => Critical -- 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/1882248 Title: plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in linux-oem source package in Bionic: Fix Committed Status in pulseaudio source package in Bionic: New Bug description: For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+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 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS
*** This bug is a duplicate of bug 1683383 *** https://bugs.launchpad.net/bugs/1683383 Same with Kubuntu 20. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1720364 Title: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS Status in MATE Desktop: New Status in Ubuntu MATE: New Status in X.Org X server: Confirmed Status in marco package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Status in xorg-hwe-16.04 package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: marco 1.18.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Fri Sep 29 16:18:02 2017 InstallationDate: Installed on 2017-08-26 (33 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) SourcePackage: marco UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1720364/+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 1844775] Re: HDR support for Ubuntu
FWIW, There is also HDR10 tone map support in gstreamer-vaapi https://gitlab.freedesktop.org/gstreamer/gstreamer- vaapi/-/merge_requests/270 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1844775 Title: HDR support for Ubuntu Status in ffmpeg package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Status in weston package in Ubuntu: Confirmed Bug description: This is a tracker bug for getting HDR support integrated in Ubuntu. Kernel i915: - 5.3 (Ice Lake) - plus at least https://patchwork.freedesktop.org/series/65656/ - gen4+ needs https://patchwork.freedesktop.org/series/63373/ - so anything beyond initial Ice Lake support will not be in 5.4 Mesa - needs current git master plus https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942 Mutter: https://gitlab.gnome.org/GNOME/mutter/merge_requests/804 Weston: https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 1881699] Re: No analog output
Seems to share the same root cause on lp: #1875199. -- 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/1881699 Title: No analog output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+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