[Touch-packages] [Bug 1886729] Re: Dell displayport YJ3Y6 adapter doesn't drive 4K screen properly
You certainly seem to have the latest and greatest Intel GPU which should support 4K up to 120Hz: https://ark.intel.com/content/www/us/en/ark/products/196597/intel- core-i7-1065g7-processor-8m-cache-up-to-3-90-ghz.html So I suspect using "adapters" is the main issue. If you can then please try to get a Thunderbolt-to-DisplayPort CABLE. The Thunderbolt end looks like USB-C but it's much more capable and can carry a full-speed DisplayPort signal. This is probably not a software bug, or if it is then probably not one we need to worry about if you just get a different cable. In the meantime you might want to try selecting 'Ubuntu on Wayland' from the login screen to see if the experience is any different there. ** 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/1886729 Title: Dell displayport YJ3Y6 adapter doesn't drive 4K screen properly Status in xorg-server package in Ubuntu: Incomplete Bug description: I have some early dell 4k 60hz screens - the ones which report 2 panels internally for DP 60Hz - horrid hack I know; I recently got a new XPS laptop and put Ubuntu on it. That XPS laptop has two USB-C/thunderbolt ports, so to drive the screens I bought two slightly different DP adapters - one with power passthrough, and a cheaper one that only does DP. The more expensive one 'USB-C to HDMI/DP' drives the monitor happily over DP, though sadly only at 30Hz - can't have everything :/. It reports one monitor as one output: DP-1 in the attached information: DP-1 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 527mm x 296mm 3840x2160 29.98*+ 30.0029.97 1920x1200 59.88 ... The cheaper one reports the single monitor as two distinct outputs, at 60hz interestingly - DP-3-8 connected (normal left inverted right x axis y axis) 1920x2160 59.99 + DP-3-9 connected 1920x2160+7680+0 (normal left inverted right x axis y axis) 527mm x 296mm 1920x2160 59.99*+ 1920x1200 59.88 which in theory if summed together would be one whole screen. But attempting to configure the output results in an error: xrandr --output DP-1 --auto --left-of eDP-1 --output DP-3-9 --auto --right-of DP-3-8 --output DP-3-8 --auto --right-of eDP-1 xrandr: cannot find crtc for output DP-3-8 I'm not sure if this is an intrinsic limitation of the USB-C->DP dongle, or whether there is something that can be done in the software to deal with this 10 year old hardware hack I have sitting on my desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 8 11:20:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Plus Graphics G7 [1028:096d] InstallationDate: Installed on 2020-07-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Touch-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
Ubuntu 19.10 is reaching end-of-life within days from now: https://wiki.ubuntu.com/Releases Please reproduce the bug on either 18.04 or 20.04 and then report a new bug from that machine by running: ubuntu-bug bluez ** Changed in: bluez (Ubuntu) Status: New => Won't Fix -- 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/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Won't Fix Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer
[Touch-packages] [Bug 1886696] Re: [Vostro 5490, Realtek ALC3204, Speaker, Internal] Pulseaudio fails to detect card
** Package changed: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1886696 Title: [Vostro 5490, Realtek ALC3204, Speaker, Internal] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Bug description: I have ubuntu Ubuntu 20.04 LTS installed, together with windows (dual boot) on my laptop. There is no sound at all, seems like Pulseaudio / Alsa dont recognize the sound card: $ pacmd list-cards 0 card(s) available. dmesg shows errors of sof-audio-pci: $ dmesg [ 13.313523] sof-audio-pci :00:1f.3: error: hw params ipc failed for stream 2 [ 13.313524] sof-audio-pci :00:1f.3: ASoC: :00:1f.3 hw params failed: -22 [ 13.313525] HDA Analog: ASoC: hw_params FE failed -22 [ 13.313883] sof-audio-pci :00:1f.3: error: ipc error for 0x6001 size 20 [ 13.313884] sof-audio-pci :00:1f.3: error: hw params ipc failed for stream 2 [ 13.313884] sof-audio-pci :00:1f.3: ASoC: :00:1f.3 hw params failed: -22 [ 13.313885] HDA Analog: ASoC: hw_params FE failed -22 [ 13.314249] sof-audio-pci :00:1f.3: error: ipc error for 0x6001 size 20 [ 13.314249] sof-audio-pci :00:1f.3: error: hw params ipc failed for stream 2 [ 13.314250] sof-audio-pci :00:1f.3: ASoC: :00:1f.3 hw params failed: -22 [ 13.314250] HDA Analog: ASoC: hw_params FE failed -22 . [10706.102325] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 pci device: $ lspci -nnk ... 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] Subsystem: Dell Device [1028:0959] Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci ... There was actually already a sound problem when I had ubuntu 18.04 - The sound worked after ubuntu got up, but then at some point the sound just died, with some different messages on dmesg. I upgraded the kernel and ubuntu version in hope it will solve the problem, but seems like it only got worse. Sound works in windows on the same laptop without issues. My attempts so far, which didnt yield anything 1. reinstall and upgrae linux-firmware. currently 'linux-firmware/focal-updates,focal-updates,now 1.187.1 all [installed]' 2. adding those line to /etc/modprobe.d/alsa-base.conf: options snd-hda-intel model=auto options snd-hda-intel dmic_detect=0 also, when I run 'alsa force-reload' the system just totally crashes, forcing me to press the power button to shut it off. Extra info $ inxi -Fxlpoz System:Kernel: 5.4.0-40-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.2 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 5490 v: N/A serial: Mobo: Dell model: 05P6R7 v: A00 serial: UEFI: Dell v: 1.5.1 date: 01/14/2020 Battery: ID-1: BAT0 charge: 40.7 Wh condition: 40.7/42.0 Wh (97%) model: SMP DELL VM73283 status: Full CPU: Topology: Quad Core model: Intel Core i5-10210U bits: 64 type: MT MCP arch: Kaby Lake rev: C L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 33599 Speed: 600 MHz min/max: 400/4200 MHz Core speeds (MHz): 1: 600 2: 600 3: 600 4: 600 5: 600 6: 600 7: 600 8: 600 Graphics: Device-1: Intel UHD Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz, 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.0.4 direct render: Yes Audio: Device-1: Intel vendor: Dell driver: sof-audio-pci bus ID: 00:1f.3 Sound Server: ALSA v: k5.4.0-40-generic Network: Device-1: Intel Wireless-AC 9462 driver: iwlwifi v: kernel port: 4000 bus ID: 00:14.3 IF: wlp0s20f3 state: up mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus ID: 01:00.0 IF: enp1s0 state: down mac: Drives:Local Storage: total: 476.94 GiB used: 173.69 GiB (36.4%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe 512GB size: 476.94 GiB ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0',
[Touch-packages] [Bug 1886697] 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) => 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/1886697 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: Reproducible on my system. Whenever my computer "sleeps" while running a specific program (Phenix), when I return to check on the job, the Desktop screen does not load. Alt-F2 and other routes have not been successful in recovery the Desktop GUI or log-in. However, if I stay at my computer and prevent the computer from sleeping, the job completes without GUI death. I don't know how to search the syslog, but I expect to find something funky around something like "GUI going to sleep". The reason I think it is a true "crash" is, despite being away from my the PC for 1 hr, the job directory is empty. This makes me think the computer processes were halted during the events that lead to the GUI death. I have played with my GPU settings. As per this NVIDIA thread https://forums.developer.nvidia.com/t/random-xid-61-and-xorg-lock- up/79731/252, I have set my minumum clock speed to 1050mHz. This had been successful up until this point at preventing a different issue not related to this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 13:26:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:13a2] InstallationDate: Installed on 2020-05-26 (41 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5a52a344-c840-428b-89b5-b3c2e86fbc43 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd.
[Touch-packages] [Bug 1886672] Re: Multiple screen display issues
Problems with locking the screen (and gnome-shell then crashing) lately have mostly been bug 184, which you don't seem to have the fix for... To get the fix please try: sudo apt update sudo apt full-upgrade Reboot and then verify your gnome-shell package is at least version 3.36.3. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (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/1886672 Title: Multiple screen display issues Status in gnome-shell package in Ubuntu: Incomplete Bug description: New bug for me. Issue was fine till last week. I think this may be related to the following as it started happening shortly thereafter. I have XPS13 with second monitor, all working fine till I lock screen or suspend. Then my second monitor will not 'resume'. I.e. stays off. This behaviour started after (or shortly after) playing a wine game using Lutris to launch. Shutting game down and almost immediately hitting suspend on the laptop. Was rushing out. It's a wild shot in the dark but I think something got messed up / not saved correctly in this process. To get it working I need to unplug monitor (using USB-C > HDMI) > suspend > plug in monitor > resume and sometimes still need to open display settings before it 'kicks in'. Damn annoying. Hope someone can help :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Jul 7 16:44:52 2020 DistUpgraded: 2020-05-15 15:17:42,708 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:082a] InstallationDate: Installed on 2019-01-29 (525 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-15 (53 days ago) dmi.bios.date: 11/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0PVG6D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 082A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/gnome-shell/+bug/1886672/+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 1855350] Re: Will not logout or shutdown from guest-session
** Summary changed: - Will not logout or shutdown form guest-session + Will not logout or shutdown from guest-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1855350 Title: Will not logout or shutdown from guest-session Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: This is in Xubuntu 19.10, a regression from 18.04. xfce4-session 4.14.0-0ubuntu1. I enabled guest-session and logged in that. But there I can not log out or even shut down using the graphical way at least unless put Action Buttons on the panel and choose Switch User. If I run "xfce4-session-logout -l" I get error dialog saying: Received error while trying to log out GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs:Type of message, "(yb)", does not match expected type"(b)" And in standard output there is: "Received error while trying to log out, error was GDBus.Error:org.xfce.SessionManager.Error.Failed: Session manager must be in idle state when requesting a shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1855350/+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 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04
Sigh indeed. The ignoring of this bug report (and many other bad, bad decisions for that matter) has now lead us to just abandon Ubuntu entirely. Even for non-server desktop use cases. I have no idea if the original reported issue has ever actually been dealt with, and I guess I never will. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1771236 Title: forced use of systemd-networkd interferes with ifupdown in 18.04 Status in ifupdown package in Ubuntu: Expired Status in systemd package in Ubuntu: Expired Bug description: For several reasons, we are not able to use netplan nor systemd- networkd due to legacy applications that expect ifupdown's pre-up and post-up script mechanism. The documentation around 18.04's (premature, I feel) wholesale adoption of netplan claims that one can revert to old behaviour by merely installing ifupdown (amongst assertions that netplan will never offer a mechanism for configuring pre-up and post-up actions even for network managers that support them). However when ifupdown is installed, systemd-networkd still tries to manage interfaces. If you 'systemctl disable systemd-networkd', upon next reboot it is automatically re-enabled. We tried disabling any systemd units even remotely related to networking and yet systemd- networkd still runs. If it hasn't been configured, it tries to DHCP. On networks that don't provide DHCP this results in a stupendously long stall during boot. Currently it appears to be impossible to tell systemd-networkd not to run in a clean manner that won't get reverted on package upgrades. I sincerely hope this is is a bug/oversight and not intentional. We need to be able to disable systemd-networkd properly. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1771236/+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 1886696] Re: [Vostro 5490, Realtek ALC3204, Speaker, Internal] Pulseaudio fails to detect card
@Yakir, the dmesg in the #1 is not a complete one, could you please upload a new one (remove the "snd-intel-dspcfg.dsp_driver=1"). BTW, could you please try the kernel older than 5.4.0-40.44-generic like 5.4.0-39/38/37/... -- 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/1886696 Title: [Vostro 5490, Realtek ALC3204, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: I have ubuntu Ubuntu 20.04 LTS installed, together with windows (dual boot) on my laptop. There is no sound at all, seems like Pulseaudio / Alsa dont recognize the sound card: $ pacmd list-cards 0 card(s) available. dmesg shows errors of sof-audio-pci: $ dmesg [ 13.313523] sof-audio-pci :00:1f.3: error: hw params ipc failed for stream 2 [ 13.313524] sof-audio-pci :00:1f.3: ASoC: :00:1f.3 hw params failed: -22 [ 13.313525] HDA Analog: ASoC: hw_params FE failed -22 [ 13.313883] sof-audio-pci :00:1f.3: error: ipc error for 0x6001 size 20 [ 13.313884] sof-audio-pci :00:1f.3: error: hw params ipc failed for stream 2 [ 13.313884] sof-audio-pci :00:1f.3: ASoC: :00:1f.3 hw params failed: -22 [ 13.313885] HDA Analog: ASoC: hw_params FE failed -22 [ 13.314249] sof-audio-pci :00:1f.3: error: ipc error for 0x6001 size 20 [ 13.314249] sof-audio-pci :00:1f.3: error: hw params ipc failed for stream 2 [ 13.314250] sof-audio-pci :00:1f.3: ASoC: :00:1f.3 hw params failed: -22 [ 13.314250] HDA Analog: ASoC: hw_params FE failed -22 . [10706.102325] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 pci device: $ lspci -nnk ... 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] Subsystem: Dell Device [1028:0959] Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci ... There was actually already a sound problem when I had ubuntu 18.04 - The sound worked after ubuntu got up, but then at some point the sound just died, with some different messages on dmesg. I upgraded the kernel and ubuntu version in hope it will solve the problem, but seems like it only got worse. Sound works in windows on the same laptop without issues. My attempts so far, which didnt yield anything 1. reinstall and upgrae linux-firmware. currently 'linux-firmware/focal-updates,focal-updates,now 1.187.1 all [installed]' 2. adding those line to /etc/modprobe.d/alsa-base.conf: options snd-hda-intel model=auto options snd-hda-intel dmic_detect=0 also, when I run 'alsa force-reload' the system just totally crashes, forcing me to press the power button to shut it off. Extra info $ inxi -Fxlpoz System:Kernel: 5.4.0-40-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.2 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 5490 v: N/A serial: Mobo: Dell model: 05P6R7 v: A00 serial: UEFI: Dell v: 1.5.1 date: 01/14/2020 Battery: ID-1: BAT0 charge: 40.7 Wh condition: 40.7/42.0 Wh (97%) model: SMP DELL VM73283 status: Full CPU: Topology: Quad Core model: Intel Core i5-10210U bits: 64 type: MT MCP arch: Kaby Lake rev: C L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 33599 Speed: 600 MHz min/max: 400/4200 MHz Core speeds (MHz): 1: 600 2: 600 3: 600 4: 600 5: 600 6: 600 7: 600 8: 600 Graphics: Device-1: Intel UHD Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz, 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.0.4 direct render: Yes Audio: Device-1: Intel vendor: Dell driver: sof-audio-pci bus ID: 00:1f.3 Sound Server: ALSA v: k5.4.0-40-generic Network: Device-1: Intel Wireless-AC 9462 driver: iwlwifi v: kernel port: 4000 bus ID: 00:14.3 IF: wlp0s20f3 state: up mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus ID: 01:00.0 IF: enp1s0 state: down mac: Drives:Local Storage: total: 476.94 GiB used: 173.69 GiB (36.4%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe 512GB size: 476.94 GiB ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64
[Touch-packages] [Bug 1814302] Please test proposed package
Hello Yancy, or anyone else affected,
Accepted quassel into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/quassel/1:0.12.4-3ubuntu1.18.04.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1814302
Title:
Quasselcore apparmor profile issue in lxd container.
Status in AppArmor:
Invalid
Status in apparmor package in Ubuntu:
Invalid
Status in quassel package in Ubuntu:
Fix Released
Status in apparmor source package in Bionic:
Invalid
Status in quassel source package in Bionic:
Fix Committed
Status in apparmor source package in Focal:
Invalid
Status in quassel source package in Focal:
Fix Committed
Status in apparmor source package in Groovy:
Invalid
Status in quassel source package in Groovy:
Fix Released
Bug description:
[impact]
quasselcore cannot start inside lxd container
[test case]
create lxd container, install quassel-core, check quasselcore service:
$ systemctl status quasselcore
● quasselcore.service - distributed IRC client using a central core component
Loaded: loaded (/lib/systemd/system/quasselcore.service; enabled; vendor
preset: enabled)
Active: failed (Result: signal) since Tue 2020-06-30 18:32:40 UTC; 4s ago
Docs: man:quasselcore(1)
Process: 3853 ExecStart=/usr/bin/quasselcore --configdir=${DATADIR}
--logfile=${LOGFILE} --loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN}
(code=killed, signal=SEGV)
Main PID: 3853 (code=killed, signal=SEGV)
Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Scheduled
restart job, restart counter is at 7.
Jun 30 18:32:40 lp1814302-f systemd[1]: Stopped distributed IRC client using
a central core component.
Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Start request
repeated too quickly.
Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Failed with
result 'signal'.
Jun 30 18:32:40 lp1814302-f systemd[1]: Failed to start distributed IRC
client using a central core component.
Also, the binary will segfault when run directly due to apparmor denials:
$ /usr/bin/quasselcore
Segmentation fault
[760149.590802] audit: type=1400 audit(1593542073.962:1058):
apparmor="DENIED" operation="file_mmap" namespace="root//lxd-
lp1814302-f_" profile="/usr/bin/quasselcore"
name="/usr/bin/quasselcore" pid=2006430 comm="quasselcore"
requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100
[regression potential]
this expands the apparmor profile, so any regression would likely
involve problems while starting due to apparmor.
[scope]
this is needed for b/f/g.
this is also needed for e, but that is EOL in weeks and this is not
important enough to bother there.
[original description]
Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04
container. Everything up todate via apt.
Install quassel-core. Service will not start.
Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.
I then added "/usr/bin/quasselcore rm," to
"/etc/apparmor.d/usr.bin.quasselcore".
Set "aa-enforce /usr/bin/quasselcore". Restarted main host.
Quasselcore service now starts and I can connect to it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1814302/+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 1814302] Re: Quasselcore apparmor profile issue in lxd container.
Hello Yancy, or anyone else affected,
Accepted quassel into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/quassel/1:0.13.1-3ubuntu2.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: quassel (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-focal
** Changed in: quassel (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1814302
Title:
Quasselcore apparmor profile issue in lxd container.
Status in AppArmor:
Invalid
Status in apparmor package in Ubuntu:
Invalid
Status in quassel package in Ubuntu:
Fix Released
Status in apparmor source package in Bionic:
Invalid
Status in quassel source package in Bionic:
Fix Committed
Status in apparmor source package in Focal:
Invalid
Status in quassel source package in Focal:
Fix Committed
Status in apparmor source package in Groovy:
Invalid
Status in quassel source package in Groovy:
Fix Released
Bug description:
[impact]
quasselcore cannot start inside lxd container
[test case]
create lxd container, install quassel-core, check quasselcore service:
$ systemctl status quasselcore
● quasselcore.service - distributed IRC client using a central core component
Loaded: loaded (/lib/systemd/system/quasselcore.service; enabled; vendor
preset: enabled)
Active: failed (Result: signal) since Tue 2020-06-30 18:32:40 UTC; 4s ago
Docs: man:quasselcore(1)
Process: 3853 ExecStart=/usr/bin/quasselcore --configdir=${DATADIR}
--logfile=${LOGFILE} --loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN}
(code=killed, signal=SEGV)
Main PID: 3853 (code=killed, signal=SEGV)
Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Scheduled
restart job, restart counter is at 7.
Jun 30 18:32:40 lp1814302-f systemd[1]: Stopped distributed IRC client using
a central core component.
Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Start request
repeated too quickly.
Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Failed with
result 'signal'.
Jun 30 18:32:40 lp1814302-f systemd[1]: Failed to start distributed IRC
client using a central core component.
Also, the binary will segfault when run directly due to apparmor denials:
$ /usr/bin/quasselcore
Segmentation fault
[760149.590802] audit: type=1400 audit(1593542073.962:1058):
apparmor="DENIED" operation="file_mmap" namespace="root//lxd-
lp1814302-f_" profile="/usr/bin/quasselcore"
name="/usr/bin/quasselcore" pid=2006430 comm="quasselcore"
requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100
[regression potential]
this expands the apparmor profile, so any regression would likely
involve problems while starting due to apparmor.
[scope]
this is needed for b/f/g.
this is also needed for e, but that is EOL in weeks and this is not
important enough to bother there.
[original description]
Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04
container. Everything up todate via apt.
Install quassel-core. Service will not start.
Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.
I then added "/usr/bin/quasselcore rm," to
"/etc/apparmor.d/usr.bin.quasselcore".
Set "aa-enforce /usr/bin/quasselcore". Restarted main host.
Quasselcore service now starts and I can connect to it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1814302/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help :
[Touch-packages] [Bug 1886729] [NEW] Dell displayport YJ3Y6 adapter doesn't drive 4K screen properly
Public bug reported: I have some early dell 4k 60hz screens - the ones which report 2 panels internally for DP 60Hz - horrid hack I know; I recently got a new XPS laptop and put Ubuntu on it. That XPS laptop has two USB-C/thunderbolt ports, so to drive the screens I bought two slightly different DP adapters - one with power passthrough, and a cheaper one that only does DP. The more expensive one 'USB-C to HDMI/DP' drives the monitor happily over DP, though sadly only at 30Hz - can't have everything :/. It reports one monitor as one output: DP-1 in the attached information: DP-1 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 527mm x 296mm 3840x2160 29.98*+ 30.0029.97 1920x1200 59.88 ... The cheaper one reports the single monitor as two distinct outputs, at 60hz interestingly - DP-3-8 connected (normal left inverted right x axis y axis) 1920x2160 59.99 + DP-3-9 connected 1920x2160+7680+0 (normal left inverted right x axis y axis) 527mm x 296mm 1920x2160 59.99*+ 1920x1200 59.88 which in theory if summed together would be one whole screen. But attempting to configure the output results in an error: xrandr --output DP-1 --auto --left-of eDP-1 --output DP-3-9 --auto --right-of DP-3-8 --output DP-3-8 --auto --right-of eDP-1 xrandr: cannot find crtc for output DP-3-8 I'm not sure if this is an intrinsic limitation of the USB-C->DP dongle, or whether there is something that can be done in the software to deal with this 10 year old hardware hack I have sitting on my desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 8 11:20:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Plus Graphics G7 [1028:096d] InstallationDate: Installed on 2020-07-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1886729 Title: Dell displayport YJ3Y6 adapter doesn't drive 4K screen properly Status in xorg package in Ubuntu: New Bug description: I have some early dell 4k 60hz screens - the ones which report 2 panels internally for DP 60Hz - horrid hack I know; I recently got a new XPS laptop and put Ubuntu on it. That XPS laptop has two USB-C/thunderbolt ports, so to drive the screens I bought two slightly different DP adapters - one with power passthrough, and a cheaper one that only does DP. The more expensive one 'USB-C to HDMI/DP' drives the monitor happily over DP, though sadly only at 30Hz - can't have everything :/. It reports one monitor as one output: DP-1 in the attached information: DP-1 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 527mm x 296mm 3840x2160 29.98*+ 30.0029.97 1920x1200 59.88 ... The cheaper one reports the single monitor as two distinct outputs, at 60hz interestingly - DP-3-8 connected (normal left inverted right x axis y axis) 1920x2160 59.99 + DP-3-9
[Touch-packages] [Bug 1885914] Re: Drop obsolete Unicode patch
Hello Gunnar, or anyone else affected, Accepted ibus into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ibus/1.5.22-2ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1885914 Title: Drop obsolete Unicode patch Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Focal: Fix Committed Bug description: [Impact] The Ubuntu 20.04 IBus version includes a patch, which was necessary in 18.04 to make the Ctrl+Shift+u shortcut work, but which has become obsolete later. Currently it prevents users from replacing Ctrl+Shift+u with some other shortcut to avoid conflicts with other applications. See also: * Bug #1885749 * https://github.com/ibus/ibus/issues/2163 In the proposed upload that patch has been dropped. [Test Case] 1. Launch ibus-setup and navigate to the Emoji tab. 2. Change the Unicode code point shortcut to something else. 3. Find that the original shortcut is still effective. 4. Install the ibus packages from focal-proposed. 5. Repeat 1. and 2. 6. Find that the new shortcut works while the original shortcut no longer works. [Regression Potential] Important to confirm that the default Ctrl+Shift+u shortcut works as intended without the patch. Otherwise the regression risk should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1885914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557157] Please test proposed package
Hello Mattias, or anyone else affected,
Accepted openldap into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/openldap/2.4.42
+dfsg-2ubuntu3.9 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557157
Title:
apparmor profile denied for saslauthd: /run/saslauthd/mux
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Trusty:
Won't Fix
Status in openldap source package in Xenial:
Fix Committed
Status in openldap source package in Bionic:
Fix Committed
Status in openldap source package in Eoan:
Fix Committed
Status in openldap source package in Focal:
Fix Committed
Status in openldap source package in Groovy:
Fix Released
Bug description:
[Impact]
When using openldap with sasl authentication, the slapd process will
communicate with the saslauthd daemon via a socket in
{,/var}/run/saslauthd/mux. Unfortunately, this will fail in every
Ubuntu release from trusty onwards, because slapd's apparmor profile
doesn't contain the necessary directive to allow it to read/write
from/to the socket specified above.
The fix is simple: just add the necessary directive to allow slapd to
read/write from/to the saslauthd socket.
[Test Case]
One can reproduce the problem by doing:
$ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy
$ lxc shell openldap-bugbug1557157-groovy
# apt install slapd sasl2-bin ldap-utils apparmor-utils
(As the domain name, use "example.com").
# sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd
# cat > /etc/ldap/sasl2/slapd.conf << __EOF__
mech_list: PLAIN
pwcheck_method: saslauthd
__EOF__
# adduser openldap sasl
# aa-enforce /etc/apparmor.d/usr.sbin.slapd
# systemctl restart slapd.service
# systemctl restart saslauthd.service
# passwd root
(You can choose any password here. You will need to type it when
running the next command.)
# ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root
-Y PLAIN
The command will fail with something like:
ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80)
additional info: SASL(-1): generic failure: Password verification
failed
[Regression Potential]
This is an extremely simple and well contained fix, so I don't
envision any possible regressions after applying it. It is important
noticing that, since the problem affects older Ubuntu releases, the
openldap package will have to be rebuilt against possible newer
versions of libraries and other depencencies, which, albeit unlikely,
may cause issues.
[Original Description]
When using slapd with saslauthd the processes communicate via the
{,/var}/run/saslauthd/mux socket (this is the default location for the
saslauthd server from the sasl2-bin package in the
/etc/default/saslauthd config), but the apparmor profile for
usr.sbin.slapd does not allow access to this socket/file.
Syslog message:
apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd"
name="/run/saslauthd/mux" pid=1880
4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0
Please add the following line to /etc/apparmor.d/usr.sbin.slapd:
/{,var/}run/saslauthd/mux rw,
Ubuntu version: Ubuntu 14.04.4 LTS
slapd version: 2.4.31-1+nmu2ubu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557157] Please test proposed package
Hello Mattias, or anyone else affected,
Accepted openldap into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/openldap/2.4.45
+dfsg-1ubuntu1.6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: openldap (Ubuntu Xenial)
Status: Confirmed => Fix Committed
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557157
Title:
apparmor profile denied for saslauthd: /run/saslauthd/mux
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Trusty:
Won't Fix
Status in openldap source package in Xenial:
Fix Committed
Status in openldap source package in Bionic:
Fix Committed
Status in openldap source package in Eoan:
Fix Committed
Status in openldap source package in Focal:
Fix Committed
Status in openldap source package in Groovy:
Fix Released
Bug description:
[Impact]
When using openldap with sasl authentication, the slapd process will
communicate with the saslauthd daemon via a socket in
{,/var}/run/saslauthd/mux. Unfortunately, this will fail in every
Ubuntu release from trusty onwards, because slapd's apparmor profile
doesn't contain the necessary directive to allow it to read/write
from/to the socket specified above.
The fix is simple: just add the necessary directive to allow slapd to
read/write from/to the saslauthd socket.
[Test Case]
One can reproduce the problem by doing:
$ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy
$ lxc shell openldap-bugbug1557157-groovy
# apt install slapd sasl2-bin ldap-utils apparmor-utils
(As the domain name, use "example.com").
# sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd
# cat > /etc/ldap/sasl2/slapd.conf << __EOF__
mech_list: PLAIN
pwcheck_method: saslauthd
__EOF__
# adduser openldap sasl
# aa-enforce /etc/apparmor.d/usr.sbin.slapd
# systemctl restart slapd.service
# systemctl restart saslauthd.service
# passwd root
(You can choose any password here. You will need to type it when
running the next command.)
# ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root
-Y PLAIN
The command will fail with something like:
ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80)
additional info: SASL(-1): generic failure: Password verification
failed
[Regression Potential]
This is an extremely simple and well contained fix, so I don't
envision any possible regressions after applying it. It is important
noticing that, since the problem affects older Ubuntu releases, the
openldap package will have to be rebuilt against possible newer
versions of libraries and other depencencies, which, albeit unlikely,
may cause issues.
[Original Description]
When using slapd with saslauthd the processes communicate via the
{,/var}/run/saslauthd/mux socket (this is the default location for the
saslauthd server from the sasl2-bin package in the
/etc/default/saslauthd config), but the apparmor profile for
usr.sbin.slapd does not allow access to this socket/file.
Syslog message:
apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd"
name="/run/saslauthd/mux" pid=1880
4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0
Please add the following line to /etc/apparmor.d/usr.sbin.slapd:
/{,var/}run/saslauthd/mux rw,
Ubuntu version: Ubuntu 14.04.4 LTS
slapd version: 2.4.31-1+nmu2ubu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help :
[Touch-packages] [Bug 1557157] Please test proposed package
Hello Mattias, or anyone else affected,
Accepted openldap into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/openldap/2.4.48+dfsg-
1ubuntu1.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
eoan to verification-done-eoan. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-eoan. In either case, without details of your testing we will not
be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: openldap (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557157
Title:
apparmor profile denied for saslauthd: /run/saslauthd/mux
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Trusty:
Won't Fix
Status in openldap source package in Xenial:
Fix Committed
Status in openldap source package in Bionic:
Fix Committed
Status in openldap source package in Eoan:
Fix Committed
Status in openldap source package in Focal:
Fix Committed
Status in openldap source package in Groovy:
Fix Released
Bug description:
[Impact]
When using openldap with sasl authentication, the slapd process will
communicate with the saslauthd daemon via a socket in
{,/var}/run/saslauthd/mux. Unfortunately, this will fail in every
Ubuntu release from trusty onwards, because slapd's apparmor profile
doesn't contain the necessary directive to allow it to read/write
from/to the socket specified above.
The fix is simple: just add the necessary directive to allow slapd to
read/write from/to the saslauthd socket.
[Test Case]
One can reproduce the problem by doing:
$ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy
$ lxc shell openldap-bugbug1557157-groovy
# apt install slapd sasl2-bin ldap-utils apparmor-utils
(As the domain name, use "example.com").
# sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd
# cat > /etc/ldap/sasl2/slapd.conf << __EOF__
mech_list: PLAIN
pwcheck_method: saslauthd
__EOF__
# adduser openldap sasl
# aa-enforce /etc/apparmor.d/usr.sbin.slapd
# systemctl restart slapd.service
# systemctl restart saslauthd.service
# passwd root
(You can choose any password here. You will need to type it when
running the next command.)
# ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root
-Y PLAIN
The command will fail with something like:
ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80)
additional info: SASL(-1): generic failure: Password verification
failed
[Regression Potential]
This is an extremely simple and well contained fix, so I don't
envision any possible regressions after applying it. It is important
noticing that, since the problem affects older Ubuntu releases, the
openldap package will have to be rebuilt against possible newer
versions of libraries and other depencencies, which, albeit unlikely,
may cause issues.
[Original Description]
When using slapd with saslauthd the processes communicate via the
{,/var}/run/saslauthd/mux socket (this is the default location for the
saslauthd server from the sasl2-bin package in the
/etc/default/saslauthd config), but the apparmor profile for
usr.sbin.slapd does not allow access to this socket/file.
Syslog message:
apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd"
name="/run/saslauthd/mux" pid=1880
4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0
Please add the following line to /etc/apparmor.d/usr.sbin.slapd:
/{,var/}run/saslauthd/mux rw,
Ubuntu version: Ubuntu 14.04.4 LTS
slapd version: 2.4.31-1+nmu2ubu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux
Hello Mattias, or anyone else affected,
Accepted openldap into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/openldap/2.4.49+dfsg-
2ubuntu1.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: openldap (Ubuntu Focal)
Status: Confirmed => Fix Committed
** Tags added: verification-needed verification-needed-focal
** Changed in: openldap (Ubuntu Eoan)
Status: Confirmed => Fix Committed
** Tags added: verification-needed-eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557157
Title:
apparmor profile denied for saslauthd: /run/saslauthd/mux
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Trusty:
Won't Fix
Status in openldap source package in Xenial:
Fix Committed
Status in openldap source package in Bionic:
Fix Committed
Status in openldap source package in Eoan:
Fix Committed
Status in openldap source package in Focal:
Fix Committed
Status in openldap source package in Groovy:
Fix Released
Bug description:
[Impact]
When using openldap with sasl authentication, the slapd process will
communicate with the saslauthd daemon via a socket in
{,/var}/run/saslauthd/mux. Unfortunately, this will fail in every
Ubuntu release from trusty onwards, because slapd's apparmor profile
doesn't contain the necessary directive to allow it to read/write
from/to the socket specified above.
The fix is simple: just add the necessary directive to allow slapd to
read/write from/to the saslauthd socket.
[Test Case]
One can reproduce the problem by doing:
$ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy
$ lxc shell openldap-bugbug1557157-groovy
# apt install slapd sasl2-bin ldap-utils apparmor-utils
(As the domain name, use "example.com").
# sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd
# cat > /etc/ldap/sasl2/slapd.conf << __EOF__
mech_list: PLAIN
pwcheck_method: saslauthd
__EOF__
# adduser openldap sasl
# aa-enforce /etc/apparmor.d/usr.sbin.slapd
# systemctl restart slapd.service
# systemctl restart saslauthd.service
# passwd root
(You can choose any password here. You will need to type it when
running the next command.)
# ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root
-Y PLAIN
The command will fail with something like:
ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80)
additional info: SASL(-1): generic failure: Password verification
failed
[Regression Potential]
This is an extremely simple and well contained fix, so I don't
envision any possible regressions after applying it. It is important
noticing that, since the problem affects older Ubuntu releases, the
openldap package will have to be rebuilt against possible newer
versions of libraries and other depencencies, which, albeit unlikely,
may cause issues.
[Original Description]
When using slapd with saslauthd the processes communicate via the
{,/var}/run/saslauthd/mux socket (this is the default location for the
saslauthd server from the sasl2-bin package in the
/etc/default/saslauthd config), but the apparmor profile for
usr.sbin.slapd does not allow access to this socket/file.
Syslog message:
apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd"
name="/run/saslauthd/mux" pid=1880
4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0
Please add the following line to /etc/apparmor.d/usr.sbin.slapd:
/{,var/}run/saslauthd/mux rw,
Ubuntu version: Ubuntu 14.04.4 LTS
slapd version: 2.4.31-1+nmu2ubu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to
[Touch-packages] [Bug 1866303] Please test proposed package
Hello Ryan, or anyone else affected,
Accepted openldap into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/openldap/2.4.42
+dfsg-2ubuntu3.9 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1866303
Title:
slapd crash with pwdAccountLockedTime and stacked overlays
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Xenial:
Fix Committed
Status in openldap source package in Bionic:
Fix Committed
Status in openldap source package in Disco:
Won't Fix
Status in openldap source package in Eoan:
Fix Committed
Status in openldap package in Debian:
Fix Released
Bug description:
[Impact]
In the configuration and conditions described below, slapd can crash:
1. ppolicy overlay configured with pwdLockout: TRUE
2. smbk5pwd overlay stacked after ppolicy
3. an account locked out via pwdAccountLockedTime
4. a client binding to the locked-out account and also requesting the ppolicy
control
[Test Case]
* get the files from the bug:
mkdir slapd-test-case; cd slapd-test-case
wget -ct0
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334194/+files/slapd.conf
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334195/+files/data.ldif
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334196/+files/samba.schema
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334197/+files/script
* run the script:
sudo apt update && sudo sh ./script
* With the bug, the result is:
ldap_bind: Invalid credentials (49)
slapd dead
* If when confirming the bug you don't see "slapd dead" like above,
check manually, as slapd might have been in the process of shutting
down when the script checked its status: "sudo systemctl status slapd"
* With the fixed packages, you get a living slapd at the end (you can
run the script again on the same system after updating the packages):
sudo sh ./script
...
slapd running
ldap_bind: Invalid credentials (49)
slapd running
[Regression Potential]
The fix is in the password policy overlay (not enabled by default), so any
regressions would be around that area and could potentially impact
authentication ("binding") to openldap.
[Other Info]
This was fixed in focal and "cooked" there for a long while, as suggested by
the Debian maintainer. We haven't received further bug reports about this in
focal+.
[Original Description]
Hello,
Please merge openldap 2.4.49+dfsg-2 from Debian unstable to fix an
issue in the ppolicy overlay that can crash slapd. Please also
consider SRUing the patch after it has had some testing time.
Upstream: https://openldap.org/its/?findid=9171
Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953150
The ingredients for the crash are:
1: ppolicy overlay configured with pwdLockout: TRUE
2. smbk5pwd overlay stacked after ppolicy
3. an account locked out via pwdAccountLockedTime
4. a client binding to the locked-out account and also requesting the ppolicy
control
The buggy code is not as specific as the above steps, so I suspect
there are probably other configurations or steps that can trigger the
same crash.
I will attach my test script and data for reproducing the crash.
Expected output (last lines):
[ ok ] Starting OpenLDAP: slapd.
slapd running
ldap_bind: Invalid credentials (49)
slapd running
Actual output (last lines):
[ ok ] Starting OpenLDAP: slapd.
slapd running
ldap_bind: Invalid credentials (49)
slapd dead
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+subscriptions
--
Mailing list:
[Touch-packages] [Bug 1866303] Re: slapd crash with pwdAccountLockedTime and stacked overlays
Hello Ryan, or anyone else affected,
Accepted openldap into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/openldap/2.4.48+dfsg-
1ubuntu1.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
eoan to verification-done-eoan. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-eoan. In either case, without details of your testing we will not
be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: openldap (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-eoan
** Changed in: openldap (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1866303
Title:
slapd crash with pwdAccountLockedTime and stacked overlays
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Xenial:
Fix Committed
Status in openldap source package in Bionic:
Fix Committed
Status in openldap source package in Disco:
Won't Fix
Status in openldap source package in Eoan:
Fix Committed
Status in openldap package in Debian:
Fix Released
Bug description:
[Impact]
In the configuration and conditions described below, slapd can crash:
1. ppolicy overlay configured with pwdLockout: TRUE
2. smbk5pwd overlay stacked after ppolicy
3. an account locked out via pwdAccountLockedTime
4. a client binding to the locked-out account and also requesting the ppolicy
control
[Test Case]
* get the files from the bug:
mkdir slapd-test-case; cd slapd-test-case
wget -ct0
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334194/+files/slapd.conf
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334195/+files/data.ldif
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334196/+files/samba.schema
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334197/+files/script
* run the script:
sudo apt update && sudo sh ./script
* With the bug, the result is:
ldap_bind: Invalid credentials (49)
slapd dead
* If when confirming the bug you don't see "slapd dead" like above,
check manually, as slapd might have been in the process of shutting
down when the script checked its status: "sudo systemctl status slapd"
* With the fixed packages, you get a living slapd at the end (you can
run the script again on the same system after updating the packages):
sudo sh ./script
...
slapd running
ldap_bind: Invalid credentials (49)
slapd running
[Regression Potential]
The fix is in the password policy overlay (not enabled by default), so any
regressions would be around that area and could potentially impact
authentication ("binding") to openldap.
[Other Info]
This was fixed in focal and "cooked" there for a long while, as suggested by
the Debian maintainer. We haven't received further bug reports about this in
focal+.
[Original Description]
Hello,
Please merge openldap 2.4.49+dfsg-2 from Debian unstable to fix an
issue in the ppolicy overlay that can crash slapd. Please also
consider SRUing the patch after it has had some testing time.
Upstream: https://openldap.org/its/?findid=9171
Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953150
The ingredients for the crash are:
1: ppolicy overlay configured with pwdLockout: TRUE
2. smbk5pwd overlay stacked after ppolicy
3. an account locked out via pwdAccountLockedTime
4. a client binding to the locked-out account and also requesting the ppolicy
control
The buggy code is not as specific as the above steps, so I suspect
there are probably other configurations or steps that can trigger the
same crash.
I will attach my test script and data for reproducing the crash.
Expected output (last lines):
[ ok ] Starting OpenLDAP: slapd.
slapd running
ldap_bind: Invalid credentials (49)
slapd running
Actual output (last
[Touch-packages] [Bug 1866303] Please test proposed package
Hello Ryan, or anyone else affected,
Accepted openldap into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/openldap/2.4.45
+dfsg-1ubuntu1.6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: openldap (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1866303
Title:
slapd crash with pwdAccountLockedTime and stacked overlays
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Xenial:
Fix Committed
Status in openldap source package in Bionic:
Fix Committed
Status in openldap source package in Disco:
Won't Fix
Status in openldap source package in Eoan:
Fix Committed
Status in openldap package in Debian:
Fix Released
Bug description:
[Impact]
In the configuration and conditions described below, slapd can crash:
1. ppolicy overlay configured with pwdLockout: TRUE
2. smbk5pwd overlay stacked after ppolicy
3. an account locked out via pwdAccountLockedTime
4. a client binding to the locked-out account and also requesting the ppolicy
control
[Test Case]
* get the files from the bug:
mkdir slapd-test-case; cd slapd-test-case
wget -ct0
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334194/+files/slapd.conf
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334195/+files/data.ldif
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334196/+files/samba.schema
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+attachment/5334197/+files/script
* run the script:
sudo apt update && sudo sh ./script
* With the bug, the result is:
ldap_bind: Invalid credentials (49)
slapd dead
* If when confirming the bug you don't see "slapd dead" like above,
check manually, as slapd might have been in the process of shutting
down when the script checked its status: "sudo systemctl status slapd"
* With the fixed packages, you get a living slapd at the end (you can
run the script again on the same system after updating the packages):
sudo sh ./script
...
slapd running
ldap_bind: Invalid credentials (49)
slapd running
[Regression Potential]
The fix is in the password policy overlay (not enabled by default), so any
regressions would be around that area and could potentially impact
authentication ("binding") to openldap.
[Other Info]
This was fixed in focal and "cooked" there for a long while, as suggested by
the Debian maintainer. We haven't received further bug reports about this in
focal+.
[Original Description]
Hello,
Please merge openldap 2.4.49+dfsg-2 from Debian unstable to fix an
issue in the ppolicy overlay that can crash slapd. Please also
consider SRUing the patch after it has had some testing time.
Upstream: https://openldap.org/its/?findid=9171
Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953150
The ingredients for the crash are:
1: ppolicy overlay configured with pwdLockout: TRUE
2. smbk5pwd overlay stacked after ppolicy
3. an account locked out via pwdAccountLockedTime
4. a client binding to the locked-out account and also requesting the ppolicy
control
The buggy code is not as specific as the above steps, so I suspect
there are probably other configurations or steps that can trigger the
same crash.
I will attach my test script and data for reproducing the crash.
Expected output (last lines):
[ ok ] Starting OpenLDAP: slapd.
slapd running
ldap_bind: Invalid credentials (49)
slapd running
Actual output (last lines):
[ ok ] Starting OpenLDAP: slapd.
slapd running
ldap_bind: Invalid credentials (49)
slapd dead
To manage notifications
[Touch-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
** Description changed: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running - Ubuntu 19.10 and Gnome 3.34.2. + Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also + persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 - john@hydra:~$ dmesg | fgrep 'sound' [7.920552] input: HDA ATI SB Rear Mic as /devices/pci:00/:00:14.2/sound/card0/input27 [7.920612] input: HDA ATI SB Front Mic as /devices/pci:00/:00:14.2/sound/card0/input28 [7.920657] input: HDA ATI SB Line as /devices/pci:00/:00:14.2/sound/card0/input29 [7.920704] input: HDA ATI SB Line Out Front as
[Touch-packages] [Bug 1882583] Update Released
The verification of the Stable Release Update for software-properties 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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1882583 Title: [SRU] Enable support for Victoria Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Groovy: Fix Released Bug description: Please add support for: cloud-archive:victoria cloud-archive:victoria-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the victoria cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:victoria sudo add-apt-repository cloud-archive:victoria-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1882583/+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 1882583] Re: [SRU] Enable support for Victoria Cloud Archive
This bug was fixed in the package software-properties - 0.98.9.1 --- software-properties (0.98.9.1) focal; urgency=medium * cloudarchive: Enable support for the Victoria Ubuntu Cloud Archive on 20.04 (LP: #1882583). -- Corey Bryant Mon, 08 Jun 2020 16:46:09 -0400 ** Changed in: software-properties (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1882583 Title: [SRU] Enable support for Victoria Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Groovy: Fix Released Bug description: Please add support for: cloud-archive:victoria cloud-archive:victoria-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the victoria cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:victoria sudo add-apt-repository cloud-archive:victoria-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1882583/+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
> I wonder if you see anything related to systemd-resolved with 'journalctl | > grep audit | grep systemd' No, not since March 30th. > at the time of the boot failure. No log files were written at that time (no log entries made it to disk before the segfault). -- 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: In Progress 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: Mac-8ED6AF5B48C039E1 dmi.modalias:
[Touch-packages] [Bug 1219529] Re: df -x tmpfs fails to exclude udev (/dev)
** Changed in: coreutils (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1219529 Title: df -x tmpfs fails to exclude udev (/dev) Status in coreutils: New Status in coreutils package in Ubuntu: Fix Committed Bug description: The command: $ /bin/df -x tmpfs should exclude all filesystems of type tmpfs. The udev filesystem mounted at /dev is of this type: $ stat -f /dev File: "/dev" ID: 0Namelen: 255 Type: tmpfs Block size: 4096 Fundamental block size: 4096 Blocks: Total: 4109101Free: 4109098Available: 4109098 Inodes: Total: 4109101Free: 4108501 However, df still displays this filesystem: $ df -l -x tmpfs Filesystem 1K-blocks Used Available Use% Mounted on ... udev 1643640412 16436392 1% /dev ... ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: coreutils 8.20-3ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 1 15:05:40 2013 InstallationDate: Installed on 2013-08-31 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/coreutils/+bug/1219529/+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 1756595] Re: disk space info inadvertently provides all installed snaps
** Changed in: coreutils (Ubuntu) Status: New => Fix Committed -- 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/1756595 Title: disk space info inadvertently provides all installed snaps Status in apt package in Ubuntu: Fix Released Status in coreutils package in Ubuntu: Fix Committed Status in apt source package in Bionic: Fix Released Status in apt source package in Disco: Fix Released Status in apt source package in Eoan: Fix Released Bug description: [Impact] When apport is reporting a crash, it includes the output of the "df" utility, to list the free disk space information per mount point. That output nowadays will inadvertently include all snaps that the user may have installed, including their revision numbers. Here is a simple df output: andreas@nsn7:~$ df Filesystem 1K-blocksUsed Available Use% Mounted on udev 8119680 0 8119680 0% /dev tmpfs 16301561828 1628328 1% /run nsn7/ROOT/ubuntu433084288 2500608 430583680 1% / tmpfs 8150776 1 8131888 1% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs 8150776 0 8150776 0% /sys/fs/cgroup nsn7/var/log430763136 179456 430583680 1% /var/log nsn7/var/tmp430583808 128 430583680 1% /var/tmp /dev/sda2 1032088 160336871752 16% /boot /dev/sda1 5232482720520528 1% /boot/efi nsn7/home 430651264 67584 430583680 1% /home nsn7/var/cache 430653312 69632 430583680 1% /var/cache nsn7/var/mail 430583808 128 430583680 1% /var/mail nsn7/var/spool 430583808 128 430583680 1% /var/spool tmpfs 1630152 16 1630136 1% /run/user/120 tmpfs 100 0 100 0% /var/lib/lxd/shmounts tmpfs 100 0 100 0% /var/lib/lxd/devlxd tmpfs 1630152 36 1630116 1% /run/user/1000 nsn7/lxd/containers/squid-ds216 431444096 860416 430583680 1% /var/lib/lxd/storage-pools/default/containers/squid-ds216 /dev/loop0 83712 83712 0 100% /snap/core/4206 /dev/loop1 102144 102144 0 100% /snap/git-ubuntu/402 You can see I have the core snap at revision 4206, and git-ubuntu at revision 402. There are already many bug reports in launchpad where one can see this information. Granted, the user can review it, refuse to send this data, etc. This bug is about the unexpectedness of having that information in the disk space data. If the user sees a prompt like "Would you like to include disk free space information in your report?", or "Would you like to include the output of the df(1) command in your report?", that doesn't immediately translate to "Would you like to include disk free space information and a list of all installed snaps and their revision numbers in your report?". [Test case] Do something that triggers the apport hook and make sure you don't see snaps in there. For example, install xterm, then add exit 1 to the start of the prerm, then run apt remove xterm, and investigate /var/crash/xterm.0.crash after that (delete before running apt). [Regression potential] Fix consists of adding -x squashfs to df output, so might hide other non-snap squashfs images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1756595/+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 1827159] Re: check_all_disks includes squashfs /snap/* which are 100%
** Changed in: coreutils (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1827159 Title: check_all_disks includes squashfs /snap/* which are 100% Status in Nagios Charm: Fix Released Status in coreutils package in Ubuntu: Fix Committed Status in monitoring-plugins package in Ubuntu: Fix Released Bug description: [Impact] False positive reports are generated in monitoring tools when artificial filesystems are mounted, since they show 100% disk utilization, and thus add unnecessary (but dire sounding) "DISK CRITICAL" noise. [Test Case] $ lxc create ubuntu-daily:19.10/amd64 lp1827159 $ lxc exec lp1827159 bash # apt-get -y update # apt-get install monitoring-plugins # snap install gnome-calculator [...] # /usr/lib/nagios/plugins/check_disk -w 10 -c 10 DISK CRITICAL - free space: / 1903 MB (1% inode=78%); /dev 0 MB (100% inode=99%); /dev/full 16018 MB (100% inode=99%); /dev/null 16018 MB (100% inode=99%); /dev/random 16018 MB (100% inode=99%); /dev/tty 16018 MB (100% inode=99%); /dev/urandom 16018 MB (100% inode=99%); /dev/zero 16018 MB (100% inode=99%); /dev/fuse 16018 MB (100% inode=99%); /dev/net/tun 16018 MB (100% inode=99%); /dev/lxd 0 MB (100% inode=99%); /dev/.lxd-mounts 0 MB (100% inode=99%); /dev/shm 16041 MB (100% inode=99%); /run 3208 MB (99% inode=99%); /run/lock 5 MB (100% inode=99%); /sys/fs/cgroup 16041 MB (100% inode=99%); /snap 1903 MB (1% inode=78%); /run/snapd/ns 3208 MB (99% inode=99%);| /=71MB;119160;119160;0;119170 /dev=0MB;-10;-10;0;0 /dev/full=0MB;16008;16008;0;16018 /dev/null=0MB;16008;16008;0;16018 /dev/random=0MB;16008;16008;0;16018 /dev/tty=0MB;16008;16008;0;16018 /dev/urandom=0MB;16008;16008;0;16018 /dev/zero=0MB;16008;16008;0;16018 /dev/fuse=0MB;16008;16008;0;16018 /dev/net/tun=0MB;16008;16008;0;16018 /dev/lxd=0MB;-10;-10;0;0 /dev/.lxd-mounts=0MB;-10;-10;0;0 /dev/shm=0MB;16031;16031;0;16041 /run=0MB;3198;3198;0;3208 /run/lock=0MB;-5;-5;0;5 /sys/fs/cgroup=0MB;16031;16031;0;16041 /snap=71MB;119160;119160;0;119170 /run/snapd/ns=0MB;3198;3198;0;3208 # /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -e -X squashfs DISK CRITICAL - free space: /dev 0 MB (100% inode=99%); /dev/lxd 0 MB (100% inode=99%); /dev/.lxd-mounts 0 MB (100% inode=99%); /run/lock 5 MB (100% inode=99%);| /=111392MB;119160;119160;0;119170 /dev=0MB;-10;-10;0;0 /dev/full=0MB;16008;16008;0;16018 /dev/null=0MB;16008;16008;0;16018 /dev/random=0MB;16008;16008;0;16018 /dev/tty=0MB;16008;16008;0;16018 /dev/urandom=0MB;16008;16008;0;16018 /dev/zero=0MB;16008;16008;0;16018 /dev/fuse=0MB;16008;16008;0;16018 /dev/net/tun=0MB;16008;16008;0;16018 /dev/lxd=0MB;-10;-10;0;0 /dev/.lxd-mounts=0MB;-10;-10;0;0 /dev/shm=0MB;16031;16031;0;16041 /run=0MB;3198;3198;0;3208 /run/lock=0MB;-5;-5;0;5 /sys/fs/cgroup=0MB;16031;16031;0;16041 /snap=111392MB;119160;119160;0;119170 /run/snapd/ns=0MB;3198;3198;0;3208 # /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -e -X tmpfs DISK OK| /=71MB;119160;119160;0;119170 /dev/full=0MB;16008;16008;0;16018 /dev/null=0MB;16008;16008;0;16018 /dev/random=0MB;16008;16008;0;16018 /dev/tty=0MB;16008;16008;0;16018 /dev/urandom=0MB;16008;16008;0;16018 /dev/zero=0MB;16008;16008;0;16018 /dev/fuse=0MB;16008;16008;0;16018 /dev/net/tun=0MB;16008;16008;0;16018 /snap=71MB;119160;119160;0;119170 [Regression Potential] As this alters the logic of how out-of-space checks are handled, relevant issues to keep an eye out for would relate to filesystem checks reporting improperly. These tools underlay a few different front-ends, so regression bugs may get filed in a few different places, however they will tend to display error messages involving check_disk, nagios, and either tmpfs or tracefs. Note that there are likely other synthetic filesystems beyond tmpfs and tracefs (e.g. udev, usbfs, devtmpfs, fuse.*, ...) which might also cause similar false positives; these should be handled as separate bugs, although they can likely be fixed the same way. [Fix] monitoring-plugins is modified to exclude the unwanted filesystems by default, in check_disk.c (see patch). [Discussion] There have been several bug reports filed about false positives with different synthetic file systems (see Dupes), including tracefs, squashfs, and tmpfs. The commonly discussed workaround is to exclude these when running the tools (e.g. using the '-X ' parameter for check_all_disks). Since wrappers are typically used for running the underlying tools, it is possible to add a string of -X... parameters. However, a cleaner solution is possible. monitoring-plugins' check_disk.c maintains an internal exclusion list, fs_exclude_list, which already excludes iso9660, and can be modified to add other filesystems to exclude by default. In other words, check_disk.c is
[Touch-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
After the crash (hid hangs, could be a side effect) this is the dmesg.0 file still existing john@hydra:~$ tail -100 /var/log/dmesg.0 [7.277226] kernel: nvidia-uvm: Loaded the UVM driver, major device number 237. [7.498321] kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database [7.521638] kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [7.785905] kernel: snd_hda_intel :00:14.2: position_fix set to 1 for device 1458:a022 [7.820545] kernel: MCE: In-kernel MCE decoding enabled. [7.825161] kernel: EDAC amd64: Node 0: DRAM ECC disabled. [7.825163] kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Either enable ECC checking or force module loading by setting 'ecc_enable_override'. (Note that use of the override may cause unknown side effects.) [7.873127] kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC889A: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line [7.873143] kernel: snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [7.873144] kernel: snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [7.873145] kernel: snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [7.873146] kernel: snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [7.873147] kernel: snd_hda_codec_realtek hdaudioC0D0:inputs: [7.873149] kernel: snd_hda_codec_realtek hdaudioC0D0: Rear Mic=0x18 [7.873150] kernel: snd_hda_codec_realtek hdaudioC0D0: Front Mic=0x19 [7.873152] kernel: snd_hda_codec_realtek hdaudioC0D0: Line=0x1a [7.873153] kernel: snd_hda_codec_realtek hdaudioC0D0: CD=0x1c [7.873154] kernel: snd_hda_codec_realtek hdaudioC0D0:dig-in=0x1f [7.877268] kernel: EDAC amd64: Node 0: DRAM ECC disabled. [7.877271] kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. Either enable ECC checking or force module loading by setting 'ecc_enable_override'. (Note that use of the override may cause unknown side effects.) [7.885647] kernel: wlan0: Broadcom BCM43b1 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) [7.885648] kernel: [7.885816] kernel: snd_hda_intel :01:00.1: Disabling MSI [7.885827] kernel: snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [7.920552] kernel: input: HDA ATI SB Rear Mic as /devices/pci:00/:00:14.2/sound/card0/input27 [7.920612] kernel: input: HDA ATI SB Front Mic as /devices/pci:00/:00:14.2/sound/card0/input28 [7.920657] kernel: input: HDA ATI SB Line as /devices/pci:00/:00:14.2/sound/card0/input29 [7.920704] kernel: input: HDA ATI SB Line Out Front as /devices/pci:00/:00:14.2/sound/card0/input30 [7.920749] kernel: input: HDA ATI SB Line Out Surround as /devices/pci:00/:00:14.2/sound/card0/input31 [7.920795] kernel: input: HDA ATI SB Line Out CLFE as /devices/pci:00/:00:14.2/sound/card0/input32 [7.920837] kernel: input: HDA ATI SB Line Out Side as /devices/pci:00/:00:14.2/sound/card0/input33 [8.035861] kernel: mc: Linux media interface: v0.10 [8.243472] kernel: videodev: Linux video capture interface: v2.00 [8.261622] kernel: usbcore: registered new interface driver r8152 [8.349483] kernel: usb 1-2.4: reset high-speed USB device number 7 using ehci-pci [8.413200] kernel: usbcore: registered new interface driver cdc_ether [8.417252] kernel: Bluetooth: Core ver 2.22 [8.417279] kernel: NET: Registered protocol family 31 [8.417280] kernel: Bluetooth: HCI device and connection manager initialized [8.417284] kernel: Bluetooth: HCI socket layer initialized [8.417286] kernel: Bluetooth: L2CAP socket layer initialized [8.417301] kernel: Bluetooth: SCO socket layer initialized [8.506254] kernel: r8152 1-2.4:1.0 eth0: v1.09.11 [8.674264] kernel: usbcore: registered new interface driver btusb [8.686155] kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input34 [8.686215] kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input35 [8.686264] kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input36 [8.686317] kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input37 [8.733961] kernel: usbcore: registered new interface driver snd-usb-audio [8.736521] kernel: uvcvideo: Found UVC 1.00 device Microsoft® LifeCam Studio(TM) (045e:0772) [8.779706] kernel: Bluetooth: hci0: BCM: chip id 63 [8.780703] kernel: Bluetooth: hci0: BCM: features 0x07 [8.796682] kernel: Bluetooth: hci0: hydra [8.800667] kernel: Bluetooth: hci0:
[Touch-packages] [Bug 1883694] Re: [SRU] New upstream release 2.64.3
This bug was fixed in the package glib2.0 - 2.64.3-1~ubuntu20.04.1 --- glib2.0 (2.64.3-1~ubuntu20.04.1) focal; urgency=medium * No-change backport from unstable / groovy to focal (LP: #1883694) * control, gbp.conf: Use the ubuntu/focal branch glib2.0 (2.64.3-1) unstable; urgency=medium * Team upload [ Laurent Bigonville ] * Drop the libgio-fam package, and install the fam GIO plugin in libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915) * Stop building the libgio-fam package on kFreeBSD ports. It is no longer necessary now that gkqueuefilemonitor is available. [ Simon McVittie ] * Clarify changelog entry regarding Hurd and kFreeBSD * New upstream stable release -- Iain Lane Tue, 16 Jun 2020 12:21:35 +0100 ** Changed in: glib2.0 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1883694 Title: [SRU] New upstream release 2.64.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Focal: Fix Released Bug description: [ Description ] Take this new upstrem stable release. +glib2.0 (2.64.3-1~ubuntu20.04.1) UNRELEASED; urgency=medium + + * No-change backport from unstable / groovy to focal. + + -- Iain Lane Tue, 16 Jun 2020 11:53:34 +0100 + +glib2.0 (2.64.3-1) unstable; urgency=medium + + * Team upload + + [ Laurent Bigonville ] + * Drop the libgio-fam package, and install the fam GIO plugin in +libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915) + * Stop building the libgio-fam package on kFreeBSD ports. +It is no longer necessary now that gkqueuefilemonitor is available. + + [ Simon McVittie ] + * Clarify changelog entry regarding Hurd and kFreeBSD + * New upstream stable release + + -- Simon McVittie Fri, 29 May 2020 20:24:33 +0100 The gio-fam related changes do not affect Ubuntu, as they are for hurd/kfreebsd only. Upstream NEWS diff: * Stability improvements for various unit tests * Bugs fixed: - #1954 gdbus-server-auth intermittent failure - #2094 Deprecation warnings when compiling with -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_28 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_28 - !1470 Backport !1440 -Wformat-nonliteral fixes to glib-2-64 - !1471 Backport !1448 memory monitor test dependency fixes to glib-2-64 - !1473 CI: Switch to new Windows runners (2.64) - !1478 Backport !1477 D-Bus keyring handling fixes to glib-2-64 - !1483 Backport !1481 “array: fix corrupt state of GPtrArray after g_ptr_array_extend_and_steal()” to glib-2-64 - !1484 Backport !1480 “CI: Make sure we use meson 0.49.2 in MSYS2” to glib-2-64 - !1486 Backport !1472 “gthread: ignore deprecated declarations in static inline functions” to glib-2-64 - !1495 Backport !1493 “meson: Remove stray ], in O_DIRECTORY check” to glib-2-64 - !1501 Backport !1439 “Fix stpcpy() detection“ to glib-2-64 * Translation updates: - Chinese (Taiwan) - German [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1883694/+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 1883694] Update Released
The verification of the Stable Release Update for glib2.0 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 glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1883694 Title: [SRU] New upstream release 2.64.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Focal: Fix Released Bug description: [ Description ] Take this new upstrem stable release. +glib2.0 (2.64.3-1~ubuntu20.04.1) UNRELEASED; urgency=medium + + * No-change backport from unstable / groovy to focal. + + -- Iain Lane Tue, 16 Jun 2020 11:53:34 +0100 + +glib2.0 (2.64.3-1) unstable; urgency=medium + + * Team upload + + [ Laurent Bigonville ] + * Drop the libgio-fam package, and install the fam GIO plugin in +libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915) + * Stop building the libgio-fam package on kFreeBSD ports. +It is no longer necessary now that gkqueuefilemonitor is available. + + [ Simon McVittie ] + * Clarify changelog entry regarding Hurd and kFreeBSD + * New upstream stable release + + -- Simon McVittie Fri, 29 May 2020 20:24:33 +0100 The gio-fam related changes do not affect Ubuntu, as they are for hurd/kfreebsd only. Upstream NEWS diff: * Stability improvements for various unit tests * Bugs fixed: - #1954 gdbus-server-auth intermittent failure - #2094 Deprecation warnings when compiling with -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_28 -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_28 - !1470 Backport !1440 -Wformat-nonliteral fixes to glib-2-64 - !1471 Backport !1448 memory monitor test dependency fixes to glib-2-64 - !1473 CI: Switch to new Windows runners (2.64) - !1478 Backport !1477 D-Bus keyring handling fixes to glib-2-64 - !1483 Backport !1481 “array: fix corrupt state of GPtrArray after g_ptr_array_extend_and_steal()” to glib-2-64 - !1484 Backport !1480 “CI: Make sure we use meson 0.49.2 in MSYS2” to glib-2-64 - !1486 Backport !1472 “gthread: ignore deprecated declarations in static inline functions” to glib-2-64 - !1495 Backport !1493 “meson: Remove stray ], in O_DIRECTORY check” to glib-2-64 - !1501 Backport !1439 “Fix stpcpy() detection“ to glib-2-64 * Translation updates: - Chinese (Taiwan) - German [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1883694/+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 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
There are several reports on the net talking about random disconnects with Bluetooth dongles reporting as BCM20702A0 and BCM20702A1, that might be important. Win10 experience the same problems, but it seems like they are able to recover. It seems like my HK Onyx Studio 4 has the same problem, but much less frequently. I have not tried to make any statistics though. I had a pair of Philips Bluetooth headphones that also had this problem. In short, I'm pretty sure it is not the devices that are the problem, although they may use the same chipset. I don't experience the same problem when the sound devices are attached to Android devices. So the problem persists over several sound devices, over several Bluetooth dongles, and over several mainboards. That should indicate that the problem somehow emerge from the system, even if Win10 seems to have fixed it to some degree. -- 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/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: New Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703]
[Touch-packages] [Bug 1886128] Re: systemd-resolved does not resolve address due to udp payload size.
> We are reffering to the local stub resolver
yes, i understand that, but i'm asking if you are talking about local
traffic TO the stub resolver, or traffic FROM the stub resolver to your
upstream nameserver.
If you have pcap showing the problem, please attach it.
If you're not sure what I'm talking about, then you should do:
$ sudo systemctl edit systemd-resolved
and in the file editor it opens, add this content:
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
then save the file and reboot.
then try looking up your host again (using the local stub resolver of
course).
Gather the resolved logs and attach or paste them here.
$ journalctl -b -u systemd-resolved --no-pager
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1886128
Title:
systemd-resolved does not resolve address due to udp payload size.
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Description: Ubuntu 18.04.4 LTS
Release: 18.04
systemd-resolve --version
systemd 237
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
-PCRE2 default-hierarchy=hybrid
We met an error: on an attempt to resolve address, the following issue
appears:
; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>>
mharder-formrec.cognitiveservices.azure.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;mharder-formrec.cognitiveservices.azure.com. IN A
;; Query time: 231 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Apr 28 20:47:14 UTC 2020
;; MSG SIZE rcvd: 72
Let me provide you important notes about the issue:
1) It's not reproducing on Ubuntu 16;
2) Bypassing systemd-resolve - everything works fine;
3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE
Successful query:
113516:27:25.964386 10.1.0.4168.63.129.16 DNS 128
Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com
OPT
Domain Name System (query)
Transaction ID: 0xc2d4
Flags: 0x0120 Standard query
0... = Response: Message is a query
.000 0... = Opcode: Standard query (0)
..0. = Truncated: Message is not truncated
...1 = Recursion desired: Do query recursively
.0.. = Z: reserved (0)
..1. = AD bit: Set
...0 = Non-authenticated data: Unacceptable
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 1
Queries
mharder-formrec.cognitiveservices.azure.com: type A, class IN
Additional records
: type OPT
Name:
Type: OPT (41)
UDP payload size: 4096
Higher bits in extended RCODE: 0x00
EDNS0 version: 0
Z: 0x
0... = DO bit: Cannot handle DNSSEC security
RRs
.000 = Reserved: 0x
Data length: 12
Option: COOKIE
Unsuccessful query:
112816:27:25.713886 10.1.0.4168.63.129.16 DNS 116
Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com
OPT
Domain Name System (query)
Transaction ID: 0x198d
Flags: 0x0100 Standard query
0... = Response: Message is a query
.000 0... = Opcode: Standard query (0)
..0. = Truncated: Message is not truncated
...1 = Recursion desired: Do query recursively
.0.. = Z: reserved (0)
...0 = Non-authenticated data: Unacceptable
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 1
Queries
mharder-formrec.cognitiveservices.azure.com: type A, class IN
Additional records
: type OPT
Name:
Type: OPT (41)
UDP payload size: 512
Higher bits in extended RCODE: 0x00
EDNS0 version: 0
Z: 0x
0... = DO bit: Cannot handle DNSSEC security
RRs
.000 = Reserved: 0x
Data length: 0
Notable difference:
Success:
UDP payload size: 4096
Failure:
UDP payload size: 512
And notable differences in the responses:
Success:
Flags: 0x8180 Standard query response, No error
..0. = Truncated: Message is not truncated
Failure:
Flags: 0x8380
[Touch-packages] [Bug 1886714] [NEW] Bluetooth disconnects, and then sound fails on reconnect
Public bug reported: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Bluetooth: RFCOMM ver 1.11 john@hydra:~$ dmesg | fgrep 'sound' [7.920552] input: HDA ATI SB Rear Mic as /devices/pci:00/:00:14.2/sound/card0/input27 [7.920612] input: HDA ATI SB Front Mic as /devices/pci:00/:00:14.2/sound/card0/input28 [7.920657] input: HDA ATI SB Line as /devices/pci:00/:00:14.2/sound/card0/input29 [7.920704] input: HDA ATI SB Line Out Front as /devices/pci:00/:00:14.2/sound/card0/input30 [7.920749] input: HDA ATI SB Line Out Surround as /devices/pci:00/:00:14.2/sound/card0/input31 [7.920795] input: HDA ATI SB Line Out CLFE as /devices/pci:00/:00:14.2/sound/card0/input32 [7.920837] input: HDA ATI SB Line Out Side as
[Touch-packages] [Bug 1886696] Re: [Vostro 5490, Realtek ALC3204, Speaker, Internal] Pulseaudio fails to detect card
** Package changed: ubuntu => pulseaudio (Ubuntu) -- 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/1886696 Title: [Vostro 5490, Realtek ALC3204, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: I have ubuntu Ubuntu 20.04 LTS installed, together with windows (dual boot) on my laptop. There is no sound at all, seems like Pulseaudio / Alsa dont recognize the sound card: $ pacmd list-cards 0 card(s) available. dmesg shows errors of sof-audio-pci: $ dmesg [ 13.313523] sof-audio-pci :00:1f.3: error: hw params ipc failed for stream 2 [ 13.313524] sof-audio-pci :00:1f.3: ASoC: :00:1f.3 hw params failed: -22 [ 13.313525] HDA Analog: ASoC: hw_params FE failed -22 [ 13.313883] sof-audio-pci :00:1f.3: error: ipc error for 0x6001 size 20 [ 13.313884] sof-audio-pci :00:1f.3: error: hw params ipc failed for stream 2 [ 13.313884] sof-audio-pci :00:1f.3: ASoC: :00:1f.3 hw params failed: -22 [ 13.313885] HDA Analog: ASoC: hw_params FE failed -22 [ 13.314249] sof-audio-pci :00:1f.3: error: ipc error for 0x6001 size 20 [ 13.314249] sof-audio-pci :00:1f.3: error: hw params ipc failed for stream 2 [ 13.314250] sof-audio-pci :00:1f.3: ASoC: :00:1f.3 hw params failed: -22 [ 13.314250] HDA Analog: ASoC: hw_params FE failed -22 . [10706.102325] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 pci device: $ lspci -nnk ... 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] Subsystem: Dell Device [1028:0959] Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci ... There was actually already a sound problem when I had ubuntu 18.04 - The sound worked after ubuntu got up, but then at some point the sound just died, with some different messages on dmesg. I upgraded the kernel and ubuntu version in hope it will solve the problem, but seems like it only got worse. Sound works in windows on the same laptop without issues. My attempts so far, which didnt yield anything 1. reinstall and upgrae linux-firmware. currently 'linux-firmware/focal-updates,focal-updates,now 1.187.1 all [installed]' 2. adding those line to /etc/modprobe.d/alsa-base.conf: options snd-hda-intel model=auto options snd-hda-intel dmic_detect=0 also, when I run 'alsa force-reload' the system just totally crashes, forcing me to press the power button to shut it off. Extra info $ inxi -Fxlpoz System:Kernel: 5.4.0-40-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.2 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 5490 v: N/A serial: Mobo: Dell model: 05P6R7 v: A00 serial: UEFI: Dell v: 1.5.1 date: 01/14/2020 Battery: ID-1: BAT0 charge: 40.7 Wh condition: 40.7/42.0 Wh (97%) model: SMP DELL VM73283 status: Full CPU: Topology: Quad Core model: Intel Core i5-10210U bits: 64 type: MT MCP arch: Kaby Lake rev: C L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 33599 Speed: 600 MHz min/max: 400/4200 MHz Core speeds (MHz): 1: 600 2: 600 3: 600 4: 600 5: 600 6: 600 7: 600 8: 600 Graphics: Device-1: Intel UHD Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz, 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.0.4 direct render: Yes Audio: Device-1: Intel vendor: Dell driver: sof-audio-pci bus ID: 00:1f.3 Sound Server: ALSA v: k5.4.0-40-generic Network: Device-1: Intel Wireless-AC 9462 driver: iwlwifi v: kernel port: 4000 bus ID: 00:14.3 IF: wlp0s20f3 state: up mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus ID: 01:00.0 IF: enp1s0 state: down mac: Drives:Local Storage: total: 476.94 GiB used: 173.69 GiB (36.4%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe 512GB size: 476.94 GiB ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p',
[Touch-packages] [Bug 1886696] [NEW] [Vostro 5490, Realtek ALC3204, Speaker, Internal] Pulseaudio fails to detect card
You have been subscribed to a public bug: I have ubuntu Ubuntu 20.04 LTS installed, together with windows (dual boot) on my laptop. There is no sound at all, seems like Pulseaudio / Alsa dont recognize the sound card: $ pacmd list-cards 0 card(s) available. dmesg shows errors of sof-audio-pci: $ dmesg [ 13.313523] sof-audio-pci :00:1f.3: error: hw params ipc failed for stream 2 [ 13.313524] sof-audio-pci :00:1f.3: ASoC: :00:1f.3 hw params failed: -22 [ 13.313525] HDA Analog: ASoC: hw_params FE failed -22 [ 13.313883] sof-audio-pci :00:1f.3: error: ipc error for 0x6001 size 20 [ 13.313884] sof-audio-pci :00:1f.3: error: hw params ipc failed for stream 2 [ 13.313884] sof-audio-pci :00:1f.3: ASoC: :00:1f.3 hw params failed: -22 [ 13.313885] HDA Analog: ASoC: hw_params FE failed -22 [ 13.314249] sof-audio-pci :00:1f.3: error: ipc error for 0x6001 size 20 [ 13.314249] sof-audio-pci :00:1f.3: error: hw params ipc failed for stream 2 [ 13.314250] sof-audio-pci :00:1f.3: ASoC: :00:1f.3 hw params failed: -22 [ 13.314250] HDA Analog: ASoC: hw_params FE failed -22 . [10706.102325] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 pci device: $ lspci -nnk ... 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] Subsystem: Dell Device [1028:0959] Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci ... There was actually already a sound problem when I had ubuntu 18.04 - The sound worked after ubuntu got up, but then at some point the sound just died, with some different messages on dmesg. I upgraded the kernel and ubuntu version in hope it will solve the problem, but seems like it only got worse. Sound works in windows on the same laptop without issues. My attempts so far, which didnt yield anything 1. reinstall and upgrae linux-firmware. currently 'linux-firmware/focal-updates,focal-updates,now 1.187.1 all [installed]' 2. adding those line to /etc/modprobe.d/alsa-base.conf: options snd-hda-intel model=auto options snd-hda-intel dmic_detect=0 also, when I run 'alsa force-reload' the system just totally crashes, forcing me to press the power button to shut it off. Extra info $ inxi -Fxlpoz System:Kernel: 5.4.0-40-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.2 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Vostro 5490 v: N/A serial: Mobo: Dell model: 05P6R7 v: A00 serial: UEFI: Dell v: 1.5.1 date: 01/14/2020 Battery: ID-1: BAT0 charge: 40.7 Wh condition: 40.7/42.0 Wh (97%) model: SMP DELL VM73283 status: Full CPU: Topology: Quad Core model: Intel Core i5-10210U bits: 64 type: MT MCP arch: Kaby Lake rev: C L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 33599 Speed: 600 MHz min/max: 400/4200 MHz Core speeds (MHz): 1: 600 2: 600 3: 600 4: 600 5: 600 6: 600 7: 600 8: 600 Graphics: Device-1: Intel UHD Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz, 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.0.4 direct render: Yes Audio: Device-1: Intel vendor: Dell driver: sof-audio-pci bus ID: 00:1f.3 Sound Server: ALSA v: k5.4.0-40-generic Network: Device-1: Intel Wireless-AC 9462 driver: iwlwifi v: kernel port: 4000 bus ID: 00:14.3 IF: wlp0s20f3 state: up mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus ID: 01:00.0 IF: enp1s0 state: down mac: Drives:Local Storage: total: 476.94 GiB used: 173.69 GiB (36.4%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe 512GB size: 476.94 GiB ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 14:36:30 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
[Touch-packages] [Bug 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)
Hi @gregrwm, Thanks for reporting this bug/regression. Patch just submitted upstream to fix it [1]. Let's see how it goes. cheers, Mauricio [1] https://github.com/karelzak/util-linux/pull/1095 ** Changed in: util-linux (Ubuntu) Status: New => In Progress ** Changed in: util-linux (Ubuntu) Importance: Undecided => Medium ** Changed in: util-linux (Ubuntu) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- 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: In Progress Bug 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 1886128] Re: systemd-resolved does not resolve address due to udp payload size.
Thank you for the answer. We are reffering to the local stub resolver(
127.0.0.53 ). As a workaround we have created symbolic link:
sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
However, with the local stub resolver is still not working.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1886128
Title:
systemd-resolved does not resolve address due to udp payload size.
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Description: Ubuntu 18.04.4 LTS
Release: 18.04
systemd-resolve --version
systemd 237
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
-PCRE2 default-hierarchy=hybrid
We met an error: on an attempt to resolve address, the following issue
appears:
; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>>
mharder-formrec.cognitiveservices.azure.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;mharder-formrec.cognitiveservices.azure.com. IN A
;; Query time: 231 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Apr 28 20:47:14 UTC 2020
;; MSG SIZE rcvd: 72
Let me provide you important notes about the issue:
1) It's not reproducing on Ubuntu 16;
2) Bypassing systemd-resolve - everything works fine;
3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE
Successful query:
113516:27:25.964386 10.1.0.4168.63.129.16 DNS 128
Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com
OPT
Domain Name System (query)
Transaction ID: 0xc2d4
Flags: 0x0120 Standard query
0... = Response: Message is a query
.000 0... = Opcode: Standard query (0)
..0. = Truncated: Message is not truncated
...1 = Recursion desired: Do query recursively
.0.. = Z: reserved (0)
..1. = AD bit: Set
...0 = Non-authenticated data: Unacceptable
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 1
Queries
mharder-formrec.cognitiveservices.azure.com: type A, class IN
Additional records
: type OPT
Name:
Type: OPT (41)
UDP payload size: 4096
Higher bits in extended RCODE: 0x00
EDNS0 version: 0
Z: 0x
0... = DO bit: Cannot handle DNSSEC security
RRs
.000 = Reserved: 0x
Data length: 12
Option: COOKIE
Unsuccessful query:
112816:27:25.713886 10.1.0.4168.63.129.16 DNS 116
Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com
OPT
Domain Name System (query)
Transaction ID: 0x198d
Flags: 0x0100 Standard query
0... = Response: Message is a query
.000 0... = Opcode: Standard query (0)
..0. = Truncated: Message is not truncated
...1 = Recursion desired: Do query recursively
.0.. = Z: reserved (0)
...0 = Non-authenticated data: Unacceptable
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 1
Queries
mharder-formrec.cognitiveservices.azure.com: type A, class IN
Additional records
: type OPT
Name:
Type: OPT (41)
UDP payload size: 512
Higher bits in extended RCODE: 0x00
EDNS0 version: 0
Z: 0x
0... = DO bit: Cannot handle DNSSEC security
RRs
.000 = Reserved: 0x
Data length: 0
Notable difference:
Success:
UDP payload size: 4096
Failure:
UDP payload size: 512
And notable differences in the responses:
Success:
Flags: 0x8180 Standard query response, No error
..0. = Truncated: Message is not truncated
Failure:
Flags: 0x8380 Standard query response, No error
..1. = Truncated: Message is truncated
Interestingly, systemd-resolved is setting the maximum payload size to 512
regardless of whether EDNS0 is configured and regardless of what is sent to it
for the payload size.
I tried to found a way to change UDP_PAYLOAD_SIZE,but it seems it is only
possible to change it only with direct code modifications.
To manage
[Touch-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver on bionic
This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu7.9 --- pulseaudio (1:11.1-1ubuntu7.9) bionic; urgency=medium [Kai-Chuan Hsieh] * alsa-mixer: Correct ucm card name (LP: #1881094) [Hui Wang] * d/p/0901-alsa-solaris-oss-remove-unnecessary-error-handling-w.patch * d/p/0902-alsa-Improve-resume-logic-after-alsa-suspend.patch * (LP: #1882042) -- Kai-Chuan Hsieh Wed, 27 May 2020 16:42:50 +0800 ** Changed in: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: Fix Committed Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: Fix Released Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function 1. enable Pre-released updates in Developer Options Software & Updates > Developer Options > Pre-released updates (bionic-proposed) 2. $ sudo apt update 3. $ sudo apt install linux-generic-hwe-18.04-edge 4. $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1882042] Update Released
The verification of the Stable Release Update for pulseaudio 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882042 Title: [SRU] Linux,Ubuntu,18.4,CI,OLP15,PRTS, Audio/video is out of sync/lag when enter Suspend during playback Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: [Impact] Users reported the audio and video is out of sync when entering suspend during playback on bionic. [Fix] The mainline pulseaudio already has the fix for this issue, and the fix is already in the eoan, focal and groovy, but it is not in the bionic. [Test Case] open a online video on the firefox, while it is playing, suspend the system, wait for 30 seconds, resume the system, the audio and video is still on the sync. [Potential Regression Risk] Low, these 2 patches are already in the mainline pulseaudio, and already in the eoan, focal and groovy. Most of the change is in the suspend/unsuspend on alsa sink/source, the potential regression risk is the playback/recording stops working after machine suspend and resume or playback/recording has an obvious discontinuity before suspend and after resume. I have done the test on a Lenovo and a Dell machine, the playback/recording worked well after resuming. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882042/+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 1881094] Update Released
The verification of the Stable Release Update for pulseaudio 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: Fix Committed Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: Fix Released Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function 1. enable Pre-released updates in Developer Options Software & Updates > Developer Options > Pre-released updates (bionic-proposed) 2. $ sudo apt update 3. $ sudo apt install linux-generic-hwe-18.04-edge 4. $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1882042] Re: [SRU] Linux, Ubuntu, 18.4, CI, OLP15, PRTS, Audio/video is out of sync/lag when enter Suspend during playback
This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu7.9 --- pulseaudio (1:11.1-1ubuntu7.9) bionic; urgency=medium [Kai-Chuan Hsieh] * alsa-mixer: Correct ucm card name (LP: #1881094) [Hui Wang] * d/p/0901-alsa-solaris-oss-remove-unnecessary-error-handling-w.patch * d/p/0902-alsa-Improve-resume-logic-after-alsa-suspend.patch * (LP: #1882042) -- Kai-Chuan Hsieh Wed, 27 May 2020 16:42:50 +0800 ** Changed in: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882042 Title: [SRU] Linux,Ubuntu,18.4,CI,OLP15,PRTS, Audio/video is out of sync/lag when enter Suspend during playback Status in HWE Next: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: [Impact] Users reported the audio and video is out of sync when entering suspend during playback on bionic. [Fix] The mainline pulseaudio already has the fix for this issue, and the fix is already in the eoan, focal and groovy, but it is not in the bionic. [Test Case] open a online video on the firefox, while it is playing, suspend the system, wait for 30 seconds, resume the system, the audio and video is still on the sync. [Potential Regression Risk] Low, these 2 patches are already in the mainline pulseaudio, and already in the eoan, focal and groovy. Most of the change is in the suspend/unsuspend on alsa sink/source, the potential regression risk is the playback/recording stops working after machine suspend and resume or playback/recording has an obvious discontinuity before suspend and after resume. I have done the test on a Lenovo and a Dell machine, the playback/recording worked well after resuming. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882042/+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 1886702] [NEW] cosmetic issue: updates tab's text is not left aligned
Public bug reported: Text alignment in updates tab is not consistent with other tabs. Text is center aligned as shown in screenshot. I think it should be left aligned. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 22:59:03 2020 InstallationDate: Installed on 2019-02-05 (518 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-04-26 (72 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "update tab text alignment.png" https://bugs.launchpad.net/bugs/1886702/+attachment/5390569/+files/update%20tab%20text%20alignment.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1886702 Title: cosmetic issue: updates tab's text is not left aligned Status in software-properties package in Ubuntu: New Bug description: Text alignment in updates tab is not consistent with other tabs. Text is center aligned as shown in screenshot. I think it should be left aligned. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 22:59:03 2020 InstallationDate: Installed on 2019-02-05 (518 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-04-26 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1886702/+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 1698388] Re: Assertion failure in journal-remote-parse.c
** Description changed: + [impact] + + assertion failure in systemd-journal-remote + + [test case] + + only happens under specific circumstances, which is unclear exactly how + to reproduce it + + [regression potential] + + any regression would likely result in the failure/crash of systemd- + journal-remote program while processing data from a remote source. + + [scope] + + this is needed only for x. + + this is fixed by commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1 which + is included upstream starting in v230, so this is already included in b + and later. + + [original description] + I am observing the following assertion failure in systemd-journal- remote: Assertion 'source->filled <= source->size' failed at ../src/journal- remote/journal-remote-parse.c:95, function get_line(). Aborting. Systemd version: systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Ubuntu release: Description: Ubuntu 16.04.1 LTS Release: 16.04 Package version: systemd: - Installed: 229-4ubuntu13 - Candidate: 229-4ubuntu17 + Installed: 229-4ubuntu13 + Candidate: 229-4ubuntu17 It looks like this issue has been fixed upstream in v230, specifically in commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1. Could this particular commit be backported? ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Xenial) Status: Confirmed => 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/1698388 Title: Assertion failure in journal-remote-parse.c Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Bug description: [impact] assertion failure in systemd-journal-remote [test case] only happens under specific circumstances, which is unclear exactly how to reproduce it [regression potential] any regression would likely result in the failure/crash of systemd- journal-remote program while processing data from a remote source. [scope] this is needed only for x. this is fixed by commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1 which is included upstream starting in v230, so this is already included in b and later. [original description] I am observing the following assertion failure in systemd-journal- remote: Assertion 'source->filled <= source->size' failed at ../src/journal- remote/journal-remote-parse.c:95, function get_line(). Aborting. Systemd version: systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Ubuntu release: Description: Ubuntu 16.04.1 LTS Release: 16.04 Package version: systemd: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu17 It looks like this issue has been fixed upstream in v230, specifically in commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1. Could this particular commit be backported? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698388/+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 1886697] [NEW] Xorg crash
Public bug reported: Reproducible on my system. Whenever my computer "sleeps" while running a specific program (Phenix), when I return to check on the job, the Desktop screen does not load. Alt-F2 and other routes have not been successful in recovery the Desktop GUI or log-in. However, if I stay at my computer and prevent the computer from sleeping, the job completes without GUI death. I don't know how to search the syslog, but I expect to find something funky around something like "GUI going to sleep". The reason I think it is a true "crash" is, despite being away from my the PC for 1 hr, the job directory is empty. This makes me think the computer processes were halted during the events that lead to the GUI death. I have played with my GPU settings. As per this NVIDIA thread https://forums.developer.nvidia.com/t/random-xid-61-and-xorg-lock- up/79731/252, I have set my minumum clock speed to 1050mHz. This had been successful up until this point at preventing a different issue not related to this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 13:26:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:13a2] InstallationDate: Installed on 2020-05-26 (41 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5a52a344-c840-428b-89b5-b3c2e86fbc43 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1886697 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: Reproducible on my system. Whenever my computer "sleeps" while running a specific program (Phenix), when I return to check on the job, the Desktop screen does not load. Alt-F2 and other routes have not been successful in recovery the Desktop GUI or log-in. However, if I stay at my computer and prevent the computer from sleeping, the job completes without GUI death. I don't know
[Touch-packages] [Bug 1851056] Re: "Proceeding WITHOUT firewalling in effect!" warning
as Eoan will be EOL in weeks, marking this wontfix. ** Changed in: systemd (Ubuntu Eoan) Status: New => Won't Fix -- 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/1851056 Title: "Proceeding WITHOUT firewalling in effect!" warning Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: Won't Fix Bug description: Hello everyone, I noticed a strange systemd warning in my kernel log about "Proceeding WITHOUT firewalling in effect!" There is an older Debian bug mention about this same issue and it is said there that it was fixed last year: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872560 Release: Ubuntu 19.10, fresh install, latest updates with updates-testing repository enabled Systemd-package version: 242-7ubuntu3 Kernel: Linux 5.3.0-21-generic Here is the relevant warning information via running sudo dmesg after boot: [2.096064] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 [2.101034] Lockdown: systemd: BPF is restricted; see man kernel_lockdown.7 [2.136885] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. [2.142209] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.) [2.158190] systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. [2.197029] systemd[1]: Listening on Journal Socket. [2.203708] systemd[1]: Starting Create list of required static device nodes for the current kernel... [2.243900] bpfilter: Loaded bpfilter_umh pid 420 #Continues normally from here without anything that seems odd The included attachment .txt has more information. From what I've read online from various bug trackers from other distributions this should be related to a missing kernel option (CONFIG_BPF_SYSCALL=y), but this option seems to be enabled: # Output after running in commandline: grep BPF /boot/config-`uname -r` # Kernel settings seem to be correct? CONFIG_CGROUP_BPF=y CONFIG_BPF=y CONFIG_BPF_SYSCALL=y CONFIG_BPF_JIT_ALWAYS_ON=y CONFIG_IPV6_SEG6_BPF=y CONFIG_NETFILTER_XT_MATCH_BPF=m CONFIG_BPFILTER=y CONFIG_BPFILTER_UMH=m CONFIG_NET_CLS_BPF=m CONFIG_NET_ACT_BPF=m CONFIG_BPF_JIT=y CONFIG_BPF_STREAM_PARSER=y CONFIG_LWTUNNEL_BPF=y CONFIG_HAVE_EBPF_JIT=y CONFIG_BPF_EVENTS=y CONFIG_BPF_KPROBE_OVERRIDE=y CONFIG_TEST_BPF=m Also my friend just installed 19.10 on his machine and is seeing the same warning, but I haven't found anyone else mentioning this issue at least on the latest Ubuntu 19.10. The same warning message is appearing if I run Ubuntu 19.10 in live mode from the USB stick. What I expected to happen: no such error (it doesn't appear on Fedora or openSUSE Tumbleweed that I've recently had installed on my other SSD) What happened instead: error appears during every boot sequence It's also worth stressing that the firewall is functioning just fine (using standard ufw) despite the error, so I'm guessing this is a harmless warning. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1851056/+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
** Description changed: - After applying updates to Ubuntu 18.04 my desktop (apple mini with + [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 + 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 + #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) + (gdb) -->8-- - and the kernel message buffer lists + 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 + 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). - --- + 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#
[Touch-packages] [Bug 1872200] Autopkgtest regression report (apt/2.0.3)
All autopkgtests for the newly accepted apt (2.0.3) for focal have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.11-0ubuntu27 (amd64) reprotest/0.7.14 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1872200 Title: apt does not accept globs and regexes in some cases Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Bug description: [Impact] Users can't use * wildcards anymore in focal, except by accident in apt list. For apt list, we now start restricting wildcard syntax to the same syntax install now accepts, and at the same time we remove the restrictions on which patterns are accepted (which only accepted patterns starting in ~ or ?), so !~napt now works, and does not accidentally match as a wildcard. [Test case] Test that * wildcards work for both install and list, and test that a ? wildcard does not. We included autopkgtests for those: BEGIN TESTS # # * wildcards should still work testsuccessequal "Listing... automatic1/now 1.0 i386 [installed,local] automatic2/now 1.0 i386 [installed,local]" apt list 'automatic*' testfailureequal "Reading package lists... Building dependency tree... Reading state information... Note, selecting 'automatic1' for glob 'automatic*' Note, selecting 'automatic2' for glob 'automatic*' automatic1 is already the newest version (1.0). automatic1 set to manually installed. automatic2 is already the newest version (1.0). automatic2 set to manually installed. You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: broken : Depends: does-not-exist but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution)." apt install -s 'automatic*' # other wildcards should fail testfailureequal "Listing... E: input:0-10: error: Expected pattern automatic? ^^" apt list 'automatic?' testfailureequal "Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package automatic?" apt install -s 'automatic?' END TESTS # Also it might be worth checking that apt list !~napt works. This used to produce an empty list, as it was accidentally matched as a wildcard and produced no result - now it produces every package whose name does not contain "apt". [Regression potential] The changes only affect interactive users, as apt(8) is not stable for in-script use, hence they can fix up their command-line if it stops working for them (though, really, more should work now). No scripts will be broken :) [Squashed in changes] The SRU also fixes potential build failures by correctly prefxing nullptr_t with the std:: namespace, and includes updated Dutch documentation. [Original bug report] Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+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 1874953] Autopkgtest regression report (less/551-1ubuntu0.1)
All autopkgtests for the newly accepted less (551-1ubuntu0.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: mercurial/5.3.1-1ubuntu1 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#less [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1874953 Title: dpkg: conffile difference visualizer subprocess returned error exit status 127 Status in dpkg package in Ubuntu: Invalid Status in less package in Ubuntu: Fix Released Status in smartmontools package in Ubuntu: Invalid Status in dpkg source package in Focal: Invalid Status in less source package in Focal: Fix Committed Status in smartmontools source package in Focal: Invalid Status in dpkg source package in Groovy: Invalid Status in less source package in Groovy: Fix Released Status in smartmontools source package in Groovy: Invalid Status in dpkg package in Debian: New Status in less package in Debian: Fix Committed Bug description: [Impact] During a release upgrade to Ubuntu 20.04 LTS some users are not able to view the differences made to a configuration file during the upgrade process. This creates a bad user experience and leads to extra crash reports. [Test Case] 1) Upgrade from a not usr-merged system (Ubuntu 16.04 LTS) to Ubuntu 18.04 LTS 2) Install the smartmontools package 3) Edit /etc/default/smartmontools (it's enough to just add a comment in there) 4) Upgrade to Ubuntu 20.04 LTS (this requires do-release-upgrade -d as 20.04.1 is not out yet so release upgrades are not enabled) To test the fix in the version of less from focal-proposed some hackery of the release upgrader code will be necessary as it disables proposed during the upgrade process. After enabling -proposed for bionic you'll want to run do-release-upgrade -d, then cancel the upgrade. After which you can cd to /tmp/ubuntu-release- upgrader-$MKTMPDIR and edit DistUpgradeController.py and the if statement around line 641 re "Disable proposed on upgrade to a development release". Then run 'sudo ./focal'. [Regression Potential] None, as we are just calling update-alternatives in the preinst of less. Issue occurred on upgrade from 19.10 to 20.04 ProblemType: PackageDistroRelease: Ubuntu 20.04 Package: smartmontools 7.1-1build1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 21:33:08 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 InstallationDate: Installed on 2011-06-18 (3233 days ago)InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2SourcePackage: smartmontools Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) mtime.conffile..etc.default.smartmontools: 2017-12-08T19:12:02.064375 mtime.conffile..etc.smartd.conf: 2017-12-08T20:27:28.727282 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1874953/+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 1364641] Re: [Address book] All, Favourites -- there should be an option to create more groups.
** Information type changed from Public to Public Security ** Information type changed from Public Security to Private -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1364641 Title: [Address book] All, Favourites -- there should be an option to create more groups. Status in Ubuntu UX: In Progress Status in address-book-app package in Ubuntu: Triaged Bug description: In the contact list, there are two lists: All Favourites There should be an option to create more lists, such as "Family" -UX comment- Adding/creating a new group should be addressed via app settings. The new header component will be able to hold more than two lists. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1364641/+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 1870088] Autopkgtest regression report (xz-utils/5.2.4-1ubuntu1)
All autopkgtests for the newly accepted xz-utils (5.2.4-1ubuntu1) for focal have finished running. The following regressions have been reported in tests triggered by the package: epson-inkjet-printer-escpr/1.7.7-1 (arm64) apt/2.0.2 (armhf) ostree/2020.3-1 (ppc64el) firejail/0.9.62-3 (ppc64el) piuparts/1.1.1build1 (ppc64el, arm64, s390x) systemd/245.4-4ubuntu3 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#xz-utils [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal Status in xz-utils package in Ubuntu: Confirmed Status in xz-utils source package in Focal: Fix Committed Status in xz-utils package in Debian: New Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz dh build --parallel make[2]: Leaving directory '/<>' dh_testroot -O--parallel dh_prep -O--parallel debian/rules override_dh_auto_install make[2]: Entering directory '/<>' dh_auto_install --builddirectory debian/xzdec-build dh_auto_install --builddirectory debian/normal-build dh_auto_install --builddirectory debian/static-build set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \ install -d debian/tmp/lib/$arch; \ mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \ dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \ ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such file or directory make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:4: install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package
** Changed in: libimobiledevice (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1721398 Title: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package Status in libimobiledevice package in Ubuntu: Confirmed Status in libimobiledevice package in Debian: New Bug description: Currently all of the other important utilities are included for installation on Ubuntu. However currently though a Ubuntu Linux user, is unable to perform an iOS device restore. In order to do so currently the user needs to have some way of running an up to date iTunes software with a usb connection to the iPhone, iPad or iPod Touch. Which is quite a hassle to go through in order to completely reload the device's iOS software. It would be much better if a binary compiled version of the software (idevicerestore and libirecovery) could be included in the utilities package. It would allow the Ubuntu user to be able to quickly and easily perform software update or device restore functions. Without the need for a virtual machine running a compatible version of Windows and iTunes etc. While also saving them from having to run Wine, its dependencies, iTunes and its own software requirements. All the would need is what is required to install idevicerestore and run its actions (the appropriate iOS release download image file). The code for idevice restore is available here (https://cgit.sukimashita.com/idevicerestore.git/) and the library from here (https://cgit.sukimashita.com/libirecovery.git/). Running Ubuntu 16.04.3 libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1721398/+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 1832754] Re: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs.
** Description changed: + [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 ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Status: New => 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/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: In Progress 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 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot
** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libseccomp (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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: Incomplete Status in libseccomp source package in Bionic: New Status in systemd source package in Bionic: New Bug 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: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.family: Macmini dmi.product.name: Macmini5,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: MATE Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.4.0-1ubuntu1~18.04 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-30 (460 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) NonfreeKernelModules: wl Package: libseccomp2 2.4.3-1ubuntu3.18.04.2 PackageArchitecture: amd64
[Touch-packages] [Bug 1721398] Re: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package
** Bug watch added: Debian Bug tracker #963042 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963042 ** Also affects: libimobiledevice (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963042 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1721398 Title: Missing "idevicerestore" & "libirecovery" from libimobiledevice-utils package Status in libimobiledevice package in Ubuntu: Confirmed Status in libimobiledevice package in Debian: Unknown Bug description: Currently all of the other important utilities are included for installation on Ubuntu. However currently though a Ubuntu Linux user, is unable to perform an iOS device restore. In order to do so currently the user needs to have some way of running an up to date iTunes software with a usb connection to the iPhone, iPad or iPod Touch. Which is quite a hassle to go through in order to completely reload the device's iOS software. It would be much better if a binary compiled version of the software (idevicerestore and libirecovery) could be included in the utilities package. It would allow the Ubuntu user to be able to quickly and easily perform software update or device restore functions. Without the need for a virtual machine running a compatible version of Windows and iTunes etc. While also saving them from having to run Wine, its dependencies, iTunes and its own software requirements. All the would need is what is required to install idevicerestore and run its actions (the appropriate iOS release download image file). The code for idevice restore is available here (https://cgit.sukimashita.com/idevicerestore.git/) and the library from here (https://cgit.sukimashita.com/libirecovery.git/). Running Ubuntu 16.04.3 libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1721398/+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 1882636] Re: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777
Jul 07 00:08:37 betty io.elementary.a[3348]: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 17 Jul 07 00:08:40 betty io.elementary.a[3348]: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 17 Jul 07 00:08:41 betty gnome-shell[1966]: pop-shell: [INFO] making above Jul 07 00:08:41 betty gnome-shell[1966]: pop-shell: [DEBUG] xprop -id 0x2a07177 _MOTIF_WM_HINTS Jul 07 00:08:41 betty gnome-shell[1966]: pop-shell: [DEBUG] _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x0, 0x0, 0x0, 0x0 Jul 07 00:08:41 betty WebKitWebProces[6490]: Failed to load module "appmenu-gtk-module" Jul 07 00:08:48 betty systemd[1669]: Started VTE child process 6523 launched by gnome-terminal-server process 2448. Jul 07 00:10:38 betty systemd[1669]: Started VTE child process 6538 launched by gnome-terminal-server process 2448. Jul 07 00:10:44 betty gnome-shell[1966]: pop-shell: [INFO] making above Jul 07 00:10:44 betty gnome-shell[1966]: pop-shell: [DEBUG] xprop -id 0x2a07177 _MOTIF_WM_HINTS Jul 07 00:10:44 betty gnome-shell[1966]: pop-shell: [DEBUG] _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x0, 0x0, 0x0, 0x0 Jul 07 00:10:44 betty WebKitWebProces[6547]: Failed to load module "appmenu-gtk-module" Jul 07 00:10:56 betty geoclue[1460]: Failed to query location: TLS/SSL support not available; install glib-networking -- 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/1882636 Title: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777 Status in glib-networking package in Ubuntu: Incomplete Bug description: OS: Pop!_OS 20.04 LTS x86_64 Host: XPS 13 9370 Kernel: 5.4.0-7634-generic Uptime: 2 hours, 50 mins Packages: 1817 (dpkg), 20 (snap) Shell: bash 5.0.16 Resolution: 1920x1080 DE: GNOME WM: Mutter WM Theme: Pop Theme: Pop-dark [GTK2/3] Icons: Pop [GTK2/3] Terminal: gnome-terminal CPU: Intel i5-8250U (8) @ 3.400GHz GPU: Intel UHD Graphics 620 Memory: 3322MiB / 15729MiB Summary(cont) - Attempt to input Google account info into online account util and get error--> TLS/SSL support not available; install glib-networking. https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777 Referenced this BUG REPORT ##Downloaded Deb build but I'm having an issue applying appropriate inputs in the provided documentation. Please help!## To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1882636/+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 1886672] [NEW] Multiple screen display issues
Public bug reported: New bug for me. Issue was fine till last week. I think this may be related to the following as it started happening shortly thereafter. I have XPS13 with second monitor, all working fine till I lock screen or suspend. Then my second monitor will not 'resume'. I.e. stays off. This behaviour started after (or shortly after) playing a wine game using Lutris to launch. Shutting game down and almost immediately hitting suspend on the laptop. Was rushing out. It's a wild shot in the dark but I think something got messed up / not saved correctly in this process. To get it working I need to unplug monitor (using USB-C > HDMI) > suspend > plug in monitor > resume and sometimes still need to open display settings before it 'kicks in'. Damn annoying. Hope someone can help :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Jul 7 16:44:52 2020 DistUpgraded: 2020-05-15 15:17:42,708 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:082a] InstallationDate: Installed on 2019-01-29 (525 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-15 (53 days ago) dmi.bios.date: 11/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0PVG6D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 082A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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 focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1886672 Title: Multiple screen display issues Status in xorg package in Ubuntu: New Bug description: New bug for me. Issue was fine till last week. I think this may be related to the following as it started happening shortly thereafter. I have XPS13 with second monitor, all working fine till I lock screen or suspend. Then my second monitor will not 'resume'. I.e. stays off. This behaviour started after (or shortly after) playing a wine game using Lutris to launch. Shutting game down and almost immediately hitting suspend on the laptop. Was rushing out. It's a wild shot in the dark but I think something got messed up / not saved correctly in this process. To get it working I need to unplug monitor (using USB-C > HDMI) > suspend > plug in monitor > resume and sometimes still need to open display settings before it 'kicks in'. Damn annoying. Hope someone can help :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Jul 7 16:44:52 2020 DistUpgraded: 2020-05-15 15:17:42,708 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00
[Touch-packages] [Bug 1826387] Re: systemd-networkd restart brings down bond slaves
*** This bug is a duplicate of bug 1833671 *** https://bugs.launchpad.net/bugs/1833671 ** This bug has been marked a duplicate of bug 1833671 bond interfaces stop working after restart of systemd-networkd -- 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/1826387 Title: systemd-networkd restart brings down bond slaves Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Won't Fix Bug description: Reported upstream as https://github.com/systemd/systemd/issues/10118 Ubuntu bionic, systemd version 237-3ubuntu10.19 When systemd-networkd is used to manage network bonds, upon systemd- networkd, bonds are brought down for ~10 seconds affecting connectivity to the server. From networkd logs (truncated to: ``` # journalctl -b -u systemd-networkd | grep enp3s0f Apr 25 12:45:33 compute01 systemd-networkd[30824]: Ignoring /etc/systemd/network/01-enp3s0f1.network, because it's not a regular file with suffix .netdev. Apr 25 12:45:33 compute01 systemd-networkd[30824]: Ignoring /etc/systemd/network/00-enp3s0f0.network, because it's not a regular file with suffix .netdev. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Flags change: +SLAVE +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link 6 added Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: udev initialized link Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Saved original MTU: 9000 Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Flags change: +SLAVE +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link 3 added Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: udev initialized link Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Saved original MTU: 9000 Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link state is up-to-date Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: found matching network '/etc/systemd/network/01-enp3s0f1.network' Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Started LLDP. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Enslaving by 'bond0' Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Link 'enp3s0f1' was up when attempting to enslave it. Bringing link down. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Bringing link down Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Enslaving link 'enp3s0f1' Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link state is up-to-date Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: found matching network '/etc/systemd/network/00-enp3s0f0.network' Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link does not request DHCPv6 prefix delegation Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Started LLDP. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Enslaving by 'bond0' Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Link 'enp3s0f0' was up when attempting to enslave it. Bringing link down. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Bringing link down Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Enslaving link 'enp3s0f0' Apr 25 12:45:33 compute01
[Touch-packages] [Bug 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot
This seems related: * https://bugzilla.redhat.com/show_bug.cgi?id=1653068 * https://github.com/systemd/systemd/pull/11157 I can't say why the libseccomp update would change anything, though the redhat bug shows an AVC denial, so I wonder if you see anything related to systemd-resolved with 'journalctl | grep audit | grep systemd' at the time of the boot failure. If you see a seccomp denial, that might indicate a change in libseccomp to further investigate. Regardless, systemd should not be crashing and https://github.com/systemd/systemd/pull/11157 should be backported IME. ** Bug watch added: Red Hat Bugzilla #1653068 https://bugzilla.redhat.com/show_bug.cgi?id=1653068 -- 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: Incomplete Bug 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: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.family: Macmini dmi.product.name: Macmini5,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop:
[Touch-packages] [Bug 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot
Note that 2.4.1-0ubuntu0.18.04.2 was previously in bionic and had been since May of 2019 (2.3.1-2.1ubuntu4 is what bionic was released with, but later updated to 2.4.1-0ubuntu0.18.04.2). 2.4.1-0ubuntu0.18.04.2 can be found here: https://launchpad.net/ubuntu/+source/libseccomp/2.4.1-0ubuntu0.18.04.2 -- 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: Incomplete Bug 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: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.family: Macmini dmi.product.name: Macmini5,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: MATE Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.4.0-1ubuntu1~18.04 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-30 (460 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) NonfreeKernelModules: wl Package: libseccomp2 2.4.3-1ubuntu3.18.04.2 PackageArchitecture:
[Touch-packages] [Bug 1885313] Re: evince crashes when opening rfc8798.pdf
@Erik, thanks for confirming it's fixed for you on focal. We should get the poppler version in the evince snap updated -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1885313 Title: evince crashes when opening rfc8798.pdf Status in poppler package in Ubuntu: Fix Released Status in poppler package in Debian: New Bug description: evince reproducabely crashes when opening the file rfc8798.pdf from https://www.rfc-editor.org/rfc/rfc8798.pdf: $ evince --version GNOME Document Viewer 3.28.4 $ evince rfc8798.pdf Segmentation fault (core dumped) $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" Required information: 1) Ubuntu release info: $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 2) Package version info: $ apt-cache policy evince evince: Installed: 3.28.4-0ubuntu1.2 Candidate: 3.28.4-0ubuntu1.2 Version table: *** 3.28.4-0ubuntu1.2 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) Expected outcome: I expected evince to successfully open the PDF, allowing me to read the document. 4) Observed behavior: The default PDF reader of Ubuntu, evince, crashed (reporting a "segmentation fault". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1885313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886128] Re: systemd-resolved does not resolve address due to udp payload size.
Are you referring to edns0 from glibc to the local stub resolver, or
edns0 from systemd-resolved to the upstream nameserver?
I don't see any problem when i resolve the name on bionic:
$ lsb_release -c
Codename: bionic
$ dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.41 amd64system and service manager
$ dig +short mharder-formrec.cognitiveservices.azure.com
westus2.api.cognitive.microsoft.com.
cognitiveusw2prod.trafficmanager.net.
cognitiveusw2prod.azure-api.net.
apimgmttmmtjxmdjuddplpewicwu8gnxxj7ehaj3ubplfwharv.trafficmanager.net.
cognitiveusw2prod-westus2-01.regional.azure-api.net.
apimgmthsn6metwepz5stnvukztxi3dks7nna13rgbo90ytolj.cloudapp.net.
52.229.16.14
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1886128
Title:
systemd-resolved does not resolve address due to udp payload size.
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Description: Ubuntu 18.04.4 LTS
Release: 18.04
systemd-resolve --version
systemd 237
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
-PCRE2 default-hierarchy=hybrid
We met an error: on an attempt to resolve address, the following issue
appears:
; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>>
mharder-formrec.cognitiveservices.azure.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;mharder-formrec.cognitiveservices.azure.com. IN A
;; Query time: 231 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Apr 28 20:47:14 UTC 2020
;; MSG SIZE rcvd: 72
Let me provide you important notes about the issue:
1) It's not reproducing on Ubuntu 16;
2) Bypassing systemd-resolve - everything works fine;
3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE
Successful query:
113516:27:25.964386 10.1.0.4168.63.129.16 DNS 128
Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com
OPT
Domain Name System (query)
Transaction ID: 0xc2d4
Flags: 0x0120 Standard query
0... = Response: Message is a query
.000 0... = Opcode: Standard query (0)
..0. = Truncated: Message is not truncated
...1 = Recursion desired: Do query recursively
.0.. = Z: reserved (0)
..1. = AD bit: Set
...0 = Non-authenticated data: Unacceptable
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 1
Queries
mharder-formrec.cognitiveservices.azure.com: type A, class IN
Additional records
: type OPT
Name:
Type: OPT (41)
UDP payload size: 4096
Higher bits in extended RCODE: 0x00
EDNS0 version: 0
Z: 0x
0... = DO bit: Cannot handle DNSSEC security
RRs
.000 = Reserved: 0x
Data length: 12
Option: COOKIE
Unsuccessful query:
112816:27:25.713886 10.1.0.4168.63.129.16 DNS 116
Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com
OPT
Domain Name System (query)
Transaction ID: 0x198d
Flags: 0x0100 Standard query
0... = Response: Message is a query
.000 0... = Opcode: Standard query (0)
..0. = Truncated: Message is not truncated
...1 = Recursion desired: Do query recursively
.0.. = Z: reserved (0)
...0 = Non-authenticated data: Unacceptable
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 1
Queries
mharder-formrec.cognitiveservices.azure.com: type A, class IN
Additional records
: type OPT
Name:
Type: OPT (41)
UDP payload size: 512
Higher bits in extended RCODE: 0x00
EDNS0 version: 0
Z: 0x
0... = DO bit: Cannot handle DNSSEC security
RRs
.000 = Reserved: 0x
Data length: 0
Notable difference:
Success:
UDP payload size: 4096
Failure:
UDP payload size: 512
And notable differences in the responses:
Success:
Flags: 0x8180 Standard query response, No error
..0.
[Touch-packages] [Bug 1882248] Re: plug headset won't proper reconfig ouput to it on machine with default output
@Seb, Ok, got it, this bug needs both kernel fix and pulseaudio fix, SRU the kernel fix first, then the fix of pulseaudio. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in linux-oem source package in Bionic: Fix Committed Status in pulseaudio source package in Bionic: New Bug description: For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
We discussed it in our meeting, it probably makes sense to include it in the next SRU we do but we don't believe it deserves rls tracking, updating the tag according to that decision ** Tags removed: rls-ff-incoming ** Tags added: rls-ff-notfixing -- 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/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Status in network-manager source package in Focal: Confirmed Bug description: I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882248] Re: plug headset won't proper reconfig ouput to it on machine with default output
@Hui, since there is a pulseaudio targetted entry there I'm assigning that to you, feel free to close as invalid if only the kernel needs fixing ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: pulseaudio (Ubuntu Bionic) Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in linux-oem source package in Bionic: Fix Committed Status in pulseaudio source package in Bionic: New Bug description: For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886618] Re: command-not-found gets stuck on locales with non-English-like collation rules
** Package changed: apt (Ubuntu) => command-not-found (Ubuntu) -- 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/1886618 Title: command-not-found gets stuck on locales with non-English-like collation rules Status in command-not-found package in Ubuntu: Confirmed Bug description: The bug in question: https://askubuntu.com/q/1142923/162831 Namely, cnf-update-db takes forever and eats almost all your disk time if your locale has different collation rules from English such as different sorting and/or case conversion. A workaround by supplying a C locale: https://askubuntu.com/a/1147303/162831 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1886618/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881972] Re: systemd-networkd crashes with invalid pointer
@r-2ohn-d can you test with systemd from this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1881972
Title:
systemd-networkd crashes with invalid pointer
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
In Progress
Bug description:
[impact]
systemd-networkd double-free causes crash under some circumstances,
such as adding/removing ip rules
[test case]
see original description
[regression potential]
this strdup's strings during addition of routing policy rules, so any
regression would likely occur when adding/modifying/removing ip rules,
possibly including networkd segfault or failure to add/remove/modify
ip rules.
[scope]
this is needed for bionic.
this is fixed by upstream commit
eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in
v240, so this is already included in Focal and later.
I did not research what original commit introduced the problem, but
the reporter indicates this did not happen for Xenial so it's unlikely
this is a problem in Xenial or earlier.
[original description]
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-
ssd/ubuntu-bionic-18.04-amd64-server-20200131 with
systemd-237-3ubuntu10.33 does NOT have the problem, but the next most
recent AWS AMI ubuntu/images/hvm-ssd/ubuntu-
bionic-18.04-amd64-server-20200311 with systemd-including
237-3ubuntu10.39 does.
Also, a system booted from the (good) 20200131 AMI starts showing the
problem after updating only systemd (to 237-3ubuntu10.41) and its
direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly
confident that a change to the systemd package between
237-3ubuntu10.33 and 237-3ubuntu10.39 introduced the problem and it is
still present.
On the NAT router I use three interfaces and have separate routing
tables for admin and forwarded traffic. Things come up fine initially
but every 30-60 minutes (DHCP lease renewal time?) one or more
interfaces is reconfigured and most of the time systemd-networkd will
crash and need to be restarted. Eventually the system becomes
unreachable when the default crash loop backoff logic prevents the
network service from being restarted at all. The log excerpt attached
illustrates the crash loop.
Also including the netplan and networkd config files below.
# grep . /etc/netplan/*
/etc/netplan/50-cloud-init.yaml:# This file is generated from information
provided by the datasource. Changes
/etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance
reboot. To disable cloud-init's
/etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a
file
/etc/netplan/50-cloud-init.yaml:#
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
/etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
/etc/netplan/50-cloud-init.yaml:network:
/etc/netplan/50-cloud-init.yaml:version: 2
/etc/netplan/50-cloud-init.yaml:ethernets:
/etc/netplan/50-cloud-init.yaml:ens5:
/etc/netplan/50-cloud-init.yaml:dhcp4: true
/etc/netplan/50-cloud-init.yaml:match:
/etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
/etc/netplan/50-cloud-init.yaml:set-name: ens5
/etc/netplan/99_config.yaml:network:
/etc/netplan/99_config.yaml: version: 2
/etc/netplan/99_config.yaml: renderer: networkd
/etc/netplan/99_config.yaml: ethernets:
/etc/netplan/99_config.yaml:ens6:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-routes: false
/etc/netplan/99_config.yaml:ens7:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz
/etc/netplan/99_config.yaml: mtu: 1500
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-mtu: false
/etc/netplan/99_config.yaml:use-routes: false
# grep . /etc/networkd-dispatcher/*/*
/etc/networkd-dispatcher/configured.d/nat:#!/bin/bash
/etc/networkd-dispatcher/configured.d/nat:# Do additional configuration for
the inside and outside interfaces
/etc/networkd-dispatcher/configured.d/nat:# route table used for
forwarded/routed/natted traffic
/etc/networkd-dispatcher/configured.d/nat:FWD_TABLE=99
/etc/networkd-dispatcher/configured.d/nat:if [ "${IFACE}" = "ens6" ]; then
/etc/networkd-dispatcher/configured.d/nat: # delete link-local
[Touch-packages] [Bug 1886618] Re: command-not-found gets stuck on locales with non-English-like collation rules
Thank you for your bug report, what Ubuntu version and locale do you use? It's a bit weird, it was just broken on some locales there would be other reports about the issue... -- 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/1886618 Title: command-not-found gets stuck on locales with non-English-like collation rules Status in apt package in Ubuntu: Confirmed Bug description: The bug in question: https://askubuntu.com/q/1142923/162831 Namely, cnf-update-db takes forever and eats almost all your disk time if your locale has different collation rules from English such as different sorting and/or case conversion. A workaround by supplying a C locale: https://askubuntu.com/a/1147303/162831 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886618/+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 1753115] Re: add-apt-repository documentation does not mention --no-updates option
** Changed in: software-properties (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1753115 Title: add-apt-repository documentation does not mention --no-updates option Status in software-properties package in Ubuntu: Confirmed Bug description: The default has changed so that --updates is the default. The man page should be updated to reflect that and to document the -n --no- updates option for 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1753115/+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 1886653] [NEW] cups-pki-expired
Public bug reported: The printer always goes to stopped state in Ubuntu 20.04. Print properties window has status message saying: "cups-pki-expired". I have HP color laserjet m552, which Ubuntu discovers directly from the local network and configures automatically. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 14:40:00 2020 InstallationDate: Installed on 2019-11-03 (247 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for HP_Color_LaserJet_M552_5F80BF_: implicitclass://HP_Color_LaserJet_M552_5F80BF_/ MachineType: LENOVO 81H1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-03-28 (100 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1886653 Title: cups-pki-expired Status in cups package in Ubuntu: New Bug description: The printer always goes to stopped state in Ubuntu 20.04. Print properties window has status message saying: "cups-pki-expired". I have HP color laserjet m552, which Ubuntu discovers directly from the local network and configures automatically. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 14:40:00 2020 InstallationDate: Installed on 2019-11-03 (247 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for HP_Color_LaserJet_M552_5F80BF_: implicitclass://HP_Color_LaserJet_M552_5F80BF_/ MachineType: LENOVO 81H1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-03-28 (100 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1886653/+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 1753115] Re: add-apt-repository documentation does not mention --no-updates option
add-apt-repository -h mentions the option, though. ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1753115 Title: add-apt-repository documentation does not mention --no-updates option Status in software-properties package in Ubuntu: Confirmed Bug description: The default has changed so that --updates is the default. The man page should be updated to reflect that and to document the -n --no- updates option for 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1753115/+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 1838329] Re: Cryptswap periodically fails to mount at boot due to missing a udev notification
** Merge proposal linked: https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/386957 -- 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/1838329 Title: Cryptswap periodically fails to mount at boot due to missing a udev notification Status in systemd: New Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: New Bug description: [impact] systems using cryptsetup-based encrypted swap may hang during boot due to udevd missing the notification that swap has been setup on the newly created swap device. [test case] see original description, and reproduction is intermittent based on timing [regression potential] any regression would likely occur during, or after, boot when creating an encrypted swap device and/or while waiting to activate the new swap device. Regressions may cause failure to correctly enable swap and/or hung boot waiting for the swap device. [scope] this was (potentially) fixed upstream with PR 15836, which is not yet included in any upstream release, so this is needed in all releases, including groovy. also note while the upstream bug is closed, and code review seems to indicate this *should* fix this specific issue, there are some comments in the upstream bug indicating it may not completely solve the problem, although there is no further debug of the new reports. [original description] On some systems, cryptsetup-based encrypted swap partitions cause systemd to get stuck at boot. This is a timing-sensitive Heisenbug, so the rate of occurrence varies from one system to another. Some hardware will not experience the issue at all, others will only occasionally experience the issue, and then there are the unlucky who are unable to boot at all, no matter how many times they restart. The workaround is for the cryptsetup-generator to generate cryptswap service entries that call `udevadm trigger` after `mkswap`. This will ensure that the udev event is triggered, so that systemd is notified that the encrypt swap partition is ready to activate. This patch has already been submitted upstream to systemd, but it was not accepted because it is a workaround for the side effect of systemd not seeing the udev event upon creating the swap partition. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1838329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 260918]
Sorry, bug fixed after Sys update (facepalm) On Tue, Jul 7, 2020 at 5:24 PM Jeremielapuree <260...@bugs.launchpad.net> wrote: > Does the bug still occur with wine-5.12? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (283421). > https://bugs.launchpad.net/bugs/260918 > > Title: > needed: libv4l and associated application patches (or "gspca stopped > working in 2.6.27") > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/260918/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/260918 Title: needed: libv4l and associated application patches (or "gspca stopped working in 2.6.27") Status in Adobe Flash Plugin Tools: Won't Fix Status in Cheese: Unknown Status in Ekiga: Fix Released Status in Mozilla Firefox: Invalid Status in gst-plugins-good: Fix Released Status in GStreamer: Fix Released Status in Kdenlive: Fix Released Status in Kopete: Fix Released Status in Medibuntu: Fix Released Status in OpenCV: Unknown Status in VLC media player: Fix Released Status in Wine: Confirmed Status in amsn package in Ubuntu: Fix Released Status in came package in Ubuntu: Fix Released Status in camorama package in Ubuntu: Invalid Status in camstream package in Ubuntu: Fix Released Status in cheese package in Ubuntu: Invalid Status in ekiga package in Ubuntu: Invalid Status in gst-plugins-good0.10 package in Ubuntu: Fix Released Status in libv4l package in Ubuntu: Fix Released Status in mplayer package in Ubuntu: Fix Released Status in pwlib package in Ubuntu: Fix Released Status in vlc package in Ubuntu: Fix Released Status in xawtv package in Ubuntu: Fix Released Status in cheese source package in Lucid: Invalid Status in amsn source package in Intrepid: Fix Released Status in came source package in Intrepid: Fix Released Status in camorama source package in Intrepid: Invalid Status in camstream source package in Intrepid: Invalid Status in cheese source package in Intrepid: Invalid Status in ekiga source package in Intrepid: Invalid Status in gst-plugins-good0.10 source package in Intrepid: Fix Released Status in libv4l source package in Intrepid: Fix Released Status in mplayer source package in Intrepid: Won't Fix Status in pwlib source package in Intrepid: Fix Released Status in vlc source package in Intrepid: Won't Fix Status in xawtv source package in Intrepid: Fix Released Status in camorama package in Debian: Fix Released Status in gst-plugins-good0.10 package in Fedora: Fix Released Status in pwlib package in Fedora: Fix Released Status in xawtv package in Fedora: Fix Released Bug description: libv4l is a user-space library used by several applications in order to convert webcam streams in user-space instead of kernel-space. As gspca is included in 2.6.27 this is needed in order to (re)support a multitude of webcams supported with ordinary applications. See http://hansdegoede.livejournal.com/3636.html for a more complete description of the software. The latest version is 0.4.0 and is available from http://people.atrpms.net/~hdegoede/ To manage notifications about this bug go to: https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/260918/+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 1886644] [NEW] SRU the current 3.36.4 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade ** Affects: evolution-data-server (Ubuntu) Importance: High Status: Fix Committed ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => High ** Changed in: evolution-data-server (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1886644 Title: SRU the current 3.36.4 stable update Status in evolution-data-server package in Ubuntu: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1886644/+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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic
** Tags added: oem-priority -- 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/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: Fix Committed Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: Fix Committed Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function 1. enable Pre-released updates in Developer Options Software & Updates > Developer Options > Pre-released updates (bionic-proposed) 2. $ sudo apt update 3. $ sudo apt install linux-generic-hwe-18.04-edge 4. $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1264311] Re: BCM43142 bluetooth adapter not finding any bluetooth devices
My Problem was just a naming issue :- $ dmesg | grep -i 'bluetooth' if you are facing some naming problem,the output of above command should be somthing like this -> Bluetooth hci0: Direct firmware load for brcm/BCM43142A0-0489-e062.hcd failed with error -2 Bluetooth: hci0: BCM: Patch brcm/BCM43142A0-0489-e062.hcd not found The Problem here is in this folder : /lib/firmware/brcm $ ls /lib/firmware/brcm/*.hcd The above command gives output of some *.hcd file (in my case BCM.hcd). But my kernal is looking for BCM43142A0-0489-e062.hcd. All you need to do is make a copy and rename. $ cp /lib/firmware/brcm/BCM.hcd /lib/firmware/brcm/BCM43142A0-0489-e062.hcd (in my case) Restart the PC and will see the frimware is loaded. BAM!! Now you can see bluetooh is working. Done. -- 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/1264311 Title: BCM43142 bluetooth adapter not finding any bluetooth devices Status in bluez package in Ubuntu: Invalid Bug description: On my officially Ubuntu-certified Lenovo B590 laptop the BCM43142 bluetooth adapter is not working. I have two further bluetooth devices placed closely to the laptop, non-paired and each being able to discover the other respectively. None of them is able to discover the laptop, nor does 'hcitool scan' on the laptop find any devices. It does not give any errors though. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Dec 26 15:34:08 2013 InstallationDate: Installed on 2013-12-25 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 37613EG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=UUID=c379c17a-9869-47a8-b9b3-83be4e302040 ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H9ET74WW(1.11) dmi.board.asset.tag: Not Available dmi.board.name: 37613EG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH9ET74WW(1.11):bd06/26/2013:svnLENOVO:pn37613EG:pvrLenovoB590:rvnLENOVO:rn37613EG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 37613EG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 1C:3E:84:E8:81:98 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1244 acl:0 sco:0 events:81 errors:0 TX bytes:2820 acl:0 sco:0 commands:77 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264311/+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 1886626] Re: after login to gnome with snd_hda_intel 0000:00:1f.3: No response from codec
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1886626 Title: after login to gnome with snd_hda_intel :00:1f.3: No response from codec Status in alsa-driver package in Ubuntu: New Bug description: After login to gnome, login takes an unsual amount of time. Goes back to login screen. On second login, works normally but audio sliders are not showing correctly. After a while, it operates normally. Logs are showing a lot of snd_hda_intel :00:1f.3: No response from codec, resetting bus:last cmd0x20a70500 +pci::00:1f.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-1063.68-oem-osp1 5.0.21 Uname: Linux 5.0.0-1063-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: killian68 1816 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 08:56:11 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2020-04-02 (96 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1886626/+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 1886626] [NEW] after login to gnome with snd_hda_intel 0000:00:1f.3: No response from codec
You have been subscribed to a public bug: After login to gnome, login takes an unsual amount of time. Goes back to login screen. On second login, works normally but audio sliders are not showing correctly. After a while, it operates normally. Logs are showing a lot of snd_hda_intel :00:1f.3: No response from codec, resetting bus:last cmd0x20a70500 +pci::00:1f.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-1063.68-oem-osp1 5.0.21 Uname: Linux 5.0.0-1063-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: killian68 1816 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 08:56:11 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2020-04-02 (96 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- after login to gnome with snd_hda_intel :00:1f.3: No response from codec https://bugs.launchpad.net/bugs/1886626 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 1873777] Re: Update to 2.64.2
Jul 07 00:08:37 betty io.elementary.a[3348]: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 17 Jul 07 00:08:40 betty io.elementary.a[3348]: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 17 Jul 07 00:08:41 betty gnome-shell[1966]: pop-shell: [INFO] making above Jul 07 00:08:41 betty gnome-shell[1966]: pop-shell: [DEBUG] xprop -id 0x2a07177 _MOTIF_WM_HINTS Jul 07 00:08:41 betty gnome-shell[1966]: pop-shell: [DEBUG] _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x0, 0x0, 0x0, 0x0 Jul 07 00:08:41 betty WebKitWebProces[6490]: Failed to load module "appmenu-gtk-module" Jul 07 00:08:48 betty systemd[1669]: Started VTE child process 6523 launched by gnome-terminal-server process 2448. Jul 07 00:10:38 betty systemd[1669]: Started VTE child process 6538 launched by gnome-terminal-server process 2448. Jul 07 00:10:44 betty gnome-shell[1966]: pop-shell: [INFO] making above Jul 07 00:10:44 betty gnome-shell[1966]: pop-shell: [DEBUG] xprop -id 0x2a07177 _MOTIF_WM_HINTS Jul 07 00:10:44 betty gnome-shell[1966]: pop-shell: [DEBUG] _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x0, 0x0, 0x0, 0x0 Jul 07 00:10:44 betty WebKitWebProces[6547]: Failed to load module "appmenu-gtk-module" Jul 07 00:10:56 betty geoclue[1460]: Failed to query location: TLS/SSL support not available; install glib-networking -- 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/1873777 Title: Update to 2.64.2 Status in glib-networking package in Ubuntu: Fix Released Status in glib-networking source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes https://gitlab.gnome.org/GNOME/glib-networking/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that GNOME web still works correctly * Regression potential The update restore the TLS 1.0/1.1 protocols due to COVID-19, try to browse one of those websites from the GNOME browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777/+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 260918]
Does the bug still occur with wine-5.12? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/260918 Title: needed: libv4l and associated application patches (or "gspca stopped working in 2.6.27") Status in Adobe Flash Plugin Tools: Won't Fix Status in Cheese: Unknown Status in Ekiga: Fix Released Status in Mozilla Firefox: Invalid Status in gst-plugins-good: Fix Released Status in GStreamer: Fix Released Status in Kdenlive: Fix Released Status in Kopete: Fix Released Status in Medibuntu: Fix Released Status in OpenCV: Unknown Status in VLC media player: Fix Released Status in Wine: Confirmed Status in amsn package in Ubuntu: Fix Released Status in came package in Ubuntu: Fix Released Status in camorama package in Ubuntu: Invalid Status in camstream package in Ubuntu: Fix Released Status in cheese package in Ubuntu: Invalid Status in ekiga package in Ubuntu: Invalid Status in gst-plugins-good0.10 package in Ubuntu: Fix Released Status in libv4l package in Ubuntu: Fix Released Status in mplayer package in Ubuntu: Fix Released Status in pwlib package in Ubuntu: Fix Released Status in vlc package in Ubuntu: Fix Released Status in xawtv package in Ubuntu: Fix Released Status in cheese source package in Lucid: Invalid Status in amsn source package in Intrepid: Fix Released Status in came source package in Intrepid: Fix Released Status in camorama source package in Intrepid: Invalid Status in camstream source package in Intrepid: Invalid Status in cheese source package in Intrepid: Invalid Status in ekiga source package in Intrepid: Invalid Status in gst-plugins-good0.10 source package in Intrepid: Fix Released Status in libv4l source package in Intrepid: Fix Released Status in mplayer source package in Intrepid: Won't Fix Status in pwlib source package in Intrepid: Fix Released Status in vlc source package in Intrepid: Won't Fix Status in xawtv source package in Intrepid: Fix Released Status in camorama package in Debian: Fix Released Status in gst-plugins-good0.10 package in Fedora: Fix Released Status in pwlib package in Fedora: Fix Released Status in xawtv package in Fedora: Fix Released Bug description: libv4l is a user-space library used by several applications in order to convert webcam streams in user-space instead of kernel-space. As gspca is included in 2.6.27 this is needed in order to (re)support a multitude of webcams supported with ordinary applications. See http://hansdegoede.livejournal.com/3636.html for a more complete description of the software. The latest version is 0.4.0 and is available from http://people.atrpms.net/~hdegoede/ To manage notifications about this bug go to: https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/260918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home
I redeployed the system where this failures was original observed and recreated the issue. Running 'sudo vgck --updatemetadata s5lp8-vg' did work around this bug, when run after the upgrade but prior to the reboot. Here is the vgdisplay output requested by Steve: ubuntu@s5lp8:~$ sudo vgdisplay --- Volume group --- VG Name s5lp8-vg System ID Formatlvm2 Metadata Areas1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV0 Cur LV3 Open LV 3 Max PV0 Cur PV1 Act PV1 VG Size <64.00 GiB PE Size 4.00 MiB Total PE 16383 Alloc PE / Size 16377 / 63.97 GiB Free PE / Size 6 / 24.00 MiB VG UUID 3B7wkv-AIvn-5A7N-pmWB-7y7h-ylkd-jUIfRd ** Changed in: lvm2 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home Status in Ubuntu on IBM z Systems: Confirmed Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no longer mounted. During boot the console shows Timed out waiting for device /dev/mapper/s5lp8--vg-home Please see the attached dist-upgrade logs and console output for more detail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886618] Re: command-not-found gets stuck on locales with non-English-like collation rules
** Description changed: The bug in question: https://askubuntu.com/q/1142923/162831 - Namely, cnf-update-db takes forever if your locale has different collation rules from English such as different sorting and/or case conversion. + Namely, cnf-update-db takes forever and eats almost all your disk time if your locale has different collation rules from English such as different sorting and/or case conversion. A workaround by supplying a C locale: https://askubuntu.com/a/1147303/162831 -- 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/1886618 Title: command-not-found gets stuck on locales with non-English-like collation rules Status in apt package in Ubuntu: Confirmed Bug description: The bug in question: https://askubuntu.com/q/1142923/162831 Namely, cnf-update-db takes forever and eats almost all your disk time if your locale has different collation rules from English such as different sorting and/or case conversion. A workaround by supplying a C locale: https://askubuntu.com/a/1147303/162831 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886618/+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 1886618] Re: command-not-found gets stuck on locales with non-English-like collation rules
Confirmed by me. ** Description changed: The bug in question: https://askubuntu.com/q/1142923/162831 - Namely, cnf-update-db takes forever if your locale has a different collation rules from English such as different sorting and/or case conversion. + Namely, cnf-update-db takes forever if your locale has different collation rules from English such as different sorting and/or case conversion. A workaround by supplying a C locale: https://askubuntu.com/a/1147303/162831 -- 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/1886618 Title: command-not-found gets stuck on locales with non-English-like collation rules Status in apt package in Ubuntu: Confirmed Bug description: The bug in question: https://askubuntu.com/q/1142923/162831 Namely, cnf-update-db takes forever if your locale has different collation rules from English such as different sorting and/or case conversion. A workaround by supplying a C locale: https://askubuntu.com/a/1147303/162831 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886618/+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 1886618] [NEW] command-not-found gets stuck on locales with non-English-like collation rules
Public bug reported: The bug in question: https://askubuntu.com/q/1142923/162831 Namely, cnf-update-db takes forever if your locale has different collation rules from English such as different sorting and/or case conversion. A workaround by supplying a C locale: https://askubuntu.com/a/1147303/162831 ** Affects: apt (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: apt (Ubuntu) Status: New => Confirmed -- 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/1886618 Title: command-not-found gets stuck on locales with non-English-like collation rules Status in apt package in Ubuntu: Confirmed Bug description: The bug in question: https://askubuntu.com/q/1142923/162831 Namely, cnf-update-db takes forever if your locale has different collation rules from English such as different sorting and/or case conversion. A workaround by supplying a C locale: https://askubuntu.com/a/1147303/162831 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886618/+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
