[Bug 1976587] [NEW] Fix can't boot up after change to vmd
Public bug reported: [Impact] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976587 Title: Fix can't boot up after change to vmd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976230] Re: Backport 2022.1-1-0ubuntu1 to jammy
I verified xlnx-firmware (2022.1-1-0ubuntu1~22.04.1) on my zcu102. boot1021.bin, boot1041.bin, boot1021.bin, boot1061.bin, boot.bin in /boot/firmware get updated after upgrading xlnx-firmware to 2022.1-1-0ubuntu1~22.04.1. System can boot without any problems with new bootX.bin. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976230 Title: Backport 2022.1-1-0ubuntu1 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xlnx-firmware/+bug/1976230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)
*** This bug is a duplicate of bug 1956915 *** https://bugs.launchpad.net/bugs/1956915 Verified internally with Ubuntu 20.04.4 + libegl-mesa0 version "21.2.6-0ubuntu0.1~20.04.2" and confirmed the crash issue is resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946621 Title: Crash in libegl-mesa0 (eglReleaseThread) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1946621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976556] Re: [Lenovo 300e 2nd GEN] ELAN Touchpad not working
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1976556 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu => linux (Ubuntu) ** 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/1976556 Title: [Lenovo 300e 2nd GEN] ELAN Touchpad not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976267] Re: edk2 ftbfs in jammy with -march=x86-64-v3
Interesting, seems to build but later fail to boot correctly (or in time) at the self tests. Since DannF usually handles edk2 for Debian and Ubuntu I subscribed him and wanted to ask if he looks at this as well (to avoid duplicate work)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976267 Title: edk2 ftbfs in jammy with -march=x86-64-v3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1976267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
Ah, SOLVED, like this: Triggered by your remarks, I found https://unix.stackexchange.com/a/656183, which says: RUB_CMDLINE_LINUX_DEFAULT="atkbd.reset i8042.reset i8042.nomux quiet splash". If this doesn't work, follow the same process but try GRUB_CMDLINE_LINUX_DEFAULT="i8042.direct i8042.dumbkbd" ... and that last line worked for me: keyboard works immediatly after boot and resume. So my grub line is now GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.debug=1i8042.direct i8042.dumbkbd" I guess I can remove i8042.debug=1 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/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976581] Re: Ubiquity installer failing with "Failed to mount the target: /target"
*** This bug is a duplicate of bug 1976585 *** https://bugs.launchpad.net/bugs/1976585 ** This bug has been marked a duplicate of bug 1976585 Ubiquity Installer Crash (Consistently Repeatable) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976581 Title: Ubiquity installer failing with "Failed to mount the target: /target" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976585] [NEW] Ubiquity Installer Crash (Consistently Repeatable)
Public bug reported: Ubiquity installer fails with the following steps, booting off a 22.04 LTS USB. Steps to reproduce: - Select: *Try or Install Ubuntu [wait for bootup] - Select: Try Ubuntu (with English) [wait for boot] - Run "Install Ubuntu 22.04 LTS" icon in the top left corner of the screen [Shows Install / Welcome screen] - Select English, click on Continue - Select English (US) / English (US) for keyboard layout, click on Continue - Select Normal Installation, Install thrid-party software, Configute secure boot, entered password, click on Continue - Select Erase disk and install Ubuntu, Advanced features..., Erase disk and use ZFS, Encrypt the new Ubuntu installation, click OK, click Install Now - Enter a security key, click Install Now - View "Write the changes to disks?" (single drive computer, partitions: vfat, swap, bpool, rpool), click Continue - View "Where are you?", select Los Angeles, click Continue - Installer crashed. Looking at /var/log/syslog, I see the following consistently with every try: Jun 2 04:16:53 ubuntu ubiquity[6225]: switched to page usersetup Jun 2 04:16:53 ubuntu ubiquity: Traceback (most recent call last): Jun 2 04:16:53 ubuntu ubiquity: File "/usr/share/ubiquity/install.py", line 769, in Jun 2 04:16:53 ubuntu ubiquity: install = Install() Jun 2 04:16:53 ubuntu ubiquity: File "/usr/share/ubiquity/install.py", line 69, in __init__ Jun 2 04:16:53 ubuntu ubiquity: assert os.path.ismount(self.target), \ Jun 2 04:16:53 ubuntu ubiquity: AssertionError: Failed to mount the target: /target ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 Date: Wed Jun 1 21:17:24 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.15 ubuntu ** Attachment added: "/var/log/syslog" https://bugs.launchpad.net/bugs/1976585/+attachment/5594430/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976585 Title: Ubiquity Installer Crash (Consistently Repeatable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967558] Re: major copy problem !
[Expired for thunar (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunar (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967558 Title: major copy problem ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1967558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967558] Re: major copy problem !
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967558 Title: major copy problem ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1967558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967558] Re: major copy problem !
[Expired for pcmanfm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pcmanfm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967558 Title: major copy problem ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1967558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
I tried "i8042.noaux=1", but no change: after boot and after resume: touchpad works immediatly, but keyboard takes 25-45 seconds. dmesg included ** Attachment added: "dmesg "i8042.noaux=1"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+attachment/5594428/+files/dmesg.i8042.noaux.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
It seems very similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882478/ which have been fixed on Bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976581] Re: Ubiquity installer failing with "Failed to mount the target: /target"
/var/log/syslog ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976581/+attachment/5594427/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976581 Title: Ubiquity installer failing with "Failed to mount the target: /target" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976581] [NEW] Ubiquity installer failing with "Failed to mount the target: /target"
Public bug reported: I'm trying to install Ubuntu with third party apps so that I can use secure boot. I also am choosing to use zfs with encryption. If fails when I press next on the timezone step. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 Date: Wed Jun 1 20:51:25 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976581 Title: Ubiquity installer failing with "Failed to mount the target: /target" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
I checked software-properties/0.99.22.2 in jammy-proposed and it does fix the problem. ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => Shih-Yuan Lee (fourdollars) ** Changed in: oem-priority Status: New => Fix Committed ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-oem-5.17/5.17.0.1009.9)
All autopkgtests for the newly accepted linux-meta-oem-5.17 (5.17.0.1009.9) for jammy have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.55.3+22.04ubuntu1 (amd64) r8168/8.049.02-1ubuntu1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu11 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-oem-5.17 [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/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969637] Re: IBus lookup table appears bottom left of application (x11)
This bug was fixed in the package gnome-settings-daemon - 42.2-1ubuntu1 --- gnome-settings-daemon (42.2-1ubuntu1) kinetic; urgency=medium * Merge with Debian. Remaining changes: + debian/control.in: - Build-depend on accountsservice - Drop build-dependency on libnss-dev and add to libgck-1-dev - Recommend pipewire-pulse instead of pulseaudio + debian/patches/ubuntu: - keyboard-sync-input-sources-to-accountsservice.patch - keyboard-Use-ibus-sources-from-locale.patch - lid-close-suspend-support.patch - media-keys-correct-logout-action.patch - media-keys-restore-terminal-keyboard-shortcut-schema.patch - print-notifications-suppress-printer-may-not-be-connected.patch - teach-gsd-about-the-gnome-calculator-snap-.desktop-name.patch - Revert-media-keys-fix-gnome-settings-desktop-file.patch + debian/patches/p11-kit: - Use p11-kit (via gck) as smartcards backend + debian/gnome-settings-daemon.install: - Install apport hook gnome-settings-daemon (42.2-1) unstable; urgency=medium * Team upload * New upstream release (LP: #1969637) * Bump Standards-Version to 4.6.1 gnome-settings-daemon (42.1-3) unstable; urgency=medium * Drop Revert-sharing-Don-t-manage-gnome-remote-desktop.patch - gnome-remote-desktop 42 provides its own systemd user session to start itself gnome-settings-daemon (42.1-2) unstable; urgency=medium * Team upload [ Jeremy Bicha ] * Seitch back to libgweather4 * debian/control.in: Build-Depend on libgweather4 * debian/control.in: Break older gnome-control-center (Closes: #1008493) -- Gunnar Hjalmarsson Wed, 01 Jun 2022 15:29:11 +0200 ** Changed in: gnome-settings-daemon (Ubuntu) Status: In Progress => 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/1969637 Title: IBus lookup table appears bottom left of application (x11) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1969637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974100] Re: qemu ide/sata disks do not work well with discard/trim
@Christian, I haven't tried all of your combinations, but when I mount a second disk using the growpart/e2fsck/resize2fs sequence that you suggest and then mount it, it grows to 725 MB and then zerofree reports what you observed: baccala@osito:~/NPDC/GNS3/bug$ sudo zerofree -v /dev/nbd0p1 3/5963617/6525179 But when I use an identical disk as the root filesystem, it grows to 789 MB and then zerofree reports this: baccala@osito:~/NPDC/GNS3/bug$ sudo zerofree -v /dev/nbd0p1 1524/5953550/6525179 Both virtual disks are ubuntu 20.04 cloudimgs extended to 25 GB. I used the procedure I described on May 20 (cloudinit.iso on a virtual CD-ROM) with the one disk as root and the other one as /dev/sdb. Both were identical when I booted the VM. You mentioned that "all tools that make it easy for me to deploy one also pick virtio by default"; can you run qemu from the command line on a bare metal system? If so, I thought my May 20 procedure was pretty simple. If not, then I guess it's harder to verify this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974100 Title: qemu ide/sata disks do not work well with discard/trim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1974100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976396] Re: laptop keyboard not working for about 30 seconds after resume from suspend
Please give "i8042.noaux=1" a try, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976396 Title: laptop keyboard not working for about 30 seconds after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976225] Re: Update the EGL headers as per AMD-Xilinx's request
@Łukas Sorry. I didn't aware that the second field is . AMD- Xilinx got libraries and header files from ARM. The version number is 9p0.01rel0. AMD-Xilinx updated one header file but the upstream version number in github[1] is still the same. The header file was not modified by Canonical. So, I updated the version number to 9p0.01rel0-1ubuntu1 instead of 9p0.01rel0-0ubuntu6. The version number in kinetic is already 9p0.01rel0-1ubuntu2. Any suggestion to correct it? --- [1] https://github.com/Xilinx/mali-userspace-binaries/tree/xilinx_v2022.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976225 Title: Update the EGL headers as per AMD-Xilinx's request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libegl-mali-xlnx/+bug/1976225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976475] Re: Installer crash when try to enable disk encryption
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1976475 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu => ubiquity (Ubuntu) ** Changed in: ubiquity (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/1976475 Title: Installer crash when try to enable disk encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970957] Re: suspend problem
This is to confirm Linux 5.18.0-051800-generic x86_64 fixed my Lenovo T460. Thanks mo! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976358] Re: Charset Boot-Login
** Package changed: linux (Ubuntu) => gdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976358 Title: Charset Boot-Login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1976358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1975744] Re: purging cloud-init doesn't remove its network configuration files
I like the idea of working this into cloud-init clean. My use case is that I use cloud-init to initially configure an instance that will later be manually configured, so I don't want files lying around that say things like "if you edit this file it will be overwritten on the next boot" (I forget the exact wording) when that's not the case. On Wed, Jun 1, 2022 at 7:50 PM Chad Smith <1975...@bugs.launchpad.net> wrote: > Thanks for the bug and triage folks. > > While this is confirmed/known behavior, I don't think cloud-init should > be automatically removing core configuration files that are not packaged > by cloud-init's deb package especially if removal of those config files > can have catastrophic consequences on the ability to connect to the > system. If the networking service happens to be restarted outside of > the perview of the admin purging the cloud-init package it would be very > surprising for the unsuspecting admin to see the system drop. > > Also we are aware of use-cases where folks may expect to use cloud-init > once, and have attempted to remove cloud-init deb package after initial > system configuration is correctly performed to ensure cloud-init no > longer acts to reconfigure the system in the future. > > While this use-case above is probably less desirable that just disabling > cloud-init via `sudo touch /etc/cloud/cloud-init.disabled` it does allow > image creators to reduce the overall size of their image if they are > trying to generate customized images with cloud-init and remove cloud- > init and any other dependencies on which cloud-init relies. > > > I'd prefer we avoid addressing this in packaging specifically, though we > could grow this functionality in cloud-init clean to clean up network > config artifacts generated by cloud-init. This would at least make it > easier for your use-case of cleaning up all network config files that > cloud-init generated on a system. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1975744 > > Title: > purging cloud-init doesn't remove its network configuration files > > Status in cloud-init package in Ubuntu: > Confirmed > > Bug description: > cloud-init creates /etc/netplan/50-cloud-init.yaml during its network > configuration step. > > However, "apt purge cloud-init" leaves this file intact. > > I've seen this behavior on Ubuntu 18, 20, and 22. > > I can always remove the file manually, but I'm left wondering what > other files cloud-init might have left lingering around on the system. > > Shouldn't a purge remove all files associated with a package? > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1975744/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975744 Title: purging cloud-init doesn't remove its network configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1975744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976567] [NEW] Desktop scaling was set incorrectly until I booted up the PC AFTER turning on the monitor
Public bug reported: Whenever I boot up my PC, I turn on the monitor as well. When this happens, the Intel Mesa graphics loads, and my screen ends up being small with large pixelated icons. The resolution was capped at 1024x768. Only after I reboot my PC multiple times without changing the display settings did the resolution increase to 1680x1050, the correct resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 21:07:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0589] InstallationDate: Installed on 2022-05-22 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:br4.6:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:sku: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy resolution ubuntu 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/1976567 Title: Desktop scaling was set incorrectly until I booted up the PC AFTER turning on the monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1976567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976395] Re: Duplicate ufw rules installed by dovecot packages
Hi timeless, Thanks for taking the time to report this bug. There are snippets from the bionic d/changelog: [snip...] dovecot (1:2.2.25-1ubuntu1) zesty; urgency=medium [snip...] * Dropped Changes as they got accepted in Debian: [snip...] + Add ufw integration: - d/dovecot-core.ufw.profile: new ufw profile. - d/rules: install profile in dovecot-core. - d/control: dovecot-core - suggest ufw. [snip...] dovecot (1:2.2.25-1) unstable; urgency=medium [snip...] * [16db179] Merged in some features of the Ubuntu dovecot package. [snip...] + dovecot-imapd,dovecot-pop3d: Added ufw profiles. [snip...] dovecot (1:2.2.24-1ubuntu1) yakkety; urgency=medium * Merge with Debian; Remaining Changes: [snip...] + Add ufw integration: - d/dovecot-core.ufw.profile: new ufw profile. - d/rules: install profile in dovecot-core. - d/control: dovecot-core - suggest ufw. From the logs above, it seems that: - we introduced the profiles in a single file (dovecot-core) in yakkety - Debian merged the change, but split it in separate files (dovecot-imapd,dovecot-pop3d) - we dropped the old file when merging the new Debian change for zesty The solution here would be to remove the old profile (dovecot-core) if it was not touched by the user. A workaround for anyone facing this issue is to remove /etc/ufw/applications.d/dovecot-core if it does not contain custom configurations. While this issue does differ from LP: #937040 because this is not cause by dovecot-common, but by an old version of dovecot-core, the arguments exposed in https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/937040/comments/7 still seem to apply here. I am marking this bug as triaged and setting the priority to low given the assumption that there are not many users facing the issue and that there is a straightforward workaround here. IMHO, this would also hinder the case for an SRU. I will not target bionic because this would still be an issue if one kept upgrading the package all the way to jammy. However, the priority may go down (or the bug may be set to invalid) once bionic hits its end of standard support. Unless someone is willing to drive this bug providing a patch and filing an SRU (do notice that it could be hard to make a case for this one with the SRU team), I am not sure if we will see much progress here other than the aforementioned workaround. ** Changed in: dovecot (Ubuntu) Status: New => Triaged ** Changed in: dovecot (Ubuntu) Importance: Undecided => Low ** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976395 Title: Duplicate ufw rules installed by dovecot packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1976395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976524] Re: [needs-packaging] Please sync liblivemedia from debian for jammy
*** This is an automated message *** This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs- packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist. ** Summary changed: - Please sync liblivemedia from debian for jammy + [needs-packaging] Please sync liblivemedia from debian for jammy ** Changed in: liblivemedia (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976524 Title: [needs-packaging] Please sync liblivemedia from debian for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liblivemedia/+bug/1976524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971271] Re: Merge crmsh from Debian unstable for kinetic
This bug was fixed in the package crmsh - 4.4.0-1ubuntu1 --- crmsh (4.4.0-1ubuntu1) kinetic; urgency=medium * Merge with Debian unstable (LP: #1971271, #1972730). Remaining changes: - d/t/pacemaker-node-status.sh: Get the node name with "crm_node -n" instead of using "corosync-cmapctl". Ubuntu's corosync default configuration file does not set the node name. - d/t/control: add resource-agents-extra as a dependency of some tests. * Dropped changes: - d/p/0020-Use-crmsh-hb_report.patch: use the crmsh shipped hb_report script when available (LP #1958247). [ The hb_report script is no longer present since 4.4.0. ] - d/p/0021-Support-python-310.patch: support Python 3.10 (LP #1958393). [ Included in 4.4.0. ] -- Athos Ribeiro Tue, 31 May 2022 18:04:36 -0300 ** Changed in: crmsh (Ubuntu) Status: In Progress => 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/1971271 Title: Merge crmsh from Debian unstable for kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1971271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972730] Re: WARNING: crmadmin -S unexpected output
This bug was fixed in the package crmsh - 4.4.0-1ubuntu1 --- crmsh (4.4.0-1ubuntu1) kinetic; urgency=medium * Merge with Debian unstable (LP: #1971271, #1972730). Remaining changes: - d/t/pacemaker-node-status.sh: Get the node name with "crm_node -n" instead of using "corosync-cmapctl". Ubuntu's corosync default configuration file does not set the node name. - d/t/control: add resource-agents-extra as a dependency of some tests. * Dropped changes: - d/p/0020-Use-crmsh-hb_report.patch: use the crmsh shipped hb_report script when available (LP #1958247). [ The hb_report script is no longer present since 4.4.0. ] - d/p/0021-Support-python-310.patch: support Python 3.10 (LP #1958393). [ Included in 4.4.0. ] -- Athos Ribeiro Tue, 31 May 2022 18:04:36 -0300 ** Changed in: crmsh (Ubuntu) Status: In Progress => 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/1972730 Title: WARNING: crmadmin -S unexpected output To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1972730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975744] Re: purging cloud-init doesn't remove its network configuration files
Thanks for the bug and triage folks. While this is confirmed/known behavior, I don't think cloud-init should be automatically removing core configuration files that are not packaged by cloud-init's deb package especially if removal of those config files can have catastrophic consequences on the ability to connect to the system. If the networking service happens to be restarted outside of the perview of the admin purging the cloud-init package it would be very surprising for the unsuspecting admin to see the system drop. Also we are aware of use-cases where folks may expect to use cloud-init once, and have attempted to remove cloud-init deb package after initial system configuration is correctly performed to ensure cloud-init no longer acts to reconfigure the system in the future. While this use-case above is probably less desirable that just disabling cloud-init via `sudo touch /etc/cloud/cloud-init.disabled` it does allow image creators to reduce the overall size of their image if they are trying to generate customized images with cloud-init and remove cloud- init and any other dependencies on which cloud-init relies. I'd prefer we avoid addressing this in packaging specifically, though we could grow this functionality in cloud-init clean to clean up network config artifacts generated by cloud-init. This would at least make it easier for your use-case of cleaning up all network config files that cloud-init generated on a system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975744 Title: purging cloud-init doesn't remove its network configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1975744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976565] [NEW] dnspython 2.2.1-1 fails IPv6 autopkgtests
Public bug reported: dnspython 2.2.1-1 fails IPv6 autopkgtests This version of dnspython attempts to probe to see if the IPv6 version of the tests should be used, but does so in an incomplete way that results in failing tests. https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/amd64/d/dnspython/20220528_213819_f0ffc@/log.gz ** Affects: dnspython (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/1976565 Title: dnspython 2.2.1-1 fails IPv6 autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnspython/+bug/1976565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976361] Re: man page “passes the buck” to a dead end for .netrc docs
Thanks for the report, Bill. And thanks for willing to solve this upstream, Matthias! Since upstream is aware and will provide the requested docs in a future release, we can wait for that patch to be ready, then we can pull that into the development release and consider SRUing it if we can make a good case for that. ** Changed in: fetchmail (Ubuntu) Status: New => Triaged ** Changed in: fetchmail (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976361 Title: man page “passes the buck” to a dead end for .netrc docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1976361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966066] Re: audio from external sound card is distorted
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1012.12 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/1966066 Title: audio from external sound card is distorted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1012.12 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/1966499 Title: Recent 5.13 kernel has broken KVM support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971667] Re: Skip setting ethernet LED on Dell EMC board
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1012.12 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/1971667 Title: Skip setting ethernet LED on Dell EMC board To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1971667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976563] [NEW] All text and images in Gnome Shell are corrupted
Public bug reported: See attached screenshot. The corrupted text and images are only appearing in the Ubuntu desktop environment (like the login screen, dock, and the bar at top of the screen). Applications like Nautilus, the Terminal app, and Chrome are not affected. Maybe an Nvidia issue? I'm going to restart my PC which will probably fix the issue. I'll edit this if the issue persists after the restart. Edit: To anyone investigating this issue, I recommend looking at some of the other issues I've reported recently. It seems like they could all be connected somehow, with Nvidia as the common thread. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 18:58:22 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.73.05, 5.15.0-33-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3287] InstallationDate: Installed on 2022-04-23 (39 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy ubuntu ** Attachment added: "Screenshot from 2022-06-01 18-57-55.png" https://bugs.launchpad.net/bugs/1976563/+attachment/5594368/+files/Screenshot%20from%202022-06-01%2018-57-55.png ** Description changed: See attached screenshot. The corrupted text and images are only appearing in the Ubuntu desktop environment (like the login screen, dock, and the bar at top of the screen). Applications like Nautilus, the Terminal app, and Chrome are not affected. Maybe an Nvidia issue? I'm going to restart my PC which will probably fix the issue. I'll edit this if the issue persists after the restart. + + Edit: To anyone investigating this issue, I recommend looking at some of + the other issues I've reported recently. It seems like they could all be +
[Bug 1871148] Re: services start before apparmor profiles are loaded
Thanks Alberto : Re-enabling the snapd.apparmor service has fixed my issue. Therefore, I have migrated my issue to a contribution to https://bugs.launchpad.net/snapd/+bug/1806135 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974456] Autopkgtest regression report (apt/2.0.9)
All autopkgtests for the newly accepted apt (2.0.9) for focal have finished running. The following regressions have been reported in tests triggered by the package: livecd-rootfs/2.664.41 (ppc64el, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974456 Title: regression: apt.postint fails if never previously configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871148] Re: services start before apparmor profiles are loaded
** Tags removed: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971114] Re: Ubuntu 22.04 python3-grpcio causes some apps to use 100% of the CPU
Hi, Any update or comment on this bug? 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/1971114 Title: Ubuntu 22.04 python3-grpcio causes some apps to use 100% of the CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grpc/+bug/1971114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1976201] Re: first time booting rpi2b crashed after setup wizard (location, timezone, login information)
Yes it's Ubuntu mate On Tue, May 31, 2022, 5:36 AM Dave Jones <1976...@bugs.launchpad.net> wrote: > Can you let me know which image you were trying to boot? The regular > ubuntu desktop image is arm64 only which wouldn't boot on a rev1.1 Pi 2B > board, so I'm guessing this *might* be Ubuntu MATE? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1976201 > > Title: > first time booting rpi2b crashed after setup wizard (location, > timezone, login information) > > Status in ubiquity package in Ubuntu: > New > > Bug description: > no further information > > ProblemType: Bug > DistroRelease: Ubuntu 21.10 > Package: ubiquity 21.10.10 > ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 > Uname: Linux 5.13.0-1009-raspi armv7l > ApportVersion: 2.20.11-0ubuntu71 > Architecture: armhf > CasperMD5CheckResult: unknown > Date: Sun May 29 22:07:03 2022 > ImageMediaBuild: 20211105 > SourcePackage: ubiquity > UbiquityDebug: > > UbiquitySyslog: > > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976201/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976201 Title: first time booting rpi2b crashed after setup wizard (location, timezone, login information) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884726] Re: [TTM] Buffer eviction failed
Switched to nvidia proprietary driver and so far no more crashes in the browser, need more time to fully test with the nvidia driver. Definitely a nouveau driver bug with the kernel: Linux svn 5.4.0-55-generic #61~18.04.1-Ubuntu SMP Wed Nov 11 14:12:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Attached is the crash_history. ** Attachment added: "crash history nouveau driver kernel 5.4.8-55 hwe (ubuntu lxde 18.04))" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884726/+attachment/5594367/+files/crash_history.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884726 Title: [TTM] Buffer eviction failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-oracle-5.4/5.4.0.1074.80~18.04.53)
All autopkgtests for the newly accepted linux-meta-oracle-5.4 (5.4.0.1074.80~18.04.53) for bionic have finished running. The following regressions have been reported in tests triggered by the package: kpatch/0.5.0-0ubuntu1.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-oracle-5.4 [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/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968228] Autopkgtest regression report (php7.4/7.4.3-4ubuntu2.11)
All autopkgtests for the newly accepted php7.4 (7.4.3-4ubuntu2.11) for focal have finished running. The following regressions have been reported in tests triggered by the package: phpmyadmin-sql-parser/4.6.1-2 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#php7.4 [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/1968228 Title: RTD collision with opcache To manage notifications about this bug go to: https://bugs.launchpad.net/php/+bug/1968228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975669] Re: USB devices are not working on Raspberry pi zero 2 with arm64 image
I got some more accessories to try yesterday, turns out the problem is related to micro usb to usb type-A/tupe-C adapter, only one of the five I tried worked both in armhf and arm64 images. With that one, everything looks fine now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975669 Title: USB devices are not working on Raspberry pi zero 2 with arm64 image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1975669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976267] Re: edk2 ftbfs in jammy with -march=x86-64-v3
** Changed in: edk2 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976267 Title: edk2 ftbfs in jammy with -march=x86-64-v3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1976267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951586] Re: Need option to specify wifi regulatory domain
** Changed in: network-manager Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951586 Title: Need option to specify wifi regulatory domain To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972866] Re: [MIR] gsasl
** 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/1972866 Title: [MIR] gsasl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsasl/+bug/1972866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929120] Re: dh_strip behaviour in Ubuntu Hirsute
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: debugedit (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/1929120 Title: dh_strip behaviour in Ubuntu Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1929120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971107] Re: Versions in Focal, Impish and Jammy are vulnerable to CVE-2022-26661 and CVE-2022-26662
** Changed in: tryton-proteus (Ubuntu) Status: Confirmed => In Progress ** Changed in: tryton-server (Ubuntu) Status: Confirmed => In Progress ** Changed in: tryton-proteus (Ubuntu) Assignee: (unassigned) => Luís Cunha dos Reis Infante da Câmara (luis220413) ** Changed in: tryton-server (Ubuntu) Assignee: (unassigned) => Luís Cunha dos Reis Infante da Câmara (luis220413) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971107 Title: Versions in Focal, Impish and Jammy are vulnerable to CVE-2022-26661 and CVE-2022-26662 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tryton-proteus/+bug/1971107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970961] Re: Version in Bionic has multiple vulnerabilities
** Changed in: faad2 (Ubuntu) Status: New => In Progress ** Changed in: faad2 (Ubuntu) Assignee: (unassigned) => Luís Cunha dos Reis Infante da Câmara (luis220413) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970961 Title: Version in Bionic has multiple vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/faad2/+bug/1970961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976478] Re: Telegram Desktop steals input on Lock screen
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976478 Title: Telegram Desktop steals input on Lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1976478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976484] Re: never sound ubuntu 20.04 22.04 alsamixer 1.2.6 card sof-hda-dsp
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976484 Title: never sound ubuntu 20.04 22.04 alsamixer 1.2.6 card sof-hda-dsp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1976484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976335] Re: CVE-2022-25762 Score 8.6
Hello Hans, the general outline of the update preparation is sketched out on this wiki page https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation -- it's not exhaustive, but it's a good start. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976335 Title: CVE-2022-25762 Score 8.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat9/+bug/1976335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970615] Re: WebGL does not work in snap firefox
It works now in snap Firefox 102.0b2 (64-bit) on Ubuntu 22.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970615 Title: WebGL does not work in snap firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974456] Re: regression: apt.postint fails if never previously configured
juliank - No. Our "overly complex" build must support environments without direct access to the ubuntu servers. Therefore we download all needed Ubuntu packages as a front-end step, putting them in an IBM- internal archive. At build time, reprepro is used to put them in to a local filesystem repo which then feeds debootstrap. The front-end step certainly downloads from focal-updates, always using apt-get download. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974456 Title: regression: apt.postint fails if never previously configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
Same issue here. Heavy black flickering on the screen with Ubuntu 22.04 after upgrade from 20.04 and after a clean install. No extra repos, only default packages. Aspire 3 A315-31 series N17Q2 Mesa Intel® HD Graphics 500 (APL 2) Linux laptop 5.15.0-33-generic #34-Ubuntu SMP Wed May 18 13:34:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976558] [NEW] upgrade from ubuntu 20.04 to 22.04 fails due to yaru-theme-gnome-shell missing files
Public bug reported: I had to delete installed files of Yaru Theme for Ubuntu 20.04 LTS before continuing the upgrade to Ubuntu 22.04 LTS. dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-enter.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/meson.build' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-layout.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-shift.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-shift-latched-uppercase.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-hide.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: file '/usr/share/themes/Yaru-dark/gnome-shell/key-shift-uppercase.svg' not owned by package 'yaru-theme-gnome-shell:all' dpkg-maintscript-helper: error: directory '/usr/share/themes/Yaru-dark/gnome-shell' contains files not owned by package yaru-theme-gnome-shell:all, cannot switch to symlink dpkg: s'ha produït un error en processar l'arxiu /tmp/apt-dpkg-install-CLn2dX/14-yaru-theme-gnome-shell_22.04.4_all.deb (--unpack): el subprocés «guió «yaru-theme-gnome-shell» nou del paquet pre-installation» retornà el codi d'eixida d'error 1 After removing those files and trying a second time, there were more missing files: /usr/share/themes/Yaru/gnome-shell/key-enter.svg /usr/share/themes/Yaru/gnome-shell/meson.build /usr/share/themes/Yaru/gnome-shell/key-layout.svg /usr/share/themes/Yaru/gnome-shell/key-shift.svg /usr/share/themes/Yaru/gnome-shell/gnome-shell-high-contrast.css /usr/share/themes/Yaru/gnome-shell/key-shift-latched-uppercase.svg /usr/share/themes/Yaru/gnome-shell/key-hide.svg /usr/share/themes/Yaru/gnome-shell/key-shift-uppercase.svg /usr/share/themes/Yaru/gnome-shell/gnome-shell.css After removing those too, I could proceed and finish the upgrade. With aptitude resolving broken dependencies was possible. Afterwards reexecuted the upgrader already unpacked to /tmp. That removed old packages not needed anymore which aptitude failed to manage. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yaru-theme-gnome-shell 22.04.4 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 21:47:29 2022 Dependencies: InstallationDate: Installed on 2014-06-05 (2917 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to jammy on 2022-06-01 (0 days ago) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976558 Title: upgrade from ubuntu 20.04 to 22.04 fails due to yaru-theme-gnome-shell missing files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1976558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976534] Re: /dev/ttyUSB0 doesn't appear for an FTDI on fresh Ubuntu 22.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1976534/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976534 Title: /dev/ttyUSB0 doesn't appear for an FTDI on fresh Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1976534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976556] Re: [Lenovo 300e 2nd GEN] ELAN Touchpad not working
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1976556/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976556 Title: [Lenovo 300e 2nd GEN] ELAN Touchpad not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1976556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976556] [NEW] [Lenovo 300e 2nd GEN] ELAN Touchpad not working
Public bug reported: Used Ubunutu 22.04 with the current 5.15.x Kernel, cross tested with Linux Mint and 5.14.x Kernel. I have a Lenovo 300e 2nd Gen with an ELAN Touchscreen AND Touchpad with AMD processor. The Touchscreen is working flawlessly. The TouchPAD is dead. According to the Windows driver: %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group2_Inst, HID\VEN_ELAN_0660; ClickPad for Capela 14e Windows %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group1_Inst, HID\VEN_ELAN_0661; ClickPad for Windows 100e/300e %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group3_Inst, HID\VEN_ELAN_066C; ClickPad for 100e/300e AMD Pollock %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group1_Inst, HID\VEN_ELAN_066E; ClickPad for 100W&300W Gen3 AMD Pollock %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group1_Inst, HID\VEN_ELAN_066F; ClickPad for 300W Gen3 Intel JasperLake it is an ELAN066C According to similar solutions i tried to block several built in kernel modules, without success. https://askubuntu.com/questions/1248176/ideapad-5-15are05-elan-touchpad- not-working-on-20-04-nor-on-18-04 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976556 Title: [Lenovo 300e 2nd GEN] ELAN Touchpad not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1976556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967003] Re: [BPO] obfs4proxy/0.0.13-1 from jammy
Thank you, Dan for your maintenance work. Unfortunately my skillset does not suffice to prepare the backported package or to find a sponsor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967003 Title: [BPO] obfs4proxy/0.0.13-1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obfs4proxy/+bug/1967003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971434] Re: Display powersave only blanks, but does not turn off
Same on 22.04 Gnome Xorg, Nouveau driver on a GeForce GTX 1650 Ti Mobile -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975634] Re: [SRU] Xena stable releases
** Description changed: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements. The update contains the following package updates: +* cinder 19.1.0 * neutron 19.3.0 * manila 13.0.3 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] Waiting for the following before moving forward: https://review.opendev.org/c/openstack/releases/+/842971 ** Also affects: cinder (Ubuntu) Importance: Undecided Status: New ** Changed in: cinder (Ubuntu) Status: New => Triaged ** Changed in: cinder (Ubuntu) Status: Triaged => Invalid ** Changed in: manila (Ubuntu) Status: New => Invalid ** Description changed: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements. The update contains the following package updates: -* cinder 19.1.0 + * cinder 19.1.0 * neutron 19.3.0 * manila 13.0.3 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] - Waiting for the following before moving forward: https://review.opendev.org/c/openstack/releases/+/842971 + I've added cinder to this SRU after neutron and manila were accepted. ** No longer affects: cinder (Ubuntu) ** No longer affects: cinder (Ubuntu Impish) ** Description changed: [Impact] This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements. The update contains the following package updates: * cinder 19.1.0 * neutron 19.3.0 * manila 13.0.3 [Test Case] The following SRU process was followed: https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates In order to avoid regression of existing consumers, the OpenStack team will run their continuous integration test against the packages that are in -proposed. A successful run of all available tests will be required before the proposed packages can be let into -updates. The OpenStack team will be in charge of attaching the output summary of the executed tests. The OpenStack team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug. [Discussion] - I've added cinder to this SRU after neutron and manila were accepted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975634 Title: [SRU] Xena stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1975634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976554] [NEW] Screen auto rotates randomly after suspend
Public bug reported: Description:Ubuntu 22.04 LTS Release:22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy ** Affects: mutter (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/1976554 Title: Screen auto rotates randomly after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976198] Autopkgtest regression report (libsdl2/2.0.20+dfsg-2ubuntu1.22.04.1)
All autopkgtests for the newly accepted libsdl2 (2.0.20+dfsg-2ubuntu1.22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: ffmpeg/7:4.4.1-3ubuntu5 (armhf) 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/jammy/update_excuses.html#libsdl2 [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/1976198 Title: [SRU] Possible missing dependencies of libsdl2-dev in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1976198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884726] Re: [TTM] Buffer eviction failed
Update info: 01:00.0 VGA compatible controller: NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1) I can work with intensive GPU accel (opengl / opengles) without any crashes. With the browser (Chrome,Chromium,Brave, and recently i have read about the TTM crash with Firefox), it can crash the computer after a few minutes while scrolling down the page with lots of ads. I am not sure if the bug is in TTM/drm or the GPU userspace in the browser. But Chromium crashes right after login into lightdm. I was not even aware chromium had a background thread running. Just for Information, here is how chromium is rendering the page, looks like corrupt page. ** Attachment added: "corrupt rendering" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884726/+attachment/5594364/+files/2022-06-01-160634_1920x1080_scrot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884726 Title: [TTM] Buffer eviction failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise on AMD Caicos
** Attachment removed: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5311593/+files/modified.conffile..etc.gdm3.custom.conf.txt ** Attachment removed: "This is what I see (taken from a camera) after Ubuntu finishes booting and loads the login manager." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5150317/+files/i5Fee.jpg ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5150318/+files/Dependencies.txt ** Attachment removed: "Output of "lspci -k"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5154814/+files/output.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5150319/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "xrandr" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5173498/+files/xrandr.txt ** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5173499/+files/dmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5311591/+files/Dependencies.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308778/+files/Dependencies.txt ** Attachment removed: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5310808/+files/modified.conffile..etc.gdm3.custom.conf.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308779/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308780/+files/modified.conffile..etc.gdm3.custom.conf.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308786/+files/CurrentDmesg.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5311592/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308787/+files/DpkgLog.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308788/+files/Lspci.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308789/+files/Lsusb.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308790/+files/ProcCpuinfo.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308791/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308792/+files/ProcModules.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308793/+files/UdevDb.txt ** Attachment removed: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308794/+files/xdpyinfo.txt ** Attachment removed: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308795/+files/Xrandr.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308796/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308797/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5308798/+files/modified.conffile..etc.gdm3.custom.conf.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5310806/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775881/+attachment/5310807/+files/ProcCpuinfoMinimal.txt ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise on AMD Caicos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1969974] Re: Gnome screen recorder doesn't work on dist-upgraded jammy systems
*** This bug is a duplicate of bug 1963264 *** https://bugs.launchpad.net/bugs/1963264 Simply deleting the cached gstreamer dir fixed it for me. rm -rf ~/.cache/gstreamer-1.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969974 Title: Gnome screen recorder doesn't work on dist-upgraded jammy systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870597] Re: libinput says "your system is too slow"
** Attachment removed: "BootLog.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350642/+files/BootLog.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350644/+files/Lspci.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5345771/+files/Dependencies.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5345772/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ShellJournal.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5345773/+files/ShellJournal.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350643/+files/CurrentDmesg.txt ** Attachment removed: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350646/+files/Lsusb-t.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350645/+files/Lsusb.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350647/+files/Lsusb-v.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350648/+files/ProcCpuinfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350649/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350650/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350651/+files/ProcModules.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350652/+files/UdevDb.txt ** Attachment removed: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350653/+files/Xrandr.txt ** Attachment removed: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1870597/+attachment/5350654/+files/xdpyinfo.txt ** Description changed: - During the freeze, the output of the install had a message from "gdm-x- - session" saying "your system is too slow". - - To reproduce: - 1. Launch the Ubuntu installer - 2. Begin the installation process - 3. When the installation process begins, move the cursor around - 4. Notice how the PC freezes and drops mouse events - - Description: Ubuntu Focal Fossa (development branch) - Release: 20.04 - - gnome-shell: - Installed: 3.36.0-2ubuntu2 - Candidate: 3.36.0-2ubuntu2 - Version table: - *** 3.36.0-2ubuntu2 500 - 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status - - ProblemType: Bug - DistroRelease: Ubuntu 20.04 - Package: gnome-shell 3.36.0-2ubuntu2 - ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 - Uname: Linux 5.4.0-21-generic x86_64 - NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair - ApportVersion: 2.20.11-0ubuntu21 - Architecture: amd64 - CasperVersion: 1.442 - Date: Fri Apr 3 14:24:21 2020 - DisplayManager: gdm3 - GsettingsChanges: - - LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash - RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 - SourcePackage: gnome-shell - UpgradeStatus: No upgrade log present (probably fresh install) - --- - ProblemType: Bug - ApportVersion: 2.20.11-0ubuntu22 - Architecture: amd64 - CasperVersion: 1.442 - CompositorRunning: None - DistUpgraded: Fresh install - DistroCodename: focal - DistroRelease: Ubuntu 20.04 - DistroVariant: ubuntu - ExtraDebuggingInterest: Yes - GraphicsCard: - Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Dell UHD Graphics 620 [1028:0810] - LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) - MachineType: Dell Inc. Inspiron 5570 - NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair - Package: xorg-server (not installed) - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash - ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- - ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 - Tags: focal ubuntu - Uname: Linux 5.4.0-21-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: - - _MarkForUpload: True - dmi.bios.date: 05/15/2019 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: 1.2.3 - dmi.board.name: 09YTN7 -
[Bug 1971993] Comment bridged from LTC Bugzilla
--- Comment From bbl...@de.ibm.com 2022-06-01 14:40 EDT--- Ah, nice, thanks. Just wanted to make sure, it didn't get lost. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971993 Title: [Ubuntu 22.04] s390-tools: subpackage chreipl-fcp-mpath installs files into wrong location and subsequently doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1971993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1037.38)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1037.38) for focal have finished running. The following regressions have been reported in tests triggered by the package: glibc/unknown (arm64) mali-midgard/unknown (arm64) wireguard-linux-compat/1.0.20201112-1~20.04.1 (arm64) lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64) bbswitch/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-bluefield [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/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884299] Re: Chromium snap won't run with nfs home drive
Matthieu, more recently a more likely problem has been characterized by Alberto Mardegan and found the line in question in https://bugs.launchpad.net/snapd/+bug/1973321 In particular, restarting snapd doesn't help at all for me, so having the directory mounted before snapd starts doesn't help, and the same problem occurs with other file systems. However _starting_ outside the home directory does help. This is the situation for me with Kerberos authenticated NFS, and others with sshfs. I don't know whether it is relevant for people using NFS without authentication. It is easy to test for yourself - restart snapd and see if that helps. So I think there is progress in understanding the problem, even if not working out how to fix it. FYI: I initially tried a work around where I used the debian repository for firefox instead of the snap version, but despite giving it a higher priority (confirmed via "sudo apt policy firefox") I found the debian package twice over a week uninstalled and replaced by the snap version that then would not start. I can manually revert it but it is inconvenient. Any suggestions on how to make that work reliably would be appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884299 Title: Chromium snap won't run with nfs home drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1884299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926218] Re: Disable or Remove FLoC features and the provider service
'find "$HOME"/snap/chromium -iname *floc*' gives me nothing either, but
I only installed it a couple of weeks ago.
Some things I observe:
1. In my set-up, Floc can _not_ be enabled in
.
2. Look into the parts concerning Floc in the source code, one finds several
stub functions, e.g. in
chrome/browser/privacy_sandbox/privacy_sandbox_service.cc:393
void PrivacySandboxService::SetFlocPrefEnabled(bool enabled) const {
// TODO(crbug.com/1299720): Remove this and all the UI code which uses it.
return;
}
3. In that page ,
> FLoC-the-feature has been removed from the codebase, but there are still a
> few UX surfaces that need to surface FLoC information (basically informing
> users that it's disabled).
>
> To support this, while also transitioning to Privacy Sandbox Settings 3, many
> functions have been left with stubs with little or no functionality.
>
> Once Privacy Sandbox Settings 3 has been launched, these surfaces are no
> longer required, and the remaining functions can be cleaned up.
And then the title of commit
https://chromium.googlesource.com/chromium/src/+/3c4b23ea94bf0efbc12d93e832b5888c50412b6b
is
> Privacy Sandbox Settings: Move FLoC to Topics API
This suggests Google is moving away from Floc.
4. Indeed, from
,
> The origin trial of FLoC in 2021 received a wide range of feedback from
> adtech and web ecosystem contributors. In particular, there were concerns
> that FLoC cohorts could be used as a fingerprinting surface to identify
> users, or could reveal a user's association with a sensitive category. There
> were also calls to make FLoC more transparent and understandable to users.
>
> The Topics API has been designed with this feedback in mind, to explore other
> ways to support interest-based advertising, with improved transparency,
> stronger privacy assurances and a different approach for sensitive categories.
All in all, apparently Floc is being phased out we have a moving target. So, if
that is a correct assessment, although this bug report will technically solve
itself with time (insofar as it is targeted at Floc), we will still keep an eye
for future tracking mechanisms inside Chromium, under whatever name they may
come to be.
** Changed in: chromium-browser (Ubuntu)
Assignee: Olivier Tilloy (osomon) => Nathan Teodosio (nteodosio)
** Changed in: chromium-browser (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926218
Title:
Disable or Remove FLoC features and the provider service
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1926218/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976330] Re: No dropdown menu on bookmarks folder in trunk build under wayland
still on trunc 103.0a1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976330 Title: No dropdown menu on bookmarks folder in trunk build under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1976330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975621] Re: [Star Labs Lite IV] screen flashes on-off unless PSR is turned off
I am trying something new : since the machine is using Wayland I have removeed the following package that was installed by default (as [installed,automatic]) : xserver-xorg-video-intel Seen on the following post that it could help : https://forums.debian.net/viewtopic.php?t=149472 Will report tomorrow if this helps fixing the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975621 Title: [Star Labs Lite IV] screen flashes on-off unless PSR is turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973229] Re: Update freerdp2 to 2.7.0
Robie, for now, we are just cherrypicking the more urgent fix. I've uploaded to the jammy Unapproved queue. Feel free to reject the freerdp2 2.7.0 upload for now. ** Changed in: freerdp2 (Ubuntu Jammy) Assignee: Jeremy Bicha (jbicha) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973229 Title: Update freerdp2 to 2.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1973229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970994] Re: /usr/libexec/gnome-remote-desktop-daemon:11:setChannelError:rdpgfx_server_thread_func:thread_launcher:start_thread:clone3
** Description changed: + Impact + -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 42.0-4ubuntu1, the problem page at https://errors.ubuntu.com/problem/77f41623474304919ac793c6665505547b583b60 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + Test Case 1 + --- + Unfortunately, we weren't able to identify a reliable test case. - It's believed this issue will be fixed with - https://github.com/FreeRDP/FreeRDP/pull/7836 + We will know if this bug is fixed if errors.ubuntu.com stops reporting + that error with a fully upgraded system. However, that means this update + will need to be pushed to -updates + + Test Case 2 + --- + Install all updates. Log out and log back in. + Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop Sharing. + Turn it off then on because there may be a gnome-control-center bug with initial enabling. + + From a second computer, connect to the first computer using Remmina. + + The Remote Desktop page on the first computer provides the username and + password to use. I wasn't able to get the "Remote Desktop Address" to + work (maybe avahi doesn't work well?) so just use the first computer's + IP address. + + So something like: + RDP jeremy@192.168.1.1 + + Ensure that the connection works. + + Then repeat the test after updating the second computer to use the + updated freerdp2 since Remmina itself uses freerdp2. Basically we want + to make sure things keep working after the update but also continue to + work for connections between systems that aren't using the same version + of freerdp2. + + What Could Go Wrong + --- + RDP Sharing using freerdp2 is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. + + RDP Sharing can be used for providing remote support so it's important + that this feature works well because it may be difficult for the remote + admin to fix issues in person. + + freerdp2 is also used by the Remmina and GNOME Connections apps as the + "client" app for RDP Sharing. (The GNOME feature is the "server" side.) + + This fix is cherrypicked from the stable freerdp2 branch. ** Changed in: gnome-remote-desktop (Ubuntu) Status: Triaged => Invalid ** Changed in: freerdp2 (Ubuntu) Status: Triaged => Fix Released ** Changed in: freerdp2 (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: freerdp2 (Ubuntu) Importance: Undecided => Medium ** Changed in: freerdp2 (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970994 Title: /usr/libexec/gnome-remote-desktop- daemon:11:setChannelError:rdpgfx_server_thread_func:thread_launcher:start_thread:clone3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1970994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974456] Re: regression: apt.postint fails if never previously configured
Hi Gary, how do you invoke debootstrap so it uses packages from the the updates pocket? I wasn't able to with --extra-suites=focal-updates, but I might have missed something. But then I guess we should actually release that fix too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974456 Title: regression: apt.postint fails if never previously configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976547] [NEW] Update gnome-remote-desktop to 42.2
Public bug reported: Impact -- This is a new stable release in the GNOME 42 series https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/42.2/NEWS Test Case #1 Install all updates. Log out and log back in. Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop Sharing. Turn it off then on because there may be a gnome-control-center bug with initial enabling. From a second computer, connect to the first computer using Remmina. The Remote Desktop page on the first computer provides the username and password to use. I wasn't able to get the "Remote Desktop Address" to work (maybe avahi doesn't work well?) so just use the first computer's IP address. So something like: RDP jeremy@192.168.1.1 Ensure that the connection works. Test Case #2 Do test case #1 but this time also enable the Legacy VNC option on the Remote Desktop Sharing page. Connect using VNC instead and ensure that the connection works. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gnome-remote-desktop (Ubuntu) Importance: Wishlist Status: Fix Committed ** Tags: jammy upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976547 Title: Update gnome-remote-desktop to 42.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1976547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731502] Re: nmbd starts fine with no interfaces, but doesn't notify systemd that it started
I believe the first ubuntu package that had this change was 2:4.8.4+dfsg-2ubuntu1, in Cosmic (18.10), in August 2018. ** Changed in: samba (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731502 Title: nmbd starts fine with no interfaces, but doesn't notify systemd that it started To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1731502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976498] Re: DING causes gvfsd 'Too many files open' error and fills syslog
Changed from ding to nautilus after reading about nautilus gvfsd-trash bug ** Package changed: ding (Ubuntu) => nautilus (Ubuntu) ** Summary changed: - DING causes gvfsd 'Too many files open' error and fills syslog + nautilus causes gvfsd-trash 'Too many files open' error and fills syslog ** Description changed: - My syslog is filled (to >30GB) regularly with these messages. I seem to - have this thing called DING going on, which maybe causing it? + My syslog is filled (to >30GB) regularly with these messages. Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.625: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.626: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.627: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.628: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gnome-shell[3312]: DING: (org.gnome.Nautilus:156898): GVFS-WARNING **: 11:41:49.618: The peer-to-peer connection failed: Unable to create socket: Too many open files. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.629: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.630: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: daemon: Error creating server at address unix:path=/run/user/1000/gvfsd/socket-z3fCgn9o: Unable to create socket: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.631: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.632: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gnome-shell[3312]: DING: GNOME nautilus 42.1.1 Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.633: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.634: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: (process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many open files Jun 1 11:41:49 marks-linux-box gvfsd[123068]: message repeated 2 times: [ (process:123068): GLib-GIO-WARNING **: 10:41:49.635: fail: Error accepting connection: Too many open files] Jun 1 11:41:49 marks-linux-box gvfsd[123068]:
[Bug 1731502] Re: nmbd starts fine with no interfaces, but doesn't notify systemd that it started
This was fixed upstream via https://github.com/samba- team/samba/commit/0e571054a61e9de69190ae023199d1670e097e88 by changing the network dependency to network-online.target instead of just network.target ** Tags added: network-online-ordering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731502 Title: nmbd starts fine with no interfaces, but doesn't notify systemd that it started To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1731502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969939] Re: puppet 5 package incompatible with ruby 3 / ubuntu 22.04
Thanks Lucas. LGTM. We tried the PPA. No errors during puppet apply. File resources, both symlinks and regular files, are being created as expected. Our full 5kloc puppet manifest applied without any puppet errors, and we haven't noticed any other regressions. If you have any specific functionality you like us to double check, please let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969939 Title: puppet 5 package incompatible with ruby 3 / ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1969939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864329] Re: too long netbios name shouldn't be a fatal error
** Changed in: samba (Ubuntu) Assignee: Andreas Hasenack (ahasenack) => (unassigned) ** Changed in: samba (Ubuntu) Status: In Progress => Triaged ** Changed in: samba (Ubuntu) Importance: High => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864329 Title: too long netbios name shouldn't be a fatal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1864329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968228] Re: RTD collision with opcache
I installed the package from focal-proposed and confirmed that the synthetic test provided in #4 runs properly, without any errors. Real- world extended validation tests to follow... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968228 Title: RTD collision with opcache To manage notifications about this bug go to: https://bugs.launchpad.net/php/+bug/1968228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962614] Re: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal
thanks, I reviewed and uploaded to the focal-backports queue. ** Changed in: memtest86+ (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/1962614 Title: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1962614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967814] Autopkgtest regression report (qemu/1:4.2-3ubuntu6.22)
All autopkgtests for the newly accepted qemu (1:4.2-3ubuntu6.22) for focal have finished running. The following regressions have been reported in tests triggered by the package: ubuntu-image/1.11+20.04ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#qemu [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/1967814 Title: Ubuntu 20.04.3 - ilzlnx3g1 - virtio-scsi devs on KVM guest having miscompares on disktests when there is a failed path. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1967814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974235] Re: sru cloud-init (22.1-14 to 22.2) Bionic, Focal, Impish, Jammy
SQA is happy to give a +1 for Bionic and Focal we have no Juju workloads which currently run on Jammy, and only do Juju workloads on LTS's Bionic: https://solutions.qa.canonical.com/testplans/testplaninstance/7792f440-db83-452a-adbe- edbb0bbd2b62 Focal: https://solutions.qa.canonical.com/testplans/testplaninstance/413b8d8a-25d8-4fed-8227-593d1381a384 In both cases we used Juju to deploy a full Openstack with complex networking and storage configuration. Everything worked as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974235 Title: sru cloud-init (22.1-14 to 22.2) Bionic, Focal, Impish, Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1974235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968076] Re: [BPO] ipmctl with support for CPS hardware
@kilobyte have you been able to find a sponsor to upload for you, and also can you clarify that you tested the backport and verified it works correctly (as mentioned in comment 3)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968076 Title: [BPO] ipmctl with support for CPS hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmctl/+bug/1968076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
*** This bug is a duplicate of bug 520546 *** https://bugs.launchpad.net/bugs/520546 Same problem and solution today in ubuntu 20.04. Thanks for the solution! -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1969901] Re: network-manager fails to renew ipv6 address
>> The exact conditions for reproducing this bug on mixed IPv4/IPv6 networks >> are not known > >Looking at the upstream commit description, isn't it just that a DHCPv6 lease >expires and the >server NAKs a request for the same IP again? Or is that not >sufficient to trigger the problem. > Yes, when having a look at the previously collected logs, that seems to be the case (journalctl -u NetworkManager.service). Some of our computers get this problem more often that other. Some persons claim that they have never seen the problem. That is the part that is unclear. >In any case, I appreciate there might be difficulty in testing the fix, but >what's the actual >criteria you propose to use to decide when the bug is to be >marked verification-done-bionic? In the best of worlds I would like to simulated environment where dhcp- packages could be controlled, but that is not feasible. I have been running this patch on two computers since 2022-04-13 and haven't seen the problem since. One laptop (restarted every day) and one desktop that is always on. The desktop has been running for 29 days continuously according to syslog, without me having to manually remove dhcp lease files and restart network manager. Ideas for getting confidence of this change: We could ask more users who have experienced this error to install this change and confirm if they experience lost ipv6 addresses after installing patched version. Another idea is to shutdown computer in single user mode (without network), edit the dhcp6 lease file in a way so that dhcp-server will respond with NACK when booting up in multi-user mode. What to change in the lease file I do not know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969901 Title: network-manager fails to renew ipv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976536] [NEW] package tiger 1:3.2.4~rc1-2 failed to install/upgrade: installed tiger package post-installation script subprocess returned error exit status 10
Public bug reported: not work ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tiger 1:3.2.4~rc1-2 Uname: Linux 4.14.116 aarch64 NonfreeKernelModules: bluetooth ecdh_generic tcp_diag inet_diag virt_wifi cfg80211 sdcardfs parport_pc parport crc32c_intel crc32_pclmul ghash_clmulni_intel e1000 i2c_piix4 9pnet_virtio 9pnet pcspkr joydev psmouse mac_hid atkbd efi_pstore efivars ApportVersion: 2.20.11-0ubuntu27.24 Architecture: arm64 CasperMD5CheckResult: skip Date: Tue May 31 23:38:37 2022 Dmesg: ErrorMessage: installed tiger package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.8, Python 3.8.10, unpackaged PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: tiger Title: package tiger 1:3.2.4~rc1-2 failed to install/upgrade: installed tiger package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tiger (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976536 Title: package tiger 1:3.2.4~rc1-2 failed to install/upgrade: installed tiger package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiger/+bug/1976536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962614] Re: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal
** Also affects: memtest86+ (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: memtest86+ (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962614 Title: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1962614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish
uploaded to -backports queues for bionic and focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965800] Re: [BPO] debhelper in focal-backports not usable for i386 package building (missing dependency)
uploaded to -backports queues for bionic and focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965800 Title: [BPO] debhelper in focal-backports not usable for i386 package building (missing dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976498] Re: DING causes gvfsd 'Too many files open' error and fills syslog
Further reading would suggest that it's a bug in Nautilus and the way that gvfsd deals with trash: https://www.reddit.com/r/gnome/comments/l0gg32/a_helpul_tip_for_those_with_gvfsdtrash_hogging/ It runs out that I don't have ding installed, and also no references to gvfsd. Yet, if I do as the post above says and kill the gvfsd process when it's running it stops my root drive filling up with an enormous syslog. How do I transfer this bug over to Nautilus? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976498 Title: DING causes gvfsd 'Too many files open' error and fills syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ding/+bug/1976498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976534] [NEW] /dev/ttyUSB0 doesn't appear for an FTDI on fresh Ubuntu 22.04
Public bug reported: Hi all, This problem appeared on a freshly installed Ubuntu 22.04 desktop. When I'm attaching a ftdi device into usb everything looks great but there's no /dev/ttyUSB0 file. Looks like it's created and then disappears immediately. I tried to remove brltty package (as some recommends https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224) but it didn't help. The same ftdi device works on older Ubuntu version w/o any problems. So hardware is ok. I'm having this in syslog: Jun 1 16:58:09 qgs-comp kernel: [ 538.642086] usb 2-1.5: new full-speed USB device number 5 using ehci-pci Jun 1 16:58:10 qgs-comp kernel: [ 538.756437] usb 2-1.5: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 Jun 1 16:58:10 qgs-comp kernel: [ 538.756445] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 1 16:58:10 qgs-comp kernel: [ 538.756448] usb 2-1.5: Product: USB Serial Jun 1 16:58:10 qgs-comp kernel: [ 538.756450] usb 2-1.5: Manufacturer: FTDI Jun 1 16:58:10 qgs-comp kernel: [ 538.756452] usb 2-1.5: SerialNumber: FT0KKBIF Jun 1 16:58:10 qgs-comp kernel: [ 538.759677] ftdi_sio 2-1.5:1.0: FTDI USB Serial Device converter detected Jun 1 16:58:10 qgs-comp kernel: [ 538.759713] usb 2-1.5: Detected FT232RL Jun 1 16:58:10 qgs-comp kernel: [ 538.760546] usb 2-1.5: FTDI USB Serial Device converter now attached to ttyUSB0 Jun 1 16:58:01 qgs-comp colord-sane: message repeated 2 times: [ io/hpmud/musb.c 2101: Invalid usb_open: Permission denied] Jun 1 16:58:10 qgs-comp mtp-probe: checking bus 2, device 5: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5" Jun 1 16:58:10 qgs-comp mtp-probe: bus: 2, device: 5 was not an MTP device Jun 1 16:58:10 qgs-comp systemd-udevd[5394]: 2-1.5: Failed to create/update device symlink '/dev/ttyUSB0', ignoring: File exists Jun 1 16:58:10 qgs-comp snapd[942]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug Jun 1 16:58:10 qgs-comp mtp-probe: checking bus 2, device 5: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5" Jun 1 16:58:10 qgs-comp mtp-probe: bus: 2, device: 5 was not an MTP device Jun 1 16:58:10 qgs-comp colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied I noticed this line: Jun 1 16:58:10 qgs-comp systemd-udevd[5394]: 2-1.5: Failed to create/update device symlink '/dev/ttyUSB0', ignoring: File exists Why is it happening? There's no /dev/ttyUSB0 neither before nor after I attach ftdi device to a USB port. ** Affects: ubuntu Importance: Undecided Status: New ** Summary changed: - /dev/ttyUSB0 file disappears on Ubuntu 22.04 + /dev/ttyUSB0 doesn't appear (fresh Ubuntu 22.04) ** Summary changed: - /dev/ttyUSB0 doesn't appear (fresh Ubuntu 22.04) + /dev/ttyUSB0 doesn't appear for an FTDI (fresh Ubuntu 22.04) ** Summary changed: - /dev/ttyUSB0 doesn't appear for an FTDI (fresh Ubuntu 22.04) + /dev/ttyUSB0 doesn't appear for an FTDI on fresh Ubuntu 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976534 Title: /dev/ttyUSB0 doesn't appear for an FTDI on fresh Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1976534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976533] Re: [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976533 Title: [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1976533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
