[Touch-packages] [Bug 1881966] Re: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** No longer affects: snappy-hwe-snaps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1881966 Title: Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 Status in network-manager package in Ubuntu: New Bug description: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1881966/+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 1881966] [NEW] Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04
You have been subscribed to a public bug: Hi, I am getting this highly recurrent problem in which the network inadvertently 'disconnects' for a minute or two and then automatically reconnects. It is so recurrent that it makes browsing and simple tasks almost impossible. My best guess is that this problem is a bug in the new NetworkManager, probably a blocking thread while network-manager performs a routine wifi-scan. I'm using the r88x2bu network driver from the rtl88x2bu-dkms package for WiFi. Here is some information about the network. $ nmcli c NAMEUUID TYPE DEVICE MIT SECURE 8b2ea417-ed65-4e36-a63e-a231344af87a wifi wlx74ee2af4348b virbr0 96dd3046-b80c-4995-8b83-289b0fc363d9 bridgevirbr0 MIT b2c5956d-b071-4d52-98c3-86852563d88e wifi -- Wired connection 1 bfacd008-8aae-3219-b84f-6d5dc9f0d9fa ethernet -- $ nmcli d DEVICE TYPE STATECONNECTION wlx74ee2af4348b wifi connectedMIT SECURE virbr0 bridgeconnectedvirbr0 enp3s0 ethernet unavailable -- lo loopback unmanaged-- virbr0-nic tun unmanaged-- I have attached the system logs, which have the NetworkManager and wpa_supplicant logging level set to DEBUG. I am happy to provide any information necessary to resolve this issue. Thanks ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Sporadic network disconnect and re-connect during wifi-scan after upgrading from Ubuntu 18.04 to 20.04 https://bugs.launchpad.net/bugs/1881966 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager 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 1882636] [NEW] https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777
Public bug reported: 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!## ** Affects: glib-networking (Ubuntu) Importance: Undecided Status: New -- 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: New 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 1882610] Re: Lenovo E590 Graphics problems using standard Ubuntu/Budgie install
It sounds like you experienced bug 1867668. Please explain in more detail what, if any, issue remains. Please also be careful to only discuss one issue per bug report. ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Changed in: xserver-xorg-video-intel (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/1882610 Title: Lenovo E590 Graphics problems using standard Ubuntu/Budgie install Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Ive had major problems (seg errors and various) stopping several apps which were all working a couple of months ago, on my new Lenovo E590 Thinkpad notebook. sudo lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02) What helped me sort it was the following command: sudo lshw -C display which showed the driver was xserver-xorg-video-intel which is not recommended; its older and problematic. Aptitude recommends use system default which is driver=i915). After removing this errant driver, its solved my applications crashing problems and more. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Jun 9 12:42:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:5072] InstallationDate: Installed on 2020-01-23 (137 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) LightdmDisplayLog: (EE) event4 - SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded. See https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html for details (EE) client bug: timer event4 keyboard: scheduled expiry is in the past (-1435ms), your system is too slow (EE) client bug: timer event4 keyboard: scheduled expiry is in the past (-821ms), your system is too slow (EE) client bug: timer event4 keyboard: scheduled expiry is in the past (-204ms), your system is too slow Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:2130 Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 008: ID 14cd:6600 Super Top M110E PATA bridge Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=fab243f0-09ed-4b95-8ed6-995ffdde426c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET42W(1.25):bd01/13/2020:svnLENOVO:pn20NBCTO1WW:pvrThinkPadE590:rvnLENOVO:rn20NBCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E590 dmi.product.name: 20NBCTO1WW dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590 dmi.product.version: ThinkPad E590 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/xserver-xorg-video-intel/+bug/1882610/+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 1882631] 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. ** Tags added: amdgpu ** Summary changed: - Xorg crash + [amdgpu] Xorg crash ** 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/1882631 Title: [amdgpu] Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: many time system hangs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 9 10:50:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF 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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882631/+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 1882607] Re: One of the updates in the last week broke super key on external usb keyboard
Please install 'evtest' and then run: sudo evtest and select the keyboard. Now tap the Super key and tell us what 'evtest' reports for it. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (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/1882607 Title: One of the updates in the last week broke super key on external usb keyboard Status in mutter package in Ubuntu: Incomplete Bug description: Worked fine until recent reboot. Now the super key on the external keyboard connected to a dock via thunderbolt port does not work. It still works on internal laptop keyboard. Tried switching to a few different languages but had no effect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b: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.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 18:41:32 2020 DistUpgraded: 2020-03-26 17:17:00,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-31-generic, x86_64: installed nvidia, 440.64, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39ab] Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39ab] InstallationDate: Installed on 2019-04-08 (427 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 81CU ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=06db1321-d690-4a95-b79d-258351c53f9d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-26 (74 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7KCN31WW(V1.12) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-15IKB dmi.modalias: dmi:bvnLENOVO:bvr7KCN31WW(V1.12):bd11/08/2019:svnLENOVO:pn81CU:pvrLenovoYOGA730-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-15IKB: dmi.product.family: YOGA 730-15IKB dmi.product.name: 81CU dmi.product.sku: LENOVO_MT_81CU_BU_idea_FM_YOGA 730-15IKB dmi.product.version: Lenovo YOGA 730-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882607/+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 1882631] [NEW] Xorg crash
Public bug reported: many time system hangs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 9 10:50:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF 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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic crash ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1882631 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: many time system hangs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 9 10:50:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF 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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-ev
[Touch-packages] [Bug 1882587] Re: Truncated audio frequency response on snd-aloop device
** Tags added: bionic ** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/915 Importance: Unknown Status: Unknown -- 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/1882587 Title: Truncated audio frequency response on snd-aloop device Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: Hi. I've found something strange happening when I record the output of a sound card through loopback device audio monitor. If I load the snd-aloop module, then setup a player to play a chirp sound that spans a sine wave between 10Hz and 22kHz through it, and then record the virtual monitor device through Audacity it drops the frequencies something over 16kHz like it have a low pass filter on it. The sampling rate is 44100 or 48000, it doesn't matters, the result is the same. Also in some cases I found that the signal path between channels doesn't have correct syncing. A chirp sound is ideal for testing, because if there is some delay between channels, it would produce a comb filter like frequency response on the mono mix. It also happens with real sound cards, not virtual ones. The question is about how to narrow down the issue. I think it's not ALSA related, because it happens both on the hardware device and the virtual loop one. Attached I put my chirp test sound. I played it on the command line with: $ ffplay -loop 1000 chirp_test.flac Then I setup the recording path with pavucontrol, to target the Audacity input My versions: pulseaudio 12.2-2 linux kernel 5.6.13 $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installed: 1:12.2-9~bionic1 Candidate: 1:12.2-9~bionic1 Version table: *** 1:12.2-9~bionic1 500 500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.8 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:11.1-1ubuntu7.7 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:11.1-1ubuntu7 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Attached on this there is a .tar.gz containing both .flac files chirp_test.flac is the original file. chirp_loopback_recorded.flac is the recorded file from the loopback device. Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1882587/+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 1882587] Re: Truncated audio frequency response on snd-aloop device
Here it is: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/915 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #915 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/915 -- 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/1882587 Title: Truncated audio frequency response on snd-aloop device Status in pulseaudio package in Ubuntu: New Bug description: Hi. I've found something strange happening when I record the output of a sound card through loopback device audio monitor. If I load the snd-aloop module, then setup a player to play a chirp sound that spans a sine wave between 10Hz and 22kHz through it, and then record the virtual monitor device through Audacity it drops the frequencies something over 16kHz like it have a low pass filter on it. The sampling rate is 44100 or 48000, it doesn't matters, the result is the same. Also in some cases I found that the signal path between channels doesn't have correct syncing. A chirp sound is ideal for testing, because if there is some delay between channels, it would produce a comb filter like frequency response on the mono mix. It also happens with real sound cards, not virtual ones. The question is about how to narrow down the issue. I think it's not ALSA related, because it happens both on the hardware device and the virtual loop one. Attached I put my chirp test sound. I played it on the command line with: $ ffplay -loop 1000 chirp_test.flac Then I setup the recording path with pavucontrol, to target the Audacity input My versions: pulseaudio 12.2-2 linux kernel 5.6.13 $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installed: 1:12.2-9~bionic1 Candidate: 1:12.2-9~bionic1 Version table: *** 1:12.2-9~bionic1 500 500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.8 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:11.1-1ubuntu7.7 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:11.1-1ubuntu7 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Attached on this there is a .tar.gz containing both .flac files chirp_test.flac is the original file. chirp_loopback_recorded.flac is the recorded file from the loopback device. Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882587/+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 1453366] Re: 15.04 (Xubuntu, Lubuntu) cannot recognize some DVDs
[Expired for libdvdread (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libdvdread (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdvdread in Ubuntu. https://bugs.launchpad.net/bugs/1453366 Title: 15.04 (Xubuntu, Lubuntu) cannot recognize some DVDs Status in libdvdread package in Ubuntu: Expired Bug description: I tested this in Xubuntu and Lubuntu 15.04 and then in Xubuntu 14.04. Xubuntu 14.04 recognized ALL the problem DVDs that 15.04 could not recognize. I tried using upstart at boot instead of systemd, the problem still persisted in 15.04. Sometimes, if I reboot using systemd with the DVD already inserted, the DVD is loaded. However, if I eject the DVD and re-insert it, it cannot be recognized again. However, one or two particularly stubborn DVDs still could not be recognized even with a reboot. Again, though, 14.04 had no problem recognizing these "stubborn" DVDs. I have tested, so far, about 30 original DVDs. 4 or 5 showed this problem in 15.04. Xubuntu 14.04 had no problems with these 4 or 5. I first posted this problem in the Ubuntu forums and at least one other user experienced the same problem (including flash drive recognition problems - I did not test this and, for me, no problems to date). http://ubuntuforums.org/showthread.php?t=2276987 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdvdread/+bug/1453366/+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 1873777] Re: Update to 2.64.2
I need help!!! I'm trying to build this repair but having a hard time running the build. I'm not very good at building from the provided fix. Please help. -- 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 1882368] Re: Sound is louder after resume from suspend or logging in Ubuntu 20.04
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New ** Summary changed: - Sound is louder after resume from suspend or logging in Ubuntu 20.04 + [OMEN by HP Obelisk Desktop 875-0xxx] Sound is louder after resume from suspend or logging in Ubuntu 20.04 -- 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/1882368 Title: [OMEN by HP Obelisk Desktop 875-0xxx] Sound is louder after resume from suspend or logging in Ubuntu 20.04 Status in pulseaudio package in Ubuntu: New Bug description: I'm running Ubuntu 20.04 and have noticed that after logging back on to a machine either after its been asleep/suspended or logged out due to inactivity the sound is much louder at the same volume. I haven't enabled amplification or any other sound feature. To duplicate, boot machine with volume at say 50% and listen to some music. Let it either log out or suspend/sleep and then log back in, start music/sound and it will be much louder. In fact this louder sound at the volume sounds correct, because the windows boot sounds the same at that level. When ubuntu boots the volume is much softer. The sound post logging in after a suspend or lock out is what it should be from the get go. Soundcard details 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) DeviceName: Onboard - Sound Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS Flags: bus master, fast devsel, latency 32, IRQ 143 Memory at a351 (64-bit, non-prefetchable) [size=16K] Memory at a310 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kashif 2925 F pulseaudio /dev/snd/controlC0: kashif 2925 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-20 (414 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-08 (30 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/19/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.name: 84FD dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.25:bd11/19/2019:svnHP:pnOMENbyHPObeliskDesktop875-0xxx:pvr:rvnHP:rn84FD:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Omen dmi.product.name: OMEN by HP Obelisk Desktop 875-0xxx dmi.product.sku: 4NM65AA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882368/+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 1882473] Re: test bug
** Changed in: systemd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1882473 Title: test bug Status in systemd: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: test upstream bug To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1882473/+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
** Changed in: pulseaudio (Ubuntu Bionic) Importance: Undecided => High -- 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: New Status in pulseaudio source package in Bionic: New 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. [Regression Risk] Low, these 2 patches are already in the mainline pulseaudio, and already in the eoan, focal and groovy. 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 1882610] [NEW] Lenovo E590 Graphics problems using standard Ubuntu/Budgie install
Public bug reported: Ive had major problems (seg errors and various) stopping several apps which were all working a couple of months ago, on my new Lenovo E590 Thinkpad notebook. sudo lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02) What helped me sort it was the following command: sudo lshw -C display which showed the driver was xserver-xorg-video-intel which is not recommended; its older and problematic. Aptitude recommends use system default which is driver=i915). After removing this errant driver, its solved my applications crashing problems and more. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Jun 9 12:42:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:5072] InstallationDate: Installed on 2020-01-23 (137 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) LightdmDisplayLog: (EE) event4 - SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded. See https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html for details (EE) client bug: timer event4 keyboard: scheduled expiry is in the past (-1435ms), your system is too slow (EE) client bug: timer event4 keyboard: scheduled expiry is in the past (-821ms), your system is too slow (EE) client bug: timer event4 keyboard: scheduled expiry is in the past (-204ms), your system is too slow Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:2130 Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 008: ID 14cd:6600 Super Top M110E PATA bridge Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=fab243f0-09ed-4b95-8ed6-995ffdde426c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET42W(1.25):bd01/13/2020:svnLENOVO:pn20NBCTO1WW:pvrThinkPadE590:rvnLENOVO:rn20NBCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E590 dmi.product.name: 20NBCTO1WW dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590 dmi.product.version: ThinkPad E590 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/1882610 Title: Lenovo E590 Graphics problems using standard Ubuntu/Budgie install Status in xorg package in Ubuntu: New Bug description: Ive had major problems (seg errors and various) stopping several apps which were all working a couple of months ago, on my new Lenovo E590 Thinkpad notebook. sudo lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02) What helped me sort it was the following command: sudo lshw -C display which showed the driver was xserver-xorg-video-intel which is not recommended; its older and problematic. Aptitude recommends use system default which is driver=i915). After removing this errant driver, its solved my applications crashing problems and more. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2
[Touch-packages] [Bug 1882607] [NEW] One of the updates in the last week broke super key on external usb keyboard
Public bug reported: Worked fine until recent reboot. Now the super key on the external keyboard connected to a dock via thunderbolt port does not work. It still works on internal laptop keyboard. Tried switching to a few different languages but had no effect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b: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.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 18:41:32 2020 DistUpgraded: 2020-03-26 17:17:00,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-31-generic, x86_64: installed nvidia, 440.64, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39ab] Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39ab] InstallationDate: Installed on 2019-04-08 (427 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 81CU ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=06db1321-d690-4a95-b79d-258351c53f9d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-26 (74 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7KCN31WW(V1.12) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-15IKB dmi.modalias: dmi:bvnLENOVO:bvr7KCN31WW(V1.12):bd11/08/2019:svnLENOVO:pn81CU:pvrLenovoYOGA730-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-15IKB: dmi.product.family: YOGA 730-15IKB dmi.product.name: 81CU dmi.product.sku: LENOVO_MT_81CU_BU_idea_FM_YOGA 730-15IKB dmi.product.version: Lenovo YOGA 730-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.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 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/1882607 Title: One of the updates in the last week broke super key on external usb keyboard Status in xorg package in Ubuntu: New Bug description: Worked fine until recent reboot. Now the super key on the external keyboard connected to a dock via thunderbolt port does not work. It still works on internal laptop keyboard. Tried switching to a few different languages but had no effect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b: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.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permissio
Re: [Touch-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
Thanks Sebastien. I'm beginning to suspect a faulty WiFi card. Wish there was some way to determine if that is the culprit. On Mon, Jun 8, 2020 at 4:30 PM Sebastien Bacher <1882...@bugs.launchpad.net> wrote: > The update mentioned fixes the iptables path on systemd not having > usrmerged, it's probably not the issue there > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1882242 > > Title: > June 4th network-manager update kills wireless networking > > Status in network-manager package in Ubuntu: > Incomplete > > Bug description: > network-manager problems > > June 4, 2020 apt update installed two networking packages: > network-manager_1.14.6-2+deb10u1_amd64.deb > libnm0_1.14.6-2+deb10u1_amd64.deb > > System: > Kernel: 5.4.0-33-generic x86_64 > Desktop: MATE 1.24.0 > Distro: Ubuntu 20.04 LTS (Focal Fossa) > Machine: > Type: Laptop System: Dell product: Latitude E6530 v: 01 > > After rebooting the laptop, the wireless access point(s) are no longer > available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- > Fi Networks" is grayed out. > > Network: > Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl > IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b > > $ sudo ip addr > > wlp2s0: mtu 1500 qdisc > fq_codel state DORMANT group default qlen 1000 > link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff > > $ sudo nmcli > wlp2s0: disconnected > "Broadcom and subsidiaries BCM43228" > wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 > > $ sudo nmcli device show > GENERAL.DEVICE: wlp2s0 > GENERAL.TYPE: wifi > GENERAL.HWADDR: 3C:77:E6:7C:5D:7B > GENERAL.MTU:1500 > GENERAL.STATE: 30 (disconnected) > GENERAL.CONNECTION: -- > GENERAL.CON-PATH: -- > > $ sudo nmcli radio wifi > enabled > > $ sudo iwlist wlp2s0 scanning > wlp2s0No scan results > > $ sudo iwlist wlp2s0 accesspoints > wlp2s0Interface doesn't have a list of Peers/Access-Points > > $ sudo iwlist wlp2s0 ap > wlp2s0Interface doesn't have a list of Peers/Access-Points > > $ sudo iwlist wlp2s0 wpakeys > wlp2s02 key sizes : 40, 104bits > 4 keys available : > Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported > > $ sudo iwconfig wlp2s0 > wlp2s0IEEE 802.11 ESSID:off/any > Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm > > Retry short limit:7 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:on > > $ sudo rfkill list > 1: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > 2: brcmwl-0: Wireless LAN > Soft blocked: no > Hard blocked: no > 3: dell-wifi: Wireless LAN > Soft blocked: no > Hard blocked: no > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1882242/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results
[Touch-packages] [Bug 1882242] IfupdownConfig.txt
apport information ** Attachment added: "IfupdownConfig.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381759/+files/IfupdownConfig.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net
[Touch-packages] [Bug 1882242] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381768/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug
[Touch-packages] [Bug 1882242] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381767/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+so
[Touch-packages] [Bug 1882242] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381766/+files/PciNetwork.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-man
[Touch-packages] [Bug 1882242] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381770/+files/nmcli-con.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manag
[Touch-packages] [Bug 1882242] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381769/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-man
[Touch-packages] [Bug 1882242] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381763/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network
[Touch-packages] [Bug 1882242] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381760/+files/IpAddr.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug
[Touch-packages] [Bug 1882242] NetDevice.eno1.txt
apport information ** Attachment added: "NetDevice.eno1.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381762/+files/NetDevice.eno1.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net
[Touch-packages] [Bug 1882242] NetDevice.wlp2s0.txt
apport information ** Attachment added: "NetDevice.wlp2s0.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381764/+files/NetDevice.wlp2s0.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source
[Touch-packages] [Bug 1882242] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381765/+files/NetworkManager.conf.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+
[Touch-packages] [Bug 1882242] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381761/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager
[Touch-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
apport information ** Tags added: apport-collected focal ** Description changed: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi-Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-06-04 (4 days ago) + InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IpRoute: + default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp2s0 scope link metric 1000 + 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 + NetworkManager.state: + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + NonfreeKernelModules: wl + Package: network-manager 1.22.10-1ubuntu2.1 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_US + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 + Tags: focal + Uname: Linux 5.4.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + nmcli-dev: + DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH + wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 + eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- + lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381757/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager p
[Touch-packages] [Bug 1882242] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381758/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network
[Touch-packages] [Bug 1882367] Re: fail to add printer
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Changed in: cups (Ubuntu) Status: New => Incomplete -- 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/1882367 Title: fail to add printer Status in cups package in Ubuntu: Incomplete Bug description: lsusb Bus 002 Device 005: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader) Bus 002 Device 004: ID 147a:e018 Formosa Industrial Computing, Inc. eHome Infrared Receiver Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 002: ID 03f0:0f0c HP, Inc Wireless Keyboard and Optical Mouse receiver Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 04b8:0812 Seiko Epson Corp. MFP Composite Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ls -l /dev/usb/lp* /dev/bus/usb/*/* crw-rw-r-- 1 root root 189, 0 Jun 6 13:43 /dev/bus/usb/001/001 crw-rw-r-- 1 root lp 189, 2 Jun 6 15:40 /dev/bus/usb/001/003 crw-rw-r-- 1 root root 189, 128 Jun 6 13:43 /dev/bus/usb/002/001 crw-rw-r-- 1 root root 189, 129 Jun 6 13:43 /dev/bus/usb/002/002 crw-rw-r-- 1 root root 189, 131 Jun 6 13:43 /dev/bus/usb/002/004 crw-rw-r-- 1 root root 189, 132 Jun 6 13:43 /dev/bus/usb/002/005 crw-rw-r-- 1 root root 189, 256 Jun 6 13:43 /dev/bus/usb/003/001 crw-rw-r-- 1 root root 189, 384 Jun 6 13:43 /dev/bus/usb/004/001 crw-rw-r-- 1 root root 189, 512 Jun 6 13:43 /dev/bus/usb/005/001 crw-rw-r-- 1 root root 189, 640 Jun 6 13:43 /dev/bus/usb/006/001 crw-rw-r-- 1 root root 189, 768 Jun 6 13:43 /dev/bus/usb/007/001 crw-rw-r-- 1 root root 189, 896 Jun 6 13:43 /dev/bus/usb/008/001 crw-rw-r-- 1 root root 189, 897 Jun 6 13:43 /dev/bus/usb/008/002 crw-rw 1 root lp 180, 2 Jun 6 15:40 /dev/usb/lp2 sudo usb_printerid /dev/usb/lp2 GET_DEVICE_ID string: MFG:EPSON;CMD:ESCPL2,BDC,D4;MDL:Stylus Photo R320;CLS:PRINTER;DES:EPSON Stylus Photo R320; sudo lpinfo -v file cups-brf:/ direct canon:/dev/usb/lp2 network http direct epson:/dev/usb/lp2 direct hp network https network ipp network ipps direct usb://EPSON/Stylus%20Photo%20R320?serial=L17P20504140921110&interface=1 network beh network socket network lpd direct hpfax ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 15:48:44 2020 InstallationDate: Installed on 2020-03-31 (66 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lpstat: device for EpsonR320: usb://EPSON/Stylus%20Photo%20R320?serial=L17P20504140921110 device for Stylus-Photo-R320: usb://EPSON/Stylus%20Photo%20R320?serial=L17P20504140921110&interface=1 MachineType: HP-Pavilion NF398AA-ABU m9565uk Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Stylus-Photo-R320.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Stylus-Photo-R320.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6516a65a-169c-45a6-831e-5f71f0bdbcfa ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-05-12 (25 days ago) dmi.bios.date: 12/16/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.35 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.ve
[Touch-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority
It would be best to work with upstream to get it merged, what is blocking? Is upstream not responding? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882161 Title: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority Status in HWE Next: New Status in pulseaudio package in Ubuntu: Incomplete Status in pulseaudio source package in Focal: Incomplete Status in pulseaudio source package in Groovy: Incomplete Bug description: This bug originates from an OEM private bug #1875597, then ubuntu users reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 and the 1st issue of #1881659 have the same root cause as #1875597 [Impact] On the Dell machines with multi function audio jack, after installing the ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the headphone/headset can't output sound automatically after users plug in a headphone/headset. This is different from ubuntu 18.04, on the 18.04, the headphone/headset could output sound automatically after plugging in the audio jack. [Fix] The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, finally the audio jack is set to Mic2 mode, this make the audio jack can't output sound anymore. To fix it, let the audio jack set to Headset MIC mode by default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the device event to module-switch-on-port-available by the order of priority in the umc2. [Test Case] applying the fix patch to pulseaudio, plug a headset/headphone to the multi function audio jack, play sound from headset/headphone, the sound could be heard from headset/headphone. [Regression Risk] Low, just do a small change to store the ucm devices by their priority. This fix is not accepted by upstream yet. Maybe we could apply this fix to ubuntu specific part, if the upstream has a solution for this issue in the future, we could revert this fix and merge the uptream's solution then. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
The update mentioned fixes the iptables path on systemd not having usrmerged, it's probably not the issue there -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1882242/+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 1882242] Re: June 4th network-manager update kills wireless networking
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1882242 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1882242/+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 1882340] Re: Alert sounds are captured by the microphone
Thank you for your bug report, what would you expect exactly? A video call to automatically mute sound effects on your computer? What software do you use for the video call? It should probably be the one handling such changes Also would you expect only effects to be muted or any sound? ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1882340 Title: Alert sounds are captured by the microphone Status in alsa-driver package in Ubuntu: Incomplete Bug description: On my Fossa the system sounds (e.g., the alert sound) are also captured by my microphone. Thus, if I press backspace in an empty terminal, my contacts in a video-call can hear the default bell sound making *pling*. When opening the System > Audio on Gnome I can see a rise on the volume bar as well. A workaround exists by disabling the alert sounds as described in the docs: https://help.ubuntu.com/stable/ubuntu-help/sound-alert.html.en This has been the default since installation for me and drives my contacts crazy. :-) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jl 3027 F pulseaudio /dev/snd/controlC0: jl 3027 F pulseaudio /dev/snd/pcmC0D0p: jl 3027 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 10:53:55 2020 InstallationDate: Installed on 2020-04-24 (42 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: ThinkPad Thunderbolt 3 Dock USB Audio - ThinkPad Thunderbolt 3 Dock USB Symptom_PulseAudioLog: Jun 05 20:03:08 x1c dbus-daemon[1617]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=125 pid=2067 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Jun 05 20:03:24 x1c systemd[2021]: pulseaudio.service: Succeeded. Jun 05 20:03:34 x1c systemd[2021]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [sof-hda-dsp - sof-hda-dsp, recording] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET47W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QES01L00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QES01L00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QES01L00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QES01L00 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1882340/+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 1882136] Re: I can't connect to 5GHz wifi
The log suggests it's a kernel issue kernel: Call Trace: kernel: dump_stack+0x6d/0x9a kernel: iwl_pcie_send_hcmd_sync+0x382/0x390 [iwlwifi] kernel: ? wait_woken+0x80/0x80 kernel: iwl_trans_pcie_send_hcmd+0x34/0xf0 [iwlwifi] kernel: iwl_trans_send_cmd+0x55/0xc0 [iwlwifi] kernel: iwl_mvm_send_cmd+0x1f/0x40 [iwlmvm] kernel: iwl_mvm_send_cmd_pdu+0x51/0x70 [iwlmvm] ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882136 Title: I can't connect to 5GHz wifi Status in linux package in Ubuntu: New Bug description: After updating the NetworkManager I can't connect to 5GHz wifi. The router is a mikrotik hap ac2.The notebook is a Dell Latitude 5580. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 22:20:15 2020 InstallationDate: Installed on 2020-05-15 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882136/+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 1882587] Re: Truncated audio frequency response on snd-aloop device
Thank you for your bug report, could you sent it also upstream on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues ? ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- 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/1882587 Title: Truncated audio frequency response on snd-aloop device Status in pulseaudio package in Ubuntu: New Bug description: Hi. I've found something strange happening when I record the output of a sound card through loopback device audio monitor. If I load the snd-aloop module, then setup a player to play a chirp sound that spans a sine wave between 10Hz and 22kHz through it, and then record the virtual monitor device through Audacity it drops the frequencies something over 16kHz like it have a low pass filter on it. The sampling rate is 44100 or 48000, it doesn't matters, the result is the same. Also in some cases I found that the signal path between channels doesn't have correct syncing. A chirp sound is ideal for testing, because if there is some delay between channels, it would produce a comb filter like frequency response on the mono mix. It also happens with real sound cards, not virtual ones. The question is about how to narrow down the issue. I think it's not ALSA related, because it happens both on the hardware device and the virtual loop one. Attached I put my chirp test sound. I played it on the command line with: $ ffplay -loop 1000 chirp_test.flac Then I setup the recording path with pavucontrol, to target the Audacity input My versions: pulseaudio 12.2-2 linux kernel 5.6.13 $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installed: 1:12.2-9~bionic1 Candidate: 1:12.2-9~bionic1 Version table: *** 1:12.2-9~bionic1 500 500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.8 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:11.1-1ubuntu7.7 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:11.1-1ubuntu7 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Attached on this there is a .tar.gz containing both .flac files chirp_test.flac is the original file. chirp_loopback_recorded.flac is the recorded file from the loopback device. Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882587/+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 1882587] Re: Truncated audio frequency response on snd-aloop device
** Summary changed: - Truncated audio frequency response on monitor device + Truncated audio frequency response on snd-aloop device -- 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/1882587 Title: Truncated audio frequency response on snd-aloop device Status in pulseaudio package in Ubuntu: New Bug description: Hi. I've found something strange happening when I record the output of a sound card through loopback device audio monitor. If I load the snd-aloop module, then setup a player to play a chirp sound that spans a sine wave between 10Hz and 22kHz through it, and then record the virtual monitor device through Audacity it drops the frequencies something over 16kHz like it have a low pass filter on it. The sampling rate is 44100 or 48000, it doesn't matters, the result is the same. Also in some cases I found that the signal path between channels doesn't have correct syncing. A chirp sound is ideal for testing, because if there is some delay between channels, it would produce a comb filter like frequency response on the mono mix. It also happens with real sound cards, not virtual ones. The question is about how to narrow down the issue. I think it's not ALSA related, because it happens both on the hardware device and the virtual loop one. Attached I put my chirp test sound. I played it on the command line with: $ ffplay -loop 1000 chirp_test.flac Then I setup the recording path with pavucontrol, to target the Audacity input My versions: pulseaudio 12.2-2 linux kernel 5.6.13 $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installed: 1:12.2-9~bionic1 Candidate: 1:12.2-9~bionic1 Version table: *** 1:12.2-9~bionic1 500 500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.8 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:11.1-1ubuntu7.7 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:11.1-1ubuntu7 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Attached on this there is a .tar.gz containing both .flac files chirp_test.flac is the original file. chirp_loopback_recorded.flac is the recorded file from the loopback device. Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882587/+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 1882596] [NEW] systemd.unit(5) incorrectly refers to systemd.syntax(5)
Public bug reported: In Ubuntu 20.04 LTS there is no systemd.syntax(5) it is actually systemd.syntax(7). "See systemd.syntax(5) for a general description of the syntax." ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Description changed: In Ubuntu 20.04 LTS there is no systemd.syntax(5) it is actually systemd.syntax(7). + + "See systemd.syntax(5) for a general description of the syntax." ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1882596 Title: systemd.unit(5) incorrectly refers to systemd.syntax(5) Status in systemd package in Ubuntu: New Bug description: In Ubuntu 20.04 LTS there is no systemd.syntax(5) it is actually systemd.syntax(7). "See systemd.syntax(5) for a general description of the syntax." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882596/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
The patch doesn't sound like something we would like to carry as a distro patch, also the depends of ofono mentioned sounds suboptimal -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1864558] Re: Printer adds automatically at boot with notification or if printer deleted
the midnight notification issue is reported as bug #1869981 -- 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/1864558 Title: Printer adds automatically at boot with notification or if printer deleted Status in cups package in Ubuntu: Confirmed Bug description: When booting 20.04 I get a notification on the logon screen each time advising that my wireless printer has been setup. If I remove the printer via settings, then as soon as it's removed, it gets re-added and I see the same notification as I do on the logon screen about the printer having been setup. I've attached a screenshot of this notification. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 21:49:43 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1864558/+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 1882587] [NEW] Truncated audio frequency response on monitor device
Public bug reported: Hi. I've found something strange happening when I record the output of a sound card through loopback device audio monitor. If I load the snd-aloop module, then setup a player to play a chirp sound that spans a sine wave between 10Hz and 22kHz through it, and then record the virtual monitor device through Audacity it drops the frequencies something over 16kHz like it have a low pass filter on it. The sampling rate is 44100 or 48000, it doesn't matters, the result is the same. Also in some cases I found that the signal path between channels doesn't have correct syncing. A chirp sound is ideal for testing, because if there is some delay between channels, it would produce a comb filter like frequency response on the mono mix. It also happens with real sound cards, not virtual ones. The question is about how to narrow down the issue. I think it's not ALSA related, because it happens both on the hardware device and the virtual loop one. Attached I put my chirp test sound. I played it on the command line with: $ ffplay -loop 1000 chirp_test.flac Then I setup the recording path with pavucontrol, to target the Audacity input My versions: pulseaudio 12.2-2 linux kernel 5.6.13 $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 pulseaudio: Installed: 1:12.2-9~bionic1 Candidate: 1:12.2-9~bionic1 Version table: *** 1:12.2-9~bionic1 500 500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.8 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:11.1-1ubuntu7.7 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:11.1-1ubuntu7 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Attached on this there is a .tar.gz containing both .flac files chirp_test.flac is the original file. chirp_loopback_recorded.flac is the recorded file from the loopback device. Thank You. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: chirp testcase ** Attachment added: "The files used for testing" https://bugs.launchpad.net/bugs/1882587/+attachment/5381754/+files/sound_files.tar.gz -- 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/1882587 Title: Truncated audio frequency response on monitor device Status in pulseaudio package in Ubuntu: New Bug description: Hi. I've found something strange happening when I record the output of a sound card through loopback device audio monitor. If I load the snd-aloop module, then setup a player to play a chirp sound that spans a sine wave between 10Hz and 22kHz through it, and then record the virtual monitor device through Audacity it drops the frequencies something over 16kHz like it have a low pass filter on it. The sampling rate is 44100 or 48000, it doesn't matters, the result is the same. Also in some cases I found that the signal path between channels doesn't have correct syncing. A chirp sound is ideal for testing, because if there is some delay between channels, it would produce a comb filter like frequency response on the mono mix. It also happens with real sound cards, not virtual ones. The question is about how to narrow down the issue. I think it's not ALSA related, because it happens both on the hardware device and the virtual loop one. Attached I put my chirp test sound. I played it on the command line with: $ ffplay -loop 1000 chirp_test.flac Then I setup the recording path with pavucontrol, to target the Audacity input My versions: pulseaudio 12.2-2 linux kernel 5.6.13 $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installed: 1:12.2-9~bionic1 Candidate: 1:12.2-9~bionic1 Version table: *** 1:12.2-9~bionic1 500 500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.8 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:11.1-1ubuntu7.7 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:11.1-1ubuntu7 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Attached on this there is a .tar.gz containing both .flac files chirp_test.flac is the original file. chirp_loopback_recorded.flac is the recorded file from the loopback device. Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~t
[Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
We have an automated solution that unpacks the crash report and sends along the relevant information about the crash+stacktrace. Had to initially deal with the fact that apport-unpack was crashing (returning non-zero exit code). Just manually entering in UserGroups info to every crash report prior to processing it now. I was mostly thinking of the other users which will likely continue to be using the 18.04 LTS for some time before they migrate to 20.04. This has been such a long standing bug and it only takes a few lines of code to fix it. I understand if it won't be backported, as it is very minor and people have been ok with it for the last 5 years almost. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Triaged Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: [Impact] apport-unpack crashes when trying to unpack a crash [Test Case] On a system running 20.04 LTS: 1) create an additional user who is only a member of their own group e.g. bdmurray@clean-focal-amd64:~$ id crashy uid=1001(crashy) gid=1001(crashy) groups=1001(crashy) 2) Launch a process as that user 3) kill -11 that process 4) Confirm there is a crash file in /var/crash for that process 5) Run apport-unpack on that .crash file With the version of apport from -proposed you will not get another crash file when unpacking the crash file. [Regression Potential] We are just setting UserGroups to 'N/A' as opposed to having it be completely empty so there isn't any chance for regression. When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: BugDistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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] [NEW] [SRU] Enable support for Victoria Cloud Archive
Public bug reported: 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 ** Affects: software-properties (Ubuntu) Importance: High Status: Triaged ** Affects: software-properties (Ubuntu Focal) Importance: High Status: Triaged ** Affects: software-properties (Ubuntu Groovy) Importance: High Status: Triaged ** Also affects: software-properties (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Focal) Status: New => Triaged ** Changed in: software-properties (Ubuntu Groovy) Status: New => Triaged ** Changed in: software-properties (Ubuntu Focal) Importance: Undecided => High ** Changed in: software-properties (Ubuntu Groovy) Importance: Undecided => High -- 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: Triaged Status in software-properties source package in Focal: Triaged Status in software-properties source package in Groovy: Triaged 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
Re: [Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
On Sun, Jun 07, 2020 at 06:03:38AM -, Nicholas Schell wrote: > Latest fix filling in 'N/A' for absent groups is working, apport-unpack > is no longer throwing stacktrace when prcoessing the report. I still > don't understand why primary groups are ignored, but the important thing > is the reports are processable without errors now. The reason primary groups are not included is because apport tries to exclude some information for privacy reasons and that includes user and group names. > This might be a totally separate issue, but will it be possible to > backport the 'N/A' fix to bionic? Its possible but not very likely. Could you explain your use case for using apport-unpack? -- Brian Murray -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Triaged Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: [Impact] apport-unpack crashes when trying to unpack a crash [Test Case] On a system running 20.04 LTS: 1) create an additional user who is only a member of their own group e.g. bdmurray@clean-focal-amd64:~$ id crashy uid=1001(crashy) gid=1001(crashy) groups=1001(crashy) 2) Launch a process as that user 3) kill -11 that process 4) Confirm there is a crash file in /var/crash for that process 5) Run apport-unpack on that .crash file With the version of apport from -proposed you will not get another crash file when unpacking the crash file. [Regression Potential] We are just setting UserGroups to 'N/A' as opposed to having it be completely empty so there isn't any chance for regression. When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: BugDistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
I've verified the fix on Ubuntu 20.04 LTS. bdmurray@clean-focal-amd64:~$ apt-cache policy apport apport: Installed: 2.20.11-0ubuntu27.3 Candidate: 2.20.11-0ubuntu27.3 Version table: *** 2.20.11-0ubuntu27.3 500 500 http://192.168.10.7/ubuntu focal-proposed/main amd64 Packages 500 http://192.168.10.7/ubuntu focal-proposed/main i386 Packages bdmurray@clean-focal-amd64:~$ sudo apport-unpack /var/crash/_usr_bin_vim.basic.1001.crash /tmp/junk2 No Traceback bdmurray@clean-focal-amd64:~$ cat /tmp/junk2/UserGroups N/A ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Triaged Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: [Impact] apport-unpack crashes when trying to unpack a crash [Test Case] On a system running 20.04 LTS: 1) create an additional user who is only a member of their own group e.g. bdmurray@clean-focal-amd64:~$ id crashy uid=1001(crashy) gid=1001(crashy) groups=1001(crashy) 2) Launch a process as that user 3) kill -11 that process 4) Confirm there is a crash file in /var/crash for that process 5) Run apport-unpack on that .crash file With the version of apport from -proposed you will not get another crash file when unpacking the crash file. [Regression Potential] We are just setting UserGroups to 'N/A' as opposed to having it be completely empty so there isn't any chance for regression. When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: BugDistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
** Description changed: [Impact] apport-unpack crashes when trying to unpack a crash [Test Case] On a system running 20.04 LTS: 1) create an additional user who is only a member of their own group e.g. bdmurray@clean-focal-amd64:~$ id crashy uid=1001(crashy) gid=1001(crashy) groups=1001(crashy) 2) Launch a process as that user 3) kill -11 that process 4) Confirm there is a crash file in /var/crash for that process 5) Run apport-unpack on that .crash file With the version of apport from -proposed you will not get another crash file when unpacking the crash file. [Regression Potential] - We are just setting UserGroups to ' ' as opposed to having it be completely empty so there isn't any chance for regression. + We are just setting UserGroups to 'N/A' as opposed to having it be completely empty so there isn't any chance for regression. When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: BugDistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Triaged Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: [Impact] apport-unpack crashes when trying to unpack a crash [Test Case] On a system running 20.04 LTS: 1) create an additional user who is only a member of their own group e.g. bdmurray@clean-focal-amd64:~$ id crashy uid=1001(crashy) gid=1001(crashy) groups=1001(crashy) 2) Launch a process as that user 3) kill -11 that process 4) Confirm there is a crash file in /var/crash for that process 5) Run apport-unpack on that .crash file With the version of apport from -proposed you will not get another crash file when unpacking the crash file. [Regression Potential] We are just setting UserGroups to 'N/A' as opposed to having it be completely empty so there isn't any chance for regression. When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: BugDistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1774843] Re: apport python exception for python versions which python-apt is not built on
I successfully performed the verification on Ubuntu 20.04 LTS. Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 python3-apport all 2.20.11-0ubuntu27.3 [83.8 kB] Fetched 83.8 kB in 1s (117 kB/s) (Reading database ... 307919 files and directories currently installed.) Preparing to unpack .../python3-apport_2.20.11-0ubuntu27.3_all.deb ... Unpacking python3-apport (2.20.11-0ubuntu27.3) over (2.20.11-0ubuntu27.2) ... Setting up python3-apport (2.20.11-0ubuntu27.3) ... bdmurray@clean-bionic-amd64:~$ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1774843 Title: apport python exception for python versions which python-apt is not built on Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Invalid Status in python3.8 package in Ubuntu: Invalid Status in apport source package in Bionic: Fix Released Status in python3.7 source package in Bionic: Won't Fix Status in python3.8 source package in Bionic: Won't Fix Status in apport source package in Eoan: Fix Released Status in python3.7 source package in Eoan: Won't Fix Status in python3.8 source package in Eoan: Won't Fix Status in apport source package in Focal: Fix Committed Status in python3.7 source package in Focal: Invalid Status in python3.8 source package in Focal: Invalid Bug description: [Impact] apport's python crash handler runs for every installed version of python e.g. on Ubuntu 18.04 LTS it will run for crashes with python3.6 or python3.7 as an interpreter. However, python apt modules are only available for the the supported version of python so the crash handler generates an exception which is annoying. [Test Case for 18.04] 1) Install the non-default version of python3 e.g. python3.7 on Ubuntu 18.04 LTS. 2) Run 'python3.7 -c 'print hello' and observe a Traceback re apt_pkg not being found. With the version of python3-apport from -proposed you'll not receive the Traceback from step # 2. [Test Case for 20.04] 1) Install python3.7 and python3.8 on an Ubuntu 19.10 system 2) Upgrade from 19.10 to 20.04 LTS and keep python3.7 installed 3) Run 'python3.7 -c 'print hello' and observe a Traceback re apt_pkg not being found. With the version of python3-apport from -proposed you'll not receive the Traceback from step # 2 [Regression Potential] Its possible the crash handler change is incorrect so it should be confirmed that we still get python crashes about the system version of python. One way to do this is to run 'apport-cli coreutils < /dev/null'. [Original Description] it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exceptio
[Touch-packages] [Bug 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
systemd-timesyncd package is the default... Please provide a tarball of /var/log such that we could trace if / when / why ntp got installed. Or please try to grep for ntp recursively in /var/log as root to see if you can see if something is manually installing ntp (and/or if install or upgrade process was broken). -- 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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: Incomplete Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+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 1882547] Re: systemd-resolved dumps core all the time
(gdb) frame 0
#0 0x7f62ef3321fa in hashmap_iterate_entry (h=h@entry=0x706f746b73656465,
i=i@entry=0x7fffd2814cc0) at ../src/basic/hashmap.c:706
706 in ../src/basic/hashmap.c
(gdb) p *i
$7 = {idx = 4294967295, next_key = 0x0}
(gdb) p/x *i
$8 = {idx = 0x, next_key = 0x0}
(gdb) p/x *h
Cannot access memory at address 0x706f746b73656465
(gdb) p $_siginfo._sifields._sigfault.si_addr
$9 = (void *) 0x0
--
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/1882547
Title:
systemd-resolved dumps core all the time
Status in systemd package in Ubuntu:
New
Bug description:
It dumps core all the time.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Jun 8 16:51:11 2020
ExecutablePath: /usr/lib/systemd/systemd-resolved
InstallationDate: Installed on 2019-09-30 (252 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Dell Inc. Precision 5530
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /usr/lib/systemd/system/rc-local.service →
/usr/lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /usr/lib/systemd/system/user@.service →
/usr/lib/systemd/system/user@.service.d/timeout.conf
2 overridden configuration files found.
UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago)
dmi.bios.date: 08/22/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.13.0
dmi.board.name: 0FP2W2
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5530
dmi.product.sku: 087D
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999
mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+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 1882547] Re: systemd-resolved dumps core all the time
Here is a call stack that I get from gdb: Reading symbols from /usr/lib/systemd/systemd-resolved... Reading symbols from /usr/lib/debug/.build-id/bb/f07ab7990febf6bbea9cd22392b488187515fb.debug... [New LWP 1752251] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/lib/systemd/systemd-resolved'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f62ef3321fa in hashmap_iterate_entry (h=h@entry=0x706f746b73656465, i=i@entry=0x7fffd2814cc0) at ../src/basic/hashmap.c:706 706 ../src/basic/hashmap.c: No such file or directory. (gdb) bt #0 0x7f62ef3321fa in hashmap_iterate_entry (h=h@entry=0x706f746b73656465, i=i@entry=0x7fffd2814cc0) at ../src/basic/hashmap.c:706 #1 0x7f62ef334122 in internal_hashmap_iterate (h=0x706f746b73656465, i=i@entry=0x7fffd2814cc0, value=value@entry=0x7fffd2814cb8, key=key@entry=0x0) at ../src/basic/hashmap.c:715 #2 0x7f62ef3341d7 in set_iterate (s=, i=i@entry=0x7fffd2814cc0, value=value@entry=0x7fffd2814cb8) at ../src/basic/hashmap.c:736 #3 0x55b8fbc76c67 in dns_query_candidate_go (c=c@entry=0x55b8fd390bb0) at ../src/resolve/resolved-dns-query.c:152 #4 0x55b8fbc75dfc in dns_query_candidate_notify (c=c@entry=0x55b8fd390bb0) at ../src/resolve/resolved-dns-query.c:312 #5 0x55b8fbc76058 in dns_transaction_complete (t=t@entry=0x55b8fd394ec0, state=state@entry=DNS_TRANSACTION_RCODE_FAILURE) at ../src/resolve/resolved-dns-transaction.c:350 #6 0x55b8fbc76a1d in dns_transaction_process_dnssec (t=0x55b8fd394ec0) at ../src/resolve/resolved-dns-transaction.c:832 #7 0x55b8fbc6f9b6 in dns_transaction_process_reply (t=t@entry=0x55b8fd394ec0, p=p@entry=0x55b8fd39e210) at ../src/resolve/resolved-dns-transaction.c:1194 #8 0x55b8fbc703ab in on_dns_packet (s=, fd=, revents=, userdata=0x55b8fd394ec0) at ../src/resolve/resolved-dns-transaction.c:1248 #9 0x7f62ef2a4507 in source_dispatch (s=s@entry=0x55b8fd392260) at ../src/libsystemd/sd-event/sd-event.c:3193 #10 0x7f62ef2a47a1 in sd_event_dispatch (e=e@entry=0x55b8fd37bf30) at ../src/libsystemd/sd-event/sd-event.c:3634 #11 0x7f62ef2a61d8 in sd_event_run (e=e@entry=0x55b8fd37bf30, timeout=timeout@entry=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:3692 #12 0x7f62ef2a63f7 in sd_event_loop (e=0x55b8fd37bf30) at ../src/libsystemd/sd-event/sd-event.c:3714 #13 0x55b8fbc4fb8a in run (argv=, argc=) at ../src/resolve/resolved.c:84 #14 main (argc=, argv=) at ../src/resolve/resolved.c:91 -- 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/1882547 Title: systemd-resolved dumps core all the time Status in systemd package in Ubuntu: New Bug description: It dumps core all the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 8 16:51:11 2020 ExecutablePath: /usr/lib/systemd/systemd-resolved InstallationDate: Installed on 2019-09-30 (252 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999 mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+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 1664844] Re: No distinction between link-up and link-down interfaces
We are actively working on it for the current 20.10 cycle. But it needs some changes in systemd-networkd, which are currently blocked due to a discussion upstream: https://github.com/systemd/systemd/pull/15060 -- 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/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Bug description: [Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything "nice" for the interface, such as rename it to what the user specified in MAAS. If I include the interface but don't specify any addresses or DHCP, it isn't clear if it will be link up (my current assumption) or link down. There should be a way to allow an interface to be recognized by netplan (and even partially configured, waiting for the user to run something like 'ifup ' on a manual but not auto-started interface in ifupdown), but marked administratively disabled. (adminStatus down) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664844/+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 1882547] Re: systemd-resolved dumps core all the time
** Attachment added: "core.systemd-resolve.102.18dc6cf436c2413aba82163837798590.1752251.1591627605" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+attachment/5381696/+files/core.systemd-resolve.102.18dc6cf436c2413aba82163837798590.1752251.1591627605 -- 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/1882547 Title: systemd-resolved dumps core all the time Status in systemd package in Ubuntu: New Bug description: It dumps core all the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 8 16:51:11 2020 ExecutablePath: /usr/lib/systemd/systemd-resolved InstallationDate: Installed on 2019-09-30 (252 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999 mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+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 1882522] Re: [Feature Request] Add Bedtime Mode on Ubuntu Desktop
Added package ** Package changed: ubuntu => ubuntu-settings (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1882522 Title: [Feature Request] Add Bedtime Mode on Ubuntu Desktop Status in ubuntu-settings package in Ubuntu: New Bug description: [Feature Request] Android OS has Bedtime Mode features. Same Bedtime features can be useful for Ubuntu Desktop. Feature of Bedtime can be: 1. Turn on Bedtime Mode everyday/specific days for a specific period of time. 2. Turn on Don't Disturb Mode (Turn off all notifications and sounds) or Turn off Selected App Notifications 3. Turn on Night Light Mode / Gray-Scale Mode 4. A User can create or choose several Bedtime Profiles, based on 1. Specific period of sleep start and end time 2. Level of Gray Scale Display or Night Light Color Temperature 3. Don't Disturb Mode On 4. Specific Application Notification On/Off For more info, please look into the following links: 1. https://support.google.com/datally/answer/9101056?hl=en 2. https://9to5google.com/2020/04/21/google-digital-wellbeing-bedtime-mode/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1882522/+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 1882522] [NEW] [Feature Request] Add Bedtime Mode on Ubuntu Desktop
You have been subscribed to a public bug: [Feature Request] Android OS has Bedtime Mode features. Same Bedtime features can be useful for Ubuntu Desktop. Feature of Bedtime can be: 1. Turn on Bedtime Mode everyday/specific days for a specific period of time. 2. Turn on Don't Disturb Mode (Turn off all notifications and sounds) or Turn off Selected App Notifications 3. Turn on Night Light Mode / Gray-Scale Mode 4. A User can create or choose several Bedtime Profiles, based on 1. Specific period of sleep start and end time 2. Level of Gray Scale Display or Night Light Color Temperature 3. Don't Disturb Mode On 4. Specific Application Notification On/Off For more info, please look into the following links: 1. https://support.google.com/datally/answer/9101056?hl=en 2. https://9to5google.com/2020/04/21/google-digital-wellbeing-bedtime-mode/ ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- [Feature Request] Add Bedtime Mode on Ubuntu Desktop https://bugs.launchpad.net/bugs/1882522 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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
Re: [Touch-packages] [Bug 1882494] Comment bridged from LTC Bugzilla
On Mon, Jun 08, 2020 at 10:59:30AM -, bugproxy wrote: > --- Comment From i...@de.ibm.com 2020-06-08 06:52 EDT--- > This is correct. > zlib acceleration has been added with > https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1823157 to 19.10, so > the fix should go there as well. Earlier versions are not affected. Note that Ubuntu 19.10 reaches EOL in just over a month, so this may not wind up being fixed in that release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1882494 Title: [UBUNTU 20.04] zlib not working on all s390x systems configurations Status in Ubuntu on IBM z Systems: Triaged Status in zlib package in Ubuntu: New Status in zlib source package in Eoan: New Status in zlib source package in Focal: New Status in zlib source package in Groovy: New Bug description: Pull request (https://github.com/madler/zlib/pull/410) and tagged https://github.com/iii-i/zlib/tree/dfltcc-20200511. The new code contains the following improvements: * Added support for switching between software and hardware compression. * Added --dfltcc configure flag (the old way of building it still works). Switching between software and hardware compression is not simply a nice-to-have feature, but is actually required by Java - that's why we are requesting an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882494/+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 1882547] Re: systemd-resolved dumps core all the time
I can't seem to be able to post a core file as attachment here. -- 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/1882547 Title: systemd-resolved dumps core all the time Status in systemd package in Ubuntu: New Bug description: It dumps core all the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 8 16:51:11 2020 ExecutablePath: /usr/lib/systemd/systemd-resolved InstallationDate: Installed on 2019-09-30 (252 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999 mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+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 1882547] Re: systemd-resolved dumps core all the time
systemd-resolved dumps core resulting in DNS resolution failures in applications. -- 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/1882547 Title: systemd-resolved dumps core all the time Status in systemd package in Ubuntu: New Bug description: It dumps core all the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 8 16:51:11 2020 ExecutablePath: /usr/lib/systemd/systemd-resolved InstallationDate: Installed on 2019-09-30 (252 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999 mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+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 1882547] [NEW] systemd-resolved dumps core all the time
Public bug reported: It dumps core all the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 8 16:51:11 2020 ExecutablePath: /usr/lib/systemd/systemd-resolved InstallationDate: Installed on 2019-09-30 (252 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999 mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1882547 Title: systemd-resolved dumps core all the time Status in systemd package in Ubuntu: New Bug description: It dumps core all the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 8 16:51:11 2020 ExecutablePath: /usr/lib/systemd/systemd-resolved InstallationDate: Installed on 2019-09-30 (252 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago) dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999 mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+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 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home
On Fri, Jun 05, 2020 at 09:38:35AM -, veribaka wrote: > Is there a time frame to consider that the original reporter will not be > returning to this discussion? > > Should I open my own bug report with my logs? Please do open your own bug report with the relevant log files and make a comment in this bug report with the number of your new report. Thanks! -- Brian Murray -- 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: Incomplete 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 1846188] Re: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only)
** Changed in: gtk Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1846188 Title: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only) Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Committed Status in nautilus package in Ubuntu: Invalid Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 In Nautilus, tooltips appear far to the left in the app menu. (Kazam and Peek were unable to record Nautilus) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1846188/+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 1879533] Re: busybox does not verify TLS connections with CONFIG_FEATURE_WGET_OPENSSL=y and CONFIG_FEATURE_WGET_HTTPS unset, and doesn't warn either about it
Build focal subiquity image with proposed enabled and busybox version 1:1.30.1-4ubuntu6.1 at https://launchpad.net/~xnox/+livefs/ubuntu/focal/any/+build/221093 downloaded just the initrd & vmlinuz. Waited for it to fail to boot, and sourced /scripts/functions and executed configure_networking. Downloaded https://start.ubuntu.com successfully Failed to download https://untrusted-root.badssl.com Verification successful. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1879533 Title: busybox does not verify TLS connections with CONFIG_FEATURE_WGET_OPENSSL=y and CONFIG_FEATURE_WGET_HTTPS unset, and doesn't warn either about it Status in busybox package in Ubuntu: Fix Released Status in busybox source package in Focal: Fix Committed Status in busybox source package in Groovy: Fix Released Bug description: [Impact] * CONFIG_FEATURE_WGET_OPENSSL=y enables https support in wget busybox applet using openssl * CONFIG_FEATURE_WGET_HTTPS=y enables https support in wget busybox applet using internal TLS code * CVE-2018-1000500 ensured that when CONFIG_FEATURE_WGET_HTTPS=y is used, a message is printed to notify the users that TLS verification is not perfomed. * However, when one configures with CONFIG_FEATURE_WGET_OPENSSL=y and CONFIG_FEATURE_WGET_HTTPS unset - no such message is printed. * Also TLS verification is not performed under OPENSSL case. * When performing https requests, it works openssl s_client and communicates with it to perform https download * Whilst doing so, it does not pass `-verify_return_error` option, meaning any verification errors are ignored * There is no warning that TLS verification was not performed [Test Case] * Preparation: sudo apt install busybox; or build busybox with CONFIG_FEATURE_WGET_OPENSSL=y * Test case: /bin/busybox wget https://untrusted-root.badssl.com/ * Expected: download failed, or download suceeds with warning printed that verification is disabled * Observed: download success without a warning that verification is disabled. $ /bin/busybox wget https://untrusted-root.badssl.com/ Connecting to untrusted-root.badssl.com (104.154.89.105:443) index.html 100% |*| 600 0:00:00 ETA $ cat index.html | grep certificate The certificate for this site is signed using an untrusted root. [Regression Potential] * The fact that /bin/busybox wget https:// succeeds without TLS verification might be relied upon. If this issue is fixed, ensure that `--no-check-certificate` is honored. [Other Info] * Proposed fix pass `-verify_return_error` to s_client, unless `--no-check- certificate` is specified To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1879533/+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 1879525] Re: Add TLS support
Build focal subiquity image with proposed enabled and busybox version 1:1.30.1-4ubuntu6.1 at https://launchpad.net/~xnox/+livefs/ubuntu/focal/any/+build/221093 downloaded just the initrd & vmlinuz. Waited for it to fail to boot, and sourced /scripts/functions and executed configure_networking. Downloaded https://start.ubuntu.com successfully Failed to download https://untrusted-root.badssl.com Verification successful. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1879525 Title: Add TLS support Status in busybox package in Ubuntu: Fix Released Status in busybox source package in Focal: Fix Committed Bug description: [Impact] * busybox in the initramfs provides wget applet that is used by casper for netboot support * It does not support https at the moment, but it is desirable that it does * There is built-in TLS code, or "fork & execute openssl" * Enable the later one, and optionally include /usr/bin/openssl & certs, when building casper-like initrds which should support netboot. [Test Case] * Boot casper created initrd, with break=bottom * Configure dhcp based networking * Attempt to wget https://start.ubuntu.com/connectivity-check * It should succeed [Regression Potential] * The openssl codepath is optional in busybox wget, and we only include openssl & certs for casper. * The casper based initrd will grow in size, due to inclusion of openssl & certs [Other Info] * Parity with d-i, which includes https support already To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1879525/+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 1878233] Re: Unable to locate package/Headers missing
Is there a warning somewhere about this? Because including the library
but not the header is bound to frustrate quite a few people. You know
thinking it should be working because it's in the library. I know it
took me quite a bit of investigation to figure out what was going on.
And from my experience, linking a locally compiled Qt version is quite
troublesome if you don't take care. Anyway, I don't know how it works,
but at least maybe include a warning somewhere?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qt3d-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1878233
Title:
Unable to locate package/Headers missing
Status in qt3d-opensource-src package in Ubuntu:
Fix Released
Status in qt3d-opensource-src source package in Focal:
Won't Fix
Bug description:
Hi,
I am a scientific software developper and I'm trying to use Qt3D on Ubuntu
20.04LTS.
I am not used to filing bugs here, sorry if its not following the standards,
any comments on this will also be appreciated.
Here is a list of the packages I installed prior to this bug.
sudo apt install qt3d5-dev
sudo apt install qt3d5-dev-tools
sudo apt install qt3d-assimpsceneimport-plugin
sudo apt install qt3d-defaultgeometryloader-plugin
sudo apt install qt3d-gltfsceneio-plugin
sudo apt install qt3d-scene2d-plugin
sudo apt install qml-module-qt3d
I also ran the command line:
sudo strip --remove-section=.note.ABI-tag
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
as per my computer science colleague request
But I am having errors left and right concerning the headers, as much
as I actually have to include in my CMakleLists.txt those lines (I
started to debug from Windows to Linux since our scientific build
machine uses this target):
#- *target*
# Note: 3D Disabled on build machine because of 3D in QT
if( ${CMAKE_SYSTEM_NAME} STREQUAL "Windows")
add_subdirectory(*target*)
set_target_properties(*target* PROPERTIES FOLDER "apps/*target*")
#Tell CMake to produce a visual studio Qt Project for integration with Qt
Vs Tools
set_target_properties(*target* PROPERTIES VS_GLOBAL_KEYWORD Qt4VSv1.0)
else
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DCore")
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DRender")
include_directories("/usr/include/x86_64-linux-gnu/qt5/Qt3DExtras") ->this
one useless
endif()
as you can see:
/usr/include/x86_64-linux-gnu/qt5$ ls
Qt3DCoreQt3DQuickRender QtDBusQtNetwork
QtPositioning QtQuick QtSerialPort QtUiTools QtWebKit
Qt3DInput Qt3DQuickScene2D QtDesignerQtOpenGL
QtPositioningQuick QtQuickParticles QtSql QtWebChannel
QtWebKitWidgets
Qt3DLogic Qt3DRenderQtDesignerComponents QtOpenGLExtensions
QtPrintSupport QtQuickShapes QtSvg QtWebEngine
QtWidgets
Qt3DQuick QtConcurrent QtGui QtPacketProtocol
QtQml QtQuickTest QtTestQtWebEngineCore QtXml
Qt3DQuickInput QtCoreQtHelpQtPlatformHeaders
QtQmlDebug QtQuickWidgetsQtUiPluginQtWebEngineWidgets
And this sub-package that you have does not contain the headers.
https://packages.ubuntu.com/focal/amd64/libqt53dextras5/filelist
I think I will also be submitting there I find it weird.
I will probably download Qt3D sources and temporarily link the headers
directly there but this is far from optimal for a build machine, as you might
expect.
And finaly, this packages appear when I tab on: apt install qt3d-op...
but when I run the install it cant find it. This is probably the issue that
you want to look at, as I will be going to this other package to see why the
headers are not following.
Thank you very much and I hope I followed the guidelines here are my infos:
/usr/include/x86_64-linux-gnu/qt5$ lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04
apt-cache policy qt3d-opensource-src
N: Unable to locate package qt3d-opensource-src
/usr/include/x86_64-linux-gnu/qt5$ apt-cache policy libqt53dextras5
libqt53dextras5:
Installed: 5.12.8+dfsg-0ubuntu1
Candidate: 5.12.8+dfsg-0ubuntu1
Version table:
*** 5.12.8+dfsg-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status
/usr/include/x86_64-linux-gnu/qt5$ sudo apt install qt3d-opensource-src
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package qt3d-opensource-src
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1878233/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
Need to report that the Broadcom BCM43228 wifi card intermittently shows the Wi-Fi networks. It will show them only occasionally; usually after a cold boot. If the machine is rebooted, the Wi-Fi networks disappear. Can anyone tell me how to test a wifi card for hardware failure? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: New Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1882242/+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 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps
** Branch linked: lp:~slyon/apport/apport-snap-handling -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: Triaged Status in Snap Store: New Status in apport package in Ubuntu: Triaged Status in apport source package in Focal: Triaged Bug description: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+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 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
Re-install systemd-timesyncd seem to fix this issue. However while trying to install systemd-timesyncd the ntp package will be removed. Maybe we're using ntp instead of systemd-timesyncd on Focal s390x by default? -- 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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: Incomplete Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+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 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
I tried to remove the /etc/systemd/system/systemd-timesyncd.service symbolic link to /dev/null by following this post [1] After that it's complaining the service was not found: $ sudo systemctl start systemd-timesyncd Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service not found. Hmm... [1] https://blog.ruanbekker.com/blog/2017/12/09/unmask-a-masked-service- in-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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: Incomplete Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
I have the same issues with: - Cowin E7 Headset - Plugable USB-BT4LE Bluetooth dongle -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
The correct file location for systemd-timesyncd.service should be: $ sudo systemctl enable systemd-timesyncd Failed to enable unit: Unit file /etc/systemd/system/systemd-timesyncd.service is masked. $ file /etc/systemd/system/systemd-timesyncd.service /etc/systemd/system/systemd-timesyncd.service: symbolic link to /dev/null -- 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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: Incomplete Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+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 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
Hello Dimitri, After a quick check it looks like this service is still in inactive (dead) state even after a reboot. ubuntu@kernel04:/lib/systemd$ sudo systemctl status systemd-timesyncd ● systemd-timesyncd.service Loaded: masked (Reason: Unit systemd-timesyncd.service is masked.) Active: inactive (dead) ubuntu@kernel04:/lib/systemd$ file /lib/systemd/system/systemd-timesyncd.service /lib/systemd/system/systemd-timesyncd.service: cannot open `/lib/systemd/system/systemd-timesyncd.service' (No such file or directory) And there is no "systemd-timesyncd.service" file at where is should be. So yeah it's not running, our testing tool did not check the state first before trying to stop / start it. $ sudo systemctl edit systemd-timesyncd Cannot edit systemd-timesyncd.service: unit is masked. Let me see if I can un-mask it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: Incomplete Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+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 1882473] Re: test bug
** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1882473 Title: test bug Status in systemd: New Status in systemd package in Ubuntu: Invalid Bug description: test upstream bug To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1882473/+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 1882524] [NEW] [CF-53DA502FW, Realtek ALC269VB, Speaker, Internal] Playback problem
Public bug reported: i have no audio from speakers in my laptop but i have audio output on hdmi. i have another harddrive with windows 7 on it and the speakers work correctly on that. they used to work on this distro Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dani 1677 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 12:59:05 2020 InstallationDate: Installed on 2020-03-24 (75 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [CF-53DA502FW, Realtek ALC269VB, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-16 (22 days ago) dmi.bios.date: 05/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.00L15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CF53-1 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.00L15:bd05/25/2012:svnPanasonicCorporation:pnCF-53DA502FW:pvr001:rvnPanasonicCorporation:rnCF53-1:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF53-1 dmi.product.name: CF-53DA502FW dmi.product.sku: CF-53DA502FW dmi.product.version: 001 dmi.sys.vendor: Panasonic Corporation ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1882524 Title: [CF-53DA502FW, Realtek ALC269VB, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: i have no audio from speakers in my laptop but i have audio output on hdmi. i have another harddrive with windows 7 on it and the speakers work correctly on that. they used to work on this distro Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dani 1677 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 12:59:05 2020 InstallationDate: Installed on 2020-03-24 (75 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [CF-53DA502FW, Realtek ALC269VB, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-16 (22 days ago) dmi.bios.date: 05/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.00L15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CF53-1 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.00L15:bd05/25/2012:svnPanasonicCorporation:pnCF-53DA502FW:pvr001:rvnPanasonicCorporation:rnCF53-1:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF53-1 dmi.product.name: CF-53DA502FW dmi.product.sku: CF-53DA502FW dmi.product.version: 001 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1882524/+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 1882368] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1882368/+attachment/5381604/+files/CurrentDmesg.txt -- 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/1882368 Title: Sound is louder after resume from suspend or logging in Ubuntu 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.04 and have noticed that after logging back on to a machine either after its been asleep/suspended or logged out due to inactivity the sound is much louder at the same volume. I haven't enabled amplification or any other sound feature. To duplicate, boot machine with volume at say 50% and listen to some music. Let it either log out or suspend/sleep and then log back in, start music/sound and it will be much louder. In fact this louder sound at the volume sounds correct, because the windows boot sounds the same at that level. When ubuntu boots the volume is much softer. The sound post logging in after a suspend or lock out is what it should be from the get go. Soundcard details 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) DeviceName: Onboard - Sound Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS Flags: bus master, fast devsel, latency 32, IRQ 143 Memory at a351 (64-bit, non-prefetchable) [size=16K] Memory at a310 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kashif 2925 F pulseaudio /dev/snd/controlC0: kashif 2925 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-20 (414 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-08 (30 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/19/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.name: 84FD dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.25:bd11/19/2019:svnHP:pnOMENbyHPObeliskDesktop875-0xxx:pvr:rvnHP:rn84FD:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Omen dmi.product.name: OMEN by HP Obelisk Desktop 875-0xxx dmi.product.sku: 4NM65AA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882368/+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 1882368] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1882368/+attachment/5381605/+files/Dependencies.txt -- 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/1882368 Title: Sound is louder after resume from suspend or logging in Ubuntu 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.04 and have noticed that after logging back on to a machine either after its been asleep/suspended or logged out due to inactivity the sound is much louder at the same volume. I haven't enabled amplification or any other sound feature. To duplicate, boot machine with volume at say 50% and listen to some music. Let it either log out or suspend/sleep and then log back in, start music/sound and it will be much louder. In fact this louder sound at the volume sounds correct, because the windows boot sounds the same at that level. When ubuntu boots the volume is much softer. The sound post logging in after a suspend or lock out is what it should be from the get go. Soundcard details 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) DeviceName: Onboard - Sound Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS Flags: bus master, fast devsel, latency 32, IRQ 143 Memory at a351 (64-bit, non-prefetchable) [size=16K] Memory at a310 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kashif 2925 F pulseaudio /dev/snd/controlC0: kashif 2925 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-20 (414 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-08 (30 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/19/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.name: 84FD dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.25:bd11/19/2019:svnHP:pnOMENbyHPObeliskDesktop875-0xxx:pvr:rvnHP:rn84FD:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Omen dmi.product.name: OMEN by HP Obelisk Desktop 875-0xxx dmi.product.sku: 4NM65AA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882368/+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 1882368] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1882368/+attachment/5381607/+files/PulseList.txt -- 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/1882368 Title: Sound is louder after resume from suspend or logging in Ubuntu 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.04 and have noticed that after logging back on to a machine either after its been asleep/suspended or logged out due to inactivity the sound is much louder at the same volume. I haven't enabled amplification or any other sound feature. To duplicate, boot machine with volume at say 50% and listen to some music. Let it either log out or suspend/sleep and then log back in, start music/sound and it will be much louder. In fact this louder sound at the volume sounds correct, because the windows boot sounds the same at that level. When ubuntu boots the volume is much softer. The sound post logging in after a suspend or lock out is what it should be from the get go. Soundcard details 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) DeviceName: Onboard - Sound Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS Flags: bus master, fast devsel, latency 32, IRQ 143 Memory at a351 (64-bit, non-prefetchable) [size=16K] Memory at a310 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kashif 2925 F pulseaudio /dev/snd/controlC0: kashif 2925 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-20 (414 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-08 (30 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/19/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.name: 84FD dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.25:bd11/19/2019:svnHP:pnOMENbyHPObeliskDesktop875-0xxx:pvr:rvnHP:rn84FD:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Omen dmi.product.name: OMEN by HP Obelisk Desktop 875-0xxx dmi.product.sku: 4NM65AA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882368/+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 1882368] Re: Sound is louder after resume from suspend or logging in Ubuntu 20.04
apport information ** Tags added: apport-collected ** Description changed: I'm running Ubuntu 20.04 and have noticed that after logging back on to a machine either after its been asleep/suspended or logged out due to inactivity the sound is much louder at the same volume. I haven't enabled amplification or any other sound feature. To duplicate, boot machine with volume at say 50% and listen to some music. Let it either log out or suspend/sleep and then log back in, start music/sound and it will be much louder. In fact this louder sound at the volume sounds correct, because the windows boot sounds the same at that level. When ubuntu boots the volume is much softer. The sound post logging in after a suspend or lock out is what it should be from the get go. Soundcard details 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) DeviceName: Onboard - Sound Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS Flags: bus master, fast devsel, latency 32, IRQ 143 Memory at a351 (64-bit, non-prefetchable) [size=16K] Memory at a310 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: kashif 2925 F pulseaudio + /dev/snd/controlC0: kashif 2925 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-04-20 (414 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + NonfreeKernelModules: nvidia_modeset nvidia + Package: pulseaudio 1:13.99.1-1ubuntu3.2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 + Tags: focal + Uname: Linux 5.4.0-33-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-05-08 (30 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/19/2019 + dmi.bios.vendor: AMI + dmi.bios.version: F.25 + dmi.board.name: 84FD + dmi.board.vendor: HP + dmi.board.version: 00 + dmi.chassis.type: 3 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnAMI:bvrF.25:bd11/19/2019:svnHP:pnOMENbyHPObeliskDesktop875-0xxx:pvr:rvnHP:rn84FD:rvr00:cvnHP:ct3:cvr: + dmi.product.family: 103C_53311M HP Omen + dmi.product.name: OMEN by HP Obelisk Desktop 875-0xxx + dmi.product.sku: 4NM65AA#ABA + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1882368/+attachment/5381603/+files/AlsaInfo.txt -- 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/1882368 Title: Sound is louder after resume from suspend or logging in Ubuntu 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.04 and have noticed that after logging back on to a machine either after its been asleep/suspended or logged out due to inactivity the sound is much louder at the same volume. I haven't enabled amplification or any other sound feature. To duplicate, boot machine with volume at say 50% and listen to some music. Let it either log out or suspend/sleep and then log back in, start music/sound and it will be much louder. In fact this louder sound at the volume sounds correct, because the windows boot sounds the same at that level. When ubuntu boots the volume is much softer. The sound post logging in after a suspend or lock out is what it should be from the get go. Soundcard details 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) DeviceName: Onboard - Sound Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS Flags: bus master, fast devsel, latency 32, IRQ 143 Memory at a351 (64-bit, non-prefetchable) [size=16K] Memory at a310 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kashif 2925 F pulseaudio /dev/snd/controlC0: kashif 2925 F pulseaudio Casper
[Touch-packages] [Bug 1882368] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1882368/+attachment/5381606/+files/ProcCpuinfoMinimal.txt -- 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/1882368 Title: Sound is louder after resume from suspend or logging in Ubuntu 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.04 and have noticed that after logging back on to a machine either after its been asleep/suspended or logged out due to inactivity the sound is much louder at the same volume. I haven't enabled amplification or any other sound feature. To duplicate, boot machine with volume at say 50% and listen to some music. Let it either log out or suspend/sleep and then log back in, start music/sound and it will be much louder. In fact this louder sound at the volume sounds correct, because the windows boot sounds the same at that level. When ubuntu boots the volume is much softer. The sound post logging in after a suspend or lock out is what it should be from the get go. Soundcard details 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) DeviceName: Onboard - Sound Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS Flags: bus master, fast devsel, latency 32, IRQ 143 Memory at a351 (64-bit, non-prefetchable) [size=16K] Memory at a310 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kashif 2925 F pulseaudio /dev/snd/controlC0: kashif 2925 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-20 (414 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-08 (30 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/19/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.name: 84FD dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.25:bd11/19/2019:svnHP:pnOMENbyHPObeliskDesktop875-0xxx:pvr:rvnHP:rn84FD:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Omen dmi.product.name: OMEN by HP Obelisk Desktop 875-0xxx dmi.product.sku: 4NM65AA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882368/+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 1882494] Re: [UBUNTU 20.04] zlib not working on all s390x systems configurations
Ok, thx. ** Also affects: zlib (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: zlib (Ubuntu Groovy) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Also affects: zlib (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: zlib (Ubuntu Eoan) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: zlib (Ubuntu Focal) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: zlib (Ubuntu Groovy) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Foundations Team (canonical-foundations) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1882494 Title: [UBUNTU 20.04] zlib not working on all s390x systems configurations Status in Ubuntu on IBM z Systems: Triaged Status in zlib package in Ubuntu: New Status in zlib source package in Eoan: New Status in zlib source package in Focal: New Status in zlib source package in Groovy: New Bug description: Pull request (https://github.com/madler/zlib/pull/410) and tagged https://github.com/iii-i/zlib/tree/dfltcc-20200511. The new code contains the following improvements: * Added support for switching between software and hardware compression. * Added --dfltcc configure flag (the old way of building it still works). Switching between software and hardware compression is not simply a nice-to-have feature, but is actually required by Java - that's why we are requesting an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882494/+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 1637800] Re: add a motd script for news
motd-news vs privacy / security / telemetry https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1637800 Title: add a motd script for news Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Bug description: Add a new update-motd script for printing news and/or important notices. == SRU == [IMPACT] We should add important security messages or other news to the MOTD. [TEST CASE] Login to the system and ensure that the "news" section of the motd is displayed. Note that you might need to force trigger an update by running 'sudo update-motd'. [REGRESSION POTENTIAL] No reasonable regression potential. The script simply prints 2 lines of text to the MOTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
All messages received over a year (Ubuntu 18.04): * Congrats to the Kubernetes community on 1.16 beta 1! Now available * Kata Containers are now fully integrated in Charmed Kubernetes 1.16! * Keen to learn Istio? It's included in the single-package MicroK8s. * Kubernetes 1.18 GA is now available! See https://microk8s.io for docs or * Latest Kubernetes 1.18 beta is now available for your laptop, NUC, cloud * MicroK8s 1.15 is out! It has already been installed on more * MicroK8s 1.15 is out! Thanks to all 40 contributors, you get the latest * MicroK8s passes 9 million downloads. Thank you to all our contributors! * Multipass 1.0 is out! Get Ubuntu VMs on demand on your Linux, Windows or * Multipass 1.1 adds proxy support for developers behind enterprise * Overheard at KubeCon: "microk8s.status just blew my mind". * 'snap info' now shows the freshness of each channel. * Ubuntu 20.04 LTS is out, raising the bar on performance, security, * Ubuntu's Kubernetes 1.14 distributions can bypass Docker and use containerd None of them are about security and none of them are customized using uptime, ubuntu version, kernel version, curl version, ip, ... Why do pack all this into User-Agent which can be linked to public IP every 12 hours? ** Attachment added: "motd-news.txt" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5381565/+files/motd-news.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Confirmed Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
@Andrew Just read the comment https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/comments/20 -- 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/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in initramfs-tools package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Fix Committed Status in lvm2 source package in Focal: Invalid Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871154/+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 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
this will be fixed as part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876321 in Ubuntu-5.3.0-56.50 ** Package changed: libdrm (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later Status in DRI: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe package in Ubuntu: Confirmed Bug description: When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or later (including 5.3.0-53), everything seems to be working as usual. However, when I shutdown, the system will only soft shutdown, with the CPU still running at full power, forcing me to hold down the power button to fully power off affected systems. If I reboot, it will cause the system to hang and not respond. Either way, a hard reset or poweroff will be required, and this is not an option for systems being remotely accessed. It is not possible for me to collect kernel logs at this point, unless something wrong is happening in those kernel versions before the actual shutdown. It is possible that this may also occur on Ubuntu 20.04 with kernel versions 5.4.0-29 and later, but I have not yet tested this out. This problem is occurring on both my desktop and laptop computers which respectively are: * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU In the meantime, I am stuck on kernel version 5.3.0-51, as that is the last working 5.3.x kernel version offered in the standard Ubuntu repositories that doesn't have this problem, without me having to use PPAs. I don't know if this problem also occurs on systems with Intel CPUs, as I don't own any recently-made system (last 3 years from 2017) with such CPUs to test if this problem occurs on them. To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1880041/+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 1882494] Comment bridged from LTC Bugzilla
--- Comment From i...@de.ibm.com 2020-06-08 06:52 EDT--- This is correct. zlib acceleration has been added with https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1823157 to 19.10, so the fix should go there as well. Earlier versions are not affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1882494 Title: [UBUNTU 20.04] zlib not working on all s390x systems configurations Status in Ubuntu on IBM z Systems: Triaged Status in zlib package in Ubuntu: New Bug description: Pull request (https://github.com/madler/zlib/pull/410) and tagged https://github.com/iii-i/zlib/tree/dfltcc-20200511. The new code contains the following improvements: * Added support for switching between software and hardware compression. * Added --dfltcc configure flag (the old way of building it still works). Switching between software and hardware compression is not simply a nice-to-have feature, but is actually required by Java - that's why we are requesting an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882494/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
Plug your headset out and back in, confirm the headset is present in
ALSA but not pulseaudio and kill pulseaudio: pkill -U $USER pulseaudio.
Pulseaudio will restart itself automatically.
All audiostreams currently active will break, but pulseaudio is
restarted and should recognoze your headset again.
Also, this does not happen with Ubunutu 20.04 on my laptop (yet).
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in alsa-lib package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1865499/+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 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
If it is masked, is it running? If it is not running, why are you trying to stop it? ** 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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: Incomplete Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+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 1882494] Re: [UBUNTU 20.04] zlib not working on all s390x systems configurations
Did I got it right that the "being able to switch between software and hardware compression _feature_" is at the same time the _fix_ for the issue with Java? And would that only need to be added to focal/20.04 or also to other Ubuntu releases? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1882494 Title: [UBUNTU 20.04] zlib not working on all s390x systems configurations Status in Ubuntu on IBM z Systems: Triaged Status in zlib package in Ubuntu: New Bug description: Pull request (https://github.com/madler/zlib/pull/410) and tagged https://github.com/iii-i/zlib/tree/dfltcc-20200511. The new code contains the following improvements: * Added support for switching between software and hardware compression. * Added --dfltcc configure flag (the old way of building it still works). Switching between software and hardware compression is not simply a nice-to-have feature, but is actually required by Java - that's why we are requesting an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882494/+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 1865499] Re: pulseaudio doesn't detect (new) USB headset
I think I have the same problem. In the last week, my USB headset
(Microsoft LifeChat LX-3000) is often only recognized as an output, or
only recognized as an input, by PulseAudio. When checking with
alsamixer, it seems that Alsa recognizes both input and output, but
PulseAudio doesn't...
This does seem like a race condition in PulseAudio, so those Alsa
changes don't seem like what's caused my problem. How can I confirm if
this is the same problem as reported or a different one?
--
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/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in alsa-lib package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1865499/+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 1882494] Re: [UBUNTU 20.04] zlib not working on all s390x systems configurations
** Changed in: ubuntu-z-systems Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1882494 Title: [UBUNTU 20.04] zlib not working on all s390x systems configurations Status in Ubuntu on IBM z Systems: Triaged Status in zlib package in Ubuntu: New Bug description: Pull request (https://github.com/madler/zlib/pull/410) and tagged https://github.com/iii-i/zlib/tree/dfltcc-20200511. The new code contains the following improvements: * Added support for switching between software and hardware compression. * Added --dfltcc configure flag (the old way of building it still works). Switching between software and hardware compression is not simply a nice-to-have feature, but is actually required by Java - that's why we are requesting an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882494/+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 1882494] Re: [UBUNTU 20.04] zlib not working on all s390x systems configurations
** Also affects: ubuntu-z-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1882494 Title: [UBUNTU 20.04] zlib not working on all s390x systems configurations Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Bug description: Pull request (https://github.com/madler/zlib/pull/410) and tagged https://github.com/iii-i/zlib/tree/dfltcc-20200511. The new code contains the following improvements: * Added support for switching between software and hardware compression. * Added --dfltcc configure flag (the old way of building it still works). Switching between software and hardware compression is not simply a nice-to-have feature, but is actually required by Java - that's why we are requesting an update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1882494/+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 1866604] Re: gdbtui source window does't display Unicode text
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdb (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1866604
Title:
gdbtui source window does't display Unicode text
Status in gdb package in Ubuntu:
Confirmed
Bug description:
In Ubuntu 20.04, I discovered that the gdb 9 TUI source code window
doesn't display properly the UTF-8 characters (Chinese, Cyrillic,
etc.) but displays correctly only the ASCII ones. For example, the
following source code
printf("Здравей, свят!\n");
appears in the source code window as
printf("^^P^ ^P^ ^Q^┗↑@^^P^ ^P^ ^P^ ^P^ ^^Q^┗↑╝^^P^ ^Q^ ^Q^ \n");
The command windows is not affected (when I type non-ASCII characters
into it, they appear OK).
Additionally, I found out the following:
(1) This bug was introduced in version 8.3;
(2) It affects only some CPU architectures.
In more detail, I tested version "Debian 8.3.1-1" on two 64-bit
machines with the same version of Debian (bullseye/sid), one with
PowerPC, and the other with SPARC. The bug shows up only on the SPARC
machine, not the PowerPC one. I then built the generic version 8.3.1
on a 64-bit ARM machine. The bug didn't show up there. And then, I
built it on a 64-bit MIPS (big endian) machine, where the bug did show
up. Repeated this with version 8.3. The bug showed up again. When I
built the generic version 8.2.1 on the same MIPS machine, the bug
didn't show up. A "diff -u gdb-8.2.1/gdb/tui gdb-8.3/gdb/tui" shows a
lot of changes made in the TUI code of version 8.3 to add some
colourisation to the TUI, and the bug was probably introduced during
this process. Sorry that I can't help more to isolate the bug. But
it's quite strange that it manifests itself only on x86-64 (as I had
found out previously using Ubuntu 20-04), SPARC and MIPS, but not on
ARM and PowerPC. I suppose that because of this, it will be rather
hard to pinpoint.
This bug is similar to the already fixed bug 1275210 where I also
described it but then realised that it has a different origin and is
therefore a different bug, so I report it as a new one now. Someone
already reported this bug as bug 25296 in the gdb Bugzilla which I
confirmed there.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1866604/+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 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
Looks like this has something to do with systemd, with zVM boot with 5.4.0-33, I can still reproduce this issue: ubuntu@kernel04:~$ sudo systemctl stop systemd-timesyncd ubuntu@kernel04:~$ sudo systemctl start systemd-timesyncd Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. ubuntu@kernel04:~$ ** Summary changed: - ubuntu_ltp_syscalls failed to run on Focal s390x + ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service ** Also affects: systemd (Ubuntu) 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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: New Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+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 1882445] Re: Applications read ICC profile always from primary monitor
*** This bug is a duplicate of bug 938751 *** https://bugs.launchpad.net/bugs/938751 The color profile works perfectly fine on my primary monitor. It's only on the secondary monitor that it's clearly picking up the wrong profile. -- 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/1882445 Title: Applications read ICC profile always from primary monitor Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.04 NVidia properietary drivers 2 monitors, each with its own ICC profile loaded Monitors are configured in "Join Displays" mode. Image Viewer and Chrome always use the color profile of whatever monitor is set as the Primary Display, regardless of which monitor they're on. Refreshing the window or creating new tabs doesn't help. Since one of my monitors is wide gamut and the other is standard gamut, the issue is extremely glaring, leading to extremely oversaturated colors on the wide gamut monitor if the standard gamut monitor is primary, or extremely undersaturated colors on the standard gamut monitor if the wide gamut one is set as primary. Expected behaviour: All color-managed applications apply the ICC profile of the monitor they're currently displayed on, as soon as they're dragged on it. I tested that Chrome on Windows 10 uses this behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06: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.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 18:23:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 [GeForce GTX 970] [1462:3160] InstallationDate: Installed on 2020-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. B450 GAMING X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=3a087e9b-0230-4c3c-93fa-663dcecc108d ro quiet SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450 GAMING X 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.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450GAMINGX:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450GAMINGX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 GAMING X dmi.product.sku: Default string dmi.product.version: Default string 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882445/+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 1875558] Re: [SRU] libproxy1-plugin-gsettings triggers a lot of warnings
Checked too, seems good to me - updating tags. Thanks! ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1875558 Title: [SRU] libproxy1-plugin-gsettings triggers a lot of warnings Status in libproxy package in Ubuntu: Fix Released Status in libproxy source package in Focal: Fix Committed Bug description: [Impact] * The proxy configuration from GSettings is not getting exported and thus is not used by libproxy-enabled applications. * Many GLib applications are now throwing critical messages in the logs when running. This is escpecially true for WebKitGtk applications which are throwing one message by subprocess. [Test Case] * Open a WebKitGtk application such as Epiphany (GNOME Web) with the terminal and see the critical messages GLib-GObject-WARNING **: 09:00:09.217: ../../../gobject/gsignal.c:2617: signal 'changed::' is invalid for instance '0x55b923a6b430' of type 'GSettings' [Regression Potential] * No regression is to expect from this patch [Other Info] * The patch is already in debian experimental and is available since 0.4.15-12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1875558/+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 1743684] Re: copying
If this is still a problem then please tell us what app or command you were using to copy. And how you can tell the files are different. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1743684 Title: copying Status in Ubuntu: Incomplete Bug description: some files lost, and some files damaged,while copying.It is to note that these files were mostly downloaded.the files earlier copied from device like cd were not defected . ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jan 17 08:54:52 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2017] InstallationDate: Installed on 2018-01-15 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BEH6110H.86A.0016.2011.0118.1128 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61WW dmi.board.vendor: Intel Corporation dmi.board.version: AAG23116-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H.86A.0016.2011.0118.1128:bd01/18/2011:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-203:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jan 17 07:45:43 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB OPTICAL MOUSEMOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1743684/+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 1750433] Re: fatal error launching grub
Sorry for the long delay... Do you still experience this problem? ** Package changed: xorg (Ubuntu) => grub2 (Ubuntu) ** Changed in: grub2 (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/1750433 Title: fatal error launching grub Status in grub2 package in Ubuntu: Incomplete Bug description: Somehow a beta version of grub is installed. I get a long list of code on startup and get a black and white box with a -e option. nothing works ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 19 20:34:28 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7660D] [1043:8526] LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Feb 19 20:33:15 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1750433/+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 1882500] [NEW] software-properties-qt: add option to remove unused deps in unattended upgrades
Public bug reported: Right now i'm using this command: sudo sed -i 's|//Unattended-Upgrade::Remove-Unused-Dependencies.*|Unattended-Upgrade::Remove-Unused-Dependencies "true";|g' /etc/apt/apt.conf.d/50unattended-upgrades But, i want software-properties-qt to have option like these in gui (see attachment) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "option" https://bugs.launchpad.net/bugs/1882500/+attachment/5381540/+files/Untitled.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/1882500 Title: software-properties-qt: add option to remove unused deps in unattended upgrades Status in software-properties package in Ubuntu: New Bug description: Right now i'm using this command: sudo sed -i 's|//Unattended-Upgrade::Remove-Unused-Dependencies.*|Unattended-Upgrade::Remove-Unused-Dependencies "true";|g' /etc/apt/apt.conf.d/50unattended-upgrades But, i want software-properties-qt to have option like these in gui (see attachment) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1882500/+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 1882453] Re: GUI blanks after long period of use
Please: 1. Attach a phoro or screenshot of the problem; and 2. Run this command: gsettings list-recursively org.gnome.shell > settings.txt and attach the resulting text file here. ** Tags added: nvidia ** Summary changed: - GUI blanks after long period of use + [nvidia] GUI blanks after long period of use ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1882453 Title: [nvidia] GUI blanks after long period of use Status in gnome-shell package in Ubuntu: Incomplete Bug description: GUI screen goes blank with a right click on the desktop or a click on the power button. The entire systems seems to slow too, with CPU utilization reaching 100% at a consistent interval. This has happened twice already after a long period of idle or when conducting many actions with several applications. Not sure if any of it is causation given its only happened twice and I can't replicate the problem consistently. If you need further information reach me at clmora...@pm.me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 Uname: Linux 5.4.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06: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.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: 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: Sun Jun 7 15:00:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM204 [GeForce GTX 970] [3842:2974] InstallationDate: Installed on 2020-05-20 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MSI MS-7885 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=40367ef8-089b-4ef9-9b43-d538f9b52b3d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/20/2015:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7885 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882453/+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 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
** Summary changed: - Images are washed out or colors are skewed in some apps + Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in Eye of GNOME: New Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+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
