[Bug 1850651] Re: [SRU] Authentication constantly re-requested for Google
bionic (18.04 LTS) was fixed mid-January, disco (19.04) and xenial (16.04 LTS) have the updated versions (minor fix version https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/) still stuck in proposed since end of November. ** Changed in: thunderbird (Ubuntu Eoan) Status: Fix Committed => Fix Released ** Changed in: thunderbird (Ubuntu Bionic) 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/1850651 Title: [SRU] Authentication constantly re-requested for Google To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1850651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864300] Re: Bump RawTherapee to 5.8
This bug was fixed in the package rawtherapee - 5.8-1 --- rawtherapee (5.8-1) unstable; urgency=medium * New upstream release (closes: #951841; LP: #1864300). * Update copyright info in d/copyright. * Bump Standards-Version to 4.5.0 (no changes necessary). * Declare 'Rules-Requires-Root: no' in d/control. -- Philip Rinn Sun, 23 Feb 2020 23:08:48 +0100 ** Changed in: rawtherapee (Ubuntu) Status: New => 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/1864300 Title: Bump RawTherapee to 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rawtherapee/+bug/1864300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859316] Re: Can't find the lazarus executable /usr/lib/lazarus/2.0.6/lazarus
I don't see errors during install in /var/log/apt/history.log or /var/log/apt/term.log should I look elsewhere? This is the list of my /usr/lib/lazarus/2.0.6 corrado@corrado-p3-ff-0217:~$ ls /usr/lib/lazarus/2.0.6 -R /usr/lib/lazarus/2.0.6: components docs examples languages startlazarus /usr/lib/lazarus/2.0.6/components: chmhelp /usr/lib/lazarus/2.0.6/components/chmhelp: lhelp /usr/lib/lazarus/2.0.6/components/chmhelp/lhelp: lhelp /usr/lib/lazarus/2.0.6/examples: codepageconverter designerbaseclass dockmanager idehelp pascalstream codetools designnonlcl exploremenu idequickfix xmlresource /usr/lib/lazarus/2.0.6/examples/codepageconverter: filefind /usr/lib/lazarus/2.0.6/examples/codepageconverter/filefind: filefindlaz.lpk /usr/lib/lazarus/2.0.6/examples/codetools: jumptoimplementation /usr/lib/lazarus/2.0.6/examples/codetools/jumptoimplementation: jumptoimplementation.lpk /usr/lib/lazarus/2.0.6/examples/designerbaseclass: designbaseclassdemopkg.lpk /usr/lib/lazarus/2.0.6/examples/designnonlcl: notlcldesigner.lpk /usr/lib/lazarus/2.0.6/examples/dockmanager: package /usr/lib/lazarus/2.0.6/examples/dockmanager/package: easydockmgr.lpk /usr/lib/lazarus/2.0.6/examples/exploremenu: exploreidemenu.lpk /usr/lib/lazarus/2.0.6/examples/idehelp: demoidehelp.lpk /usr/lib/lazarus/2.0.6/examples/idequickfix: quickfixexample.lpk /usr/lib/lazarus/2.0.6/examples/pascalstream: CopyAsPasPkg /usr/lib/lazarus/2.0.6/examples/pascalstream/CopyAsPasPkg: copyformaspascaldemopkg.lpk /usr/lib/lazarus/2.0.6/examples/xmlresource: xmlresource.lpk /usr/lib/lazarus/2.0.6/languages: debuggerstrconst.es.po lazaruside.af_ZA.po lazaruside.ja.po debuggerstrconst.fr.po lazaruside.ar.po lazaruside.lt.po debuggerstrconst.hu.po lazaruside.ca.po lazaruside.nl.po debuggerstrconst.it.po lazaruside.cs.po lazaruside.pl.po debuggerstrconst.ja.po lazaruside.de.po lazaruside.po debuggerstrconst.lt.po lazaruside.es.po lazaruside.pt_BR.po debuggerstrconst.polazaruside.fi.po lazaruside.ru.po debuggerstrconst.pt_BR.po lazaruside.fr.po lazaruside.sk.po debuggerstrconst.ru.po lazaruside.he.po lazaruside.tr.po debuggerstrconst.tr.po lazaruside.hu.po lazaruside.uk.po debuggerstrconst.uk.po lazaruside.id.po lazaruside.zh_CN.po debuggerstrconst.zh_CN.po lazaruside.it.po README.txt corrado@corrado-p3-ff-0217:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859316 Title: Can't find the lazarus executable /usr/lib/lazarus/2.0.6/lazarus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lazarus/+bug/1859316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832915] Comment bridged from LTC Bugzilla
--- Comment From harih...@in.ibm.com 2020-02-24 02:11 EDT--- root@ws-g48-2d81-host:~# uname -a Linux ws-g48-2d81-host 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:13 UTC 2020 ppc64le ppc64le ppc64le GNU/Linux root@ws-g48-2d81-host:~# cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Focal Fossa (development branch)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal root@ws-g48-2d81-host:~# service numad status ? numad.service - numad - The NUMA daemon that manages application locality. Loaded: loaded (/lib/systemd/system/numad.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Mon 2020-02-24 01:08:37 EST; 51min ago Docs: man:numad Process: 458646 ExecStart=/usr/bin/numad $DAEMON_ARGS -i 15 (code=exited, status=0/SUCCESS) Main PID: 458655 (code=dumped, signal=SEGV) Feb 23 13:13:09 ws-g48-2d81-host systemd[1]: Starting numad - The NUMA daemon that manages application locality Feb 23 13:13:09 ws-g48-2d81-host systemd[1]: Started numad - The NUMA daemon that manages application locality.. Feb 24 01:08:37 ws-g48-2d81-host systemd[1]: numad.service: Main process exited, code=dumped, status=11/SEGV Feb 24 01:08:37 ws-g48-2d81-host systemd[1]: numad.service: Failed with result 'core-dump'. Feb 24 01:08:37 ws-g48-2d81-host kernel: [420098.990410] numad[458655]: segfault (11) at 2cd49ad1990 nip 7bafaaf6253c lr 2ccc1308580 code 1 in libc-2.30.so[7bafaaeb+21] Feb 24 01:08:37 ws-g48-2d81-host kernel: [420098.990424] numad[458655]: code: 6042 7ba70fa4 7d0a3a2e 2c28 4182ff14 7ba91f24 3908 eba10028 Feb 24 01:08:37 ws-g48-2d81-host kernel: [420098.990427] numad[458655]: code: ebe10038 7d2a4a14 38c0 ebc90080 f8a90080 7d0a3b2e f8de0008 Feb 24 01:08:37 ws-g48-2d81-host systemd[1]: numad.service: Main process exited, code=dumped, status=11/SEGV Feb 24 01:08:37 ws-g48-2d81-host systemd[1]: numad.service: Failed with result 'core-dump'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832915 Title: numad crashes while running kvm guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1832915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864389] Re: Missing dependency for KDE Connect SMS
** Changed in: kdeconnect (Ubuntu Focal) 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/1864389 Title: Missing dependency for KDE Connect SMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1864389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864317] Re: CapsLock toggles group on keyrelease instead of keypress
this was due to a patch we carried, but it was dropped when we migrated to xserver 1.19 ** Changed in: xorg-server (Ubuntu) Status: New => 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/1864317 Title: CapsLock toggles group on keyrelease instead of keypress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864284] Re: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug
Upstream: https://lore.kernel.org/linux- usb/20200224071541.117363-1-vicamo.y...@canonical.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864284 Title: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1864284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864423] [NEW] Failed test 'default log is not used' with new procps 3.3.16-1
Public bug reported: Since the new procps upload procps | 2:3.3.16-1ubuntu1 | focal-proposed | source, amd64, arm64, armhf, i386, ppc64el, s390x the tests of postgresql-common fail. The issues are: autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - results - - - - - - - - - - run-testsuiteFAIL non-zero exit status 2 autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - stderr - - - - - - - - - - # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 143. # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 154. # Looks like you failed 2 tests of 144. It was retried a few times by different people now and reproduced so we can assume it is a real issues for now. I was running two VMs to compare: $ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --test-name=run-testsuite --apt-pocket=proposed=src:procps --shell postgresql-common_211.dsc -- qemu --qemu-options='-cpu host' --ram-size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img (and the other one without --apt-pocket=proposed=src:procps) The issue reproduced locally in only the one with the new procps. In Debian the latest similar run is https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-common/4279031/log.gz https://ci.debian.net/data/packages/testing/amd64/p/postgresql-common/4279031.log But that is pre-3.3.16 and I wasn't able to find their result with the same combination. Lets mark this bug update-excuse and check if we can find anything in these VMs. ** Affects: postgresql-common (Ubuntu) Importance: Undecided Status: New ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864423 Title: Failed test 'default log is not used' with new procps 3.3.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727971] Re: Kontact crashes on start
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kontact (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/1727971 Title: Kontact crashes on start To manage notifications about this bug go to: https://bugs.launchpad.net/kdepim/+bug/1727971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864284] Re: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug
SRU: https://lists.ubuntu.com/archives/kernel- team/2020-February/107726.html ** Description changed: + [SRU Justification] + + [Impact] + USB devices attached to Dell WD19/WD19DC USB Type-C dock take up to nearly one + minutes to be ready for use. + + [Fix] + r8152 driver init process involves several for-loops that each may take up to 14 + seconds to exit when USB port reset occurs during hotplug. This is still + reproducible with latest v5.6-rc mainline kernel although the fail rate is much + lower since v5.5-rc7. + + [Test Case] + Verified on Dell WD19DC. + + [Regression Potential] + Low. Just to exit the loop early when it should have been. + + == original bug description == + Dell USB Type C docking WD19/WD19DC attaches additional peripherals as: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M |__ Port 1: Dev 11, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M where usb 2-1-3 is a hub connecting all USB Type-A/C ports on the dock. When hotplugging such dock with additional usb devices already attached on it, the probing process may reset usb 2.1 port, therefore r8152 ethernet device is also reset. However, in r8152 driver there are several for-loops that may take up to 14 seconds during the initialization for each in practice, and that has to be completed before USB may re-enumerate devices on the bus. As a result, devices attached to the dock will only be available after nearly 1 minute after the dock is plugged in. - [ 216.388290] [250] r8152 2-1.4:1.0: usb_probe_interface - [ 216.388292] [250] r8152 2-1.4:1.0: usb_probe_interface - got id - [ 258.830410] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): PHY not ready - [ 258.830460] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Invalid header when reading pass-thru MAC addr - [ 258.830464] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Get ether addr fail + [ 216.388290] [250] r8152 2-1.4:1.0: usb_probe_interface + [ 216.388292] [250] r8152 2-1.4:1.0: usb_probe_interface - got id + [ 258.830410] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): PHY not ready + [ 258.830460] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Invalid header when reading pass-thru MAC addr + [ 258.830464] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Get ether addr fail This can be reproduced on all kernel versions up to latest v5.6-rc2, but after v5.5-rc7 the reproduce rate is dramatically lower to 1/30 or so while it was around 1/2. The time consuming for-loops are at: https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L3206 https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5400 https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5537 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1037-oem-osp1 5.0.0-1037.42 ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21 Uname: Linux 5.0.0-1037-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 2014 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 04:07:20 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-hodor+X95 InstallationDate: Installed on 2020-01-16 (37 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 IwConfig: enp1s0no wireless extensions. enxd8d090035306 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Latitude 3310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 root=UUID=1ad036ce-aa29-4d5e-8692-d980d1a7140f ro "dyndbg=file drivers/usb/* +pt" log_buf_len=32M ignore_loglevel usbcore.quirks=0bda:0487:k RelatedPackageVersions: linux-restricted-modules-5.0.0-1037-oem-osp1 N/A linux-backports-modules-5.0.0-1037-oem-osp1 N/A linux-firmware 1.173.15 SourcePackage: linux-oem-osp1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 99.51.2[V2 AMI] dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr99.51.2[V2AMI]:bd01/07/2020:svnDellInc.:pnLatitude3310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family:
[Bug 1859744] Re: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error
** Tags removed: ikeradar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859744 Title: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864198] Re: Update kernel options CONFIG_NR_CPUS and CONFIG_NUMA_EMU for focal
Request submitted to kernel team's mailing list: https://lists.ubuntu.com/archives/kernel-team/2020-February/thread.html#107724 changing status to 'In Progress' ** Changed in: ubuntu-z-systems Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: Frank Heimes (fheimes) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864198 Title: Update kernel options CONFIG_NR_CPUS and CONFIG_NUMA_EMU for focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1864198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit
** Tags removed: ikeradar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859261 Title: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859269] Re: [roce-0111]sync mainline kernel 5.5rc6 roce patchset into ubuntu HWE kernel branch
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-20.04 Status: Incomplete => In Progress ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Incomplete => In Progress ** Changed in: kunpeng920 Status: Incomplete => In Progress ** Changed in: kunpeng920/ubuntu-20.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-18.04-hwe Assignee: (unassigned) => Ike Panhc (ikepanhc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859269 Title: [roce-0111]sync mainline kernel 5.5rc6 roce patchset into ubuntu HWE kernel branch To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850681] Re: TREKSTOR Primebook C11B touchpad and touchscreen not working
** Changed in: linux (Ubuntu) Status: Expired => 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/1850681 Title: TREKSTOR Primebook C11B touchpad and touchscreen not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863751] Re: Fails to install ppcle version of Ubuntu 19.10 dued to downlevel qemu-system-ppc
*** This bug is a duplicate of bug 1847806 *** https://bugs.launchpad.net/bugs/1847806 Hi Chris, the emulation issue is known (bug 1847806) and resolved (as you confirmed) in qemu 4.2 that is in Ubuntu 20.04. The TL;DR is that glibc in >=19.10 picked up some new instructions that are not emulated before the newer qemu version. I'll mark the bug as a dup ... ** This bug has been marked a duplicate of bug 1847806 eoan: ppc64el install on pseries-eoan VM fails to install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863751 Title: Fails to install ppcle version of Ubuntu 19.10 dued to downlevel qemu- system-ppc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1863751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861408] Re: firefox apparmor messages
after firefox restart these appeared:
Feb 24 09:30:04 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 141.932834] audit:
type=1400 audit(1582525804.452:27): apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/1888/uid_map"
pid=1888 comm=495043204C61756E6368202331 requested_mask="w" denied_mask="w"
fsuid=1000 ouid=1000
Feb 24 09:30:04 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 141.934780] IPC
Launch #1[1888]: segfault at 0 ip 7fa9fe84808c sp 7fa9f0efa780 error 6
in libxul.so[7fa9fdfac000+6f21000]
Feb 24 09:30:04 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 141.934798] Code:
75 12 89 e8 48 81 c4 10 02 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 f5 bb fc ff 48
8d 05 ae 89 85 04 48 8b 0d 57 75 c6 06 48 89 01 04 25 00 00 00 00 1e 02 00
00 e8 ac 4a fd ff 48 8d 05 e3 89 85
Feb 24 09:30:06 dinar-HP-Pavilion-g7-Notebook-PC wpa_supplicant[826]: wlo1:
CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-85 noise=-95 txrate=14400
Feb 24 09:30:10 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 148.016837] audit:
type=1400 audit(1582525810.536:28): apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/1926/uid_map"
pid=1926 comm=495043204C61756E6368202331 requested_mask="w" denied_mask="w"
fsuid=1000 ouid=1000
Feb 24 09:30:10 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 148.017346] IPC
Launch #1[1926]: segfault at 0 ip 7fa9fe84808c sp 7fa9eb29d780 error 6
in libxul.so[7fa9fdfac000+6f21000]
Feb 24 09:30:10 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 148.017359] Code:
75 12 89 e8 48 81 c4 10 02 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 f5 bb fc ff 48
8d 05 ae 89 85 04 48 8b 0d 57 75 c6 06 48 89 01 04 25 00 00 00 00 1e 02 00
00 e8 ac 4a fd ff 48 8d 05 e3 89 85
Feb 24 09:30:11 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 148.895517] IPC
Launch #1[1973]: segfault at 0 ip 7fa9fe84808c sp 7fa9ea5a2780 error 6
in libxul.so[7fa9fdfac000+6f21000]
Feb 24 09:30:11 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 148.895535] Code:
75 12 89 e8 48 81 c4 10 02 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 f5 bb fc ff 48
8d 05 ae 89 85 04 48 8b 0d 57 75 c6 06 48 89 01 04 25 00 00 00 00 1e 02 00
00 e8 ac 4a fd ff 48 8d 05 e3 89 85
Feb 24 09:30:11 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 148.895594] audit:
type=1400 audit(1582525811.416:29): apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/1973/uid_map"
pid=1973 comm=495043204C61756E6368202331 requested_mask="w" denied_mask="w"
fsuid=1000 ouid=1000
Feb 24 09:30:12 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 150.432287] IPC
Launch #1[1991]: segfault at 0 ip 7fa9fe84808c sp 7fa9fba7f780 error 6
in libxul.so[7fa9fdfac000+6f21000]
Feb 24 09:30:12 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 150.432303] Code:
75 12 89 e8 48 81 c4 10 02 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 f5 bb fc ff 48
8d 05 ae 89 85 04 48 8b 0d 57 75 c6 06 48 89 01 04 25 00 00 00 00 1e 02 00
00 e8 ac 4a fd ff 48 8d 05 e3 89 85
Feb 24 09:30:12 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 150.432405] audit:
type=1400 audit(1582525812.952:30): apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/1991/uid_map"
pid=1991 comm=495043204C61756E6368202331 requested_mask="w" denied_mask="w"
fsuid=1000 ouid=1000
Feb 24 09:30:14 dinar-HP-Pavilion-g7-Notebook-PC wpa_supplicant[826]: wlo1:
CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-75 noise=-95 txrate=13000
Feb 24 09:30:14 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 152.373278] IPC
Launch #1[2012]: segfault at 0 ip 7fa9fe84808c sp 7fa9f6fd9780 error 6
in libxul.so[7fa9fdfac000+6f21000]
Feb 24 09:30:14 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 152.373293] Code:
75 12 89 e8 48 81 c4 10 02 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 f5 bb fc ff 48
8d 05 ae 89 85 04 48 8b 0d 57 75 c6 06 48 89 01 04 25 00 00 00 00 1e 02 00
00 e8 ac 4a fd ff 48 8d 05 e3 89 85
Feb 24 09:30:14 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 152.373325] audit:
type=1400 audit(1582525814.892:31): apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/2012/uid_map"
pid=2012 comm=495043204C61756E6368202331 requested_mask="w" denied_mask="w"
fsuid=1000 ouid=1000
and i have seen some suspicious things, for that i commented out those
capability rules.
also, there were problems, in addition to the new messages: firefox said
{ff has been updated, you must restart it} on every tab, if i open them,
and then after restarting, content of that tabs were lost. one of them
has put ubuntu.com at address bar, another become blank.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861408
Title:
firefox apparmor messages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1861408/+subscriptions
--
ubuntu-bugs mailing list
[Bug 1859743] Re: [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64 platform
** Tags removed: ikeradar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859743 Title: [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64 platform To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863590] Re: Chrony test hangs with libpcap2 1:2.31-1
FYI - libcap2 2.32 is blocking on bubblewrap (bug 1863733) that needs the tests updated (https://github.com/containers/bubblewrap/issues/353) to pass proposed migration. FYI No current chrony tests in excuses that are blocking anyone (and if so testing vs libcap2 from proposed makes it work) - we can wait on bubblewrap a few days (it is a test-only bugfix, that isn't feature freeze related). ** Bug watch added: github.com/containers/bubblewrap/issues #353 https://github.com/containers/bubblewrap/issues/353 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863590 Title: Chrony test hangs with libpcap2 1:2.31-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1863590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864419] Re: [bionic][azure] fence_scsi unable to unfence from another node
I have tried in another environment, using LIO as storage server, and Focal (because I only had Focal available) and I was able to release all keys from the shared disk: (k)rafaeldtinoco@clufocal01:~$ sudo sg_persist -v --out --release --param-rk=0xbf09 --prout-type=5 /dev/sda inquiry cdb: 12 00 00 00 24 00 LIO-ORG cluster.focal.t 4.0 Peripheral device type: disk Persistent reservation out cdb: 5f 02 05 00 00 00 00 00 18 00 PR out: command (Release) successful (k)rafaeldtinoco@clufocal01:~$ sudo sg_persist -v --out --release --param-rk=0xbf090001 --prout-type=5 /dev/sda inquiry cdb: 12 00 00 00 24 00 LIO-ORG cluster.focal.t 4.0 Peripheral device type: disk Persistent reservation out cdb: 5f 02 05 00 00 00 00 00 18 00 PR out: command (Release) successful (k)rafaeldtinoco@clufocal01:~$ sudo sg_persist -v --out --release --param-rk=0xbf090002 --prout-type=5 /dev/sda inquiry cdb: 12 00 00 00 24 00 LIO-ORG cluster.focal.t 4.0 Peripheral device type: disk Persistent reservation out cdb: 5f 02 05 00 00 00 00 00 18 00 PR out: command (Release) successful Note that the SCSI CMD is pretty much the same to the faulty one in Azure environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864419 Title: [bionic][azure] fence_scsi unable to unfence from another node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
** Changed in: binutils Status: Confirmed => 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/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757517]
Hi guys, In ByteDance, we hit this Glibc bug twice in real-world production and adopted the fix based on the OpenJDK solution. However, these temporary fixes are not extensible. In the end, it needs to be fixed on the Glibc side. Cheers, Wang Liushuai. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757517 Title: An unused thread-local memory allocation can cause library calls to segfault. To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1757517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711407] Re: unregister_netdevice: waiting for lo to become free
4.15.0-54-generic did work great in the past we moved to 5.3.0-28-generic and this bug is notable... funny enough one of our machines was able to recover... both have the very same OS version Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic 5.3.0-28-generic maybe a downgrade de to Ubuntu 18.04.2 is a "solution" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711407 Title: unregister_netdevice: waiting for lo to become free To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711407] Re: unregister_netdevice: waiting for lo to become free
4.15.0-54-generic is bug free 5.3.0-28-generic has the bug funny enough one of our machines was able to recover... both have the very same OS version Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic 5.3.0-28-generic maybe a downgrade de to Ubuntu 18.04.2 is a "solution" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711407 Title: unregister_netdevice: waiting for lo to become free To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843479]
Closing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843479]
Can be closed now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864419] [NEW] [bionic][azure] fence_scsi unable to unfence from another node
Public bug reported: When playing with fence_scsi in Azure's new shared disk feature, I discovered that I'm able to register a key and acquire a reservation using that key for the host I have generated the key to. BUT, when trying to unregister a key from another host I get errors. With that problem, I can't use fence_scsi agent for fencing in Microsoft Azure. --- rafaeldtinoco@clubionic01:~$ cat /etc/fence_scsi.key 3abe Registering a node into the shared disk manually: rafaeldtinoco@clubionic01:~$ sudo fence_scsi --verbose -n 10.250.3.10 -d /dev/sdc -k 3abe -D debug.log -o on Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_persist -n -i -k -d /dev/sdc 0 PR generation=0x8, there are NO registered reservation keys No registration for key 3abe on device /dev/sdc Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_persist -n -o -I -S 3abe -d /dev/sdc 0 Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_persist -n -i -k -d /dev/sdc 0 PR generation=0x9, 1 registered reservation key follows: 0x3abe Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_persist -n -i -r -d /dev/sdc 0 PR generation=0x9, there is NO reservation held Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_persist -n -o -R -T 5 -K 3abe -d /dev/sdc 0 Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_persist -n -i -k -d /dev/sdc 0 PR generation=0x9, 1 registered reservation key follows: 0x3abe Success: Powered ON Trying to un-register from the same node HAS TO FAIL (fence_scsi does not allow it) rafaeldtinoco@clubionic01:~$ sudo fence_scsi --verbose -n 10.250.3.10 -d /dev/sdc -k 3abe -D debug.log -o off Delay 0 second(s) before logging in to the fence device Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_persist -n -i -k -d /dev/sdc 0 PR generation=0x9, 1 registered reservation key follows: 0x3abe Failed: keys cannot be same. You can not fence yourself. Trying to un-register from another node (has to succeed, that is the fencing purpose!) rafaeldtinoco@clubionic02:~$ sudo fence_scsi --verbose -n 10.250.3.10 -d /dev/sdc -k 3abe -D debug.log -o off Delay 0 second(s) before logging in to the fence device Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_persist -n -i -k -d /dev/sdc 0 PR generation=0x9, 1 registered reservation key follows: 0x3abe Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_persist -n -i -k -d /dev/sdc 0 PR generation=0x9, 1 registered reservation key follows: 0x3abe Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_persist -n -o -A -T 5 -K 62ed0001 -S 3abe -d /dev/sdc 99 persistent reserve out: transport: Host_status=0x07 [DID_ERROR] Driver_status=0x00 [DRIVER_OK] PR out (Preempt and abort): Sense category: -1, try '-v' option for more information Executing: /usr/bin/sg_turs /dev/sdc 0 Executing: /usr/bin/sg_persist -n -i -k -d /dev/sdc 0 PR generation=0x9, 1 registered reservation key follows: 0x3abe Failed to remove key 3abe on device /dev/sdc Failed to verify 1 device(s) - And I have realized that, in the SAME node (as the key in place), I'm able to release and unregister a node's key: rafaeldtinoco@clubionic01:~$ sudo sg_persist --out --release --param-rk=0x3abe --prout-type=5 /dev/sdc Msft Virtual Disk 1.0 Peripheral device type: disk rafaeldtinoco@clubionic01:~$ sudo sg_persist --out --register --param-rk=0x3abe --prout-type=5 /dev/sdc Msft Virtual Disk 1.0 Peripheral device type: disk - But in a different node, after the reservation is set in a different node, I CANNOT release and unregister the node'skey: rafaeldtinoco@clubionic02:~$ sudo sg_persist --in --read-keys --device=/dev/sdc Msft Virtual Disk 1.0 Peripheral device type: disk PR generation=0x9, 1 registered reservation key follows: 0x3abe rafaeldtinoco@clubionic02:~$ sudo sg_persist --out --release --param-rk=0x3abe --prout-type=5 /dev/sdc Msft Virtual Disk 1.0 Peripheral device type: disk persistent reserve out: transport: Host_status=0x07 [DID_ERROR] Driver_status=0x00 [DRIVER_OK] rafaeldtinoco@clubionic02:~$ sudo sg_persist --out --register --device=/dev/sdc --param-rk=0x3abe Msft Virtual Disk 1.0 Peripheral device type: disk persistent reserve out: transport: Host_status=0x07 [DID_ERROR] Driver_status=0x00 [DRIVER_OK] ** Affects: fence-agents (Ubuntu) Importance: Undecided Status: New ** Affects: fence-agents (Ubuntu Bionic) Importance: High Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed **
[Bug 1864419] Re: [bionic][azure] fence_scsi unable to unfence from another node
Creating an easier reproducer: Node 01: rafaeldtinoco@clubionic01:~$ sudo sg_persist --out --register --param-sark=3abe /dev/sdc Msft Virtual Disk 1.0 Peripheral device type: disk rafaeldtinoco@clubionic01:~$ sudo sg_persist --out --reserve --param-rk=3abe --prout-type=5 /dev/sdc Msft Virtual Disk 1.0 Peripheral device type: disk rafaeldtinoco@clubionic01:~$ sudo sg_persist -r /dev/sdc Msft Virtual Disk 1.0 Peripheral device type: disk PR generation=0xb, Reservation follows: Key=0x3abe scope: LU_SCOPE, type: Write Exclusive, registrants only Node 02: (has to be able to remove node's 01 reservation): rafaeldtinoco@clubionic02:~$ sudo sg_persist -v --out --release --param-rk=3abe --prout-type=5 /dev/sdc inquiry cdb: 12 00 00 00 24 00 Msft Virtual Disk 1.0 Peripheral device type: disk Persistent Reservation Out cmd: 5f 02 05 00 00 00 00 00 18 00 persistent reserve out: transport: Host_status=0x07 [DID_ERROR] Driver_status=0x00 [DRIVER_OK] PR out (Release): Sense category: -1 We get a sense out of the storage server. But if we try to remove the reservation from the same node it works: rafaeldtinoco@clubionic01:~$ sudo sg_persist -v --out --release --param-rk=3abe --prout-type=5 /dev/sdc inquiry cdb: 12 00 00 00 24 00 Msft Virtual Disk 1.0 Peripheral device type: disk Persistent Reservation Out cmd: 5f 02 05 00 00 00 00 00 18 00 PR out: command (Release) successful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864419 Title: [bionic][azure] fence_scsi unable to unfence from another node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
Also, if you have upgraded to 19.10 then please run this again to send us fresh system information: apport-collect 1838919 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864404] Re: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist)
** Also affects: fence-agents (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: fence-agents (Ubuntu Xenial) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864404 Title: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864404] Re: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist)
** Also affects: fence-agents (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: fence-agents (Ubuntu Xenial) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1864404 Title: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
Actually I should have just continued from comment #27. To do that please run: mv ~/.local/share/gnome-shell/extensions ~/old-extensions and then reboot. Any improvement? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: mutter (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/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864410] Re: [xenial] fence_scsi does not support hostnames in node list
** Also affects: fence-agents (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: fence-agents (Ubuntu Xenial) ** Summary changed: - [xenial] fence_scsi does not support hostnames in node list + [bionic] fence_scsi does not support hostnames in node list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864410 Title: [bionic] fence_scsi does not support hostnames in node list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864410] Re: [xenial] fence_scsi does not support hostnames in node list
** Summary changed: - fence_scsi does not support hostnames in node list + [xenial] fence_scsi does not support hostnames in node list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864410 Title: [bionic] fence_scsi does not support hostnames in node list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864413] Re: [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864413 Title: [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
The conversation above is no longer fresh in my memory, but I can see a couple of problems worth mentioning: * The bug description at the top doesn't clearly describe the problem. If the issue is "Slow and lost keyboard and mouse events" then please explain how you experience that issue in more detail; and... * Avoid mentioning log messages in the discussion and bug description as they are usually irrelevant and misleading. * Your attachment GsettingsChanges.txt seems to mention a few changes on the system that might relate to the problem: b'org.gnome.desktop.a11y.keyboard' b'mousekeys-max-speed' b'750' b'org.gnome.desktop.a11y.keyboard' b'mousekeys-init-delay' b'160' b'org.gnome.desktop.a11y.keyboard' b'mousekeys-accel-time' b'1200' b'org.gnome.desktop.a11y.keyboard' b'bouncekeys-beep-reject' b'true' b'org.gnome.desktop.a11y.keyboard' b'mousekeys-enable' b'true' b'org.gnome.desktop.a11y.keyboard' b'stickykeys-modifier-beep' b'true' b'org.gnome.desktop.a11y.keyboard' b'stickykeys-two-key-off' b'true' b'org.gnome.desktop.a11y.keyboard' b'slowkeys-beep-accept' b'true' b'org.gnome.desktop.a11y.keyboard' b'slowkeys-beep-press' b'true' b'org.gnome.desktop.a11y.keyboard' b'disable-timeout' b'120' If you don't remember why you have those set then please remove them by running: dconf reset -f /org/gnome/desktop/a11y/ and then reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
** Tags removed: disco ** Tags added: eoan ** Changed in: gnome-shell (Ubuntu) Status: Won't Fix => New ** Changed in: mutter (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863805] Re: When booting to install the language selection menu not available
Yeah, it's not ideal but it's more of a general Ubuntu question than a Lubuntu one. ** Package changed: calamares (Ubuntu) => grub2 (Ubuntu) ** Changed in: grub2 (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/1863805 Title: When booting to install the language selection menu not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864413] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1864413 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864413 Title: [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864413] [NEW] [bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways
Public bug reported:
[Impact]
To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways.
[Fixes]
Most of the patches are already upstream (either Accepted or under review) and
being
tracked here:
https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A
SAUCE patches have been tested by Canonical CE-QA (based on
Ubuntu-4.15.0-73.82).
[Regression Potential]
Low. We've carried these patches in the linux-oem (4.15.y) kernel for more than
2 years.
Also, the impact is limited to the Redpine RS9113 Wifi+BT with following VID/PID
{ SDIO_DEVICE(0x041B, 0x9330) }.
[Note]
linux-oem SRU tracking bug link: http://bugs.launchpad.net/bugs/1657682
This bug is used for tracking purposes, please do not triage.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: Incomplete
** Tags: bionic
** Description changed:
[Impact]
- To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways.
+ To support RS9113 Wifi+BT chip on Dell Edge 300x IoT Gateways.
[Fixes]
Most of the patches are already upstream (either Accepted or under review)
and being
tracked here:
https://patchwork.kernel.org/project/linux-wireless/list/?state=*=rsi%3A
SAUCE patches have been tested by Canonical CE-QA (based on
Ubuntu-4.15.0-73.82).
[Regression Potential]
Low. We've carried these patches in the linux-oem (4.15.y) kernel for more
than 2 years.
Also, the impact is limited to the Redpine RS9113 Wifi+BT with following
VID/PID
{ SDIO_DEVICE(0x041B, 0x9330) }.
+ [Note]
+ linux-oem SRU tracking bug link: http://bugs.launchpad.net/bugs/1657682
+
This bug is used for tracking purposes, please do not triage.
** Also affects: linux (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/1864413
Title:
[bionic] Support Redpine RS9113 Wifi+BT chip on Dell Edge 300x IoT
Gateways
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864413/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857364] Re: group sambashare with gid 1000
** Changed in: lubuntu-meta (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/1857364 Title: group sambashare with gid 1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1857364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864352] Re: Failure to assign user selected hostmame
There were changes in 3.2.19 that added functionality to specify the mechanism to set the hostname. None of them appear to work at all. The theory is this is because there's already an /etc/hostname. Curiously the log provides no information other than it seems to start the job but provides no information about it ending, whether as a failure or success. Should be fixed in 3.2.19.1. BTW Leó you should use `ubuntu-bug «package-name»` and it will automatically pull in diagnostic information such as the session log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864352 Title: Failure to assign user selected hostmame To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1864352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Since the Apple usb NIC doesn't have this issue, it is a problem on the driver lan78xx.c Do you mean even without ipv6 tunnel, only setup a bridge on rpi3 to let eth0 connect WAN and let wlan0 play a role of AP, this issue could be reproduced? Could you please share the detailed steps on how to setup a bridge on the rpi3 to reproduce this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851188] Re: Failed to create a partition table - install failed
** Changed in: calamares (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851188 Title: Failed to create a partition table - install failed To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1851188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864352] Re: Failure to assign user selected hostmame
** Changed in: calamares (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864352 Title: Failure to assign user selected hostmame To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1864352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864410] [NEW] fence_scsi does not support hostnames in node list
Public bug reported: Whenever configuring fence_scsi in a pacemaker cluster, the "fence_scsi" fencing agent won't support having node names in its pcmk_host_list. You can reproduce this behavior using the fence_scsi agent directly: $ sudo fence_scsi --verbose -n clubionic01 --action=off -d /dev/disk/by- path/acpi-VMBUS:01-scsi-0:0:0:0 Delay 0 second(s) before logging in to the fence device Executing: /usr/sbin/corosync-cmapctl totem.cluster_name 0 totem.cluster_name (str) = clubionic Executing: /usr/sbin/corosync-cmapctl nodelist. 0 nodelist.local_node_pos (u32) = 0 nodelist.node.0.name (str) = clubionic01 nodelist.node.0.nodeid (u32) = 1 nodelist.node.0.ring0_addr (str) = 10.250.3.10 nodelist.node.1.name (str) = clubionic02 nodelist.node.1.nodeid (u32) = 2 nodelist.node.1.ring0_addr (str) = 10.250.3.11 nodelist.node.2.name (str) = clubionic03 nodelist.node.2.nodeid (u32) = 3 nodelist.node.2.ring0_addr (str) = 10.250.3.12 Failed: unable to parse output of corosync-cmapctl or node does not exist Please use '-h' for usage -- When using IP address fence_scsi agent works: rafaeldtinoco@clubionic01:~$ sudo fence_scsi --verbose -n 10.250.3.10 --action=off -d /dev/disk/by-path/acpi-VMBUS:01-scsi-0:0:0:0 Delay 0 second(s) before logging in to the fence device Executing: /usr/sbin/corosync-cmapctl totem.cluster_name 0 totem.cluster_name (str) = clubionic Executing: /usr/sbin/corosync-cmapctl nodelist. 0 nodelist.local_node_pos (u32) = 0 nodelist.node.0.name (str) = clubionic01 nodelist.node.0.nodeid (u32) = 1 nodelist.node.0.ring0_addr (str) = 10.250.3.10 nodelist.node.1.name (str) = clubionic02 nodelist.node.1.nodeid (u32) = 2 nodelist.node.1.ring0_addr (str) = 10.250.3.11 nodelist.node.2.name (str) = clubionic03 nodelist.node.2.nodeid (u32) = 3 nodelist.node.2.ring0_addr (str) = 10.250.3.12 Executing: /usr/bin/sg_turs /dev/disk/by-path/acpi-VMBUS:01-scsi-0:0:0:0 0 Executing: /usr/bin/sg_turs /dev/disk/by-path/acpi-VMBUS:01-scsi-0:0:0:0 0 Executing: /usr/bin/sg_persist -n -i -k -d /dev/disk/by-path/acpi- VMBUS:01-scsi-0:0:0:0 0 PR generation=0x4, there are NO registered reservation keys No registration for key 3abe on device /dev/disk/by-path/acpi-VMBUS:01-scsi-0:0:0:0 Success: Already OFF ** Affects: fence-agents (Ubuntu) Importance: Undecided Status: New ** Affects: fence-agents (Ubuntu Xenial) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Also affects: fence-agents (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fence-agents (Ubuntu Xenial) Status: New => Confirmed ** Changed in: fence-agents (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: fence-agents (Ubuntu Xenial) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864410 Title: fence_scsi does not support hostnames in node list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863336] Re: trusty/linux-lts-xenial: 4.4.0-175.205~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1863338 packages: main: linux-lts-xenial meta: linux-meta-lts-xenial signed: linux-signed-lts-xenial phase: Testing phase-changed: Thursday, 20. February 2020 22:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863336 Title: trusty/linux-lts-xenial: 4.4.0-175.205~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376903] Re: Caps lock delay
** Changed in: xorg-server Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376903 Title: Caps lock delay To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1376903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838919] Re: Slow and lost keyboard and mouse events
Sorry for the delay. The problem still exists under 19.10 desktop, but does not occur quite as often. However, it is slightly harder to escape from... I either need to wait 20+ seconds uselessly pressing keys I will have to subsequently delete, or tab to another command prompt, type something in easily, then return to the "stuck" prompt. My comment is only to bring the bug report up to date and keep it open. We are only a few weeks from the 20.04 release, where this bug will be much more important if still present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838919 Title: Slow and lost keyboard and mouse events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851188] Re: Failed to create a partition table - install failed
I don't know why I never caught this before:
2020-02-22 - 18:56:39 [6]: Running "env" ("/sbin/udevadm", "settle")
2020-02-22 - 18:56:39 [6]: Finished. Exit code: 127
2020-02-22 - 18:56:39 [6]: Target cmd: ("/sbin/udevadm", "settle")
2020-02-22 - 18:56:39 [6]: Target output:
/usr/bin/env: ‘/sbin/udevadm’: No such file or directory
2020-02-22 - 18:56:39 [2]: WARNING: Could not settle disks.
That was the activity mentioned in the upstream bug that they suspected
would fix the issue. I believe they even added a second run of it in
hopes if making it better.
And here it is not running at all because it's calling a full path
that's the wrong one. But /usr/bin/udevadm is the right one.
Creating a symlink fixes the issue: `sudo ln -s /usr/bin/udevadm
/sbin/udevadm`.
Though the original upstream bug
(https://github.com/calamares/calamares/issues/1170) is still relevant,
it really came to no clear conclusion because we weren't looking in the
wrong place.
There's a new bug to fix this and several other issues which I have now
linked instead.
** Bug watch added: Calamares Issues #1324
https://github.com/calamares/calamares/issues/1324
** Changed in: calamares
Remote watch: Calamares Issues #1170 => Calamares Issues #1324
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851188
Title:
Failed to create a partition table - install failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/calamares/+bug/1851188/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863336] Re: trusty/linux-lts-xenial: 4.4.0-175.205~14.04.1 -proposed tracker
4.4.0-175.205~14.04.1 - lowlatency Regression test CMPL, RTB. 47 / 48 tests were run, missing: ubuntu_boot Issue to note in amd64: ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789) ubuntu_kvm_unit_tests - apic (bug 1748103) debug (bug 1821906) umip should be skipped (bug 1821905) ubuntu_ltp_syscalls - fanotify07 won't fix (bug 1775165) fanotify06 (bug 1833028) fanotify10 (bug 1802454) openat03 (bug 1798027) prctl07 (bug 1839064) quotactl07 (bug 1864092) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 46 / 47 tests were run, missing: ubuntu_boot Issue to note in i386: ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007) ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789) ubuntu_ltp_syscalls - fanotify07 won't fix (bug 1775165) fanotify06 (bug 1833028) fanotify10 (bug 1802454) openat03 (bug 1798027) prctl07 (bug 1839064) quotactl07 (bug 1864092) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 4.4.0-175.205~14.04.1 - generic Regression test CMPL, RTB. 47 / 48 tests were run, missing: ubuntu_boot Issue to note in amd64: ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789) ubuntu_kvm_unit_tests - apic (bug 1748103) debug (bug 1821906) umip should be skipped (bug 1821905) ubuntu_ltp_syscalls - fanotify07 won't fix (bug 1775165) fanotify06 (bug 1833028) fanotify10 (bug 1802454) openat03 (bug 1798027) prctl07 (bug 1839064) quotactl07 (bug 1864092) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 46 / 47 tests were run, missing: ubuntu_boot Issue to note in i386: ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789) ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007) ubuntu_ltp_syscalls - fanotify07 won't fix (bug 1775165) fanotify06 (bug 1833028) fanotify10 (bug 1802454) openat03 (bug 1798027) prctl07 (bug 1839064) quotactl07 (bug 1864092) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863336 Title: trusty/linux-lts-xenial: 4.4.0-175.205~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864404] Re: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist)
Make sure to also create the "fence_scsi.dev" file doing the same: # node01 create a file /etc/fence_scsi.dev containing: /dev/disk/by-path/acpi- VMBUS:01-scsi-0:0:0:0 # node02 create a file /etc/fence_scsi.dev containing: /dev/disk/by-path/acpi- VMBUS:01-scsi-0:0:0:0 # node03 create a file /etc/fence_scsi.dev containing: /dev/disk/by-path/acpi- VMBUS:01-scsi-0:0:0:0 Note: of course do change contents of the file to your shared disk device "by-path" path. Then, in all 3 nodes, add a 2nd line to /etc/tmpfiles.d/fence_scsi.conf file: L /var/run/cluster/fence_scsi.key - - - - /etc/fence_scsi.key L /var/run/cluster/fence_scsi.dev - - - - /etc/fence_scsi.dev And reboot the node to check if the file gets created after boot: rafaeldtinoco@clubionic01:~$ sudo ls /var/run/cluster fence_scsi.dev fence_scsi.key rafaeldtinoco@clubionic02:~$ sudo ls /var/run/cluster fence_scsi.dev fence_scsi.key rafaeldtinoco@clubionic03:~$ sudo ls /var/run/cluster fence_scsi.dev fence_scsi.key -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1864404 Title: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1864404] Re: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist)
Make sure to also create the "fence_scsi.dev" file doing the same: # node01 create a file /etc/fence_scsi.dev containing: /dev/disk/by-path/acpi- VMBUS:01-scsi-0:0:0:0 # node02 create a file /etc/fence_scsi.dev containing: /dev/disk/by-path/acpi- VMBUS:01-scsi-0:0:0:0 # node03 create a file /etc/fence_scsi.dev containing: /dev/disk/by-path/acpi- VMBUS:01-scsi-0:0:0:0 Note: of course do change contents of the file to your shared disk device "by-path" path. Then, in all 3 nodes, add a 2nd line to /etc/tmpfiles.d/fence_scsi.conf file: L /var/run/cluster/fence_scsi.key - - - - /etc/fence_scsi.key L /var/run/cluster/fence_scsi.dev - - - - /etc/fence_scsi.dev And reboot the node to check if the file gets created after boot: rafaeldtinoco@clubionic01:~$ sudo ls /var/run/cluster fence_scsi.dev fence_scsi.key rafaeldtinoco@clubionic02:~$ sudo ls /var/run/cluster fence_scsi.dev fence_scsi.key rafaeldtinoco@clubionic03:~$ sudo ls /var/run/cluster fence_scsi.dev fence_scsi.key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864404 Title: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845756] Re: lubuntu 19.10 strange movement of wallpaper on monitor.settings change
QA- install on hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) testcase: manual partitioning, using free space, BIOS, ENCRYPTION, internet On reboot, after validating the 'new' install I adjusted displays to match my setup; and had https://bugs.launchpad.net/ubuntu/+source/lxqt- session/+bug/1845756 occur; top display has the bottom of the wallpaper, my bottom display contains the top of wallpaper; mouse movement though is correct. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845756 Title: lubuntu 19.10 strange movement of wallpaper on monitor.settings change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1845756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864404] Re: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist)
# WORKAROUND: A way to workaround this issue is the following... in a 3 node cluster you can do this: # node01 create a file /etc/fence_scsi.key containing: 62ed # node02 create a file /etc/fence_scsi.key containing: 62ed0001 # node03 create a file /etc/fence_scsi.key containing: 62ed0002 In all 3 nodes create a file /etc/tmpfiles.d/fence_scsi.conf containing: L /var/run/cluster/fence_scsi.key - - - - /etc/fence_scsi.key This will make systemd to create a symlink /var/run/cluster/fence_scsi.key pointing to your /etc/fence_scsi.key file and will allow fence_scsi agent to use that file to do its SCSI persistent reservations. After creating those files reboot all the nodes and check if the file got created after boot: rafaeldtinoco@clubionic01:~$ ls /var/run/cluster/fence_scsi.key /var/run/cluster/fence_scsi.key rafaeldtinoco@clubionic01:~$ cat /var/run/cluster/fence_scsi.key 62ed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864404 Title: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864404] Re: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist)
# WORKAROUND: A way to workaround this issue is the following... in a 3 node cluster you can do this: # node01 create a file /etc/fence_scsi.key containing: 62ed # node02 create a file /etc/fence_scsi.key containing: 62ed0001 # node03 create a file /etc/fence_scsi.key containing: 62ed0002 In all 3 nodes create a file /etc/tmpfiles.d/fence_scsi.conf containing: L /var/run/cluster/fence_scsi.key - - - - /etc/fence_scsi.key This will make systemd to create a symlink /var/run/cluster/fence_scsi.key pointing to your /etc/fence_scsi.key file and will allow fence_scsi agent to use that file to do its SCSI persistent reservations. After creating those files reboot all the nodes and check if the file got created after boot: rafaeldtinoco@clubionic01:~$ ls /var/run/cluster/fence_scsi.key /var/run/cluster/fence_scsi.key rafaeldtinoco@clubionic01:~$ cat /var/run/cluster/fence_scsi.key 62ed -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1864404 Title: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1864404] [NEW] [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist)
Public bug reported: Whenever trying to configure fence_scsi using Ubuntu Bionic the following error happens: Failed Actions: * fence_clubionicpriv01_start_0 on clubionic01 'unknown error' (1): call=8, status=Error, exitreason='', last-rc-change='Mon Feb 24 03:20:28 2020', queued=0ms, exec=1132ms And the logs show: Feb 24 03:20:31 clubionic02 fence_scsi[14072]: Failed: Cannot open file "/var/run/cluster/fence_scsi.key" Feb 24 03:20:31 clubionic02 fence_scsi[14072]: Please use '-h' for usage That happens because the key to be used by fence_scsi agent does not exist. ** Affects: fence-agents (Ubuntu) Importance: Undecided Status: New ** Affects: fence-agents (Ubuntu Xenial) Importance: High Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Also affects: fence-agents (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fence-agents (Ubuntu Xenial) Status: New => Confirmed ** Changed in: fence-agents (Ubuntu Xenial) Importance: Undecided => High ** Changed in: fence-agents (Ubuntu Xenial) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864404 Title: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864404] [NEW] [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist)
Public bug reported: Whenever trying to configure fence_scsi using Ubuntu Bionic the following error happens: Failed Actions: * fence_clubionicpriv01_start_0 on clubionic01 'unknown error' (1): call=8, status=Error, exitreason='', last-rc-change='Mon Feb 24 03:20:28 2020', queued=0ms, exec=1132ms And the logs show: Feb 24 03:20:31 clubionic02 fence_scsi[14072]: Failed: Cannot open file "/var/run/cluster/fence_scsi.key" Feb 24 03:20:31 clubionic02 fence_scsi[14072]: Please use '-h' for usage That happens because the key to be used by fence_scsi agent does not exist. ** Affects: fence-agents (Ubuntu) Importance: Undecided Status: New ** Affects: fence-agents (Ubuntu Xenial) Importance: High Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Also affects: fence-agents (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fence-agents (Ubuntu Xenial) Status: New => Confirmed ** Changed in: fence-agents (Ubuntu Xenial) Importance: Undecided => High ** Changed in: fence-agents (Ubuntu Xenial) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1864404 Title: [bionic] fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1864404/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1863338] Re: xenial/linux: 4.4.0-175.205 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Monday, 17. February 2020 21:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1863334 trusty/linux-lts-xenial: bug 1863336 xenial/linux-aws: bug 1863311 xenial/linux-cascade: bug 1863314 xenial/linux-fips: bug 1863331 xenial/linux-kvm: bug 1863319 xenial/linux-raspi2: bug 1863324 xenial/linux-snapdragon: bug 1863329 xenial/linux/caracalla-kernel: bug 1863304 xenial/linux/pc-kernel: bug 1863306 xenial/linux/stlouis-kernel: bug 1863307 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863338 Title: xenial/linux: 4.4.0-175.205 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863338] Re: xenial/linux: 4.4.0-175.205 -proposed tracker
4.4.0-175.205 - generic Regression test CMPL, RTB. 56 / 59 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in amd64: ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) vmx (bug 1821394) ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 51 / 54 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_kvm_unit_tests - gicv2-mmio on X-ARM64 (bug 1828165) gicv2-mmio-3p (bug 1828027) gicv2-mmio-up (bug 1828026) pmu on ms10-34-mcdivittB0-kernel (bug 1751000) ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) ubuntu_lxc - failed to fetch GPG key, probably FW issue ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 50 / 54 tests were run, missing: ubuntu_kvm_unit_tests, ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in i386: ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 52 / 55 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_ecryptfs - faild to fork child for file-concurrent.sh and directory-concurrent.sh.ext3 ubuntu_fan_smoke_test - Failed to fetch file from http://ports.ubuntu.com (bug 1864140) ubuntu_ltp_syscalls - fallocate04, fallocate05, fsetxattr01, fdatasync03, fgetxattr01, fremovexattr01, fremovexattr02, fsync01, fsync04, fanotify13, fanotify14, fanotify15, lremovexattr01, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, setxattr01, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) fanotify10 (bug 1802454) move_pages12 (bug 1831043) ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) Issue to note in s390x (Ubuntu on LPAR): libhugetlbfs - failed 5 (Address is not hugepage, Heap not on hugepages) killed by signal 1 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) Issue to note in s390x (zVM): libhugetlbfs - failed 5 (Address is not hugepage, Heap not on hugepages) killed by signal 1 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705) ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) Note: * Missing s390x KVM because of bug 1859656 ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863338 Title: xenial/linux: 4.4.0-175.205 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814481] Re: Keychron K1 keyboard not working
Note that if the problem is fixed in later Ubuntu releases then it likely would be fixed in Ubuntu 18.04.4 too: https://ubuntu.com/download/desktop If you just update Ubuntu 18.04 then you won't ever get the same newer kernel as comes with 18.04.4. So maybe the issue is already fixed- released via the HWE kernel. You should be able to try it by: sudo apt install linux-generic-hwe-18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: Keychron K1 keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864284] Re: r8152 init may take up to 40 seconds at initialization with Dell WD19/WD19DC during hotplug
** Description changed: - TBD + Dell USB Type C docking WD19/WD19DC attaches additional peripherals as: + + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M + |__ Port 1: Dev 11, If 0, Class=Hub, Driver=hub/4p, 5000M + |__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 5000M + |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M + + where usb 2-1-3 is a hub connecting all USB Type-A/C ports on the dock. + + When hotplugging such dock with additional usb devices already attached + on it, the probing process may reset usb 2.1 port, therefore r8152 + ethernet device is also reset. However, in r8152 driver there are + several for-loops that may take up to 14 seconds during the + initialization for each in practice, and that has to be completed before + USB may re-enumerate devices on the bus. As a result, devices attached + to the dock will only be available after nearly 1 minute after the dock + is plugged in. + + This can be reproduced on all kernel versions up to latest v5.6-rc2, but + after v5.5-rc7 the reproduce rate is dramatically lower to 1/30 or so + while it was around 1/2. + + The time consuming for-loops are at: + https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L3206 + https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5400 + https://elixir.bootlin.com/linux/v5.5/source/drivers/net/usb/r8152.c#L5537 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1037-oem-osp1 5.0.0-1037.42 ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21 Uname: Linux 5.0.0-1037-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: u 2014 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: u 2014 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 04:07:20 2020 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-bionic-amd64-20180608-47+beaver-hodor+X95 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20180608-47+beaver-hodor+X95 InstallationDate: Installed on 2020-01-16 (37 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 IwConfig: - enp1s0no wireless extensions. - - enxd8d090035306 no wireless extensions. - - lono wireless extensions. + enp1s0no wireless extensions. + + enxd8d090035306 no wireless extensions. + + lono wireless extensions. MachineType: Dell Inc. Latitude 3310 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 root=UUID=1ad036ce-aa29-4d5e-8692-d980d1a7140f ro "dyndbg=file drivers/usb/* +pt" log_buf_len=32M ignore_loglevel usbcore.quirks=0bda:0487:k RelatedPackageVersions: - linux-restricted-modules-5.0.0-1037-oem-osp1 N/A - linux-backports-modules-5.0.0-1037-oem-osp1 N/A - linux-firmware 1.173.15 + linux-restricted-modules-5.0.0-1037-oem-osp1 N/A + linux-backports-modules-5.0.0-1037-oem-osp1 N/A + linux-firmware 1.173.15 SourcePackage: linux-oem-osp1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 99.51.2[V2 AMI] dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr99.51.2[V2AMI]:bd01/07/2020:svnDellInc.:pnLatitude3310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3310 dmi.product.sku: 0A13 dmi.sys.vendor: Dell Inc. ** Description changed: Dell USB Type C docking WD19/WD19DC attaches additional peripherals as: - /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M - |__ Port 1: Dev 11, If 0, Class=Hub, Driver=hub/4p, 5000M - |__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 5000M - |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M + |__ Port 1: Dev 11, If 0, Class=Hub, Driver=hub/4p, 5000M + |__ Port 3: Dev 12, If 0, Class=Hub, Driver=hub/4p, 5000M + |__ Port 4: Dev 13, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M where usb 2-1-3 is a hub connecting all USB Type-A/C ports
[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
I can't seem to reproduce this bug in 20.04. Although LibreOffice is a little slow and unresponsive the rest of the shell continues to animate smoothly the whole time (I left another window animating on top). So I wonder if this bug is either fixed already or caused by some modification to your machine. Please run this command to send us more information about the system: apport-collect 1864301 And if you can please also try booting Ubuntu 20.04 from USB and tell us if you can reproduce it there: http://cdimage.ubuntu.com/daily-live/current/ ** 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/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #944 https://gitlab.gnome.org/GNOME/mutter/issues/944 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/mutter/issues/944 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
** Description changed: https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b - https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8 gnome-shell crashes with this bug every time that: * I am editing a file in geany * I open the Find window (CTRL-F) and it opens on another monitor * I type in some un-findable text in the find window and press ENTER (or click the Next button) The system beeps to indicate that the text isn't found, but then crashes. Note especially that the find window must be on the other monitor - if it's on the same monitor as geany, gnome-shell doesn't crash. (Note: I originally thought that if I moved the find window to the other window and then searched, gnome-shell crashed, but I think what happens is a) I open the window, b) I move it, search for something, and it works, c) I close it and re-open it - it then opens on the other monitor and searching will crash gnome-shell.) gnome-shell restarts, but the crash causes data loss, as most of the running applications don't reappear when it restarts. In case it's relevant, I have a laptop screen set at 2048x1152 and an external monitor configured to be above it at 2560x1440. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.4.0-050400rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 10:37:36 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1570619894 InstallationDate: Installed on 2019-07-01 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo separator: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864326] Re: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE
Tracking in https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8 ** Description changed: + https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8 + Gnome Shell crashes and restarts when I try to open a dialog window. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu17 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 21:15:33 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-02-04 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: - () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2020-02-22 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864326 Title: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860057] Re: /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:set_workspace_state:_meta_window_shared_new
*** This bug is a duplicate of bug 1864326 *** https://bugs.launchpad.net/bugs/1864326 ** This bug is no longer a duplicate of bug 1849249 gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) ** This bug has been marked a duplicate of bug 1864326 gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860057 Title: /usr/bin/gnome- shell:6:__GI_raise:__GI_abort:g_assertion_message:set_workspace_state:_meta_window_shared_new To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864326] Re: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (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/1864326 Title: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864326] Re: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (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/1864326 Title: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864326] Re: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE
** Summary changed: - gnome-shell crashed with SIGABRT + gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864326 Title: gnome-shell crashed with SIGABRT, assertion failed: src/core/window.c:4853:set_workspace_state: 'window->unmanaging || workspace != NULL' should be TRUE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376903] Re: Caps lock delay
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #312 https://gitlab.freedesktop.org/xorg/xserver/issues/312 ** Changed in: xorg-server Importance: Wishlist => Unknown ** Changed in: xorg-server Status: Confirmed => Unknown ** Changed in: xorg-server Remote watch: freedesktop.org Bugzilla #56491 => gitlab.freedesktop.org/xorg/xserver/issues #312 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376903 Title: Caps lock delay To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1376903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814481] Re: Keychron K1 keyboard not working
good idea, thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: Keychron K1 keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864325] Re: On press of space key, lock screen got into a loop of trying to show the password field
I've never seen this behaviour before so wonder if it's caused by any of the modifications you've made to this system. Please start by uninstalling all of these extensions: 'openweather-extens...@jenslody.de', 'dash-to-d...@micxgx.gmail.com', 'clipboard-indica...@tudmotu.com', 'places-m...@gnome-shell-extensions.gcampax.github.com', 'refresh-w...@kgshank.net', 'NotificationCounter@coolllsk', 'permanent-notificati...@bonzini.gnu.org', 'removeaccesibility@lomegor', 'variety_control@manjaro' and then reboot. We need to look at extensions first because so many bugs are caused by extensions. And we require that you uninstall extensions and not just disable them because buggy extensions can still interfere with the system. ** 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/1864325 Title: On press of space key, lock screen got into a loop of trying to show the password field To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864390] Re: IDK
** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1864390 Title: IDK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1864390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864317] Re: CapsLock toggles group on keyrelease instead of keypress
** Tags added: xenial ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864317 Title: CapsLock toggles group on keyrelease instead of keypress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1864317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814481] Re: Keychron K1 keyboard not working
To ensure this bug does not become oversubscribed by other people with other problems I have clarified this bug is only about the "Keychron K1 keyboard". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: Keychron K1 keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814481] Re: bluetooth keyboard not working
Yes, sorry. I'm not sure what I was aiming for there. ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Summary changed: - bluetooth keyboard not working + Keychron K1 keyboard not working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: Keychron K1 keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
** Tags added: eoan ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2225 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225 Importance: Unknown Status: Unknown ** Tags added: performance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864287] Re: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected
It sounds like you might have a local config file specifying HDMI as your default sink. Try removing: ~/.config/pulse and then reboot. Separately, I notice your system seems to be some months out of date. Please update it by running: sudo apt update sudo apt full-upgrade and then reboot. Once up to date please run: apport-collect 1864287 to automatically send us more information about the machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864287 Title: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249705] Re: HDMI output not available in 13.10 or 14.04
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => 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/1249705 Title: HDMI output not available in 13.10 or 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1249705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310812] Re: No sound after upgrade from 13.10 to 14.04
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: pulseaudio (Ubuntu) Status: New => 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/1310812 Title: No sound after upgrade from 13.10 to 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1310812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864287] Re: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864287 Title: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864281] Re: Xorg freeze
Please take care to only report one issue per bug report. We should make this bug about the first issue: > I am getting nothing on my desktop Can you please explain in more detail what that problem means? Maybe with a photo? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freeze + Nothing on my desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864281 Title: Nothing on my desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1864281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814481] Re: bluetooth keyboard not working
@vanvugt, shouldn't that be after actually merging the fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: bluetooth keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864253] Re: Pulseaudio sink/source selection, weird behaviour.
This is the intended default behaviour of Ubuntu; to automatically switch to the audio device most recently plugged in. To disable this feature, please edit /etc/pulse/default.pa and comment out the line: load-module module-switch-on-connect making it: # load-module module-switch-on-connect ** Changed in: pulseaudio (Ubuntu) Status: New => 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/1864253 Title: Pulseaudio sink/source selection, weird behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)
Though if you use "Ubuntu on Wayland" then you need to set: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862081 Title: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1862081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)
That would probably be because a window in the foreground prevents fullscreen unredirect from being used. I suggest if you need both fullscreen window support and fractional scaling then logging into "Ubuntu on Wayland" might be a better option right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862081 Title: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1862081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855757] Re: [nvidia] Background image corrupted after standby
Please note Ubuntu 19.04 has reached end-of-life and is no longer supported. https://wiki.ubuntu.com/Releases -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)
Yes, Gnome 3.36 will be in Ubuntu 20.04 before April. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825842 Title: [vmware] Background goes white when using scaling (200%, 300% or 400%) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797734] Re: slow calculator startup
** Tags added: focal ** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814481] Re: bluetooth keyboard not working
** No longer affects: linux (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: bluetooth keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864400] Re: alsa/asoc: export the number of dmic to userspace to work with the latest ucm2 (focal)
** Description changed: - This bug is for tracking purpose. + [Impact] + In the ubuntu 20.04, we plan to integrate alsa-ucm-conf-v1.2.1.2 + or alsa-ucm-conf-v1.2.2, in the ucm2, adding a new element to + tell pulseaudo the number of dmics on this machine, this needs kernel + to export the number via component. + Without these 2 patches, the pulseaudio will fail to initialize + on Lenovo X1 Carbon since this machine has 4 dmics. + + [Fix] + Backported the patches from mainline kernel v5.6-c1 + + [Test Case] + Install the sof-firmware v1.4.2 + Install the master branch of alsa-ucm-conf (focal will integrate it too) + Install the master branch of pulseaudio (focal will integrate it too) + boot the kernel with these patches, check the gnome-control-center, + all audio function work well. + + + [Regression Risk] + Low, the patches are backported from upstream kernel, and I tested + this patch on Lenovo and Dell dmic machines. And after merging + these 2 patches, the kernel still could work with old firmware + and ucm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864400 Title: alsa/asoc: export the number of dmic to userspace to work with the latest ucm2 (focal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864400] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1864400 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** 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/1864400 Title: alsa/asoc: export the number of dmic to userspace to work with the latest ucm2 (focal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864400] [NEW] alsa/asoc: export the number of dmic to userspace to work with the latest ucm2 (focal)
Public bug reported: This bug is for tracking purpose. ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: Incomplete ** Tags: focal ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Summary changed: - alsa/asoc: export the number of dmic to userspace to work with the latest ucm2 + alsa/asoc: export the number of dmic to userspace to work with the latest ucm2 (focal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864400 Title: alsa/asoc: export the number of dmic to userspace to work with the latest ucm2 (focal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861237] Re: Audio not detected on X1 Yoga 4th
Probably kernel-5.4.0.15 will have all needed patches for supporting sof driver. But the sof-firmware has not been integrated to linux-firmware. So when .15 kernel is ready, we could manually install the firmware and alsa-ucm-conf to test. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861237 Title: Audio not detected on X1 Yoga 4th To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864269] Re: Details about accessing printer ink levels out of date
Thanks for your report! This docs page origin from upstream GNOME Help. Any chance that you can report the issue upstream too? https://gitlab.gnome.org/GNOME/gnome-user-docs/issues ** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864269 Title: Details about accessing printer ink levels out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1864269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
