[Bug 1908695] [NEW] AMD Zen3 CPUs (5800x, 5900x, 5950x) not fully supported in LTS yet
Public bug reported: Hi, As per subject the most recent AMD CPUs are not fully supported in Ubuntu LTS. The CPUs do run and work, but a very important feature such as sensors support via driver _k10temp_ is only going to be present from Kernel 5.10 onwards. Would it be possible to backport this patch (https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux- staging.git/commit/?h=hwmon- next&id=2835d860d3fcc3e4829e96987544e811d35dee48) into LTS kernels? Hopefully wouldn't be too complex? Kind regards. ** Affects: linux-meta-hwe (Ubuntu) Importance: Undecided Status: New ** Package changed: alsa-ucm-conf (Ubuntu) => linux-meta-hwe (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908695 Title: AMD Zen3 CPUs (5800x, 5900x, 5950x) not fully supported in LTS yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1908695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908632] Re: I have screen shots of an install bug, assoc. with grub
** Package changed: ubuntu => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908632 Title: I have screen shots of an install bug, assoc. with grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1908632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906738] Re: alsa/sdw: add support for tgl_3_in_1_sdca soundwire machine
verified on a private bug ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906738 Title: alsa/sdw: add support for tgl_3_in_1_sdca soundwire machine To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1906738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906236] Re: Intel Thunderbolt 4 Maple Ridge support
verified on the private bug ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906236 Title: Intel Thunderbolt 4 Maple Ridge support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1906236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''
Validate on Latitude 9420. Its codec init.conf under /usr/share/alsa/ucm2/codecs/rt715-sdca/init.conf introduced by https://github.com/thesofproject/alsa-ucm-conf/pull/45 The command: cset "name='rt714 ADC 22 Mux' 'DMIC3'" cset "name='rt714 ADC 23 Mux' 'DMIC4'" doesn't work, and internal microphone is not able to use. After update the libasound2. run $ alsactl init $ amixer cget name='rt714 ADC 22 Mux' numid=85,iface=MIXER,name='rt714 ADC 22 Mux' ; type=ENUMERATED,access=rw--,values=1,items=8 ; Item #0 'MIC1' ; Item #1 'MIC2' ; Item #2 'LINE1' ; Item #3 'LINE2' ; Item #4 'DMIC1' ; Item #5 'DMIC2' ; Item #6 'DMIC3' ; Item #7 'DMIC4' : values=6 $ amixer cget name='rt714 ADC 23 Mux' numid=86,iface=MIXER,name='rt714 ADC 23 Mux' ; type=ENUMERATED,access=rw--,values=1,items=8 ; Item #0 'MIC1' ; Item #1 'MIC2' ; Item #2 'LINE1' ; Item #3 'LINE2' ; Item #4 'DMIC1' ; Item #5 'DMIC2' ; Item #6 'DMIC3' ; Item #7 'DMIC4' : values=7 And the internal microphone works. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899857 Title: [SRU] alsa-lib: support the enum value settings both in "" and in '' To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable
somewhat verified on the private bug ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879633 Title: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1879633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907160] Re: intel-hid is not loaded on new Intel platform
assuming verified, can't wait anymore ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907160 Title: intel-hid is not loaded on new Intel platform To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903798] Re: Some Dell RKL AIO platform with e1000e require quirk to enter s0ix
verified on the private bug ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903798 Title: Some Dell RKL AIO platform with e1000e require quirk to enter s0ix To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1903798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903665] Re: Built-in screen is blank on some RKL platforms
verified on the private bug ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903665 Title: Built-in screen is blank on some RKL platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1903665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902687] Re: e1000e: fix issues with S0ix
we'll go with the old set for now, and maybe reuse this bug when the final version is upstream ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902687 Title: e1000e: fix issues with S0ix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1902687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908697] [NEW] Evince opens on the secondary monitor connected in HDMI instead of the main monitor.
Public bug reported: Evince opens on the secondary monitor connected in HDMI instead of the main monitor. lsb_release -rd: Description:Ubuntu 18.04.5 LTS Release:18.04 apt-cache policy evince: evince: Installato: 3.28.4-0ubuntu1.2 Candidato: 3.28.4-0ubuntu1.2 Tabella versione: *** 3.28.4-0ubuntu1.2 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 18 09:22:22 2020 InstallationDate: Installed on 2019-09-07 (467 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic evince third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908697 Title: Evince opens on the secondary monitor connected in HDMI instead of the main monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1908697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908697] Re: Evince opens on the secondary monitor connected in HDMI instead of the main monitor.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (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/1908697 Title: Evince opens on the secondary monitor connected in HDMI instead of the main monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1908697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908698] [NEW] package nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-440-server script post-installation devolvió el cód
Public bug reported: PC ASUS TUF GAMING FX506 NVIDIA GEFORCE RTX 2060 Drivers not install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 18 09:16:22 2020 ErrorMessage: el subproceso instalado paquete nvidia-dkms-440-server script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2020-06-10 (190 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-440-server Title: package nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-440-server script post-installation devolvió el código de salida de error 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-440-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908698 Title: package nvidia-dkms-440-server 440.95.01-0ubuntu0.20.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia- dkms-440-server script post-installation devolvió el código de salida de error 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440-server/+bug/1908698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907160] Re: intel-hid is not loaded on new Intel platform
Thanks Timo! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907160 Title: intel-hid is not loaded on new Intel platform To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908677] Re: Dell Latitude 9510 capture volume is too low
Upload debdiff for focal. ** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu0.6.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1908677/+attachment/5444875/+files/alsa-ucm-conf_1.2.2-1ubuntu0.6.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908677 Title: Dell Latitude 9510 capture volume is too low To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
** Also affects: system76 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908699] [NEW] New bugfix release 20.2.6
Public bug reported: [Impact] This is the last point-release of the 20.2.x-series, we should put it in groovy so latest bugfixes would get there, and for focal because that would minimize the risk of regressions when going from 20.0.x to 20.2.x. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mesa (Ubuntu Focal) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Affects: mesa (Ubuntu Groovy) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Also affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Changed in: mesa (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Groovy) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Description changed: [Impact] This is the last point-release of the 20.2.x-series, we should put it in groovy so latest bugfixes would get there, and for focal because that would minimize the risk of regressions when going from 20.0.x to 20.2.x. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. - [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this - update. + update, since upstream and vendor (Intel) CI machinery have tested + these. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908699 Title: New bugfix release 20.2.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906515] Re: Bluetooth : No device found (rtl8822cu)
End of the output of : make -j`nproc` deb-pkg I don't now how to join the total output (longer as my terminal) But on another place on the someone with kernel errors compilations says to use : make -j$(nproc) bindeb-pkg and not make -j`nproc` deb-pkg With "make -j$(nproc) bindeb-pkg" I have no error. Should I do that ? ** Attachment added: "end ogf output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906515/+attachment/5444876/+files/outut.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906515 Title: Bluetooth : No device found (rtl8822cu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908535] Re: Xorg crash after clean Ubuntu 20.10 install on Intel system
I found the ID in /var/crash/_usr_lib_xorg_Xorg.0.uploaded ID: c77eb797-4110-11eb-8995-fa163e6cac46 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908535 Title: Xorg crash after clean Ubuntu 20.10 install on Intel system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908535] Re: Xorg crash after clean Ubuntu 20.10 install on Intel system
The page is empty "no errors reported from this system" But whoopsie-id: b744c83b79ee4cccf7a0b4df8befd415349bf7a3c7812ca07ae97fffe4e2e1f6c3e6948c17804619bd89042abaa65cba74d7a2f997c74edb893fd356abf6abe7 https://errors.ubuntu.com/oops/c77eb797-4110-11eb-8995-fa163e6cac46 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908535 Title: Xorg crash after clean Ubuntu 20.10 install on Intel system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1908535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908335] Re: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908335 Title: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907200] Re: rtwpci driver blocks the system to enter PC10, stuck at PC3
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907200 Title: rtwpci driver blocks the system to enter PC10, stuck at PC3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1907200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906770] Re: Kernel 5.4.0-56 Wi-Fi does not connect
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906770 Title: Kernel 5.4.0-56 Wi-Fi does not connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894618] Re: samba vfs glusterfs shares do not work because glusterfs.so is missing from samba-vfs-modules
Will there be a package with vfs_glusterfs for Ubuntu 20.04 Focal in near future? Or does anyone have built a vfs_glusterfs package for Focal in the meantime? It is really annoying that - in difference to Redhat - no separate binary package for this VFS module is available. Yes, it makes sense, not putting it into main - but as separate package to universe - why not? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894618 Title: samba vfs glusterfs shares do not work because glusterfs.so is missing from samba-vfs-modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1894618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888473] Re: GUI does not start, only if started from command line
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pychess (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/1888473 Title: GUI does not start, only if started from command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pychess/+bug/1888473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471723] Re: systemctl completion is slow
For me the main issue is 'journalctl -u '. Not always, but often this takes very long. I just time a run of 38 seconds, on a 8 core 32GB machine. A process called 'journalctl -F _SYSTEMD_UNIT' takes 100% CPU doing it. If systemd is going to replace traditional rotated log files where you can just do 'cat logfile|grep', this kind of thing should really be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471723 Title: systemctl completion is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1471723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888473] Re: GUI does not start, only if started from command line
Same here on Ubuntu 20.04(.1). For me it seems like an incompatibility with gnuchess (gnuchessu). I had to uninstall package gnuchess, delete pychess config files (~/.config/pychess, ~/.local/share/pychess) and re- run pychess. All works then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888473 Title: GUI does not start, only if started from command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pychess/+bug/1888473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882503] Re: eeh-basic.sh in powerpc from ubuntu_kernel_selftests timeout with 5.4 P8 / P9
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882503 Title: eeh-basic.sh in powerpc from ubuntu_kernel_selftests timeout with 5.4 P8 / P9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906515] Re: Bluetooth : No device found (rtl8822cu)
I tried some new builds with the new command "make -j$(nproc) bindeb-pkg" and all works. I continue the process now... What should I answer to this every time I get this question ? I only give "ENTER" on the keyboard. Is this true ? Realtek devices (WLAN_VENDOR_REALTEK) [Y/n/?] y Realtek 8180/8185/8187SE PCI support (RTL8180) [N/m/?] n Realtek 8187 and 8187B USB support (RTL8187) [N/m/?] n RTL8723AU/RTL8188[CR]U/RTL819[12]CU (mac80211) support (RTL8XXXU) [N/m/?] n * * Realtek 802.11ac wireless chips support * Realtek 802.11ac wireless chips support (RTW88) [M/n/?] m Realtek 8822BE PCI wireless network adapter (RTW88_8822BE) [N/m/?] n Realtek 8822CE PCI wireless network adapter (RTW88_8822CE) [M/n/?] m Realtek 8723DE PCI wireless network adapter (RTW88_8723DE) [N/m/?] n Realtek 8821CE PCI wireless network adapter (RTW88_8821CE) [N/m/?] (NEW) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906515 Title: Bluetooth : No device found (rtl8822cu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882503] Re: eeh-basic.sh in powerpc from ubuntu_kernel_selftests timeout with 5.4 P8 / P9
** Description changed:
+ [Impact]
+ The breakable devices test is hardware-dependent. In our test pool
+ it will take about:
+ * 30 seconds to run on a Power8 system that with 5 breakable devices,
+ * 60 seconds to run on a Power9 system that with 4 breakable devices.
+
+ The default 45 seconds kselftest framework timeout is not enough to
+ allow this test to finish on some nodes. Thus causing this test to
+ fail with TIMEOUT error.
+
+ [Fix]
+ * f5eca0b279117f ("selftests/powerpc/eeh: disable kselftest timeout
+ setting for eeh-basic")
+
+ We have this testcase since Focal, and this patch can be cherry-picked
+ into all afffected releases.
+
+ [Test case]
+ Run this test on P9 node baltar, on which this timeout issue can be
+ 100% reprocuded. With this patch applied, the test can finish without
+ being terminated by the default timeout.
+
+ [Where problems could occur]
+ This will make test takes longer to finish, but it's still being
+ controlled by the timeout mechanism both in the test case and
+ kselftest framework. It's unlikely to make the test hang forever.
+
+
+ == Original Bug Report ==
Issue found on 5.4.0-34.38, Focal P9 "baltar"
- # selftests: powerpc/eeh: eeh-basic.sh
- # :00:00.0, Skipped: bridge
- # 0001:00:00.0, Skipped: bridge
- # 0002:00:00.0, Skipped: bridge
- # 0002:01:00.0, Added
- # 0003:00:00.0, Skipped: bridge
- # 0003:01:00.0, Added
- # 0004:00:00.0, Skipped: bridge
- # 0004:01:00.0, Skipped: bridge
- # 0004:02:00.0, Added
- # 0005:00:00.0, Skipped: bridge
- # 0005:01:00.0, Added
- # 0030:00:00.0, Skipped: bridge
- # 0031:00:00.0, Skipped: bridge
- # 0032:00:00.0, Skipped: bridge
- # 0033:00:00.0, Skipped: bridge
- # Found 4 breakable devices...
- # Breaking 0002:01:00.0...
- # 0002:01:00.0, waited 0/60
- # 0002:01:00.0, waited 1/60
- # 0002:01:00.0, waited 2/60
- # 0002:01:00.0, waited 3/60
- # 0002:01:00.0, waited 4/60
- # 0002:01:00.0, waited 5/60
- # 0002:01:00.0, waited 6/60
- # 0002:01:00.0, Recovered after 7 seconds
- # Breaking 0003:01:00.0...
- # 0003:01:00.0, waited 0/60
- # 0003:01:00.0, waited 1/60
- # 0003:01:00.0, waited 2/60
- # 0003:01:00.0, waited 3/60
- # 0003:01:00.0, waited 4/60
- # 0003:01:00.0, waited 5/60
- # 0003:01:00.0, waited 6/60
- # 0003:01:00.0, waited 7/60
- # 0003:01:00.0, waited 8/60
- # 0003:01:00.0, waited 9/60
- # 0003:01:00.0, waited 10/60
- # 0003:01:00.0, waited 11/60
- # 0003:01:00.0, waited 12/60
- # 0003:01:00.0, waited 13/60
- # 0003:01:00.0, waited 14/60
- # 0003:01:00.0, waited 15/60
- # 0003:01:00.0, waited 16/60
- # 0003:01:00.0, waited 17/60
- # 0003:01:00.0, waited 18/60
- # 0003:01:00.0, waited 19/60
- # 0003:01:00.0, waited 20/60
- # 0003:01:00.0, waited 21/60
- # 0003:01:00.0, waited 22/60
- # 0003:01:00.0, waited 23/60
- # 0003:01:00.0, waited 24/60
- # 0003:01:00.0, waited 25/60
- # 0003:01:00.0, waited 26/60
- # 0003:01:00.0, waited 27/60
- # 0003:01:00.0, waited 28/60
- # 0003:01:00.0, waited 29/60
- # 0003:01:00.0, waited 30/60
- # 0003:01:00.0, waited 31/60
- # 0003:01:00.0, waited 32/60
- # 0003:01:00.0, waited 33/60
- # 0003:01:00.0, waited 34/60
- # 0003:01:00.0, waited 35/60
- # 0003:01:00.0, Recovered after 36 seconds
- # Breaking 0004:02:00.0...
- # 0004:02:00.0, Recovered after 0 seconds
- # Breaking 0005:01:00.0...
- # 0005:01:00.0, waited 0/60
- # 0005:01:00.0, waited 1/60
- #
- not ok 1 selftests: powerpc/eeh: eeh-basic.sh # TIMEOUT
+ # selftests: powerpc/eeh: eeh-basic.sh
+ # :00:00.0, Skipped: bridge
+ # 0001:00:00.0, Skipped: bridge
+ # 0002:00:00.0, Skipped: bridge
+ # 0002:01:00.0, Added
+ # 0003:00:00.0, Skipped: bridge
+ # 0003:01:00.0, Added
+ # 0004:00:00.0, Skipped: bridge
+ # 0004:01:00.0, Skipped: bridge
+ # 0004:02:00.0, Added
+ # 0005:00:00.0, Skipped: bridge
+ # 0005:01:00.0, Added
+ # 0030:00:00.0, Skipped: bridge
+ # 0031:00:00.0, Skipped: bridge
+ # 0032:00:00.0, Skipped: bridge
+ # 0033:00:00.0, Skipped: bridge
+ # Found 4 breakable devices...
+ # Breaking 0002:01:00.0...
+ # 0002:01:00.0, waited 0/60
+ # 0002:01:00.0, waited 1/60
+ # 0002:01:00.0, waited 2/60
+ # 0002:01:00.0, waited 3/60
+ # 0002:01:00.0, waited 4/60
+ # 0002:01:00.0, waited 5/60
+ # 0002:01:00.0, waited 6/60
+ # 0002:01:00.0, Recovered after 7 seconds
+ # Breaking 0003:01:00.0...
+ # 0003:01:00.0, waited 0/60
+ # 0003:01:00.0, waited 1/60
+ # 0003:01:00.0, waited 2/60
+ # 0003:01:00.0, waited 3/60
+ # 0003:01:00.0, waited 4/60
+ # 0003:01:00.0, waited 5/60
+ # 0003:01:00.0, waited 6/60
+ # 0003:01:00.0, waited 7/60
+ # 0003:01:00.0, waited 8/60
+ # 0003:01:00.0, waited 9/60
+ # 0003:01:00.0, waited 10/60
+ # 0003:01:00.0, waited 11/60
+ # 0003:01:00.0, waited 12/60
+ # 0003:01:00.0, waited 13/60
+ # 0003:01:00.0, waited 14/60
+ # 0003:01:00.0, waited 15/60
+ # 0003:01:00.0, waited 16/60
+ # 0003:01:00.0, waited 17/60
+ # 0003:01:00.0, waited 18/60
+ # 0003:01:00.0, waited 19/60
+ # 0003:
[Bug 1891003] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable on B-AWS-5.3
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) 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/1891003 Title: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable on B-AWS-5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1891003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891003] 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 1891003 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891003 Title: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable on B-AWS-5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1891003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908702] [NEW] aiol from ubuntu_stress_smoke_test ADT test failure with linux-hwe 4.15.0-129.132~16.04.1
Public bug reported: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux-hwe/20201217_204555_e0436@/log.gz The testcase is failing only with ppc64el, and only on xenial/linux-hwe (not on bionic/linux). 20:17:34 DEBUG| [stdout] aiol STARTING 20:17:39 DEBUG| [stdout] aiol RETURNED 2 20:17:39 DEBUG| [stdout] aiol FAILED 20:17:39 DEBUG| [stdout] stress-ng: debug: [30457] 4 processors online, 4 processors configured 20:17:39 DEBUG| [stdout] stress-ng: info: [30457] dispatching hogs: 4 aiol 20:17:39 DEBUG| [stdout] stress-ng: debug: [30457] cache allocate: reducing cache level from L3 (too high) to L1 20:17:39 DEBUG| [stdout] stress-ng: debug: [30457] cache allocate: default cache size: 64K 20:17:39 DEBUG| [stdout] stress-ng: debug: [30457] starting stressors 20:17:39 DEBUG| [stdout] stress-ng: debug: [30458] stress-ng-aiol: started [30458] (instance 0) 20:17:39 DEBUG| [stdout] stress-ng: debug: [30457] 4 stressors started 20:17:39 DEBUG| [stdout] stress-ng: debug: [30460] stress-ng-aiol: started [30460] (instance 2) 20:17:39 DEBUG| [stdout] stress-ng: debug: [30459] stress-ng-aiol: started [30459] (instance 1) 20:17:39 DEBUG| [stdout] stress-ng: debug: [30461] stress-ng-aiol: started [30461] (instance 3) 20:17:39 DEBUG| [stdout] stress-ng: fail: [30461] stress-ng-aiol: data mismatch in buffer 0 20:17:39 DEBUG| [stdout] stress-ng: fail: [30461] stress-ng-aiol: data mismatch in buffer 1 20:17:39 DEBUG| [stdout] stress-ng: fail: [30461] stress-ng-aiol: data mismatch in buffer 2 20:17:39 DEBUG| [stdout] stress-ng: fail: [30461] stress-ng-aiol: data mismatch in buffer 3 20:17:39 DEBUG| [stdout] stress-ng: fail: [30461] stress-ng-aiol: data mismatch in buffer 4 20:17:39 DEBUG| [stdout] info: 5 failures reached, aborting stress process 20:17:39 DEBUG| [stdout] stress-ng: fail: [30461] stress-ng-aiol: data mismatch in buffer 5 20:17:39 DEBUG| [stdout] stress-ng: fail: [30461] stress-ng-aiol: data mismatch in buffer 6 20:17:39 DEBUG| [stdout] stress-ng: debug: [30460] stress-ng-aiol: exited [30460] (instance 2) 20:17:39 DEBUG| [stdout] stress-ng: debug: [30458] stress-ng-aiol: exited [30458] (instance 0) 20:17:39 DEBUG| [stdout] stress-ng: debug: [30457] process [30458] terminated 20:17:39 DEBUG| [stdout] stress-ng: debug: [30459] stress-ng-aiol: exited [30459] (instance 1) 20:17:39 DEBUG| [stdout] stress-ng: debug: [30457] process [30459] terminated 20:17:39 DEBUG| [stdout] stress-ng: debug: [30457] process [30460] terminated 20:17:39 DEBUG| [stdout] stress-ng: debug: [30461] stress-ng-aiol: exited [30461] (instance 3) 20:17:39 DEBUG| [stdout] stress-ng: error: [30457] process 30461 (stress-ng-aiol) terminated with an error, exit status=1 (stress-ng core failure) 20:17:39 DEBUG| [stdout] stress-ng: debug: [30457] process [30461] terminated 20:17:39 DEBUG| [stdout] stress-ng: info: [30457] unsuccessful run completed in 5.13s 20:17:39 DEBUG| [stdout] stress-ng: debug: [30457] metrics-check: all stressor metrics validated and sane This is likely a testcase issue, probably caused by https://github.com/ColinIanKing/stress- ng/commit/08d42b48c4cb8c116a7644bb3485d3ef3d77c701. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-hwe (Ubuntu Xenial) Importance: Undecided Status: Confirmed ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - linux-hwe 4.15.0-129.132~16.04.1 ADT test failure with linux-hwe 4.15.0-129.132~16.04.1 + aiol from ubuntu_stress_smoke_test ADT test failure with linux-hwe 4.15.0-129.132~16.04.1 ** Also affects: linux-hwe (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: Testing failed on: - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/linux-hwe/20201217_184643_e5c8e@/log.gz - i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux-hwe/20201217_155813_9f14d@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux-hwe/20201217_204555_e0436@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux-hwe/20201217_135357_de17e@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux-hwe/20201217_204555_e0436@/log.gz + + The testcase is failing only with ppc64el, and only on xenial/linux-hwe + (not on bionic/linux). + + 20:17:34 DEBUG| [stdout] aiol STARTING + 20:17:39 DEBUG| [stdout] aiol
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Helmut Stult (helmut-stult) I got it working both on Manjaro and Gentoo with kernel 5.10.1 downloaded from kernel.org with #189. On Gentoo I had to use Manjaro's running .config obtained with make localmodconfig while in chroot from manjaro. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892860] Re: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B-arm64
I can see this on B-azure-fips 4.15 with instance Standard_D48_v3 only -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892860 Title: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B-arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891003] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable on B-AWS-5.3
** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891003 Title: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable on B-AWS-5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1891003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882669] Re: Focal / Groovy Azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
Found on F-azure 5.4.0-1035.36 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882669 Title: Focal / Groovy Azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908608] Re: Crash to login screen when plugging in/out external monitor
Thanks for taking a look. I see. Found it - UUID from crash.uploaded: 362c2716-4051-11eb- 8be3-fa163ee63de6 Thank you for the suggestion. Did you spot any specific indication that that extension was the source of the crash? Anyway, if you do, I can reach out to them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908608 Title: Crash to login screen when plugging in/out external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound
*** This bug is a duplicate of bug 1797002 *** https://bugs.launchpad.net/bugs/1797002 I understand. I was assuming that gnome-shell was big enough to warrant at least one person who could view private reports, and that the message suggested a mistake. Thanks for the info. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908064 Title: [Multiple bluetooth speakers, playback] Stuttering sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908699] Re: New bugfix release 20.2.6
** Changed in: mesa (Ubuntu Groovy) Status: New => In Progress ** Changed in: mesa (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908699 Title: New bugfix release 20.2.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908608] Re: Crash to login screen when plugging in/out external monitor
Just a FYI, I'm a bit confused regarding the ID. The .uploaded file has a timestamp earlier than the .crash file (about 12 hours earlier than when I actually experienced the crash most recently) and the .uploaded file doesn't change its contents after running ubuntu-bug, even as superuser. It doesn't appear to correspond to the actual upload? Or am I just tricked by some sort of deduplication mechanism that prevents subsequent uploads of identical crashes? If so I guess it's the correct ID since I've experienced it multiple times, but can't really be sure since I don't have permission to inspect the uploaded file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908608 Title: Crash to login screen when plugging in/out external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882669] Re: Focal Azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
This issue does not exist on G-azure 5.8.0-1016.17. Closing corresponding groovy task. ** Summary changed: - Focal / Groovy Azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test + Focal Azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test ** Changed in: linux-azure (Ubuntu Groovy) Status: New => Fix Released ** No longer affects: linux-azure-5.4 (Ubuntu) ** No longer affects: linux-azure-5.4 (Ubuntu Focal) ** No longer affects: linux-azure-5.4 (Ubuntu Groovy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882669 Title: Focal Azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908050] Re: Support post install enablement of OEM-enabled devices
Hello Iain, or anyone else affected, Accepted update-manager into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update- manager/1:20.04.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: update-manager (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908050 Title: Support post install enablement of OEM-enabled devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1908050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901627] Re: Update product naming: Simplify UA Infrastructure ESM to UA Infra: ESM
this bug is blocking another update, so please verify it ASAP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901627 Title: Update product naming: Simplify UA Infrastructure ESM to UA Infra: ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1901627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908706] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: il sottoprocesso installato pacchetto initramfs-tools script post-installation ha restituito lo stato di errore 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908706 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: il sottoprocesso installato pacchetto initramfs-tools script post- installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1908706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908706] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: il sottoprocesso installato pacchetto initramfs-tools script post-installation ha restituito lo stato di errore 1
Public bug reported: while do-release-upgrade from 18.04 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 18 12:22:57 2020 ErrorMessage: il sottoprocesso installato pacchetto initramfs-tools script post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2013-12-11 (2564 days ago) InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: il sottoprocesso installato pacchetto initramfs-tools script post-installation ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to focal on 2020-12-18 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908706 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: il sottoprocesso installato pacchetto initramfs-tools script post- installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1908706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863434] Re: 20.04 grub menu not visible
I ran into the same problem, and found the solution. Initially in grub2 the configuration is set to GRUB_GFXMODE=auto. On several systems grub seems to be unable to autodetect the proper resolution. (In grub console "videoinfo" returned no (!) output on my system.) After altering to GRUB_GFXMODE=1280x800 which is the known resolution of my screen, yours may differ of course, my lovely bootmenu (don't forget to run update-grub after altering the config file) was visible again. Formerly grub's default configuration seemed to be GRUB_TERMINAL= console, which now has been commented out. That leads to a nice output (as grub themes are supported) if it works. If not, it leads into the dark... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906515] Re: Bluetooth : No device found (rtl8822cu)
I finished the process after 13 kernel compilation. Here is the last output. What should I do now ? meloli@Asus-A17:~/Bureau/meloli/GITBISECT/linux$ git bisect bad b2cc23398e8166b38f8715026273503b081c2a7a is the first bad commit commit b2cc23398e8166b38f8715026273503b081c2a7a Author: Sathish Narasimman Date: Thu Jul 23 18:09:02 2020 +0530 Bluetooth: Enable RPA Timeout Enable RPA timeout during bluetooth initialization. The RPA timeout value is used from hdev, which initialized from debug_fs Signed-off-by: Sathish Narasimman Signed-off-by: Marcel Holtmann include/net/bluetooth/hci.h | 2 ++ net/bluetooth/hci_core.c| 8 2 files changed, 10 insertions(+) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906515 Title: Bluetooth : No device found (rtl8822cu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906364] Re: [SRU] unattended-upgrade still restarts blacklisted daemons
Hello sascha, or anyone else affected, Accepted docker.io into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/19.03.13-0ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker.io (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Re: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon
Hello Bernd, or anyone else affected, Accepted docker.io into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/19.03.13-0ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker.io (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870514 Title: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908708] [NEW] dh_strip: sh: 1: Syntax error: "(" unexpected
Public bug reported:
dh_strip in debhelper 13.3ubuntu3 (currently in hirsute-proposed) fails
with error:
sh: 1: Syntax error: "(" unexpected
dh_strip: error: lto-no-text-in-archive:
debian/libfoo3-dev/usr/lib/s390x-linux-gnu/libfoo.a
dh_strip: error: Aborting due to earlier error
The diff [1] with the previous revision does indeed show a change in a
dh_strip regexp.
[1]
https://launchpadlibrarian.net/511780702/debhelper_13.3ubuntu2_13.3ubuntu3.diff.gz
** Affects: debhelper (Ubuntu)
Importance: High
Status: New
** Tags: 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/1908708
Title:
dh_strip: sh: 1: Syntax error: "(" unexpected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1908708/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908708] Re: dh_strip: sh: 1: Syntax error: "(" unexpected
Random build log showing the failure:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-hirsute/hirsute/s390x/d/dh-ada-
library/20201218_035409_93407@/log.gz
** 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/1908708
Title:
dh_strip: sh: 1: Syntax error: "(" unexpected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1908708/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound
*** This bug is a duplicate of bug 1797002 *** https://bugs.launchpad.net/bugs/1797002 ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443423/+files/AlsaInfo.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443424/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443425/+files/Dependencies.txt ** Attachment removed: "PaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443426/+files/PaInfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443427/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443428/+files/PulseList.txt ** Attachment removed: "Symptom_PulseAudioLog.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+attachment/5443429/+files/Symptom_PulseAudioLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908064 Title: [Multiple bluetooth speakers, playback] Stuttering sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906364] Re: [SRU] unattended-upgrade still restarts blacklisted daemons
Hello sascha, or anyone else affected, Accepted docker.io into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/19.03.8-0ubuntu1.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker.io (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal ** Changed in: docker.io (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906364] Please test proposed package
Hello sascha, or anyone else affected, Accepted docker.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/19.03.6-0ubuntu1~18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908710] [NEW] errinjct open fails on IBM POWER LPAR
Public bug reported: [Impact] errinjct open fails on IBM POWER LPAR. That prevents error injection tests to be performed. [Test case] Run errinjct open on an LPAR. Success case: $ sudo errinjct open RTAS error injection facility open, token = 1 Failure case: [Fix] Typo in RTAS filters. [Regression potential] errinjct could still be broken, or other RTAS operations could break, which could even prevent booting on any IBM POWER systems. ** Affects: linux (Ubuntu) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Confirmed ** Affects: linux (Ubuntu Groovy) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Groovy) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) 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/1908710 Title: errinjct open fails on IBM POWER LPAR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906364] Re: [SRU] unattended-upgrade still restarts blacklisted daemons
Hello sascha, or anyone else affected, Accepted docker.io into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/18.09.7-0ubuntu1~16.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker.io (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Re: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon
Hello Bernd, or anyone else affected, Accepted containerd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.3.7-0ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: containerd (Ubuntu Groovy) Status: Confirmed => Fix Committed ** Changed in: containerd (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870514 Title: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Please test proposed package
Hello Bernd, or anyone else affected, Accepted containerd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.3.3-0ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker.io (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870514 Title: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Please test proposed package
Hello Bernd, or anyone else affected, Accepted docker.io into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/19.03.8-0ubuntu1.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker.io (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870514 Title: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Please test proposed package
Hello Bernd, or anyone else affected, Accepted docker.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/19.03.6-0ubuntu1~18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: containerd (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870514 Title: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Please test proposed package
Hello Bernd, or anyone else affected, Accepted containerd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.3.3-0ubuntu1~18.04.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: containerd (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870514 Title: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Please test proposed package
Hello Bernd, or anyone else affected, Accepted containerd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/1.2.6-0ubuntu1~16.04.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker.io (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870514 Title: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Please test proposed package
Hello Bernd, or anyone else affected, Accepted docker.io into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/18.09.7-0ubuntu1~16.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870514 Title: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Re: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon
fixed in hirsute by 1.3.7-0ubuntu5 ** Changed in: containerd (Ubuntu Hirsute) 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/1870514 Title: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737351] Re: package intltool-debian 0.35.0+20060710.4 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.
. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737351 Title: package intltool-debian 0.35.0+20060710.4 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intltool-debian/+bug/1737351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695745] Re: package intltool-debian 0.35.0+20060710.4 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.
. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695745 Title: package intltool-debian 0.35.0+20060710.4 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intltool-debian/+bug/1695745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906515] Re: Bluetooth : No device found (rtl8822cu)
$ git checkout b2cc23398e8166b38f8715026273503b081c2a7a # build kernel and test, make sure it's bad $ git checkout b2cc23398e8166b38f8715026273503b081c2a7a^ # build kernel and test, make sure it's good If we are sure b2cc23398e8166b38f8715026273503b081c2a7a is the offending commit, let's report back to upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906515 Title: Bluetooth : No device found (rtl8822cu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908710] Re: errinjct open fails on IBM POWER LPAR
** Description changed: [Impact] errinjct open fails on IBM POWER LPAR. That prevents error injection tests to be performed. [Test case] Run errinjct open on an LPAR. Success case: $ sudo errinjct open RTAS error injection facility open, token = 1 Failure case: + $ sudo errinjct open + errinjct: Could not open RTAS error injection facility + + errinjct: librtas: open: Unexpected I/O error + [Fix] Typo in RTAS filters. [Regression potential] errinjct could still be broken, or other RTAS operations could break, which could even prevent booting on any IBM POWER systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908710 Title: errinjct open fails on IBM POWER LPAR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818403] Re: cups-pdf ld.so: object 'libsets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file)
Unfortunately, I can no longer check that. I upgraded to Ubuntu 20.04.1 and the problem no longer exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818403 Title: cups-pdf ld.so: object 'libsets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-pdf/+bug/1818403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908713] [NEW] Fix suspend error of SOF driver
Public bug reported: [Impact] SOF driver in oem-5.6 kernel tries to access HDA codec register when the codec is already suspended. This may freeze suspend. [Fix] Revert HDA codec PM direct-complete optimization. The same suspend optimization works perfectly on 5.8 and 5.10 kernel, so something's wrong in the SOF driver in oem-5.6. However, SOF in oem-5.6 is in Frankenstein state so we better not touch it. [Test] Suspend a laptop with SOF driver, it can take 30 seconds to suspend, or worse, it freezes. With the patch applied, it can suspend in 1 second. [Regression Risk] For HDA codecs that benefit from this PM optimization, it'll take longer to suspend and resume. Nothing else changes other than that. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: High Status: Confirmed ** Tags: oem-priority originate-from-1908495 stella ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided => High ** Tags added: oem-priority originate-from-1908495 stella -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908713 Title: Fix suspend error of SOF driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908710] Re: errinjct open fails on IBM POWER LPAR
** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908710 Title: errinjct open fails on IBM POWER LPAR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907815] Re: preinstall `plasma-disks` by default
This has now been synced from debian experimental to hirsute. I will add it to our seeds/meta once it is available in the release pocket. ** Also affects: kubuntu-meta (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: kubuntu-meta (Ubuntu Hirsute) Status: New => In Progress ** Changed in: kubuntu-meta (Ubuntu Hirsute) Assignee: (unassigned) => Rik Mills (rikmills) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907815 Title: preinstall `plasma-disks` by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1907815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906250] Re: Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using qemu-s390x on x86_64.
Yes this is a different fix in Focal, but it fixes the actual endianness problem rather than improving the corruption check. In my testing that resolved the reported issue, please give a try to the newly build cross packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906250 Title: Segmentation fault in s390x ld.so while parsing /etc/ld.so.cache using qemu-s390x on x86_64. To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1906250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908715] [NEW] something
Public bug reported: Install failed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 18 14:11:07 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=de_CH.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908715 Title: something To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1908715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908717] Re: Black screen with blinking cursor
Just to point out I have power-cycled my laptop in case a reboot wasn't cutting it. Also, I can switch TTY no problem, that's how I'm starting the window manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908717 Title: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908717] [NEW] Black screen with blinking cursor
Public bug reported: For some reason, since today GDM has ceased to work. No updates came through as last time I installed any updates was a week ago. Upon boot, gdm goes to a black screen with a cursor. This screen flickers to show the underlying tty and on each flicker the cursor position resets. I can start my window manager (sway) without issue from the console still and everything functions normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: sway Date: Fri Dec 18 13:44:09 2020 SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908717 Title: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904922] Re: External monitor undetected over hdmi
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10/amd64/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904922 Title: External monitor undetected over hdmi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894618] Re: samba vfs glusterfs shares do not work because glusterfs.so is missing from samba-vfs-modules
Beside all of the good reasons given, this is an issue blocking several users that should be considered for a permanent solution as a matter of priority. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894618 Title: samba vfs glusterfs shares do not work because glusterfs.so is missing from samba-vfs-modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1894618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894618] Re: samba vfs glusterfs shares do not work because glusterfs.so is missing from samba-vfs-modules
Just wondering the same, is a package ever going to be made available? If GlusterFS cannot be made available in 'main' why not make vfs_glusterfs as part of the gluster package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894618 Title: samba vfs glusterfs shares do not work because glusterfs.so is missing from samba-vfs-modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1894618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908717] Re: Black screen with blinking cursor
If I leave GDM3 like that for a while (around 30 secs or so) it will eventually terminate and drop to the underlying tty. Conversely, lightdm is working correctly. I can use that for the time being. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908717 Title: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Autopkgtest regression report (containerd/1.2.6-0ubuntu1~16.04.6)
All autopkgtests for the newly accepted containerd (1.2.6-0ubuntu1~16.04.6) for xenial have finished running. The following regressions have been reported in tests triggered by the package: docker.io/18.09.7-0ubuntu1~16.04.7 (amd64, arm64, s390x, i386, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/xenial/update_excuses.html#containerd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870514 Title: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906364] Autopkgtest regression report (docker.io/18.09.7-0ubuntu1~16.04.7)
All autopkgtests for the newly accepted docker.io (18.09.7-0ubuntu1~16.04.7) for xenial have finished running. The following regressions have been reported in tests triggered by the package: docker.io/18.09.7-0ubuntu1~16.04.7 (amd64, arm64, s390x, i386, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/xenial/update_excuses.html#docker.io [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Autopkgtest regression report (docker.io/18.09.7-0ubuntu1~16.04.7)
All autopkgtests for the newly accepted docker.io (18.09.7-0ubuntu1~16.04.7) for xenial have finished running. The following regressions have been reported in tests triggered by the package: docker.io/18.09.7-0ubuntu1~16.04.7 (amd64, arm64, s390x, i386, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/xenial/update_excuses.html#docker.io [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870514 Title: [SRU] update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850294] Re: ICA HW token missing after the package update
Looks to me that the two commits do not fit to the bionic version of opencryptoki, which is: opencryptoki | 3.9.0+dfsg-0ubuntu1.3 | bionic-updates/universe because the two files (ica_s390_stdll/ica_specific.c, ep11_stdll/ep11_specific.c) do not come with an define "libica.so" line at all and at github one can see that the patches landed only in v3.15.1 v3.15.0 v3.14.0 v3.13.0 v3.12.1 v3.12.0. Hence I assume that the problem reported here does not affect bionic, is that correct? ** Changed in: opencryptoki (Ubuntu Bionic) Status: New => Incomplete ** Changed in: ubuntu-z-systems Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850294 Title: ICA HW token missing after the package update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1850294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908721] [NEW] autopkgtest fails in hirsute
Public bug reported: https://autopkgtest.ubuntu.com/packages/g/golang-github-azure-azure-sdk- for-go/hirsute/s390x Triggered with hello: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/s390x/g/golang-github-azure-azure-sdk-for-go/20201216_213855_c8ce8@/log.gz ... dh_auto_build -O--buildsystem=golang found packages filesystem (client.go) and datalakestore (version.go) in /tmp/autopkgtest.XkghEn/autopkgtest_tmp/obj-s390x-linux-gnu/src/github.com/Azure/azure-sdk-for-go/datalake-store/filesystem cd obj-s390x-linux-gnu && go install -trimpath -v -p 1 package .: no Go files in /tmp/autopkgtest.XkghEn/autopkgtest_tmp/obj-s390x-linux-gnu dh_auto_build: error: cd obj-s390x-linux-gnu && go install -trimpath -v -p 1 returned exit code 1 make: *** [debian/rules:11: build] Error 25 autopkgtest [21:38:42]: test dh-golang-autopkgtest: ---] autopkgtest [21:38:43]: test dh-golang-autopkgtest: - - - - - - - - - - results - - - - - - - - - - dh-golang-autopkgtest FAIL non-zero exit status 2 ... ** Affects: golang-github-azure-azure-sdk-for-go (Ubuntu) Importance: Undecided Status: New ** Tags: 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/1908721 Title: autopkgtest fails in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-azure-azure-sdk-for-go/+bug/1908721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1908446] Re: Wifi disconnecting and reconnecting over and over (Ubuntu 20.04 LTS)
*** This bug is a duplicate of bug 1908445 *** https://bugs.launchpad.net/bugs/1908445 Update did not solve the problem, still disconnecting Em qui., 17 de dez. de 2020 às 07:41, Hans Joachim Desserud < 1908...@bugs.launchpad.net> escreveu: > *** This bug is a duplicate of bug 1908445 *** > https://bugs.launchpad.net/bugs/1908445 > > ** This bug has been marked a duplicate of bug 1908445 >Wifi disconnecting and reconnecting over and over (Ubuntu 20.04 LTS) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1908446 > > Title: > Wifi disconnecting and reconnecting over and over (Ubuntu 20.04 LTS) > > Status in ubuntu-release-upgrader package in Ubuntu: > New > > Bug description: > After a system update my wifi got bugged and randomly disconnects, I > believe it is something in the Kernel > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: ubuntu-release-upgrader-core 1:20.04.29 > ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 > Uname: Linux 5.4.0-56-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.13 > Architecture: amd64 > CasperMD5CheckResult: skip > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > Date: Wed Dec 16 18:18:13 2020 > InstallationDate: Installed on 2020-06-16 (183 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > PackageArchitecture: all > SourcePackage: ubuntu-release-upgrader > Symptom: release-upgrade > UpgradeStatus: No upgrade log present (probably fresh install) > VarLogDistupgradeTermlog: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908446/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908446 Title: Wifi disconnecting and reconnecting over and over (Ubuntu 20.04 LTS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908445] Re: Wifi disconnecting and reconnecting over and over (Ubuntu 20.04 LTS)
Update did not solve the problem, still disconnecting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908445 Title: Wifi disconnecting and reconnecting over and over (Ubuntu 20.04 LTS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1908445] Re: Wifi disconnecting and reconnecting over and over (Ubuntu 20.04 LTS)
Update did not solve the problem, still disconnecting Em qua., 16 de dez. de 2020 às 21:15, Ubuntu Foundations Team Bug Bot < 1908...@bugs.launchpad.net> escreveu: > ** Package changed: ubuntu => ubuntu-release-upgrader (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1908445 > > Title: > Wifi disconnecting and reconnecting over and over (Ubuntu 20.04 LTS) > > Status in ubuntu-release-upgrader package in Ubuntu: > New > > Bug description: > After a system update my wifi got bugged and randomly disconnects, I > believe it is something in the Kernel > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: ubuntu-release-upgrader-core 1:20.04.29 > ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 > Uname: Linux 5.4.0-56-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.13 > Architecture: amd64 > CasperMD5CheckResult: skip > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > Date: Wed Dec 16 18:18:13 2020 > InstallationDate: Installed on 2020-06-16 (183 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > PackageArchitecture: all > SourcePackage: ubuntu-release-upgrader > Symptom: release-upgrade > UpgradeStatus: No upgrade log present (probably fresh install) > VarLogDistupgradeTermlog: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908445/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908445 Title: Wifi disconnecting and reconnecting over and over (Ubuntu 20.04 LTS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906515] Re: Bluetooth : No device found (rtl8822cu)
I have built the 2 kernels and can confirm that b2cc23398e8166b38f8715026273503b081c2a7a is the offending commit. I have already opened a bug report here : https://bugzilla.kernel.org/show_bug.cgi?id=210453 Is this the good way ? What should I add more ? ** Bug watch added: Linux Kernel Bug Tracker #210453 https://bugzilla.kernel.org/show_bug.cgi?id=210453 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906515 Title: Bluetooth : No device found (rtl8822cu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587154] Re: --working-directory does not work anymore
--working-directory still not working. Opens a tab at the home directory not at the specified directory. gnome-terminal --window --working-directory="~/any/path" will open a window at home directory Any work around atm? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587154 Title: --working-directory does not work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1587154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908721] Re: autopkgtest fails in hirsute
** Merge proposal linked: https://code.launchpad.net/~rbalint/britney/+git/hints-ubuntu/+merge/395510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908721 Title: autopkgtest fails in hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-azure-azure-sdk-for-go/+bug/1908721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908574] Re: autopkgtest fails in hirsute on s390x
** Merge proposal linked: https://code.launchpad.net/~rbalint/britney/+git/hints-ubuntu/+merge/395510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908574 Title: autopkgtest fails in hirsute on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-http/+bug/1908574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908725] [NEW] Update the package for Focal Fossa to >= 2.5.3
Public bug reported: The current Darktable from the Focal Fossa repo can't be upgraded because it requires libopenexr25 (>= 2.5.3) and the currently available one is libopenexr24/focal-updates,focal-security,now 2.3.0-6ubuntu0.2 Can you please update it to >=2.5.3 ? $ sudo apt upgrade darktable Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: darktable : Depends: libexiv2-27 (>= 0.27.3) but 0.27.2-8ubuntu2 is to be installed Depends: libilmbase25 (>= 2.5.3) but it is not installable Depends: libjson-glib-1.0-0 (>= 1.5.2) but 1.4.4-2ubuntu2 is to be installed Depends: libopenexr25 (>= 2.5.3) but it is not installable E: Broken packages ** Affects: openexr (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908725 Title: Update the package for Focal Fossa to >= 2.5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1908725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897405] Re: fastqc FTBFS due to libsis-jhdf5-java FTBFS
No migration is blocked on libsis-jhdf5-java failing tests due to not having enough memory. The test pass locally and the test script is telling, too: java -Xmx2048M ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897405 Title: fastqc FTBFS due to libsis-jhdf5-java FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fastqc/+bug/1897405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898494] Re: ubiquity in Ubuntu 20.04 Deprecation warning
** Changed in: ubiquity (Ubuntu) Status: New => Triaged ** Changed in: ubiquity (Ubuntu) Importance: Undecided => Low ** Merge proposal linked: https://code.launchpad.net/~ubuntu-installer/ubiquity/+git/ubiquity/+merge/395535 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898494 Title: ubiquity in Ubuntu 20.04 Deprecation warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1898494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897405] Re: fastqc FTBFS due to libsis-jhdf5-java FTBFS
** Merge proposal linked: https://code.launchpad.net/~rbalint/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/395536 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897405 Title: fastqc FTBFS due to libsis-jhdf5-java FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fastqc/+bug/1897405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908726] [NEW] Update the package for Focal Fossa to >= 0.27.3
Public bug reported: The current Darktable from the Focal Fossa repo can't be upgraded because it requires libexiv2-27 (>= 0.27.3) and the currently available one is libexiv2-27/0.27.2-8ubuntu2 Can you please update it to >= 0.27.3 ? $ sudo apt upgrade darktable Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: darktable : Depends: libexiv2-27 (>= 0.27.3) but 0.27.2-8ubuntu2 is to be installed Depends: libilmbase25 (>= 2.5.3) but it is not installable Depends: libjson-glib-1.0-0 (>= 1.5.2) but 1.4.4-2ubuntu2 is to be installed Depends: libopenexr25 (>= 2.5.3) but it is not installable E: Broken packages ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908726 Title: Update the package for Focal Fossa to >= 0.27.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1908726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860640] Re: Add / Enable "32Bit UEFI Support" in Ubuntu?
** Description changed: Hi there! I want to add here a request regarding the addition of a very nice, currently Fedora-exclusive, feature. It's called "32Bit UEFI Support" and makes it possible to boot and install a 64bit Linux onto a 32 bit (U)EFI based system which contains a 64bit CPU. Source: https://fedoraproject.org/wiki/Changes/32BitUefiSupport So far I understand, this works through a special modified BOOTIA32.EFI file. That one acts as some kind of a "wrapper" which converts some (essential) EFI64 calls to EFI32 (during the boot-up). I have tested this principle with latest Fedora 31 at an early Intel iMac which contains a 64bit CPU but has a 32bit EFI. To my big surprise it works absolutely GREAT! There exist currently some ways to apply this principle also at other Linux Distros like Ubuntu and Debian. Unfortunately these are all quite complex and needs a lot of modifications. More information can be found at the following link: https://medium.com/@realzedgoat/a-sorta-beginners-guide-to-installing- ubuntu-linux-on-32-bit-uefi-machines-d39b1d1961ec I tried to modify a Kubuntu 18.04 LTS DVD ISO image but I failed. Fedora Linux uses a quite different DVD install layout (folder & file organization) which is not easy applicable at Ubuntu / Debian based Distros. In detail I tried to copy the mentioned BOOTIA32.EFI wrapper file into the /EFI/boot directory. Well, the edited / modified Kubuntu DVD image was not recognized by the 32bit EFI firmware (at an iMac). I have uploaded some of the needed files. Fedora seems to include also a special macboot.img file which is not present (in that form) in Ubuntu. + Update 18.12.2020: + The following link shows a step-by-step guide how an installation can be done with latest Ubuntu / Kubuntu 20.04 LTS: https://wiki.ubuntuusers.de/Howto/32-Bit_EFI/ + + As mentioned in my initial request the main problem lies in the missing + grubia32.efi file. That one is unfortunately not included at current + Ubuntu 64 bit x86-64 install medias. So it is needed to add it from + another Distro like Debian 10. + + Note, Debian supports that "64bit CPU & 32bit EFI" install option since + Version 8: https://wiki.debian.org/UEFI#Support_for_mixed- + mode_systems:_64-bit_system_with_32-bit_UEFI + Kind regards C. Leu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860640 Title: Add / Enable "32Bit UEFI Support" in Ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1860640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908512] Re: VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso
I don't have issue to boot the debian-10.7.0-amd64-DVD-1.iso -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908512 Title: VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1908512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
