[Touch-packages] [Bug 1890515] Re: ubuntu-bug blah.crash file gives errors that imply it wasn't submitted
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1890515 ** Tags added: iso-testing -- 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/1890515 Title: ubuntu-bug blah.crash file gives errors that imply it wasn't submitted Status in apport package in Ubuntu: New Bug description: Unclear messages on `ubuntu-bug /var/crash/blah.crash` on i386 live qa-test asus eepc 1000HE (intel atom n270, 1gb, intel mobile 945gse integrated), wireless RT2790 lubuntu@lubuntu:/var/crash$ ubuntu-bug _usr_bin_gnome-mpv.999.crash (apport-gtk:2872): dbind-WARNING **: 01:56:11.124: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files ERROR: gdb does not exist in the sandbox nor on the host The last line "ERROR: gdb does not exist in the sandbox nor on the host" I wonder if it's a reason for the submission not taking place, but it could also be something else. A clearer message at the end would be helpful, eg. "Bug submitted: Thank you for helping make Ubuntu better" or "Submission a duplicate of existing, noted. Thank you for helping make Ubuntu better" Note: I've not thought about what I've written here, but a clearer message maybe helpful. But ending on an 'ERROR:' doesn't help users/testers know if the `ubuntu-bug` succeeded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.16 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: i386 CasperVersion: 1.394.3 CrashReports: 640:999:117:17658765:2020-08-06 01:57:14.718189716 +:2020-08-06 01:57:15.718189716 +:/var/crash/_usr_bin_gnome-mpv.999.crash CurrentDesktop: LXDE Date: Thu Aug 6 02:08:57 2020 LiveMediaBuild: Lubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgradwas not provided by any .service files ERROR: gdb does not exist in the sandbox nor on the hoste log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890515/+subscriptions -- Mailing list: https://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 1890332] Re: apt update fails on docker arm container 20.04
The root cause of the problem [is in libseccomp When][1]. The newer version fixes the problem, but it is not yet available in Debian's stable repos. There are two way to fix this problem: **Method 1** Start the container with `--privileged`. This bypasses docker's security measures, so it is not recommended. **Method 2** Upgrade libseccomp manually. Dowload version from unstable repos (I tested with 2.4.3-1) [here][2]. Uninstall the current version: `sudo dpkg --force-all -P libseccomp2` Install the new version: `sudo dpkg -i libseccomp2_2.4.3-1+b1_armhf.deb` [1]: https://github.com/moby/moby/issues/40734 [2]: https://packages.debian.org/sid/libseccomp2 ** Bug watch added: github.com/moby/moby/issues #40734 https://github.com/moby/moby/issues/40734 -- 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/1890332 Title: apt update fails on docker arm container 20.04 Status in apt package in Ubuntu: New Bug description: Running `apt update` in a ubuntu:20.04 docker container on raspberry pi fails with GPG errors. Expected behaviour: Successfully update the system through `apt update` What happens instead: `Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease At least one invalid signature was encountered.` Complete log: https://pastebin.com/sggGJcY1 How to reproduce: On a Raspberry Pi 3b or 4b (and maybe others ?), run the following command: `docker run ubuntu:latest apt update` or more specifically: `docker run arm32v7/ubuntu:20.04 apt update` More information: I can reproduce the bug on the following host systems: * Raspberry Pi 3b running HypriotOS * Raspberry Pi 4b running Raspbian GNU/Linux 10 (buster) The problem does not happens on the following host system: * Raspberry Pi 3b running Arch Linux Arm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1890332/+subscriptions -- Mailing list: https://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 1890515] Re: ubuntu-bug blah.crash file gives errors that imply it wasn't submitted
Possible duplicate. This issue I've reported before, but I cannot find it. -- 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/1890515 Title: ubuntu-bug blah.crash file gives errors that imply it wasn't submitted Status in apport package in Ubuntu: New Bug description: Unclear messages on `ubuntu-bug /var/crash/blah.crash` on i386 live qa-test asus eepc 1000HE (intel atom n270, 1gb, intel mobile 945gse integrated), wireless RT2790 lubuntu@lubuntu:/var/crash$ ubuntu-bug _usr_bin_gnome-mpv.999.crash (apport-gtk:2872): dbind-WARNING **: 01:56:11.124: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files ERROR: gdb does not exist in the sandbox nor on the host The last line "ERROR: gdb does not exist in the sandbox nor on the host" I wonder if it's a reason for the submission not taking place, but it could also be something else. A clearer message at the end would be helpful, eg. "Bug submitted: Thank you for helping make Ubuntu better" or "Submission a duplicate of existing, noted. Thank you for helping make Ubuntu better" Note: I've not thought about what I've written here, but a clearer message maybe helpful. But ending on an 'ERROR:' doesn't help users/testers know if the `ubuntu-bug` succeeded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.16 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: i386 CasperVersion: 1.394.3 CrashReports: 640:999:117:17658765:2020-08-06 01:57:14.718189716 +:2020-08-06 01:57:15.718189716 +:/var/crash/_usr_bin_gnome-mpv.999.crash CurrentDesktop: LXDE Date: Thu Aug 6 02:08:57 2020 LiveMediaBuild: Lubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgradwas not provided by any .service files ERROR: gdb does not exist in the sandbox nor on the hoste log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890515/+subscriptions -- Mailing list: https://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 1890515] [NEW] ubuntu-bug blah.crash file gives errors that imply it wasn't submitted
Public bug reported: Unclear messages on `ubuntu-bug /var/crash/blah.crash` on i386 live qa-test asus eepc 1000HE (intel atom n270, 1gb, intel mobile 945gse integrated), wireless RT2790 lubuntu@lubuntu:/var/crash$ ubuntu-bug _usr_bin_gnome-mpv.999.crash (apport-gtk:2872): dbind-WARNING **: 01:56:11.124: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files ERROR: gdb does not exist in the sandbox nor on the host The last line "ERROR: gdb does not exist in the sandbox nor on the host" I wonder if it's a reason for the submission not taking place, but it could also be something else. A clearer message at the end would be helpful, eg. "Bug submitted: Thank you for helping make Ubuntu better" or "Submission a duplicate of existing, noted. Thank you for helping make Ubuntu better" Note: I've not thought about what I've written here, but a clearer message maybe helpful. But ending on an 'ERROR:' doesn't help users/testers know if the `ubuntu-bug` succeeded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.16 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: i386 CasperVersion: 1.394.3 CrashReports: 640:999:117:17658765:2020-08-06 01:57:14.718189716 +:2020-08-06 01:57:15.718189716 +:/var/crash/_usr_bin_gnome-mpv.999.crash CurrentDesktop: LXDE Date: Thu Aug 6 02:08:57 2020 LiveMediaBuild: Lubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgradwas not provided by any .service files ERROR: gdb does not exist in the sandbox nor on the hoste log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ** Description changed: + Unclear messages on `ubuntu-bug /var/crash/blah.crash` + on i386 live qa-test + asus eepc 1000HE (intel atom n270, 1gb, intel mobile 945gse integrated), wireless RT2790 + lubuntu@lubuntu:/var/crash$ ubuntu-bug _usr_bin_gnome-mpv.999.crash (apport-gtk:2872): dbind-WARNING **: 01:56:11.124: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files ERROR: gdb does not exist in the sandbox nor on the host - - The last line "ERROR: gdb does not exist in the sandbox nor on the host" I wonder if it's a reason for the submission not taking place, but it could also be something else. + The last line "ERROR: gdb does not exist in the sandbox nor on the host" + I wonder if it's a reason for the submission not taking place, but it + could also be something else. A clearer message at the end would be helpful, eg. "Bug submitted: Thank you for helping make Ubuntu better" or "Submission a duplicate of existing, noted. Thank you for helping make Ubuntu better" Note: I've not thought about what I've written here, but a clearer message maybe helpful. But ending on an 'ERROR:' doesn't help users/testers know if the `ubuntu-bug` succeeded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.16 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: i386 CasperVersion: 1.394.3 CrashReports: 640:999:117:17658765:2020-08-06 01:57:14.718189716 +:2020-08-06 01:57:15.718189716 +:/var/crash/_usr_bin_gnome-mpv.999.crash CurrentDesktop: LXDE Date: Thu Aug 6 02:08:57 2020 LiveMediaBuild: Lubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200805) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash SourcePackage: apport - UpgradeStatus: No upgrade log present (probably fresh install) + UpgradeStatus: No upgradwas not provided by any .service files + ERROR: gdb does not exist in the sandbox nor on the hoste log present (probably fresh install) -- 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/1890515 Title: ubuntu-bug blah.crash file gives errors that imply it wasn't submitted Status in apport package in Ubuntu: New Bug description: Unclear messages on `ubuntu-bug /var/crash/blah.crash` on i386 live qa-test asus eepc 1000HE (intel atom n270, 1gb, intel mobile 945gse integrated), wireless RT2790
[Touch-packages] [Bug 1866444] Re: [MacBook2, 1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem
Hi! I just want to chime in and document my workaround to use a generic UVC webcam with a built-in mic. I attach a screenshot showing both a "multichannel input" and "microphone" once the UVC webcam is attached. Notice the picklist still does not contain an item for the system built- in [analog] microphone. ** Attachment added: "Sound setting missing picklist item for internal analog mic" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866444/+attachment/5399088/+files/Settings%20-%20Sounds%20-%20Microphone%20-%20Camera.png -- 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/1866444 Title: [MacBook2,1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: What you expected to happen Settings -> Sound -> Input to list internal mic (to test orange bars for recording from internal mic) What actually happened Settings -> Sound -> Input only lists "Digital Input (S/PDIF)" (no bars move because no digital input connected) If possible, a minimal series of steps necessary to make it happen, where step 1 is "start the program" 1. Open Settings 2. Select Sound setting 3. Select Input tab -- NOTE: ultimately, I want recording to work in apps such as Chrome, Firefox, Zoom, etc. NOTE 2: mic recording was last working in Ubuntu 18.04.x (32-bit) instance on *same* MacBook hardware (this installation went corrupt so I can't reverify it still works unfortunately - I will add to this issue if I get the cycles to reinstall or at your request) NOTE 3: interestingly enough, while using "ubuntu-bug" it was able to record from the mic on the 1st (of 2 tests the bug collector initiated). -- $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 from "apt list --installed" alsa-base/bionic,bionic,bionic,bionic,now 1.0.25+dfsg-0ubuntu5 all [installed] alsa-utils/bionic,bionic,now 1.1.3-1ubuntu1 amd64 [installed] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_76_86_generic_63 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D1c: chinarut 1724 F...m pulseaudio /dev/snd/controlC0: chinarut 1724 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 22:41:25 2020 InstallationDate: Installed on 2020-01-24 (42 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Intel failed Symptom_Type: Only some of inputs are working Title: [MacBook2,1, SigmaTel STAC9221 A1, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.family: MacBook dmi.product.name: MacBook2,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1866444/+subscriptions -- Mailing list: https://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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)
This looks like a signalling problem. There doesn't seem to be any corruption in the image. Only the signal to the monitor doesn't correctly match the frequencies that the monitor requires. As a workaround please try selecting 'Ubuntu on Wayland' from the login screen. Please also try a different VGA cable if you can. ** Summary changed: - Screen corruption with multi monitor setup + VGA image is ghosted and stretched (LG L1953S) ** Package changed: xorg (Ubuntu) => xorg-server (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/1890436 Title: VGA image is ghosted and stretched (LG L1953S) Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
[Touch-packages] [Bug 1890512] Re: bluetooth stopped working after recent apt updates
There have been no updates to the 'bluez' package since 20.04 was released. So that can't be the problem. Most likely it's a kernel update that caused the problem. The most recent one was only a week or two ago. Please try downgrading (or upgrading) your kernel version using these: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1890512 Title: bluetooth stopped working after recent apt updates Status in linux package in Ubuntu: Incomplete Bug description: bluetooth stopped working after recent apt updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 06:20:29 2020 InstallationDate: Installed on 2020-03-02 (156 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bluetooth Lsusb: Bus 002 Device 002: ID 1058:25e1 Western Digital Technologies, Inc. My Passport 25E1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 002: ID 24ae:1813 RAPOO Rapoo 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX461FN_UX461FN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=68586d80-0dfa-454e-918b-83ddbf1d4c3c ro quiet splash dis_ucode_ldr resume=UUID=014fadee-e595-4994-a198-c7eb8db1fa57 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-21 (76 days ago) dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX461FN.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX461FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX461FN.302:bd01/28/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX461FN_UX461FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX461FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook UX461FN_UX461FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2020-06-30T20:08:54.584021 mtime.conffile..etc.bluetooth.main.conf: 2020-03-04T03:26:07.238405 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890512/+subscriptions -- Mailing list: https://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 1890411] Re: Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.
Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.
** Tags added: bionic
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
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/1890411
Title:
Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Status in mesa package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
When ubuntu starts up, gdm3 does not start due to a crash in the the
xserver:
[ 1271.342] (II) SELinux: Disabled on system
[ 1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
[ 1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 1271.346] (II) AIGLX: Loaded and initialized i965
[ 1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1271.348] (II) modeset(0): Damage tracking initialized
[ 1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
[ 1271.352] (EE)
[ 1271.352] (EE) Backtrace:
[ 1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
[ 1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869)
[0x5649b579f869]
[ 1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
[ 1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
[ 1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
[ 1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
[ 1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
[ 1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
[ 1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
[ 1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
[ 1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
[ 1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03)
[0x5649b5721d03]
[ 1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f)
[0x5649b577fd1f]
[ 1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112)
[0x5649b577fa62]
[ 1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41)
[0x5649b568cc41]
[ 1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
[ 1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79)
[0x5649b5639e79]
[ 1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
[ 1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
[ 1271.352] (EE)
[ 1271.352] (EE) Segmentation fault at address 0x4
[ 1271.352] (EE)
Fatal server error:
[ 1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 1271.352] (EE)
[ 1271.352] (EE)
As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
specific package from version 20.0.8-0ubuntu1~18.04.1 back to
19.2.8-0ubuntu0~18.04.3.
This solves the problem. So I suspect that the problem is in this
specific package.
My machine is (uname):
4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64
[Touch-packages] [Bug 1890512] [NEW] bluetooth stopped working after recent apt updates
Public bug reported: bluetooth stopped working after recent apt updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 06:20:29 2020 InstallationDate: Installed on 2020-03-02 (156 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bluetooth Lsusb: Bus 002 Device 002: ID 1058:25e1 Western Digital Technologies, Inc. My Passport 25E1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 002: ID 24ae:1813 RAPOO Rapoo 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX461FN_UX461FN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=68586d80-0dfa-454e-918b-83ddbf1d4c3c ro quiet splash dis_ucode_ldr resume=UUID=014fadee-e595-4994-a198-c7eb8db1fa57 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-21 (76 days ago) dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX461FN.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX461FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX461FN.302:bd01/28/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX461FN_UX461FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX461FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook UX461FN_UX461FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2020-06-30T20:08:54.584021 mtime.conffile..etc.bluetooth.main.conf: 2020-03-04T03:26:07.238405 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1890512 Title: bluetooth stopped working after recent apt updates Status in bluez package in Ubuntu: New Bug description: bluetooth stopped working after recent apt updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 06:20:29 2020 InstallationDate: Installed on 2020-03-02 (156 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bluetooth Lsusb: Bus 002 Device 002: ID 1058:25e1 Western Digital Technologies, Inc. My Passport 25E1 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 002: ID 24ae:1813 RAPOO Rapoo 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX461FN_UX461FN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=68586d80-0dfa-454e-918b-83ddbf1d4c3c ro quiet splash dis_ucode_ldr resume=UUID=014fadee-e595-4994-a198-c7eb8db1fa57 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-05-21 (76 days ago) dmi.bios.date: 01/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX461FN.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX461FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX461FN.302:bd01/28/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX461FN_UX461FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX461FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook UX461FN_UX461FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: mtime.conffile..etc.bluetooth.input.conf: 2020-06-30T20:08:54.584021 mtime.conffile..etc.bluetooth.main.conf: 2020-03-04T03:26:07.238405 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1890512/+subscriptions -- Mailing list: https://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 1861451] Re: apport's cloud-init-specific handling tracebacks on minimal cloud images
This actually only affects Ubuntu 18.04. ** Changed in: apport (Ubuntu Focal) Status: New => Invalid ** Changed in: apport (Ubuntu) Status: New => Fix Released ** Also affects: apport (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Bionic) Status: New => In Progress ** Changed in: apport (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) -- 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/1861451 Title: apport's cloud-init-specific handling tracebacks on minimal cloud images Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: In Progress Status in apport source package in Focal: Invalid Bug description: Steps to reproduce: 1) Install multipass. 2) `multipass launch http://cloud-images.ubuntu.com/minimal/daily/bionic/current/bionic-minimal-cloudimg-amd64.img -n reproducer` 3) `multipass shell reproducer` 4) `ubuntu-bug cloud-init` Expected behaviour: Usual bug reporting flow (though, currently, I would really expect to see just the issue reported in bug 1861450). Actual behaviour: ERROR: hook /usr/share/apport/package-hooks/cloud-init.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/cloud-init.py", line 6, in add_info return cloudinit_add_info(report, ui) File "/usr/lib/python3/dist-packages/cloudinit/apport.py", line 123, in add_info attach_cloud_init_logs(report, ui) File "/usr/lib/python3/dist-packages/cloudinit/apport.py", line 57, in attach_cloud_init_logs 'cloud-init-output.log.txt': 'cat /var/log/cloud-init-output.log'}) File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 444, in attach_root_command_outputs sp = subprocess.Popen(_root_command_prefix() + [wrapper_path, script_path]) File "/usr/lib/python3.6/subprocess.py", line 729, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.6/subprocess.py", line 1364, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'pkexec': 'pkexec' (As alluded to above, this also demonstrates bug 1861450 after the traceback is emitted.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861451/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
CURRENT STATUS:
SUMMARY:
BUG: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941
TESTCASE: https://paste.ubuntu.com/p/37KGy2Smnp/
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1861941
BCACHE-TOOLS:
GROOVY: https://tinyurl.com/yxonp5hz (merged)
FOCAL: https://tinyurl.com/y3tbd3un (committed + verified)
BIONIC: https://tinyurl.com/y58fm4l5 (being reviewed)
SYSTEMD-UDEV:
GROOVY: https://tinyurl.com/y4w22s57 (merged patch rewording, will wait next
upload)
FOCAL: https://tinyurl.com/y2uqbyll (merged patch, will ask for an upload - SRU)
BIONIC: BEING WORKED
KERNEL:
Decided that won't be changed as the udev bcache changes won't cause any
harm. Will ask for the patch to be dropped from groovy's kernel since
there isn't any need to keep it.
** Description changed:
+ [Impact]
+
+ * bcache-tools udev created symlinks might disappear when other udev
+ events are processed for the same devices.
+
+ * after mkfs.XXX in /dev/bcacheY you might face a condition where
+ /dev/bcache/by-{uuid,label}/zzz symlinks are gone.
+
+ * /dev/bcache/by-{uuid,label}/ symlinks are important so bcache devices
+ can be addressed by their UUIDs and not the ordering they were assembled
+ (MAAS depends on this feature, for example).
+
+ * it was also discussed in this bug that systemd-udev should *not*
+ populate /dev/disk/by-uuid/ with symlinks of disks that were bcache
+ backing devices. this was turned into a discussion whether blkid should
+ report those or not, and this discussion "died" after sometime.
+
+ [Test Case]
+
+ * The reproducer script is here:
+
+https://paste.ubuntu.com/p/37KGy2Smnp/
+
+ [Regression Potential]
+
+ * We are not depending on bcache device udev events any more when
+ creating the /dev/bcache/by-{uuid,label}/ symlinks. Instead, we are
+ depending on a wrapper script that heads bcache device superblock. If
+ there is a bug in this wrapper the symlinks wouldn't work.
+
+ * Previously we were thinking in asking the kernel team to remove the
+ bcache udev event delta script they've done for previous case (LP:
+ #1729145). It creates the udev events that were being read and filling
+ the symlinks. We decided not to remove those (just from Groovy and on)
+ so we don't need to worry on Breaks/Conflicts in between the kernel
+ package and bcache-tools (and udev)).
+
+ * Long story short: kernel will continue to emit bcache udev events as
+ it did previously but now those events won't be used by anything - after
+ installing this SRU - because udev wrapper script is doing this job (and
+ doing it properly)
+
+ [Other Info]
+
+ - Original Description:
+
+
1.
root@ubuntu:~# lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
- 2.
+ 2.
root@ubuntu:~# lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
- root@ubuntu:~# apt-cache policy linux-image-virtual
+ root@ubuntu:~# apt-cache policy linux-image-virtual
linux-image-virtual:
- Installed: 5.4.0.12.15
- Candidate: 5.4.0.12.15
- Version table:
- *** 5.4.0.12.15 500
- 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
- root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic
+ Installed: 5.4.0.12.15
+ Candidate: 5.4.0.12.15
+ Version table:
+ *** 5.4.0.12.15 500
+ 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
+ root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic
linux-image-5.4.0-12-generic:
- Installed: 5.4.0-12.15
- Candidate: 5.4.0-12.15
- Version table:
- *** 5.4.0-12.15 500
- 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: 5.4.0-12.15
+ Candidate: 5.4.0-12.15
+ Version table:
+ *** 5.4.0-12.15 500
+ 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
+ ls -al /dev/bcache/by-uuid/
total 0
drwxr-xr-x 2 root root 60 Feb 4 23:31 .
drwxr-xr-x 3 root root 60 Feb 4 23:31 ..
lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a
-> ../../bcache0
4.
root@ubuntu:~# ls -al /dev/bcache/by-uuid
ls: cannot access '/dev/bcache/by-uuid': No such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Tue Feb 4 23:31:52 2020
ProcEnviron:
- TERM=xterm-256color
- PATH=(custom, no user)
- LANG=C.UTF-8
- SHELL=/bin/bash
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ LANG=C.UTF-8
+ SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
[Touch-packages] [Bug 1890041] Re: Apport does not work without Chrome
no, I meant $ grep chromium ~/.local/share/applications/* -- 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/1890041 Title: Apport does not work without Chrome Status in apport package in Ubuntu: Incomplete Bug description: I cannot recall Apport ever working for me, but this time it fails because I don't have chromium installed on my machine. I use Firefox instead. Besides, on the second screen, "I don't know" should realy be called "My bug is not listed". Error message: arcturus ~ > apport-bug 1276 /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) non-network local connections being added to access control list sudo: chromium-browser: command not found Further information: Kubuntu 20.04.1 LTS apport: Installed: 2.20.11-0ubuntu27.4 Candidate: 2.20.11-0ubuntu27.4 Version table: *** 2.20.11-0ubuntu27.4 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/bcache-tools/+git/bcache-tools/+merge/388774 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in bcache-tools source package in Focal: Fix Committed Status in systemd source package in Focal: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
@Hui, we will get the new version but unsure when so if it's not too much extra work it would be b etter to generate debdiffs for G -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch ucm-allow-to-ignore-errors-for-the-value-substitutio.patch ucm-allow-to-use-the-defined-variables-in-the-substi.patch
[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
VERIFICATION FOR FOCAL: (k)rafaeldtinoco@bcachefocal:~$ apt-cache policy bcache-tools bcache-tools: Installed: (none) Candidate: 1.0.8-3ubuntu0.1 Version table: 1.0.8-3ubuntu0.1 500 500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 1.0.8-3 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages (k)rafaeldtinoco@bcachefocal:~$ apt-get install bcache-tools (k)rafaeldtinoco@bcachefocal:~/scripts$ sudo ./test-bcache.sh /mnt is not a mountpoint /dev/bcache0: 2 bytes were erased at offset 0x0438 (ext4): 53 ef writing 1 to /sys/class/block/bcache0/bcache/stop writing 1 to /sys/fs/bcache/6fcbc055-be04-4527-9c73-788c2419b292/stop /dev/vdc: 16 bytes were erased at offset 0x1018 (bcache): c6 85 73 f6 4e 1a 45 ca 82 65 f5 7f 48 ba 6d 81 10+0 records in 10+0 records out 10485760 bytes (10 MB, 10 MiB) copied, 0.0204717 s, 512 MB/s /dev/vdb: 16 bytes were erased at offset 0x1018 (bcache): c6 85 73 f6 4e 1a 45 ca 82 65 f5 7f 48 ba 6d 81 10+0 records in 10+0 records out 10485760 bytes (10 MB, 10 MiB) copied, 0.0092515 s, 1.1 GB/s UUID: 73cc1c6f-ded6-4874-b76a-465408cfbd19 Set UUID: a2400c1f-e83b-4086-a58d-0b2ebba97a9c version:0 nbuckets: 2048 block_size: 1 bucket_size:1024 nr_in_set: 1 nr_this_dev:0 first_bucket: 1 UUID: 5f51a399-d65d-49ec-af3b-6b2b28c39605 Set UUID: a2400c1f-e83b-4086-a58d-0b2ebba97a9c version:1 block_size: 1 data_offset:16 /dev/vdc tee: /sys/fs/bcache/register: Invalid argument /dev/vdb tee: /sys/fs/bcache/register: Invalid argument total 0 drwxr-xr-x 2 root root 60 Aug 5 21:12 . drwxr-xr-x 3 root root 60 Aug 5 21:12 .. lrwxrwxrwx 1 root root 13 Aug 5 21:12 5f51a399-d65d-49ec-af3b-6b2b28c39605 -> ../../bcache0 Creating filesystems on bcache0 mke2fs 1.45.5 (07-Jan-2020) Discarding device blocks: done Creating filesystem with 2621438 4k blocks and 655360 inodes Filesystem UUID: 1b609131-52ca-43f7-96b2-4dc931f2553f Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 Allocating group tables: done Writing inode tables: done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done mounting bcache0 to /mnt total 0 drwxr-xr-x 2 root root 60 Aug 5 21:12 . drwxr-xr-x 3 root root 60 Aug 5 21:12 .. lrwxrwxrwx 1 root root 13 Aug 5 21:12 5f51a399-d65d-49ec-af3b-6b2b28c39605 -> ../../bcache0 Everything OK All good! ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in bcache-tools source package in Focal: Fix Committed Status in systemd source package in Focal: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Touch-packages] [Bug 1848862] Re: HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work
Please note that I received help in translating the archlinux code. The site below lists out the solution for anyone else trying to resolve this problem on their laptop. https://github.com/systemd/systemd/issues/15774 ** Bug watch added: github.com/systemd/systemd/issues #15774 https://github.com/systemd/systemd/issues/15774 ** Changed in: systemd (Ubuntu) Status: Invalid => In Progress -- 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/1848862 Title: HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work Status in systemd package in Ubuntu: In Progress Bug description: I just installed Ubuntu 19.10 on my HP Elitebook 840 G1. Switching from Windows to Ubuntu for personal use. The mic does not enable/disable with FN+F8 combo and the light is constantly on. I found the following solution to my problem. However, I do not know how to implement it in Ubuntu 19.10 (new to Ubuntu and generally not as techinical). https://wiki.archlinux.org/index.php/HP_EliteBook_840_G1#Enable_the_microphone_muting_key 1. Would greatly appreciate if someone could point me to step by step instructions to install the code from the link above. I can report back if this resolve the issue. 2. Also, is there a way to incorporate a fix for this issue with HP laptops in Ubuntu going forward? When I was searching for a fix, I found this to be a widespread issue with various HP laptops and Ubuntu dating back a couple years. Many thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1848862/+subscriptions -- Mailing list: https://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 1876659] Re: Unhandled exception in run_hang()
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu -- 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/1876659 Title: Unhandled exception in run_hang() Status in Apport: New Status in apport package in Ubuntu: Fix Released Bug description: ## Description When we start apport-cli without PID, an unhandled exception in apport 2.20.11 and earlier may allow an authenticated user to potentially enable a denial of service via local access. The following command may cause an application crash due to an unhandled exception. $ apport-cli --hanging *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (24.0 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): K Problem report file: /tmp/apport.apport.uc0_znhj.apport Traceback (most recent call last): File "/usr/bin/apport-cli", line 387, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 690, in run_argv self.run_hang(self.options.pid) File "/usr/lib/python3/dist-packages/apport/ui.py", line 410, in run_hang os.kill(int(pid), signal.SIGKILL) TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' Above command generates the following application crash file in /var/crash/ directory. ProblemType: Crash CurrentDesktop: ubuntu:GNOME Date: Sun May 3 19:09:41 2020 ExecutablePath: /usr/bin/apport-cli ExecutableTimestamp: 1585099033 InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli --hanging ProcCwd: /home/user/apport/bin ProcEnviron: ... ProcMaps: ... ProcStatus: ... PythonArgs: ['/usr/bin/apport-cli', '--hanging'] Traceback: Traceback (most recent call last): File "/usr/bin/apport-cli", line 387, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 690, in run_argv self.run_hang(self.options.pid) File "/usr/lib/python3/dist-packages/apport/ui.py", line 410, in run_hang os.kill(int(pid), signal.SIGKILL) TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _LogindSession: 6 Many thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1876659/+subscriptions -- Mailing list: https://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 1877023] Re: Unhandled exception in check_ignored()
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu
--
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/1877023
Title:
Unhandled exception in check_ignored()
Status in Apport:
New
Status in apport package in Ubuntu:
Fix Released
Bug description:
Hi,
I have found a security issue on apport 2.20.11 and earlier.
## Vulnerability
apport 2.20.11 and earlier have an unhandled exception vulnerability during
parsing apport-ignore.xml.
An attacker can cause a denial of service (i.e., application crash) via a
crafted apport-ignore.xml file.
## Description
Reports can be suppressed by blacklisting in apport-ignore.xml.
This is an example of apport-ignore.xml
Unfortunately, it may cause an unhandled exception when 'mtime'
attribute is specified as a string value, not a number like this.
It may disrupt apport service and allow an attacker to potentially
enable a denial of service via local access.
The flaw lies in improper exception handling of 'mtime' attribute in
apport-ignore.xml (see
https://git.launchpad.net/ubuntu/+source/apport/tree/apport/report.py?h=applied/ubuntu/devel#n1104).
## Log
Here is /var/log/apport.log when the above exception occurs.
ERROR: apport (pid 25904) Tue May 5 18:38:21 2020: Unhandled exception:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 629, in
if info.check_ignored():
File "/usr/lib/python3/dist-packages/apport/report.py", line 1082, in
check_ignored
if float(ignore.getAttribute('mtime')) >= cur_mtime:
ValueError: could not convert string to float: 'string'
Sincerely,
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1877023/+subscriptions
--
Mailing list: https://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 1872118] Re: DHCP Cluster crashes after a few hours
Jorge, I have been running for 25 hours on the patched version with no crashes on either server. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872118 Title: DHCP Cluster crashes after a few hours Status in DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: Confirmed Bug description: I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked perfectly until recently, when they started stopping with code=killed, status=6/ABRT. This is being fixed by https://bugs.launchpad.net/bugs/1870729 However now one stops after a few hours with the following errors. One can stay on line but not both. Syslog shows Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ?? nothing in kern.log apport.log shows ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 6, core limit 0, dump mode 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid with dump mode of 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: /usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf") ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report /var/crash/_usr_sbin_dhcpd.0.crash /var/crash/_usr_sbin_dhcpd.0.crash shows ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Fri Apr 10 17:20:15 2020 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/sbin/dhcpd ExecutableTimestamp: 1586210315 ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' ProcStatus: Name: dhcpd Umask: 0022 State: D (disk sleep) Tgid: 6828 Ngid: 0 Pid: 6828 PPid: 1 TracerPid: 0 Uid: 113 113 113 113 Gid: 118 118 118 118 FDSize:128 Groups: NStgid:6828 NSpid: 6828 NSpgid:6828 NSsid: 6828 VmPeak: 236244 kB VmSize: 170764 kB VmLck:0 kB VmPin:0 kB VmHWM:12064 kB VmRSS:12064 kB RssAnon: 5940 kB RssFile: 6124 kB RssShmem: 0 kB VmData: 30792 kB VmStk: 132 kB VmExe: 592 kB VmLib: 5424 kB VmPTE: 76 kB VmSwap: 0 kB HugetlbPages: 0 kB CoreDumping: 1 THP_enabled: 1 Threads: 4 SigQ: 0/7609 SigPnd: ShdPnd: SigBlk: SigIgn:1000 SigCgt:00018000 CapInh: CapPrm: CapEff: CapBnd:003f CapAmb: NoNewPrivs:0 Seccomp: 0 Speculation_Store_Bypass: thread vulnerable Cpus_allowed: 3 Cpus_allowed_list: 0-1 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,0001 Mems_allowed_list: 0 voluntary_ctxt_switches: 111 nonvoluntary_ctxt_switches:144 Signal: 6 Uname: Linux 5.4.0-21-generic x86_64 UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1872118/+subscriptions -- Mailing list: https://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 1872118] Re: DHCP Cluster crashes after a few hours
OK, I have no crashes to report for the last 24 hours with the PPA included here. ● isc-dhcp-server.service - ISC DHCP IPv4 server Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-08-04 14:58:11 UTC; 1 day 1h ago Docs: man:dhcpd(8) Main PID: 1202 (dhcpd) Tasks: 5 (limit: 5882) Memory: 6.3M CGroup: /system.slice/isc-dhcp-server.service └─592 dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf root@dhcpd1:/home/ubuntu# dpkg -l | grep ppa1 ii isc-dhcp-server 4.4.1-2.1ubuntu6~ppa1 amd64 ISC DHCP server for automatic IP address assignment ii libirs-export161 1:9.11.16+dfsg-3~ppa1 amd64 Exported IRS Shared Library ii libisc-export1105:amd64 1:9.11.16+dfsg-3~ppa1 amd64 Exported ISC Shared Library ii libisccfg-export163 1:9.11.16+dfsg-3~ppa1 amd64 Exported ISC CFG Shared Library Andrew, what's the current version of libisc-export1105:amd64 installed in your system? can you provide a dpkg -l output and a systemctl status for the dhcpd service? Did you restarted/killed the dhcpd processes after upgrading that library? Thanks in advance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872118 Title: DHCP Cluster crashes after a few hours Status in DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: Confirmed Bug description: I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked perfectly until recently, when they started stopping with code=killed, status=6/ABRT. This is being fixed by https://bugs.launchpad.net/bugs/1870729 However now one stops after a few hours with the following errors. One can stay on line but not both. Syslog shows Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ?? nothing in kern.log apport.log shows ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 6, core limit 0, dump mode 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid with dump mode of 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: /usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf") ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report /var/crash/_usr_sbin_dhcpd.0.crash /var/crash/_usr_sbin_dhcpd.0.crash shows ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Fri Apr 10 17:20:15 2020 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/sbin/dhcpd ExecutableTimestamp: 1586210315 ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' ProcStatus: Name: dhcpd Umask: 0022 State: D (disk sleep) Tgid: 6828 Ngid: 0 Pid: 6828 PPid: 1 TracerPid: 0 Uid: 113 113 113 113 Gid: 118 118 118 118 FDSize:128 Groups: NStgid:6828 NSpid: 6828 NSpgid:6828 NSsid: 6828 VmPeak: 236244 kB VmSize: 170764 kB VmLck:0 kB VmPin:0 kB VmHWM:12064 kB VmRSS:12064 kB RssAnon: 5940 kB RssFile: 6124 kB RssShmem: 0 kB VmData: 30792 kB VmStk: 132 kB VmExe: 592 kB VmLib: 5424 kB VmPTE: 76 kB VmSwap: 0 kB HugetlbPages: 0 kB CoreDumping: 1 THP_enabled: 1 Threads: 4 SigQ: 0/7609 SigPnd: ShdPnd: SigBlk: SigIgn:1000 SigCgt:00018000 CapInh: CapPrm: CapEff: CapBnd:003f CapAmb: NoNewPrivs:0 Seccomp: 0
[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours
Running over a day with the packages from the PPA in place: ● isc-dhcp-server.service - ISC DHCP IPv4 server Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-08-04 16:23:19 UTC; 1 day 1h ago Docs: man:dhcpd(8) Main PID: 592 (dhcpd) Tasks: 4 (limit: 4620) Memory: 6.4M CGroup: /system.slice/isc-dhcp-server.service └─592 dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf root@unique-macaw:/home/ubuntu# dpkg -l | grep ppa1 ii isc-dhcp-client 4.4.1-2.1ubuntu6~ppa1 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.4.1-2.1ubuntu6~ppa1 amd64common manpages relevant to all of the isc-dhcp packages ii isc-dhcp-server 4.4.1-2.1ubuntu6~ppa1 amd64ISC DHCP server for automatic IP address assignment ii libdns-export11091:9.11.16+dfsg-3~ppa1 amd64Exported DNS Shared Library ii libirs-export161 1:9.11.16+dfsg-3~ppa1 amd64Exported IRS Shared Library ii libisc-export1105:amd64 1:9.11.16+dfsg-3~ppa1 amd64Exported ISC Shared Library ii libisccfg-export163 1:9.11.16+dfsg-3~ppa1 amd64Exported ISC CFG Shared Library -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872118 Title: DHCP Cluster crashes after a few hours Status in DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: Confirmed Bug description: I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked perfectly until recently, when they started stopping with code=killed, status=6/ABRT. This is being fixed by https://bugs.launchpad.net/bugs/1870729 However now one stops after a few hours with the following errors. One can stay on line but not both. Syslog shows Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ?? nothing in kern.log apport.log shows ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 6, core limit 0, dump mode 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid with dump mode of 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: /usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf") ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report /var/crash/_usr_sbin_dhcpd.0.crash /var/crash/_usr_sbin_dhcpd.0.crash shows ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Fri Apr 10 17:20:15 2020 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/sbin/dhcpd ExecutableTimestamp: 1586210315 ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' ProcStatus: Name: dhcpd Umask: 0022 State: D (disk sleep) Tgid: 6828 Ngid: 0 Pid: 6828 PPid: 1 TracerPid: 0 Uid: 113 113 113 113 Gid: 118 118 118 118 FDSize:128 Groups: NStgid:6828 NSpid: 6828 NSpgid:6828 NSsid: 6828 VmPeak: 236244 kB VmSize: 170764 kB VmLck:0 kB VmPin:0 kB VmHWM:12064 kB VmRSS:12064 kB RssAnon: 5940 kB RssFile: 6124 kB RssShmem: 0 kB VmData: 30792 kB VmStk: 132 kB VmExe: 592 kB VmLib: 5424 kB VmPTE: 76 kB VmSwap: 0 kB HugetlbPages: 0 kB CoreDumping: 1 THP_enabled: 1 Threads: 4 SigQ: 0/7609 SigPnd: ShdPnd: SigBlk: SigIgn:
[Touch-packages] [Bug 1857769] Re: program linked to protobuf crashes before main
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: protobuf (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1857769
Title:
program linked to protobuf crashes before main
Status in protobuf package in Ubuntu:
Confirmed
Bug description:
This simple test crashes on a system that I installed Ubuntu Server 20.04
daily build on yesterday:
echo "syntax = \"proto2\";" >| test.pbc
echo "message TestMsg" >> test.pbc
echo "{" >> test.pbc
echo " required double f1 = 1;" >> test.pbc
echo "}" >> test.pbc
echo "int main() {return 0;}" >| test.cc
protoc --cpp_out=. ./test.pbc
g++ -c -o test.pbc.pb.o test.pbc.pb.cc
g++ -c -o test.o test.cc
g++ -o test test.o test.pbc.pb.o -lprotobuf
./test
terminate called after throwing an instance of 'std::system_error'
what(): Unknown error -1
Aborted (core dumped)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: protobuf-compiler 3.6.1.3-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
Date: Sat Dec 28 19:10:20 2019
InstallationDate: Installed on 2019-12-27 (1 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64
(20191227)
SourcePackage: protobuf
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1857769/+subscriptions
--
Mailing list: https://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 1872118] Re: DHCP Cluster crashes after a few hours
Last time in only did sudo apt install \ isc-dhcp-server=4.4.1-2.1ubuntu6~ppa1 \ sudo systemctl restart isc-dhcp-server This time i ried as someone else had done. sudo apt install \ isc-dhcp-server=4.4.1-2.1ubuntu6~ppa1 \ libdns-export1109=1:9.11.16+dfsg-3~ppa1 \ libirs-export161=1:9.11.16+dfsg-3~ppa1 \ libisc-export1105=1:9.11.16+dfsg-3~ppa1 && \ I've uploaded the full crash dump ** Attachment added: "_usr_sbin_dhcpd.0.crash" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+attachment/5398988/+files/_usr_sbin_dhcpd.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872118 Title: DHCP Cluster crashes after a few hours Status in DHCP: New Status in bind9-libs package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9-libs source package in Focal: New Status in isc-dhcp source package in Focal: New Status in bind9-libs source package in Groovy: New Status in isc-dhcp source package in Groovy: Confirmed Bug description: I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked perfectly until recently, when they started stopping with code=killed, status=6/ABRT. This is being fixed by https://bugs.launchpad.net/bugs/1870729 However now one stops after a few hours with the following errors. One can stay on line but not both. Syslog shows Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ?? nothing in kern.log apport.log shows ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 6, core limit 0, dump mode 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid with dump mode of 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: /usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf") ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report /var/crash/_usr_sbin_dhcpd.0.crash /var/crash/_usr_sbin_dhcpd.0.crash shows ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Fri Apr 10 17:20:15 2020 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/sbin/dhcpd ExecutableTimestamp: 1586210315 ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' ProcStatus: Name: dhcpd Umask: 0022 State: D (disk sleep) Tgid: 6828 Ngid: 0 Pid: 6828 PPid: 1 TracerPid: 0 Uid: 113 113 113 113 Gid: 118 118 118 118 FDSize:128 Groups: NStgid:6828 NSpid: 6828 NSpgid:6828 NSsid: 6828 VmPeak: 236244 kB VmSize: 170764 kB VmLck:0 kB VmPin:0 kB VmHWM:12064 kB VmRSS:12064 kB RssAnon: 5940 kB RssFile: 6124 kB RssShmem: 0 kB VmData: 30792 kB VmStk: 132 kB VmExe: 592 kB VmLib: 5424 kB VmPTE: 76 kB VmSwap: 0 kB HugetlbPages: 0 kB CoreDumping: 1 THP_enabled: 1 Threads: 4 SigQ: 0/7609 SigPnd: ShdPnd: SigBlk: SigIgn:1000 SigCgt:00018000 CapInh: CapPrm: CapEff: CapBnd:003f CapAmb: NoNewPrivs:0 Seccomp: 0 Speculation_Store_Bypass: thread vulnerable Cpus_allowed: 3 Cpus_allowed_list: 0-1 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,0001 Mems_allowed_list: 0 voluntary_ctxt_switches: 111 nonvoluntary_ctxt_switches:144 Signal: 6 Uname: Linux 5.4.0-21-generic x86_64 UserGroups: To manage notifications about this bug go to:
[Touch-packages] [Bug 1889059] Comment bridged from LTC Bugzilla
--- Comment From i...@de.ibm.com 2020-08-05 12:34 EDT--- I've updated https://github.com/madler/zlib/pull/410 to https://github.com/iii-i/zlib/releases/tag/dfltcc-20200805 level. -- 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/1889059 Title: [Ubuntu 20.04] zlib on s390x may produce incomplete raw (but not gzip/zlib) streams Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Status in zlib source package in Focal: New Status in zlib source package in Groovy: New Bug description: zlib on s390x may produce incomplete raw (but not gzip/zlib) streams ---uname output--- Linux t35lp56.lnxne.boe 5.8.0-20200703.rc3.git0.52a479d42203.300.fc31.s390x #1 SMP Fri Jul 3 00:46:20 CEST 2020 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Create a raw (negative windowBits value) stream with zlib. EOBS might be missing or truncated. This affects all distro levels that contain hardware acceleration (DFLTCC) patch. I've attached the preliminary fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889059/+subscriptions -- Mailing list: https://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 1876513] Re: .bashrc color_prompt check only works for xterm-color, not xterm-256color
The attachment "0001-share-dot.bashrc-color-support-for-256-color- terms.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 base-files in Ubuntu. https://bugs.launchpad.net/bugs/1876513 Title: .bashrc color_prompt check only works for xterm-color, not xterm- 256color Status in base-files package in Ubuntu: Confirmed Bug description: The `share/dot.bashrc` file checks like this whether to enable `color_prompt`: case "$TERM" in xterm-color) color_prompt=yes;; esac Nowaways, most terminals support 256 colors (instead of 8 like xterm- color). Their $TERM will usually be something like `xterm-256color`. Accordingly, this check was modified in the `skel`-package `/etc/skel/.bashrc` like this: case "$TERM" in xterm-color|*-256color) color_prompt=yes;; esac I would suggest the same modification be done in the base-files .bashrc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1876513/+subscriptions -- Mailing list: https://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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
** Tags added: originate-from-1874593 sutton -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch ucm-allow-to-ignore-errors-for-the-value-substitutio.patch ucm-allow-to-use-the-defined-variables-in-the-substi.patch ucm-implement-CardNumberByName-substitution.patch
[Touch-packages] [Bug 1876513] Re: .bashrc color_prompt check only works for xterm-color, not xterm-256color
It's a trivial patch, but included for completeness. ** Patch added: "0001-share-dot.bashrc-color-support-for-256-color-terms.patch" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1876513/+attachment/5398969/+files/0001-share-dot.bashrc-color-support-for-256-color-terms.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1876513 Title: .bashrc color_prompt check only works for xterm-color, not xterm- 256color Status in base-files package in Ubuntu: Confirmed Bug description: The `share/dot.bashrc` file checks like this whether to enable `color_prompt`: case "$TERM" in xterm-color) color_prompt=yes;; esac Nowaways, most terminals support 256 colors (instead of 8 like xterm- color). Their $TERM will usually be something like `xterm-256color`. Accordingly, this check was modified in the `skel`-package `/etc/skel/.bashrc` like this: case "$TERM" in xterm-color|*-256color) color_prompt=yes;; esac I would suggest the same modification be done in the base-files .bashrc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1876513/+subscriptions -- Mailing list: https://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 1876513] Re: .bashrc color_prompt check only works for xterm-color, not xterm-256color
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: base-files (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1876513 Title: .bashrc color_prompt check only works for xterm-color, not xterm- 256color Status in base-files package in Ubuntu: Confirmed Bug description: The `share/dot.bashrc` file checks like this whether to enable `color_prompt`: case "$TERM" in xterm-color) color_prompt=yes;; esac Nowaways, most terminals support 256 colors (instead of 8 like xterm- color). Their $TERM will usually be something like `xterm-256color`. Accordingly, this check was modified in the `skel`-package `/etc/skel/.bashrc` like this: case "$TERM" in xterm-color|*-256color) color_prompt=yes;; esac I would suggest the same modification be done in the base-files .bashrc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1876513/+subscriptions -- Mailing list: https://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 1890436] Re: Screen corruption with multi monitor setup
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1890436 Title: Screen corruption with multi monitor setup Status in xorg package in Ubuntu: New Bug description: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1890436/+subscriptions -- Mailing list: https://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 1890436] [NEW] Screen corruption with multi monitor setup
You have been subscribed to a public bug: Hello, last week I was digging in the BIOS of my PC at work since I tried to see if there is a way to update the dbx for secure boot. Since there was no option to perform this task, I modified some settings. In detail, I disabled CSM in BIOS and that's when hell broke loose! To get an idea about the hardware, the Lenovo machine isn't running the latest BIOS as its updater is broken and won't update it within win or its ISO image. It uses the previous version released by its manufacturer. The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled the DP monitor is lit first and then the VGA one prior OS loading. When CSM is disabled it goes the other way around. The VGA monitor is lit and the DP one opens up during OS load. With CSM disabled the VGA monitor is the primary one and it is corrupted as you can see on the pictures I have attached. Interestingly printing screens within Ubuntu does not capture the corruption problem I am getting as you can see on the pictures I have also attached. Neither X log contains anything useful. The issue is repeatable on every boot. As I have seen on other bug reports, I have enabled DRM debug, captured the dmesg using a huge buffer to get it and have uploaded it as well. I hope that it will help you track this issue down and fix it soon. Since I will be away some days for vacation, I will have physical access to it till this Friday and will get back to work at the 24th of August. In the mean time, I hope that someone will pinpoint the root cause of it and prepare a patch. Since this machine is running w10 2004, it should be noted that in win I do not get any corruption at all either in CSM mode or UEFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 11:30:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 3209C54 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9BAUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3209C54 dmi.product.sku: LENOVO_MT_3209 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal third-party-packages ubuntu -- Screen corruption with multi monitor setup https://bugs.launchpad.net/bugs/1890436 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890448] [NEW] hwdb: Add EliteBook to use micmute hotkey
Public bug reported:
[Impact]
Micmute hotkey on many HP EliteBooks don't work.
[Fix]
Commit b6eb208b29ae ("hwdb: Add EliteBook to use micmute hotkey"), to map AT
keyboard's scancode to micmute hotkey.
[Test]
With the one-liner fix, micmute hotkey works on all the EliteBooks I tested.
[Regression Potential]
The hwdb originally only matches a few EliteBook, and fix changes that to match
all EliteBook models. So if there's an EliteBook that uses the scancode for
other purpose, there will be a regression.
However, the risk is rather slim because HP is confident that all EliteBooks
use the same scancode for mic mute hotkey.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: oem-priority originate-from-1883044 stella
** Tags added: oem-priority originate-from-1883044 stella
--
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/1890448
Title:
hwdb: Add EliteBook to use micmute hotkey
Status in HWE Next:
New
Status in systemd package in Ubuntu:
New
Bug description:
[Impact]
Micmute hotkey on many HP EliteBooks don't work.
[Fix]
Commit b6eb208b29ae ("hwdb: Add EliteBook to use micmute hotkey"), to map AT
keyboard's scancode to micmute hotkey.
[Test]
With the one-liner fix, micmute hotkey works on all the EliteBooks I tested.
[Regression Potential]
The hwdb originally only matches a few EliteBook, and fix changes that to
match all EliteBook models. So if there's an EliteBook that uses the scancode
for other purpose, there will be a regression.
However, the risk is rather slim because HP is confident that all EliteBooks
use the same scancode for mic mute hotkey.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1890448/+subscriptions
--
Mailing list: https://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 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)
** Changed in: util-linux (Ubuntu Groovy) Status: Confirmed => Fix Committed ** Changed in: util-linux (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1886300 Title: rename.ul refuses to rename links that don't resolve (regression) Status in util-linux package in Ubuntu: Fix Committed Status in util-linux source package in Focal: In Progress Status in util-linux source package in Groovy: Fix Committed Bug description: [Impact] rename.ul refuses to rename links that don't resolve. bionic rename.ul renames links whether or not they resolve (util-linux 2.31.1-0.4ubuntu3.6). focal rename.ul refuses to rename links that don't resolve (regression) (util-linux 2.34-0.1ubuntu9). Eoan is EOL, so removed. [Test case] Commit has good test case. I paste it here Before: $ touch file-found $ ln -s file-found symlink-1 $ ./rename sym symbolic- symlink-1 # XPASS. $ echo $? 0 $ ln -s file-not-found symlink-2 $ ./rename sym symbolic- symlink-2 # FAIL! REGRESSION. rename: symlink-2: not accessible: No such file or directory $ echo $? 1 $ ./rename sym symbolic- symlink-3 # XFAIL. rename: symlink-3: not accessible: No such file or directory $ echo $? 1 $ touch file-found $ ./rename found existing file-found# XPASS. $ echo $? 0 $ ./rename found existing file-not-found # XFAIL. rename: file-not-found: not accessible: No such file or directory $ echo $? 1 After: $ touch file-found $ ln -s file-found symlink-1 $ ./rename sym symbolic- symlink-1 # XPASS. $ echo $? 0 $ ln -s file-not-found symlink-2 $ ./rename sym symbolic- symlink-2 # PASS! REGRESSION FIXED. $ echo $? 0 $ ./rename sym symbolic- symlink-3 # XFAIL. rename: symlink-3: not accessible: No such file or directory $ echo $? 1 $ touch file-found $ ./rename found existing file-found# XPASS. $ echo $? 0 $ ./rename found existing file-not-found # XFAIL. rename: file-not-found: not accessible: No such file or directory $ echo $? 1 [Regression Potential] This commit changes code that checking accessibility to file or sym link. If this fails, rename command will not work properly.it could be crashed or causes failure of rename. [Original Description] rename.ul refuses to rename links that don't resolve. bionic rename.ul renames links whether or not they resolve (util-linux 2.31.1-0.4ubuntu3.6). focal rename.ul refuses to rename links that don't resolve (regression) (util-linux 2.34-0.1ubuntu9). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: util-linux 2.34-0.1ubuntu9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jul 4 20:38:06 2020 InstallationDate: Installed on 2020-04-05 (90 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886814] Comment bridged from LTC Bugzilla
--- Comment From s...@de.ibm.com 2020-08-05 09:16 EDT--- Hi xnox, have you had the chance to retest flatpak-builder autopkgtests with an adjusted flatpak package like mentioned in my previous comment? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to make-dfsg in Ubuntu. https://bugs.launchpad.net/bugs/1886814 Title: posix_spawn usage in gnu make causes failures on s390x Status in Ubuntu on IBM z Systems: Triaged Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in make-dfsg package in Ubuntu: New Bug description: posix_spawn usage in gnu make causes failures on s390x Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it started to use posix_spawn, instead of fork()/exec(). This has caused failure of an unrelated package flatpak-builder autopkgtests on s390x only, like so echo Building make: echo: Operation not permitted make: *** [Makefile:2: all] Error 127 Julian Klaude investigated this in-depth. His earlier research also indicated that this is a heisenbug, if one tries to print to stderr before printing to stdout, no issue occurs. We are configuring GNU make to be build with --disable-posix-spawn on s390x only. We passed these details to Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=964541 too. But I do wonder, if there is something different or incorrect about posix_spawn() implementation in either glibc, or linux kernel, on s390x. Or gnu-make's usage of posix_spawn(). As otherise, using posix_spawn() in gnu-make works on other architectures, and flatpak-builder autopkgtests pass too. It seems very weird that stdout does not appear to be functional, unless stderr was opened/written to, from gnu-make execution compiled with posix-spawn feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886115] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1886115 Title: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot Status in libseccomp package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Fix Released Status in libseccomp source package in Bionic: New Status in systemd source package in Bionic: Fix Released Bug description: [impact] systemd sometimes crashes on boot due to free of uninitalized var [test case] a specific system setup is required, see original description [regression potential] any regression would likely involve further crashes on boot. [scope] this is needed in b. this is fixed upstream by commit 58d9d89b4b41189bdcea86c2ad5cf708b7d54aca which is included starting in v240, so this is included already in f and later. this is caused by commit 25cd49647c8 which is included starting in v237, so this bug does not exist in x. [original description] After applying updates to Ubuntu 18.04 my desktop (apple mini with i5-2415M CPU) failed to complete the boot process. A few seconds into the boot, the last message displayed is "/var mounted". The system then appears to hang indefinitely. Luckily, the 'rescue' boot image allows the boot process to proceed sufficiently far to allow a root shell to be spawned. Unfortunately no log files were written during the unsuccessful attempts to boot. Spawning a 2nd root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to observe the message 'systemd freezing execution' after I closed the first root shell and resumed the boot process. Further a core file was created (belonging to /sbin/init) in the root fs --8<-- (gdb) bt #0 0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78 #1 0x563b957223b7 in ?? () #2 #3 __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103 #4 0x563b9577c22e in ?? () #5 0x563b957672d6 in ?? () #6 0x563b9576ba22 in ?? () #7 0x563b9574f51a in ?? () #8 0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so #9 0x7f16803a53ea in sd_event_dispatch () from /lib/systemd/libsystemd-shared-237.so #10 0x7f16803a5579 in sd_event_run () from /lib/systemd/libsystemd-shared-237.so #11 0x563b9572a49d in ?? () #12 0x563b9571560c in ?? () #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, argv=0x7ffe78153758, init=, fini=, rtld_fini=, stack_end=0x7ffe78153748) at ../csu/libc-start.c:310 #14 0x563b957164fa in ?? () (gdb) -->8-- and the kernel message buffer lists --8<-- traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 error:0 in libc-2.27.so[7f17ebed7000+1e7000] -->8-- . To me that looked a bit like Bug 669702 of Gentoo (https://bugs.gentoo.org/669702) and indeed one of the (few) updates applied just prior the reboot was the update of libseccomp. I was able to circumvent the problem by disabling (commenting out) the syscall filtering requested by systemd (on my system, only /etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be modified). --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-30 (460 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Apple Inc. Macmini5,1 NonfreeKernelModules: wl Package: systemd 237-3ubuntu10.41 [modified: lib/systemd/system/systemd-resolved.service] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B10.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version:
[Touch-packages] [Bug 1881972] Re: systemd-networkd crashes with invalid pointer
This bug was fixed in the package systemd - 237-3ubuntu10.42
---
systemd (237-3ubuntu10.42) bionic; urgency=medium
[ Dan Streetman ]
*
d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,
d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch,
d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch:
- Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier
(LP: #1860926)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e
* d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
(LP: #1876018)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc
* d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch:
- Avoid double-free by strdup'ing iif/oif strings for new policy rules
(LP: #1881972)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483
* d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch
- Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f
*
d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch,
d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch:
- Try unmounting even if ro-remount fails, and don't bother remounting
api/ro fs
(LP: #1832754)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216
[ Alex Murray, Jamie Strandboge ]
* d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch:
- Fix free of uninitialized pointer (LP: #1886115)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8
-- Dan Streetman Wed, 08 Jul 2020 14:59:14
-0400
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => 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/1881972
Title:
systemd-networkd crashes with invalid pointer
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Bug description:
[impact]
systemd-networkd double-free causes crash under some circumstances,
such as adding/removing ip rules
[test case]
Use networkd-dispatcher events to add and remove IP rules. The example
scripts below are contrived (and by themselves likely to break access
to a machine) but would be adequate to trigger the bug. Put scripts
like these in place, reboot or run "netplan apply", and then leave the
machine running for a few DHCP renewal cycles.
=== /etc/networkd-dispatcher/configured.d/test.sh ===
#!/bin/bash
/sbin/ip rule add iif lo lookup 99
/sbin/ip rule add to 10.0.0.0/8 iif lo lookup main
=== END ===
=== /etc/networkd-dispatcher/configuring.d/test.sh ===
#!/bin/bash
# Tear down existing ip rules so they aren't duplicated
OLDIFS="${IFS}"
IFS="
"
for rule in `ip rule show|grep "iif lo" | cut -d: -f2-`; do
IFS="${OLDIFS}"
ip rule delete ${rule}
done
IFS="${OLDIFS}"
=== END ===
[regression potential]
this strdup's strings during addition of routing policy rules, so any
regression would likely occur when adding/modifying/removing ip rules,
possibly including networkd segfault or failure to add/remove/modify
ip rules.
[scope]
this is needed for bionic.
this is fixed by upstream commit
eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in
v240, so this is already included in Focal and later.
I did not research what original commit introduced the problem, but
the reporter indicates this did not happen for Xenial so it's unlikely
this is a problem in Xenial or earlier.
[original description]
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-
ssd/ubuntu-bionic-18.04-amd64-server-20200131 with
systemd-237-3ubuntu10.33 does NOT have the problem, but the next most
recent AWS AMI ubuntu/images/hvm-ssd/ubuntu-
bionic-18.04-amd64-server-20200311 with systemd-including
237-3ubuntu10.39 does.
Also, a system booted from the (good) 20200131 AMI starts showing the
problem after updating only systemd (to 237-3ubuntu10.41) and its
direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly
confident that a change to the
[Touch-packages] [Bug 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters
This bug was fixed in the package systemd - 237-3ubuntu10.42
---
systemd (237-3ubuntu10.42) bionic; urgency=medium
[ Dan Streetman ]
*
d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,
d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch,
d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch:
- Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier
(LP: #1860926)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e
* d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
(LP: #1876018)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc
* d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch:
- Avoid double-free by strdup'ing iif/oif strings for new policy rules
(LP: #1881972)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483
* d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch
- Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f
*
d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch,
d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch:
- Try unmounting even if ro-remount fails, and don't bother remounting
api/ro fs
(LP: #1832754)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216
[ Alex Murray, Jamie Strandboge ]
* d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch:
- Fix free of uninitialized pointer (LP: #1886115)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8
-- Dan Streetman Wed, 08 Jul 2020 14:59:14
-0400
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => 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/1876018
Title:
40-vm-hotadd.rules attempts to set non-existent sysfs parameters
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
In Progress
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
40-vm-hotadd.rules unconditionally tries onlining memory, which
results in logged error messages if the memory is already online
[test case]
since this rules file restricts operation to only hyper-v or xen
guests, boot a hyper-v or xen vm guest, and check for logged error
msgs like:
Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
alternately, to test on a vm guest other than hyper-v or xen,
comment/remove the 'GOTO="vm_hotadd_end"' line from the rules file and
reboot.
[regression potential]
as this adds a check before attempting to online memory for hyper-v
and xen vm guests, any regression would likely involve failure to
correctly online all memory on those guest platforms.
[scope]
this rule has been around for a long time, so is needed for x/b/f/g.
[original description]
In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
resulting in warnings such as:
Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument
Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
removed, or something else. This behavior is present on systems
upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
first reboot of the VM.
udev: 245.4-4ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+subscriptions
--
Mailing list: https://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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
This bug was fixed in the package systemd - 237-3ubuntu10.42 --- systemd (237-3ubuntu10.42) bionic; urgency=medium [ Dan Streetman ] * d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch, d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch, d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch: - Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier (LP: #1860926) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e * d/e/rules-ubuntu/40-vm-hotadd.rules: - Hotadd only offline memory and CPUs (LP: #1876018) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc * d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch: - Avoid double-free by strdup'ing iif/oif strings for new policy rules (LP: #1881972) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483 * d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch - Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f * d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch, d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch: - Try unmounting even if ro-remount fails, and don't bother remounting api/ro fs (LP: #1832754) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216 [ Alex Murray, Jamie Strandboge ] * d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch: - Fix free of uninitialized pointer (LP: #1886115) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8 -- Dan Streetman Wed, 08 Jul 2020 14:59:14 -0400 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => 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/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [test case, pre-focal] same netplan as above. Reboot, and the bridge should have its address and route: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever ubuntu@test-e:~$ ip r default via 192.168.0.1 dev br0 proto static linkdown 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown add and remove carrier, by adding and removing a slave interface: ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::5411:daff:fe23:bb93/64 scope link
[Touch-packages] [Bug 1832754] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1832754 Title: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [impact] shutdown sometimes fails to unmount some fs, which causes shutdown hang [test case] it's unclear what the specific configuration is to be able to reproduce this, but there are some examples in the upstream bug [regression potential] as this adjusts shutdown umounting, any regression would likely involve either failure to unmount some filesystems on shutdown and/or failure to shutdown the system. [scope] this is needed for b. this is fixed upstream by PR 8429 which is included starting in v239, so this is fixed already in Focal and later. this was caused by upstream commit d5641e0d7e8 which was added in v236, so this bug is not present in x. [original description] I am using Xubuntu 18.04 64 bit and got "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. systemd: 237-3ubuntu10.22 It's this issue: https://github.com/systemd/systemd/issues/8155 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881972] Update Released
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1881972
Title:
systemd-networkd crashes with invalid pointer
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Bug description:
[impact]
systemd-networkd double-free causes crash under some circumstances,
such as adding/removing ip rules
[test case]
Use networkd-dispatcher events to add and remove IP rules. The example
scripts below are contrived (and by themselves likely to break access
to a machine) but would be adequate to trigger the bug. Put scripts
like these in place, reboot or run "netplan apply", and then leave the
machine running for a few DHCP renewal cycles.
=== /etc/networkd-dispatcher/configured.d/test.sh ===
#!/bin/bash
/sbin/ip rule add iif lo lookup 99
/sbin/ip rule add to 10.0.0.0/8 iif lo lookup main
=== END ===
=== /etc/networkd-dispatcher/configuring.d/test.sh ===
#!/bin/bash
# Tear down existing ip rules so they aren't duplicated
OLDIFS="${IFS}"
IFS="
"
for rule in `ip rule show|grep "iif lo" | cut -d: -f2-`; do
IFS="${OLDIFS}"
ip rule delete ${rule}
done
IFS="${OLDIFS}"
=== END ===
[regression potential]
this strdup's strings during addition of routing policy rules, so any
regression would likely occur when adding/modifying/removing ip rules,
possibly including networkd segfault or failure to add/remove/modify
ip rules.
[scope]
this is needed for bionic.
this is fixed by upstream commit
eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in
v240, so this is already included in Focal and later.
I did not research what original commit introduced the problem, but
the reporter indicates this did not happen for Xenial so it's unlikely
this is a problem in Xenial or earlier.
[original description]
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-
ssd/ubuntu-bionic-18.04-amd64-server-20200131 with
systemd-237-3ubuntu10.33 does NOT have the problem, but the next most
recent AWS AMI ubuntu/images/hvm-ssd/ubuntu-
bionic-18.04-amd64-server-20200311 with systemd-including
237-3ubuntu10.39 does.
Also, a system booted from the (good) 20200131 AMI starts showing the
problem after updating only systemd (to 237-3ubuntu10.41) and its
direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly
confident that a change to the systemd package between
237-3ubuntu10.33 and 237-3ubuntu10.39 introduced the problem and it is
still present.
On the NAT router I use three interfaces and have separate routing
tables for admin and forwarded traffic. Things come up fine initially
but every 30-60 minutes (DHCP lease renewal time?) one or more
interfaces is reconfigured and most of the time systemd-networkd will
crash and need to be restarted. Eventually the system becomes
unreachable when the default crash loop backoff logic prevents the
network service from being restarted at all. The log excerpt attached
illustrates the crash loop.
Also including the netplan and networkd config files below.
# grep . /etc/netplan/*
/etc/netplan/50-cloud-init.yaml:# This file is generated from information
provided by the datasource. Changes
/etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance
reboot. To disable cloud-init's
/etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a
file
/etc/netplan/50-cloud-init.yaml:#
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
/etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
/etc/netplan/50-cloud-init.yaml:network:
/etc/netplan/50-cloud-init.yaml:version: 2
/etc/netplan/50-cloud-init.yaml:ethernets:
/etc/netplan/50-cloud-init.yaml:ens5:
/etc/netplan/50-cloud-init.yaml:dhcp4: true
/etc/netplan/50-cloud-init.yaml:match:
/etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
/etc/netplan/50-cloud-init.yaml:set-name: ens5
/etc/netplan/99_config.yaml:network:
/etc/netplan/99_config.yaml: version: 2
/etc/netplan/99_config.yaml: renderer: networkd
/etc/netplan/99_config.yaml: ethernets:
/etc/netplan/99_config.yaml:ens6:
/etc/netplan/99_config.yaml:
[Touch-packages] [Bug 1832754] Re: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs.
This bug was fixed in the package systemd - 237-3ubuntu10.42 --- systemd (237-3ubuntu10.42) bionic; urgency=medium [ Dan Streetman ] * d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch, d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch, d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch: - Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier (LP: #1860926) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e * d/e/rules-ubuntu/40-vm-hotadd.rules: - Hotadd only offline memory and CPUs (LP: #1876018) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc * d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch: - Avoid double-free by strdup'ing iif/oif strings for new policy rules (LP: #1881972) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483 * d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch - Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f * d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch, d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch: - Try unmounting even if ro-remount fails, and don't bother remounting api/ro fs (LP: #1832754) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216 [ Alex Murray, Jamie Strandboge ] * d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch: - Fix free of uninitialized pointer (LP: #1886115) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8 -- Dan Streetman Wed, 08 Jul 2020 14:59:14 -0400 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => 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/1832754 Title: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [impact] shutdown sometimes fails to unmount some fs, which causes shutdown hang [test case] it's unclear what the specific configuration is to be able to reproduce this, but there are some examples in the upstream bug [regression potential] as this adjusts shutdown umounting, any regression would likely involve either failure to unmount some filesystems on shutdown and/or failure to shutdown the system. [scope] this is needed for b. this is fixed upstream by PR 8429 which is included starting in v239, so this is fixed already in Focal and later. this was caused by upstream commit d5641e0d7e8 which was added in v236, so this bug is not present in x. [original description] I am using Xubuntu 18.04 64 bit and got "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. systemd: 237-3ubuntu10.22 It's this issue: https://github.com/systemd/systemd/issues/8155 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832754/+subscriptions -- Mailing list: https://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 1886197] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1886197 Title: FTBFS in b due to libseccomp change Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [impact] systemd FTBFS in b because __NR__sysctl was force-defined by libseccomp in 2.4.1-0ubuntu0.18.04.2, but that force-defining was (correctly) reverted in the latest version 2.4.3-1ubuntu3.18.04.2. On arm64, __NR__sysctl is not defined, so the build now fails, e.g.: https://launchpadlibrarian.net/486997294/buildlog_ubuntu-bionic-arm64.systemd_237-3ubuntu10.42~202007031245~ubuntu18.04.1_BUILDING.txt.gz ../src/test/test-seccomp.c: In function ‘test_protect_sysctl’: ../src/test/test-seccomp.c:251:5: error: "__NR__sysctl" is not defined, evaluates to 0 [-Werror=undef] #if __NR__sysctl > 0 ^~~~ [test case] build systemd on bionic with latest packages (i.e. with latest libseccomp2 package) [regression potential] this adds a defined() check before comparing the __NR__sysctl value, so any regression would be limited to the specific function test_protect_sysctl() which is part of the test framework, thus leading to a failed build or incorrectly passed/failed test. [scope] this is needed only in Bionic. This is fixed upstream by commit 4df8fe8415eaf4abd5b93c3447452547c6ea9e5f which is included in v244 and later, so this is fixed already for Focal and later. Xenial does not include the __NR__sysctl check so does not need this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1886197/+subscriptions -- Mailing list: https://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 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot
This bug was fixed in the package systemd - 237-3ubuntu10.42 --- systemd (237-3ubuntu10.42) bionic; urgency=medium [ Dan Streetman ] * d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch, d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch, d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch: - Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier (LP: #1860926) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e * d/e/rules-ubuntu/40-vm-hotadd.rules: - Hotadd only offline memory and CPUs (LP: #1876018) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc * d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch: - Avoid double-free by strdup'ing iif/oif strings for new policy rules (LP: #1881972) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483 * d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch - Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f * d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch, d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch: - Try unmounting even if ro-remount fails, and don't bother remounting api/ro fs (LP: #1832754) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216 [ Alex Murray, Jamie Strandboge ] * d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch: - Fix free of uninitialized pointer (LP: #1886115) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8 -- Dan Streetman Wed, 08 Jul 2020 14:59:14 -0400 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => 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/1886115 Title: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot Status in libseccomp package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Fix Released Status in libseccomp source package in Bionic: New Status in systemd source package in Bionic: Fix Released Bug description: [impact] systemd sometimes crashes on boot due to free of uninitalized var [test case] a specific system setup is required, see original description [regression potential] any regression would likely involve further crashes on boot. [scope] this is needed in b. this is fixed upstream by commit 58d9d89b4b41189bdcea86c2ad5cf708b7d54aca which is included starting in v240, so this is included already in f and later. this is caused by commit 25cd49647c8 which is included starting in v237, so this bug does not exist in x. [original description] After applying updates to Ubuntu 18.04 my desktop (apple mini with i5-2415M CPU) failed to complete the boot process. A few seconds into the boot, the last message displayed is "/var mounted". The system then appears to hang indefinitely. Luckily, the 'rescue' boot image allows the boot process to proceed sufficiently far to allow a root shell to be spawned. Unfortunately no log files were written during the unsuccessful attempts to boot. Spawning a 2nd root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to observe the message 'systemd freezing execution' after I closed the first root shell and resumed the boot process. Further a core file was created (belonging to /sbin/init) in the root fs --8<-- (gdb) bt #0 0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78 #1 0x563b957223b7 in ?? () #2 #3 __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103 #4 0x563b9577c22e in ?? () #5 0x563b957672d6 in ?? () #6 0x563b9576ba22 in ?? () #7 0x563b9574f51a in ?? () #8 0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so #9 0x7f16803a53ea in sd_event_dispatch () from /lib/systemd/libsystemd-shared-237.so #10 0x7f16803a5579 in sd_event_run () from /lib/systemd/libsystemd-shared-237.so #11 0x563b9572a49d in ?? () #12 0x563b9571560c in ?? () #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, argv=0x7ffe78153758, init=, fini=, rtld_fini=,
[Touch-packages] [Bug 1886197] Re: FTBFS in b due to libseccomp change
This bug was fixed in the package systemd - 237-3ubuntu10.42 --- systemd (237-3ubuntu10.42) bionic; urgency=medium [ Dan Streetman ] * d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch, d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch, d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch: - Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier (LP: #1860926) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e * d/e/rules-ubuntu/40-vm-hotadd.rules: - Hotadd only offline memory and CPUs (LP: #1876018) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc * d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch: - Avoid double-free by strdup'ing iif/oif strings for new policy rules (LP: #1881972) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483 * d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch - Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f * d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch, d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch: - Try unmounting even if ro-remount fails, and don't bother remounting api/ro fs (LP: #1832754) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216 [ Alex Murray, Jamie Strandboge ] * d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch: - Fix free of uninitialized pointer (LP: #1886115) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8 -- Dan Streetman Wed, 08 Jul 2020 14:59:14 -0400 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => 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/1886197 Title: FTBFS in b due to libseccomp change Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: [impact] systemd FTBFS in b because __NR__sysctl was force-defined by libseccomp in 2.4.1-0ubuntu0.18.04.2, but that force-defining was (correctly) reverted in the latest version 2.4.3-1ubuntu3.18.04.2. On arm64, __NR__sysctl is not defined, so the build now fails, e.g.: https://launchpadlibrarian.net/486997294/buildlog_ubuntu-bionic-arm64.systemd_237-3ubuntu10.42~202007031245~ubuntu18.04.1_BUILDING.txt.gz ../src/test/test-seccomp.c: In function ‘test_protect_sysctl’: ../src/test/test-seccomp.c:251:5: error: "__NR__sysctl" is not defined, evaluates to 0 [-Werror=undef] #if __NR__sysctl > 0 ^~~~ [test case] build systemd on bionic with latest packages (i.e. with latest libseccomp2 package) [regression potential] this adds a defined() check before comparing the __NR__sysctl value, so any regression would be limited to the specific function test_protect_sysctl() which is part of the test framework, thus leading to a failed build or incorrectly passed/failed test. [scope] this is needed only in Bionic. This is fixed upstream by commit 4df8fe8415eaf4abd5b93c3447452547c6ea9e5f which is included in v244 and later, so this is fixed already for Focal and later. Xenial does not include the __NR__sysctl check so does not need this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1886197/+subscriptions -- Mailing list: https://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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Same here Ununtu 20.04 with Anker Soundcore life Q10, what is worse it that ofono/phonesim can't be used properly, no stable version for Ubuntu 20.04 and no proper instructions to set it up... Please help!!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://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 1890411] Re: Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Was wrong package
** Package changed: apport (Ubuntu) => xorg-server (Ubuntu)
--
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/1890411
Title:
Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Status in xorg-server package in Ubuntu:
New
Bug description:
When ubuntu starts up, gdm3 does not start due to a crash in the the
xserver:
[ 1271.342] (II) SELinux: Disabled on system
[ 1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
[ 1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 1271.346] (II) AIGLX: Loaded and initialized i965
[ 1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1271.348] (II) modeset(0): Damage tracking initialized
[ 1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
[ 1271.352] (EE)
[ 1271.352] (EE) Backtrace:
[ 1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
[ 1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869)
[0x5649b579f869]
[ 1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
[ 1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
[ 1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
[ 1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
[ 1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
[ 1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
[ 1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
[ 1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
[ 1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
[ 1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03)
[0x5649b5721d03]
[ 1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f)
[0x5649b577fd1f]
[ 1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112)
[0x5649b577fa62]
[ 1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41)
[0x5649b568cc41]
[ 1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
[ 1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79)
[0x5649b5639e79]
[ 1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
[ 1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
[ 1271.352] (EE)
[ 1271.352] (EE) Segmentation fault at address 0x4
[ 1271.352] (EE)
Fatal server error:
[ 1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 1271.352] (EE)
[ 1271.352] (EE)
As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
specific package from version 20.0.8-0ubuntu1~18.04.1 back to
19.2.8-0ubuntu0~18.04.3.
This solves the problem. So I suspect that the problem is in this
specific package.
My machine is (uname):
4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux
(lspci)
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
(rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #3 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H81
[Touch-packages] [Bug 1863080] Re: Unable to use dead keys in Java apps
Upstream didn't acknowledge it as a valid bug, so we are back at square one. -- 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/1863080 Title: Unable to use dead keys in Java apps Status in ibus: Fix Released Status in ibus package in Ubuntu: Confirmed Bug description: This is same bug as #540751, as it happens again in Ubuntu 19.10 with Java 11. Way of reproduce it: - Fresh Ubuntu 19.10 install. - Install default-jre. - Download (for example) lastest NetBeans version. - Edit a file in NetBeans, you can't insert characters like 'á'. The workaround is the same, define XMODIFIERS='' before launching the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1863080/+subscriptions -- Mailing list: https://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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
@seb, I plan to upload the debdiff for focal, but how to handle the groovy? we will definitely upgrade those packages to higher version in the groovy sooner or later, do I need to upload debdiff for groovy as well? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch
[Touch-packages] [Bug 1890411] Re: Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1890411/+attachment/5398898/+files/Xorg.0.log.old
--
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/1890411
Title:
Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Status in apport package in Ubuntu:
New
Bug description:
When ubuntu starts up, gdm3 does not start due to a crash in the the
xserver:
[ 1271.342] (II) SELinux: Disabled on system
[ 1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
[ 1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 1271.346] (II) AIGLX: Loaded and initialized i965
[ 1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1271.348] (II) modeset(0): Damage tracking initialized
[ 1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
[ 1271.352] (EE)
[ 1271.352] (EE) Backtrace:
[ 1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
[ 1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869)
[0x5649b579f869]
[ 1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
[ 1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
[ 1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
[ 1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
[ 1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
[ 1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
[ 1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
[ 1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
[ 1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
[ 1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03)
[0x5649b5721d03]
[ 1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f)
[0x5649b577fd1f]
[ 1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112)
[0x5649b577fa62]
[ 1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41)
[0x5649b568cc41]
[ 1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
[ 1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79)
[0x5649b5639e79]
[ 1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xe7) [0x7f5c7ccd5b97]
[ 1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
[ 1271.352] (EE)
[ 1271.352] (EE) Segmentation fault at address 0x4
[ 1271.352] (EE)
Fatal server error:
[ 1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 1271.352] (EE)
[ 1271.352] (EE)
As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
specific package from version 20.0.8-0ubuntu1~18.04.1 back to
19.2.8-0ubuntu0~18.04.3.
This solves the problem. So I suspect that the problem is in this
specific package.
My machine is (uname):
4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux
(lspci)
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
(rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #3 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB
[Touch-packages] [Bug 1863080] Re: Unable to use dead keys in Java apps
it's not marked as fixed in Ubuntu, it's just an automaking reflection of the status of https://github.com/ibus/ibus/issues/2237 upstream -- 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/1863080 Title: Unable to use dead keys in Java apps Status in ibus: Fix Released Status in ibus package in Ubuntu: Confirmed Bug description: This is same bug as #540751, as it happens again in Ubuntu 19.10 with Java 11. Way of reproduce it: - Fresh Ubuntu 19.10 install. - Install default-jre. - Download (for example) lastest NetBeans version. - Edit a file in NetBeans, you can't insert characters like 'á'. The workaround is the same, define XMODIFIERS='' before launching the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1863080/+subscriptions -- Mailing list: https://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 1890411] [NEW] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
Public bug reported:
When ubuntu starts up, gdm3 does not start due to a crash in the the
xserver:
[ 1271.342] (II) SELinux: Disabled on system
[ 1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
[ 1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 1271.346] (II) AIGLX: Loaded and initialized i965
[ 1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 1271.348] (II) modeset(0): Damage tracking initialized
[ 1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
[ 1271.352] (EE)
[ 1271.352] (EE) Backtrace:
[ 1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
[ 1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869)
[0x5649b579f869]
[ 1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
[ 1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
[ 1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
[ 1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
[ 1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
[ 1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
[ 1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
[ 1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
[ 1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
[ 1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03)
[0x5649b5721d03]
[ 1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f) [0x5649b577fd1f]
[ 1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112)
[0x5649b577fa62]
[ 1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41)
[0x5649b568cc41]
[ 1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
[ 1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79)
[0x5649b5639e79]
[ 1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7)
[0x7f5c7ccd5b97]
[ 1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
[ 1271.352] (EE)
[ 1271.352] (EE) Segmentation fault at address 0x4
[ 1271.352] (EE)
Fatal server error:
[ 1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 1271.352] (EE)
[ 1271.352] (EE)
As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
specific package from version 20.0.8-0ubuntu1~18.04.1 back to
19.2.8-0ubuntu0~18.04.3.
This solves the problem. So I suspect that the problem is in this
specific package.
My machine is (uname):
4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux
(lspci)
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
(rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI
Express Root Port #3 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H81 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family
6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus
Controller (rev 05)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 0c)
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
[Touch-packages] [Bug 1890170] Re: ImportError libstdc++.so.6 cannot allocate memory after importing PyQt5.Qt PyQt5.QtCore and cv2
*** This bug is a duplicate of bug 1889851 *** https://bugs.launchpad.net/bugs/1889851 I have the same issue while running python-qgis. I don't know how (or IF) it is related, but here's the log never the less: even@even-ThinkPad-P53:~$ qgis --version QGIS 3.14.1-Pi 'Pi' (de08d6b71d) even@even-ThinkPad-P53:~$ python3 --version Python 3.8.2 even@even-ThinkPad-P53:~$ python3 Python 3.8.2 (default, Jul 16 2020, 14:00:26) [GCC 9.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import qgis >>> from qgis import core Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/qgis/core/__init__.py", line 25, in from qgis._core import * ImportError: /lib/x86_64-linux-gnu/libstdc++.so.6: cannot allocate memory in static TLS block >>> -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1890170 Title: ImportError libstdc++.so.6 cannot allocate memory after importing PyQt5.Qt PyQt5.QtCore and cv2 Status in mysql-8.0 package in Ubuntu: Confirmed Status in opencv package in Ubuntu: Confirmed Status in pyqt5 package in Ubuntu: Confirmed Bug description: I'm using an updated Lubuntu focal. Starting maybe last week (monday July 27th), if in python3 I do from PyQt5 import Qt, QtCore import cv2 I get ImportError: /lib/x86_64-linux-gnu/libstdc++.so.6: cannot allocate memory in static TLS block I noticed only now that the reverse (first import cv2, then Qt, QtCore) seems to work correctly and displays no errors. I'm afraid I might not be able to do the reverse in my real software... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon Aug 3 17:49:20 2020 InstallationDate: Installed on 2020-07-15 (19 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890170/+subscriptions -- Mailing list: https://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 1890390] Re: Xorg freeze
When the problem happens, can you still move the mouse cursor? Also, next time a freeze happens please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Tags added: nouveau ** Summary changed: - Xorg freeze + [nouveau] Xorg freeze ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1890390 Title: [nouveau] Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: The screen freezes especially when I am using Zoom. If I minimise the Zoom window or shorten it to a small size, the screen does not freeze. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 16:41:20 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GK107GL [Quadro K600] [10de:0ffa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK107GL [Quadro K600] [10de:094b] InstallationDate: Installed on 2020-04-07 (119 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Precision T1700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60b287f6-f7bb-4e75-a4b3-61468b59150b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.asset.tag: MU00042259 dmi.board.name: 04JGCK dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.asset.tag: MU00042259 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd06/06/2013:svnDellInc.:pnPrecisionT1700:pvr01:rvnDellInc.:rn04JGCK:rvrA02:cvnDellInc.:ct15:cvr: dmi.product.name: Precision T1700 dmi.product.sku: Precision T1700 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 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/+source/xorg-server/+bug/1890390/+subscriptions -- Mailing list: https://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 1890047] Re: Sessions crash, all X11 remote users disconnected
** Changed in: glib-networking (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1890047 Title: Sessions crash, all X11 remote users disconnected Status in glib-networking package in Ubuntu: Incomplete Bug description: Hello, I have a Ubuntu 16.04.6 LTS (Xenial Xerus) used by many X11 remote user. When upgrading to glib-networking, glib-networking-common and lib- networking-services to 2.48.2-1~ubuntu16.04.2; all sessions crash randomly at the same time many times a day. When it happens, all users are disconnected and it looks like lightdm is restarted. Downgrading to 2.48.2-1~ubuntu16.04.1 resolve the problem. X11 terminals were not upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1890047/+subscriptions -- Mailing list: https://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 1890390] [NEW] Xorg freeze
Public bug reported: The screen freezes especially when I am using Zoom. If I minimise the Zoom window or shorten it to a small size, the screen does not freeze. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 16:41:20 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GK107GL [Quadro K600] [10de:0ffa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK107GL [Quadro K600] [10de:094b] InstallationDate: Installed on 2020-04-07 (119 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Precision T1700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60b287f6-f7bb-4e75-a4b3-61468b59150b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.asset.tag: MU00042259 dmi.board.name: 04JGCK dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.asset.tag: MU00042259 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd06/06/2013:svnDellInc.:pnPrecisionT1700:pvr01:rvnDellInc.:rn04JGCK:rvrA02:cvnDellInc.:ct15:cvr: dmi.product.name: Precision T1700 dmi.product.sku: Precision T1700 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 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 freeze 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/1890390 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: The screen freezes especially when I am using Zoom. If I minimise the Zoom window or shorten it to a small size, the screen does not freeze. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 16:41:20 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GK107GL [Quadro K600] [10de:0ffa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK107GL [Quadro K600] [10de:094b] InstallationDate: Installed on 2020-04-07 (119 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Precision T1700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=60b287f6-f7bb-4e75-a4b3-61468b59150b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.asset.tag: MU00042259 dmi.board.name: 04JGCK dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.asset.tag: MU00042259 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd06/06/2013:svnDellInc.:pnPrecisionT1700:pvr01:rvnDellInc.:rn04JGCK:rvrA02:cvnDellInc.:ct15:cvr: dmi.product.name: Precision T1700 dmi.product.sku: Precision T1700 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx
[Touch-packages] [Bug 1890384] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg crash + Crash -- 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/1890384 Title: Crash Status in Ubuntu: Incomplete Bug description: ls -l /var/crash backport-iwlwifi-dkms.0.crash _opt_google_chrome_chrome.1000.crash _usr_bin_gnome-control-center.1000.crash ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 09:12:04 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 7906: added rtl8812au, 5.6.4.2~ppa: added ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 510 [1043:8694] InstallationDate: Installed on 2018-12-21 (592 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0026 SiGma Micro Keyboard Bus 001 Device 003: ID 062a: Creative Labs Optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-111-generic root=UUID=239295ef-655d-4e9d-986a-bc396201c864 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3408 dmi.board.asset.tag: Default string dmi.board.name: H110M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3408:bd09/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 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/1890384/+subscriptions -- Mailing list: https://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 1890384] [NEW] Xorg crash
Public bug reported: ls -l /var/crash backport-iwlwifi-dkms.0.crash _opt_google_chrome_chrome.1000.crash _usr_bin_gnome-control-center.1000.crash ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 09:12:04 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 7906: added rtl8812au, 5.6.4.2~ppa: added ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 510 [1043:8694] InstallationDate: Installed on 2018-12-21 (592 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0026 SiGma Micro Keyboard Bus 001 Device 003: ID 062a: Creative Labs Optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-111-generic root=UUID=239295ef-655d-4e9d-986a-bc396201c864 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3408 dmi.board.asset.tag: Default string dmi.board.name: H110M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3408:bd09/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 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 crash 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/1890384 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: ls -l /var/crash backport-iwlwifi-dkms.0.crash _opt_google_chrome_chrome.1000.crash _usr_bin_gnome-control-center.1000.crash ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 09:12:04 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 7906: added rtl8812au, 5.6.4.2~ppa: added ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 510 [1043:8694] InstallationDate: Installed on 2018-12-21 (592 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0026 SiGma Micro Keyboard Bus 001 Device 003: ID 062a: Creative Labs Optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-111-generic root=UUID=239295ef-655d-4e9d-986a-bc396201c864 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably
