[Touch-packages] [Bug 1754145] Re: Pen input rotated by 90 degrees on ASUS Transformer mini T103
** Summary changed: - Pen input rotated by 90 degrees + Pen input rotated by 90 degrees on ASUS Transformer mini T103 ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1754145 Title: Pen input rotated by 90 degrees on ASUS Transformer mini T103 Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I install and Ubuntu 18.04 on a ASUS Transformer mini T103. From the beginning the boot screen is rotated by 90 degrees ccw off like it is described in this post: https://askubuntu.com/questions/1008893/ubuntu-17-10-boots-90-degrees. The login screen has than the correct orientation, but the behaviour of the ASUS Pen is the same as it is still rotated. If I tip on the upper left corner using the pen, the pointer shows up in the upper right. If I move than down, the pointer moves left. If I touch on the screen with the finger all goes right. If I turn the tablet to portrait, the screen contents switches as expected and than the pen works correctly. It seem as if there a transformation issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754145/+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 1864793] Re: a
Please explain what kind of problem you are experiencing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1864793 Title: a Status in Ubuntu: Incomplete Bug description: a ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 11:07:21 2020 DistUpgraded: 2019-11-05 10:48:27,360 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 5.3.0-29-generic, x86_64: installed nvidia, 430.50, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e0] InstallationDate: Installed on 2019-09-16 (162 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Latitude E5540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=81b7b69e-f5c3-45b1-8be9-217300cb3b27 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-05 (113 days ago) dmi.bios.date: 02/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0NHP4F dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd02/01/2018:svnDellInc.:pnLatitudeE5540:pvr00:rvnDellInc.:rn0NHP4F:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5540 dmi.product.sku: 05E0 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1864793/+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 1864793] [NEW] a
Public bug reported: a ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 11:07:21 2020 DistUpgraded: 2019-11-05 10:48:27,360 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 5.3.0-29-generic, x86_64: installed nvidia, 430.50, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e0] InstallationDate: Installed on 2019-09-16 (162 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Latitude E5540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=81b7b69e-f5c3-45b1-8be9-217300cb3b27 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-05 (113 days ago) dmi.bios.date: 02/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0NHP4F dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd02/01/2018:svnDellInc.:pnLatitudeE5540:pvr00:rvnDellInc.:rn0NHP4F:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5540 dmi.product.sku: 05E0 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan performance 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/1864793 Title: a Status in xorg package in Ubuntu: New Bug description: a ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 11:07:21 2020 DistUpgraded: 2019-11-05 10:48:27,360 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 5.3.0-29-generic, x86_64: installed nvidia, 430.50, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e0] InstallationDate: Installed on 2019-09-16 (162 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Latitude E5540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=81b7b69e-f5c3-45b1-8be9-217300cb3b27 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-05 (113 days ago) dmi.bios.date: 02/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0NHP4F dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd02/01/2018:svnDellInc.:pnLatitudeE5540:pvr00:rvnDellInc.:rn0NHP4F:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5540 dmi.product.sku: 05E0 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
[Touch-packages] [Bug 1864781] Re: Xorg freeze
It appears this bug was reported after you removed (?) the nvidia driver, which is understandable. But that also means we have no logs showing when the bug was happening. Please run these commands to help gather the system logs of previous boots so that we can try to identify what the problem was, when it was happening: journalctl -b-1 > boot-1.txt journalctl -b-2 > boot-2.txt journalctl -b-3 > boot-3.txt journalctl -b-4 > boot-4.txt journalctl -b-5 > boot-5.txt and then attach the resulting text files to this bug. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freeze + System failed to boot when nvidia-390 was installed ** Package changed: ubuntu => nvidia-graphics-drivers-390 (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1864781 Title: System failed to boot when nvidia-390 was installed Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742941] Re: zlib: improve crc32 performance on P8
** Changed in: ubuntu-power-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1742941 Title: zlib: improve crc32 performance on P8 Status in The Ubuntu-power-systems project: In Progress Status in zlib package in Ubuntu: In Progress Bug description: Calculate the checksum of data that is 16 byte aligned and a multiple of 16 bytes. The first step is to reduce it to 1024 bits. We do this in 8 parallel chunks in order to mask the latency of the vpmsum instructions. If we have more than 32 kB of data to checksum we repeat this step multiple times, passing in the previous 1024 bits. The next step is to reduce the 1024 bits to 64 bits. This step adds 32 bits of 0s to the end - this matches what a CRC does. We just calculate constants that land the data in this 32 bits. We then use fixed point Barrett reduction to compute a mod n over GF(2) for n = CRC using POWER8 instructions. We use x = 32. http://en.wikipedia.org/wiki/Barrett_reduction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864274] Re: crunchy pixels
ok, so this is:
https://gitlab.freedesktop.org/mesa/mesa/issues/2552
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #2552
https://gitlab.freedesktop.org/mesa/mesa/issues/2552
** Changed in: mesa (Ubuntu)
Status: Incomplete => Confirmed
** Also affects: mesa via
https://gitlab.freedesktop.org/mesa/mesa/issues/2552
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1864274
Title:
crunchy pixels
Status in Mesa:
Unknown
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Hello, after upgrading firefox (and many other packages) on focal
today, I've got some video artifacts in firefox.
When typing in text boxes and text fields, the new character is drawn
very slowly, pixel-by-pixel, and isn't complete until the cursor has
moved on. When larger portions of the screen are updated, it looks a
lot like the entire window is being run through a video codec or you
can see parts of the video memory from other processes. (But it looks
more deliberate and predictable than either of these descriptions.)
So far Firefox is the only application I've found that is affected.
urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.
I did get cairo package update today, but the changelog is just:
pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:15:23 +
And an xorg update:
xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:21:28 +
So I don't believe these are involved.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
(rev 07)
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 73.0.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-14-generic.
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sarnold3296 F pulseaudio
/dev/snd/controlC0: sarnold3296 F pulseaudio
BuildID: 20200217142647
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
Mixer name : 'Realtek ALC285'
Components : 'HDA:10ec0285,17aa225c,0012
HDA:8086280b,80860101,0010'
Controls : 53
Simple ctrls : 15
Card1.Amixer.info:
Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at
usb-:00:14.0-4.2.4, high speed'
Mixer name : 'USB Mixer'
Components : 'USB17ef:306f'
Controls : 9
Simple ctrls : 4
Channel: Unavailable
Date: Sat Feb 22 05:41:10 2020
ForcedLayersAccel: False
IncompatibleExtensions:
Pentadactyl - pentadac...@dactyl.googlecode.com
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100
10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1
192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric
100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:737
PrefSources: prefs.js
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET69W (1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHCTO1WW
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
[Touch-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working
I'm also having this problem after reinstalling 18.04 on the same machine and the problem didn't exist before. Here's all the details https://askubuntu.com/questions/1203558/ubuntu-18-04-intel-wireless- ac-9260-this-device-is-not-working-under-additiona -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1859308 Title: software-properties-gtk erroneously reports that Intel Wireless-AC 9260 device is not working Status in software-properties package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 (development branch), as of today, Additional Drivers (software-properties-gtk 0.98.6) reports that the device "Intel Corporation: Wireless-AC 9260" is not working, and suggests using a manually installed driver (cf. screenshot). However the device is working correctly: * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show that its driver iwlwifi is in use * ls /lib/firmware/*9260* show that the appropriate firmware files are present And I am indeed writing this bug report connected to an ac (5 GHz) wifi network, where I can verify a ~130-160 Mbps download speed, so software-properties-gtk shouldn't report the device as not working and suggest manually installing a driver. Not sure why it says so? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 00:53:43 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1859308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864781] [NEW] Xorg freeze
Public bug reported: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 bug freeze nvidia 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/1864781 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias:
[Touch-packages] [Bug 1857461] Re: package systemd 242-7ubuntu3.2 failed to install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1857461 Title: package systemd 242-7ubuntu3.2 failed to install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor Status in systemd package in Ubuntu: Expired Bug description: I cant install any package ProblemType: Package DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: libsystemd0:amd64: Configure systemd:amd64: Configure amd64-microcode:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Dec 24 14:12:10 2019 ErrorMessage: bağımlılık sorunları - yapılandırılmadan bırakılıyor InstallationDate: Installed on 2019-11-09 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTeK Computer Inc. N53SN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=0da0bcf3-cf92-40af-af14-27abd569b570 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-timesyncd.service → /usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: package systemd 242-7ubuntu3.2 failed to install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N53SN.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N53SN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53SN.204:bd02/10/2011:svnASUSTeKComputerInc.:pnN53SN:pvr1.0:rvnASUSTeKComputerInc.:rnN53SN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N53SN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857461/+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 1864778] Re: Intel Drivers Artifacts after Mesa-Dev Update
I will not provide additional data out of respect for my own privacy of which machine metal specifications I have. I will only say that I have a Mesa Intel(R) HD Graphics 530 (SKL GT2) The current build of Ubuntu with all the latest updates. A 20-intel.conf file with the following config in /etc/X11/xorg.conf.d/: Section "Device" Identifier "Intel Graphics" Driver "intel" EndSection When Option AccelMethod "uxa" is applied this bug appears to be cured. This bug with artifacts occurs when Ubuntu Base drivers are upgrading Mesa from 19.3.3-1 to 20.0.0-1. Thank you. -- 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/1864778 Title: Intel Drivers Artifacts after Mesa-Dev Update Status in mesa package in Ubuntu: New Bug description: After the update from the 20.04 LTS fresh live image from 19.3.3-1ubuntu1 to 20.0.0-1ubuntu1 mesa I get serious artifacts on startup when using the intel driver instead of modesetting. These artifacts go away when I enable Option AccelMethod "uxa" but persist if the default, "sna" or the other modes are used "none", "off", "blt". These pixels appear throughout the experience of using Ubuntu and generate in sporadic places. The font also looks completely broken. I've never had this issue before with the Intel drivers. I have Skylake HD 530. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1864778/+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 1864778] [NEW] Intel Drivers Artifacts after Mesa-Dev Update
Public bug reported: After the update from the 20.04 LTS fresh live image from 19.3.3-1ubuntu1 to 20.0.0-1ubuntu1 mesa I get serious artifacts on startup when using the intel driver instead of modesetting. These artifacts go away when I enable Option AccelMethod "uxa" but persist if the default, "sna" or the other modes are used "none", "off", "blt". These pixels appear throughout the experience of using Ubuntu and generate in sporadic places. The font also looks completely broken. I've never had this issue before with the Intel drivers. I have Skylake HD 530. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: artifacts glitch intel mesa sna visual ** Attachment added: "Artifacts from Mesa Update" https://bugs.launchpad.net/bugs/1864778/+attachment/5331029/+files/Screenshot_from_2020-02-25_20-44-41.png -- 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/1864778 Title: Intel Drivers Artifacts after Mesa-Dev Update Status in mesa package in Ubuntu: New Bug description: After the update from the 20.04 LTS fresh live image from 19.3.3-1ubuntu1 to 20.0.0-1ubuntu1 mesa I get serious artifacts on startup when using the intel driver instead of modesetting. These artifacts go away when I enable Option AccelMethod "uxa" but persist if the default, "sna" or the other modes are used "none", "off", "blt". These pixels appear throughout the experience of using Ubuntu and generate in sporadic places. The font also looks completely broken. I've never had this issue before with the Intel drivers. I have Skylake HD 530. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1864778/+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
Re: [Touch-packages] [Bug 1864274] Re: crunchy pixels
On Tue, Feb 25, 2020 at 10:16:50PM -, Timo Aaltonen wrote:
> which desktop environment?
None, I use i3wm in x11.
> probably caused by the new mesa, which now defaults to the Iris driver
> on newer Intel GPU's, you can verify this by running firefox like:
>
> "dri_driver=i965 firefox"
The artifacts still show with this version.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1864274
Title:
crunchy pixels
Status in mesa package in Ubuntu:
Incomplete
Bug description:
Hello, after upgrading firefox (and many other packages) on focal
today, I've got some video artifacts in firefox.
When typing in text boxes and text fields, the new character is drawn
very slowly, pixel-by-pixel, and isn't complete until the cursor has
moved on. When larger portions of the screen are updated, it looks a
lot like the entire window is being run through a video codec or you
can see parts of the video memory from other processes. (But it looks
more deliberate and predictable than either of these descriptions.)
So far Firefox is the only application I've found that is affected.
urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.
I did get cairo package update today, but the changelog is just:
pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:15:23 +
And an xorg update:
xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:21:28 +
So I don't believe these are involved.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
(rev 07)
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 73.0.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-14-generic.
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sarnold3296 F pulseaudio
/dev/snd/controlC0: sarnold3296 F pulseaudio
BuildID: 20200217142647
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
Mixer name : 'Realtek ALC285'
Components : 'HDA:10ec0285,17aa225c,0012
HDA:8086280b,80860101,0010'
Controls : 53
Simple ctrls : 15
Card1.Amixer.info:
Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at
usb-:00:14.0-4.2.4, high speed'
Mixer name : 'USB Mixer'
Components : 'USB17ef:306f'
Controls : 9
Simple ctrls : 4
Channel: Unavailable
Date: Sat Feb 22 05:41:10 2020
ForcedLayersAccel: False
IncompatibleExtensions:
Pentadactyl - pentadac...@dactyl.googlecode.com
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100
10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1
192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric
100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:737
PrefSources: prefs.js
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET69W (1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHCTO1WW
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1864274/+subscriptions
--
[Touch-packages] [Bug 1758529] Re: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno
** No longer affects: python-apt (Ubuntu) ** No longer affects: python-apt (Ubuntu Bionic) ** No longer affects: python-apt (Ubuntu Disco) ** No longer affects: python-apt (Ubuntu Eoan) ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1758529 Title: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno Status in Landscape Client: Fix Committed Status in landscape-client package in Ubuntu: Fix Released Status in landscape-client source package in Bionic: Fix Committed Status in landscape-client source package in Disco: Won't Fix Status in landscape-client source package in Eoan: Fix Committed Bug description: [Impact] * landscape-package-changer will output stack traces when executed with python3. This adds noise in the logs and confuse apport into thinking there was a crash, even though the error does not affect functionality. * The activity log for package operations will also show errors. * The patch overrides python-apt reporting of progress, as landscape-package-changer is never executed from a terminal. [Test Case] * register landscape-client and wait for packages to be reported. * trigger a package installation from the landscape server. * check /var/log/landscape/manager.log for Package changer warnings [Regression Potential] * The change is trivially simple. * The changed code path is only used by python-apt progress reporting. Since landscape-package-changer does not rely on it and is able to continue, other errors would likely have the same fate: that is crashing the progress reporting thread and continuing. [Original Description] Crash in the background ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: landscape-client 18.01-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 24 07:05:34 2018 ExecutablePath: /usr/bin/landscape-package-changer InstallationDate: Installed on 2015-07-04 (994 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/bin/landscape-package-changer --quiet ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonArgs: ['/usr/bin/landscape-package-changer', '--quiet'] PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SourcePackage: landscape-client Title: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apt/progress/text.py", line 164, in pulse not os.isatty(self._file.fileno())): io.UnsupportedOperation: fileno UpgradeStatus: Upgraded to bionic on 2018-03-15 (8 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1758529/+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 1864698] Re: Can't change laptop-screen brightness on Dell XPS 13 9370
** Summary changed: - Can't change laptop-screen brightness + Can't change laptop-screen brightness on Dell XPS 13 9370 ** Package changed: xorg (Ubuntu) => linux (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/1864698 Title: Can't change laptop-screen brightness on Dell XPS 13 9370 Status in linux package in Ubuntu: Confirmed Bug description: I can't change the screen brightness anymore, on a Dell XPS13. Neither the keyboard shortcuts nor gnome's sliders work. They move, but brightness remains unchanged. I first noticed this after disconnecting an external display, but I have since rebooted and the problem remains. This on Focal. I have done a series of upgrades since the original installation and I know this used to work, but I can't be sure of when exactly it stopped working. I noticed now, but it could have arisen earlier. I am pretty sure it was OK on Disco. I attach the output of lshw. Let me know what else I can provide. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 25 17:52:13 2020 DistUpgraded: 2020-02-24 18:02:48,088 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2019-01-21 (400 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=ae14977c-0724-4298-9c08-80ea948af070 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-02-24 (0 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: ricab-xps13 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864698/+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 1864679] Re: amd gpu
Thanks for the bug report. You seem to be using the 'Oibaf' PPA and describing graphics problems. This is not unusual as Oibaf is unsupported and is known to cause bugs. Please remove that PPA from your system and then report new bugs if you still have any problems. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1864679 Title: amd gpu Status in Ubuntu: Invalid Bug description: all i want to do is to get back amd gpu detect and to play steam game ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 25 23:13:47 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:9080] InstallationDate: Installed on 2020-02-20 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Sony Corporation VPCCB35FK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=9da3e7bb-f994-413c-96a6-d8aff4f5a023 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2100V2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2100V2:bd08/24/2011:svnSonyCorporation:pnVPCCB35FK:pvrC609SSM7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCCB35FK dmi.product.sku: N/A dmi.product.version: C609SSM7 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git2002250630.8a7337~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2002250730.5ab94d~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2002250730.5ab94d~oibaf~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1864679/+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 1864644] Re: I get logged out immediately after login to an X session
There's a lot of information in that log. One possible reason for this bug I can see is: Feb 25 11:06:55 tjcw-Standard-PC-i440FX-PIIX-1996 /usr/lib/gdm3/gdm-x-session[882]: (WW) qxl(0): drmSetMaster failed: Permission denied ... Feb 25 11:06:55 tjcw-Standard-PC-i440FX-PIIX-1996 /usr/lib/gdm3/gdm-x-session[882]: (EE) systemd-logind: failed to take device /dev/dri/card0: Operation not permitted Feb 25 11:06:55 tjcw-Standard-PC-i440FX-PIIX-1996 /usr/lib/gdm3/gdm-x-session[882]: (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied This means there's some kind of incompatibility between the qxl Xorg driver and the kernel. Indeed that would only be a problem for virtual machines. ** Package changed: xorg (Ubuntu) => xserver-xorg-video-qxl (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - I get logged out immediately after login to an X session + I get logged out immediately after login to an X session (QXL Xorg driver on kernel 5.4) -- 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/1864644 Title: I get logged out immediately after login to an X session (QXL Xorg driver on kernel 5.4) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: I just installed ubuntu 20.04 in a virtual machine and did 'apt-get update;apt-get upgrade' to get current (using Ctl-Alt-F2 to get a non-X session). After that, I tried logging in to a gnome session, and got logged out during login processing. This happened a few times; then I installed xfce4, rebooted, and got the same behaviour (logout during login processing) while trying to log in to an xfce session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Tue Feb 25 12:06:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-02-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=14c5cf63-466a-44d5-add6-bd5fc486c067 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-eoan dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-eoan dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864644/+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 1864683] Re: I dont no
Can you explain (in any language) what kind of problem you are experiencing? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1864683 Title: I dont no Status in Ubuntu: Incomplete Bug description: Please forgive me but I am completely overwhelmed with the English language. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Feb 25 18:28:59 2020 DistUpgraded: 2020-02-19 17:33:11,495 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0420] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0420] InstallationDate: Installed on 2018-04-19 (677 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. OptiPlex 780 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=f5f6c46b-c03c-4fdb-9bbd-bf9cac8d00b8 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-02-19 (6 days ago) dmi.bios.date: 01/21/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0C27VV dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/21/2011:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA03:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 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 Feb 19 07:48:43 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLITE-ON Technology USB NetVista Full Width Keyboard. KEYBOARD, id 8 inputPIXART USB OPTICAL MOUSE MOUSE, id 9 inputDell WMI hotkeys KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1864683/+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 1800012] Re: ogg vorbis corruption
The attachment "taglib-1.11.1-bug-864.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to taglib in Ubuntu. https://bugs.launchpad.net/bugs/1800012 Title: ogg vorbis corruption Status in taglib package in Ubuntu: Confirmed Bug description: TagLib 1.11.1 corrupts ogg vorbis files. See https://github.com/taglib/taglib/issues/775 It would be good to apply attached patch for released distributions. See upstream bugs for more details: https://github.com/taglib/taglib/issues/775 https://github.com/taglib/taglib/issues/864 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/taglib/+bug/1800012/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
About the server:
- It's certificate is valid for 2 years, and Apple has started to
rejecting any servers for which certificate is valid for more than 13
months.
- It has a SHA1withRSA certificate in its chain, which will be rejected
by all clients soon.
- It supports many weak TLSv1.2 ciphersuites
- It is susceptible to OpenSSL 0-Length attack
Please contact the administrators of said website to secure it
immediately & acquire certificate with shorter timespan and no SHA1
signatures.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in openssl package in Ubuntu:
New
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864274] Re: crunchy pixels
which desktop environment?
probably caused by the new mesa, which now defaults to the Iris driver
on newer Intel GPU's, you can verify this by running firefox like:
"dri_driver=i965 firefox"
from a terminal
** Package changed: firefox (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1864274
Title:
crunchy pixels
Status in mesa package in Ubuntu:
Incomplete
Bug description:
Hello, after upgrading firefox (and many other packages) on focal
today, I've got some video artifacts in firefox.
When typing in text boxes and text fields, the new character is drawn
very slowly, pixel-by-pixel, and isn't complete until the cursor has
moved on. When larger portions of the screen are updated, it looks a
lot like the entire window is being run through a video codec or you
can see parts of the video memory from other processes. (But it looks
more deliberate and predictable than either of these descriptions.)
So far Firefox is the only application I've found that is affected.
urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.
I did get cairo package update today, but the changelog is just:
pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:15:23 +
And an xorg update:
xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:21:28 +
So I don't believe these are involved.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
(rev 07)
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 73.0.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-14-generic.
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sarnold3296 F pulseaudio
/dev/snd/controlC0: sarnold3296 F pulseaudio
BuildID: 20200217142647
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
Mixer name : 'Realtek ALC285'
Components : 'HDA:10ec0285,17aa225c,0012
HDA:8086280b,80860101,0010'
Controls : 53
Simple ctrls : 15
Card1.Amixer.info:
Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at
usb-:00:14.0-4.2.4, high speed'
Mixer name : 'USB Mixer'
Components : 'USB17ef:306f'
Controls : 9
Simple ctrls : 4
Channel: Unavailable
Date: Sat Feb 22 05:41:10 2020
ForcedLayersAccel: False
IncompatibleExtensions:
Pentadactyl - pentadac...@dactyl.googlecode.com
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100
10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1
192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric
100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:737
PrefSources: prefs.js
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET69W (1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHCTO1WW
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1864274/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 1864274] [NEW] crunchy pixels
You have been subscribed to a public bug:
Hello, after upgrading firefox (and many other packages) on focal today,
I've got some video artifacts in firefox.
When typing in text boxes and text fields, the new character is drawn
very slowly, pixel-by-pixel, and isn't complete until the cursor has
moved on. When larger portions of the screen are updated, it looks a lot
like the entire window is being run through a video codec or you can see
parts of the video memory from other processes. (But it looks more
deliberate and predictable than either of these descriptions.)
So far Firefox is the only application I've found that is affected.
urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.
I did get cairo package update today, but the changelog is just:
pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:15:23 +
And an xorg update:
xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
-- Matthias Klose Sat, 08 Feb 2020 11:21:28 +
So I don't believe these are involved.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
(rev 07)
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 73.0.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic.
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sarnold3296 F pulseaudio
/dev/snd/controlC0: sarnold3296 F pulseaudio
BuildID: 20200217142647
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
Mixer name : 'Realtek ALC285'
Components : 'HDA:10ec0285,17aa225c,0012
HDA:8086280b,80860101,0010'
Controls : 53
Simple ctrls : 15
Card1.Amixer.info:
Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4,
high speed'
Mixer name : 'USB Mixer'
Components : 'USB17ef:306f'
Controls : 9
Simple ctrls : 4
Channel: Unavailable
Date: Sat Feb 22 05:41:10 2020
ForcedLayersAccel: False
IncompatibleExtensions:
Pentadactyl - pentadac...@dactyl.googlecode.com
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100
10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1
192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric
100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:737
PrefSources: prefs.js
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET69W (1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHCTO1WW
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: amd64 apport-bug champagne focal
--
crunchy pixels
https://bugs.launchpad.net/bugs/1864274
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to mesa in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800012] Re: ogg vorbis corruption
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: taglib (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to taglib in Ubuntu. https://bugs.launchpad.net/bugs/1800012 Title: ogg vorbis corruption Status in taglib package in Ubuntu: Confirmed Bug description: TagLib 1.11.1 corrupts ogg vorbis files. See https://github.com/taglib/taglib/issues/775 It would be good to apply attached patch for released distributions. See upstream bugs for more details: https://github.com/taglib/taglib/issues/775 https://github.com/taglib/taglib/issues/864 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/taglib/+bug/1800012/+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 1800012] Re: ogg vorbis corruption
This bug makes ogg files unusable and may destroy entire music collections. Fixing of this bug is highly neccessary -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to taglib in Ubuntu. https://bugs.launchpad.net/bugs/1800012 Title: ogg vorbis corruption Status in taglib package in Ubuntu: Confirmed Bug description: TagLib 1.11.1 corrupts ogg vorbis files. See https://github.com/taglib/taglib/issues/775 It would be good to apply attached patch for released distributions. See upstream bugs for more details: https://github.com/taglib/taglib/issues/775 https://github.com/taglib/taglib/issues/864 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/taglib/+bug/1800012/+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 1834875] Re: cloud-init growpart race with udev
This bug was fixed in the package cloud-initramfs-tools - 0.45ubuntu1 --- cloud-initramfs-tools (0.45ubuntu1) focal; urgency=medium * Add dependency on flock for growroot's use of growpart. (LP: #1834875) -- Scott Moser Tue, 25 Feb 2020 13:08:22 -0500 ** Changed in: cloud-initramfs-tools (Ubuntu) Status: Confirmed => Fix Released -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Fix Released Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
The browsers will require SECLEVEL=2 from April 2020, the change in
libraries has already landed.
You can override this via command-line, a system config file, or a local
config file + environment variable pointing to it.
On Ubuntu 20.04 LTS:
man SSL_CTX_get_security_level.3ssl
does have:
--
Level 2
On Ubuntu, TLS versions below 1.2 are not permitted.
NOTES
The default security level can be configured when OpenSSL is compiled by
setting -DOPENSSL_TLS_SECURITY_LEVEL=level. On Ubuntu, 2 is used.
--
In addition to having TLSv1.2 min, DTLSv1.2 min, bigger keys ie 2048 bit
RSA, we are still to land requirement to reject SHA1 signatures on
certs.
This is an intentional change.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in openssl package in Ubuntu:
New
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742941] Re: zlib: improve crc32 performance on P8
** Changed in: zlib (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1742941 Title: zlib: improve crc32 performance on P8 Status in The Ubuntu-power-systems project: Triaged Status in zlib package in Ubuntu: In Progress Bug description: Calculate the checksum of data that is 16 byte aligned and a multiple of 16 bytes. The first step is to reduce it to 1024 bits. We do this in 8 parallel chunks in order to mask the latency of the vpmsum instructions. If we have more than 32 kB of data to checksum we repeat this step multiple times, passing in the previous 1024 bits. The next step is to reduce the 1024 bits to 64 bits. This step adds 32 bits of 0s to the end - this matches what a CRC does. We just calculate constants that land the data in this 32 bits. We then use fixed point Barrett reduction to compute a mod n over GF(2) for n = CRC using POWER8 instructions. We use x = 32. http://en.wikipedia.org/wiki/Barrett_reduction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742941/+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
Re: [Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev
On Tue, Feb 25, 2020 at 2:35 PM Scott Moser wrote: > this seemed to "just work" for me. > http://paste.ubuntu.com/p/93dWDPZfZT/ Ah, I didn't check that there was an existing ubuntu/devel branch. Sorry. I've pushed a MR here: https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379851 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1834875 > > Title: > cloud-init growpart race with udev > > To manage notifications about this bug go to: > https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions > -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1834875] Re: cloud-init growpart race with udev
** Merge proposal linked: https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379851 -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864708] [NEW] Mount unit fails but systemctl status shows success
Public bug reported: I have this mount unit # cat /etc/systemd/system/srv-cctvstore.mount [Unit] Description=Drive for CCTVstore [Mount] What=/dev/disk/by-id/ata-ST2000NM0011_Z1P21NQ7-part1 Where=/srv/cctvstore Type=ext4 Options=defaults [Install] WantedBy=multi-user.target On boot systemd thinks it is mounted: $ systemctl status srv-cctvstore.mount ● srv-cctvstore.mount - Drive for CCTVstore Loaded: loaded (/etc/systemd/system/srv-cctvstore.mount; enabled; vendor preset: enabled) Active: active (mounted) since Tue 2020-02-25 22:37:16 SAST; 48s ago Where: /srv/cctvstore What: /dev/sda1 Process: 1294 ExecMount=/bin/mount /dev/disk/by-id/ata-ST2000NM0011_Z1P21NQ7-part1 /srv/cctvstore -t ext4 -o defaults (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/srv-cctvstore.mount Feb 25 22:37:16 kluis systemd[1]: Mounting Drive for CCTVstore... Feb 25 22:37:16 kluis systemd[1]: Mounted Drive for CCTVstore. and the mount command seems to agree $ mount | grep cctv /dev/sda1 on /srv/cctvstore type ext4 (rw,relatime) but the mountpoint is empty: $ ls -al /srv/cctvstore/ total 1 drwxr-xr-x 2 root root 2 Dec 7 22:51 . drwxr-xr-x 4 root root 4 Dec 7 22:51 .. and umount thinks it is not mounted: $ sudo umount /srv/cctvstore [sudo] password for johann: umount: /srv/cctvstore: not mounted. journalctl doesn't report any funnies: $ journalctl -u srv-cctvstore.mount -- Logs begin at Tue 2020-02-25 22:37:16 SAST, end at Tue 2020-02-25 22:41:43 SAST. -- Feb 25 22:37:16 kluis systemd[1]: Mounting Drive for CCTVstore... Feb 25 22:37:16 kluis systemd[1]: Mounted Drive for CCTVstore. but mounting by hand works: $ sudo mount /dev/sda1 /srv/cctvstore johann@kluis:~$ ls -al /srv/cctvstore total 3157 drwxrwxrwx 7 root root 4096 Dec 9 22:27 . drwxr-xr-x 4 root root 4 Dec 7 22:51 .. drwxr-xr-x 14 165569 1655694096 Dec 10 23:10 events drwxr-xr-x 2 165569 1655694096 Dec 7 22:59 images drwxr-xr-x 2 165569 1655694096 Dec 7 23:01 logs drwx-- 2 root root 16384 Dec 7 22:47 lost+found drwxrwxr-x 2 165569 165569 3194880 Feb 25 22:25 mlevents I am unsure where to go next, any help appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 Date: Tue Feb 25 22:27:59 2020 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-5.3.0-40-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: E3C232D2I dmi.board.vendor: ASRockRack dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/07/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnE3C232D2I:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2020-01-08T12:29:15.304369 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1864708 Title: Mount unit fails but systemctl status shows success Status in systemd package in Ubuntu: New Bug description: I have this mount unit # cat /etc/systemd/system/srv-cctvstore.mount [Unit] Description=Drive for CCTVstore [Mount] What=/dev/disk/by-id/ata-ST2000NM0011_Z1P21NQ7-part1 Where=/srv/cctvstore Type=ext4 Options=defaults [Install] WantedBy=multi-user.target On boot systemd thinks it is mounted: $ systemctl status srv-cctvstore.mount ● srv-cctvstore.mount - Drive for CCTVstore Loaded: loaded (/etc/systemd/system/srv-cctvstore.mount; enabled; vendor preset: enabled) Active: active (mounted) since Tue 2020-02-25 22:37:16 SAST; 48s ago Where: /srv/cctvstore What: /dev/sda1 Process: 1294 ExecMount=/bin/mount /dev/disk/by-id/ata-ST2000NM0011_Z1P21NQ7-part1
[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev
this seemed to "just work" for me. http://paste.ubuntu.com/p/93dWDPZfZT/ -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1864561] Re: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1864561 Title: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event Status in gtk+3.0 package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: If the keypress event contains GDK_HYPER_MASK as a modifier, gtk_im_context_filter_keypress() returns true, reporting that the IM handled the event, even though it did not, therefore it should return false. Background: We are working on modifying Gnome-Terminal / libvte-2.91.so.0 to enable Terminal-bespoke remapping of modifier keys. This is to facilitate OS X users to migrate to Ubuntu. (Discussion here: #220. Background and unsuccessful alternative approaches detailed here: https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/README.md). When we replace GDK_CONTROL_MASK by GDK_HYPER_MASK, the input method (ibus) reports that it handled the event that had Hyper as the modifier. When we use export GTK_IM_MODULE=xim, the Hyper modifier is passed as expected. We believe that this is a bug in ibus XOR gtk. Unfortunately I'm not sure whether this is an issue in ibus or gtk, so I'm reporting it in both places (as well as upstream). Apologies for the inconvenience caused by this. Many thanks for looking at this. I'll track updates here https://gitlab.gnome.org/GNOME/gnome-terminal/issues/220 and here https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/Building%20a%20Gnome-Hyper-Terminal.md so that people compinging Gnonme Terminal are aware of the status. Many thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1864561/+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 1864562] Re: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event
*** This bug is a duplicate of bug 1864561 *** https://bugs.launchpad.net/bugs/1864561 Thanks for reporting. I don't know whether gtk or ibus is causing this issue, but I've taken the liberty of marking a single issue as affecting both packages. That makes it easier to keep the discussion in one place. :) ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 1864561 For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1864562 Title: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event Status in Ubuntu: New Bug description: If the keypress event contains GDK_HYPER_MASK as a modifier, gtk_im_context_filter_keypress() returns true, reporting that the IM handled the event, even though it did not, therefore it should return false. Background: We are working on modifying Gnome-Terminal / libvte-2.91.so.0 to enable Terminal-bespoke remapping of modifier keys. This is to facilitate OS X users to migrate to Ubuntu. (Discussion here: #220. Background and unsuccessful alternative approaches detailed here: https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/README.md). When we replace GDK_CONTROL_MASK by GDK_HYPER_MASK, the input method (ibus) reports that it handled the event that had Hyper as the modifier. When we use export GTK_IM_MODULE=xim, the Hyper modifier is passed as expected. We believe that this is a bug in ibus XOR gtk. Unfortunately I'm not sure whether this is an issue in ibus or gtk, so I'm reporting it in both places (as well as upstream). Apologies for the inconvenience caused by this. Many thanks for looking at this. I'll track updates here https://gitlab.gnome.org/GNOME/gnome-terminal/issues/220 and here https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/Building%20a%20Gnome-Hyper-Terminal.md so that people compinging Gnonme Terminal are aware of the status. Many thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1864562/+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 1864698] [NEW] Can't change laptop-screen brightness
Public bug reported: I can't change the screen brightness anymore, on a Dell XPS13. Neither the keyboard shortcuts nor gnome's sliders work. They move, but brightness remains unchanged. I first noticed this after disconnecting an external display, but I have since rebooted and the problem remains. This on Focal. I have done a series of upgrades since the original installation and I know this used to work, but I can't be sure of when exactly it stopped working. I noticed now, but it could have arisen earlier. I am pretty sure it was OK on Disco. I attach the output of lshw. Let me know what else I can provide. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 25 17:52:13 2020 DistUpgraded: 2020-02-24 18:02:48,088 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2019-01-21 (400 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=ae14977c-0724-4298-9c08-80ea948af070 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-02-24 (0 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: ricab-xps13 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal regression reproducible third-party-packages ubuntu ** Attachment added: "Output from lshw" https://bugs.launchpad.net/bugs/1864698/+attachment/5330946/+files/lshw.out -- 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/1864698 Title: Can't change laptop-screen brightness Status in xorg package in Ubuntu: New Bug description: I can't change the screen brightness anymore, on a Dell XPS13. Neither the keyboard shortcuts nor gnome's sliders work. They move, but brightness remains unchanged. I first noticed this after disconnecting an external display, but I have since rebooted and the problem remains. This on Focal. I have done a series of upgrades since the original installation and I know this used to work, but I can't be sure of when exactly it stopped working. I noticed now, but it could have arisen earlier. I am pretty sure it was OK on Disco. I attach the output of lshw. Let me know what else I can provide. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 25 17:52:13 2020 DistUpgraded: 2020-02-24 18:02:48,088 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation
[Touch-packages] [Bug 1668944] Re: The _apt user ignores group membership.
Dropping all secondary groups is standard security practice for sandboxing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1668944 Title: The _apt user ignores group membership. Status in apt package in Ubuntu: Invalid Bug description: Actually I had the same problem described in http://askubuntu.com/questions/773955/apt-get-ssl-client-certificate-not-working-on-16-04-error-while-reading-file I want to use client certificates with apt. But I don't want to make them world readable in order to make apt working. So I created a group 'ssl-cert' and changed the group ownership of the ssl cert files to match this group. I also added the _apt user to the ssl-cert group. Then I tried to open these files as user '_apt' in bash (su -s /bin/bash _apt) which works well. But if I run: "apt-get -o "Debug::Acquire::https=true" update" I still get the following error: * error reading ca cert file /etc/certs/mycert/ca.pem (Error while reading file.) * Closing connection 26 So my guess is that apt somehow ignores the ssl-cert membership. Possible workarounds: - make ssl client cert world readable - change owner ssl client cert to _apt - change main group of _apt user from 'nogroup' to 'ssl-cert' - set APT::Sandbox::User "root"; in apt.conf.d Neither of them is pretty. Maybe this is a wanted behavior, then just suggest how to fix the issue in nice way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1668944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864423] Re: Failed test 'default log is not used' with new procps 3.3.16-1
This bug was fixed in the package postgresql-common - 213 --- postgresql-common (213) unstable; urgency=medium [ Christian Ehrhardt ] * t/020_create_sql_remove.t: fix file clear with procps 3.16. (LP: #1864423) [ Christoph Berg ] * pg_lsclusters: List clusters even if the corresponding PostgreSQL binaries are missing; include "binaries_missing" in status column. (Salsa #13) * Reload systemd on install since we don't do that automatically via dh_installinit. Problem reported by velix, thanks! (Salsa #12) * debian/maintscripts-functions: Save full bin and lib dirs on catversion bump. Problem reported by Komzzpa, thanks! (Salsa #9) * debian/maintscripts-functions: Suppress errors from pg_controldata, the control file might be missing if the cluster was pg_upgraded. Spotted by Michael Banck, thanks! (Salsa #6) * pg_wrapper: Reword docs to better describe clusters on the local system. Reported by James Coleman, thanks! (Closes: #950149) * pg_wrapper: Document that `ALTER SYSTEM SET port` will interact badly with cluster selection. (Closes: #919385) -- Christoph Berg Mon, 24 Feb 2020 16:20:14 +0100 ** Changed in: postgresql-common (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1864423 Title: Failed test 'default log is not used' with new procps 3.3.16-1 Status in postgresql-common package in Ubuntu: Fix Released Status in procps package in Ubuntu: New Bug description: Since the new procps upload procps | 2:3.3.16-1ubuntu1 | focal-proposed | source, amd64, arm64, armhf, i386, ppc64el, s390x the tests of postgresql-common fail. The issues are: autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - results - - - - - - - - - - run-testsuiteFAIL non-zero exit status 2 autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - stderr - - - - - - - - - - # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 143. # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 154. # Looks like you failed 2 tests of 144. It was retried a few times by different people now and reproduced so we can assume it is a real issues for now. I was running two VMs to compare: $ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --test-name=run-testsuite --apt-pocket=proposed=src:procps --shell postgresql-common_211.dsc -- qemu --qemu-options='-cpu host' --ram-size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img (and the other one without --apt-pocket=proposed=src:procps) The issue reproduced locally in only the one with the new procps. In Debian the latest similar run is https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-common/4279031/log.gz https://ci.debian.net/data/packages/testing/amd64/p/postgresql-common/4279031.log But that is pre-3.3.16 and I wasn't able to find their result with the same combination. Lets mark this bug update-excuse and check if we can find anything in these VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
Aha! `curl -v --ciphers 'DEFAULT:@SECLEVEL=1' https://www.toodledo.com/`
works but `curl -v --ciphers 'DEFAULT:@SECLEVEL=2'
https://www.toodledo.com/` fails.
According to
https://www.openssl.org/docs/man1.1.0/man3/SSL_CTX_get_security_level.html,
the default security level for the library is 1 if it isn't specified at
compile time. Has Canonical made a decision to set a higher security
level by default?
Oh, wait, it appears that yes it has. `openssl version -a` says
`-DOPENSSL_TLS_SECURITY_LEVEL=2`.
It appears that this was an intentional change? I question the
advisability of this, especially since it doesn't appear that there's
any way to override it in a configuration file (is there?).
I am not sure it is advisable for command-line tools in the OS to have
stricter security level requirements than users' browsers?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in openssl package in Ubuntu:
New
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
I may be misunderstanding something, but as far as I can tell this is
not a cipher mismatch problem.
According to
https://www.ssllabs.com/ssltest/analyze.html?d=www.toodledo.com, the
site supports TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256. According to
"openssl ciphers", openssl supports ECDHE-RSA-AES128-GCM-SHA256, which
apperas to be the same thing. But `curl -v --ciphers ECDHE-RSA-AES128
-GCM-SHA256 --tlsv1.2 --tls-max 1.2 https://www.toodledo.com/` still
fails.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in openssl package in Ubuntu:
New
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
Example output:
jik@jik-x1:~$ curl -v https://www.toodledo.com/
* Trying 146.20.52.175:443...
* TCP_NODELAY set
* Connected to www.toodledo.com (146.20.52.175) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS alert, handshake failure (552):
* error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake
failure
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in openssl package in Ubuntu:
New
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864689] [NEW] openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
Public bug reported:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will be
able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal wayland-session
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in openssl package in Ubuntu:
New
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864683] [NEW] I dont no
Public bug reported: Please forgive me but I am completely overwhelmed with the English language. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Feb 25 18:28:59 2020 DistUpgraded: 2020-02-19 17:33:11,495 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0420] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0420] InstallationDate: Installed on 2018-04-19 (677 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. OptiPlex 780 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=f5f6c46b-c03c-4fdb-9bbd-bf9cac8d00b8 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-02-19 (6 days ago) dmi.bios.date: 01/21/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0C27VV dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/21/2011:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA03:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 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 Feb 19 07:48:43 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLITE-ON Technology USB NetVista Full Width Keyboard. KEYBOARD, id 8 inputPIXART USB OPTICAL MOUSE MOUSE, id 9 inputDell WMI hotkeys KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1864683 Title: I dont no Status in xorg package in Ubuntu: New Bug description: Please forgive me but I am completely overwhelmed with the English language. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Feb 25 18:28:59 2020 DistUpgraded: 2020-02-19 17:33:11,495 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0420] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0420] InstallationDate: Installed on 2018-04-19 (677 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. OptiPlex 780 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=f5f6c46b-c03c-4fdb-9bbd-bf9cac8d00b8 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-02-19 (6 days ago) dmi.bios.date: 01/21/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0C27VV dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1856366] Re: PCI/internal sound card not detected on a Swift SF314-57
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1856366 Title: PCI/internal sound card not detected on a Swift SF314-57 Status in alsa-driver package in Ubuntu: Confirmed Bug description: No sound card detected with kernel 5.5.0-050500rc1-generic 1. Description: Ubuntu 19.10 Release: 19.10 2. linux-image- unsigned-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb 3. have at least one soundcard 4. cat /proc/asound/cards reports: --- no soundcards --- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.5.0-050500rc1-generic x86_64 NonfreeKernelModules: hda_intel ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 22:09:17 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T20:34:57.551680 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668944] Re: The _apt user ignores group membership.
Dictating to people what their PKI policy should be is outside the scope of apt. Apt must behave properly as per standard unix behaviour, with a proper working user and a proper working group. Trying to dictate directory permissions to people breaks automation, breaks orchestration, and makes it really hard to convince people to do security properly. Please fix this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1668944 Title: The _apt user ignores group membership. Status in apt package in Ubuntu: Invalid Bug description: Actually I had the same problem described in http://askubuntu.com/questions/773955/apt-get-ssl-client-certificate-not-working-on-16-04-error-while-reading-file I want to use client certificates with apt. But I don't want to make them world readable in order to make apt working. So I created a group 'ssl-cert' and changed the group ownership of the ssl cert files to match this group. I also added the _apt user to the ssl-cert group. Then I tried to open these files as user '_apt' in bash (su -s /bin/bash _apt) which works well. But if I run: "apt-get -o "Debug::Acquire::https=true" update" I still get the following error: * error reading ca cert file /etc/certs/mycert/ca.pem (Error while reading file.) * Closing connection 26 So my guess is that apt somehow ignores the ssl-cert membership. Possible workarounds: - make ssl client cert world readable - change owner ssl client cert to _apt - change main group of _apt user from 'nogroup' to 'ssl-cert' - set APT::Sandbox::User "root"; in apt.conf.d Neither of them is pretty. Maybe this is a wanted behavior, then just suggest how to fix the issue in nice way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1668944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev
** Patch added: "debdiff showing the changes to upload to fix the bug." https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5330894/+files/cloud-utils_0.31-6_to_0.31-7.debdiff -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1834875] Re: cloud-init growpart race with udev
** Attachment added: "tarball of source package to upload" https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5330895/+files/cloud-utils_0.31-7-gd99b2d76-source.tar.xz -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1834875] Re: cloud-init growpart race with udev
@Scott, cloud-utils isn't quite new-upstream-snapshot out of the box; the debian dir does not contain the changelog; however, I think I've got this sorted out. I've a MP I can put up; but it only will show the add of the changelog file. I'll attach a debdiff and a source package. -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1864679] [NEW] amd gpu
Public bug reported: all i want to do is to get back amd gpu detect and to play steam game ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 25 23:13:47 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:9080] InstallationDate: Installed on 2020-02-20 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Sony Corporation VPCCB35FK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=9da3e7bb-f994-413c-96a6-d8aff4f5a023 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2100V2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2100V2:bd08/24/2011:svnSonyCorporation:pnVPCCB35FK:pvrC609SSM7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCCB35FK dmi.product.sku: N/A dmi.product.version: C609SSM7 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git2002250630.8a7337~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2002250730.5ab94d~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2002250730.5ab94d~oibaf~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance third-party-packages 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/1864679 Title: amd gpu Status in xorg package in Ubuntu: New Bug description: all i want to do is to get back amd gpu detect and to play steam game ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 25 23:13:47 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:9080] InstallationDate: Installed on 2020-02-20 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Sony Corporation VPCCB35FK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=9da3e7bb-f994-413c-96a6-d8aff4f5a023 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2100V2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2100V2:bd08/24/2011:svnSonyCorporation:pnVPCCB35FK:pvrC609SSM7:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCCB35FK dmi.product.sku: N/A dmi.product.version: C609SSM7 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git2002250630.8a7337~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2002250730.5ab94d~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2002250730.5ab94d~oibaf~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package zoneminder - 1.32.3-2ubuntu1 --- zoneminder (1.32.3-2ubuntu1) focal; urgency=medium * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) * d/rules: override build-dep to fix FTBFS (thanks to robie.ba...@canonical.com) (LP: #1863793, Closes: #951600) * MySQL8 runtime fixes (LP: #1859295): - d/p/mysql8-password-deprecated.patch: password() is deprecated - d/p/mysql8-reserved-keywords.patch: quote MySQL8 reserved keywords - d/p/mysql8-replace-password-call.patch: replace password() * d/README.Debian: quick update for MySQL8 and Focal -- Andreas Hasenack Tue, 25 Feb 2020 10:22:20 -0300 ** Changed in: zoneminder (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: Fix Committed Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: Fix Released Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: Fix Released Status in gnunet package in Ubuntu: Fix Released Status in hoel package in Ubuntu: Fix Released Status in isc-kea package in Ubuntu: Fix Released Status in jabberd2 package in Ubuntu: Fix Released Status in kannel package in Ubuntu: Fix Released Status in libgda5 package in Ubuntu: Fix Released Status in libodb-mysql package in Ubuntu: Fix Released Status in lyricue package in Ubuntu: Fix Released Status in motion package in Ubuntu: Fix Released Status in mysql-8.0 package in Ubuntu: Fix Released Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: Fix Released Status in opendnssec package in Ubuntu: Fix Released Status in opensmtpd-extras package in Ubuntu: Fix Released Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: Fix Released Status in pvpgn package in Ubuntu: Fix Released Status in qt4-x11 package in Ubuntu: Fix Released Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: Fix Released Status in tntdb package in Ubuntu: Fix Released Status in voms-mysql-plugin package in Ubuntu: Fix Released Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: Fix Released Status in zoneminder package in Ubuntu: Fix Released Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856428] Re: Disable TLS below 1.2 by default
** Changed in: openssl (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1856428 Title: Disable TLS below 1.2 by default Status in gnutls28 package in Ubuntu: Fix Released Status in golang-1.13 package in Ubuntu: New Status in nss package in Ubuntu: Fix Released Status in openssl package in Ubuntu: Fix Released Bug description: Disable TLS 1.0, TLS1.1, DTLS1.0 As part of focal commitment, we shall disable obsolete protocols by default. Users can override this behaviour with a config file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1856428/+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 1834875] Re: cloud-init growpart race with udev
a.) I gave the wrong link. ugh. It should have been: https://code.launchpad.net/~smoser/cloud-initramfs-tools/+git/cloud-initramfs-tools/+merge/379774 b.) the fixed link to 'a' probably makes more sense now. But basically you need a newer cloud-initramfs-tools to adjust for the fact that growpart needs flock now. cloud-initramfs-tools I believe is still a "native package". So it just has the packaging along side c.) you can use new-upstream-snapshot. cloud-utils is set to use the same basic workflow as cloud-init or curtin. I'm OK to upload cloud-initramfs-tools and also cloud-utils, but I think in both cases it makes sense to get someone from server team to do it. Just to have someone other than myself having done it. -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+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 1834875] Re: cloud-init growpart race with udev
@smoser a looks merged b has not had any changes since 2018 and looks up-to-date in Focal. What am I missing? c I see a devel branch, is it assumed that it uses a packaging structure similar to cloud-init or can someone just grab and upload master? -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. An example is provided, followed by a complete procedure to reproduce the issue. Affected container distributions Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo systemd 240-6ubuntu5.8: OK, not affected Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Example steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu
[Touch-packages] [Bug 1854237] Re: autopkgtests fail after security fixes
Looking good, I'll accept this into eoan-proposed - but please, before we actually release it to eoan-updates, can you add a Regression Potential section to this bug at least? The test fixes touch more than just test-code, so this change can (in the unlikely case) introduce some unrelated regressions. Thanks! ** Changed in: apport (Ubuntu Eoan) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1854237 Title: autopkgtests fail after security fixes Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Bionic: New Status in apport source package in Disco: New Status in apport source package in Eoan: Fix Committed Bug description: The following autopkgtests fail after the recent security fixes: log:FAIL: test_get_logind_session (__main__.T) log:FAIL: test_core_dump_packaged (__main__.T) log:FAIL: test_core_dump_unpackaged (__main__.T) log:FAIL: test_crash_setuid_drop (__main__.T) log:FAIL: test_crash_setuid_keep (__main__.T) log:FAIL: test_crash_setuid_nonwritable_cwd (__main__.T) log:FAIL: test_lock_symlink (__main__.T) test_get_logind_session is a test failing to keep up with an API change. test_core_dump_* is failures to remove partly written core files. Both of these are easy fixes, I'll have a MP for them soon. test_crash_setuid_* are caused by the dropping of privileges when accessing the crashing process's /proc. They seem to be testing behaviour now explicitly forbidden by the fix to be honest! test_lock_symlink fails because the lock file is now always in /var/lock/apport/ and not in $APPORT_REPORT_DIR. I guess we could update the test, but is it really worth it after the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1854237/+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 1854237] Please test proposed package
Hello Michael, or anyone else affected, Accepted apport into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu8.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1854237 Title: autopkgtests fail after security fixes Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Bionic: New Status in apport source package in Disco: New Status in apport source package in Eoan: Fix Committed Bug description: The following autopkgtests fail after the recent security fixes: log:FAIL: test_get_logind_session (__main__.T) log:FAIL: test_core_dump_packaged (__main__.T) log:FAIL: test_core_dump_unpackaged (__main__.T) log:FAIL: test_crash_setuid_drop (__main__.T) log:FAIL: test_crash_setuid_keep (__main__.T) log:FAIL: test_crash_setuid_nonwritable_cwd (__main__.T) log:FAIL: test_lock_symlink (__main__.T) test_get_logind_session is a test failing to keep up with an API change. test_core_dump_* is failures to remove partly written core files. Both of these are easy fixes, I'll have a MP for them soon. test_crash_setuid_* are caused by the dropping of privileges when accessing the crashing process's /proc. They seem to be testing behaviour now explicitly forbidden by the fix to be honest! test_lock_symlink fails because the lock file is now always in /var/lock/apport/ and not in $APPORT_REPORT_DIR. I guess we could update the test, but is it really worth it after the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1854237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report
Hello errors.ubuntu.com, or anyone else affected, Accepted apport into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu8.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apport (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1848064 Title: /usr/share/apport/whoopsie-upload- all:PermissionError:/usr/share/apport/whoopsie-upload- all@168:collect_info:process_report Status in apport package in Ubuntu: Fix Released Status in apport source package in Eoan: Fix Committed Bug description: [Impact] whoopsie-upload-all is not collecting data for existing crash reports which are not owned by root if /proc/sys/fs/protected_regular is set to 1. Subsequently, the crash reports are incomplete and not getting uploaded to the Error Tracker therefore Ubuntu developers may be missing out on important crash reports. [Test Case] 1) Confirm /proc/sys/fs/protected_regular is set to 1. 2) Run an application as your user and cause it to crash. (kill -11 $APP) 3) Confirm there is a crash report in /var/crash 4) Run 'sudo /usr/share/apport/whoopsie-upload-all' 5) Observe the Traceback in this bug report is produced by whoopsie-upload-all. With the version of apport from -proposed the Traceback will not occur and a .uploaded file will be created for the corresponding .crash file. [Regression Potential] Not all systems may have /proc/sys/fs/protected_regular set to 1, so we should also test the case where /proc/sys/fs/protected_regular is set to 0. This can be done by manually changing the value and running through the test case above and confirming that a .uploaded file is created for the .crash file. Original Description The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1848064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. An example is provided, followed by a complete procedure to reproduce the issue. Affected container distributions Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo systemd 240-6ubuntu5.8: OK, not affected Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Example steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. - Affected distributions - == - - Bionic Beaver systemd 237-3ubuntu10.38: OK + A complete procedure to reproduce the issue is available below. + + Affected container distributions + + + Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected + Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY - Disco Dingo 240-6ubuntu5.8: OK - Eoan Ermine systemd 242-7ubuntu3.6: OK + Disco Dingo systemd 240-6ubuntu5.8: OK, not affected + Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3
[Touch-packages] [Bug 1864423] Re: Failed test 'default log is not used' with new procps 3.3.16-1
Tests are all good now, things should migrate once britney gets to them ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1864423 Title: Failed test 'default log is not used' with new procps 3.3.16-1 Status in postgresql-common package in Ubuntu: In Progress Status in procps package in Ubuntu: New Bug description: Since the new procps upload procps | 2:3.3.16-1ubuntu1 | focal-proposed | source, amd64, arm64, armhf, i386, ppc64el, s390x the tests of postgresql-common fail. The issues are: autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - results - - - - - - - - - - run-testsuiteFAIL non-zero exit status 2 autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - stderr - - - - - - - - - - # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 143. # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 154. # Looks like you failed 2 tests of 144. It was retried a few times by different people now and reproduced so we can assume it is a real issues for now. I was running two VMs to compare: $ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --test-name=run-testsuite --apt-pocket=proposed=src:procps --shell postgresql-common_211.dsc -- qemu --qemu-options='-cpu host' --ram-size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img (and the other one without --apt-pocket=proposed=src:procps) The issue reproduced locally in only the one with the new procps. In Debian the latest similar run is https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-common/4279031/log.gz https://ci.debian.net/data/packages/testing/amd64/p/postgresql-common/4279031.log But that is pre-3.3.16 and I wasn't able to find their result with the same combination. Lets mark this bug update-excuse and check if we can find anything in these VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I have the absolutely same issue on Dell Inspiron 7590. Internel Mic is not shown in the input devices list. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: - In all our unprivileged LXC containers running Bionic Beaver, installing - systemd 237-3ubuntu10.39 results in losing network configuration. + In all our LXC containers running Bionic Beaver, installing systemd + 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. A complete procedure to reproduce the issue is here: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/6 - Affected distributions: + Affected distributions + == Bionic Beaver systemd 237-3ubuntu10.38: OK Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo 240-6ubuntu5.8: OK Eoan Ermine systemd 242-7ubuntu3.6: OK Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY - - Hosts: - - Debian Buster - default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel - - Example container network configuration: + + Affected hosts + == + + Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 + kernel + + Example host bridge configuration + = + + 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 + inet 127.0.0.1/8 scope host lo +valid_lft forever preferred_lft forever + inet6 ::1/128 scope host +valid_lft forever preferred_lft forever + 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 + link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff + 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 + link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff + 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 + link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff + inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 +valid_lft forever preferred_lft forever + inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 +valid_lft forever preferred_lft forever + inet6 fe80::225:90ff:fe2b:f160/64 scope link +valid_lft forever preferred_lft forever + + Example container network configuration + === lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 - Steps to reproduce, inside the container: + Steps to reproduce, inside the container + root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu
[Touch-packages] [Bug 1864644] Re: I get logged out immediately after login to an X session
I just downloaded today's build of Focal Fossa (25 Feb 2020, sha256sum 7cdae20c68d9fb1854024ee5e77cee00dfb6e27b9502be6bc15ff5a050b0d259 ) and got the same problem. This is probably specific to running in a virtual machine; I am using the virt-manager in Ubuntu 19.10 up-to-date as of 25 Feb 2020; since if it happened on real hardware then everyone trying Focal Fossa would run into the problem. -- 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/1864644 Title: I get logged out immediately after login to an X session Status in xorg package in Ubuntu: New Bug description: I just installed ubuntu 20.04 in a virtual machine and did 'apt-get update;apt-get upgrade' to get current (using Ctl-Alt-F2 to get a non-X session). After that, I tried logging in to a gnome session, and got logged out during login processing. This happened a few times; then I installed xfce4, rebooted, and got the same behaviour (logout during login processing) while trying to log in to an xfce session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Tue Feb 25 12:06:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-02-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=14c5cf63-466a-44d5-add6-bd5fc486c067 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-eoan dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-eoan dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. A complete procedure to reproduce the issue is here: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/6 Affected distributions: Bionic Beaver systemd 237-3ubuntu10.38: OK Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo 240-6ubuntu5.8: OK Eoan Ermine systemd 242-7ubuntu3.6: OK Eoan Ermine systemd 242-7ubuntu3.7: BUGGY - + Focal Fossa systemd 244.2-1ubuntu1: BUGGY + Hosts: Debian Buster default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Setting up libsystemd0:amd64 (237-3ubuntu10.39) ... Setting up systemd (237-3ubuntu10.39) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.39) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.39) ... Processing triggers for dbus (1.12.2-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group
[Touch-packages] [Bug 1864644] [NEW] I get logged out immediately after login to an X session
Public bug reported: I just installed ubuntu 20.04 in a virtual machine and did 'apt-get update;apt-get upgrade' to get current (using Ctl-Alt-F2 to get a non-X session). After that, I tried logging in to a gnome session, and got logged out during login processing. This happened a few times; then I installed xfce4, rebooted, and got the same behaviour (logout during login processing) while trying to log in to an xfce session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Tue Feb 25 12:06:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-02-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=14c5cf63-466a-44d5-add6-bd5fc486c067 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-eoan dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-eoan dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal reproducible single-occurrence 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/1864644 Title: I get logged out immediately after login to an X session Status in xorg package in Ubuntu: New Bug description: I just installed ubuntu 20.04 in a virtual machine and did 'apt-get update;apt-get upgrade' to get current (using Ctl-Alt-F2 to get a non-X session). After that, I tried logging in to a gnome session, and got logged out during login processing. This happened a few times; then I installed xfce4, rebooted, and got the same behaviour (logout during login processing) while trying to log in to an xfce session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Tue Feb 25 12:06:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-02-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[Touch-packages] [Bug 1864644] Re: I get logged out immediately after login to an X session
Here is the output from 'journalctl'. I think it shows X11 taking a SIGABRT (signal 6) but I cannot find any X11 log files in /var/log . My next tack will be to try installing a new version of ubuntu 20.04 . ** Attachment added: "Output of 'journalctl' on the affected virtual machine" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864644/+attachment/5330866/+files/jc.log -- 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/1864644 Title: I get logged out immediately after login to an X session Status in xorg package in Ubuntu: New Bug description: I just installed ubuntu 20.04 in a virtual machine and did 'apt-get update;apt-get upgrade' to get current (using Ctl-Alt-F2 to get a non-X session). After that, I tried logging in to a gnome session, and got logged out during login processing. This happened a few times; then I installed xfce4, rebooted, and got the same behaviour (logout during login processing) while trying to log in to an xfce session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Tue Feb 25 12:06:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-02-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=14c5cf63-466a-44d5-add6-bd5fc486c067 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-eoan dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-eoan dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864644/+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 1760190] Re: Useless icon themes installed
Is this issue going anywhere? ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1760190 Title: Useless icon themes installed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Humanity-Dark LoginIcons Ubuntu-mono-dark Ubuntu-mono-light Hicolor if i switch icons from these icons nothing happening. I think these icons are no longer used in ubuntu. And DMZ-Black, DMZ-White listing in icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1760190/+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 1864638] [NEW] e-cal-recur: Incorrect timezone used for DTEND from DURATION
Public bug reported: Recurring events from CalDAV with DTSTART and DURATION but no DTEND get incorrect timezone for the end time. Reported upstream: https://gitlab.gnome.org/GNOME/evolution-data-server/issues/194 And fixed: https://gitlab.gnome.org/GNOME/evolution-data- server/-/commit/80072aea88235e1cfe2223d8d5c7d9605700a71f I'd love to see this backported to 18.04. The equivalent patch against 3.28.5 should just be: --- evolution-data-server-3.28.5.orig/src/calendar/libecal/e-cal-recur.c +++ evolution-data-server-3.28.5/src/calendar/libecal/e-cal-recur.c @@ -206,6 +206,8 @@ ensure_timezone (icalcomponent *comp, if (!prop) prop = icalcomponent_get_first_property (comp, prop_kind); + if (!prop && prop_kind == ICAL_DTEND_PROPERTY) + prop = icalcomponent_get_first_property (comp, ICAL_DTSTART_PROPERTY); if (!prop) return TRUE; (I've been running this patch for a week and it seems to be working great). ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1864638 Title: e-cal-recur: Incorrect timezone used for DTEND from DURATION Status in evolution-data-server package in Ubuntu: New Bug description: Recurring events from CalDAV with DTSTART and DURATION but no DTEND get incorrect timezone for the end time. Reported upstream: https://gitlab.gnome.org/GNOME/evolution-data-server/issues/194 And fixed: https://gitlab.gnome.org/GNOME/evolution-data- server/-/commit/80072aea88235e1cfe2223d8d5c7d9605700a71f I'd love to see this backported to 18.04. The equivalent patch against 3.28.5 should just be: --- evolution-data-server-3.28.5.orig/src/calendar/libecal/e-cal-recur.c +++ evolution-data-server-3.28.5/src/calendar/libecal/e-cal-recur.c @@ -206,6 +206,8 @@ ensure_timezone (icalcomponent *comp, if (!prop) prop = icalcomponent_get_first_property (comp, prop_kind); + if (!prop && prop_kind == ICAL_DTEND_PROPERTY) + prop = icalcomponent_get_first_property (comp, ICAL_DTSTART_PROPERTY); if (!prop) return TRUE; (I've been running this patch for a week and it seems to be working great). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1864638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. A complete procedure to reproduce the issue is here: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/6 - + + Affected distributions: + + Bionic Beaver systemd 237-3ubuntu10.38: OK + Bionic Beaver systemd 237-3ubuntu10.39: BUGGY + Disco Dingo 240-6ubuntu5.8: OK + Eoan Ermine systemd 242-7ubuntu3.6: OK + Eoan Ermine systemd 242-7ubuntu3.7: BUGGY + Hosts: Debian Buster default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Setting up libsystemd0:amd64 (237-3ubuntu10.39) ... Setting up systemd (237-3ubuntu10.39) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.39) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.39) ... Processing triggers for dbus (1.12.2-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
same behavior here! systemd 237-3ubuntu10.38 -> IPV4 Adress after start of lxc-Container, everything OK systemd 237-3ubuntu10.39 -> NO IPV4 Adress in Container after lxc-start Host: Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 Container: Ubuntu 18.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. A complete procedure to reproduce the issue is here: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/6 Hosts: Debian Buster default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Setting up libsystemd0:amd64 (237-3ubuntu10.39) ... Setting up systemd (237-3ubuntu10.39) ... Setting up libnss-systemd:amd64 (237-3ubuntu10.39) ... Setting up libpam-systemd:amd64 (237-3ubuntu10.39) ... Processing triggers for dbus (1.12.2-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd
[Touch-packages] [Bug 1848202] Autopkgtest regression report (glib2.0/2.62.4-1~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.4-1~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: openssh/1:8.0p1-6build1 (i386, ppc64el, amd64, arm64, s390x, armhf) openjdk-8/unknown (amd64, armhf) libreoffice/unknown (i386) dbus-python/unknown (armhf) modemmanager-qt/unknown (amd64) graphene/1.10.0-1 (arm64) firefox/73.0+build3-0ubuntu0.19.10.1 (arm64) gvfs/1.42.1-1ubuntu1 (arm64) cmake-extras/1.3+17.04.20170310-5 (armhf) glib2.0/2.62.4-1~ubuntu19.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1848202 Title: Use after free in gdbus leads to eds segfaults Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/b1f62616406e36e521fd1fb1d2be4ac2fe9a2cda contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. [ Fix ] This bug was fixed upstream in 2.62.2 (see the links below). That update is being issues to eoan. [ QA ] Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't need to explicitly test that this bug is fixed. Nevertheless, to verify this bug please give the desktop a good workout. Ideally install the SRU and use your machine as you would normally for a variety of tasks. Make sure there are no regressions. [ Regression potential ] 1) The changes involve mutexes and stuff, which is error prone. 2) It's GLib, a core library, so any bad regressions will be really serious for the desktop as a whole. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1848202/+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 1844853] Autopkgtest regression report (glib2.0/2.62.4-1~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.4-1~ubuntu19.10.1) for
eoan have finished running.
The following regressions have been reported in tests triggered by the package:
openssh/1:8.0p1-6build1 (i386, ppc64el, amd64, arm64, s390x, armhf)
openjdk-8/unknown (amd64, armhf)
libreoffice/unknown (i386)
dbus-python/unknown (armhf)
modemmanager-qt/unknown (amd64)
graphene/1.10.0-1 (arm64)
firefox/73.0+build3-0ubuntu0.19.10.1 (arm64)
gvfs/1.42.1-1ubuntu1 (arm64)
cmake-extras/1.3+17.04.20170310-5 (armhf)
glib2.0/2.62.4-1~ubuntu19.10.1 (i386)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#glib2.0
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no longer works in Qt applications after upgrade
Status in GLib:
Fix Released
Status in ibus:
Fix Released
Status in glib2.0 package in Ubuntu:
Fix Released
Status in ibus package in Ubuntu:
Fix Released
Status in glib2.0 source package in Xenial:
Fix Committed
Status in glib2.0 source package in Bionic:
Fix Committed
Status in glib2.0 source package in Disco:
Fix Committed
Status in glib2.0 source package in Eoan:
Fix Committed
Status in glib2.0 source package in Focal:
Fix Released
Status in ibus source package in Focal:
Fix Released
Status in glib2.0 package in Debian:
Fix Released
Bug description:
[Impact]
IBus was broken for Qt applications as a regression due to the fix of
CVE-2019-14822. As a result the IBus patch was disabled temporarily,
which fixed IBus from a usability POV.
The real fix has been made in glib2.0, and the updates in -proposed
will allow the IBus patch to be re-enabled.
[Test Case]
* On a standard Ubuntu {eoan,disco,bionic,xenial} installation
- Upgrade the glib2.0 packages from
{eoan,disco,bionic,xenial}-proposed
- Upgrade the ibus packages from
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
- Install some IBus input method, e.g. ibus-libpinyin
- Install some Qt application, e.g. Kate
* Relogin (maybe reboot)
* Add the input method to the input sources
* Open the Qt app and try to input something using the IBus IM
=> Find that the transliteration works as expected
[Regression Potential]
The applicable patches origin from glib upstream:
https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
Consequently the changes have been reviewed by the glib maintainer, but also
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.
[Original description]
Kubuntu Release 18.04.3 LTS
Expected behavior:
ibus continues working as before after applying security update
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
Observed behavior:
ibus is not usable anymore in Qt applications.
After updating ibus and the related packages ibus-gtk, ibus-gtk3,
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using
shift-space no longer changes the selected input method and even when i switch
to the mozc input method in a gtk application, i can not use it in any Qt
applications.
When starting qtconfig in a terminal, I also get the following message:
Bus::open: Connect ibus failed!
IBusInputContext::createInputContext: no connection to ibus-daemon
This bug was not present in version 1.5.17-3ubuntu5 and I also
confirmed that downgrading the packages to version 1.5.17-3ubuntu4
restores ibus functionality in Qt applications.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu5.1
ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 21 07:58:56 2019
InstallationDate: Installed on 2019-06-28 (84 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+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 1850932] Autopkgtest regression report (glib2.0/2.62.4-1~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.4-1~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: openssh/1:8.0p1-6build1 (i386, ppc64el, amd64, arm64, s390x, armhf) openjdk-8/unknown (amd64, armhf) libreoffice/unknown (i386) dbus-python/unknown (armhf) modemmanager-qt/unknown (amd64) graphene/1.10.0-1 (arm64) firefox/73.0+build3-0ubuntu0.19.10.1 (arm64) gvfs/1.42.1-1ubuntu1 (arm64) cmake-extras/1.3+17.04.20170310-5 (armhf) glib2.0/2.62.4-1~ubuntu19.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850932 Title: [SRU] Backport 2.62.4-1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.4-1 from focal. One purpose of this backport is to fix bug #1844853. But there are several other changes. Here's the diff of NEWS: +Overview of changes in GLib 2.62.4 +== + +* Apply recursion depth limits to variants in D-Bus messages (!1290) + +* Bugs fixed: + - #1938 GDateTime doesn't support leap seconds + - !1240 Backport !1233 “gdatetime: Handle leap seconds in ISO8601 dates” +to glib-2-62 + - !1257 Backport !1232 “kqueue: Do not return early from _kqsub_cancel” +to glib-2-62 + - !1266 Backport !1265 “build: don't check for protected visibility” to +glib-2-62 + - !1276 Backport !1274 “trash portal: Don't follow symlinks” to glib-2-62 + - !1290 Backport !1201 “gdbusmessage: Limit recursion of variants in +D-Bus messages” to glib-2-62 + +Overview of changes in GLib 2.62.3 +== + +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject to + FD limits (#954) + +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917) + +* Bugs fixed: + - #954 The g_spawn_sync() function uses select() which has limitations + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type '(null)' in cast to 'GDBusServer' + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7 + - #1903 use-after-free in mimeapps test causes intermittent segfault during testing + - #1916 objcopy not used from cross-compilation file in GIO tests + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and new GCC + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62 + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to glib-2-62 + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62` + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62 + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by kdeinit5” to glib-2-62 + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1 + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error” + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring events” to glib-2-62 + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” to glib-2-62 + + +Overview of changes in GLib 2.62.2 +== + +* Bugs fixed: + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a dedicated thread + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” to glib-2-62 + - !1156 Backport !1146 Solaris fixes to glib-2-62 This release can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME There are patches from the upstream master branch rather than this stable release: + Add-a-test-for-GDBusServer-authentication.patch + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch + Make-ld-executable-configurable.patch They are sensible backports which I hope are appropriate for SRU. [ QA ] The testsuite fixes will verify themselves during the build and autopkgtest. For the rest of the fixes, please exercise the desktop thoroughly. Log in, log out, run many applications and make sure there are no regressions. [ Regression potential ] test fixes> Build failures or autopkgtest failures. GLib is a central desktop library. Regressions could break any part of the desktop - so QA is important,
[Touch-packages] [Bug 1863590] Re: Chrony test hangs with libpcap2 1:2.31-1
** Bug watch added: Debian Bug tracker #951577 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951577 ** Also affects: bubblewrap (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951577 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1863590 Title: Chrony test hangs with libpcap2 1:2.31-1 Status in chrony package in Ubuntu: Confirmed Status in libcap2 package in Ubuntu: New Status in bubblewrap package in Debian: Unknown Status in libcap2 package in Debian: Fix Released Bug description: Tests are blocking and failing eventually with a timeout. Hits all architectures and is reproducible. Locally reproducible in autopkgtest: sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built- binaries --apt-upgrade --apt-pocket=proposed=src:libpcap2 --shell-fail chrony_3.5-5ubuntu1.dsc -- qemu --qemu-options='-cpu host' --ram- size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img Seems to be a block on network on __skb_wait_for_more_packets $cat /proc/3833/wchan __skb_wait_for_more_packets From strace POV that is a wait in accept that does not unblock: $ sudo strace -rT -p 3833 strace: Process 3833 attached 0.00 accept(6, NULL, NULL The logs are no help: /tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-stderr => empty /tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-stdout => matches the console $ cat /tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-stdout make: Entering directory '/tmp/autopkgtest.epy1pq/autopkgtest_tmp' cc -O2 -Wall -g -fPIC -c -o client.o client.c cc -O2 -Wall -g -fPIC -shared -o clknetsim.so client.o -ldl -lm g++ -O2 -Wall -g -fPIC -c -o clock.o clock.cc g++ -O2 -Wall -g -fPIC -c -o node.o node.cc g++ -O2 -Wall -g -fPIC -c -o generator.o generator.cc g++ -O2 -Wall -g -fPIC -c -o network.o network.cc g++ -O2 -Wall -g -fPIC -c -o server.o server.cc g++ -O2 -Wall -g -fPIC -c -o stats.o stats.cc g++ -O2 -Wall -g -fPIC -o clknetsim clock.o node.o generator.o network.o server.o stats.o make: Leaving directory '/tmp/autopkgtest.epy1pq/autopkgtest_tmp' 001-defaults Noisy PS output: 4 0 506 1 20 0 2600 1920 - Ss ttyS1 0:00 /bin/sh 1 03690 506 20 0 2600 128 - S+ ttyS1 0:00 \_ /bin/sh 4 036913690 20 0 8172 3660 - S+ ttyS1 0:00 \_ su -s /bin/bash ubuntu -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2>&1 || true; buildtree="/tmp/autopkgtest.epy1pq/build.KhE/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-artifacts"; export AUTOPKGTEST_ARTIFA CTS="/tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest.epy1pq/autopkgtest_tmp"; export AUTOP KGTEST_TMP="/tmp/autopkgtest.epy1pq/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pi d; set -C; echo $$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod +x /tmp/autopkgtest.epy1pq/build.KhE/src/debian/ tests/upstream-simulation-test-suite; touch /tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-stdout /tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-stderr; /tmp/autopkgtest.epy1 pq/build.KhE/src/debian/tests/upstream-simulation-test-suite 2> >(tee -a /tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-stderr >&2) > >(tee -a /tmp/autopkgtest.epy1pq/upstream-simula tion-test-suite-stdout); 4 100037203691 20 0 8608 3852 do_wai Ss ? 0:00 \_ bash -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true; . ~/.profile >/dev/null 2> &1 || true; buildtree="/tmp/autopkgtest.epy1pq/build.KhE/src"; mkdir -p -m 1777 -- "/tmp/autopkgtest.epy1pq/upstream-simulation-test-suite-artifacts"; export AUTOPKGTEST_ARTIFACTS="/tmp/auto pkgtest.epy1pq/upstream-simulation-test-suite-artifacts"; export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 "/tmp/autopkgtest.epy1pq/autopkgtest_tmp"; export AUTOPKGTEST_TMP="/t mp/autopkgtest.epy1pq/autopkgtest_tmp"; export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE LC_C TYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS
[Touch-packages] [Bug 1863733] Re: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later
** Bug watch added: Debian Bug tracker #951577 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951577 ** Also affects: bubblewrap (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951577 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1863733 Title: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later Status in bubblewrap package in Ubuntu: New Status in libcap2 package in Ubuntu: New Status in bubblewrap package in Debian: Unknown Bug description: The bubblewrap upstream-as-root test started failing after libcap2 1:2.31-1 got synced from Debian. The same failure can be seen with 1:2.32-1. I have reproduced the issue locally on focal - when using the focal-proposed version, the aforementioned test fails, where with the release version (1:2.27-1) it passes. It seems to fail here already: bwrap --bind / / --tmpfs /tmp --as-pid-1 --cap-drop CAP_KILL --cap-drop CAP_FOWNER --unshare-pid capsh --print assert_not_file_has_content caps.test '^Current: =.*cap_kill' It looks like the requested caps did not get dropped, as the logs show that both cap_kill and cap_fowner are still there. This is only for the upstream-as-root test, i.e. executing tests/test-run.sh as root. This might be an issue with bubblewrap, but seeing that it all works fine with the release version, it all feels weird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1863733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
** Description changed: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. + A complete procedure to reproduce the issue is here: + https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/6 + Hosts: Debian Buster - custom 5.3.9, 5.4.8 or 5.4.13 kernel + default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: - Installed: 237-3ubuntu10.38 - Candidate: 237-3ubuntu10.39 - Version table: - 237-3ubuntu10.39 500 - 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - *** 237-3ubuntu10.38 500 - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 100 /var/lib/dpkg/status - 237-3ubuntu10 500 - 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installed: 237-3ubuntu10.38 + Candidate: 237-3ubuntu10.39 + Version table: + 237-3ubuntu10.39 500 + 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + *** 237-3ubuntu10.38 500 + 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 100 /var/lib/dpkg/status + 237-3ubuntu10 500 + 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 - link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 - inet 127.0.0.1/8 scope host lo -valid_lft forever preferred_lft forever - inet6 ::1/128 scope host -valid_lft forever preferred_lft forever + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 + inet 127.0.0.1/8 scope host lo + valid_lft forever preferred_lft forever + inet6 ::1/128 scope host + valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 - link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 - inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 -valid_lft forever preferred_lft forever - inet6 ::x:xx::x:/128 scope global -valid_lft forever preferred_lft forever - inet6 ::xx::/64 scope link -valid_lft forever preferred_lft forever + link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 + inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 + valid_lft forever preferred_lft forever + inet6 ::x:xx::x:/128 scope global + valid_lft forever preferred_lft forever + inet6 ::xx::/64 scope link + valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: - libnss-systemd libpam-systemd libsystemd0 + libnss-systemd libpam-systemd libsystemd0 Suggested packages: - systemd-container policykit-1 + systemd-container policykit-1 The following packages will be upgraded: - libnss-systemd libpam-systemd libsystemd0 systemd + libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack
[Touch-packages] [Bug 1864423] Re: Failed test 'default log is not used' with new procps 3.3.16-1
FYI: - postgresql-common itself had a flaky test on armhf (re-started) and should migrate soon (everything else is good) - I triggered the procps tests with the new postgresql-common @Steve - thanks for picking up the cleanup of the fs.protected_regular setting on procps itself -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1864423 Title: Failed test 'default log is not used' with new procps 3.3.16-1 Status in postgresql-common package in Ubuntu: In Progress Status in procps package in Ubuntu: New Bug description: Since the new procps upload procps | 2:3.3.16-1ubuntu1 | focal-proposed | source, amd64, arm64, armhf, i386, ppc64el, s390x the tests of postgresql-common fail. The issues are: autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - results - - - - - - - - - - run-testsuiteFAIL non-zero exit status 2 autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - stderr - - - - - - - - - - # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 143. # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 154. # Looks like you failed 2 tests of 144. It was retried a few times by different people now and reproduced so we can assume it is a real issues for now. I was running two VMs to compare: $ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --test-name=run-testsuite --apt-pocket=proposed=src:procps --shell postgresql-common_211.dsc -- qemu --qemu-options='-cpu host' --ram-size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img (and the other one without --apt-pocket=proposed=src:procps) The issue reproduced locally in only the one with the new procps. In Debian the latest similar run is https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-common/4279031/log.gz https://ci.debian.net/data/packages/testing/amd64/p/postgresql-common/4279031.log But that is pre-3.3.16 and I wasn't able to find their result with the same combination. Lets mark this bug update-excuse and check if we can find anything in these VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864623] [NEW] apt-get attempts to download Packages.xz which is not InRelease and does not exist
Public bug reported:
When trying to install the latest virtualbox-6.0 from virtualbox.org, we
got a failure:
Err:1 http://download.virtualbox.org/virtualbox/debian xenial/contrib amd64
virtualbox-6.0 amd64 6.0.16-135674~Ubuntu~xenial
404 Not Found
E: Failed to fetch
http://download.virtualbox.org/virtualbox/debian/pool/contrib/v/virtualbox-6.0/virtualbox-6.0_6.0.16-135674~Ubuntu~xenial_amd64.deb
404 Not Found
We expected that this was a case of `apt-get update` not having been run before
`apt-get install`, but turns out it's a bit more interesting:
apt-get update fetched the following files:
ubuntu@ubuntu:~$ apt-get --print-uris update |grep virtualbox
'http://download.virtualbox.org/virtualbox/debian/dists/xenial/InRelease'
download.virtualbox.org_virtualbox_debian_dists_xenial_InRelease 0
'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/binary-amd64/Packages.xz'
download.virtualbox.org_virtualbox_debian_dists_xenial_contrib_binary-amd64_Packages
0
'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/binary-all/Packages.xz'
download.virtualbox.org_virtualbox_debian_dists_xenial_contrib_binary-all_Packages
0
'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/i18n/Translation-en.xz'
download.virtualbox.org_virtualbox_debian_dists_xenial_contrib_i18n_Translation-en
0
http://download.virtualbox.org/virtualbox/debian/dists/xenial/InRelease
returns 200 and lists a bunch of Packages lists. However, it does *not*
list contrib/binary-amd64/Packages.xz, only:
- contrib/binary-amd64/Packages
- contrib/binary-amd64/Packages.gz
- contrib/binary-amd64/Packages.bz2
For some reason, apt still attempts to download the .xz files, and does
not even report an error for them!
Trying to download the file locally, I get a 404, but with an HTML error
page as the content:
$ curl -v
'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/binary-amd64/Packages.xz'
| head -n 20
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0*
Trying 2.22.40.42...
* TCP_NODELAY set
* Connected to download.virtualbox.org (2.22.40.42) port 80 (#0)
> GET /virtualbox/debian/dists/xenial/contrib/binary-amd64/Packages.xz HTTP/1.1
> Host: download.virtualbox.org
> User-Agent: curl/7.58.0
> Accept: */*
>
0 00 00 0 0 0 --:--:-- 0:00:02 --:--:-- 0<
HTTP/1.1 404 Not Found
< Accept-Ranges: bytes
< Content-Type: text/html
< ETag: "477d9862374177c810b0b7d73b4f1e53:1531792454.541174"
< Last-Modified: Wed, 31 Aug 2011 20:28:54 GMT
< Server: AkamaiNetStorage
< Content-Length: 7073
< Date: Tue, 25 Feb 2020 09:08:16 GMT
< Connection: keep-alive
<
{ [7073 bytes data]
100 7
Error Page 404
http://download.oracle.com/index.html; />
I think it's a bug that:
a) apt tries to download Packages files not listed in InRelease
b) apt does not report errors on 404 it gets when downloading them
It is of course possible that apt get a *different* InRelease and a
*different* response when trying to download the .xz files, but that
seems unlikely. If you want to, I can try to confirm the actual network
traffic.
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1864623
Title:
apt-get attempts to download Packages.xz which is not InRelease and
does not exist
Status in apt package in Ubuntu:
New
Bug description:
When trying to install the latest virtualbox-6.0 from virtualbox.org,
we got a failure:
Err:1 http://download.virtualbox.org/virtualbox/debian xenial/contrib amd64
virtualbox-6.0 amd64 6.0.16-135674~Ubuntu~xenial
404 Not Found
E: Failed to fetch
http://download.virtualbox.org/virtualbox/debian/pool/contrib/v/virtualbox-6.0/virtualbox-6.0_6.0.16-135674~Ubuntu~xenial_amd64.deb
404 Not Found
We expected that this was a case of `apt-get update` not having been run
before `apt-get install`, but turns out it's a bit more interesting:
apt-get update fetched the following files:
ubuntu@ubuntu:~$ apt-get --print-uris update |grep virtualbox
'http://download.virtualbox.org/virtualbox/debian/dists/xenial/InRelease'
download.virtualbox.org_virtualbox_debian_dists_xenial_InRelease 0
'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/binary-amd64/Packages.xz'
download.virtualbox.org_virtualbox_debian_dists_xenial_contrib_binary-amd64_Packages
0
'http://download.virtualbox.org/virtualbox/debian/dists/xenial/contrib/binary-all/Packages.xz'
download.virtualbox.org_virtualbox_debian_dists_xenial_contrib_binary-all_Packages
0
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
Here is a full procedure to reproduce the issue. Set-up == 1. Install an amd64 Debian Buster (default network install), 2. install lxc and create a bionic amd64 container, ```bash apt install lxc lxc-create -t download -n bionic lxc-start -n bionic ``` 3. inside the container, deactivate dhcp (dhcp4: false )in `/etc/netplan/10-lxc.yaml`, and install the systemd packages without the bug, ```bash lxc-attach -n bionic sed -i 's/true/false/' /etc/netplan/10-lxc.yaml apt install systemd=237-3ubuntu10.38 libsystemd0=237-3ubuntu10.38 libnss-systemd=237-3ubuntu10.38 libpam-systemd=237-3ubuntu10.38 exit ``` 4. create a bridge on the host with a static IP and deactivate dhcp, in `/etc/network/interfaces`, ``` # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback ## The primary network interface #allow-hotplug ens18 #iface ens18 inet dhcp ## This is an autoconfigured IPv6 interface #iface ens18 inet6 auto iface ens18 inet manual auto br0 iface br0 inet static address 192.168.1.168 netmask 255.255.255.0 gateway 192.168.1.220 bridge_ports ens18 bridge_stp off bridge_waitport 0 bridge_fd 0 ``` 5. on the host, modify the network configuration of the container to use the bridge with a static IP in `/var/lib/lxc/bionic/config`, ``` # Template used to create this container: /usr/share/lxc/templates/lxc-download # Parameters passed to the template: # Template script checksum (SHA-1): 273c51343604eb85f7e294c8da0a5eb769d648f3 # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware this has security implications) # Distribution configuration lxc.include = /usr/share/lxc/config/common.conf # For Ubuntu 14.04 lxc.mount.entry = /sys/kernel/debug sys/kernel/debug none bind,optional 0 0 lxc.mount.entry = /sys/kernel/security sys/kernel/security none bind,optional 0 0 lxc.mount.entry = /sys/fs/pstore sys/fs/pstore none bind,optional 0 0 lxc.mount.entry = mqueue dev/mqueue mqueue rw,relatime,create=dir,optional 0 0 lxc.arch = linux64 # Container specific configuration lxc.apparmor.profile = generated lxc.apparmor.allow_nesting = 1 lxc.rootfs.path = dir:/var/lib/lxc/bionic/rootfs lxc.uts.name = bionic ## Network configuration #lxc.net.0.type = empty # Network configuration lxc.net.0.type = veth lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.1.220 lxc.net.0.ipv4.address = 192.168.1.169/32 ``` 6. reboot the host. ```bash reboot ``` Let’s do it === 1. Start the container and check the IP config, which should be ok, ```bash lxc-start -n bionic lxc-attach -n bionic ip a ``` 2. upgrade the system and check the IP config, the static is gone. ```bash apt upgrade ip a exit ``` If systemd is downgraded again to 237-3ubuntu10.38, the IP is back at the next reboot of the container. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. A complete procedure to reproduce the issue is here: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/6 Hosts: Debian Buster default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
