[Bug 1880817] [NEW] tried to update to 20.04 again and failed again
Public bug reported: tried to update to 20.04 again and failed again ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18 Uname: Linux 5.3.0-55-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashDB: ubuntu Date: Wed May 27 08:48:24 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2020-05-27 (0 days ago) VarLogDistupgradeAptlog: Log time: 2020-05-27 08:47:41.092201 Log time: 2020-05-27 08:47:46.351147 Log time: 2020-05-27 08:48:08.914659 Log time: 2020-05-27 08:48:26.242672 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880817 Title: tried to update to 20.04 again and failed again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1880817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873762] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-05-27 02:57 EDT--- IBM Bugzilla status-> closed, works as designed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873762 Title: [Ubuntu 20.04] memory hotplug triggers page migration warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1873762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836162] Re: userns06 in containers from ubuntu_ltp failed on ARM64 / i386 / PowerPC
Passed on Eoan ARM64 / P8 / P9. i386 not tested on Eoan. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836162 Title: userns06 in containers from ubuntu_ltp failed on ARM64 / i386 / PowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879033] Re: [SRU focal] Bad theming/colors network manager (connections)
** Changed in: plasma-nm (Ubuntu Focal) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879033 Title: [SRU focal] Bad theming/colors network manager (connections) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-nm/+bug/1879033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880653] Re: irq/126-aerdrv always eating 30-40 % of a CPU core
The kernel disabled L0s of the Realtek wifi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880653 Title: irq/126-aerdrv always eating 30-40 % of a CPU core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879321] Re: Fix Pericom USB controller OHCI/EHCI PME# defect
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879321 Title: Fix Pericom USB controller OHCI/EHCI PME# defect To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1879321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880821] [NEW] xterm huge no longer works, displays same size as large.
Public bug reported: Whether I select large or huge, same size results, huge no longer gives me a very large font which owing to my crappy eyesight is sometimes helpful. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xterm 353-1ubuntu1 Uname: Linux 5.6.0 x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 27 00:07:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0 root=UUID=2332aa64-69b1-479f-88e1-dd92583809d9 ro SourcePackage: xterm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-eoan dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-eoan:cvnQEMU:ct1:cvrpc-q35-eoan: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-eoan dmi.sys.vendor: QEMU version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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 20.0.4-2ubuntu1 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: xterm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880821 Title: xterm huge no longer works, displays same size as large. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1880821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880653] Re: irq/126-aerdrv always eating 30-40 % of a CPU core
Can you please test this kernel without "pcie_aspm=off": https://people.canonical.com/~khfeng/lp1880653/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880653 Title: irq/126-aerdrv always eating 30-40 % of a CPU core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728045] Re: Please restore battery time remaining to top bar!
** Bug watch added: bugzilla.gnome.org/ #540373 https://bugzilla.gnome.org/show_bug.cgi?id=540373 ** Changed in: gnome-shell Remote watch: GNOME Bug Tracker #540373 => bugzilla.gnome.org/ #540373 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728045 Title: Please restore battery time remaining to top bar! To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1728045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
Can you please try kernel parameter "nomodeset"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880824] [NEW] Crashes when dragging items out of Budgie's task icon list
Public bug reported: Budgie Panel (or sometimes even the whole session) crashes when dragging items out of Budgie's task icon list. Notes: Budgie Panel is placed on bottom on the very bottom screen (of 3). Dragging them downside out of screen causes the crash. Crash details: Either budgie-panel freezes (and restarts after ~10 secs), or the whole session crashes and one ends up at the display manager's login screen. This issue also applied to Ubuntu Budgie 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: budgie-desktop 10.5-0ubuntu7 ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed May 27 09:13:01 2020 InstallationDate: Installed on 2019-08-26 (274 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: budgie-desktop UpgradeStatus: Upgraded to eoan on 2020-01-24 (123 days ago) ** Affects: budgie-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880824 Title: Crashes when dragging items out of Budgie's task icon list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1880824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880825] [NEW] Create guest failed on xen-hypervisor on Ubuntu 20.04
Public bug reported: Environment: Host OS :Ubuntu20.04 Host kernel:5.4.0-29-generic xen version:4.11.4-pre Bug detailed description: -- Create guest failed on xen-hypervisor on Ubuntu 20.04 Reproduce steps: 1. Boot up with OS with xen-hypervisor 2. Create a guest with a normal config builder= "hvm" name= "hvm_guest" memory = 8192 vcpus=4 disk = [ '/root/images/rhel7.qcow,qcow2,xvda,rw' ] device_model_override = '/usr/local/lib/xen/bin/qemu-system-i386' device_model_version = 'qemu-xen' Current result: create guest failed Expected result: create guest pass error log: root@clx-2s1:/home/img# xl create test.conf Parsing config from test.conf libxl: error: libxl_dm.c:2426:device_model_spawn_outcome: Domain 1:domain 1 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1563:domcreate_devmodel_started: Domain 1:device model did not start: -3 libxl: error: libxl_dm.c:2541:kill_device_model: Device Model already exited libxl: error: libxl_domain.c:1034:libxl__destroy_domid: Domain 1:Non-existant domain libxl: error: libxl_domain.c:993:domain_destroy_callback: Domain 1:Unable to destroy guest libxl: error: libxl_domain.c:920:domain_destroy_cb: Domain 1:Destruction of domain failed ** Affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880825 Title: Create guest failed on xen-hypervisor on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1880825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880394] Re: 20.10 iso syslinux menu screen unreadable
** Changed in: gfxboot-theme-ubuntu (Ubuntu) Status: Fix Released => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880394 Title: 20.10 iso syslinux menu screen unreadable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gfxboot-theme-ubuntu/+bug/1880394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879272] Re: corrupted json payload when adding a device
Test worked for me as well, thanks Andreas for the fast test on your side as well. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879272 Title: corrupted json payload when adding a device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1879272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880826] [NEW] trying to repair file system from original install system instalion failure...wasnt allow to both pick repair and reformat teh EFI partition back to efi from fat 32....which it wen
Public bug reported: I was getting a btfs loading system hang whe I tried to do a recovery from the uefi boot options but it just wouldnt happen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Wed May 27 00:21:30 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880826 Title: trying to repair file system from original install system instalion failure...wasnt allow to both pick repair and reformat teh EFI partition back to efi from fat 32which it went to for some reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1880826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879981] Re: touchpad does't work properly
Could you follow the instruction below to update the latest kernel? 1. Goto https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc7/ 2. Download these files: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc7/linux-headers-5.7.0-050700rc7_5.7.0-050700rc7.202005242331_all.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc7/linux-headers-5.7.0-050700rc7-generic_5.7.0-050700rc7.202005242331_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc7/linux-image-unsigned-5.7.0-050700rc7-generic_5.7.0-050700rc7.202005242331_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc7/linux-modules-5.7.0-050700rc7-generic_5.7.0-050700rc7.202005242331_amd64.deb 3. Put them into the same folders, and then run: sudo dpkg -i *.deb 4. Reboot After installing the v5.7-rc7, please retest your touchpad, to see whether it works or not? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879981 Title: touchpad does't work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880739] Re: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1
Yes, it did and authorized applications. https://i.imgur.com/M7AR39W.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
Which kernel would you like me to test with that parameter? The drm-tip one, or the regular Ubuntu 20.04 one (v5.4)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879272] Re: corrupted json payload when adding a device
** Changed in: gpsd (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879272 Title: corrupted json payload when adding a device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1879272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880739] Re: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1
Hmm, seems it got lost somewhere. Can you please try again? apport-collect 1880739 ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880629] Re: Ubuntu 20.04: Titlebar buttons on the Left not working properly; titlebar disappears in Tweaks app
** Package changed: gnome-tweak-tool (Ubuntu) => gnome-tweaks (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880629 Title: Ubuntu 20.04: Titlebar buttons on the Left not working properly; titlebar disappears in Tweaks app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1880629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880586] Re: Serious regression (low FPS) in overview animation 3.36/20.024
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880586 Title: Serious regression (low FPS) in overview animation 3.36/20.024 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880394] Re: 20.10 iso syslinux menu screen unreadable
@ Jean-Baptiste Lallement, Please explain what you mean by 'opinion': - Are you not affected by this bug? - Do you think that we should live with this bug? - Should we wait a few more days to let the bug-fix reach the iso files? - Or something else (in this case please specify)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880394 Title: 20.10 iso syslinux menu screen unreadable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gfxboot-theme-ubuntu/+bug/1880394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880394] Re: 20.10 iso syslinux menu screen unreadable
sorry, wrong bug. ** Changed in: gfxboot-theme-ubuntu (Ubuntu) Status: Opinion => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880394 Title: 20.10 iso syslinux menu screen unreadable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gfxboot-theme-ubuntu/+bug/1880394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880394] Re: 20.10 iso syslinux menu screen unreadable
Main Ubuntu ISO confirmed as still being broken. ** Attachment added: "Main ubuntu corrupt menu" https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1880394/+attachment/5377261/+files/55e52d41f8.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880394 Title: 20.10 iso syslinux menu screen unreadable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gfxboot-theme-ubuntu/+bug/1880394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880824] Re: Crashes when dragging items out of Budgie's task icon list
Please try 20.04 to see if its reproducible. Thx ** Changed in: budgie-desktop (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880824 Title: Crashes when dragging items out of Budgie's task icon list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1880824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879116] Re: Keyboard doesn't work on desktop
*** This bug is a duplicate of bug 1855711 *** https://bugs.launchpad.net/bugs/1855711 ** Package changed: gnome-tweak-tool (Ubuntu) => gnome-shell-extension- desktop-icons (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879116 Title: Keyboard doesn't work on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1879116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880830] [NEW] deja-dup failing with gpg read errors
Public bug reported: Starting a couple weeks ago, backups have begun failing with the following message. Until now, I have had no problems with backups; I backup via ssh to a cloud provider. (Until ~6 months ago I was backing up via ssh to a machine on my local net.) The scheduled backup asks for my ssh key passphrase and backup encryption passphrase as normal, but a few minutes later this error is displayed. The mounted ssh filesystem is visible in Nautilus and looks normal to me. GPGError: GPG Failed, see log below: = Begin GnuPG log = gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect gpg: AES256 encrypted data gpg: encrypted with 1 passphrase gpg: block_filter 0x562ce7e1c020: read error (size=16008,a->size=16008) gpg: block_filter 0x562ce7e1ccc0: read error (size=15992,a->size=15992) gpg: WARNING: message was not integrity protected gpg: block_filter: pending bytes! gpg: block_filter: pending bytes! = End GnuPG log = ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: deja-dup 40.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 27 00:27:14 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2016-04-15 (1503 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 SourcePackage: deja-dup UpgradeStatus: Upgraded to eoan on 2020-01-01 (147 days ago) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880830 Title: deja-dup failing with gpg read errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1880830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879116] Re: Keyboard doesn't work on desktop
*** This bug is a duplicate of bug 1855711 *** https://bugs.launchpad.net/bugs/1855711 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1855711, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1855711 Add keyboard navigation -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879116 Title: Keyboard doesn't work on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1879116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700811] Re: GNOME Tweak Tool hangs on startup on Artful
BTW, the correct package for more recent releases is 'gnome-tweaks'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700811 Title: GNOME Tweak Tool hangs on startup on Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweak-tool/+bug/1700811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845797] Re: Microphone not detected Lenovo Yoga S940
Can you please attach dmesg for both 5.4.0-29-generic and 5.4.0-31-generic? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845797 Title: Microphone not detected Lenovo Yoga S940 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
Both are fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700811] Re: GNOME Tweak Tool hangs on startup on Artful
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-tweak-tool (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700811 Title: GNOME Tweak Tool hangs on startup on Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweak-tool/+bug/1700811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880739] Re: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1
apport information ** Tags added: apport-collected ** Description changed: Till yesterday, it was working fine. But today after reboot, night light failed to start. I tried turning Night Light off/on but nothing seemed to work. - Unfortunately, I don't know what the previous version of mutter was - installed. + Unfortunately, I don't know what the previous version of mutter was installed. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-05-04 (22 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 + RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 + Tags: focal + Uname: Linux 5.4.0-31-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1880739/+attachment/5377267/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard
There still one problem. When I plug in the headphones (with 3 pins no-mic or 4 pins with mic) it switches the Input to "Microphone (plugged-in)" and strangely enough there is no sound at all on the headphones. If I change the microphone setting to anything "Internal Microphone (plugged in)" or the "Headset Microphone (plugged-in)" I get sound on the headphones -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876065 Title: After unplug headphones and plug them again no sound can be heard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880739] Re: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1
No worries. I did it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873996] Re: DevTools does not open at 84.0.4115.5
Yes indeed, feel free to close it. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873996 Title: DevTools does not open at 84.0.4115.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1873996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880739] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1880739/+attachment/5377269/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880739] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1880739/+attachment/5377268/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880739] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1880739/+attachment/5377271/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875864] Re: Flickr upload authentication fails in Shotwell 0.28
Hi Brian, thanks for the update. I used Software Boutique to add 'proposed' source. Running "sudo apt-get install shotwell" pulled the new version, along with shotwell-common. Shotwell now correctly logs into flikr and is able to upload photos and videos. Many thanks. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875864 Title: Flickr upload authentication fails in Shotwell 0.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1875864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872652] Re: reuseport_bpf_cpu in net from ubuntu_kernel_selftests failed on X-4.15 / B-5.3 PowerPC
Can be found on B-4.15 Power8 as well ** Tags added: bionic sru-20200518 ** Summary changed: - reuseport_bpf_cpu in net from ubuntu_kernel_selftests failed on X-4.15 / B-5.3 PowerPC + reuseport_bpf_cpu in net from ubuntu_kernel_selftests failed on 4.15 / 5.3 PowerPC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872652 Title: reuseport_bpf_cpu in net from ubuntu_kernel_selftests failed on 4.15 / 5.3 PowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880513] Re: Battery status indicator is wrong
** Package changed: ubuntu => gnome-shell (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880513 Title: Battery status indicator is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880739] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1880739/+attachment/5377270/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
please keep an eye on freezes after random time, for me "nomodeset" do not fix freezes during operation especially in battery mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574882] Re: Jing dependencies (java runtime, batik, avalon-framework)
The "No java runtime was found" warning disappeared. Likely corrected upstream since 2016. I realise today that installing libbatik-java and libavalon-framework- java packages in Ubuntu makes the two other warnings disappear too. I suppose that these warnings a related to the contents of the schema and that they are not present for everybody, but this is not easy to understand for an occasional, non professional user of jing and of RelaxNG. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574882 Title: Jing dependencies (java runtime, batik, avalon-framework) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1574882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up
** Package changed: grub (Ubuntu) => grub2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880663 Title: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1880663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880513] Re: Battery status indicator is wrong
Please attach a screenshot of the problem and run this command to send us more information about the system: apport-collect 1880513 ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880513 Title: Battery status indicator is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880832] [NEW] [SRU] accept wslu 2.3.6 to all current supported reelases
Public bug reported: [Impact] The package is already released in focal/groovy but it still affects eoan/bionic/xenial, a SRU is needed. [Test Case] * Install the package in Ubuntu on WSL and observe the following bug being solved: #1871986, #1869878, #1859509, #1857426 [Regression Potential] * There is a issue on #1877016 which is already addressed in the next release, but I hope to SRU the current packages in order to prevent future issues when SRUing. ** Affects: wslu (Ubuntu) Importance: Undecided Status: New ** Affects: wslu (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: wslu (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: wslu (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: wslu (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880832 Title: [SRU] accept wslu 2.3.6 to all current supported reelases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1880832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880513] Re: Battery status indicator is wrong
Before you take a screenshot please open the 'Power Statistics' app and include the battery information from that window in the same screenshot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880513 Title: Battery status indicator is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU
@lurii, Looks like the 1st error is "sof-audio-pci :00:1f.3: error: codec #0 probe error, ret: -2", so it means it fails to initialize your analogue codec driver. I never met this issue before, could you please add dmic_detect=0 to make sure audio works, then generate an alsa-info.txt and upload here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877757 Title: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872074] Re: unable to load VPN connection editor
Had the same problem. Same fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872074 Title: unable to load VPN connection editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1872074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880572] Re: package systemd-timesyncd 245.4-4ubuntu3.1 failed to install/upgrade: package systemd-timesyncd is already installed and configured
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dpkg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880572 Title: package systemd-timesyncd 245.4-4ubuntu3.1 failed to install/upgrade: package systemd-timesyncd is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1880572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880835] [NEW] pulse audio hangs in kernel call
Public bug reported: there is no audio device accessible any more and pulse-audio process can not be terminated in kernel log there is such a output: This makes the complete audio unstable in the laptop. I think it is started to happen when I installed Nvidia driver and there is an external monitor attached with DP audio device. [ 364.150644] INFO: task pulseaudio:2183 blocked for more than 120 seconds. [ 364.150646] Tainted: P OE 5.4.0-31-generic #35-Ubuntu [ 364.150647] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 364.150647] pulseaudio D0 2183 2175 0x4120 [ 364.150649] Call Trace: [ 364.150653] __schedule+0x2e3/0x740 [ 364.150655] ? dma_pte_clear_level+0x142/0x190 [ 364.150655] schedule+0x42/0xb0 [ 364.150656] schedule_timeout+0x203/0x2f0 [ 364.150657] wait_for_completion+0xb1/0x120 [ 364.150659] ? wake_up_q+0x70/0x70 [ 364.150663] fw_run_transaction+0xdc/0x110 [firewire_core] [ 364.150665] ? fw_core_handle_bus_reset+0x440/0x440 [firewire_core] [ 364.150666] ? free_iova_fast+0x18/0x30 [ 364.150667] ? close_transaction+0x110/0x110 [firewire_core] [ 364.150668] ? intel_unmap+0xd9/0x1c0 [ 364.150670] ? transmit_phy_packet_callback+0x20/0x20 [firewire_core] [ 364.150671] snd_fw_transaction+0xbc/0x110 [snd_firewire_lib] [ 364.150673] ? avc_general_get_plug_info+0x100/0x100 [snd_firewire_lib] [ 364.150674] pcr_modify+0x65/0x100 [snd_firewire_lib] [ 364.150675] cmp_connection_break+0x37/0x50 [snd_firewire_lib] [ 364.150677] snd_oxfw_stream_start_duplex+0x1ee/0x2e0 [snd_oxfw] [ 364.150678] ? wait_woken+0x80/0x80 [ 364.150679] pcm_capture_prepare+0x26/0x50 [snd_oxfw] [ 364.150682] snd_pcm_do_prepare+0x1e/0x30 [snd_pcm] [ 364.150684] snd_pcm_action_single+0x3c/0x80 [snd_pcm] [ 364.150686] snd_pcm_action_nonatomic+0x6e/0x80 [snd_pcm] [ 364.150687] snd_pcm_prepare+0x6a/0x90 [snd_pcm] [ 364.150689] snd_pcm_common_ioctl+0x28c/0xc00 [snd_pcm] [ 364.150691] snd_pcm_ioctl+0x27/0x40 [snd_pcm] [ 364.150692] do_vfs_ioctl+0x407/0x670 [ 364.150694] ? __secure_computing+0x42/0xe0 [ 364.150694] ksys_ioctl+0x67/0x90 [ 364.150695] __x64_sys_ioctl+0x1a/0x20 [ 364.150697] do_syscall_64+0x57/0x190 [ 364.150698] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 364.150699] RIP: 0033:0x7f0bbfa1a37b [ 364.150701] Code: Bad RIP value. [ 364.150701] RSP: 002b:7ffed915d308 EFLAGS: 0202 ORIG_RAX: 0010 [ 364.150702] RAX: ffda RBX: 5607c7b63de0 RCX: 7f0bbfa1a37b [ 364.150703] RDX: RSI: 4140 RDI: 006e [ 364.150703] RBP: 5607c7b63bb0 R08: R09: 1000 [ 364.150703] R10: 0004 R11: 0202 R12: 5607c7b63de0 [ 364.150704] R13: 7ffed915d6f0 R14: R15: 7ffed915d480 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 10:07:13 2020 InstallationDate: Installed on 2020-02-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) MachineType: Dell Inc. Precision 7540 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=UUID=7a5890f6-2724-480a-8fa7-778d07cd929d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0T2FXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd03/12/2020:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0T2FXT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880835 Title: pulse audio hangs in kernel call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880834] [NEW] qeth: utilize virtual MAC for Layer2 OSD devices
Public bug reported: ---Problem Description--- qeth on a DPM-managed IBM Z machine does not obtain its MAC Address for L2 OSD interfaces from the OSA Network Adapter. Instead it uses a random MAC Address. This causes connectivity issues in setups where a reliable & pre-determined MAC Address is required - ie. when doing network configuration via DHCP. ---uname output--- Ubuntu 18.04 / vmlinuz-4.15.0-101-generic Machine Type = IBM z14 GA2 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- - Bring up a qeth L2 OSD interface in DPM-managed LPAR. - Inspect the interface's MAC Address. It should be the same as displayed in the DPM Panels. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Attach sysctl -a output output to the bug. Backport of "s390/qeth: improve fallback to random MAC address" Backport of "s390/qeth: utilize virtual MAC for Layer2 OSD devices" This ticket is for 18.04 only. Already available with 20.04 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-185982 severity-high targetmilestone-inin18044 ** Tags added: architecture-s39064 bugnameltc-185982 severity-high targetmilestone-inin18044 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880834 Title: qeth: utilize virtual MAC for Layer2 OSD devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880739] Re: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880739 Title: Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878596] Comment bridged from LTC Bugzilla
--- Comment From thorsten.di...@de.ibm.com 2020-05-27 04:05 EDT--- (In reply to comment #23) > First of all thanks for sharing the additional information. > I would assume that things worked for you on such a special disk by > coincidence - such DASDs are not tested nor supported by subiquity or d-i. > We only use and test on standard 3390 models (like 9, 27, 54 etc.) and work > for FBA is underway. > Can you share on how you define such a 3390 MOD60 (60 * MOD1) on zVM (incl. > user direct and the dasdfmt command with the options you've used) - and > which z/VM release you are using? Since I'm not aware about such kind of > DASD definitions... > > I 'think' CPFMTXA shouldn't be needed for Linux (just for CMS disks) - for > Linux only dasdfmt (with cdl) is needed in case of DASD ECKD storage. > > Regarding the parmfile - well, the parmfile is not generally limited to 80 > characters, but on z/VM CMS the standard file with 80 chars is the > limitation. But that shouldn't be a problem, since you can just proceed with > the next line after you reached 80 characters - the linux kernel treats it > all as one long line (I think the max is about 11 lines in total). Make sure > you don't have unwanted spaces inside of your arguments - in case one > argument spans multiple lines. > It's best to start a new line if an argument doesn't fit into the existing > line - just to avoid problems. > In case one single argument itself is longer than 80 characters, well, you > have to proceed with the next line. In this case the tooling is a bit > tricky, since xedit shows by default the command prefix on the very left > which 'eats up' some characters - I suggest to disable it to see the entire > 80 characters (prefix off | on). IMO and IIRC any type of 3390 DASD should be usable, regardless of having multiple 3390-Mod1 capacity or just specified cylinders. We also test 3390-ModA EAV and EAV-II DASDs with 771062 Mod1 multiples. The Volume Labael LX0200 is suspicious. IIRC it indicates, that this DASD has been LDL formatted, and often installers can not handle LDL- formatted DASDs, because there is only a single partition that can not be changed. Please destroy the formatting of the DASD, either by using a CMS tool like CPFMTXA or (under linux) dasdfmt (if you terminate dasdfmt, the format is destroyed) - or do a manual dasdfmt with default parameters, which will use cdl formatting (instead of ldl), and use blocksize 4096. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878596 Title: [Ubuntu 20.04] - Install - problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1878596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
I confirm the same issue. This issue occurs after a kernel update from 4.15.0 to 5.3.0.51 and keeps up to current kernel 5.3.0.53. reset to Kernel 4.15.0 can solve the problem. Release: Linux Mint 19.3 Tricia CPU: AMD Ryzen 7 2700X Motherboard: Gigabyte AX370-Gaming K5 GPU: Radeon vega 64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876902] Re: subiquity crashed on entering help menu after upgrade
** Changed in: subiquity (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876902 Title: subiquity crashed on entering help menu after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1876902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879949] Re: Can not log in
Is there information you still need? I found out, that when stuck in the login screen I can switch to another tty. There I can login without a gui. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879949 Title: Can not log in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880834] Re: qeth: utilize virtual MAC for Layer2 OSD devices
** Also affects: ubuntu-z-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880834 Title: qeth: utilize virtual MAC for Layer2 OSD devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1880834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880832] Re: [SRU] accept wslu 2.3.6 to all current supported reelases
** Changed in: wslu (Ubuntu) Status: New => Fix Released ** Summary changed: - [SRU] accept wslu 2.3.6 to all current supported reelases + [SRU] accept wslu 2.3.6 to all current supported releases -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880832 Title: [SRU] backport wslu 2.3.6-0ubuntu1 to all current supported releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1880832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880837] [NEW] remake for GNU Make 4.3 is available
Public bug reported: GNU Make 4.3 is a fairly signification release. And version 1.5 of remake has a few features, like `--search-parent` (`-c` that I use on a daily basis and I suspect many others will as well. Also, I looked at the Debian make for this and it is in major need of overhaul. ** Affects: remake (Ubuntu) Importance: Undecided Status: New ** Description changed: GNU Make 4.3 is a fairly signification release. And version 1.5 of remake has a few features, like `--search-parent` - (`-c`0 that I use on a daily basis and I suspect many others will as + (`-c` that I use on a daily basis and I suspect many others will as well. + + + Also, I looked at the Debian make for this and it is in major need of overhaul. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880837 Title: remake for GNU Make 4.3 is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remake/+bug/1880837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876882] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/20.0.4-2ubuntu1~18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876882 Title: Backport packages for 18.04.5 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1876882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866041] Re: 53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim resulted in ALLOW on 4.4 / 4.15 non-amd64
Didn't see this on Xenial AMD64 / i386 / P8 / s390x (ARM64 blacklisted) 4.4.0-180.210 ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866041 Title: 53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim resulted in ALLOW on 4.4 / 4.15 non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866041] Re: 53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim resulted in ALLOW on 4.4 / 4.15 non-amd64
Didn't see this on Bionic AMD64 / i386 / P8, P9 / s390x (ARM64 blacklisted) 4.15.0-102.103 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866041 Title: 53-sim-binary_tree from ubuntu_seccomp failed with FAILURE bpf_sim resulted in ALLOW on 4.4 / 4.15 non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880832] Re: [SRU] accept wslu 2.3.6 to all current supported releases
** Description changed: [Impact] The package is already released in focal/groovy but it still affects eoan/bionic/xenial, a SRU is needed. [Test Case] - * Install the package in Ubuntu on WSL and observe the following bug being solved: - - #1871986, #1869878, #1859509, #1857426 + * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates + * Run the autopktest in a WSL environment where the user name contains space. + * Verify the other individual bugs fixed by the SRU. [Regression Potential] * There is a issue on #1877016 which is already addressed in the next release, but I hope to SRU the current packages in order to prevent future issues when SRUing. ** Changed in: wslu (Ubuntu) Status: Fix Released => New ** Summary changed: - [SRU] accept wslu 2.3.6 to all current supported releases + [SRU] backport wslu 2.3.6-0ubuntu1 to all current supported releases -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880832 Title: [SRU] backport wslu 2.3.6-0ubuntu1 to all current supported releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1880832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880835] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880835 Title: pulse audio hangs in kernel call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+attachment/5377303/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: gnome-shell freezes randomly on nouveau and wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880834] Re: qeth: utilize virtual MAC for Layer2 OSD devices
** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880834 Title: qeth: utilize virtual MAC for Layer2 OSD devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1880834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850904] Re: 36-sim-ipc_syscalls, 37-sim-ipc_syscalls_be from ubuntu_seccomp failed with X/B/D s390x / PPC
Didn't see this on X/B PPC. * 4.4.0-180.210 * 4.15.0-102.103 Looks like this has been fixed, closing this bug. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Disco) Status: Incomplete => Invalid ** Changed in: ubuntu-kernel-tests Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850904 Title: 36-sim-ipc_syscalls, 37-sim-ipc_syscalls_be from ubuntu_seccomp failed with X/B/D s390x / PPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1850904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
Thank you kindly. I was able to ssh into the machine and prepare a crash report from the gnome-shell process, I will upload that shortly, perhaps as a separate bug report. However, the real culprit might be located in the dmesg: ``` [12870.773176] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] [12870.773196] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery [12870.773220] nouveau :01:00.0: fifo: channel 6: killed [12870.773229] nouveau :01:00.0: fifo: engine 5: scheduled for recovery [12870.773234] nouveau :01:00.0: fifo: engine 0: scheduled for recovery [12870.773896] nouveau :01:00.0: systemd-logind[1312]: channel 6 killed! [12907.524710] GpuWatchdog[5838]: segfault at 0 ip 560accf3e4c9 sp 7f3ce9a516c0 error 6 in chrome[560ac8dd1000+7094000] [12907.524716] Code: 00 79 09 48 8b 7d c0 e8 05 28 2b fc c7 45 c0 aa aa aa aa 0f ae f0 41 8b 84 24 e0 00 00 00 89 45 c0 48 8d 7d c0 e8 e7 44 e9 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e [12922.616876] nouveau :01:00.0: Xwayland[2419]: failed to idle channel 4 [Xwayland[2419]] [12937.616723] nouveau :01:00.0: Xwayland[2419]: failed to idle channel 4 [Xwayland[2419]] [12937.616907] nouveau :01:00.0: fifo: fault 00 [READ] at 00013000 engine 07 [HOST0] client 07 [HUB/HOST_CPU] reason 02 [PTE] on channel 4 [007fa19000 Xwayland[2419]] [12937.616915] nouveau :01:00.0: fifo: channel 4: killed [12937.616917] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery [12937.616923] nouveau :01:00.0: fifo: engine 0: scheduled for recovery [12937.616941] nouveau :01:00.0: fifo: engine 5: scheduled for recovery [12937.616945] nouveau :01:00.0: Xwayland[2419]: channel 4 killed! [12937.735092] [ cut here ] [12937.735142] WARNING: CPU: 3 PID: 26055 at drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x6d/0x80 [nouveau] [12937.735142] Modules linked in: rfcomm aufs cmac algif_hash algif_skcipher af_alg bnep overlay binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua intel_rapl_msr mei_hdcp snd_hda_codec_hdmi intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm intel_cstate intel_rapl_perf iwlmvm mac80211 libarc4 snd_usb_audio snd_hda_codec_realtek serio_raw intel_wmi_thunderbolt uvcvideo rmi_smbus snd_hda_codec_generic snd_usbmidi_lib rmi_core snd_seq_midi snd_seq_midi_event wmi_bmof videobuf2_vmalloc iwlwifi videobuf2_memops videobuf2_v4l2 snd_rawmidi snd_hda_intel videobuf2_common snd_intel_dspcfg rtsx_pci_ms thinkpad_acpi btusb snd_hda_codec nvram videodev btrtl btbcm snd_hda_core input_leds memstick ledtrig_audio mc snd_seq btintel joydev cfg80211 snd_hwdep bluetooth snd_pcm snd_seq_device mei_me ecdh_generic ecc snd_timer mei intel_pch_thermal snd soundcore mac_hid sch_fq_codel cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress dm_crypt [12937.735161] raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nouveau rtsx_pci_sdmmc mxm_wmi aesni_intel crypto_simd i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt cryptd fb_sys_fops glue_helper drm e1000e psmouse ahci i2c_i801 rtsx_pci libahci wmi video [12937.735173] CPU: 3 PID: 26055 Comm: chrome Not tainted 5.4.0-31-generic #35-Ubuntu [12937.735174] Hardware name: LENOVO 20EN0005MS/20EN0005MS, BIOS N1EET87W (1.60 ) 12/06/2019 [12937.735194] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau] [12937.735196] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 48 89 45 e8 e8 71 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb f2 e8 ea f6 58 eb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 [12937.735196] RSP: 0018:b807c5f5fbc8 EFLAGS: 00010282 [12937.735197] RAX: fffe RBX: b807c5f5fbf8 RCX: [12937.735198] RDX: 0010 RSI: b807c5f5fb38 RDI: b807c5f5fbd8 [12937.735198] RBP: b807c5f5fbe8 R08: R09: [12937.735199] R10: 0030 R11: 9b7ac9c07e40 R12: b807c5f5fc30 [12937.735199] R13: 9b7ca4fff0b0 R14: R15: 9b7ac9c07e38 [12937.735200] FS: 7f3cfaa1db00() GS:9b7cac2c() knlGS: [12937.735201] CS: 0010 DS: ES: CR0: 80050033 [12937.735201] CR2: 560ad25fe010 CR3: 000842f0a004 CR4: 003606e0 [12937.735202] DR0: DR1: DR2: [12937.735202] DR3: DR6: fffe0ff0 DR7: 0400 [12937.735203] Call Trace: [12937.735265] nouveau_vma_del+0x75/0xc0 [nouveau] [12937.735316] nouveau_gem_object_close+0x1f5/0x210 [nouveau] [12937.735330] drm_gem_object_release_handle+0x35/0xa0 [drm] [12937.735337] drm_gem_handle_delete+0x59/0xa0 [drm] [12937.735344] ? drm_gem_handle_create+0x40/0x4
[Bug 1850904] Re: 36-sim-ipc_syscalls, 37-sim-ipc_syscalls_be from ubuntu_seccomp failed with X/B/D s390x / PPC
For comment #5, nor seeing this on s390x. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850904 Title: 36-sim-ipc_syscalls, 37-sim-ipc_syscalls_be from ubuntu_seccomp failed with X/B/D s390x / PPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1850904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880337] Re: Screen lock won't work
I've noticed that when the computer is idle, it tries to lock the screen, but a few seconds later, it returns to the desktop. There seems to be some process that prevents the screen lock when it occurs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880337 Title: Screen lock won't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423
You are right. It looks like a problem with the ActivKey device. I don't see what change could have created this regression. First, do not use virtual machine. They often make the things more complex to debug. Second, try to re-install a previous version of Ubuntu to check it was working fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879960 Title: pcscd doesn't support ActivKEy SIM B/N: 0945423 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879704] Re: [UBUNTU 20.04] s390x/pci: implement linking between PF and VF for multifunction devices
Thx for the update - yepp, found them in linux-next. So should be possible to address them with the upcoming kernel SRU ... ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: ubuntu-z-systems Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879704 Title: [UBUNTU 20.04] s390x/pci: implement linking between PF and VF for multifunction devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable
** Description changed: + [Impact] + + This affects all wslu tools on all releases. When PATH do not include + Windows path, the all tools will complain that reg.exe is not found. + + [Test Case] + + * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates + * Run the autopktest in a WSL environment where the user name contains space. + * Verify the other individual bugs fixed by the SRU. + + [Regression Potential] + + * For future release of wslu 3.1.0 proposed, huge refactoring will be + needed. + + [Original Bug Report] + ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable - $ wslfetch + $ wslfetch /usr/bin/wslfetch: line 108: reg.exe: command not found /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied - ./+o+- Windows 10 Linux Subsystem - y. 'yy+ rafaeldtinoco@lenovo - .;//+/h yyo BUILD: -.++ .:/++/-.`sss/` BRANCH: - .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS - o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft -.:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 6m - .++/+ +oo+o:` \sssooo; - /+++//+: oo+o - \+/+o+++ o++o ydddhh+ - .++.o+ +oo+:` /dddhhh; -.+.o+oo:. odd+ - \+.++o+o` -.:ohdh+ - `:o+++ oyo++os: -.o: .syhhh'.oo++o. -/osyyy.+++\ -` +oo+++o:/ - `oo++'` + ./+o+- Windows 10 Linux Subsystem + y. 'yy+ rafaeldtinoco@lenovo + .;//+/h yyo BUILD: + .++ .:/++/-.`sss/` BRANCH: + .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS + o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft + .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 6m + .++/+ +oo+o:` \sssooo; + /+++//+: oo+o + \+/+o+++ o++o ydddhh+ + .++.o+ +oo+:` /dddhhh; + .+.o+oo:. odd+ + \+.++o+o` -.:ohdh+ + `:o+++ oyo++os: + .o: .syhhh'.oo++o. + /osyyy.+++\ + ` +oo+++o:/ + `oo++'` After : echo $PATH /snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:. $ wslfetch - ./+o+- Windows 10 Linux Subsystem - y. 'yy+ rafaeldtinoco@lenovo - .;//+/h yyo BUILD:18363 -.++ .:/++/-.`sss/` BRANCH: 19h1_release - .:++o: `\/:---:/-RELEASE: Ubuntu 20.04 LTS - o:+o+:++. `'-/ooo+
[Bug 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU
@Hui Here is alsa-info.sh output with snd_hda_intel.dmic_detect=0 http://alsa-project.org/db/?f=a0666f31d648566f09d98d4ca79746a197403e28 With dmic_detect=0 internal speakers works but internal mic does not. External headset works fine both headphones and mic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877757 Title: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880840] [NEW] stress-ng reports null checksum region when stressor is killed before it invokes the stressor function
Public bug reported: When running on slow or memory constrained systems the bogo op sanity checking reports that the checksum region is null because the child has been killed before it can set this region up. This can be fixed by moving this setup into the parent before forking off the child because they use the same shared memory segment. ** Affects: stress-ng (Ubuntu) Importance: High Assignee: Colin Ian King (colin-king) Status: In Progress ** Changed in: stress-ng (Ubuntu) Importance: Undecided => High ** Changed in: stress-ng (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: stress-ng (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880840 Title: stress-ng reports null checksum region when stressor is killed before it invokes the stressor function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1880840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper
Maybe keep an eye on https://gitlab.gnome.org/GNOME/mutter/-/issues/1271 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1271 https://gitlab.gnome.org/GNOME/mutter/-/issues/1271 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423773 Title: Gnome-Shell don't free ram when I change a wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880841] [NEW] usr.sbin.nscd needs unix socket access to @userdb-*
Public bug reported: This concerns apparmor-profiles 2.13.3-7ubuntu5 in Ubuntu focal. I use the usr.sbin.nscd profile in enforce mode, and am seeing the following messages in /var/log/syslog . I don't know if the SIGABRT is related: May 27 04:39:56 test-ubuntu64 kernel: [ 199.392521] audit: type=1400 audit(1590568796.975:76): apparmor="DENIED" operation="bind" profile="nscd" pid=1679 comm="nscd" family="unix" sock_type="dgram" protocol=0 requested_mask="bind" denied_mask="bind" addr="@userdb-4a5d3fdcfb9afbd7fc75948800519358" May 27 04:40:17 test-ubuntu64 systemd[1]: nscd.service: Main process exited, code=killed, status=6/ABRT May 27 04:40:17 test-ubuntu64 systemd[1]: nscd.service: Failed with result 'signal'. May 27 04:40:17 test-ubuntu64 systemd[1]: nscd.service: Scheduled restart job, restart counter is at 9. The @userdb-* binding looks like a systemd thing. Should a rule for this go into /etc/apparmor.d/abstractions/nameservice ? ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880841 Title: usr.sbin.nscd needs unix socket access to @userdb-* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1880841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable
** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/384608 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877016 Title: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1877016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
Thanks. Yes if the nouveau kernel driver is crashing then it's quite possible the gnome-shell process will be frozen. Still, it would be interesting to know where in gnome-shell this happens. And to confirm they're the same issue or two coincidental ones. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: gnome-shell freezes randomly on nouveau and wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878005] Re: Chrony crashes on install from raspberry pi 2
Trying as-is on armhf: After install I see the reported fail: $ systemctl status chrony ● chrony.service - chrony, an NTP client/server Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled) Active: failed (Result: protocol) since Wed 2020-05-27 08:40:07 UTC; 1min 18s ago Docs: man:chronyd(8) man:chronyc(1) man:chrony.conf(5) May 27 08:40:06 ubuntu systemd[1]: Starting chrony, an NTP client/server... May 27 08:40:06 ubuntu chronyd[27223]: chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG) May 27 08:40:06 ubuntu chronyd[27223]: Initial frequency 11.023 ppm May 27 08:40:07 ubuntu systemd[1]: chrony.service: New main PID 27223 does not exist or is a zombie. May 27 08:40:07 ubuntu systemd[1]: chrony.service: Failed with result 'protocol'. May 27 08:40:07 ubuntu systemd[1]: Failed to start chrony, an NTP client/server. Trying the daemon directly: $ sudo chronyd -d -n -F 1 2020-05-27T08:43:29Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG) 2020-05-27T08:43:29Z Frequency 18.044 +/- 39.335 ppm read from /var/lib/chrony/chrony.drift Bad system call Installing the fix from proposed: Upgrade works: $ sudo apt install chrony Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: chrony 1 upgraded, 0 newly installed, 0 to remove and 17 not upgraded. Need to get 201 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main armhf chrony armhf 3.5-6ubuntu6.1 [201 kB] Fetched 201 kB in 0s (1241 kB/s) (Reading database ... 99010 files and directories currently installed.) Preparing to unpack .../chrony_3.5-6ubuntu6.1_armhf.deb ... Unpacking chrony (3.5-6ubuntu6.1) over (3.5-6ubuntu6) ... Setting up chrony (3.5-6ubuntu6.1) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.1) ... Now the process is fine $ systemctl status chrony ● chrony.service - chrony, an NTP client/server Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-05-27 08:47:50 UTC; 58s ago Docs: man:chronyd(8) man:chronyc(1) man:chrony.conf(5) Main PID: 28356 (chronyd) Tasks: 2 (limit: 4915) CGroup: /system.slice/chrony.service ├─28356 /usr/sbin/chronyd -F -1 └─28357 /usr/sbin/chronyd -F -1 May 27 08:47:50 ubuntu systemd[1]: Starting chrony, an NTP client/server... May 27 08:47:50 ubuntu chronyd[28356]: chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG) May 27 08:47:50 ubuntu chronyd[28356]: Frequency 18.044 +/- 39.335 ppm read from /var/lib/chrony/chrony.drift May 27 08:47:50 ubuntu chronyd[28356]: Loaded seccomp filter May 27 08:47:50 ubuntu systemd[1]: Started chrony, an NTP client/server. May 27 08:47:59 ubuntu chronyd[28356]: Selected source 131.188.3.220 When running directly no abort after seccomp filter is applied: $ sudo chronyd -d -n -F 1 2020-05-27T08:49:24Z chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG) 2020-05-27T08:49:24Z Frequency 14.709 +/- 17.455 ppm read from /var/lib/chrony/chrony.drift 2020-05-27T08:49:24Z Loaded seccomp filter 2020-05-27T08:49:33Z Selected source 131.188.3.220 Setting tags as being verified ** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878005 Title: Chrony crashes on install from raspberry pi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1878005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
If we're unable to solve this quickly then consider opening the 'Additional Drivers' app and installing the proprietary Nvidia driver... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: gnome-shell freezes randomly on nouveau and wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878005] Re: Chrony crashes on install from raspberry pi 2
FYI: The armhf test is known to be flaky, improved in groovy and retried in Bionic for this SRU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878005 Title: Chrony crashes on install from raspberry pi 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1878005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880840] Re: stress-ng reports null checksum region when stressor is killed before it invokes the stressor function
Fix committed: https://kernel.ubuntu.com/git/cking/stress- ng.git/commit/?id=8724ce7b630c8e284479adf977c8ea82a17b8d40 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880840 Title: stress-ng reports null checksum region when stressor is killed before it invokes the stressor function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1880840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
I've switched back to the 5.4 kernel and have enabled the 'nomodeset' parameter. The laptop has booted fine. I'll keep using it like this and let you know if I see another hang on boot. I've noticed that Wayland is no longer an option on the login screen. I presume this is an expected consequence of disabling modesetting. $ cat /proc/version Linux version 5.4.0-31-generic (buildd@lgw01-amd64-059) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 $ cat /proc/version_signature Ubuntu 5.4.0-31.35-generic 5.4.34 $ cat /etc/default/grub | grep GRUB_CMDLINE GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" GRUB_CMDLINE_LINUX="" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879692] Re: [SRU] Strongswan pki creates CA certificates with invalid Key Usage flags
I just tested the package from focal-proposed and generated a new CA certificate with correct Key-Extension Flags. This fixes the bug for me. See https://paste.ubuntu.com/p/z5pPDSZHHH/ ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879692 Title: [SRU] Strongswan pki creates CA certificates with invalid Key Usage flags To manage notifications about this bug go to: https://bugs.launchpad.net/strongswan/+bug/1879692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880774] Re: chronyd not synching time anymore since last update
Hi Thomas, Please attach the output of 'systemctl status chrony' and 'chronyc tracking'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880774 Title: chronyd not synching time anymore since last update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1880774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
Daniel thank you so much for being so supportive, I really appreciate it :) I have ran the command `ubuntu-bug /var/crash/_usr_bin_gnome- shell.1000.crash` which then opens a dialog; however when I press "Send" there's no follow-up - no browser tab opens. The contents of `_usr_bin_gnome-shell.1000.uploaded` says `93823806-9ff7-11ea- 9bb3-fa163e102db1` so maybe it's already there in your servers. From the dialog I see the following title: gnome-shell crashed with SIGABRT in __Gl___poll() (sorry copy-paste from the dialog doesn't work). And there is no rush - the computer crashes once per day or so, so it's definitely not that annoying; if it becomes an annoyance I'll install the proprietary driver as a workaround. Thanks again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: gnome-shell freezes randomly on nouveau and wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879692] Re: [SRU] Strongswan pki creates CA certificates with invalid Key Usage flags
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879692 Title: [SRU] Strongswan pki creates CA certificates with invalid Key Usage flags To manage notifications about this bug go to: https://bugs.launchpad.net/strongswan/+bug/1879692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880607] Re: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04
My cmdline.txt: root=LABEL=rpi4-root rootfstype=ext4 rootwait verbose nosplash console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 net.ifnames=0 dwc_otg.lpm_enable=0 dwc_otg.fiq_fix_enable=1 fsck.repair=yes My config.txt: [pi4] # Route interrupts to ARM cores using legacy interrupt controller (default: 0 = route via GIC-400) enable_gic=1 armstub=armstub8-gic.bin # Fix graphical glitches dtoverlay=vc4-fkms-v3d [all] # evade u-boot, just boot directly (vmlinuz has to be uncompressed!) kernel=vmlinuz initramfs initrd.img followkernel # boot in AArch64 (64-bit) mode arm_64bit=1 # GPU shared memory, default: 64 (too low might disable features) gpu_mem=32 # Energy Efficient Ethernet off dtparam=eee=off # Use red PWR LED for activity indicator dtparam=pwr_led_trigger=cpu # Use green ACT LED for MicroSD indicator dtparam=act_led_trigger=mmc0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880607 Title: Raspberry Pi 4 extremely slow file i/o after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880307] Re: Unsupported messages: MediaDice with emoticon field
** Also affects: telegram-desktop (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: telegram-desktop (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: telegram-desktop (Ubuntu Groovy) Status: New => Fix Released ** Changed in: telegram-desktop (Ubuntu Focal) Assignee: (unassigned) => Nicholas Guriev (mymedia) ** Changed in: telegram-desktop (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880307 Title: Unsupported messages: MediaDice with emoticon field To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1880307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879325] Re: Unable to remove disk metadata on vm
The extra change we need is now pushed upstream => https://libvirt.org/git/?p=libvirt.git;a=commit;h=55029d93150e33d70b02b6de2b899c05054c5d3a My PPA builds include this final version of the change and the initially referred fix for the warning. Waiting for MP review by the team now. @Riccardo - this certainly fixes "an issue" I'd still be happy to hear from you if that also fixes your CI fails. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879325 Title: Unable to remove disk metadata on vm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1879325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876741] Re: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
Hi Maria, I don't think your issue is the same I got. Note that my problem happened with or without the dock, and I wasn't even reaching grub. That's the big difference here. If you lose the video after grub, than your problem is elsewhere, and my suggestion is to boot without "quiet splash" on the grup command line, so that you can see where the boot is stuck. If it reaches the end of the boot process and it is just unable to start X (so GDM, LightDM or whatever), then your problem might be related to the drivers, maybe not blacklisting nouveau or things like these. Maybe as suggested elsewhere [1], you just need to uninstall the buggy xserver-xorg-video-intel package. What is more important here is that my problem got solved by setting the "Set Optimized" option in the BIOS to true. This solved a huge amount of problems, the last one I'm waiting to solve before closing this bug is to understand how to boot without a customized /etc/X11/xorg.conf. Hope this helps. [1] https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879484 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879325] Re: Unable to remove disk metadata on vm
** Description changed: [Impact] - * The impact is log flooding with warnings for every guest start/stop + * The impact is log flooding with warnings for every guest start/stop - * Maybe the impact also has in some cases worse effects due to the bad RC -of the function e.g. blocking other actions - that could be happening in -the CI run it was reported with. + * Maybe the impact also has in some cases worse effects due to the bad RC + of the function e.g. blocking other actions - that could be happening in + the CI run it was reported with. - * Upstream has added a fix and this is backporting it (applies cleanly as- -is) + * Upstream has added a fix that fixes the warning. +We worked on and upstreamed another fix that also corrects the internal +error we were seeing. +Both are easily backportd and apply as-is. [Test Case] - * Run this in one console - $ journalctl -f -u libvirtd | grep -i meta - * and in the other spawn a guest (e.g. via uvtool-libvirt or any other) -and shut it down. Shutdown will pass qemuBlockRemoveImageMetadata -> -qemuSecurityMoveImageMetadata ... which will trigger the issue. + * Run this in one console + $ journalctl -f -u libvirtd | grep -i meta + * In the other console spawn a guest (e.g. via uvtool-libvirt or +any other and shut it down. Shutdown will pass: + qemuBlockRemoveImageMetadata -> + qemuSecurityMoveImageMetadata +... which will trigger the issue. -Without a fix the log will all the time get an entry like: + Without a fix the log will all the time get an entry like: Mai 20 07:10:12 Keschdeichel libvirtd[2638]: this function is not supported by the connection driver: virSecurityManagerMoveImageMetadata Mai 20 07:10:12 Keschdeichel libvirtd[2638]: internal error: child reported (status=125): this function is not supported by the connection driver: virSecurityManagerMoveImageMetadata Mai 20 07:10:12 Keschdeichel libvirtd[2638]: Unable to remove disk metadata on vm focal from /var/lib/uvtool/libvirt/images/focal.qcow (disk target vda) Mai 20 07:10:12 Keschdeichel libvirtd[2638]: this function is not supported by the connection driver: virSecurityManagerMoveImageMetadata Mai 20 07:10:12 Keschdeichel libvirtd[2638]: internal error: child reported (status=125): this function is not supported by the connection driver: virSecurityManagerMoveImageMetadata Mai 20 07:10:12 Keschdeichel libvirtd[2638]: Unable to remove disk metadata on vm focal from /var/lib/uvtool/libvirt/images/x-uvt-b64-Y29tLnVidW50dS5jbG91ZC5kYWlseTpzZXJ2ZXI6MjAuMDQ6YW1kNjQgMjAyMDAzMjk= (disk target vda) Mai 20 07:10:12 Keschdeichel libvirtd[2638]: this function is not supported by the connection driver: virSecurityManagerMoveImageMetadata Mai 20 07:10:12 Keschdeichel libvirtd[2638]: internal error: child reported (status=125): this function is not supported by the connection driver: virSecurityManagerMoveImageMetadata Mai 20 07:10:12 Keschdeichel libvirtd[2638]: Unable to remove disk metadata on vm focal from /var/lib/uvtool/libvirt/images/focal-ds.qcow (disk target vdb) - [Regression Potential] - * It is a check on a function that doesn't need to exist for apparmor. -Hence making that check not a fail does not have a huge regression -potential - it is not that "now" it would do more. It just no more -complains about it and thereby avoids log flooding. + * It is a check on a function that doesn't need to exist for apparmor. + Hence making that check not a fail does not have a huge regression + potential - it is not that "now" it would do more. It just no more + complains about it and thereby avoids log flooding. +Regressions could happen if we'd have silenced other warnings by that, +but I don't see that in code or tests. + * The other change converts a bad RC into a good RC for a given set of +condition that applies either when built without libattr or when working +on an FS that does not support XATTR. +The same change of behavior we have in Ubuntu (built without libattr) +would now also be dependent on the FS type (no error on such FS +anymore). But that isn't true for Ubuntu builds and therefore doesn't +matter for the SRU considerations. +A regression could be if there would be another low level fail that is +mis-detected and masked to be "ok" by the code. But the API is rather +clear on -1 = fail, -2 = the kind we mask 0 = ok. So this seems not to +be an issue. + [Other Info] - - * n/a + * n/a --- - We can reproduce this 100% in our CI (upstream Openstack Ironic) using Ubuntu 20.04 LTS Focal Fossa with libvirt 6.0.0 2020-05-15 10:05:50.626+: 96089: error : virSecurityManagerMoveImageMetadata:476 : this function is not supported by the connection driver: virSecurityManagerMoveImageMetadata 2020-05-15 10:05:50.628+: 96089: error :
[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland
Thanks, that worked: https://errors.ubuntu.com/oops/93823806-9ff7-11ea-9bb3-fa163e102db1 but I can't see any interesting functions blocking in any of the threads. Let's skip that and just make this about the nouveau kernel crash. ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - gnome-shell freezes randomly on nouveau and wayland + Kernel crash in nouveau with Wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878166 Title: Kernel crash in nouveau with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878937] Re: [MIR] mathjax
** Changed in: mathjax (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878937 Title: [MIR] mathjax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mathjax/+bug/1878937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880850] [NEW] Ubuntu 20.04 keyboard doesn't work in desktop
Public bug reported: Hi, I can see that none of the keyboard keys works while I'm on the desktop. I've to use my mouse to open (copy, paste, see properties) the file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 15:25:32 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-04 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880850 Title: Ubuntu 20.04 keyboard doesn't work in desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
